Disclosure of Invention
The application provides a communication method and a communication device, which send a message for decision traffic distribution to an F1 anchor point CU through two non-F1 anchor point CUs under the condition that a double-connection scene and a continuous local migration scene of an IAB node coexist, so that the F1 anchor point CUs can make reasonable traffic distribution decisions for two communication paths between the two non-F1 anchor point CUs and the IAB node.
In a first aspect, a communication method is provided, which may be performed by a host node, or may also be performed by a chip or a circuit configured in the host node, which is not limited by the present application.
The method comprises the steps that a first host node receives first traffic migration configuration information, the first traffic migration configuration information is used for determining traffic distribution when traffic of the first host node migrates to a second topology and a third topology, the second topology is a traffic transmission path between the second host node and a first IAB node, the third topology is a traffic transmission path between the third host node and the first IAB node, the first IAB node comprises a first distributed unit and a first mobile terminal, F1 connection exists between the first distributed unit and the first host node, RRC connection exists between the first mobile terminal and the second host node and between the first mobile terminal and the third host node, and the first host node distributes the traffic of the first host node to the second topology and the third topology according to the first traffic migration configuration information.
According to the scheme of the application, the first host node is connected with the first IAB node by F1, and the flow in the first host node is distributed to the second topology and the third topology by receiving the first flow migration configuration information, so that unreasonable flow distribution of the F1 anchor point CU when the link quality of the return link is not known is avoided. The method and the device realize the flow distribution in the IAB node continuous local migration scene and the double connection scene which are not supported in the prior art.
In one possible implementation, the first traffic migration configuration information includes second traffic migration configuration information indicating migration to the second topology and third traffic migration configuration information indicating migration to the third topology.
In one possible implementation, the first host node receiving the first traffic migration configuration information includes the first host node receiving the second traffic migration configuration information and the third traffic migration configuration information from the second host node, or the first host node receiving the first traffic migration configuration information includes the first host node receiving the second traffic migration configuration information from the second host node, the first host node receiving the third traffic migration configuration information from the third host node.
In one possible implementation, the second traffic migration configuration information includes traffic information and traffic transmission path information migrated to the second topology, and the third traffic migration configuration information includes traffic information and traffic transmission path information migrated to the third topology.
In one possible implementation, the traffic transmission path information includes an IP address and/or backhaul link BH information of the traffic transmission.
In one possible implementation, before the first host node receives the first traffic migration configuration information, the method further includes the first host node sending first traffic migration request information to the second host node, the first traffic migration request information being used to request that traffic of the first host node be migrated into the second topology and the third topology.
In one possible implementation, after the first host node receives the first traffic migration configuration information, the method further includes the first host node sending first traffic migration request information, where the first traffic migration request information is used to request migration of traffic of the first host node into the second topology and the third topology, and the first host node receiving first traffic migration response information, where the first traffic migration response information is used to instruct the first host node to migrate traffic of the first host node into the second topology and the third topology.
In one possible implementation, the first host node sending the first traffic migration request information includes the first host node sending the first traffic migration request information to the second host node.
In one possible implementation, the first traffic migration request information includes second traffic migration request information for requesting to migrate traffic of the first host node into the second topology and third traffic migration request information for requesting to migrate traffic of the first host node into the third topology, and the first host node sending the first traffic migration request information includes the first host node sending the second traffic migration request information to the second host node and sending the third traffic migration request information to the third host node.
In one possible implementation, the first host node receiving first traffic migration response information includes the first host node receiving the first traffic migration response information from the second host node.
In one possible implementation, the first traffic migration response information includes second traffic migration response information for instructing the first host node to migrate traffic of the first host node into the second topology and third traffic migration response information for instructing the first host node to migrate traffic of the first host node into the third topology, and the first host node receiving the first traffic migration response information includes the first host node receiving the second traffic migration response information from the second host node and the third traffic migration response information from the third host node.
In one possible implementation, the first traffic migration configuration information includes second traffic migration configuration information indicating migration to the second topology and third traffic migration configuration information indicating migration to the third topology, the second traffic migration configuration information including link quality and/or resource allocation information of the second topology, the third traffic migration configuration information including link quality and/or resource allocation information of the third topology.
In a second aspect, a communication method is provided, which may be performed by a host node, or may also be performed by a chip or a circuit configured in the host node, which is not limited by the present application.
The method comprises the steps that a second host node determines second traffic migration configuration information, the second traffic migration configuration information is used for determining traffic distribution of traffic migration of a first host node to a second topology, the second topology is a traffic transmission path between the second host node and a first IAB node, the first IAB node comprises a first distributed unit and a first mobile terminal, F1 connection exists between the first distributed unit and the first host node, RRC connection exists between the first mobile terminal and the second host node and RRC connection exists between the first mobile terminal and a third host node, and the second host node sends the second traffic migration configuration information to the first host node.
In one possible implementation, the second traffic migration configuration information includes traffic information and traffic transmission path information migrated to the second topology.
In one possible implementation, the traffic transmission path information of the second topology includes an IP address and/or backhaul link BH information of traffic transmitted in the second topology.
In one possible implementation, the method further includes the second host node receiving third traffic migration configuration information from the third host node, the third traffic migration configuration information being used to determine traffic distribution of traffic migration of the first host node to the third topology, the second host node sending the third traffic migration configuration information to the first host node.
In one possible implementation, the third traffic migration configuration information includes traffic information and traffic transmission path information migrated to the third topology.
In one possible implementation, the traffic transmission path information of the third topology includes an IP address and/or backhaul link BH information of the traffic transmitted in the third topology.
In one possible implementation, before the second host node sends the second traffic migration configuration information to the first host node, the method further includes the second host node receiving first traffic migration request information from the first host node, the first traffic migration request information being used to request that traffic of the first host node be migrated into the second topology and a third topology, the third topology being a traffic transmission path between the third host node and the first IAB node, the second host node sending third traffic migration request information to the third host node, the third traffic migration request information being used to request that traffic of the first host node be migrated into the third topology.
In one possible implementation, the method further comprises the second host node sending the first identification information to the third host node, the first identification information being used to determine to send a message to the first host node.
In a possible implementation, the first identification information includes an identification of the first host node, and optionally, an identification of the first mobile terminal under the first host node.
Optionally, the identification of the first home node may include a base station ID and/or an IP address of the first home node, and the identification of the first mobile terminal under the first home node may include an ID of a terminal device Xn application protocol (XnAP) of the first mobile terminal under the first home node.
In one possible implementation, after the second host node sends the second traffic migration configuration information to the first host node, the method further includes the second host node receiving first traffic migration request information sent by the first host node, where the first traffic migration request information is used to request migration of traffic of the first host node into the second topology and the third topology, the second host node sending third traffic migration request information to the third host node, where the third traffic migration request information is used to request migration of traffic of the first host node into the third topology, or the method further includes the second host node receiving second traffic migration request information sent by the first host node, where the second traffic migration request information is used to request migration of traffic of the first host node into the second topology.
In one possible implementation, the first traffic migration response information includes second traffic migration response information, the second traffic migration response information being used to instruct the first host node to migrate traffic of the first host node into the second topology, the method further including the second host node sending the first traffic migration response information or the second traffic migration response information to the first host node.
In one possible implementation, the second traffic migration configuration information includes link quality and/or resource allocation information for the second topology.
In a third aspect, a communication method is provided, which may be performed by a host node, or may also be performed by a chip or circuit configured in the host node, which is not limited by the present application.
The method comprises the steps that a third host node determines third flow migration configuration information, the third flow migration configuration information is used for determining flow distribution of flow migration of a first host node to a third topology, the third topology is a flow transmission path between the third host node and a first IAB node, the first IAB node comprises a first distributed unit and a first mobile terminal, F1 connection exists between the first distributed unit and the first host node, RRC connection exists between the first mobile terminal and a second host node and between the first mobile terminal and the third host node, and the third host node sends the third flow migration configuration information to the first host node or the second host node.
In one possible implementation, the third traffic migration configuration information includes traffic information and traffic transmission path information migrated to the third topology.
In one possible implementation, the traffic transmission path information of the third topology includes an IP address and/or backhaul link BH information of the traffic transmitted in the third topology.
In one possible implementation, before the third host node sends the third traffic migration configuration information to the first host node or the second host node, the method further includes the third host node receiving third traffic migration request information from the second host node, the third traffic migration request information being used to request migration of traffic of the first host node into the third topology.
In one possible implementation, the method further includes the third host node receiving first identification information from the second host node, the first identification information being used to determine to send a message to the first host node, and the third host node sending the third flow migration configuration information to the first host node or the second host node including the third host node sending the third flow migration configuration information to the first host node according to the first identification information.
In a possible implementation, the first identification information includes an identification of the first host node, and optionally, an identification of the first mobile terminal under the first host node.
Optionally, the identification of the first home node may include a base station ID and/or an IP address of the first home node, and the identification of the first mobile terminal under the first home node may include an ID of a terminal device Xn application protocol (XnAP) of the first mobile terminal under the first home node.
In one possible implementation, after the third host node sends the third traffic migration configuration information to the first host node or the second host node, the method further includes the third host node receiving third traffic migration request information from the first host node or the second host node, the third traffic migration request information being used to request migration of traffic of the first host node into the third topology, the third host node sending third traffic migration response information to the first host node or the second host node, the third traffic migration response information being used to instruct the first host node to migrate traffic of the first host node into the third topology.
In one possible implementation, the third traffic migration configuration information includes link quality and/or resource allocation information for the third topology.
In a fourth aspect, a communication method is provided, which may be performed by a host node, or may also be performed by a chip or a circuit configured in the host node, which is not limited by the present application.
The method comprises the steps that a second host node sends fourth traffic migration request information, the fourth traffic migration request information is used for requesting traffic of a first host node to be distributed to a second topology and traffic of a third topology to be migrated between the second topology and the third topology, the second topology is a traffic transmission path between the second host node and a first IAB node, the third topology is a traffic transmission path between the third host node and the first IAB node, the first IAB node comprises a first distributed unit and a first mobile terminal, F1 connection exists between the first distributed unit and the first host node, the first mobile terminal is connected with the second host node and the third host node in an RRC mode, the second host node receives fourth traffic migration configuration information, the fourth traffic migration configuration information is used for determining traffic information needed to be migrated between the second topology and the third topology, and the second host node sends fourth traffic migration indication information, and the fourth traffic migration indication information is used for indicating traffic needed to be migrated between the second topology and the third topology.
According to the scheme of the application, after the two non-F1 anchor points CU exchange traffic withdrawal or traffic migration information in the IAB node continuous local migration scene and the double connection scene, traffic migration or traffic redistribution of the F1 anchor point CU in two communication paths between the two non-F1 anchor points CU and the IAB node is realized.
In one possible implementation, the fourth traffic migration indication information includes first mapping configuration information of the second topology, and the second host node sending the fourth traffic migration indication information includes sending, by the second host node, the first mapping configuration information of the second topology to the first host node, where the first mapping configuration information includes updated backhaul link BH resource mapping information and/or quality of service mapping information of the second topology, and the first mapping configuration information is used to instruct the first host node to redetermine traffic transmitted in the second topology.
In a possible implementation manner, the fourth traffic migration indication information further includes second mapping configuration information of the third topology, and the method further includes that the second host node sends the second mapping configuration information of the third topology to the first host node, where the second mapping configuration information includes updated backhaul link BH resource mapping information and/or service quality mapping information of the third topology, and the second mapping configuration information is used to instruct the first host node to redetermine traffic transmitted in the third topology.
In one possible implementation, the second host node sending fourth traffic migration request information includes the second host node sending the fourth traffic migration request information to the first host node, and the second host node receiving fourth traffic migration configuration information includes the second host node receiving the fourth traffic migration configuration information from the first host node, or the second host node sending fourth traffic migration request information includes the second host node sending the fourth traffic migration request information to the third host node, and the second host node receiving fourth traffic migration configuration information includes the second host node receiving the fourth traffic migration configuration information from the third host node.
In one possible implementation, the second host node sending fourth traffic migration request information to the third host node further includes the second host node sending first identification information to the third host node, the first identification information being used to determine to send a message to the first host node.
In a possible implementation, the first identification information includes an identification of the first host node, and optionally, an identification of the first mobile terminal under the first host node.
Optionally, the identification of the first home node may include a base station ID and/or an IP address of the first home node, and the identification of the first mobile terminal under the first home node may include an ID of a terminal device Xn application protocol (XnAP) of the first mobile terminal under the first home node.
In one possible implementation, the second host node includes a second distributed unit, the third host node includes a third distributed unit, a tunnel for transmitting traffic is provided between the second distributed unit and the third distributed unit, the fourth traffic migration indication information includes first traffic transmission indication information or second traffic transmission indication information, and the second host node sends fourth traffic migration indication information includes sending the first traffic transmission indication information to the second distributed unit when migrating part of the traffic of the second topology to the third topology, where the first traffic transmission indication information is used for indicating that part of the traffic of the second topology is transmitted from the second distributed unit to the third distributed unit via the tunnel, or sending the second traffic transmission indication information to the second distributed unit when migrating part of the traffic of the third topology to the second topology, where the second traffic transmission indication information is used for indicating that the part of the traffic of the third topology reaches the selected traffic transmission link of the second distributed unit.
In one possible implementation, the first traffic transmission indication information includes an IP address of the third distributed unit.
In one possible implementation, the first traffic transmission indication information further includes an IP address of a portion of the traffic of the second topology.
In one possible implementation, the second traffic transmission indication information includes backhaul link BH resources mapped when a portion of traffic of the third topology arrives at the second distributed element.
In a fifth aspect, a communication method is provided, which may be performed by a host node, or may also be performed by a chip or a circuit configured in the host node, which is not limited by the present application.
The method comprises the steps that a third host node receives fourth traffic migration request information, the fourth traffic migration request information is used for requesting traffic of a first host node to be distributed to a second topology and traffic of a third topology to be migrated between the second topology and the third topology, the second topology is a traffic transmission path between the second host node and a first IAB node, the third topology is a traffic transmission path between the third host node and the first IAB node, the first IAB node comprises a first distributed unit and a first mobile terminal, F1 connection exists between the first distributed unit and the first host node, the first mobile terminal, the second host node and the third host node are connected, the third host node sends fourth traffic migration configuration information, the fourth traffic migration configuration information is used for determining traffic information needed to be migrated between the second topology and the third topology, and the third host node sends fourth traffic migration indication information, and the fourth traffic migration indication information is used for indicating traffic needed to be migrated between the second topology and the third topology.
In one possible implementation, the third host node receiving the fourth traffic migration request information includes the third host node receiving the fourth traffic migration request information from the first host node, the third host node sending the fourth traffic migration configuration information includes the third host node sending the fourth traffic migration configuration information to the first host node, or the third host node receiving the fourth traffic migration request information includes the third host node receiving the fourth traffic migration request information from the second host node, the third host node sending the fourth traffic migration configuration information includes the third host node sending the fourth traffic migration configuration information to the second host node.
In one possible implementation, the third host node receiving the fourth traffic migration request information from the second host node further includes the third host node receiving first identification information from the second host node, the first identification information being used for determining to send a message to the first host node, and the third host node sending fourth traffic migration indication information includes the third host node sending the fourth traffic migration indication information to the first host node according to the first identification information.
In a possible implementation, the first identification information includes an identification of the first host node, and optionally, an identification of the first mobile terminal under the first host node.
Optionally, the first identification information includes a base station ID and/or an IP address of the first home node, and an ID of a terminal device Xn application protocol XnAP of the first mobile terminal under the first home node.
In one possible implementation, the fourth traffic migration indication information includes second mapping configuration information of the third topology, where the second mapping configuration information includes updated backhaul link BH resource mapping information and/or quality of service mapping information of the third topology, the second mapping configuration information is used to instruct the first host node to redetermine traffic transmitted in the third topology, and the third host node sending the fourth traffic migration indication information includes sending the second mapping configuration information to the first host node or the second host node by the third host node.
In one possible implementation, the second host node includes a second distributed unit, the third host node includes a third distributed unit, a tunnel for transmitting traffic is provided between the second distributed unit and the third distributed unit, the fourth traffic migration indication information includes third traffic transmission indication information or fourth traffic transmission indication information, and the third host node sends fourth traffic migration indication information to the third distributed unit, where the third host node sends the third traffic transmission indication information to the third distributed unit, where the third traffic transmission indication information is used to indicate that the partial traffic of the third topology is transmitted from the third distributed unit to the second distributed unit via the tunnel, or sends the fourth traffic transmission indication information to the third distributed unit, where the third host node migrates the partial traffic of the second topology to the third distributed unit, where the fourth traffic transmission indication information is used to indicate that the partial traffic of the second topology reaches the selected link after the third distributed unit.
In one possible implementation, the third traffic transmission indication information includes an IP address of the second distributed unit.
In one possible implementation, the third traffic transmission indication information further includes an IP address of a portion of traffic of the third topology.
In one possible implementation, the fourth traffic transmission indication information includes backhaul link BH resources mapped when a portion of traffic of the second topology arrives at the third distributed element.
In a sixth aspect, a communication method is provided, which may be performed by a host node, or may also be performed by a chip or a circuit configured in the host node, which is not limited by the present application.
The method comprises the steps that a first host node receives fourth traffic migration indication information, the fourth traffic migration indication information is used for indicating traffic to be migrated between a second topology and a third topology, the second topology is a traffic transmission path between the second host node and a first IAB node, the third topology is a traffic transmission path between the third host node and the first IAB node, the first IAB node comprises a first distributed unit and a first mobile terminal, F1 connection exists between the first distributed unit and the first host node, the first mobile terminal, the second host node and the third host node are connected in an RRC mode, and the first host node redistributes the traffic of the first host node to the second topology and the third topology according to the fourth traffic migration indication information.
In one possible implementation, the method further comprises the steps that the first host node receives fourth traffic migration request information from the second host node, the fourth traffic migration request information is used for requesting traffic migration between the second topology and the third topology, the first host node sends the fourth traffic migration request information to the third host node, the first host node receives fourth traffic migration configuration information from the third host node, the fourth traffic migration configuration information is used for determining traffic information needing to be migrated between the second topology and the third topology, and the first host node sends the fourth traffic migration configuration information to the second host node.
In one possible implementation, the fourth traffic migration indication information includes first mapping configuration information of the second topology and second mapping configuration information of the third topology, the first mapping configuration information including updated backhaul link BH resource mapping information and/or quality of service mapping information of the second topology, the first mapping configuration information being for indicating the first host node to re-determine traffic transmitted in the second topology, the second mapping configuration information including updated backhaul link BH resource mapping information and/or quality of service mapping information of the third topology, the second mapping configuration information being for indicating the first host node to re-determine traffic transmitted in the third topology, the first host node receiving the fourth traffic migration indication information including the first host node receiving the first mapping configuration information and the second mapping configuration information from the second host node, or the first host node receiving the first mapping configuration information from the second host node and the second mapping configuration information from the third host node.
In a seventh aspect, a communication apparatus is provided, which is a home node having an F1 connection with a first mobile terminal, and the apparatus includes a receiving module configured to receive first traffic migration configuration information, where the first traffic migration configuration information is used to determine traffic distribution when traffic of the first home node migrates to a second topology and a third topology, the second topology is a traffic transmission path between the second home node and a first IAB node, the third topology is a traffic transmission path between the third home node and the first IAB node, the first IAB node includes a first distributed unit and a first mobile terminal, an F1 connection is between the first distributed unit and the first home node, and the first mobile terminal has an RRC connection with both the second home node and the third home node, and a processing module configured to distribute the traffic of the first home node to the second topology and the third topology according to the first traffic migration configuration information.
In one possible implementation, the first traffic migration configuration information includes second traffic migration configuration information indicating migration to the second topology and third traffic migration configuration information indicating migration to the third topology.
In a possible implementation, the receiving module is specifically configured to receive the second traffic migration configuration information and the third traffic migration configuration information, or the receiving module is specifically configured to receive the second traffic migration configuration information from the second host node and the third traffic migration configuration information from the third host node.
In one possible implementation, the second traffic migration configuration information includes traffic information and traffic transmission path information migrated to the second topology, and the third traffic migration configuration information includes traffic information and traffic transmission path information migrated to the third topology.
In one possible implementation, the traffic transmission path information includes an IP address and/or backhaul link BH information of the traffic transmission.
In one possible implementation, the apparatus further includes a sending module, before the receiving module receives the first traffic migration configuration information, the sending module is configured to send first traffic migration request information, where the first traffic migration request information is used to request migration of traffic of the first host node into the second topology and the third topology.
In one possible implementation manner, the device further includes a sending module, after the receiving module receives the first traffic migration configuration information, the sending module is configured to send first traffic migration request information, where the first traffic migration request information is used to request migration of the traffic of the first host node into the second topology and the third topology, and the receiving module is specifically configured to receive first traffic migration response information, where the first traffic migration response information is used to instruct the first host node to migrate the traffic of the first host node into the second topology and the third topology.
In a possible implementation manner, the sending module is specifically configured to send the first traffic migration request information to the second host node.
In one possible implementation manner, the first traffic migration request information includes second traffic migration request information and third traffic migration request information, where the second traffic migration request information is used to request migration of traffic of the first host node into the second topology, the third traffic migration request information is used to request migration of traffic of the first host node into the third topology, and the sending module is specifically configured to send the second traffic migration request information to the second host node, and send the third traffic migration request information to the third host node.
In one possible implementation, the receiving module is specifically configured to receive the first traffic migration response information from the second host node.
In one possible implementation manner, the first traffic migration response information includes second traffic migration response information and third traffic migration response information, the second traffic migration response information is used for instructing the first host node to migrate traffic of the first host node into the second topology, the third traffic migration request information is used for instructing the first host node to migrate traffic of the first host node into the third topology, and the receiving module is specifically used for receiving the second traffic migration response information from the second host node and receiving the third traffic migration response information from the third host node.
In one possible implementation, the first traffic migration configuration information includes second traffic migration configuration information indicating migration to the second topology and third traffic migration configuration information indicating migration to the third topology, the second traffic migration configuration information including link quality and/or resource allocation information of the second topology, the third traffic migration configuration information including link quality and/or resource allocation information of the third topology.
In an eighth aspect, a communication apparatus is provided, which is a home node having an RRC connection with a first mobile terminal, and the apparatus includes a determining module configured to determine second traffic migration configuration information, where the second traffic migration configuration information is used to determine traffic distribution of traffic migration of the first home node to a second topology, where the second topology is a traffic transmission path between the second home node and a first IAB node, and the first IAB node includes a first distributed unit and a first mobile terminal, where an F1 connection exists between the first distributed unit and the first home node, and where the first mobile terminal has an RRC connection with both the second home node and a third home node, and a transmitting module configured to transmit the second traffic migration configuration information to the first home node.
In one possible implementation, the second traffic migration configuration information includes traffic information and traffic transmission path information migrated to the second topology.
In one possible implementation, the traffic transmission path information of the second topology includes an IP address and/or backhaul link BH information of traffic transmitted in the second topology.
In a possible implementation manner, the device further comprises a receiving module, a sending module and a sending module, wherein the receiving module is used for receiving third flow migration configuration information from the third host node, the third flow migration configuration information is used for determining flow distribution of the flow migration of the first host node to the third topology, and the sending module is specifically used for sending the third flow migration configuration information to the first host node by the second host node.
In one possible implementation, the third traffic migration configuration information includes traffic information and traffic transmission path information migrated to the third topology.
In one possible implementation, the traffic transmission path information of the third topology includes an IP address and/or backhaul link BH information of the traffic transmitted in the third topology.
In one possible implementation manner, before the sending module sends the second traffic migration configuration information to the first host node, the receiving module is specifically configured to receive first traffic migration request information from the first host node, where the first traffic migration request information is used to request migration of traffic of the first host node into the second topology and a third topology, where the third topology is a traffic transmission path between the third host node and the first IAB node, and the sending module is specifically configured to send third traffic migration request information to the third host node, where the third traffic migration request information is used to request migration of traffic of the first host node into the third topology.
In a possible implementation manner, the sending module is further configured to send the first identification information to the third host node, where the first identification information is used to determine to send a message to the first host node.
In a possible implementation, the first identification information includes an identification of the first host node, and optionally, an identification of the first mobile terminal under the first host node.
Optionally, the identification of the first home node may include a base station ID and/or an IP address of the first home node, and the identification of the first mobile terminal under the first home node may include an ID of a terminal device Xn application protocol (XnAP) of the first mobile terminal under the first home node.
In one possible implementation manner, after the sending module sends the second traffic migration configuration information to the first host node, the receiving module is further configured to receive first traffic migration request information sent by the first host node, where the first traffic migration request information is used for requesting migration of traffic of the first host node into the second topology and the third topology, the sending module is further configured to send third traffic migration request information to the third host node, where the third traffic migration request information is used for requesting migration of traffic of the first host node into the third topology, or the receiving module is further configured to receive second traffic migration request information sent by the first host node, where the second traffic migration request information is used for requesting migration of traffic of the first host node into the second topology.
In one possible implementation, the first traffic migration response information includes second traffic migration response information, where the second traffic migration response information is used to instruct the first host node to migrate traffic of the first host node into the second topology, and the sending module is further configured to send the first traffic migration response information or the second traffic migration response information to the first host node.
In one possible implementation, the second traffic migration configuration information includes link quality and/or resource allocation information for the second topology.
In a ninth aspect, a communication apparatus is provided, which is a home node having an RRC connection with a first mobile terminal, and the apparatus includes a processing module configured to determine third traffic migration configuration information, where the third traffic migration configuration information is used to determine traffic distribution of traffic migration of the first home node to a third topology, where the third topology is a traffic transmission path between the third home node and a first IAB node, and the first IAB node includes a first distributed unit and a first mobile terminal, where an F1 connection exists between the first distributed unit and the first home node, where the first mobile terminal has an RRC connection with both a second home node and the third home node, and a transmitting module configured to transmit the third traffic migration configuration information to the first home node or the second home node.
In one possible implementation, the third traffic migration configuration information includes traffic information and traffic transmission path information migrated to the third topology.
In one possible implementation, the traffic transmission path information of the third topology includes an IP address and/or backhaul link BH information of the traffic transmitted in the third topology.
In one possible implementation, before the sending module sends the third traffic migration configuration information to the first host node or the second host node, the receiving module is further configured to receive third traffic migration request information from the second host node, where the third traffic migration request information is used to request migration of traffic of the first host node into the third topology.
In a possible implementation manner, the receiving module is further configured to receive first identification information from the second host node, where the first identification information is used to determine to send a message to the first host node, and the sending module is specifically configured to send the third flow migration configuration information to the first host node or the second host node, where the sending module is specifically configured to send the third flow migration configuration information to the first host node according to the first identification information.
In a possible implementation, the first identification information includes an identification of the first host node, and optionally, an identification of the first mobile terminal under the first host node.
Optionally, the identification of the first home node may include a base station ID and/or an IP address of the first home node, and the identification of the first mobile terminal under the first home node may include an ID of a terminal device Xn application protocol (XnAP) of the first mobile terminal under the first home node.
In one possible implementation manner, after the sending module sends the third traffic migration configuration information to the first host node or the second host node, the receiving module is specifically configured to receive third traffic migration request information from the first host node or the second host node, where the third traffic migration request information is used to request migration of traffic of the first host node into the third topology, and the sending module is specifically configured to send third traffic migration response information to the first host node or the second host node, where the third traffic migration response information is used to instruct the first host node to migrate traffic of the first host node into the third topology.
In one possible implementation, the third traffic migration configuration information includes link quality and/or resource allocation information for the third topology.
In a tenth aspect, a communication apparatus is provided, which is a home node having an RRC connection with a first mobile terminal, and the apparatus includes a transmitting module configured to transmit fourth traffic migration request information for requesting traffic migration between a second topology and a third topology, the second topology being a traffic transmission path between the second home node and a first IAB node, the third topology being a traffic transmission path between the third home node and the first IAB node, the first IAB node including a first distributed unit and a first mobile terminal, an F1 connection being present between the first distributed unit and the first home node, the first mobile terminal having an RRC connection with the second home node and the third home node, a receiving module configured to receive fourth traffic migration configuration information for determining traffic information to be migrated between the second topology and the third topology, and a transmitting module configured to transmit fourth traffic migration configuration information indicating that traffic migration between the second topology and the third topology is required, and the fourth traffic migration information indicating that traffic migration between the fourth topology is required.
According to the scheme of the application, after the two non-F1 anchor points CU exchange traffic withdrawal or traffic migration information in the IAB node continuous local migration scene and the double connection scene, traffic migration or traffic redistribution of the F1 anchor point CU in two communication paths between the two non-F1 anchor points CU and the IAB node is realized.
In a possible implementation manner, the fourth traffic migration indication information includes first mapping configuration information of the second topology, and the sending module is specifically configured to send the first mapping configuration information of the second topology to the first host node, where the first mapping configuration information includes updated backhaul link BH resource mapping information and/or quality of service mapping information of the second topology, and the first mapping configuration information is used to instruct the first host node to redetermine traffic transmitted in the second topology.
In a possible implementation manner, the fourth traffic migration indication information further includes second mapping configuration information of the third topology, and the sending module is further configured to send the second mapping configuration information of the third topology to the first host node, where the second mapping configuration information includes updated backhaul link BH resource mapping information and/or quality of service mapping information of the third topology, and the second mapping configuration information is used to instruct the first host node to redetermine traffic transmitted in the third topology.
In one possible implementation manner, the sending module is specifically configured to send the fourth traffic migration request information to the first host node, the receiving module is specifically configured to receive the fourth traffic migration configuration information from the first host node, or the sending module is specifically configured to send the fourth traffic migration request information to the third host node, and the receiving module is specifically configured to receive the fourth traffic migration configuration information from the third host node.
In one possible implementation, the sending module is further configured to send first identification information to the third host node, where the first identification information is used to determine to send a message to the first host node.
In a possible implementation, the first identification information includes an identification of the first host node, and optionally, an identification of the first mobile terminal under the first host node.
Optionally, the identification of the first home node may include a base station ID and/or an IP address of the first home node, and the identification of the first mobile terminal under the first home node may include an ID of a terminal device Xn application protocol (XnAP) of the first mobile terminal under the first home node.
In a possible implementation manner, the second host node comprises a second distributed unit, the third host node comprises a third distributed unit, a tunnel for transmitting traffic is arranged between the second distributed unit and the third distributed unit, the fourth traffic migration indication information comprises first traffic transmission indication information or second traffic transmission indication information, and the sending module is specifically configured to send the first traffic transmission indication information to the second distributed unit when the partial traffic of the second topology is migrated to the third topology, where the first traffic transmission indication information is used for indicating that the partial traffic of the second topology is transmitted from the second distributed unit to the third distributed unit through the tunnel, or send the second traffic transmission indication information to the second distributed unit when the partial traffic of the third topology is migrated to the second topology, where the second traffic transmission indication information is used for indicating that the partial traffic of the third topology reaches a traffic transmission link selected after the second distributed unit.
In one possible implementation, the first traffic transmission indication information includes an IP address of the third distributed unit.
In one possible implementation, the first traffic transmission indication information further includes an IP address of a portion of the traffic of the second topology.
In one possible implementation, the second traffic transmission indication information includes backhaul link BH resources mapped when a portion of traffic of the third topology arrives at the second distributed element.
In an eleventh aspect, a communication apparatus is provided, which is a host node having an RRC connection with a first mobile terminal, and the apparatus includes a receiving module configured to receive fourth traffic migration request information, where the fourth traffic migration request information is configured to request that traffic of a first host node be allocated to a second topology and traffic of a third topology be migrated between the second topology and the third topology, the second topology is a traffic transmission path between the second host node and a first IAB node, the third topology is a traffic transmission path between the third host node and the first IAB node, the first IAB node includes a first distributed unit and a first mobile terminal, where an F1 connection exists between the first distributed unit and the first host node, and where the first mobile terminal has an RRC connection with the second host node and the third host node, a sending module configured to send fourth traffic migration configuration information, where the fourth traffic migration configuration information is configured to determine traffic information that needs to be migrated between the second topology and the third topology, and a sending module is specifically configured to send fourth traffic migration information indicating that traffic needs to be migrated between the second topology and the third topology.
In one possible implementation manner, the receiving module is specifically configured to receive the fourth traffic migration request information from the first host node, the sending module is specifically configured to send the fourth traffic migration configuration information to the first host node, or the receiving module is specifically configured to receive the fourth traffic migration request information from the second host node, and the sending module is specifically configured to send the fourth traffic migration configuration information to the second host node.
In a possible implementation manner, the receiving module is further configured to receive first identification information from the second host node, where the first identification information is used to determine to send a message to the first host node, and the sending module is specifically configured to send the fourth traffic migration indication information to the first host node according to the first identification information.
In a possible implementation, the first identification information includes an identification of the first host node, and optionally, an identification of the first mobile terminal under the first host node.
Optionally, the identification of the first home node may include a base station ID and/or an IP address of the first home node, and the identification of the first mobile terminal under the first home node may include an ID of a terminal device Xn application protocol (XnAP) of the first mobile terminal under the first home node.
In a possible implementation manner, the fourth traffic migration indication information includes second mapping configuration information of the third topology, where the second mapping configuration information includes updated backhaul link BH resource mapping information and/or quality of service mapping information of the third topology, the second mapping configuration information is used to instruct the first host node to redetermine traffic transmitted in the third topology, and the sending module is specifically configured to send the second mapping configuration information to the first host node or the second host node.
In one possible implementation manner, the second host node comprises a second distributed unit, the third host node comprises a third distributed unit, a tunnel for transmitting traffic is arranged between the second distributed unit and the third distributed unit, the fourth traffic migration indicating information comprises third traffic transmission indicating information or fourth traffic transmission indicating information, and the sending module is specifically configured to send the third traffic transmission indicating information to the third distributed unit when the partial traffic of the third topology is migrated to the second topology, where the third traffic transmission indicating information is used for indicating that the partial traffic of the third topology is transmitted from the third distributed unit to the second distributed unit through the tunnel, or send the fourth traffic transmission indicating information to the third distributed unit when the partial traffic of the second topology is migrated to the third topology, where the fourth traffic transmission indicating information is used for indicating that the partial traffic of the second topology reaches a traffic transmission link selected after the third distributed unit.
In one possible implementation, the third traffic transmission indication information includes an IP address of the second distributed unit.
In one possible implementation, the third traffic transmission indication information further includes an IP address of a portion of traffic of the third topology.
In one possible implementation, the fourth traffic transmission indication information includes backhaul link BH resources mapped when a portion of traffic of the second topology arrives at the third distributed element.
In a twelfth aspect, a communication device is provided, which is a home node connected with a first mobile terminal by F1, and the device includes a receiving module configured to receive fourth traffic migration indication information, where the fourth traffic migration indication information is configured to indicate to migrate traffic between the second topology and the third topology, the second topology is a traffic transmission path between the second home node and a first IAB node, the third topology is a traffic transmission path between the third home node and the first IAB node, the first IAB node includes a first distributed unit and a first mobile terminal, an F1 connection exists between the first distributed unit and the first home node, and the first mobile terminal is connected with RRC between the second home node and the third home node, and a processing module configured to redistribute traffic of the first home node to the second topology and the third topology according to the fourth traffic migration indication information.
In a possible implementation manner, the device further comprises a sending module, the receiving module is further configured to receive fourth traffic migration request information from the second host node, the fourth traffic migration request information is used for requesting traffic migration between the second topology and the third topology by distributing the first host node to the second topology and the third topology, the sending module is configured to send the fourth traffic migration request information to the third host node, the receiving module is specifically configured to receive fourth traffic migration configuration information from the third host node, the fourth traffic migration configuration information is used for determining traffic information needing to be migrated between the second topology and the third topology, and the sending module is specifically configured to send the fourth traffic migration configuration information to the second host node.
In a possible implementation manner, the fourth traffic migration indication information includes first mapping configuration information of the second topology and second mapping configuration information of the third topology, where the first mapping configuration information includes updated backhaul link BH resource mapping information and/or quality of service mapping information of the second topology, the first mapping configuration information is used to instruct the first host node to redefine traffic transmitted in the second topology, the second mapping configuration information includes updated backhaul link BH resource mapping information and/or quality of service mapping information of the third topology, the second mapping configuration information is used to instruct the first host node to redefine traffic transmitted in the third topology, and the receiving module is used to receive the first mapping configuration information and the second mapping configuration information from the second host node, or the receiving module is used to receive the first mapping configuration information from the second host node and the second mapping configuration information from the third host node.
In a thirteenth aspect, a wireless communication device is provided, comprising means or units for performing the method of the first aspect or any one of the possible implementations of the first aspect.
In a fourteenth aspect, there is provided a wireless communication device comprising means or units for performing the method of the second aspect or any one of the possible implementations of the second aspect.
A fifteenth aspect provides a wireless communications apparatus comprising means or units for performing the method of the third aspect or any one of the possible implementations of the third aspect.
In a sixteenth aspect, there is provided a wireless communication device comprising means or units for performing the method of the fourth aspect or any one of the possible implementations of the fourth aspect.
A seventeenth aspect provides a wireless communication device comprising means or units for performing the method of the fifth aspect or any one of the possible implementations of the fifth aspect.
In an eighteenth aspect, there is provided a wireless communication device comprising means or units for performing the method of the sixth aspect or any one of the possible implementations of the sixth aspect.
In a nineteenth aspect, a communications device is provided, comprising a processor coupled with a memory, operable to perform the method of the first aspect and its possible implementation, the sixth aspect and its possible implementation. In one possible implementation, the communication device further includes a memory. In one possible implementation, the communication device further includes a communication interface, and the processor is coupled to the communication interface. In one possible implementation, the communication device further includes a communication interface, and the processor is coupled to the communication interface.
In one implementation, the communication device is a home node. When the communication device is a hosting node, the communication interface may be a transceiver, or an input/output interface.
In another implementation, the communication device is a chip or a system-on-chip. When the communication device is a chip or a chip system, the communication interface may be an input/output interface, an interface circuit, an output circuit, an input circuit, a pin, or related circuits on the chip or the chip system. The processor may also be embodied as processing circuitry or logic circuitry.
In a twentieth aspect, a communications device is provided, comprising a processor coupled to a memory, operable to execute instructions in the memory to implement the method of the second aspect and possible implementations thereof or of the fourth aspect and possible implementations thereof. In one possible implementation, the communication device further includes a memory. In one possible implementation, the communication device further includes a communication interface, and the processor is coupled to the communication interface. In one possible implementation, the transceiver may be a transceiver circuit. In one possible implementation, the input/output interface may be an input/output circuit.
In one implementation, the communication device is a home node. When the communication device is a hosting node, the communication interface may be a transceiver, or an input/output interface.
In another implementation, the communication device is a chip or a system-on-chip. When the communication device is a chip or a chip system, the communication interface may be an input/output interface, an interface circuit, an output circuit, an input circuit, a pin, or related circuits on the chip or the chip system. The processor may also be embodied as processing circuitry or logic circuitry.
In a twenty-first aspect, a communication device is provided, comprising a processor coupled to a memory, operable to execute instructions in the memory to implement the method of the third aspect and possible implementations thereof or the method of the fifth aspect and possible implementations thereof. In one possible implementation, the communication device further includes a memory. In one possible implementation, the communication device further includes a communication interface, and the processor is coupled to the communication interface. In one possible implementation, the transceiver may be a transceiver circuit. In one possible implementation, the input/output interface may be an input/output circuit.
In one implementation, the communication device is a home node. When the communication device is a hosting node, the communication interface may be a transceiver, or an input/output interface.
In another implementation, the communication device is a chip or a system-on-chip. When the communication device is a chip or a chip system, the communication interface may be an input/output interface, an interface circuit, an output circuit, an input circuit, a pin, or related circuits on the chip or the chip system. The processor may also be embodied as processing circuitry or logic circuitry.
In a twenty-second aspect, a communication device is provided that includes an input circuit, an output circuit, and a processing circuit. The processing circuit is configured to receive signals via the input circuit and to transmit signals via the output circuit such that any of the first to sixth aspects, and the method in any of the possible implementations of the foregoing aspects, are implemented.
In a specific implementation process, the communication device may be a chip, the input circuit may be an input pin, the output circuit may be an output pin, and the processing circuit may be a transistor, a gate circuit, a flip-flop, various logic circuits, and the like. The input signal received by the input circuit may be received and input by, for example and without limitation, a receiver, the output signal may be output to and transmitted by, for example and without limitation, a transmitter, and the input circuit and the output circuit may be different circuits or the same circuit, in which case the circuits function as the input circuit and the output circuit, respectively, at different times. The embodiment of the application does not limit the specific implementation modes of the processor and various circuits.
In a twenty-third aspect, a processing device is provided that includes a processor and a memory. The processor is configured to read instructions stored in the memory and is configured to receive signals via the receiver and to transmit signals via the transmitter to perform any of the first to sixth aspects and the method of any of the possible implementations of the aspects.
In one possible implementation, the processor is one or more, and the memory is one or more.
In one possible implementation, the memory may be integrated with the processor or the memory may be separate from the processor.
In a specific implementation process, the memory may be a non-transient (non-transitory) memory, for example, a Read Only Memory (ROM), which may be integrated on the same chip as the processor, or may be separately disposed on different chips.
It should be appreciated that the related data interaction process, for example, transmitting the indication information, may be a process of outputting the indication information from the processor, and the receiving the capability information may be a process of receiving the input capability information by the processor. Specifically, the data output by the processing may be output to the transmitter, and the input data received by the processor may be from the receiver. Wherein the transmitter and receiver may be collectively referred to as a transceiver.
The processor in the above aspect may be a chip, and the processor may be implemented by hardware or software, and when implemented by hardware, the processor may be a logic circuit, an integrated circuit, or the like, and when implemented by software, the processor may be a general-purpose processor, and implemented by reading software code stored in a memory, which may be integrated in the processor, may be located outside the processor, and exist independently.
In a twenty-fourth aspect, there is provided a computer program product comprising a computer program (which may also be referred to as code, or instructions) which, when run, causes a computer to perform any of the first to sixth aspects and the method in any of the possible implementations of the aspects.
In a twenty-fifth aspect, there is provided a computer readable medium storing a computer program (which may also be referred to as code, or instructions) which, when run on a computer, causes the computer to perform any of the above-described first to sixth aspects, and the method in any of the possible implementations of the above-described aspects.
In a twenty-sixth aspect, a communication system is provided, including at least one of the aforementioned first, second, and third host nodes.
Detailed Description
The technical scheme of the application will be described below with reference to the accompanying drawings.
The technical scheme of the embodiment of the application can be applied to various communication systems, such as a code division multiple access (Code Division Multiple Access, CDMA) system, a wideband code division multiple access (Wideband Code Division Multiple Access, WCDMA) system, a long term evolution (Long Term Evolution, LTE) system, an LTE frequency division duplex (Frequency Division Duplex, FDD) system, an LTE time division duplex (Time Division Duplex, TDD), a wireless fidelity (WIRELESS FIDELITY, WIFI), a device-to-device (D2D) communication system, a vehicle-to-everything, a V2X) communication system, a universal mobile communication system (Universal Mobile Telecommunication System, UMTS), a machine-to-machine communication (machine to machine, M2M) system, a machine type communication (MACHINE TYPE communication, MTC) system, an Internet of things (internet of things, ioT) communication system, a non-terrestrial communication (non-TERRESTRIAL NETWORK, NTN) system, a fifth generation mobile communication system (the 5th Generation,5G) system or a New wireless (New Radio, NR) system, and the like or future wireless communication systems.
A network architecture suitable for use with the present application will first be briefly described.
The present application refers to a relay node supporting integrated access and backhaul as an IAB node (IAB node) to distinguish between relays of LTE (long term evolution, LTE), and a system including the IAB node is also referred to as a relay system.
It should be understood that the names of all nodes and information in the present application are only names set for convenience in description of the present application, and names in actual networks may be different, and it should not be understood that the present application is limited to the names of various nodes and information, but any names having the same or similar functions as those of the nodes or information used in the present application are regarded as a method or an equivalent replacement of the present application, and are not repeated in the scope of protection of the present application.
In order to design a flexible and convenient access and backhaul scheme, an access link (ACCESS LINK, AL) and a Backhaul Link (BL) in an IAB scenario both adopt a wireless transmission scheme.
In a network including an IAB node (hereinafter referred to as an IAB network), the IAB node may provide a radio access service for a terminal device, and a UE may be connected to the IAB node through a radio access link and may be connected to a host node (IAB node/donor node) through a radio backhaul link to transmit service data of a user.
Illustratively, the home node may be a home base station. The host node may simply be referred to as an IAB host (IAB donor) or DgNB (i.e., donor gNodeB) in a 5G network. The host node may be a complete entity or a separate form of a centralized unit (centralized unit, CU) (referred to herein simply as a Donor-CU, or CU) and a Distributed Unit (DU) (referred to herein simply as a Donor-DU), i.e. the host node consists of a Donor-CU and a Donor-DU. In the embodiment of the application and in the drawings, the host node is taken as an example to be composed of a Donor-CU and a Donor-DU, so that the method provided by the embodiment of the application is exemplified.
The IAB node is composed of a mobile terminal (mobile termination, MT) part and a Distributed Unit (DU) part. An IAB node may be considered a terminal device when it is facing its parent node. At this time, the IAB node plays the role of MT. An IAB node may be considered a communication device when it is facing its child node (which may be a terminal device or a terminal device part of another IAB node). At this time, the IAB node plays the role of a DU. Thus, the IAB node may be considered to consist of an MT part and a DU part. An IAB node may establish a backhaul connection between the MT part and at least one parent node of the IAB node. The DU portion of one IAB node may provide access services for the terminal device or MT portion of other IAB nodes.
The Donor-CU may also be a separate form of User Plane (UP) (CU-UP) and Control Plane (CP) (CU-CP) that is composed of CU-CP and CU-UP.
The IAB node is connected to the core network via a wired link via a host node. For example, in a 5G architecture of independent networking, the IAB node is connected to a core network (5G core,5 gc) of the 5G network through a wired link via a host node. Under a 5G architecture of a non-independent networking, an IAB node is connected to an evolved packet core (evolved packet core, EPC) via an eNB at a control plane and to the EPC via a hosting node and the eNB at a user plane.
In order to ensure the reliability of service transmission, the IAB network supports multi-hop IAB nodes and multi-connection IAB node networking. Therefore, there may be multiple transmission paths between the terminal device and the home node. On one path, there is a certain hierarchical relationship between the IAB nodes, and between the IAB nodes and the hosting node serving the IAB nodes, each IAB node regards the node for which backhaul service is provided as a parent node. Accordingly, each IAB node may be considered a child of its parent node.
For example, referring to fig. 1, the parent node of the IAB node 1 is a host node, the IAB node 1 is a parent node of the IAB node 2 and the IAB node 3, the IAB node 2 and the IAB node 3 are both parent nodes of the IAB node 4, and the parent node of the IAB node 5 is the IAB node 3. The uplink data packet of the terminal device may be transmitted to the host node through one or more IAB nodes, and then sent to the mobile gateway device (e.g., a UPF network element in a 5G network) by the host node, and the downlink data packet is received from the mobile gateway device by the host node, and then sent to the terminal device through one or more IAB nodes. Two available paths are respectively formed between the terminal equipment 1, the IAB node 4, the IAB node 3, the IAB node 1, the host node, the terminal equipment 1, the IAB node 4, the IAB node 2, the IAB node 1 and the host node for transmitting the data packet. Three paths are available for transmitting the data packet between the terminal device 2 and the host node, namely, the terminal device 2, the IAB node 4, the IAB node 3, the IAB node 1, the host node, the terminal device 2, the IAB node 4, the IAB node 2, the IAB node 1, the host node, the terminal device 2, the IAB node 5, the IAB node 2, the IAB node 1 and the host node.
It will be appreciated that in an IAB network, one or more IAB nodes may be included on one transmission path between a terminal device and a home node. Each IAB node needs to maintain a wireless backhaul link towards the parent node and also needs to maintain a wireless link with the child node. If an IAB node is a node to which a terminal device accesses, a radio access link is between the IAB node and a child node (i.e., the terminal device). If one IAB node is a node that provides backhaul services for other IAB nodes, a wireless backhaul link is between the IAB node and a child node (i.e., other IAB nodes). For example, referring to fig. 1, in the path "terminal device 1→iabnode 4→iabnode 3→iabnode 1→home node". The terminal device 1 accesses the IAB node 4 through a wireless access link, the IAB node 4 accesses the IAB node 3 through a wireless backhaul link, the IAB node 3 accesses the IAB node 1 through a wireless backhaul link, and the IAB node 1 accesses the host node through a wireless backhaul link.
Illustratively, the IAB node may be a customer premises device (customer premises equipment, CPE), a home gateway (RESIDENTIAL GATEWAY, RG), or the like. In this case, the method provided by the embodiment of the application can also be applied to a home connection (home access) scene.
The above-mentioned IAB networking scenario is merely exemplary, and in an IAB scenario where multiple hops and multiple connections are combined, there are many other possibilities for the IAB networking scenario, for example, where a home node and an IAB node under another home node form a dual connection to serve a terminal device, etc., which are not listed here.
Fig. 2 shows a schematic diagram of a system architecture suitable for use with embodiments of the present application. As shown in fig. 2, the IAB (or referred to as an IAB device) is a wireless backhaul base station, which is specific in that the IAB first establishes a backhaul channel with a target macro station, and then provides wireless coverage service to the outside, similar to the customer premise equipment (customer premise equipment, CPE), except that the CPE provides wireless fidelity (WIRELESS FIDELITY, WIFI) coverage to the outside. The IAB provides base station radio signals, such as fifth generation (the fifth generation, 5G) signals, externally. The IAB is mainly used as coverage extension of the macro station, and by means of the characteristics of high-power multi-antenna reception of its backhaul device, the remote coverage of the macro station is extended, changing the weak coverage area that is originally a far point for the macro station into a good coverage area of a near-middle point. The IAB generally requires accurate access to the target macro station to establish a backhaul path due to the connection relationship with the fixed macro station.
In the IAB network architecture illustrated in fig. 2, taking independent networking (standalone, SA) networking as an example, the IAB donor may be formed of a centralized unit (centralized unit, CU) and a Distributed Unit (DU), that is, splitting functions of the IAB donor, deploying part of the functions on one CU, deploying the rest of the functions on the DU, and sharing one CU by multiple DUs, the cost may be saved, and the network expansion may be easy. The CU and the DU are connected through an F1 interface. CU stands for IAB donor connected to the core network via the Next Generation (NG) interface, and CU stands for IAB donor connected to other gNB via the Xn interface.
The IAB node DU (which may be abbreviated as IAB-DU in the present application) is logically connected to an IAB donor CU (which may be abbreviated as CU in the present application) through an F1 interface, and in fact, the connection of the IAB-DU to the CU is implemented through an NR Uu interface between the IAB-MT and the parent node DU of each hop, but since the final IAB-DU can communicate with the CU, it can be considered that the F1 interface logically exists. The IAB-MT function is defined as a component like a UE. In an IAB network, an MT is referred to as a function residing on an IAB node. Since the MT functions like a normal UE, the IAB node can be considered to be accessed to a higher node or network through the MT.
The user plane and control plane protocol stacks in an IAB network are shown in fig. 3. The F1 interface supports a user plane protocol (F1-user plane, F1-U) and a control plane protocol (F1-C), wherein the user plane protocol comprises one or more of the following protocol layers, namely a GPRS (general packet radio service) protocol user plane (GENERAL PACKET Radio Service tunneling protocol user plane, GTP-U), UDP (user datagram protocol ), IP (internet protocol, internet protocol) and the like, as shown in (b) of fig. 3, and the control plane protocol comprises one or more of the following protocol layers, namely F1AP (F1 application protocol ), SCTP (stream control transport protocol, stream control transmission protocol), IP and the like. Interface management, IAB-DU management, UE context related configuration and the like can be performed between the IAB node and the IAB node through the F1-C, and functions such as user plane data transmission, downlink transmission state feedback and the like can be performed between the IAB node and the IAB node through the F1-U.
It should be noted that the foregoing descriptions of fig. 1 and fig. 2 are only examples, and the technical solution of the present application may be applied to each communication system including an access network element. The access network element may be, for example, an IAB in fig. 1 or a gNB as shown in fig. 2. In addition, the communication system may further include a terminal device.
The terminal equipment related to the embodiment of the application can also be called a terminal, can be equipment with a wireless receiving and transmitting function, can be deployed on land, including indoor or outdoor, handheld or vehicle-mounted, can be deployed on water surface (such as a ship and the like), and can be deployed in air (such as an airplane, a balloon, a satellite and the like). The terminal device may be a User Equipment (UE). The UE includes a handheld device, an in-vehicle device, a wearable device, or a computing device with wireless communication functionality. Illustratively, the UE may be a mobile phone (mobile phone), a tablet computer, a computer with a wireless transceiver function, or the like. Furthermore, the terminal device may also be a device capable of supporting the terminal to implement the function, such as a chip or a chip system, which may be installed in the terminal. In the technical solution provided in the embodiment of the present application, the device for implementing the function of the terminal is the terminal, which is used as an example to describe the technical solution provided in the embodiment of the present application. It should be understood that the terminal is a generic term including most common handsets, CPE, backhaul (IAB) terminals, and the terminal device may also be a Virtual Reality (VR) terminal device, an augmented reality (augmented reality, AR) terminal device, a wireless terminal in industrial control, a wireless terminal in unmanned driving, a wireless terminal in telemedicine, a wireless terminal in smart grid, a wireless terminal in smart city (SMART CITY), a wireless terminal in smart home (smart home), etc.
The network device according to the embodiment of the present application includes a Base Station (BS), which may be a device deployed in a radio access network and capable of performing wireless communication with a terminal. The base stations may take many forms, such as macro base stations, micro base stations, relay stations and access points, backhaul stations, and so forth. Illustratively, the base station involved in the embodiment of the present application may be a base station in 5G or a base station in LTE. Among them, the base stations in 5G may also be referred to as transmission reception points (transmission reception point, TRP) or next generation base stations (next generation nodded, gNB). In the embodiment of the application, the device for realizing the function of the network equipment can be the network equipment, or can be a device which can support the network equipment to realize the function, such as a chip or a chip system, and can be installed in the network equipment. In the technical solution provided in the embodiment of the present application, the device for implementing the function of the network device is a network device, and the network device is a base station as an example, which describes the technical solution provided in the embodiment of the present application.
In the embodiment of the application, the chip system can be composed of chips, and can also comprise chips and other discrete devices.
It should be understood that the network architecture shown above is merely illustrative, and the network architecture to which the embodiments of the present application are applied is not limited, and any network architecture capable of implementing the functions of the respective network elements described above is applicable to the embodiments of the present application.
It should also be understood that the above designations are merely intended to facilitate distinguishing between different functions and should not be construed as limiting the application in any way. The application does not exclude the possibility of using other designations in 6G networks as well as other networks in the future.
It should also be understood that the names of interfaces between the network elements in fig. 2 are only an example, and the names of interfaces in the specific implementation may be other names, which are not limited in particular by the present application. In addition, the names of the transmitted information (or signaling) between the above-mentioned network elements are also merely an example, and the functions of the information itself are not limited in any way.
The following describes the process of IAB node-in-network (IAB integration). Fig. 4 is a flowchart of an IAB node network access, taking an IAB node2 network access procedure as an example, where IAB node 1 is its parent node and is already in the network.
The network access procedure of the IAB node can be summarized as follows:
Stage (Phase) 1. The IAB-MT accesses the cell in a similar way to the normal UE, establishes an RRC connection with the host node, and indicates itself as an IAB node when the RRC connection is established (carrying an IAB node indication (IAB node indication) in RRC connection establishment complete (RRC Setup Complete) information), the CU also carries an IAB-node indication when sending UE initial information (INITIAL UE MESSAGE) to the core network (specifically, an AMF network element in the core network), the AMF authenticates the IAB-MT, and carries an IAB grant element (IAB grant element) in information indicating that the CU has established a UE initial context for the IAB-MT (INITIAL CONTEXT SETUP REQUEST), and if the authentication is passed, the value of the IAB grant element is authorized, otherwise the value of the IAB grant element is not authorized. Since the network access procedure of the IAB node is described herein, it is assumed that the value of the IAB grant cell is authorized, and the subsequent steps are performed.
Phase2 CU configures the backhaul link RLC channel (BH RLC CHANNEL) for the IAB node through RRC messages and performs routing configuration. Specifically, only one default (default) backhaul link RLC channel and default route are configured at this time, and are used in the subsequent initial establishment of the F1 interface (see Phase3 for details), until the F1 interface is established, more backhaul link RLC channels and route paths can be configured to the IAB node through the F1-C information, and are used in the subsequent more F1-C information and F1-U user plane data. In Phase2, in addition to configuration of IAB node2, a node between IAB node and donor (IAB node 1) is also updated to inform the node how to select the next hop link and the next hop RLC channel when a packet from IAB node2 or a packet addressed to IAB node2 is received.
Phase 3. IAB-DU2 initiates F1 connection establishment REQUEST (F1 SETUP REQUEST information, carrying cell configuration information under DU 2) to the donor-CU by using default configuration obtained in Phase2, and REQUESTs to establish F1 interface, the donor-CU replies F1 connection establishment corresponding (F1 SETUP RESPONSE) information to IAB-DU2, activates the cell, and completes F1 interface establishment.
For the case that the value of the IAB grant is authorized, the donor-CU will follow the above description of the IAB access to the network (including configuring the backhaul link RLC channel, etc.), and for the case that the value of the IAB grant is not authorized, which means that this IAB node is not allowed to provide the IAB service, the donor-CU may perform operations such as not configuring the default configuration for the IAB-MT, or configuring the default configuration for the IAB-MT but rejecting the IAB-DU initiated F1 connection establishment request, etc.
In addition to the amb sending the IAB grant information to the CU at the initial access of the IAB node, at a later time, if the grant status of the IAB is changed (e.g., because the IAB has moved to a specific location or the service time of the IAB has been specified), the AMF sends the updated IAB grant information element value to the CU via UE CONTEXT MODIFICATION REQUESET.
The wide mobility of the IAB node has some impact on the core network side, and the mobile IAB node needs a separate authorization cell to move (mobile) IAB authorization cells, which are used in exactly the same way as the IAB authorization cells.
Here, it is collectively described that the IAB node in the present application may be a normal IAB node or a mobile IAB node.
The basic concept of the IAB and the network access procedure are described above, and some topology change related characteristics of the IAB are described below. In particular, these properties are all across CUs (inter-donor CUs), for the case of non-across CUs (intra-donor CUs) and across donor DUs (inter-donor DUs), although the donor DUs are crossed, but without crossing CUs, reconfiguration by the CUs is sufficient, and the following scenarios need to involve interactions between CUs.
1. Local migration (partial migration):
The local migration of the IAB node is shown in fig. 5. The IAB node where migration occurs is called a boundary node (boundary node), such as IAB node2 (including IAB-MT2 and IAB-DU 2). The node downstream of the boundary node is referred to as a child node (DESCENDANT NODE), such as IAB node4 (including IAB-MT4 and IAB-DU 4). Before migration, there is an RRC connection between IAB-MT2 and CU1, an F1 interface between IAB-DU2 and CU1, and IAB node2 and IAB node communicate via the source path (via IAB node1 composed of IAB-MT1 and IAB-DU 1). Upon local migration, the IAB-MT2 has cell handover across the CU and has established an RRC connection with the CU 2.
To avoid introducing the re-establishment procedure of the F1 interface, the IAB-DU2 still maintains the F1 interface with CU1 and does not establish the F1 interface with CU2 at the time of local migration, and thus the communication path between CU1 and IAB-DU2 becomes cross-topology: In FIG. 5, CU1 and CU2 are referred to as an F1 anchor CU (F1-TERMINATING CU) and a non-F1 anchor CU (non-F1-TERMINATING CU), respectively, and may also be referred to as a source CU and a target CU (target CU). It should be noted that the data traffic is not transmitted via CU2 during this communication path or topology, and CU1 and the Donor-DU2 are in direct communication via the IP network.
The F1 anchor CU sends a transmission migration management request (IAB TRANSPORT MIGRATION MANAGEMENTIAB REQUEST) message to the non-F1 anchor CU, requests to establish cross-topology traffic transmission, replies a transmission migration management RESPONSE (IAB TRANSPORT MIGRATION MANAGEMENTIAB RESPONSE) message to the F1 anchor CU if the non-F1 anchor CU agrees to establish the cross-topology traffic transmission, replies a transmission migration management rejection (IAB TRANSPORT MIGRATION MANAGEMENTIAB REJECT) message if the non-F1 anchor CU disagrees with the transmission migration management rejection (IAB TRANSPORT MIGRATION MANAGEMENTIAB REJECT), and can also interactively transmit a migration modification request/RESPONSE (IAB TRANSPORT MIGRATION MODIFICATIONIAB REQUEST/RESPONSE) message if the subsequent F1 anchor CU or the non-F1 anchor CU wants to perform operations such as quality of service (quality of service, qoS) modification or withdrawal of traffic.
2. Topology redundancy topology redundancy (alternatively referred to as dual connectivity, dual connectivity):
In NR, the UE may make dual connectivity, connecting to two different base stations, to improve throughput and robustness. Double connection scenario of IAB node as shown in fig. 6, IAB-MT may also perform double connection, and connect to two different CUs, and data between IAB-DU and CU1 (specifically, F1 anchor CU) may be transmitted simultaneously through two paths, double throughput. RRC connection exists between IAB-MT and CU1 and CU2, and F1 interface exists between IAB-DU2 and CU 1. Like the local migration, data traffic also communicates with the IP network of the donor-DU2 through CU1, without going through CU2. And as with partial migration, CU1 needs to send IAB TRANSPORT MIGRATION MANAGEMENT REQUEST message to CU2 to transmit a portion of the traffic request in the topology of CU2.
In the dual-connection scenario, it is necessary to distribute traffic, and determine how much traffic is carried on each of the two paths. Similar to partial migration, the F1 anchor CU sends IAB TRANSPORT MIGRATION MANAGEMENT REQUEST message to the non-F1 anchor CU requesting to establish cross-topology traffic transmission, except that in the dual connectivity scenario, the F1 anchor CU may only carry part of the traffic information in the IAB TRANSPORT MIGRATION MANAGEMENT REQUEST message requesting that the topology under the non-F1 anchor CU assume this part of the traffic, and its own topology assumes the rest. Whereas in partial migration, with a single connection, CU1 would request that all traffic be migrated into the topology under CU 2. The decision of how much traffic to offload to the CU2 topology by CU1 is determined by the implementation of CU1, e.g. CU1 decides how much traffic to afford itself based on the link quality and resource allocation under the CU1 topology, offloading the remaining requests to the CU2 topology. After the primary traffic allocation, in the dual connectivity scenario, traffic withdrawal is also supported (revocation), when CU1 finds an improvement in link quality under its own topology, a IAB TRANSPORT MIGRATION MODIFICATION REQUEST message may be sent to CU2, or when CU2 finds a deterioration in link quality under its own topology, a IAB TRANSPORT MIGRATION MODIFICATION REQUEST message may be sent to CU1 requesting that a portion of the traffic be withdrawn under CU1 topology. Alternatively, traffic withdrawal may also be considered as migration of traffic between CU1 and CU2 topologies. In this way, the F1 anchor point CU can flexibly allocate the flow born by each of the two topologies based on the link quality and the resource allocation condition of the two topologies in the double-connection scene.
3. Continuous local migration (consecutive partial migration):
As shown in fig. 7, when the MT switches from CU2 to CU3, the F1 interface of the DU is always associated with CU 1. Here mIAB is a short for mobile IAB, for example, the mobile IAB scenario may be a scenario in which an IAB node is deployed on a vehicle such as a subway, bus, or private car to serve UEs in a car. mIAB node in fig. 7 is a direct connection to a donor-DU, but other IAB nodes may be present between mIAB node and the donor-DU, and the application is not limited thereto. Further, the MT may be switched from CU1 to CU2 (e.g., fig. 5), or may be switched from another CU to CU 2.
It should be noted that the above terms or techniques are all of the prior art and are not limiting.
It is to be understood that the term "and/or" is merely an association relationship describing the associated object, and means that three relationships may exist, for example, a and/or B, and that three cases, a alone, a and B together, and B alone, may be represented. In addition, the character "/" herein generally indicates that the front and rear associated objects are an "or" relationship.
The terms related to the present application are briefly described above, and will not be repeated in the following examples. The communication method provided by the embodiment of the application will be described in detail below with reference to the accompanying drawings. The embodiments provided in the present application may be applied to the network architecture shown in fig. 5 to 7, and are not limited thereto.
At this stage, in the case where the dual connection scenario and the continuous local migration scenario of the IAB node exist at the same time, the IAB node and the F1 anchor CU only maintain the F1 connection, but do not perform RRC connection, but perform RRC connection with two non-F1 anchor CUs. Taking the case that the dual connection scenario and the continuous local migration scenario shown in fig. 8 exist simultaneously as an example, the mIAB node includes a mIAB-MT part and a mIAB-DU part, CU1 is an F1 anchor CU, and is a mIAB-DU host CU or is connected with mIAB-DU existence F1, and CU2 and CU3 respectively have RRC connection with the IAB-MT. In the figure, the mIAB node is denoted mIAB-node (mobile IAB-node), because only in the mobile IAB scenario, the case where the F1 anchor CU, the dual-connected non-F1 anchor CU, is three nodes may occur.
As can be seen from the above, in the dual connectivity scenario, traffic distribution is required. Thus, in the scenario shown in FIG. 8, the traffic of the F1 anchor CU, or CU1, needs to be distributed under the topology between CU2 and CU3 and mIAB nodes. In the dual-connection scenario shown in fig. 6, the mIAB node is dual-connected to an F1 anchor CU and another non-F1 anchor CU, which are in relationship with the primary station and the secondary station, so that the F1 anchor CU can determine traffic information allocated under topology between the non-F1 anchor CU and the mIAB node. However, in the dual-connection scenario shown in fig. 8, the mIAB node is dual-connected to two non-F1 anchor points CU, namely CU2 and CU3, which are the relationship between the master station and the slave station, whereas CU1 is not the relationship between the master station and the slave station, and CU2 and CU 3. At this time, the F1 anchor CU cannot learn the link quality of the communication paths or topologies between the two non-F1 anchor CUs and the IAB node, and thus cannot correctly determine how much flow of the F1 anchor CU should be carried by each of the two communication paths, which may further cause congestion and affect the service experience.
The application provides a communication method, which is characterized in that under the condition that a double-connection scene and a continuous local migration scene of an IAB node coexist, a message for making decision flow distribution is sent to an F1 anchor point CU through two non-F1 anchor point CUs, so that the F1 anchor point CU can make reasonable flow distribution decisions for two communication paths between the two non-F1 anchor point CUs and the IAB node.
For convenience of description, the hosting node to which CU1 belongs will be referred to as a first hosting node, the hosting node to which CU2 belongs will be referred to as a second hosting node, and the hosting node to which CU3 belongs will be referred to as a third hosting node. The second host node is a master station and the third host node is a slave station, or the second host node is a slave station and the third host node is a master station.
Fig. 9 is a schematic diagram of a communication method 900 according to an embodiment of the present application. The method 900 may include step S910 and step S920.
S910, the first host node receives first traffic migration configuration information.
Specifically, the first traffic migration configuration information is used for determining traffic distribution when traffic of the first host node migrates to the second topology and the third topology. As shown in the mobile IAB and dual connectivity scenario of fig. 8, the second topology is the traffic transmission path between CU2 and the mobile IAB node, the third topology is the traffic transmission path between CU3 and the mobile IAB node, and traffic is allocated by CU 1. The mobile IAB node includes a first distributed unit and a first mobile terminal, where an F1 connection exists between the first distributed unit and the first home node, and RRC connections exist between the first mobile terminal and the second home node and between the first mobile terminal and the third home node.
The first traffic migration configuration information may be used to determine traffic allocation results of the second topology and the third topology, that is, the portion of traffic that needs to be borne by each of the second topology and the third topology.
The first traffic migration configuration information may include traffic information and traffic transmission path information that each needs to assume in the second topology and the third topology, for example. For example, the traffic information may include a source destination IP address, a source destination port, etc. of traffic that each topology needs to assume, and the traffic transmission path information may include an IP address and/or backhaul link information that the traffic transmits in each topology.
The first traffic migration configuration information may include link quality and/or resource allocation information in the second topology and the third topology, for example. For example, the link quality may include signal quality, transmission rate, delay, etc., and the resource allocation information may include bandwidth allocation, time-frequency domain allocation, etc. In this way, the first host node may reasonably determine the traffic that needs to be allocated to the second topology and the third topology according to the link quality and/or the resource allocation information in the second topology and the third topology.
It should be noted that, in the scenario shown in fig. 8, direct communication among the first host node, the second host node, and the third host node may be implemented through an Xn interface, in other words, in step S910, the first host node receives an Xn message through the Xn interface, where the Xn message carries the first traffic migration configuration information.
S920, the first host node distributes the traffic of the first host node to the second topology and the third topology according to the first traffic migration configuration information.
It should be appreciated that, after receiving the first traffic migration configuration information, the first host node or CU1 shown in fig. 8 determines traffic allocations of the second topology and the third topology, and further reasonably allocates the traffic of the first host node to the second topology and the third topology.
Specifically, in S910, the first host node may receive the first traffic migration configuration information in the following ways.
Mode one:
Fig. 10 shows a schematic diagram of a method 1000 of mode one. As shown in fig. 10, the method 1000 further includes S915 and S916 (opt 1), or S917 and S918 (opt 2).
In an aspect, the first traffic migration configuration information may include second traffic migration configuration information indicating migration to the second topology and third traffic migration configuration information indicating migration to the third topology. For example, the second traffic migration configuration information may include traffic information and traffic transmission path information that are to be assumed in the second topology, and the third traffic migration configuration information may include traffic information and traffic transmission paths that are to be assumed in the third topology. Traffic information may include source destination IP addresses, source destination ports, etc. of traffic that each topology needs to assume, and traffic transmission path information may include IP addresses and/or backhaul link information that traffic is transmitted in each topology.
In opt1, the first host node receives traffic migration configuration information for the respective topology from the second host node and the third host node, respectively.
At S915, the first host node receives second traffic migration configuration information from the second host node.
Accordingly, the second host node sends second traffic migration configuration information to the first host node. The second traffic migration configuration information may be IAB TRANSPORT MIGRATION MANAGEMENT RESPONSE messages sent by the second host node through the Xn interface, and may carry second traffic migration configuration information migrated to the second topology.
It should be appreciated that the first host node receives the second traffic migration configuration information to determine traffic that needs to be migrated to the second topology.
S916, the first host node receives third traffic migration configuration information from the third host node.
Accordingly, the third host node sends third traffic migration configuration information to the first host node. The third traffic migration configuration information may be IAB TRANSPORT MIGRATION MANAGEMENT RESPONSE messages sent by the third host node through the Xn interface, and may carry third traffic migration configuration information migrated to the third topology.
It should be appreciated that the first host node receives third traffic migration configuration information to determine traffic that needs to migrate to the third topology.
In opt2, the first host node receives traffic migration configuration information for both topologies from the second host node, i.e., receives the first traffic migration configuration information. At this time, the second host node serves as a transit node that transmits the message to the first host node as a third host node.
S917, the second host node receives third traffic migration configuration information from the third host node.
Accordingly, the third host node sends third traffic migration configuration information to the second host node. The third traffic migration configuration information may be IAB TRANSPORT MIGRATION MANAGEMENT RESPONSE messages sent by the third host node through the Xn interface, and may carry third traffic migration configuration information migrated to the third topology.
S918, the first host node receives first traffic migration configuration information from the second host node.
Accordingly, the second host node sends the first traffic migration configuration information, or alternatively, sends the second traffic migration configuration information and the third traffic migration configuration information to the first host node. The first traffic migration configuration information may be IAB TRANSPORT MIGRATION MANAGEMENT RESPONSE messages sent by the second host node through the Xn interface, and may carry second traffic migration configuration information migrated to the second topology and third traffic migration configuration information migrated to the third topology.
Alternatively, the second host node may send the second traffic migration configuration information and the third traffic migration configuration information to the first host node in the same message, or send the second traffic migration configuration information and the third traffic migration configuration information in different messages.
Mode two:
Fig. 11 shows a schematic diagram of mode two. As shown in fig. 11, the method 1100 further includes S901 and S903 before the method 1000, on the basis of the method 1000.
S901, the first host node sends first traffic migration request information to the second host node.
Accordingly, the second host node receives the first traffic migration request information from the first host node to determine the second traffic migration configuration information.
Specifically, the first traffic migration request information is used to request migration of all traffic of the first home node into the second topology and the third topology. For example, the first traffic migration request information may be IAB TRANSPORT MIGRATION MANAGEMENT REQUEST sent by CU1 through the Xn interface, requesting that all traffic in CU1 be migrated into the second topology and the third topology.
Optionally, S901 further includes the first host node sending the identification information of the first host node or CU1 and/or the identification information of the second host node or CU2 to the second host node. The identification information is used to determine to send a message to the first host node and/or the second host node. For example, the first host node sends the identification information of the first host node to the second host node, and the second host node can implement step S915 or S918 according to the identification information of the first host node.
It should be appreciated that the second hosting node is any one of the non-F1 anchor CUs, or that the F1 anchor CU may send the first traffic migration request information to any one of the two non-F1 anchor CUs in the dual connectivity scenario.
S903, the second host node sends third flow migration request information to a third host node.
Accordingly, the third host node receives third traffic migration request information from the second host node to determine third traffic migration configuration information.
Specifically, third traffic migration request information is used to request migration of all traffic of the first home node into the third topology. For example, the third traffic migration request information may be IAB TRANSPORT MIGRATION MANAGEMENT REQUEST sent by CU2 through the Xn interface, requesting that a portion of the traffic in CU1 be migrated into the third topology. The information may carry a traffic to be added list (traffic to be ADDED LIST) cell, where the traffic to be ADDED LIST cell includes traffic information, data flows, etc. to be added to the third topology.
It will be appreciated that there is a relationship of primary and secondary sites between the second host node and the third host node, which can be determined by the association of the primary and secondary sites.
Optionally, S903 may further include the second hosting node sending the identification information of the first hosting node or CU1 and/or the identification information of the second hosting node or CU2 to the third hosting node. Step S917 may be implemented by the third host node when the identification information of the second host node or CU2 is received, and step S916 may be implemented by the third host node when the identification information of the first host node or CU1 is received. For example, fig. 12 shows a schematic diagram of a method 1200, wherein the method 1200 includes S904.
Between step S903 and step S916, further including S904, the second host node transmits the first identification information to the third host node. Specifically, the first identification information includes identification information of the first host node or CU1, and optionally identification information of the first mobile terminal under the first host node. Further, after receiving the first identification information, the third host node can implement step S916, i.e., the third host node can send the third traffic migration configuration information to the first host node, otherwise the third host node needs to forward the third traffic migration configuration information to the first host node through the second host node.
Optionally, the identification information may include an identification of CU1 or CU2, such as a next generation base station (next generation node B, gNB) ID and/or an internet protocol (internet protocol, IP) address of CU1 or CU2, and optionally an ID of a terminal device Xn application protocol (XnAP) of the MT of the IAB node under CU1 or CU 2.
Mode three:
Fig. 13 shows a schematic diagram of a third mode. As shown in fig. 13, the method 1300 further includes a migration request and a migration corresponding step after the method 1000, based on the method 1000. Unlike method 1200, the migration request in method 1200 precedes method 900, and the migration request and migration response in method 1300 follow step 900.
First, in the step of the migration request, opt1 (S901 and S903) and opt2 (S902 and S904) may be included. S901 and S903 in opt1 are the same as S901 and S903 in method 1100, and are not described here.
In opt2, the first host node sends a second traffic migration request message to the second host node in S902, and the first host node sends a third traffic migration request message to the third host node in S904.
The second traffic migration request information is used for requesting to migrate the traffic of the first host node into the second topology, and the third traffic migration request information is used for requesting to migrate the traffic of the first host node into the third topology. For example, the second traffic migration request information may be IAB TRANSPORT MIGRATION MANAGEMENT REQUEST sent by CU1 through the Xn interface, requesting that a portion of the traffic in CU1 be migrated into the second topology. The information may carry traffic to be ADDED LIST cells, including traffic information, data flows, etc. to be added to the second topology.
Next, in the step of migrating the response, opt3 (S905 and S907) and opt4 (S906 and S908) may be included.
In opt3, the third host node sends the third traffic migration response information to the second host node, S905, and the second host node sends the first traffic migration response information to the first host node, S907. The third host node needs to forward the third traffic migration response information to the first host node through the second host node.
The first traffic migration response information is used for indicating the first host node to migrate traffic of the first host node into the second topology and the third topology. The first traffic migration response information includes second traffic migration response information for instructing the first host node to migrate traffic of the first host node into the second topology and third traffic migration response information for instructing the first host node to migrate traffic of the first host node into the third topology.
In opt4, the third host node sends the third traffic migration response information to the first host node, S906, and the second host node sends the second traffic migration response information to the first host node, S908.
It should be appreciated that after receiving the first traffic migration response information (i.e., the second traffic migration response information and the third traffic migration response information), the first host node distributes all traffic in the first host node to the second topology and the third topology according to the received traffic migration configuration information of the two topologies.
According to the scheme of the application, the first host node is connected with the first IAB node by F1, and the traffic in the first host node is distributed to the second topology and the third topology by receiving the first traffic migration configuration information, so that unreasonable traffic distribution of the F1 anchor point CU (i.e. the first host node) when the link quality of the return links of the two non-F1 anchor point CUs (i.e. the second host node and the third host node) is not known is avoided. The method and the device realize the flow distribution in the IAB node continuous local migration scene and the double connection scene which are not supported in the prior art.
In the dual connectivity scenario described above, there is also a traffic retraction (revocation) scenario. For example, CU1 may be requested to withdraw a portion of traffic when CU2 finds that the link quality under its own topology is poor, or withdraw and migrate a portion of traffic from the topology of CU2 to the topology of CU1, and CU1 may be requested to assume more traffic when CU2 finds that the link quality under its own topology is improved.
In order to realize traffic withdrawal in the double-connection scene and the continuous local migration scene of the mobile IAB node, the application provides a communication method. Fig. 14 is a schematic diagram of a communication method 1400 provided in an embodiment of the application. The method 1400 may include steps S1410, S1430, and S1450.
It should be appreciated that traffic withdrawal in the context of a continuous local migration scenario of a dual connectivity scenario and a mobile IAB node may also be considered as a migration of traffic between the above-described second topology and third topology.
Notably, the method 900 occurs with the motivation that new F1 traffic arrives in the first host node and is therefore initiated by the first host node, while with traffic withdrawal or traffic migration between the second topology and the third topology, the motivation that occurs is that the link quality of the second topology or the third topology has changed and is therefore initiated by the second host node or the third host node, and not by the first host node. Thus, the traffic migration of method 900 is initiated by the first host node, while the traffic retraction request of method 1400 is initiated by either the second host node or the third host node, or the non-F1 anchor CU (hereinafter, the second host node initiates the traffic retraction request as an example).
In embodiments of the present application, either one of the non-F1 anchor CUs may initiate a traffic withdrawal request of its own topology or of the topology of the other non-F1 anchor CU. For example, when a link quality of the second topology drops causing a portion of traffic of the second topology to need to be withdrawn and migrated to the third topology, either the second hosting node or the third hosting node may initiate a traffic withdrawal request.
S1410, the second host node sends fourth traffic migration request information.
Specifically, the fourth traffic migration request information is used for requesting traffic migration between the second topology and the third topology to distribute the traffic of the first host node to the second topology and the third topology, so as to realize traffic withdrawal of the second topology or the third topology.
The fourth traffic migration request information may be IAB TRANSPORT MIGRATION MODIFICATION REQUEST messages sent by the second home node through the Xn interface, which carries traffic information requesting to withdraw, for example, may be traffic information (traffic to be released information) cells to be released, including information such as source and destination IP addresses of traffic that needs to be released or withdrawn.
At S1430, the second host node receives the fourth traffic migration configuration information.
Specifically, the fourth traffic migration configuration information is used for determining traffic information that needs to be migrated between the second topology and the third topology.
The fourth traffic migration configuration information may be traffic information that needs to be withdrawn or migrated and determined by the third host node, for example, may be TRAFFIC RELEASED information cells, including traffic information that determines that the third host node confirms withdrawal or migration.
Specifically, S1410 and S1430 may be implemented in the following manner. Fig. 15 shows a schematic diagram of a method 1500. S1410 and S1430 in method 1500 include two cases, opt1 (S1411 and S1431) and opt2 (S1415, S1419, S1435 and S1439), respectively.
In opt1, the second home node sends fourth traffic migration request information to the third home node, S1411.
Correspondingly, the third host node receives fourth traffic migration request information from the second host node.
S1431, the second host node receives fourth traffic migration configuration information from the third host node.
Correspondingly, the third host node sends fourth traffic migration configuration information to the second host node.
In opt2, the second and third hosting nodes are mutually traffic withdrawn through the first hosting node, since all traffic in the topology is distributed for the first hosting node, and forwarding by the first hosting node is reasonable. The method comprises the following steps:
s1415, the second home node sends fourth traffic migration request information to the first home node.
Correspondingly, the first host node receives fourth traffic migration request information from the second host node.
S1419, the first home node sends fourth traffic migration request information to the third home node.
Correspondingly, the third host node receives fourth traffic migration request information from the first host node.
S1435, the third host node sends fourth traffic migration configuration information to the first host node.
Correspondingly, the first host node receives fourth traffic migration configuration information from the third host node.
The second host node receives the fourth traffic migration configuration information from the first host node, S1439.
Correspondingly, the first host node sends fourth traffic migration configuration information to the second host node.
Optionally, in step S1410, the second host node may further comprise sending the first identification information to a third host node. Specifically, the first identification information is used to determine to send a message to the first host node. For example, the first identification information may include an identification of the first home node, such as a gNB ID and/or an IP address, and optionally an ID of a terminal device Xn application protocol (XnAP) of the MT of the IAB node under the first home node. In this way, correspondingly, the third host node receives the first identification information from the second host node and is able to send a message to the first host node according to the first identification information, i.e. step S1435 is implemented.
S1450, the second host node transmits fourth traffic migration indication information.
Specifically, the fourth traffic migration indication information is used for indicating that traffic to be migrated between the second topology and the third topology is migrated, that is, for indicating that traffic withdrawal or traffic migration between the second topology and the third topology is completed.
Specifically, the second host node may implement step S1450 in several ways.
Mode one:
The first host node receives the traffic migration indication information, or the non-F1 anchor CU unifies or respectively informs the F1 anchor CU of the traffic migration indication information, and the F1 anchor CU readjusts traffic distribution of the second topology and the third topology according to the traffic migration indication information. Fig. 16 shows a schematic diagram of a method 1600. Step S1450 in method 1600 includes opt1 (S1451 and S1452) and opt2 (S1454 and S1455), among others.
In opt1, the second and third host nodes send mapping configuration information within the respective topologies to the first host node, respectively.
S1451, the first host node receives the first mapping configuration information from the second host node.
Correspondingly, the second host node sends the first mapping configuration information to the first host node. For example, the second host node sends the first mapping configuration information to the first host node over the Xn interface.
S1452, the first host node receives the second mapping configuration information from the third host node.
Correspondingly, the third host node sends the second mapping configuration information to the first host node. For example, the third hosting node sends the first mapping configuration information to the first hosting node over the Xn interface. In some embodiments of the present application, the third host node may implement sending the second mapping configuration information to the first host node according to the received first identification information.
Specifically, the first mapping configuration information and the second mapping configuration information are used to instruct the first host node to redetermine traffic transmitted in the second topology and the third topology, respectively. For example, the first mapping information may include updated Backhaul (BH) resource mapping information of the second topology, such as UL mapping, and/or quality of service (quality of service, qoS) mapping information, such as QoS mapping, and the second mapping information may include updated BH resource mapping information of the third topology and/or QoS mapping information.
It should be appreciated that UL mapping is configured by the F1 anchor CU or first host node to the IAB node for the IAB node to map upstream traffic onto BH resources. Because BH resources corresponding to part of traffic to be migrated in the second topology or the third topology are changed (topology switching occurs), the F1 anchor CU needs to send updated UL mapping to the IAB node, and BH resource information in UL mapping needs to be sent to the F1 anchor CU from the non-F1 anchor CU.
QoS mapping is a mapping relationship of an F1 anchor CU to an IP header of downstream traffic, including an IP address and QoS parameters, where the QoS parameters include a Differentiated Services Code Point (DSCP) or a flow label (flowlabel, FL) field. When the topology of the traffic changes, the QoS parameters of the traffic need to be converted into the associated QoS parameters under the new topology, so that the non-F1 anchor CU needs to send the new QoS mapping rule to the F1 anchor CU for the F1 anchor CU to drive into the IP header when sending the downstream traffic.
In opt2, the second host node sends mapping configuration information within the second topology and the third topology to the first host node.
S1454, the second host node receives the second mapping configuration information from the third host node.
Correspondingly, the third host node sends the first mapping configuration information to the second host node. For example, the third home node sends the first mapping configuration information to the second home node over the Xn interface.
S1455, the first host node receives the first mapping configuration information and the second mapping configuration information from the second host node.
Correspondingly, the second host node sends the first mapping configuration information and the second mapping configuration information to the first host node. For example, the second host node sends the first mapping configuration information and the second mapping configuration information to the first host node over the Xn interface.
The principles of S1454 and S1455 are basically the same as the above principle that the second host node forwards the message of the third host node, which is not described here.
Alternatively, step S1450 in the first embodiment may be performed simultaneously with opt2 of step S1410. For example, in opt2 of step S1410, the second host node may simultaneously transmit the first mapping configuration information to the first host node when transmitting the fourth traffic migration request information to the first host node, and the third host node may simultaneously transmit the second mapping configuration information to the first host node when transmitting the fourth traffic migration configuration information to the first host node. For another example, in opt2 of step S1410, fourth traffic migration request information may carry the first mapping configuration information, and fourth traffic migration configuration information may carry the second mapping configuration information.
Mode two:
In the second mode, after the second and third home nodes have undergone negotiation of steps S1410 and S1430, by configuring respective donor-DUs, and a traffic transmission tunnel of the inter-donor-DU is established between the donor-DU2 and the donor-DU3 and is used for directly transmitting downlink traffic. In other words, part of traffic to be migrated in the second topology and the third topology is directly migrated through the tunnel, without the first host node having to redistribute the traffic in the second topology and the third topology.
Alternatively, the traffic tunnel may be established through internet security protocol (internet protocol security, IPSec) or layer-two tunneling protocol (layer 2tunneling protocol,L2TP) or the like, and the required functions are configured on each donor-DU to ensure participation in tunnel establishment, including IP address allocation, routing configuration, firewall settings, and the like.
Fig. 17 shows a schematic diagram of a method 1700. The method 1700 takes the withdrawal of traffic in the third topology as an example, or a portion of the traffic in the third topology needs to be migrated into the second topology. S1450 in method 1700 includes steps S1456 and S1457.
S1456, the third host node transmits the first traffic transmission information to the donor-DU 3.
Specifically, CU3 sends first traffic transmission information to the donor-DU 3. The first traffic transmission information is used for indicating that the transmission path of the partial traffic to be migrated is from the donor-DU3 to the donor-DU2 through the tunnel, or that the traffic originally needing to go through the third topology needs to go through the tunnel to be sent to the donor-DU2 when passing through the donor-DU3, instead of carrying out DL MAPPING, and going through the backhaul link of the original third topology. In the above case, the traffic transmission path of the partial traffic to be migrated is "CU1- > donor-DU3- > tunnel- > donor-DU2".
It should be appreciated that DL MAPPING is a non-F1 anchor CU configured to a donor-DU for the donor-DU to map downstream traffic onto BH resources of its own topology.
Optionally, the first traffic transmission information may include identification information of the portion of the traffic to be migrated, such as source and destination IP address identifications of the traffic, may include identification information of the donor-DU2, such as an IP address, for determining that the traffic is transmitted to the donor-DU2, and may also carry updated DL MAPPING rules of the portion of the traffic to be migrated.
S1457, the second host node transmits the second traffic transmission information to the donor-DU 2.
Specifically, CU2 sends second traffic transmission information to the donor-DU 2. The second traffic transmission information is used to indicate the traffic transmission paths selected by the traffic to be migrated in the third topology after reaching the donor-DU2, for example, the traffic to be migrated should be mapped to which BH resources after reaching the donor-DU 2.
The traffic withdrawal scenario in the second topology is the same as above, and this is not described in detail herein.
By adopting the methods 1400 to 1700, the information of traffic withdrawal can be interacted between two non-F1 anchor CUs, the F1 anchor CUs can be unified or respectively informed to enable the F1 anchor CU to complete traffic redistribution, or the F1 anchor CU can not be informed, and the withdrawal of downlink traffic or traffic migration in the second topology and the third topology can be realized by establishing an inter-donor-DU tunnel.
It will be appreciated that the examples of fig. 9 to 17 in the embodiments of the present application are merely for facilitating understanding of the embodiments of the present application by those skilled in the art, and are not intended to limit the embodiments of the present application to the specific scenarios illustrated. It will be apparent to those skilled in the art from the examples of fig. 9-17 that various equivalent modifications or variations may be made, and such modifications or variations are intended to be within the scope of the embodiments of the present application.
It will also be appreciated that some optional features of the various embodiments of the application may, in some circumstances, be independent of other features or may, in some circumstances, be combined with other features, without limitation.
It is also to be understood that the aspects of the embodiments of the application may be used in any reasonable combination, and that the explanation or illustration of the various terms presented in the embodiments may be referred to or explained in the various embodiments without limitation.
It should be further understood that the magnitude of the various numerical numbers in the embodiments of the present application does not mean the order of execution, but merely serves to distinguish between the convenience of description and the implementation of the embodiments of the present application, and should not constitute any limitation.
It should be further understood that, in the embodiments of the present application, some message names, such as the first traffic migration request information or the first traffic migration configuration information, etc., are referred to, and it should be understood that the names do not limit the protection scope of the embodiments of the present application.
It should also be understood that, in the foregoing embodiments of the method and operations implemented by the host node, the method and operations may also be implemented by a component (such as a chip or a circuit) of the host node, which is not limited thereto. Corresponding to the methods given by the above method embodiments, the embodiments of the present application also provide corresponding apparatuses, where the apparatuses include corresponding modules for executing the above method embodiments. The module may be software, hardware, or a combination of software and hardware. It will be appreciated that the technical features described in the method embodiments described above are equally applicable to the device embodiments described below.
It should be understood that the first host node, the second host node, and the third host node may perform some or all of the steps in the above-described embodiments, which are merely examples, and that embodiments of the present application may also perform other operations or variations of the various operations. Furthermore, the various steps may be performed in a different order presented in the above embodiments, and it is possible that not all of the operations in the above embodiments are performed.
The method of communication provided by the embodiment of the present application is described in detail above with reference to fig. 9 to 17, and the communication device provided by the embodiment of the present application is described in detail below with reference to fig. 18 to 20, so as to implement the communication method shown in fig. 9 to 17. It should be understood that the descriptions of the apparatus embodiments and the descriptions of the method embodiments correspond to each other, and thus, descriptions of details not shown may be referred to the above method embodiments, and for the sake of brevity, some parts of the descriptions are omitted.
Fig. 18 is a schematic block diagram of a communication apparatus provided by an embodiment of the present application. The apparatus 1800 comprises a transceiver unit 1810, which transceiver unit 1810 may be used to implement corresponding communication functions. The transceiver unit 1810 may also be referred to as a communication interface or a communication unit.
Optionally, the apparatus 1800 may further comprise a processing unit 1820, which processing unit 1820 may be adapted to perform data processing.
Optionally, the apparatus 1800 further comprises a storage unit, which may be used to store instructions and/or data, and the processing unit 1820 may read the instructions and/or data in the storage unit, so that the apparatus implements the actions of the different terminal devices in the foregoing respective method embodiments, for example, the actions of the first host node, the second host node, and the third host node.
The apparatus 1800 may be configured to perform the actions performed by the first host node, the second host node, and the third host node in the above method embodiments, where the apparatus 1800 may be the first host node, the second host node, and the third host node, or a component of the first host node, the second host node, or the third host node, the transceiver unit 1810 is configured to perform operations related to the transceiving of the first host node, the second host node, or the third host node in the above method embodiments, and the processing unit 1820 is configured to perform operations related to the processing of the first host node, the second host node, or the third host node in the above method embodiments.
It should also be appreciated that the apparatus 1800 herein is embodied in the form of functional units. The term "unit" herein may refer to an Application Specific Integrated Circuit (ASIC), an electronic circuit, a processor (e.g., a shared, dedicated, or group processor, etc.) and memory that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable components that support the described functionality. In an alternative example, it may be understood by those skilled in the art that the apparatus 1800 may be specifically configured to perform each flow and/or step corresponding to the first host node, the second host node, or the third host node in the foregoing method embodiments, or the apparatus 1800 may be specifically configured to perform each flow and/or step corresponding to the first host node, the second host node, or the third host node in the foregoing method embodiments, which are not described herein for the sake of avoiding repetition.
The apparatus 1800 of each of the above aspects has a function of implementing the corresponding step performed by the first host node, the second host node, or the third host node in the above method, or the apparatus 1800 of each of the above aspects has a function of implementing the corresponding step performed by the first host node, the second host node, or the third host node in the above method. The functions may be implemented by hardware, or may be implemented by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the functions described above, for example, the transceiver unit may be replaced by a transceiver (for example, a transmitting unit in the transceiver unit may be replaced by a transmitter, a receiving unit in the transceiver unit may be replaced by a receiver), and other units, such as a processing unit, may be replaced by a processor, to perform the transceiver operations and related processing operations in the respective method embodiments, respectively.
The transceiver 1810 may be a transceiver circuit (e.g., may include a receiving circuit and a transmitting circuit), and the processing unit may be a processing circuit.
It should be noted that the device in fig. 18 may be the host node in the foregoing embodiment, or may be a chip or a system on chip (SoC), for example. The receiving and transmitting unit can be an input and output circuit and a communication interface, and the processing unit is a processor or a microprocessor or an integrated circuit integrated on the chip. And are not limited herein.
As shown in fig. 19, an embodiment of the present application provides another communications apparatus 1900. The apparatus 1900 comprises a processor 1910, the processor 1910 being coupled to a memory 1920, the memory 1920 being for storing computer programs or instructions and/or data, the processor 1910 being for executing the computer programs or instructions stored by the memory 1920 or for reading data stored by the memory 1920 for performing the methods in the method embodiments above.
Optionally, the processor 1910 is one or more.
Optionally, the memory 1920 is one or more.
Optionally, the memory 1920 is integrated with the processor 1910 or separately provided.
Optionally, as shown in fig. 19, the apparatus 1900 further comprises a transceiver 1930, the transceiver 1930 being used for receiving and/or transmitting signals. For example, the processor 1910 may be configured to control the transceiver 1930 to receive and/or transmit signals.
As an aspect, the apparatus 1900 is configured to implement operations performed by the first host node, the second host node, or the third host node in the above method embodiments.
For example, the processor 1910 is configured to execute computer programs or instructions stored in the memory 1920 to implement the operations associated with the first host node in the various method embodiments above. For example, the first host node, the second host node, or the third host node in any of the embodiments shown in fig. 9 to 17, or the method of the first host node, the second host node, or the third host node in any of the embodiments shown in fig. 9 to 17.
It should be appreciated that the processor referred to in the embodiments of the present application may be a central processing unit (central processing unit, CPU), but may also be other general purpose processors, digital signal processors (DIGITAL SIGNAL processors, DSPs), application Specific Integrated Circuits (ASICs), off-the-shelf programmable gate arrays (field programmable GATE ARRAY, FPGAs) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
It should also be understood that the memory referred to in embodiments of the present application may be volatile memory and/or nonvolatile memory. The nonvolatile memory may be a read-only memory (ROM), a Programmable ROM (PROM), an erasable programmable ROM (erasable PROM), an electrically erasable programmable EPROM (EEPROM), or a flash memory. The volatile memory may be random access memory (random access memory, RAM). For example, RAM may be used as an external cache. By way of example, and not limitation, RAM includes various forms of static random access memory (STATIC RAM, SRAM), dynamic random access memory (DYNAMIC RAM, DRAM), synchronous Dynamic Random Access Memory (SDRAM), double data rate synchronous dynamic random access memory (doubledata RATE SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (ENHANCED SDRAM, ESDRAM), synchronous link dynamic random access memory (SYNCHLINK DRAM, SLDRAM), and direct memory bus random access memory (direct rambus RAM, DR RAM).
It should be noted that when the processor is a general purpose processor, DSP, ASIC, FPGA or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, the memory (storage module) may be integrated into the processor.
It should also be noted that the memory described herein is intended to comprise, without being limited to, these and any other suitable types of memory.
Referring to fig. 20, an embodiment of the present application provides a chip system 2000. The system-on-chip 2000 (or may also be referred to as a processing system) includes logic 2010 and an input/output interface 2020.
Logic 2010 may be a processing circuit in system on a chip 2000. Logic 2010 may be coupled to the memory unit and invoke instructions in the memory unit so that system-on-chip 2000 may implement the methods and functions of embodiments of the present application. The input/output interface 2020 may be an input/output circuit in the chip system 2000, outputting information processed by the chip system 2000, or inputting data or signaling information to be processed into the chip system 2000 for processing.
As an aspect, the chip system 2000 is configured to implement the operations performed by the first host node, the second host node, or the third host node in the above method embodiments.
For example, the logic 2010 may be configured to implement operations related to processing by the first host node, the second host node, or the third host node in the above method embodiments, such as the first host node, the second host node, or the third host node in any of the embodiments shown in fig. 9 to 17, and the input/output interface 2020 may be configured to implement operations related to transmitting and/or receiving by the first host node, the second host node, or the third host node in the above method embodiments, such as the first host node, the second host node, or the third host node in any of the embodiments shown in fig. 9 to 17.
The embodiments of the present application further provide a computer readable storage medium having stored thereon computer instructions for implementing the methods performed by the first host node, the second host node, or the third host node in the above-described method embodiments.
For example, the computer program, when executed by a computer, enables the computer to implement the method performed by the first host node, the second host node, or the third host node in the embodiments of the method described above.
The embodiments of the present application also provide a computer program product comprising instructions which, when executed by a computer, implement the method performed by the first host node, the second host node, or the third host node in the above method embodiments.
The explanation and beneficial effects of the related content in any of the above-mentioned devices can refer to the corresponding method embodiments provided above, and are not repeated here.
In the several embodiments provided by the present application, it should be understood that the disclosed apparatus and method may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Furthermore, the coupling or direct coupling or communication connection shown or discussed with each other may be through some interface, device or unit indirect coupling or communication connection, which may be in electrical, mechanical or other form.
In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, produces a flow or function in accordance with embodiments of the present application, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. For example, the computer may be a personal computer, a server, or a network device, etc. The computer instructions may be stored in or transmitted from one computer-readable storage medium to another, for example, by wired (e.g., coaxial cable, optical fiber, digital Subscriber Line (DSL)), or wireless (e.g., infrared, wireless, microwave, etc.). The computer readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains an integration of one or more available media. The usable medium may be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid State Disk (SSD) STATE DISK, etc.. For example, the aforementioned usable medium includes but is not limited to: a U-disk, a removable hard disk, a read-only memory (ROM), a random access memory (random access memory, RAM), a magnetic disk, or an optical disk, or the like, which can store program codes.
The foregoing is merely illustrative of the present application, and the present application is not limited thereto, and any person skilled in the art will readily recognize that variations or substitutions are within the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.