Data forwarding method and device

Abstract

The invention discloses a data forwarding method and device. The method comprises the steps of obtaining first information; the first information is used for configuring a forwarding unit of the relay equipment to forward data from the first network equipment. Wherein the forwarding unit is in the first state, and the forwarding unit forwards data from the second network equipment in the first state. According to the embodiment of the invention, when the relay device forwards the data of the second network device, the first information sent by the first network device is received. Therefore, the relay equipment can configure to forward the data from the first network equipment without disconnecting the forwarding with the second network equipment. The communication between the terminal and the network equipment is ensured not to be interrupted, the service continuity of the terminal can be ensured, and the communication performance of the terminal and the user experience are improved.

Description

Technical Field

[0001] This application relates to the field of communications, and in particular, to a data forwarding method and apparatus. Background Art

[0002] Coverage is a basic function of a cellular network. Deploying intermediate nodes in areas with poor signal coverage can expand network coverage. A radio frequency (RF) repeater, as a non-regenerative type of relay node, can perform operations such as amplifying and forwarding the received signal. Among them, a repeater can also be referred to as a straight-through amplifier. The RF repeater has advantages such as low cost, simple structure, and easy deployment. However, how to improve the communication performance of a terminal in a relay scenario has become a problem to be solved currently. Summary of the Invention

[0003] Embodiments of this application provide a data forwarding method and apparatus, which can receive configuration information for forwarding data of other network devices during the period when a relay device forwards data. The relay device does not need to disconnect the forwarding from the source network device, so that the communication between the terminal and the network device will not be interrupted, improving the user experience.

[0004] To achieve the above object, this application adopts the following technical solutions:

[0005] In a first aspect, a data forwarding method is provided, including: obtaining first information. The first information is used to configure a forwarding unit of a relay device to forward data from a first network device. Among them, the forwarding unit is in a first state, and the forwarding unit forwards data from a second network device in the first state.

[0006] Embodiments of this application can receive the first information sent by the first network device when the relay device forwards data of the second network device. This enables the relay device to configure to forward data from the first network device without disconnecting the forwarding from the second network device. It ensures that the communication between the terminal and the network device will not be interrupted, can guarantee the service continuity of the terminal, and improve the communication performance of the terminal and the user experience.

[0007] In a possible design, the method further includes: maintaining the state of the forwarding unit as the first state; in the first state, controlling the forwarding unit to forward data sent by the first network device according to the first information.

[0008] The relay device involved in embodiments of this application can implement simultaneously configuring to forward data from the first network device and configuring to forward data from the second network device. This enables the relay device not to disconnect the connection from the second network device, and the terminal can receive data from different network devices, avoiding communication interruption caused by Fwd shutdown, and improving the communication performance of the terminal and the user experience.

[0009] In a possible design, before obtaining the first information, the method further includes: sending second information, where the second information is used to instruct the forwarding unit of the relay device to forward data from the first network device. For example, it can also be considered that the second information is used to trigger the first network device or the second network device to send the first information.

[0010] The relay device according to the embodiment of the present application can send the second information, so that the network device receiving the second information can know that the relay device is to forward data from the first network device. Further, it triggers the first network device to send the first information to the relay device, thereby achieving the purpose of the relay device forwarding data from the first network device.

[0011] In a possible design, before sending the second information, the method further includes: receiving seventh information from a third network device, where the seventh information is used to indicate the first network device.

[0012] The relay device according to the embodiment of the present application can also determine to forward data from the first network device according to the OAM configuration. It can more flexibly configure the network devices that the relay device needs to forward, improving the flexibility of the configuration.

[0013] In a possible design, configuring the forwarding unit to forward data from the first network device includes: generating a first logical forwarding unit. Wherein, the forwarding unit includes a first logical forwarding unit and a second logical forwarding unit. The second logical forwarding unit is used to forward data sent by the second network device. The relay device configures the first logical forwarding unit to forward data sent by the first network device.

[0014] The embodiment of the present application can realize that different logical Fwds are configured to forward data from different network devices by generating logical Fwds. So that the Fwd of the relay device can operate independently for different logical Fwds, controlling whether the corresponding logical Fwd forwards the data of the corresponding network device, improving the flexibility of the Fwd configuration.

[0015] In a possible design, the method further includes: controlling the forwarding unit to stop forwarding data from the second network device.

[0016] The embodiment of the present application can control the forwarding unit to stop forwarding data from the second network device, so as to avoid the resource conflicts, signal interference, etc. that may be caused by the forwarding unit forwarding data from different network devices simultaneously in some scenarios. It can also reduce the power consumption of the relay device and reduce resource consumption in some scenarios.

[0017] In a possible design, the method further includes: receiving third information. The third information is used to instruct the forwarding unit to stop forwarding data from the second network device.

[0018] In the embodiments of the present application, the network device may instruct the relay device to stop forwarding data from the second network device through the third information, thereby achieving flexible control of the data forwarding of the relay device.

[0019] In a possible design, the forwarding unit includes a second logical forwarding unit. Controlling the forwarding unit to stop forwarding data from the second network device includes: controlling the second logical forwarding unit to stop forwarding data from the second network device.

[0020] The embodiments of the present application can control the corresponding logical forwarding unit to stop forwarding data from the corresponding network device, thereby achieving the opening and closing of the logically independent control forwarding unit and improving the flexibility of the forwarding unit to forward data.

[0021] In a possible design, the first information includes a first parameter, and the first parameter is used to indicate the beam used by the forwarding unit to forward data sent by the first network device.

[0022] In the embodiments of the present application, the first information may include the beam used to indicate the forwarding unit to forward data sent by the first network device, so that the relay device can configure the forwarding unit to forward based on the beam. Without interruption of communication between the terminal and the second network device, forward the data from the first network to improve the user experience.

[0023] In a possible design, the first parameter is obtained through a second parameter, and the second parameter is used to indicate the beam used by the forwarding unit to forward data sent by the second network device.

[0024] In the embodiments of the present application, the beam used by the forwarding unit to forward data sent by the first network device may have a certain correlation with the beam used by the forwarding unit to forward data sent by the second network device, reducing the problems caused by excessive beam changes due to network device changes, and improving the communication performance and user experience of the terminal.

[0025] In a possible design, the first information further includes a cell identifier of the target cell, where the target cell is the cell where the forwarding unit forwards the data of the first network device.

[0026] The first information of the embodiments of the present application may further include the cell identifier of the target cell, so that the relay device can determine the target cell based on the cell identifier and forward the data of the target cell, improving the forwarding efficiency of the relay device.

[0027] In a possible design, the relay device is dual-connected to the first network device and the second network device. Among them, there is a first control link between the relay device and the first network device, and a second control link between the relay device and the second network device.

[0028] Embodiments of this application can, in the scenario where the relay device is dual-connected, not interrupt the service of the relay device, and can change the forwarding network device of the relay device. There is no need to release the MT of the relay device to the IDLE state or the INACTIVE state. This improves the communication performance and service experience of the terminal under the relay device.

[0029] In a possible design, there is a second control link and a second backhaul link between the relay device and the second network device. Before obtaining the first information, control the mobile terminal unit of the relay device to perform cell handover or redirection to obtain the first control link between the relay device and the first network device. Obtaining the first information includes: obtaining the first information through the first control link.

[0030] Embodiments of this application can, in the case where the relay device switches the network device it is connected to, not interrupt the service of the relay device. And can change the forwarding network device of the relay device, improving the communication performance and service experience of the terminal.

[0031] In a possible design, the method further includes: receiving an eighth piece of information through the second control link. Among them, the eighth piece of information is used to indicate that after the mobile terminal unit is redirected to a cell under the first network device, initiate the establishment of a Radio Resource Control (RRC) connection to the first network device through the mobile terminal unit, or the eighth piece of information is used to indicate that the mobile terminal unit switches to a cell under the first network device.

[0032] In embodiments of this application, the second network device can also, after the relay device performs cell handover or redirection, instruct the relay device to reconnect to a cell under the first network device to implement the switching of the network device connected by the relay device.

[0033] In a possible design, the method further includes: during the cell handover or redirection of the mobile terminal unit, forwarding data from the second network device through the forwarding unit.

[0034] Embodiments of this application can ensure that the services of the terminal are not interrupted, improving the communication performance and user experience of the terminal.

[0035] In a possible design, there is a second control link between the relay device and the second network device. Obtaining the first information includes: obtaining the first information through the second control link. For example, the method may further include obtaining the first backhaul link between the relay device and the first network device based on the first information.

[0036] Embodiments of the present application may allow the network device that controls the relay device to be different from the network device used for signal forwarding. And without interrupting the service of the relay device, the forwarding network device of the relay device can be changed, and at the same time, the connection relationship of the MT of the relay device does not need to be changed. Without interrupting the service of the relay device, the communication performance and service experience of the terminal are improved.

[0037] In a possible design, the method further includes: the public land mobile network (PLMN) supported or selected by the mobile terminal unit of the relay device is different from the PLMN corresponding to the terminal served by the relay device, and the ninth information is received through the first backhaul link with the first network device, where the ninth information is used to instruct the terminal to perform beam switching, RRC release, or cell switching. Wherein, the terminal receives the data forwarded by the relay device.

[0038] Embodiments of the present application can enable some specific terminals to use the service of the relay device, thereby realizing flexible configuration of the relay device.

[0039] In a second aspect, a data forwarding method is provided, including: generating first information, where the first information is used to configure the forwarding unit of the relay device to forward data from the first network device in a first state, where the forwarding unit in the first state forwards data sent by the second network device; sending the first information. For example, the first network device may send the first information to the relay device. Or, for example, the first network device may send the first information to the second network device.

[0040] Embodiments of the present application may send the first information when the relay device forwards the data of the second network device. So that the relay device can be configured to forward the data from the first network device without disconnecting the forwarding with the second network device. Ensure that the communication between the terminal and the network device will not be interrupted, can ensure the service continuity of the terminal, and improve the communication performance and user experience of the terminal.

[0041] In a possible design, the first information is used to configure the forwarding unit of the relay device to forward data from the first network device in a first state, including: the first information is used to configure the forwarding unit to forward data from the first network device while maintaining the first state.

[0042] In a possible design, generating the first information includes: satisfying a first condition, generating the first information; where the first condition includes at least one of the following conditions: sending fourth information, where the fourth information is used to request or determine that the forwarding unit forwards data from the first network device; receiving fifth information, where the fifth information is used to determine or request that the forwarding unit forwards data from the first network device.

[0043] In a possible design, the first information includes a first parameter, and the first parameter is used to indicate the beam used by the forwarding unit to forward the data sent by the first network device.

[0044] In a possible design, the method further includes: receiving sixth information from a second network device, where the sixth information carries a second parameter, and the second parameter is used to indicate the beam used by the forwarding unit to forward the data sent by the second network device; obtaining the first parameter based on the second parameter.

[0045] In a possible design, the first information further includes the cell identifier of the target cell, where the target cell is the cell to which the forwarding unit forwards the data of the first network device.

[0046] In a possible design, the first network device and the second network device are network devices that are dual-connected to the mobile terminal unit of the relay device, where there is a first control link between the relay device and the first network device, and there is a second control link between the relay device and the second network device.

[0047] In a possible design, before sending the first information, cell handover or redirection is performed through the mobile terminal unit of the relay device to obtain the first control link between the first network device and the relay device; sending the first information includes: sending the first information through the first control link.

[0048] In a possible design, the method further includes: sending third information, where the third information is used to indicate that the forwarding unit stops forwarding the data from the second network device.

[0049] In a possible design, the forwarding unit includes a second logical forwarding unit, and the fourth information is further used to indicate that the second logical forwarding unit stops forwarding the data from the second network device.

[0050] In a possible design, during the cell handover or redirection of the mobile terminal unit, the forwarding unit maintains the first state.

[0051] In a possible design, the method further includes: when the public land mobile network (PLMN) supported or selected by the mobile terminal unit of the relay device is different from the PLMN corresponding to the terminal served by the relay device, sending ninth information through the first backhaul link between the relay device and the terminal, where the ninth information is used to indicate that the terminal performs beam switching, RRC release, or cell handover, and the terminal receives the data forwarded by the relay device.

[0052] In a possible design, the method further includes: obtaining the first backhaul link between the first network device and the relay device based on the first information.

[0053] In a third aspect, a data forwarding method is provided, including: triggering a first network device to generate first information, where the first information is used to configure a forwarding unit of a relay device to forward data from the first network device in a first state, and in the first state, the forwarding unit forwards data sent by a second network device. For example, the second network device may trigger the first network device to send the first information to the relay device. For another example, the second network device may trigger the first network device to send the first information to the second network device, and then the second network device sends the first information to the relay device.

[0054] In an embodiment of the present application, when the relay device forwards data of the second network device, the first network device may be triggered to send the first information, so that the relay device can configure to forward data from the first network device without disconnecting the forwarding connection with the second network device, ensuring that communication between the terminal and the network device will not be interrupted, guaranteeing the service continuity of the terminal, and improving the communication performance of the terminal and the user experience.

[0055] In a possible design, the first information for configuring the forwarding unit of the relay device to forward data from the first network device in the first state includes: the first information is used to configure the forwarding unit to forward data from the first network device while maintaining the first state.

[0056] In a possible design, triggering the first network device to generate the first information includes: when a first condition is met, triggering the first network device to generate the first information; where the first condition includes at least one of the following conditions: receiving fourth information for requesting or determining that the forwarding unit forwards data from the first network device; sending fifth information for determining or requesting that the forwarding unit forwards data from the first network device.

[0057] In a possible design, the first information includes a first parameter for indicating the beam used by the forwarding unit to forward data sent by the first network device.

[0058] In a possible design, the first parameter is obtained from a second parameter for indicating the beam used by the forwarding unit to forward data sent by the second network device; the method further includes: sending sixth information carrying the second parameter.

[0059] In a possible design, the first information further includes a cell identifier of a target cell, where the target cell is the cell where the forwarding unit forwards data of the first network device.

[0060] In a possible design, before triggering the first network device to generate the first information, the method further includes: receiving second information for indicating that the forwarding unit of the relay device forwards data from the first network device.

[0061] In a possible design, the first network device and the second network device are network devices for dual connection of the mobile terminal unit of the relay device. There is a first control link between the relay device and the first network device, and a second control link between the relay device and the second network device.

[0062] In a possible design, there is a second control link and a second backhaul link between the relay device and the second network device; before triggering the first network device to generate the first information, the method further includes: triggering the mobile terminal unit of the relay device to perform cell handover or redirection to obtain the first control link between the first network device and the relay device.

[0063] In a possible design, before obtaining the first control link, the method further includes: sending an eighth piece of information through the second control link; where the eighth piece of information is used to indicate that after the mobile terminal unit is redirected to a cell under the first network device, an establishment of a radio resource control (RRC) connection is initiated to the first network device through the mobile terminal unit, or the eighth piece of information is used to indicate that the mobile terminal unit switches to a cell under the first network device.

[0064] In a possible design, during the cell handover or redirection of the mobile terminal unit, the forwarding unit is maintained to forward data from the second network device.

[0065] In a possible design, there is a second control link between the relay device and the second network device. The method further includes: sending a first piece of information through the second control link.

[0066] In a possible design, the method further includes: sending a third piece of information, where the third piece of information is used to instruct the forwarding unit to stop forwarding data from the second network device.

[0067] In a fourth aspect, a data forwarding method includes: the public land mobile network (PLMN) supported or selected by the mobile terminal unit of the relay device is different from the PLMN corresponding to the terminal served by the relay device, and a ninth piece of information is sent through the first backhaul link between the relay device and the relay device, where the ninth piece of information is used to instruct the terminal to perform beam switching, RRC release, or cell handover, and where the terminal receives the data forwarded by the relay device.

[0068] The embodiments of the present application can determine whether different terminals are allowed to use the relay device, and enable some specific terminals to use the services of the relay device, realizing flexible configuration of the relay device.

[0069] Fifth aspect, a data forwarding method, comprising: a first network device generates first information. The first information is used to configure a forwarding unit of a relay device to forward data from the first network device. The first network device sends second interface information to a second network device, wherein the second interface information carries the first information; the second network device sends the first information to the relay device.

[0070] In a possible design, the second interface information is Xn interface information.

[0071] The relay device according to the embodiment of the present application can receive the first information sent by the first network device through the second network device. So that the relay device can forward data from the first network device. Improve the communication performance of the terminal and the user experience.

[0072] Sixth aspect, a data forwarding apparatus is provided. The data forwarding apparatus includes: a processor and a memory; the memory is used to store computer instructions, and when the processor executes the instructions, the data forwarding apparatus is enabled to execute the data forwarding method according to any one of the above aspects.

[0073] Seventh aspect, a chip system is provided. The chip system includes a processor and an input / output port. The processor is used to implement the processing functions involved in the data forwarding method according to any one of the above aspects, and the input / output port is used to implement the transceiver functions involved in the data forwarding method according to any one of the above aspects.

[0074] In a possible design, the chip system further includes a memory, and the memory is used to store program instructions and data for implementing the functions involved in the data forwarding method according to any one of the above aspects.

[0075] The chip system can be composed of chips, or can include chips and other discrete devices.

[0076] Eighth aspect, a communication system is provided. The system includes a relay device that executes any method according to any one of the above aspects, and a network device that executes any method according to any one of the above aspects.

[0077] Ninth aspect, a computer-readable storage medium is provided. Computer instructions are stored in the computer-readable storage medium; when the computer instructions run on a computer, the computer is enabled to execute the data forwarding method according to any one of the designs in the above aspects.

[0078] Tenth aspect, a computer program product is provided. The computer program product includes a computer program or instructions, and when the computer program or instructions run on a computer, the computer is enabled to execute the data forwarding method according to any one of the designs in the above aspects. Description of the Drawings

[0079] Figure 1 It is a schematic diagram of the architecture of the communication system provided by the embodiment of the present application;

[0080] Figure 2 It is a schematic diagram of the architecture of a network control repeater provided by the embodiment of the present application;

[0081] Figure 3 It is a schematic diagram of an example scenario of an integrated access and backhaul node provided by the embodiment of the present application;

[0082] Figure 4 It is a schematic diagram of the network architecture of an integrated access and backhaul node provided by the embodiment of the present application;

[0083] Figure 5 It is a schematic diagram of the user plane protocol stack of the network of an integrated access and backhaul node provided by the embodiment of the present application;

[0084] Figure 6 It is a schematic diagram of the control plane protocol stack of the network of an integrated access and backhaul node provided by the embodiment of the present application;

[0085] Figure 7 It is a schematic diagram of the migration process of the distributed unit of an integrated access and backhaul node provided by the embodiment of the present application;

[0086] Figure 8 It is a schematic diagram of a data forwarding method provided by the embodiment of the present application;

[0087] Figure 9 It is a schematic diagram of a dual-connection scenario of a relay device provided by the embodiment of the present application;

[0088] Figure 10 It is a schematic diagram of the interaction of a data forwarding method provided by the embodiment of the present application;

[0089] Figure 11 It is a schematic diagram of a single-connection scenario of a relay device provided by the embodiment of the present application;

[0090] Figure 12 It is a schematic diagram of the interaction of another data forwarding method provided by the embodiment of the present application;

[0091] Figure 13 It is a schematic diagram of another single-connection scenario of a relay device provided by the embodiment of the present application;

[0092] Figure 14 It is a schematic diagram of the interaction of yet another data forwarding method provided by the embodiment of the present application;

[0093] Figure 15 It is a schematic diagram of yet another single-connection scenario of a relay device provided by the embodiment of the present application;

[0094] Figure 16Another interaction schematic diagram of the data forwarding method provided by the embodiment of the present application;

[0095] Figure 17 A schematic diagram of a data forwarding device provided by the embodiment of the present application;

[0096] Figure 18 Another schematic diagram of a data forwarding device provided by the embodiment of the present application. Detailed implementation manners

[0097] The network architecture and service scenarios described in the embodiments of the present application are used to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided by the embodiments of the present application. Those of ordinary skill in the art can know that with the evolution of the network architecture and the emergence of new service scenarios, the technical solutions provided by the embodiments of the present application are equally applicable to similar technical problems.

[0098] The terms "first" and "second" in the description and drawings of the embodiments of the present application are used to distinguish different objects or different processes for the same object. The words "first", "second", etc. can distinguish the same items or similar items with basically the same functions and effects. For example, the first device and the second device are only used to distinguish different devices, and do not limit their sequence. Those skilled in the art can understand that the words "first", "second", etc. do not limit the quantity and execution order, and the words "first", "second", etc. do not necessarily limit to be different.

[0099] "At least one" means one or more, and "a plurality" means two or more than two.

[0100] In the description of the embodiments of the present application, unless otherwise specified, " / " means that the associated objects before and after are in an "or" relationship. For example, A / B can represent A or B; the "and / or" in the embodiments of the present application is only a description of the association relationship of the associated objects, indicating that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist simultaneously, and B exists alone. Among them, A and B can be singular or plural.

[0101] In the description of the embodiments of the present application, unless otherwise specified, "a plurality" means two or more than two. "At least one (item)" or its similar expression means any combination of these items, including any combination of single item (item) or plural items (items). For example, at least one (item) of a, b, or c can represent: a, b, c, a - b, a - c, b - c, or a - b - c, where a, b, and c can be single or multiple.

[0102] In addition, for the convenience of clearly describing the technical solutions of the embodiments of the present application, in the embodiments of the present application, terms such as "first" and "second" are used to distinguish identical or similar items with basically the same functions and roles. Those skilled in the art can understand that terms such as "first" and "second" do not limit the quantity and execution order, and "first", "second", etc. do not necessarily mean different.

[0103] In the embodiments of the present application, words such as "exemplary" or "for example" are used to indicate examples, illustrations, or explanations. Any embodiment or design solution described as "exemplary" or "for example" in the embodiments of the present application should not be construed as being more preferred or having more advantages than other embodiments or design solutions. Rather, the use of words such as "exemplary" or "for example" is intended to present relevant concepts in a specific manner for easy understanding.

[0104] It can be understood that the "embodiments" mentioned throughout the specification mean that specific features, structures, or characteristics related to the embodiments are included in at least one embodiment of the embodiments of the present application. Therefore, the various embodiments throughout the specification do not necessarily refer to the same embodiment. In addition, these specific features, structures, or characteristics can be combined in one or more embodiments in any suitable manner. It can be understood that in the various embodiments of the embodiments of the present application, the magnitudes of the sequence numbers of the various processes do not mean the order of execution, and the execution order of the various processes should be determined by their functions and internal logics, and should not constitute any limitation to the implementation process of the embodiments of the present application.

[0105] It can be understood that in the embodiments of the present application, both "when..." and "if" refer to corresponding processing under certain objective circumstances, which do not limit time, and do not require a judgment action during implementation, nor do they mean the existence of other limitations.

[0106] It can be understood that some optional features in the embodiments of the present application can, in some scenarios, be implemented independently without relying on other features, such as the current solution they are based on, to solve the corresponding technical problems and achieve the corresponding effects. In some scenarios, they can also be combined with other features according to requirements. Correspondingly, the devices given in the embodiments of the present application can also implement these features or functions accordingly, which will not be elaborated here.

[0107] In the embodiments of the present application, unless otherwise specified, the same or similar parts among the various embodiments can be referred to each other. In the embodiments of the present application, among the various embodiments and among the various implementation manners / implementation methods / realization methods in each embodiment, if there is no special specification and logical conflict, the terms and / or descriptions among different embodiments and among the various implementation manners / implementation methods / realization methods in each embodiment are consistent and can be mutually referred to, and the technical features in different embodiments and among the various implementation manners / implementation methods / realization methods in each embodiment can be combined to form new embodiments, implementation manners, implementation methods, or realization methods according to their internal logical relationships. The implementation manners of the embodiments of the present application described below do not constitute a limitation on the protection scope of the embodiments of the present application.

[0108] Figure 1 It is a schematic diagram of the architecture of the communication system provided by the embodiments of the present application.

[0109] As Figure 1 shown, the communication system involved in the embodiments of the present application may include at least one terminal 110, a repeater 120, and a network device 130.

[0110] Among them, the terminal 110 and the repeater 120 communicate with each other wirelessly, and the repeater 120 and the network device 130 communicate with each other wirelessly. The network device 130 may be a radio access network device. Terminals can be connected to each other, and radio access network devices can be connected to each other, either wired or wirelessly. Figure 1 This is just a schematic diagram. The communication system may also include other network devices, such as a wireless backhaul device, a core network device, etc., which are not drawn in Figure 1 It. The connection relationships between the devices are not limited to the above-listed manners.

[0111] The radio access network device can be a base station, an evolved NodeB (eNodeB), a transmission reception point (TRP), a next generation NodeB (gNB) in a 5th generation (5G) mobile communication system, a next generation NodeB in a 6th generation (6G) mobile communication system, a base station in a future mobile communication system, or an access node in a WiFi system, etc.; it can also be a module or unit that completes some functions of the base station. For example, it can be a central unit (CU) or a distributed unit (DU). The radio access network device can be a macro base station, a micro base station or an indoor station, and can also be a relay node or a donor node, etc. In some other embodiments, the radio access network device can also be an access network device in an open RAN (O-RAN). In O-RAN, the CU can be called an open CU (O-CU), the DU can be called an open DU (O-DU), and the RU can be called an open RU (O-RU). The embodiments of the present application do not limit the specific technologies and specific device forms adopted by the radio access network device. The radio access network device is sometimes also simply referred to as a network device. For the convenience of description, the base station is used as an example of the radio access network device in the following description.

[0112] The repeater can also be called a relay device, a relay apparatus, a relay node, etc. For example, it can be a wireless relay device. For example, it can be an integrated access and backhaul (IAB) node or a network controlled repeater (NCR). Among them, the NCR can also be called a network controlled repeater. The embodiments of the present application do not limit the specific technologies and specific device forms adopted by the repeater.

[0113] A terminal can also be referred to as a terminal device, user equipment (UE), mobile station, mobile terminal, etc. Terminal devices can be widely applied in various scenarios, such as device-to-device (D2D), vehicle to everything (V2X) communication, machine-type communication (MTC), internet of things (IOT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grid, smart furniture, smart office, smart wearables, smart transportation, smart city, etc. Terminal devices can be mobile phones, tablets, computers with wireless transceiver functions, wearable devices, vehicles, drones, helicopters, airplanes, ships, robots, robotic arms, smart home devices, etc. The embodiments of this application do not limit the specific technologies and specific device forms adopted by terminal devices.

[0114] Base stations, repeaters, and terminals can be in fixed positions or movable. Base stations, repeaters, and terminal devices can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; and can also be deployed on airplanes, balloons, and artificial satellites in the air. The embodiments of this application do not limit the application scenarios of base stations, repeaters, and terminal devices.

[0115] Communication can be carried out between base stations and repeaters, between repeaters and terminals, between base stations and base stations, and between terminals and terminals through licensed spectrum, or through unlicensed spectrum, or simultaneously through licensed spectrum and unlicensed spectrum; communication can be carried out through spectrum below 6 gigahertz (GHz), or through spectrum above 6 GHz, or simultaneously use spectrum below 6 GHz and spectrum above 6 GHz. The embodiments of this application do not limit the spectrum resources used for wireless communication.

[0116] In the embodiments of this application, the functions of a base station can also be executed by modules (such as chips) in the base station, or by a control subsystem containing base station functions. Here, the control subsystem containing base station functions can be the control center in the application scenarios of the above terminal devices such as smart grid, industrial control, smart transportation, and smart city. The functions of a repeater can also be executed by modules (such as chips or modems) in the repeater, or by a device containing repeater functions. The functions of a terminal can also be executed by modules (such as chips or modems) in the terminal, or by a device containing terminal functions.

[0117] At present, RF repeaters have the advantages of low cost, simple structure, easy deployment, low power consumption, and low maintenance cost, and have become the simplest and most cost-effective solution to improve network coverage. They have been deployed in networks such as 2G, 3G, and 4G.

[0118] For 5G, higher-frequency spectrum resources are used to obtain a larger transmission bandwidth. For example, it includes the sub-6GHz and millimeter-wave frequency bands. However, due to the propagation characteristics of high-frequency radio, its path loss and penetration loss are very large, making it difficult to expand area coverage. There will also be some areas where communication is impossible even within the coverage area. Therefore, a relay system is needed to expand the coverage area. Among them, in the radio access network work group 4 (RAN4) of the 3rd generation partnership project (3GPP) technical standards group, in release (R) 17, it is stated that 5G RF repeaters can support frequency division duplex (FDD) or time division duplex (TDD) in the 5G Frequency Range (FR) 1 band, as well as support the FR2 band. Among them, 5G RF repeaters can also be called new radio (NR) repeaters. Among them, NR is the wireless network of 5G.

[0119] Considering that 5G also supports technologies such as TDD, configurable bandwidth part (BWP), massive multiple-input multiple-output (MIMO), and hybrid beamforming (BF), the capabilities of NR repeaters will be very different from those in the past. At present, for NR repeaters in terms of RF, adaptive BF is not performed on the user access side. Instead, static beamforming with a fixed direction is used and manually managed. When the access-side terminal encounters strong interference, this solution will lead to deteriorated performance. Among them, RF repeaters and NR repeaters usually consist of radio unit (RU) modules.

[0120] In some solutions, an NR repeater is proposed that can obtain effective control information such as timing information, transmit (TX) spatial beam information, receive (RX) spatial beam information, bandwidth information, and switch information. This enables such NR repeaters to perform "intelligent" amplify-and-forward operations. Such NR repeaters can be referred to as NCRs. Among them, NCRs can also be called smart repeaters (SRs). For example, NCRs can support uplink and downlink sensing and dynamic TDD, configurable bandwidth, beam sensing, access-side BF, uplink and downlink forwarding power control, and dynamic switch lighting. Especially in the FR2 frequency band, NCRs with adaptive BF capabilities can achieve easy and efficient area deployment.

[0121] For example Figure 2An NCR architecture is shown. It can be seen that the NCR is also different from a general repeater in architecture. In addition to the RU module, a separate mobile terminal (MT) module is added. This MT module can be used to receive and feedback control signaling sent by network devices. Among them, the RU module in the NCR can be called the NCR forwarding (Fwd) module, denoted as NCR-Fwd. NCR-Fwd indicates that the function of this module is to amplify and forward. The link between NCR-Fwd and the terminal can be called the access link, and the link between NCR-Fwd and the network device can be called the backhaul link. Among them, the role of NCR-Fwd is to transparently amplify and forward physical layer signals and does not have the function of protocol stack processing. The link between NCR-MT and the network device can be called the control link. This control link is similar to the radio resource control (RRC) connection between a general terminal and a network device. NCR-MT has the protocol functions of each layer below the RRC layer. For example, the radio link control (RLC) layer, the media access control (MAC) layer, and the physical layer (PHY). The network device sends control information about NCR-Fwd, such as beam direction, power control, etc., to NCR-MT. For example, the network device can send control information to NCR-MT through RRC messages, MAC control elements (CE), etc. NCR-MT decodes the received control information and controls NCR-Fwd to perform corresponding operations. That is to say, the "network control" function in the NCR is mainly reflected in the interaction between the network device and NCR-MT. And NCR-Fwd, as the controlled object, has a relatively simpler function.

[0122] The network access process of NCR is similar to that of the terminal because the NCR-MT itself can be regarded as a special terminal. For a terminal, when it is just powered on, it will perform cell search. For a cell that simultaneously meets the conditions that the signal quality is greater than or equal to the corresponding threshold, and it is not barred, and the public land mobile network (PLMN) broadcast by the cell contains the PLMN selected by the terminal, it can be called a suitable cell, and the terminal will camp on this suitable cell. Among them, the signal quality being greater than or equal to the corresponding threshold can also be considered to meet the S criterion. The PLMN can be understood as the corresponding operator code. After the terminal camps on the corresponding cell, it is in the RRC idle state, which can be denoted as the RRC_IDLE state. When the terminal has data services to process, the terminal will initiate a random access to the cell. After the RRC connection is established, the terminal enters the RRC connected state and conducts data service interaction. Among them, the RRC connected state can also be denoted as the RRC_CONNECTED state. Similarly, for the NCR-MT, after it enters the RRC connected state, it can establish a data radio bearer (DRB) and communicate with the operations, administration and maintenance (OAM) server. And receive control information from the network device.

[0123] In some examples, the behavior of NCR-Fwd is not the same when the NCR-MT is in different RRC states. For example, after the NCR-MT enters the RRC idle state, NCR-Fwd is turned off. Among them, the reason for the NCR-MT to enter the RRC idle state may be due to a radio link failure (RLF) and an RRC reestablishment failure. Or the OAM of NCR indicates that the NCR-MT enters the RRC idle state. In this case, the network device has lost control of the NCR. Therefore, to avoid interference, NCR needs to turn off its NCR-Fwd.

[0124] Another example is that an RLF may occur when the NCR-MT is in the RRC connected state. In this case, an RRC reestablishment can be initiated. In the protocol, this situation will be considered that the NCR-MT is still in the RRC connected state, and it will be considered that the NCR-MT enters the RRC idle state only after the RRC reestablishment fails. However, in this case, although the NCR-MT is still in the RRC connected state, the network device has also lost control of this NCR. To avoid interference, NCR needs to turn off its NCR-Fwd.

[0125] For another example, the network device is supported to release the NCR-MT to the RRC inactive state, which can be denoted as the RRC_INACTIVE state. After the NCR-MT enters the RRC_INACTIVE state, the NCR-Fwd continues to work with the current configuration. This scenario mainly considers the power saving of the NCR. It is possible that the network device does not need to modify the configuration of the NCR for some time in the future. Therefore, the NCR-MT can be released to the RRC_INACTIVE state to achieve the purpose of energy consumption reduction. And the NCR-Fwd continues to work as an ordinary NR repeater.

[0126] It can be understood that in this example, the NCR-MT is released to the RRC_INACTIVE state instead of the RRC_IDLE state because when in the RRC_INACTIVE state, if the network device hopes to control the NCR again, it can wake up the NCR-MT again to enter the RRC_CONNECTED state through paging by the radio access network (RAN). It can be understood that in this case, the network device usually refers to an access network device, such as a gNB. When in the RRC_IDLE state, only the core network (CN) can wake up the NCR-MT to enter the RRC_CONNECTED state through CN Paging. The access network device cannot wake up the NCR-MT. After the NCR-MT enters the RRC_INACTIVE state, due to possible fluctuations in the signal quality between the NCR and the access network device caused by occlusion or other reasons. For example, the signal quality of the backhaul beam is less than a certain threshold, or the NCR-MT reselects to another cell. In this case, the NCR can turn off the NCR-Fwd. For the case where the signal quality of the backhaul beam deteriorates, considering that the signal quality of the backhaul beam used by the NCR is already very poor and cannot be provided anymore, the NCR-Fwd can be turned off. The NCR-MT can actively initiate RRC resume (denoted as RRCResume) to return to the RRC_CONNECTED state. So that the NCR can receive new backhaul beam configuration information and change the original backhaul beam to a new one. For the case where the NCR-MT reselects to another cell, since the NCR-MT has changed the cell, the NCR-Fwd needs to be turned off first. The NCR can, based on specific implementation, actively initiate RRCResume in the new cell to return to the RRC_CONNECTED state, and re-receive configuration information in the new cell and serve based on this configuration information.

[0127] It can be understood that closing NCR-Fwd involved in the above examples can be considered as controlling NCR-Fwd to stop data forwarding.

[0128] In some solutions, a scenario of NCR out-of-band backhaul is provided. Among them, the meaning of out-of-band backhaul is that the frequency of NCR-Fwd forwarding is different from the frequency adopted by NCR-MT. In other words, the frequencies of the backhaul link and the access link are different from the frequency of the control link. Among them, the frequency can be considered as FR or component carrier (CC). The scenario of out-of-band backhaul can allow NCR-MT to establish a dual connection (DC) with two network devices, or the network device controlling NCR-MT and the network device to which NCR-Fwd is to forward are different network devices.

[0129] In other solutions, an implementation method in which the relay device is an IAB node is provided. Among them, the IAB architecture also has the effect of improving network coverage. For example Figure 3 As shown, in the IAB network, the relay node can be called an IAB node, denoted as IAB-node. The IAB-node can provide wireless access services for the terminal. The service data of the terminal is interacted by the IAB-node through a wireless backhaul link connected to the IAB host node. Among them, the IAB host node can be denoted as IAB-donor. The IAB-node can be composed of an MT part and a DU part. Among them, when the IAB-node faces its parent node, it can act as a terminal, that is, the role of MT; when the IAB-node faces its child nodes, it can act as a network device, that is, the role of DU. The child nodes can be, for example, another IAB-node or an ordinary terminal. The IAB-donor is considered as an access network element with complete network device functions, such as having complete base station functions. The IAB-donor can include a CU and a DU. The IAB-donor is connected to the core network serving the terminal, such as the 5G core network.

[0130] It can be understood that the backhaul link in the NCR scenario and the backhaul link in IAB are different links in different scenarios.

[0131] In an IAB network, a transmission path between a terminal and an IAB-donor may include one or more IAB-nodes. Each IAB-node needs to maintain a wireless backhaul link facing the parent node and also needs to maintain a wireless link with the child node. Of course, if the child node of the IAB-node is a terminal, then the link between the IAB-node and the child node is a wireless access link. If the child node of the IAB-node is another IAB-node, then the link between the IAB-node and the child node is a wireless backhaul link. It can be understood that in the embodiments of the present application, the wireless access link can be abbreviated as the access link, the wireless backhaul link can be abbreviated as the backhaul link, and the wireless control link can be abbreviated as the control link, which is not limited in the embodiments of the present application.

[0132] Continuing to refer to Figure 3 , assuming the path is "Terminal 1 → IAB Node 4 → IAB Node 3 → IAB Node 1 → IAB Host Node", Terminal 1 accesses IAB Node 4 through the access link, IAB Node 4 is connected to IAB Node 3 through the backhaul link, IAB Node 3 is connected to IAB Node 1 through the backhaul link, and IAB Node 1 is connected to the IAB Host Node through the backhaul link.

[0133] Figure 4 Then an IAB network architecture is shown. Logically, the IAB node-DU can be connected to the IAB host node-CU through the F1 interface. That is to say, the connection established through the F1 interface is physically realized through the NR Uu interface between each hop of the IAB node-MT and the parent node DU. However, since the IAB node-DU can finally communicate with the IAB host node-CU, it can be considered that there is an F1 interface logically.

[0134] Among them, the F1 interface can support the user plane protocol (F1 user plane, F1-U) and the control plane protocol (F1 control plane, F1-C). The user plane protocol can include one or more of the following protocol layers, such as one or more of the general packet radio service tunneling protocol user plane (GTP-U), user datagram protocol (UDP), internet protocol (IP), etc. The control plane protocol can include one or more of the following protocol layers, such as one or more of the F1 application protocol (F1AP), stream control transport protocol (SCTP), IP, etc.

[0135] Figure 5 It shows a schematic diagram of the IAB network user plane protocol stack. Among them, for the service data adaptation protocol (SDAP) layer, it can be regarded as the direct interaction between the terminal and the IAB host node-CU. Similarly, the packet data convergence protocol (PDCP) layer is similar. For protocol layers such as GTP-U, UDP, and IP, it can be regarded as the direct interaction between IAB node 2 and the IAB host node-CU. For example, it is implemented through the logically F1-U interface. Among them, Figure 5 IAB node 2 therein is the first IAB node accessed by the terminal. For the backhaul adaptation protocol (BAP) layer, it interacts through the interfaces between IAB nodes until it is connected to the IAB host node-DU. For the RLC, MAC, and PHY layers, it interacts through the NR-Uu interfaces between different nodes until it is connected to the IAB host node-DU. Figure 6 It shows a schematic diagram of the IAB network control plane protocol stack. Figure 6 And Figure 5 The difference is only that the SDAP layer is replaced by the RRC layer, the GTP-U layer is replaced by the F1AP layer, and the UDP layer is replaced by the SCTP layer. Correspondingly, for protocol layers such as F1AP, SCTP, and IP, it can be regarded as the interaction between IAB node 2 and the IAB host node-CU through the logically F1-C interface.

[0136] It can be seen that through F1-U, the IAB node and the IAB host node can perform functions such as user plane data interaction and downlink transmission status feedback. Through F1-C, the IAB node and the IAB host node can perform interface management, manage the IAB-DU, and execute configurations related to the terminal context.

[0137] In some solutions, a DU migration is proposed. In some scenarios, assume that the IAB node moves extensively, such as deploying the IAB node on a vehicle to provide services for in-vehicle terminals. In this case, the IAB node needs to change its affiliated host node. For example, change the affiliated IAB host node - CU. For both the MT part and the DU part included in the IAB node, migration can be performed. The MT migration and the DU migration can be carried out independently. Therefore, when analyzing the MT, it can be considered that the DU does not migrate during this MT migration process; while when analyzing the DU migration, it can be considered that the MT does not migrate during this DU migration process. For example Figure 7 As shown, assume that this is a DU migration of mIAB, the MT of mIAB does not migrate, and the MT of mIAB is located under the IAB host node - CU2, and the DU of mIAB migrates from the IAB host node - CU1 to the IAB host node - CU3. Figure 7 The mIAB shown in it represents a mobile IAB. Among them, mIAB includes DU1 and DU2, which can be considered as two logical DUs divided on an entity DU. Assume that the source DU is mIAB-DU1, and the process of DU migration can be that the mIAB node generates a new logical DU, that is, mIAB-DU2. mIAB-DU2 establishes an F1 interface with the IAB host node - CU3. The IAB host node - CU1 sends a handover request of the terminal to the IAB host node - CU3, and hands over the terminal from the cell under mIAB-DU1 to the cell under mIAB-DU2. The IAB host node - CU1 releases the F1 interface with mIAB-DU1, thus completing a DU migration.

[0138] It can be understood that only a limited number of IAB nodes are described in the above-mentioned examples. Of course, in reality, there may be more or fewer IAB nodes, which are not limited in the embodiments of the present application.

[0139] Both the aforementioned NCR and IAB are regarded as a kind of relay device, which can be used to improve network coverage. For the terminal, the terminal is unaware of the existence of the relay device. In the IAB network, there is no distinction between the IAB-DU and the DU of other ordinary access network devices. As long as the terminal accesses the DU, it can also be regarded as accessing the network. The backhaul link of the IAB is invisible to the terminal. In the NCR network, the terminal is also unaware of the existence of the NCR. The NCR-Fwd is used for the transparent amplification and forwarding of physical signals and is invisible to the terminal. The function of the NCR-MT is to control the NCR-Fwd by the network device, which is also invisible to the terminal.

[0140] From the perspective of the number of hops of the path in the network structure, the IAB network is more complex and can support functions such as multi-hop, dual connection, and mobility of IAB nodes. While the NCR is often a single-hop fixed relay device.

[0141] From the architecture perspective, the IAB has a DU, which means it has the function of a high-level protocol stack. A new cell can be generated under the DU. The configuration of the cell under the DU can be configured by the IAB host node - CU through the F1 interface. For the IAB node, the cell generated by its DU and the cell of the parent node accessed by the MT can be two different cells. The CU can configure these two cells separately. Among them, the cell generated by the DU can be used as the cell for serving the terminal. The NCR-Fwd does not generate a new cell. It amplifies and forwards the signals of the existing cell and cannot perform cell-level configuration on the NCR-Fwd, such as configuring the cell identifier. Physical signal-level configuration can be performed, such as controlling the direction of the beam.

[0142] From the connection relationship, the backhaul link of the IAB node is on the IAB-MT. All data communicated between the IAB-DU and the parent node and the IAB host node needs to pass through the IAB-MT. While the backhaul link of the NR directly exists between the NCR-Fwd and the network device. The link between the NCR-MT and the network device is the control link corresponding to the NCR-MT, not the backhaul link.

[0143] Obviously, the IAB structure is more complex. Although it supports more functions, the existence of the DU will also lead to a higher device cost. The NCR has a simple architecture, supports relatively simple functions, and has a lower cost. However, if you want the NCR to implement relatively complex functions, separate design for the NCR is required.

[0144] For the scenario of NCR out-of-band backhaul, since the network device forwarded by the NCR-Fwd and the network device controlling the NCR-MT are different, this requires the network device to be able to control the change of the network device forwarded by the NCR-Fwd, but currently the network device cannot achieve this control.

[0145] For the scenario of NCR single connection, the network device relayed by NCR-Fwd is the same as the network device controlling NCR-MT. Therefore, if you want to change the network device relayed by NCR-Fwd, you need to migrate NCR-MT to the corresponding network device as well. Since the switching of NCR-MT is not currently supported, it can only be achieved through redirection in the RRC release. This redirection is the redirection of the terminal to a cell. For example, by temporarily releasing NCR-MT to the RRC_INACTIVE state or the RRC_IDLE state, the redirection indication information is carried in the RRCRelease message. For example, the RedirectedCarrierInfo cell in the RRCRelease message indicates to perform cell reselection for a specific cell. When NCR-MT reselects to the cell that NCR-Fwd is to forward to, NCR-MT will initiate RRCResume or an RRC connection request (RRCSetupRequest) again to enter the RRC connected state. NCR can receive configuration information in the new cell and control NCR-Fwd to perform corresponding data forwarding according to this configuration information.

[0146] It can be seen that if you want to change the network device relayed by NCR-Fwd, NCR-MT needs to disconnect the RRC connection with the source network device, that is, release it to the RRC_INACTIVE state or the RRC_IDLE state, and temporarily turn off NCR-Fwd. NCR switches MT and Fwd to the new network device together. However, turning off NCR-Fwd will disconnect the terminal served by NCR from the network device, thereby affecting the service experience of the terminal.

[0147] Therefore, the embodiment of the present application provides a data forwarding method, which can receive the configuration information of the target network device when the relay device forwards the data of the source network device. Furthermore, the relay device can forward the data of the target network device according to the configuration information while forwarding the data of the source network device, avoiding the forwarding unit of the relay device from being turned off. This enables the terminal and the network device to maintain communication and improves the user experience.

[0148] Figure 8 It is a schematic diagram of a data forwarding method provided by an embodiment of the present application.

[0149] As Figure 8 shown, this communication process can be applicable to Figure 1 the communication scenario shown. Among them, the relay device can be NCR. Of course, in some examples, the relay device can also be any other possible relay device, which is not limited in the embodiment of the present application. The method may include the following steps:

[0150] S101, The first network device sends the first information to the relay device.

[0151] In some embodiments, the first network device sends the first information. The first information can be used to configure the forwarding unit of the relay device to forward data from the first network device.

[0152] For example, the first network device sends the first information to the relay device. The first information can be cell group configuration information, denoted as cellgroupconfig.

[0153] In some embodiments, the relay device can receive the first information from the first network device. For example, the relay device directly receives the first information sent by the first network device. Or, the relay device receives the first information forwarded by other devices, which is sent by the first network device and forwarded to the relay device through these other devices.

[0154] For example, the relay device may include a forwarding unit, such as Fwd. The relay device may also include a mobile terminal unit, such as MT. The MT of the relay device can establish a connection with the first network device, such as a first control link. The MT of the relay device can receive the first information through this first control link. The first information can be used for the relay device to control Fwd to forward data from the first network device.

[0155] S102, The second network device sends the first service data to the relay device.

[0156] In some embodiments, the second network device can send the first service data. The first service data can be regarded as the data from the second network device that the relay device needs to forward.

[0157] For example, a connection is established between the second network device and the relay device. The second network device can send the first service data through a second backhaul link between the second network device and the Fwd of the relay device. The Fwd of the relay device can receive the data from the second network device, that is, the first service data, through this second backhaul link.

[0158] S103, The relay device forwards the first service data to the terminal.

[0159] In some embodiments, the relay device can forward the data received from the second network device in S102 to the terminal. In other words, the relay device forwards the first service data to the terminal.

[0160] For example, the relay device can forward the first service data received in S102 to the terminal through the access link with the terminal, thereby realizing the communication between the second network device and the terminal based on the first service data. Of course, before S102, the second network device can also send configuration information through the second control link with the MT of the relay device, and the configuration information can be used to configure the Fwd of the relay device to forward data from the second network device. For example, the beam used when configuring the Fwd of the relay device to forward data from the second network device, and / or the cell information of the second network device. The cell indicated by the cell information of the second network device can be considered as the cell for the Fwd of the relay device to forward, that is, the Fwd of the relay device forwards the data sent by the second network device in this cell.

[0161] Of course, steps S102 and S103 can be optional steps. For example, in some scenarios, the relay device can have been used to forward data from the second network device, that is, forward the first service data, before receiving the first information. In other scenarios, a connection can be established between the relay device and the second network device, but the second network device does not send the first service data. In this case, the relay device can temporarily not forward data from the second network device, that is, does not execute S102 and S103.

[0162] S104, the first network device sends second service data to the relay device.

[0163] In some embodiments, the first network device can send second service data, which can be considered as the data from the first network device that the relay device needs to forward.

[0164] For example, a connection is established between the first network device and the relay device, and the first network device can send the second service data through the first backhaul link with the Fwd of the relay device. The Fwd of the relay device can receive the data from the first network device, that is, the second service data, through this first backhaul link.

[0165] S105, the relay device forwards the second service data to the terminal.

[0166] In some embodiments, the relay device can forward the data from the first network device received in S104 to the terminal. In other words, the relay device forwards the second service data to the terminal.

[0167] For example, the relay device can forward the second service data received in S104 to the terminal through the access link with the terminal, thereby realizing the communication between the first network device and the terminal based on the second service data. It can be understood that the relay device can determine how to configure the Fwd of the relay device to forward data from the first network device through the first information.

[0168] Of course, steps S104 and S105 can be optional steps. In some scenarios, for example, after receiving the first information, the relay device can forward the data of the first network device based on the configuration of the first information, that is, forward the second service data. In other scenarios, the relay device can establish a connection with the first network device based on the first information. However, the first network device may not send the second service data temporarily. In this case, the relay device may not forward the data from the first network device temporarily. That is, S104 and S105 are not executed. Until the first network device sends the second service data to the relay device, the relay device then executes S104 and S105. The embodiments of the present application do not make any limitations in this regard.

[0169] In the embodiments of the present application, when the relay device forwards the data of the second network device, it can receive the first information sent by the first network device. This enables the relay device to configure the forwarding of the data from the first network device without disconnecting the forwarding connection with the second network device. It ensures that the communication between the terminal and the network device will not be interrupted, can guarantee the service continuity of the terminal, and improve the communication performance of the terminal and the user experience.

[0170] In a data forwarding method provided by the embodiments of the present application, the method may further include: keeping the state of the forwarding unit as the first state. In the first state, the forwarding unit is controlled according to the first information to forward the data sent by the first network device.

[0171] In some embodiments, the Fwd of the relay device can maintain the first state, that is, the Fwd of the relay device keeps forwarding the data from the second network device. In this case, the MT of the relay device can, according to the first information, configure the Fwd of the relay device to forward the data from the first network device. The MT of the relay device can control the Fwd of the relay device to forward the data from the first network device. Of course, the Fwd of the relay device can still continue to keep forwarding the data from the second network device.

[0172] That is to say, the Fwd of the relay device can be configured to forward the data from the first network device and be configured to forward the data from the second network device simultaneously.

[0173] The relay device involved in the embodiments of the present application can be configured to forward the data from the first network device and be configured to forward the data from the second network device simultaneously. This enables the relay device to avoid disconnecting the connection with the second network device, and the terminal can receive data from different network devices, preventing communication interruption caused by the Fwd being closed, and improving the communication performance of the terminal and the user experience.

[0174] In a data forwarding method provided by an embodiment of the present application, the method further includes: generating a first logical forwarding unit, where the forwarding unit includes a first logical forwarding unit and a second logical forwarding unit, and the second logical forwarding unit is used to forward data sent by a second network device; controlling the first logical forwarding unit to forward data sent by a first network device.

[0175] In some embodiments, the Fwd of the relay device can be used as a complete entity and is configured to forward data from a first network device and is also configured to forward data from a second network device. When the Fwd of the relay device receives data from the first network device, the Fwd of the relay device is used as a complete entity to forward data from the first network device; and when the Fwd of the relay device receives data from the second network device, the Fwd of the relay device is used as a complete entity to forward data from the second network device. Of course, forwarding data from the first network device and forwarding data from the second network device can be carried out at different times respectively, or can be carried out simultaneously. For simultaneous execution, it can be considered that the Fwd of the relay device is used as a complete entity to simultaneously receive data from beams in different directions and use beams in different directions to forward data from different network devices respectively.

[0176] In some embodiments, the Fwd of the relay device can also be logically divided into multiple logical forwarding units, that is, logical Fwd. The Fwd of the relay device can generate a first logical Fwd according to the first information. The first logical Fwd is configured to forward data from the first network device. Correspondingly, the Fwd of the relay device can also generate a second logical Fwd, and the second logical Fwd is configured to forward data from the second network device. It can be understood that when, before generating the first logical Fwd, the Fwd of the relay device is only configured to forward data from one network device, it can be considered that the second logical Fwd is the Fwd of the relay device. Or rather, it can be considered that the whole Fwd of the relay device is the second logical Fwd.

[0177] It can be understood that before generating the first logical Fwd, there may already be a second logical Fwd, or there may be more other logical Fwds, which are not limited in the embodiments of the present application.

[0178] In some examples, the Fwd of the relay device can include one or more of the first logical Fwd and the second logical Fwd.

[0179] In the embodiments of the present application, different logical Fwds can be generated to implement that different logical Fwds are configured to forward data from different network devices. In this way, the Fwd of the relay device can operate separately for different logical Fwds to control whether the corresponding logical Fwd forwards the data of the corresponding network device, improving the flexibility of Fwd configuration.

[0180] In a data forwarding method provided by an embodiment of the present application, the first information includes a first parameter. The first parameter is used to indicate the beam used by the forwarding unit to forward the data sent by the first network device.

[0181] In some embodiments, the first information sent by the first network device may include a first parameter. Among them, the first parameter can be used to indicate the beam used by the forwarding unit to forward the data sent by the first network device. For example, the first parameter may be a beam configuration parameter. For example, the first parameter may be embodied in ways such as a transmission configuration indicator (TCI) state, a quasi co-location (QCL) type D, or a sounding reference signal resource indicator (SRI).

[0182] In some examples, the first parameter can be obtained from a second parameter. The second parameter is used to indicate the beam used by the forwarding unit to forward the data sent by the second network device. That is to say, the beam used by the forwarding unit to forward the data sent by the first network device may have a certain relationship with the beam used to forward the data sent by the second network device.

[0183] In some examples, the first parameter may be the same as the second parameter. That is to say, when the forwarding unit forwards the data sent by the first network device, it may still use the beam used to forward the data sent by the second network device. For the terminal, it can receive the data of the first network device without changing the beam.

[0184] In other examples, the first network device may generate the first parameter based on the second parameter. That is to say, when generating the first parameter, the first network device refers to the second parameter. This makes the beam used by the forwarding unit to forward the data sent by the first network device have a certain correlation with the beam used by the forwarding unit to forward the data sent by the second network device. It can reduce the excessive change of the beam caused by handover, which is beneficial for the terminal to receive the data sent by the first network device based on the new beam.

[0185] In the embodiment of the present application, the beam used by the forwarding unit to forward the data sent by the first network device may have a certain correlation with the beam used by the forwarding unit to forward the data sent by the second network device, so as to reduce the problems caused by excessive beam changes due to changes in network devices, and improve the communication performance and user experience of the terminal.

[0186] In a data forwarding method provided in the embodiment of the present application, the first information further includes the cell identifier of the target cell, where the target cell is the cell to which the forwarding unit forwards the data of the first network device.

[0187] In some embodiments, the first information sent by the first network device may further include the cell identifier of the target cell. Wherein, the target cell may be the cell under the first network device corresponding to when the forwarding unit forwards the data of the first network device. In other words, the Fwd of the relay device forwards the data of the first network device, that is, forwards the data sent by the first network device on the target cell.

[0188] It can be understood that the first network device may correspond to one or more cells, and the target cell is one of the above one or more cells. The target cell may be determined by the first network device, or may be determined by the second network device after the relay device performs cell measurement on one or more cells under the first network device.

[0189] For example, the second network device may send information for cell measurement to the relay device, and the relay device performs cell measurement on one or more cells corresponding to the first network device based on this information to obtain cell measurement results corresponding to different cells. The relay device may report the cell measurement results corresponding to the one or more cells to the second network device, and the second network device selects a suitable cell as the target cell based on the cell measurement results corresponding to the one or more cells. Of course, the specific implementation process of selecting the target cell may be to select the one with the best measurement result as the target cell based on the cell measurement results, or to select a cell that meets the corresponding conditions according to some preset conditions. The specific implementation process can be adjusted according to the actual situation, and the embodiments of the present application do not make limitations.

[0190] In some embodiments, the identifier may be, for example, an identity (ID) or an index. For example, the cell identifier may be a cell ID.

[0191] In some embodiments, the cell identifier of the target cell may not be carried in the first information. In this case, the relay device may default to select the cell corresponding to the connection between its MT and the first network device as the cell for forwarding the data of the first network device.

[0192] The first information in the embodiments of the present application may further include the cell identifier of the target cell, so that the relay device can determine the target cell based on the cell identifier and forward the data of the target cell, improving the forwarding efficiency of the relay device.

[0193] In a data forwarding method provided by the embodiments of the present application, before obtaining the first information, the method may further include: sending second information. The second information is used to instruct the forwarding unit of the relay device to forward the data from the first network device.

[0194] In some embodiments, before obtaining the first information, the relay device may further send second information. Wherein, the second information is used to instruct the forwarding unit of the relay device to forward the data from the first network device.

[0195] For example, before the MT of the relay device obtains the first information sent by the first network device, it may further send second information to the second network device. The second information is used to instruct the relay device to forward the data from the first network device. Wherein, the relay device may be pre-configured with information indicating that the relay device is to forward the data from the first network device. That is to say, in this case, the relay device itself knows that it is to forward the data from the first network device, so the relay device can send the second information to the second network device through the MT.

[0196] In some examples, the second information may carry the network device identifier of the first network device, such as the gNB ID. And / or, the second information may carry the first IP address. The first IP address is used to indicate the first network device. The second network device can determine that the relay device is to forward the data from the first network device according to the second information.

[0197] It can be understood that the reason for the relay device to send the second information to the second network device is that the current state of the relay device is to forward the data from the second network device, which also indicates that there is a control link between the relay device and the second network device, enabling the interaction of information for control. Therefore, it can also be understood that the relay device can send the second information to the network device from which it is currently forwarding data.

[0198] The relay device in the embodiments of the present application can send the second information so that the network device receiving the second information can know that the relay device is to forward the data from the first network device. Thereby triggering the first network device to send the first information to the relay device, so as to achieve the purpose of the relay device forwarding the data from the first network device.

[0199] In a data forwarding method provided by the embodiments of the present application, before sending the second information, the method further includes: receiving seventh information from a third network device, and the seventh information is used to indicate the first network device.

[0200] In some embodiments, the third network device may be, for example, an OAM server. The OAM server is connected to the relay device. For example, the relay device may be connected to a core network device and communicate with the OAM server through the core network device. It can be understood that in the embodiments of the present application, it will be simply described that the relay device communicates with the OAM server.

[0201] In some embodiments, the OAM server may send seventh information to the relay device, and the seventh information is used to indicate the first network device. After receiving the seventh information, the relay device determines the first network device through the seventh information. Then the relay device determines to forward the data from the first network device. In some examples, after the relay device receives the seventh information, the relay device may also send second information to the second network device. The specific implementation process of sending the second information may refer to the description of the corresponding embodiments above, and will not be elaborated herein in the embodiments of the present application.

[0202] In the embodiments of the present application, the relay device may also determine to forward the data from the first network device according to the OAM configuration. The network devices that the relay device needs to forward can be configured more flexibly, improving the flexibility of the configuration.

[0203] In a data forwarding method provided in the embodiments of the present application, the method further includes: the control forwarding unit stops forwarding the data from the second network device.

[0204] In some embodiments, the MT of the relay device may control the Fwd of the relay device to stop forwarding the data from the second network device. For example, when the MT of the relay device receives the first information, it may determine that the Fwd of the relay device needs to forward the data from the first network device. However, the current state of the relay device is forwarding the data from the second network device. Then the MT of the relay device may control the Fwd of the relay device to stop forwarding the data from the second network device so that the Fwd of the relay device can forward the data from the first network device.

[0205] In some examples, the Fwd of the relay device may immediately stop forwarding the data from the second network device while determining to forward the data from the first network device. For another example, the Fwd of the relay device may also stop forwarding the data from the second network device within a preset time after determining the first information. For still another example, the Fwd of the relay device may stop forwarding the data from the second network device after a certain duration after determining the first information. The embodiments of the present application do not make specific limitations on when the Fwd of the relay device stops forwarding the data from the second network device.

[0206] It can be understood that, in order to ensure that the relay device can continuously forward data for the communication between the terminal and the second network device, generally, it is not considered to stop forwarding data from the second network device before forwarding data from the first network device. However, in some cases, it is allowed to first stop forwarding data from the second network device and then receive and forward data from the first network device. The embodiments of the present application do not make any limitations in this regard.

[0207] In some examples, considering that the beams used for forwarding data from different network devices are similar, interference may be generated. Or, in order to further reduce the power consumption of the relay device and avoid the situation of a large amount of resource consumption caused by simultaneously forwarding data from different network devices, it can be considered to stop forwarding data from the second network device.

[0208] The embodiments of the present application can control the forwarding unit to stop forwarding data from the second network device, so as to avoid the resource conflicts, signal interference, etc. that may be caused by the forwarding unit simultaneously forwarding data from different network devices in some scenarios. It can also reduce the power consumption of the relay device and the resource consumption in some scenarios.

[0209] In a data forwarding method provided by the embodiments of the present application, the method further includes: receiving third information, where the third information is used to instruct the forwarding unit to stop forwarding data from the second network device.

[0210] In some embodiments, the MT of the relay device can also receive the third information. The third information can be used to instruct the forwarding unit to stop forwarding data from the second network device.

[0211] For example, the MT of the relay device can receive the third information sent by the second network device. In this case, considering that there is still a control link between the relay device and the second network device, such as the second control link. Therefore, the second network device can send the third information to the MT of the relay device. The MT of the relay device receives the third information and controls the Fwd of the relay device to stop forwarding data from the second network device based on the third information.

[0212] For another example, the MT of the relay device can receive the third information sent by the first network device. In this case, considering that the connection between the relay device and the second network device may have been disconnected. Therefore, it is necessary for the first network device to send the third information so that the MT of the relay device can control the Fwd of the relay device to stop forwarding data from the second network device based on the third information.

[0213] In the embodiments of the present application, the network device can instruct the relay device to stop forwarding data from the second network device through the third information, so as to achieve flexible control of the data forwarding of the relay device.

[0214] In a data forwarding method provided by an embodiment of the present application, the forwarding unit includes a second logical forwarding unit. Controlling the forwarding unit to stop forwarding data from a second network device may include: controlling the second logical forwarding unit to stop forwarding data from the second network device.

[0215] In some embodiments, the Fwd of the relay device can be logically divided into a second logical Fwd. Then, for the MT of the relay device to control the Fwd of the relay device to stop forwarding data from the second network device, it may be to control the second logical Fwd to stop forwarding data from the second network device.

[0216] That is to say, the MT of the relay device can specifically control the corresponding logical Fwd to be turned off. For example, if the second logical Fwd is used to forward data from the second network device, the MT of the relay device can control the second logical Fwd to be turned off, that is, control the second logical Fwd to stop forwarding data from the second network device.

[0217] The embodiment of the present application can control the corresponding logical forwarding unit to stop forwarding data from the corresponding network device, thereby realizing the opening and closing of the logically independent control forwarding unit and improving the flexibility of the forwarding unit to forward data.

[0218] In a data forwarding method provided by an embodiment of the present application, the relay device is dual-connected to a first network device and a second network device. Among them, there is a first control link between the relay device and the first network device, and a second control link between the relay device and the second network device.

[0219] In some embodiments, the relay device can be dual-connected to a first network device and a second network device. In the dual-connection mode, there is a first control link between the relay device and the first network device, and a second control link between the relay device and the second network device.

[0220] For example Figure 9 as shown in a schematic diagram of a dual-connection scenario of a relay device. In Figure 9 the shown scenario, a dual-connection is established between the MT of the relay device and the first network device and the second network device, so that the two network devices can respectively control the Fwd of the relay device through their respective control links. Of course, specifically which network device controls the Fwd of the relay device can be determined through negotiation between the two network devices.

[0221] Among them, there is a first control link between the MT of the relay device and the first network device, corresponding to cell 1; there is a second control link between the MT of the relay device and the second network device, corresponding to cell 2. Among them, cells and component carriers (CCs) can be used interchangeably. That is, different CCs are considered different cells. A CC can also be referred to as a member carrier. It can be understood that since the relay device is connected to different network devices, the CCs under different network devices are very likely to belong to different cells. Therefore, CCs and cells can be used interchangeably. The Fwd of the relay device can also have a second backhaul link with the second network device. For example, if the relay device has a logical Fwd, the one with the second backhaul link to the second network device can be the second logical Fwd, that is, relay device - Fwd2.

[0222] It should be noted that in the embodiments of the present application, the backhaul link can be considered to exist after the relay device and the network device establish a connection. That is to say, this backhaul link can be transmitting data for forwarding, or it can temporarily not transmit data, that is, be in an idle state. Even if no data is transmitted on this backhaul link, it is still considered that the backhaul link exists. For example, if the Fwd of the relay device is within the coverage area of the network device and can amplify and forward the signal of the network device, it can be considered that the backhaul link exists.

[0223] Of course, it can also be considered that the backhaul link exists only when the network device sends data that needs to be forwarded to the relay device. In the case where the network device does not send data that needs to be forwarded to the relay device, it can be considered that the corresponding backhaul link does not exist.

[0224] The embodiments of the present application do not limit the determination of when the backhaul link exists as described above.

[0225] Through Figure 9 It can be seen that when the relay device hopes to be dual-connected to the second network device and the first network device, it switches the network device that needs to be forwarded, that is, switches from the forwarding path including the second backhaul link and the second access link to the forwarding path including the first backhaul link and the first access link. In other words, it switches from forwarding data from the second network device by the relay device to forwarding data from the first network device.

[0226] In some embodiments, a Figure 9 more specific data forwarding process in a scenario is provided. As Figure 10As shown, the forwarding process may involve a terminal, a first network device, a second network device, a relay device, and an OAM server. In some examples, the OAM server may be a remote OAM that supports a session based on a relay device protocol data unit (PDU). Alternatively, it may be a local OAM based on local direct connection. For example, the OAM server and the relay device are directly connected by a wired connection. It can be understood that the OAM server is optional and may not be involved in some cases. This is not limited in the embodiments of this application. The data forwarding process may be applicable to Figure 1 , Figure 9 the scenarios shown. It may include the following steps:

[0227] S201, the relay device initially accesses the first network device.

[0228] In some examples, the MT of the relay device may access the network from the first network device. This process may be considered as the initial access of the MT of the relay device. For example, the first network device may authenticate the relay device; the relay device connects to the OAM server, etc. Since the relay device has an MT, the process of the MT of the relay device accessing the network may refer to the process of an ordinary terminal accessing the network.

[0229] Among them, the authentication may be to determine whether the relay device has the permission to access the first network device. Of course, for the specific implementation process of S201, reference may be made to related technologies, and this is not elaborated in the embodiments of this application.

[0230] S202, the OAM server sends a first notification to the relay device.

[0231] In some examples, the OAM server may send a first notification to the relay device. This first notification may include, for example, the network device identifier of the second network device and / or the IP address of the second network device. In some examples, the relay device may receive the first notification sent by the OAM server.

[0232] Taking the case where the relay device is to forward data from the second network device as an example, the first notification may carry the identifier of the second network device. It is used to indicate that the relay device needs to forward data from the second network device.

[0233] In some examples, this first notification may also be pre-configured on the relay device, or in other words, the relay device may pre-store information indicating that the relay device forwards data from the second network device. In this case, S202 may not be executed, that is, S202 is an optional step.

[0234] S203, The relay device sends the first RRC information to the first network device.

[0235] In some examples, the relay device sends the first RRC information (message) to the first network device. For example, the first RRC information may include the network device identifier of the second network device, and / or the IP address of the second network device.

[0236] It can be considered that the purpose of the relay device sending the first RRC information is to let the first network device know that the relay device is going to forward data from the second network device. Of course, in some examples, the information indicating that the relay device is going to forward data from the second network device can also be pre-stored in the first network device. Therefore, S203 is also an optional step.

[0237] In some examples, the first network device can receive the first RRC information sent by the relay device.

[0238] S204, The first network device sends a secondary node addition request to the second network device.

[0239] In some examples, the first network device sends a secondary node addition request to the second network device. This request is used to request to establish the second network device as a secondary node (SN) of the relay device to establish a dual connection. In some examples, the second network device receives the secondary node addition request sent by the first network device.

[0240] For example, assuming the relay device is an NCR, NCR indication information can be carried in the secondary node addition request. It is used to indicate that the relay device is an NCR device.

[0241] For another example, optionally, the first network device may also send a forwarding network device indication information to the second network device, which is used to indicate whether the network device receiving this information is a forwarding network device of the NCR. That is, whether the second network device needs to control this NCR. Among them, the forwarding network device indication information may be a Fwd gNB indication.

[0242] For yet another example, optionally, the first network device may also send the cell identifier of the target cell to the second network device, and this cell identifier may also be referred to as the primary cell (Pcell) identifier. Such as the Pcell ID. It can be used for subsequent terminal handover.

[0243] Of course, the forwarded network device indication information and / or the cell identifier of the target cell mentioned above may be carried in the secondary station establishment request and sent, or may be sent using a new message. The embodiments of the present application do not make any limitations in this regard.

[0244] S205. The relay device establishes a dual connection with the first network device and the second network device.

[0245] In some examples, the relay device may establish a dual connection with the first network device and the second network device. Among them, the first network device can be regarded as the master node (MN) of the relay device. During the establishment of the dual connection, the second network device may send a secondary station establishment response to the first network device to reply to the secondary station establishment request in S204. It may also include operations such as the MT of the relay device initiating random access to the cell under the second network device and establishing an RRC connection. The specific implementation process may refer to the technologies related to dual connection, and the embodiments of the present application do not make any limitations in this regard.

[0246] S206. The relay device sends second RRC information to the second network device.

[0247] In some examples, the relay device sends second RRC information to the second network device. The second RRC information may be used to indicate that the relay device hopes that the second network device serves as its forwarding network device. For example, the second RRC information may include the network device identifier of the second network device and / or the IP address of the second network device.

[0248] It can be understood that S206 is an optional step. Considering that the first network device may have sent a forwarded network device indication to the second network device in S204. In the case where the forwarded network device indication has been sent in S204, S206 can be skipped and not executed.

[0249] In some examples, the second network device receives the second RRC information sent by the relay device.

[0250] S207. The second network device sends first-side control information to the relay device.

[0251] In some examples, the second network device may send first-side control information to the relay device. The first-side control information is used to configure the Fwd of the relay device so that the Fwd forwards data from the second network device. In some examples, the relay device receives the first-side control information sent by the second network device.

[0252] For example, the first-side control information may be related to the cell group configuration of the second network device. For instance, the first-side control information may include the cell identifiers of the cells that need to be forwarded under the second network device. Another example is that the first-side control information may include the beam information that the relay device may use when forwarding data from the second network device in Fwd mode.

[0253] It can be understood that the processes of S201 to S207 above can be simply described as follows: the relay device accesses the network and establishes the DC of the MT. And it establishes a backhaul link with one of the network devices. For example, the relay device establishes a second backhaul link with the second network device. This second backhaul link is used for the relay device to receive data from the second network device and forward the data to the terminal.

[0254] After S207, the relay device may have been operating stably for some time until the forwarding network device of the relay device is renegotiated among different network devices.

[0255] For the negotiation of the forwarding network device of the relay device among different network devices, the following three methods may be included. Method 1, that is, the relay device actively informs the network device that the network device it wants to forward has changed. Method 2, the second network device actively initiates a request to inform the first network device that the network device the relay device wants to forward has changed. Method 3, the first network device actively initiates a request to inform the second network device that the network device the relay device wants to forward has changed.

[0256] In some possible implementation manners, there may be two cases for Method 1. For example, in Method 1.1, the relay device actively informs the second network device that the network device it wants to forward has changed from the second network device to the first network device; another example is that in Method 1.2, the relay device actively informs the first network device that the network device it wants to forward has changed from the second network device to the first network device.

[0257] In some possible implementation manners, Method 1.1 may include the following steps:

[0258] S208, the OAM server sends the seventh information to the relay device.

[0259] In some examples, the OAM server sends the seventh information to the relay device. Among them, the seventh information may be similar to the first notification. The seventh information may carry the network device identifier of the first network device and / or the IP address of the first network device. It can be understood that the seventh information can indicate to the relay device that the network device it needs to serve is the first network device. In some examples, the relay device receives the seventh information sent by the OAM server.

[0260] Of course, S208 is an optional step. That is to say, the information indicating that the network device that the relay device needs to serve is the first network device can be pre-configured on the relay device. In this case, S208 does not need to be executed.

[0261] S209. The relay device sends second information to the second network device.

[0262] In some examples, the relay device sends second information to the second network device. The second information may be an RRC message for indicating that the network device that the relay device itself needs to forward is the first network device. For example, the second information may carry the network device identifier of the first network device and / or the IP address of the first network device.

[0263] Of course, S209 can also be considered an optional step, that is, the information indicating that the network device that the relay device needs to forward is the first network device can also be pre-configured on the second network device. In this case, S209 may not be executed, corresponding to the implementation process of Mode 2.

[0264] In some examples, the second network device receives the second information sent by the relay device.

[0265] S210. The second network device sends fifth information to the first network device.

[0266] In some examples, the second network device sends fifth information to the first network device. The fifth information may be used to request the first network device to forward data from the first network device through the relay device. In some examples, the first network device may receive the fifth information sent by the second network device.

[0267] For example, the fifth information may carry the identifier of the relay device. Specifically, the identifier of the relay device may be the identifier of the MT of the relay device. For example, it may be the Xn interface identifier of the MT, denoted as UE XnAP ID. The UE XnAP ID can be used to indicate a specific relay device. It can be understood that since a dual connection has been established between the relay device and the first network device and the second network device, it can be considered that the first network device and the second network device have exchanged Xn interface messages about the MT of the relay device. Therefore, a specific relay device can be indicated by the UE XnAP ID. Among them, the Xn interface is an interface used for interaction between different next-generation (NG) RAN nodes.

[0268] In some examples, the fifth information may also carry the configuration information of the relay device under the second network device. For example, it may include an access beam, a backhaul beam, etc. Among them, the access beam is used to represent the beam used by the relay device to forward data to the terminal. The backhaul beam represents the beam used by the relay device to receive data sent by the second network device.

[0269] S211, the first network device sends the fourth information to the second network device.

[0270] In some examples, the first network device may send the fourth information to the second network device. This fourth information can be regarded as a response to the fifth information, indicating that the first network device accepts the request of the relay device to forward data from the first network device. In some examples, the second network device may receive the fourth information sent by the first network device.

[0271] For example, the fourth information may carry the identifier of the relay device. For example, the UE XnAP ID is carried in the fourth information. Also for example, optionally, the fourth information may also carry the cell identifier of the target cell.

[0272] It can be simply understood that the solution corresponding to Method 1.1 is that the relay device triggers the second network device to request the relay device to forward data from the first network device.

[0273] In some possible implementation manners, Method 1.2 may include the following steps:

[0274] S220, the OAM server sends the seventh information to the relay device.

[0275] S221, the relay device sends the second information to the first network device.

[0276] In some examples, the relay device sends the second information to the first network device. In some examples, the first network device receives the second information sent by the relay device.

[0277] Of course, S221 can also be regarded as an optional step, that is, the information indicating that the network device to be forwarded by the relay device is the first network device can also be pre-configured on the first network device. In this case, S221 may not be executed, corresponding to the implementation process of Method 3.

[0278] S222, the first network device sends the fourth information to the second network device.

[0279] In some examples, the fourth information may be used to request the second network device to forward data from the first network device by the relay device. The cell identifier of the target cell to be forwarded by the relay device may be carried in the fourth information.

[0280] In some examples, the first network device sends fourth information to the second network device. This fourth information can be used to request the relay device to forward data from the first network device to the second network device. In some examples, the second network device may receive the fourth information sent by the first network device.

[0281] For example, the fourth information may carry the identifier of the relay device. Specifically, the identifier of the relay device may be the identifier of the MT of the relay device, such as the UE XnAP ID.

[0282] S223, the second network device sends fifth information to the first network device.

[0283] In some examples, the second network device may send fifth information to the first network device. This fifth information can be regarded as a response to the fourth information, indicating that the second network device accepts the request for the relay device to forward data from the first network device. In some examples, the first network device may receive the fifth information sent by the second network device.

[0284] For example, the identifier of the relay device may be carried in the fifth information. Such as the UE XnAP ID is carried in the fifth information. Also, as an option, the configuration information of the relay device under the second network device may further be carried in the fifth information. For example, it may include access beams, backhaul beams, etc.

[0285] It can be understood that the implementation process of step S220 is similar to that of S208, the implementation process of step S221 is similar to that of S209, the implementation process of step S222 is similar to that of S211, and the implementation process of step S223 is similar to that of S210. Specifically, reference may be made to the descriptions of the corresponding embodiments of S208 to S211, and the embodiments of the present application will not be elaborated herein.

[0286] It can be simply understood that the solution corresponding to Method 1.2 is that the relay device triggers the first network device to request the relay device to forward data from the first network device.

[0287] In some possible implementation manners, Method 2 may include the following steps:

[0288] S230, the second network device sends fifth information to the first network device.

[0289] S231, the first network device sends fourth information to the second network device.

[0290] It can be understood that the implementation process of step S230 is similar to that of S210, and the implementation process of step S231 is similar to that of S211. Specifically, reference may be made to the descriptions of the corresponding embodiments of S210 to S211. The embodiments of the present application will not be elaborated herein.

[0291] It can be understood that the difference between Mode 2 and Mode 1.1 is that the triggering condition for the second network device to send the fifth information is actively triggered by the second network device itself. That is to say, the second network device itself knows that the relay device is to forward data from the first network device, without the relay device sending the second information to inform.

[0292] In some possible implementation manners, Mode 3 may include the following steps:

[0293] S240, the first network device sends the fourth information to the second network device.

[0294] S241, the second network device sends the fifth information to the first network device.

[0295] It can be understood that the implementation process of step S240 is similar to that of S222, and the implementation process of step S241 is similar to that of S223. For details, reference can be made to the descriptions of the corresponding embodiments of S222 to S223. The embodiments of the present application will not be elaborated herein.

[0296] It can be understood that the difference between Mode 3 and Mode 1.2 is that the triggering condition for the first network device to send the fourth information is actively triggered by the first network device itself. That is to say, the first network device itself knows that the relay device is to forward data from the first network device, without the relay device sending the second information to inform.

[0297] It should be noted that in Mode 1.2 and Mode 3, the fourth information may be a request message for requesting the relay device to forward data from the first network device. The fifth information may be a response message to the fourth information. In Mode 1.1 and Mode 2, the fifth information may be a request message for requesting the relay device to forward data from the first network device. The fourth information may be a response message to the fifth information.

[0298] It can be understood that the processes of S208 to S211, S220 to S223, S230 to S231, and S240 to S241 above can be simply described as that the first network device and the second network device negotiate to change the service network device of the relay device. That is, they negotiate to change the network device that the relay device is to forward.

[0299] It can be understood that the process of the first network device and the second network device negotiating to change the service network device of the relay device Figure 10 only shows S208 to S211, that is, Mode 1.1. However, it should be understood that S208 to S211 can also be equivalently replaced by S220 to S223, S230 to S231, or S240 to S241. The embodiments of the present application do not make limitations.

[0300] Regarding the process of negotiating and changing the serving network device of the relay device between the first network device and the second network device above, from the perspective of the second network device, it can also be considered that this negotiation process is used to trigger the first network device to generate the first information.

[0301] S212. The first network device generates the first information.

[0302] In some examples, the first network device can generate the first information. For example, generate a beam configuration. This beam configuration can be, for example, the first parameter mentioned in the foregoing embodiments.

[0303] In some examples, considering that the experience of the terminal is kept unchanged as much as possible, the first parameter can be generated based on the second parameter. Wherein, the second parameter is the one mentioned in the foregoing embodiments and can include the beam used to forward the data from the second network device. For example, the first parameter can be the same as the second parameter, that is, the beam configuration remains consistent and unchanged.

[0304] In some examples, the second parameter can be carried by the sixth information. For example, the second network device sends the sixth information carrying the second parameter to the first network device. In some examples, the sixth information can be multiplexed with the fifth information, that is, the sixth information is carried by the fifth information, or the second parameter is directly carried in the fifth information. The embodiments of the present application do not make limitations.

[0305] S213. The first network device sends the first information to the relay device.

[0306] In some examples, the first network device can send the first information generated in S212 to the relay device. The relay device can receive the first information sent by the first network device. For example, the first information can be side control information different from the first-side control information.

[0307] S214. The relay device generates the first logical Fwd.

[0308] In some examples, the relay device can generate a new logical Fwd, such as the first logical Fwd. It can be considered that the original Fwd used to forward the data from the second network device is the second logical Fwd. The relay device can use the first logical Fwd to forward the data from the first network device. For example, the relay device can simultaneously use the first logical Fwd to forward the data from the first network device and use the second logical Fwd to forward the data from the second network device.

[0309] Wherein, S214 is an optional step. That is, the relay device can also not generate the logical Fwd. The Fwd of this relay device can be used as a whole, both for forwarding the data from the first network device and for forwarding the data from the second network device.

[0310] It can be understood that the processes of S211 to S214 above can be simply described as that the first network device sends new configuration information so that the relay device can forward data from the first network device.

[0311] S215. The first network device sends first interface information to the second network device.

[0312] In some examples, the first network device can send first interface information to the second network device. This first interface information can be used to notify the second network device that the Fwd of the relay device can already forward data from the first network device according to the new configuration, and terminal handover can be performed. Among them, the identity of the relay device, such as UE XnAP ID, can be carried in the first interface information. In some examples, the second network device can receive the first interface information sent by the first network device.

[0313] In some examples, the first interface information can also carry the cell identity of the target cell, and / or the beam correspondence between the Fwd of the relay device for forwarding the first network device and the second network device. For example, it can include the correspondence of the access beam between the first network device and the second network device, and / or the correspondence of the backhaul beam between the first network device and the second network device. In some examples, this correspondence can also be understood as the correspondence between the first parameter and the second parameter.

[0314] In some examples, the first interface information can be Xn interface information.

[0315] The above-mentioned cell identity of the target cell and the beam correspondence can be used for the second network device to directly obtain the cell identity of the target cell and the target beam of the terminal without waiting for the measurement report of the terminal. Thus, the terminal handover can be accelerated. It can be understood that this handover is not caused by the mobility of the terminal, but because the relay device needs to change the forwarded cell. Therefore, the new configuration adopted by the relay device, that is, the first parameter can be generated based on the second parameter. There can be a correspondence between the first parameter and the second parameter. The second network device can directly determine the target cell and the target beam of the terminal based on this correspondence without the terminal having to perform cell measurement, beam measurement, etc.

[0316] Of course, S215 can be an optional step. For example, after negotiating and determining between network devices to change the network device to be forwarded by the relay device, the second network device directly performs terminal handover after a period of time based on the corresponding implementation.

[0317] S216. The second network device sends a terminal handover request to the first network device.

[0318] In some examples, the second network device sends a terminal handover request to the first network device, and this terminal handover request may be denoted as HANDOVER REQUEST. In some examples, the first network device may receive the terminal handover request sent by the second network device. Among them, the terminal handover request may include information for indicating the target cell. The target cell may be determined based on the PCell ID in S204, or may be determined based on the cell identifier of the target cell carried in the fourth information in S230.

[0319] In some examples, the terminal handover request may further include information indicating the target beam to be used after the terminal handover. The target beam may be determined according to the beam correspondence relationship mentioned in S215. The target beam may correspond to the first logical Fwd.

[0320] S217. The first network device sends a handover request response to the second network device.

[0321] In some examples, the first network device sends a handover request response to the second network device, that is, the response information corresponding to the terminal handover request. In some examples, the second network device receives the handover request response sent by the first network device. For example, the handover request response may be denoted as HANDOVER REQUEST ACK.

[0322] It can be understood that S216 and S217 may be optional steps. That is to say, after a certain preset time after S213, the terminal handover can be directly performed, and the embodiments of the present application do not make any limitations here.

[0323] S218. Perform the terminal handover.

[0324] In some examples, the handover of the terminal is performed. The specific implementation process may refer to the related art, and the embodiments of the present application will not elaborate here.

[0325] Of course, S218 may be an optional step. For example, after the relay device receives the first information, if there is no data that needs to be sent from the first network device to the terminal for the time being, there is no need for the terminal to receive data from the first network device for the time being. Therefore, the terminal may not perform the handover either. For example, the terminal handover is performed until the terminal needs to perform data interaction with the first network device, so that the terminal can receive the data from the first network device forwarded by the relay device.

[0326] S219. The second network device sends the third information to the relay device.

[0327] In some examples, the second network device may send the third information to the relay device. The third information may be used to stop the relay device from forwarding the data from the second network device.

[0328] For example, if the Fwd of the relay device includes a second logical Fwd, the third information may be used to close the second logical Fwd. Closing the second logical Fwd means controlling to stop forwarding data from the second network device.

[0329] Of course, S219 may be an optional step, that is, the relay device may determine by itself to stop forwarding data from the second network device. For example, while forwarding data from the first network device, stop forwarding data from the second network device. Or, after a period of time of forwarding data from the first network device, or after a period of time of receiving the first information, then stop forwarding data from the second network device. The embodiments of the present application do not limit when the relay device stops forwarding data from the second network device.

[0330] It can be understood that the processes of S211 to S214 above can be simply described as that the terminal performs a handover. After the terminal handover, the relay device stops forwarding data from the second network device.

[0331] For Figure 10 the specific implementation processes of the steps in Figure 8 reference may also be made to the descriptions of the corresponding embodiments in

[0332] In Figure 9 and Figure 10 In the described solution, the relay device always maintains a dual connection of the control link with two network devices, the MT of the relay device does not need to be switched, and both network devices always have the ability to control the relay device. Therefore, through negotiation between the two network devices, the first information is sent by the forwarding network device desired by the relay device. For the case where the relay device establishes a dual connection, it may mean that the relay device is located at the junction of the control ranges of the two network devices, so the need to change the forwarding network device is considered.

[0333] The embodiments of the present application can, in the scenario of the relay device's dual connection, not interrupt the service of the relay device and can change the forwarding network device of the relay device. There is no need to release the MT of the relay device to the IDLE state or the INACTIVE state. The communication performance and service experience of the terminal under the relay device are improved.

[0334] In a data forwarding method provided by an embodiment of the present application, there is a second control link and a second backhaul link between the relay device and the second network device. Before obtaining the first information, control the mobile terminal unit of the relay device to perform a cell handover or redirection to obtain a first control link between the relay device and the first network device; obtaining the first information includes: obtaining the first information through the first control link.

[0335] In some embodiments, there may be a second control link and a second backhaul link between the relay device and the second network device. That is, the relay device is connected to the second network device and forwards data from the second network device.

[0336] In some embodiments, the relay device is only connected to one network device. Therefore, before receiving the first information, the relay device can establish a connection with the first network device through cell handover, redirection, etc., that is, establish a first control link. The relay device can receive the first information through this first control link. The first network device can send the first information through the first control link.

[0337] For example Figure 11 A schematic diagram of a single-connection scenario of a relay device is shown. In Figure 11 In the shown scenario, a connection is established between the MT of the relay device and the second network device, so that the second network device can control the Fwd of the relay device through the second control link respectively. Among them, the second control link between the MT of the relay device and the second network device can correspond to cell 2. There may also be a second backhaul link between the Fwd of the relay device and the second network device for the relay device to receive data from the second network device, and this data is the data that the relay device needs to forward.

[0338] The relay device can switch the network device it is connected to, that is, switch to the first network device. When the relay device switches to the first network device, since the relay device is single-connected to the network device, through Figure 11 it can be seen that the second control link is switched to the first control link, corresponding to cell 1. The second backhaul link is switched to the first backhaul link. For the access link between the relay device and the terminal, it is also switched from the second access link to the first access link.

[0339] For example, if the relay device has a logical Fwd, the one with the second backhaul link to the second network device can be the second logical Fwd, that is, relay device - Fwd2. After the network device is switched, the one with the first backhaul link between the relay device and the first network device can be the first logical Fwd, that is, relay device - Fwd1. Therefore, it can also be understood that the relay device is switched from relay device - Fwd2 to relay device - Fwd1.

[0340] In some embodiments, a more specific data forwarding process in the Figure 11 scenario is provided. As Figure 12 shown, this forwarding process may involve a terminal, a first network device, a second network device, a relay device, and an OAM server. The devices involved above may be similar to the devices in the Figure 10 corresponding embodiments, and will not be elaborated in the embodiments of the present application. This data forwarding process can be applied toFigure 1 , Figure 11 The scenarios shown. The following steps may be included:

[0341] S301, The relay device initially accesses the second network device.

[0342] In some examples, the MT of the relay device can access the network from the second network device.

[0343] It can be understood that the implementation process of S301 is similar to that of S201, except that the initially accessed network device is different. For details, reference can be made to the description of the corresponding embodiment of S201, and the embodiments of the present application will not be elaborated here.

[0344] S302, The OAM server sends a first notification to the relay device.

[0345] It can be understood that the implementation process of S302 is similar to that of S202. For the specific implementation process, reference can be made to the description of the corresponding embodiment of S202, and the embodiments of the present application will not be elaborated here.

[0346] S303, The relay device sends second RRC information to the second network device.

[0347] In some examples, the relay device sends second RRC information to the second network device. For example, the second RRC information may include the network device identifier of the second network device and / or the IP address of the second network device.

[0348] It can be understood that the implementation process of S303 is similar to that of S203, except that the network device receiving the RRC information is different. For the specific implementation process, reference can be made to the description of the corresponding embodiment of S203, and the embodiments of the present application will not be elaborated here.

[0349] S304, The second network device sends first side control information to the relay device.

[0350] S305, The OAM server sends seventh information to the relay device.

[0351] S306, The relay device sends second information to the second network device.

[0352] S307, The second network device sends fifth information to the first network device.

[0353] S308, The first network device sends fourth information to the second network device.

[0354] It can be understood that the implementation process of S304 is similar to that of S207, the implementation process of S305 is similar to that of S208 and S220, the implementation process of S306 is similar to that of S209 and S221, the implementation process of S307 is similar to that of S210, S223, S230, and S241, and the implementation process of S308 is similar to that of S211, S222, S231, and S240. For the specific implementation process, reference can be made to Figure 10 the description of the corresponding embodiments of the corresponding steps in this application, and the embodiments of this application will not be elaborated herein.

[0355] It should be noted that in Figure 12 the scenario shown, for the forwarding network device of the relay device negotiated between network devices, in modes 1.2 and 3, when the first network device sends the fourth information, the identifier of the relay device is not carried. The reason is that since the first network device has not yet connected to the relay device at this time, the first network device is not aware of the existence of the relay device and is also not aware of the existence of the MT of the relay device. The first network device can only attempt to request a relay device from the second network device. It cannot request a specific relay device.

[0356] After the forwarding network device of the relay device is negotiated and determined between the first network device and the second network device, the relay device can switch the network device to be established by means of cell handover or redirection. Among them, the redirection mentioned in the embodiments of this application can be understood as the redirection of the cell. In some possible implementation manners, the method of performing cell handover may include the following steps:

[0357] S309, the second network device sends a relay device handover request to the first network device.

[0358] In some examples, the second network device may send a relay device handover request to the first network device, and this request may be for the network device handover of the MT of the relay device. It can be denoted as the HANDOVER REQUEST of the MT. For example, assuming that the relay device is NCR, the relay device handover request may carry NCR indication information and / or NCR authorized indication information. It is used to indicate that the relay device is an NCR and / or an authorized NCR.

[0359] In some examples, before S309, the second network device may configure a measurement object for the MT of the relay device. The second network device will send down the measurement configuration for the MT of the relay device. For example, the second network device configures the cell beam under the first network device for the measurement object of the MT of the relay device according to the network device negotiation process.

[0360] In some examples, the first network device receives a relay device handover request sent by the second network device.

[0361] S310. The first network device sends a relay device handover request response to the second network device.

[0362] In some examples, the first network device sends a relay device handover request response to the second network device as the response information for the relay device handover request involved in S309. In some examples, the second network device may receive the relay device handover request response sent by the first network device.

[0363] For example, the relay device handover request response may be a HANDOVER REQUEST ACK of the MT.

[0364] In some possible implementation manners, when the network devices negotiate the manner 2 of the forwarding network device of the relay device, the fifth information may reuse S309, and the fourth information may reuse S310.

[0365] S311. The MT of the relay device performs network device handover.

[0366] In some examples, the MT of the relay device may perform network device handover. For example, the MT of the relay device switches to a cell under the first network device.

[0367] In some examples, the MT of the relay device may receive the eighth information through the second control link. The eighth information may be, for example, an RRCRelease. The eighth information may be used to indicate that the MT switches to a cell under the first network device. The MT of the relay device may switch to a cell under the first network device according to the eighth information.

[0368] It can be understood that the specific implementation processes of S309 to S311 may also refer to related technologies, and are not described in detail in the embodiments of this application.

[0369] In some possible implementation manners, the manner of performing redirection may include the following steps, for example:

[0370] S312. The second network device sends an RRC redirection request to the relay device.

[0371] In some examples, the second network device may send an RRC redirection request to the relay device. The RRC redirection request may be an RRCRelease related to redirection. It can be understood that the RRC redirection request is mainly used to release the MT of the relay device to the RRC_IDLE state or the RRC_INACTIVE state, and to indicate the MT of the relay device to reselect to a cell under the first network device.

[0372] In some examples, the relay device may receive the eighth piece of information through the second control link. In the redirection scenario, the eighth piece of information may be used to indicate that after the MT of the relay device is redirected to the cell under the first network device, the MT of the relay device initiates the establishment of an RRC connection to the first network device.

[0373] In some examples, the eighth piece of information may be carried in the RRC redirection request.

[0374] S313, the relay device reselects to the cell under the first network device.

[0375] In some examples, the relay device may perform cell reselection according to the RRC redirection request, for example, reselect to the cell under the first network device.

[0376] S314, the relay device makes an RRC connection to the first network device.

[0377] In some examples, the relay device initiates an RRC connection to the first network device. For example, the relay device may initiate an RRC connection through RRCResume or RRCSetupRequest to establish an RRC connection between the MT of the relay device and the first network device.

[0378] It can be understood that the specific implementation processes of S309 to S311 can also refer to related technologies, and are not elaborated herein in the embodiments of the present application.

[0379] In some embodiments, whether it is the method of cell handover for S309 to S311 or the method of redirection for S309 to S311, during the period of implementing the handover of the network device to which the relay device is connected, the Fwd of the relay device can continue to forward data from the second network device. That is to say, the Fwd of the relay device remains in the working state and is not turned off.

[0380] For example, during the period when the MT of the relay device is switched to another cell, or is released to the RRC_IDLE state or the RRC_INACTIVE state, or reselected to another cell, the Fwd of the relay device continues to forward the signal of the source cell according to the original configuration, that is, the data of the second network device.

[0381] The embodiments of the present application can ensure that the services of the terminal will not be interrupted and improve the user experience.

[0382] S315, the first network device generates the first piece of information.

[0383] S316, the first network device sends the first piece of information to the relay device.

[0384] S317, the relay device generates the first logical Fwd.

[0385] S318, the first network device sends first interface information to the second network device.

[0386] S319, the second network device sends a terminal handover request to the first network device.

[0387] S320, the first network device sends a handover request response to the second network device.

[0388] S321, perform terminal handover.

[0389] This process can be considered as the terminal handing over from the cell under the second network device to the cell under the first network device. It can also be considered as switching from the second logical Fwd to the first logical Fwd, that is, switching from relay device - Fwd2 to relay device - Fwd1.

[0390] It can be understood that the implementation process of S315 is similar to that of S212, the implementation process of S316 is similar to that of S213, the implementation process of S317 is similar to that of S214, the implementation process of S318 is similar to that of S215, the implementation process of S319 is similar to that of S216, the implementation process of S320 is similar to that of S217, and the implementation process of S321 is similar to that of S218. For the specific implementation process, reference can be made to Figure 10 the description of the corresponding embodiments in the corresponding steps, which will not be elaborated in the embodiments of the present application.

[0391] S322, the first network device sends third information to the relay device.

[0392] In some examples, the first network device may send third information to the relay device. This third information can be used to stop the relay device from forwarding data from the second network device.

[0393] For example, in the case where the relay device generates a logical Fwd, the third information may carry the network device identifier of the second network device and / or the identifier of the second logical Fwd. To indicate which part of the forwarding the relay device should stop. Considering the case of dual connection between the relay device and the network device, it can be determined which network device's data to stop forwarding by receiving the third information sent by which network device. For the case of single connection of the relay device, corresponding identifiers are required to indicate which part of the forwarding the relay device should stop.

[0394] It can be understood that the implementation process of S322 is similar to that of S219, except that the network device sending the third information is different. In Figure 12In the scenario corresponding to the local method, since the relay device has switched the network device it is connected to, it is impossible to instruct the relay device to stop forwarding data from the second network device through the second network device. It is necessary to receive the third information through the first control link with the first network device to instruct the relay device to stop forwarding data from the second network device. The specific implementation process can refer to the description of the corresponding embodiment of S219, which will not be elaborated in this embodiment of the present application.

[0395] In Figure 11 、 Figure 12 The described solution can be simply described as follows: when the relay device switches or redirects from the second network device to the first network device, the control of the relay device is changed from being controlled by the second network device to being controlled by the first network device, and it is required that the relay device continues to forward the signal under the second network device during the migration. This process does not require the relay device to introduce the support ability of dual connection. It only needs to be specified that after the relay device is redirected or cell-switched to other network devices, Fwd is not closed and continues to forward the signal of the source network device. Of course, the switching ability may need to be introduced.

[0396] The embodiment of the present application can not interrupt the service of the relay device when the relay device switches the network device it is connected to. And it can change the forwarding network device of the relay device, improving the communication performance and service experience of the terminal.

[0397] In a data forwarding method provided by an embodiment of the present application, there is a second control link between the relay device and the second network device. Obtaining the first information includes: obtaining the first information through the second control link.

[0398] In some embodiments, there may be a second control link and a second backhaul link between the relay device and the second network device. That is, the relay device is connected to the second network device and forwards data from the second network device.

[0399] In some embodiments, the method may further include: obtaining the first backhaul link between the relay device and the first network device based on the first information.

[0400] In some embodiments, the network device controlling the relay device may not be changed. That is, the control link is not changed. For example Figure 13 As shown, the relay device realizes the switching of the network device by changing the backhaul link. That is to say, the network device controlling the relay device remains unchanged, and the network device that the relay device needs to forward is switched. Referring to Figure 13 In, the second control link remains unchanged, and the second backhaul link is switched to the first backhaul link. For the access link between the relay device and the terminal, it is switched from the second access link to the first access link.

[0401] AndFigure 11 Similarly, if the relay device has logic Fwd, it can be considered that the relay device switches from Relay Device - Fwd2 to Relay Device - Fwd1.

[0402] In some embodiments, a more specific data forwarding process in a scenario is provided. Figure 13 As shown in Figure 14 , this forwarding process may involve a terminal, a first network device, a second network device, a relay device, and an OAM server. The devices involved above may be similar to the respective devices in the Figure 10 , Figure 12 corresponding embodiments, and will not be elaborated in the embodiments of the present application. This data forwarding process may be applicable to the scenarios shown in Figure 1 , Figure 13 . It may include the following steps:

[0403] S401, The relay device initially accesses the second network device.

[0404] S402, The OAM server sends a first notification to the relay device.

[0405] S403, The relay device sends second RRC information to the second network device.

[0406] S404, The second network device sends first side control information to the relay device.

[0407] In some embodiments, S404 may be an optional step. In the case where S404 is not executed, the relay device may receive first information in a non - first state. So that the Fwd of the relay device forwards data from the first network device.

[0408] S405, The OAM server sends seventh information to the relay device.

[0409] S406, The relay device sends second information to the second network device.

[0410] S407, The second network device sends fifth information to the first network device.

[0411] S408, The first network device sends fourth information to the second network device.

[0412] It can be understood that the implementation process of S401 is similar to that of S301, the implementation process of S402 is similar to that of S302, the implementation process of S403 is similar to that of S303, the implementation process of S404 is similar to that of S304, the implementation process of S405 is similar to that of S305, the implementation process of S406 is similar to that of S306, the implementation process of S407 is similar to that of S307, and the implementation process of S408 is similar to that of S308. The specific implementation process can refer to Figure 12For the description of the embodiments corresponding to the corresponding steps in [reference document], the embodiments of the present application will not be elaborated here.

[0413] S409, The first network device generates first information.

[0414] It can be understood that the implementation process of S409 is similar to that of S212. The specific implementation process can refer to Figure 10 For the description of the embodiments corresponding to the corresponding steps in [reference document], the embodiments of the present application will not be elaborated here.

[0415] S410, The first network device sends second interface information to the second network device.

[0416] In some examples, the first network device can send second interface information to the second network device. The second interface information is used to forward the first parameter sent by the first network device to the relay device. For example, the first parameter can be sent through side control information. The second interface information can carry the identifier of the relay device. For example, the second interface information can also carry the first parameter generated by the first network device. For example, cellgroupconfig information. In the case where the relay device generates the first logical Fwd, the cellgroupconfig information can be for the first logical Fwd.

[0417] In some examples, the second interface information can be Xn interface information.

[0418] For example, the second interface information can also carry the cell identifier of the target cell, and / or the correspondence relationship of the backhaul beam between the first network device and the second network device.

[0419] In some examples, the second network device can receive the second interface information sent by the first network device.

[0420] S411, The second network device sends the first information to the relay device.

[0421] In some examples, the second network device sends the first information to the relay device. For example, the second network device can forward the first parameter received in S410 to the relay device. For example, the first information can carry the network device identifier of the first network device, and / or the identifier of the first logical Fwd. To indicate that the first information is related to the first network device, used to control data forwarding under the first network device, or can be considered as regarding the first logical Fwd.

[0422] S412, The relay device generates the first logical Fwd.

[0423] S413, The second network device sends a terminal handover request to the first network device.

[0424] S414, The first network device sends a handover request response to the second network device.

[0425] Among them, the terminal handover request may include a target cell, and the target cell can be determined by the cell identifier of the target cell in the second interface information, without being measured by the relay device. Of course, the terminal handover request may also include a target beam, for example, determined by the corresponding relationship of the backhaul beam between the first network device and the second network device in the second interface information.

[0426] S415, Perform terminal handover.

[0427] S416, The second network device sends third information to the relay device.

[0428] It can be understood that the implementation process of S412 is similar to that of S214, the implementation process of S413 is similar to that of S216, the implementation process of S414 is similar to that of S217, the implementation process of S415 is similar to that of S218, and the implementation process of S416 is similar to that of S219. For the specific implementation process, reference can be made to the description of the corresponding embodiments in Figure 10 , and the embodiments of the present application will not be elaborated herein.

[0429] For Figure 13 the scenario shown, after the relay device switches to the first network device, it can work stably for a period of time and forward data from the first network device. Of course, the relay device can also switch back to the second network device again, for example Figure 15 as shown. Similar to Figure 13 , the difference is that Figure 15 the relay device in

[0430] switches back from the first network device to the second network device again. Figure 16 Therefore, as

[0431] shown, the method may further include the following steps:

[0432] S501, The OAM server sends seventh information to the relay device.

[0433] In some examples, the relay device may send tenth information to the first network device. The tenth information may be used to indicate that the relay device is to forward data from the second network device. For example, the tenth information may carry the device identifier of the second network device and / or the IP address of the second network device.

[0434] S503, The first network device sends fourth information to the second network device.

[0435] S504, The second network device sends fifth information to the first network device.

[0436] S505, the second network device sends first-side control information to the relay device.

[0437] It can be understood that the implementation process of S501 is similar to that of S208, the implementation process of S503 is similar to that of S211, S221, and S230, the implementation process of S504 is similar to that of S210, S220, and S231, and the implementation process of S505 is similar to that of S207. For the specific implementation process, reference can be made to Figure 10 the description of the corresponding embodiments of the corresponding steps in, and the embodiments of the present application will not be elaborated herein.

[0438] S506, the relay device generates a second logical Fwd.

[0439] It can be understood that S507 is similar to S214, except that the generated logical Fwd is used to forward data from the second network device. Of course, if the relay device has generated a second logical Fwd before, it can also be considered that the relay device re-opens or enables the second logical Fwd.

[0440] S507, the first network device sends a terminal handover request to the second network device.

[0441] S508, the second network device sends a handover request response to the first network device.

[0442] It can be understood that S507 is similar to S216, except that the sending device and the receiving device are swapped. Similarly, S507 is similar to S217, except that the sending device and the receiving device are swapped.

[0443] S509, perform terminal handover.

[0444] S510, the second network device sends the eleventh information to the relay device.

[0445] In some examples, the eleventh information is used to instruct the relay device to stop forwarding data from the first network device.

[0446] It can be understood that the implementation process of S506 is similar to that of S214, the implementation process of S507 is similar to that of S216, the implementation process of S508 is similar to that of S217, the implementation process of S509 is similar to that of S218, and the implementation process of S510 is similar to that of S219. For the specific implementation process, reference can be made to Figure 10 the description of the corresponding embodiments of the corresponding steps in, and the embodiments of the present application will not be elaborated herein.

[0447] In Figures 13 to 16In the described solution, there is no need to introduce the handover or dual connection of relay devices. The target network device, i.e., the first network device, can forward through the source network device, i.e., the second network device, and send control information, i.e., the first information, to the relay device. During this period, the control network device of the relay device is always the second network device. In this case, when the second network device sends control information to the relay device, such as the first information, it is necessary to indicate which network device the information is about, or which logical Fwd it is about.

[0448] The embodiments of the present application can allow the network device controlling the relay device to be different from the network device for forwarding signals. And it can change the forwarding network device of the relay device without interrupting the service of the relay device, and at the same time, there is no need to change the connection relationship of the MT of the relay device. Without interrupting the service of the relay device, the communication performance and service experience of the terminal are improved.

[0449] In a data forwarding method provided by an embodiment of the present application, the method further includes: when the public land mobile network (PLMN) supported or selected by the mobile terminal unit of the relay device is different from the PLMN corresponding to the terminal served by the relay device, receiving a ninth piece of information through a first backhaul link between the relay device and the first network device, where the ninth piece of information is used to instruct the terminal to perform beam switching, RRC release, or cell handover, and the terminal receives the data forwarded by the relay device.

[0450] In some embodiments, the PLMN supported or selected by the MT of the relay device may be different from the PLMN of the terminal served by the relay device. Among them, the terminal served by the relay device is the terminal that receives the data forwarded by the relay device. In this case, the first network device may send a ninth piece of information. The ninth piece of information can be used to instruct the terminal to perform beam switching, RRC release, or cell handover. The relay device forwards it to the terminal through Fwd, so that the terminal performs beam switching, RRC release, or cell handover according to the ninth piece of information, thereby avoiding the terminal receiving the data sent by the network device through the relay device. That is, avoiding the relay device from forwarding the data of the network device to the terminal.

[0451] In some examples, considering the mobility of the relay device, there may be a scenario of a mobile relay device. Taking the relay device as NCR as an example, the mobility of NCR will bring the following problems. For example, when NCR moves to a cell shared by multiple operators, such a cell can be called a RAN sharing cell. And NCR may be purchased by a certain operator, and this operator does not want the NCR to be used by the terminals of other operators. Among them, there is an association relationship between the operator and the PLMN, that is, different operators can be distinguished through the PLMN.

[0452] For NCR, the function of Fwd is to forward physical layer signals and it cannot distinguish the PLMN information of terminals. NCR itself will provide services to all terminals without discrimination. Therefore, it can be configured through network devices. In related technologies, the mobility of NCR is not considered, so it is considered that NCR is only deployed in specific cells and the above problems will not occur. When considering the mobility of NCR, there are some cases where it is necessary to restrict that only terminals of certain PLMNs can enjoy the extended coverage service provided by this NCR.

[0453] Obviously, when NCR moves to a RAN shared cell, for the terminals within the coverage of this NCR, how to enable only terminals of some PLMNs to enjoy the services of NCR is also a problem that needs to be solved.

[0454] In some examples, the network device can determine one or more PLMNs allowed to be served by this relay device according to the RRC message sent by the MT of the relay device after handover, such as the PLMN selected by the MT of the relay device carried in the RRCSetupComplete message, or the list of PLMNs supported by the MT of the relay device. Then, the network device can determine whether to send the ninth information according to the PLMN information selected by the terminal and based on the implementation to determine whether the terminal is within the coverage of NCR. Among them, the PLMN information selected by the terminal can be the PLMN selected by the terminal itself reported through the RRCSetupComplete message when establishing an RRC connection with this network device when the terminal accesses the network from the network device or when switching from other network devices to this network device. The specific implementation process can refer to related technologies and will not be elaborated in the embodiments of this application.

[0455] For the terminals within the coverage of the relay device, the PLMN they select is different from the PLMN selected by the relay device or does not belong to any PLMN in the list of PLMNs supported by the relay device. Then the network device can consider that the terminal cannot use the services of this NCR. The network device can send the ninth information to the terminal, for example, forward it through NCR-Fwd. The ninth information can be, for example, an RRC message. It can be used for the terminal to perform beam switching, RRC release, cell handover, etc., so that the terminal does not use the services of this relay device.

[0456] For example, if the ninth information is used for the terminal to perform beam switching, the target beam for switching does not belong to this relay device and other relay devices that do not support serving the PLMN selected by the terminal.

[0457] For another example, if the ninth piece of information is used for the terminal to perform RRC release, the target carrier for rejecting access or the target carrier for allowing redirection can be indicated in the ninth piece of information. The target carrier for rejecting access may include the carriers under this relay device and the carriers of other relay devices that do not support the PLMN service selected for the terminal. The target carrier for allowing redirection does not include the carriers under this relay device and the carriers of other relay devices that do not support the PLMN service selected for the terminal.

[0458] For yet another example, if the ninth piece of information is used for the terminal to perform cell handover, the measurement objects configured for the terminal may not include the beams under the relay devices in the neighboring cells that do not support the PLMN service selected for the terminal. For example, it can be reflected by configuring the synchronization signal and physical broadcast channel block (SSB) and / or the channel state information-reference signal (CSI-RS).

[0459] The embodiments of the present application can enable some specific terminals to use the services of relay devices, thereby achieving flexible configuration of relay devices.

[0460] In the embodiments of the present application, in the case where the relay device stops forwarding data from a certain network device, it can also be considered that the relay device disconnects the backhaul link with the network device. Similarly, if the relay device disconnects the connection with a certain network device, it can also be considered that the relay device disconnects the control link with the network device. Of course, for the handover of the access link between the relay device and the terminal, it can also be considered that the source access link is disconnected.

[0461] It should be noted that the above-mentioned multiple embodiments can be combined and the combined solutions can be implemented. Optionally, some operations in the processes of the method embodiments are optionally combined, and / or the order of some operations is optionally changed. And, the execution order between the steps of each process is only exemplary and does not constitute a limitation on the execution order between the steps. There can also be other execution orders between the steps. It is not intended to indicate that the execution order is the only order in which these operations can be performed. Those of ordinary skill in the art will think of various ways to reorder the operations herein. In addition, it should be pointed out that the process details involved in a certain embodiment herein are also applicable to other embodiments in a similar manner, or different embodiments can be combined and used.

[0462] It can be understood that, in order to implement the functions in the above embodiments, the base station and the terminal include corresponding hardware structures and / or software modules for executing each function. Those skilled in the art should easily realize that, in combination with the units and method steps of each example described in the embodiments disclosed in this application, the embodiments of this application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed in the manner of hardware or computer software driving hardware depends on the specific application scenario and design constraints of the technical solution.

[0463] Figure 17 and Figure 18 FIG. 17 is a schematic structural diagram of a possible data forwarding device provided by an embodiment of this application. These data forwarding devices can be used to implement the functions of the terminal, relay device, or network device in the above method embodiments, and thus can also achieve the beneficial effects possessed by the above method embodiments. In the embodiments of this application, the data forwarding device can be a terminal, a relay device, or a network device, and can be a module applied to the terminal, relay device, or network device. For example, a chip.

[0464] As Figure 17 shown, the data forwarding device 1700 includes a processing unit 1710 and a transceiver unit 1720. The data forwarding device 1700 is used to implement the above Figure 8 , Figure 10 , Figure 12 , Figure 14 and Figure 16 functions of the terminal, relay device, or network device in the method embodiments shown.

[0465] When the data forwarding device 1700 is used to implement the function of the relay device in the method embodiment shown in Figure 8 FIG. 17: The transceiver unit 1720 is used to obtain the first information. The processing unit 1710 is used to execute all operations other than the transceiver operations performed by the data forwarding device in the embodiment shown in Figure 8 FIG. 17, and / or other processes for supporting the technologies described herein.

[0466] When the data forwarding device 1700 is used to implement the function of the first network device in the method embodiment shown in Figure 8 FIG. 17: The processing unit 1710 is used to generate the first information. The transceiver unit 1720 is used to send the first information. The processing unit 1710 is further used to execute all operations other than the transceiver operations performed by the data forwarding device in the embodiment shown in Figure 8 FIG. 17, and / or other processes for supporting the technologies described herein.

[0467] When the data forwarding device 1700 is used to implement the function of the... in the method embodiment shown in Figure 8When implementing the functions of the second network device in the method embodiments shown: The processing unit 1710 is used to trigger the first network device to generate the first information. The processing unit 1710 is also used to execute Figure 8 All operations other than the transceiver operations performed by the data forwarding device in the embodiments shown, and / or other processes for supporting the technologies described herein.

[0468] For a more detailed description of the above-mentioned processing unit 1710 and transceiver unit 1720, reference can be made to Figure 8 , Figure 10 , Figure 12 , Figure 14 and Figure 16 The relevant descriptions in the method embodiments shown. The above-mentioned processing unit 1710 and transceiver unit 1720 can also execute other steps. For specific implementations, reference can be made to the method embodiments, which will not be elaborated here.

[0469] Optionally, the transceiver unit 1720 can be a transceiver, and the transceiver can include an antenna and a radio frequency circuit, etc.

[0470] The processing unit 1710 can be a processor (or, processing circuit), such as a baseband processor, and the baseband processor can include one or more CPUs.

[0471] As Figure 18 shown, the data forwarding device 1800 includes a processor 1810 and an interface circuit 1820. The processor 1810 and the interface circuit 1820 are coupled to each other. It can be understood that the interface circuit 1820 can be a transceiver or an input / output interface. Optionally, the data forwarding device 1800 can also include a memory 1830, which is used to store the instructions executed by the processor 1810 or the input data required for the processor 1810 to run the instructions or the data generated after the processor 1810 runs the instructions.

[0472] When the data forwarding device 1800 is used to implement Figure 8 , Figure 10 , Figure 12 , Figure 14 and Figure 16 and other methods shown, the processor 1810 is used to implement the functions of the above-mentioned processing unit 1710, and the interface circuit 1820 is used to implement the functions of the above-mentioned transceiver unit 1720.

[0473] When the above data forwarding device is a chip applied to a terminal, the terminal chip implements the functions of the terminal in the above method embodiments. The terminal chip receives information from a network device, which can be understood as the information is first received by other modules (such as a radio frequency module or an antenna) in the terminal and then sent by these modules to the terminal chip. The terminal chip sends information to the network device, which can be understood as the information is first sent to other modules (such as a radio frequency module or an antenna) in the terminal and then sent by these modules to the network device.

[0474] When the above data forwarding device is a chip applied to a network device, the network device chip implements the functions of the network device in the above method embodiments. The network device chip receives information from a terminal, which can be understood as the information is first received by other modules (such as a radio frequency module or an antenna) in the network device and then sent by these modules to the network device chip. The network device chip sends information to the terminal, which can be understood as the information is sent to other modules (such as a radio frequency module or an antenna) in the network device and then sent by these modules to the terminal.

[0475] Figure 17 or Figure 18 The communication device shown is only an example, and in practical applications, the communication device may have more or fewer components than those shown in Figure 17 or Figure 18 more or fewer components than those shown in, may combine two or more components, or may have different component configurations.

[0476] In the embodiments of the present application, when entity A sends information to entity B, it may be that A directly sends to B, or A indirectly sends to B through other entities. Similarly, when entity B receives information from entity A, it may be that entity B directly receives the information sent by entity A, or entity B indirectly receives the information sent by entity A through other entities. Here, entity A and B may be RAN nodes or terminals, or may be modules inside RAN nodes or terminals. The sending and receiving of information may be information interaction between a RAN node and a terminal, for example, information interaction between a network device and a terminal; the sending and receiving of information may also be information interaction between two RAN nodes, for example, information interaction between a CU and a DU; the sending and receiving of information may also be information interaction between different modules inside a device, for example, information interaction between a terminal chip and other modules of the terminal, or information interaction between a network device chip and other modules in the network device.

[0477] In an embodiment of the present application, a network device sends a downlink signal or downlink information to a terminal device, and the downlink information is carried on a downlink channel; the terminal device sends an uplink signal or uplink information to the network device, and the uplink information is carried on an uplink channel. In order to communicate with the network device, the terminal device needs to establish a wireless connection with a cell controlled by the network device. A cell that has established a wireless connection with the terminal device is called the serving cell of the terminal device.

[0478] It can be understood that in the embodiment of the present application, PDSCH and PUSCH are only taken as examples of a downlink data channel and an uplink data channel. In different systems and different scenarios, the data channel and the control channel may have different names, and the embodiment of the present application does not limit this.

[0479] It can be understood that the processor in the embodiment of the present application may be a central processing unit (CPU), or may also be other general-purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. The general-purpose processor may be a microprocessor or any conventional processor.

[0480] The method steps in the embodiment of the present application may be implemented in hardware or in software instructions executable by a processor. The software instructions may be composed of corresponding software modules, and the software modules may be stored in a random access memory, a flash memory, a read-only memory, a programmable read-only memory, an erasable programmable read-only memory, an electrically erasable programmable read-only memory, a register, a hard disk, a removable hard disk, a CD-ROM, or any other form of storage medium well known in the art. An exemplary storage medium is coupled to the processor so that the processor can read information from the storage medium and write information to the storage medium. The storage medium may also be a component of the processor. The processor and the storage medium may be located in an ASIC. In addition, the ASIC may be located in a network device or a terminal. The processor and the storage medium may also exist as discrete components in a network device or a terminal.

[0481] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented in the form of a computer program product in whole or in part. The computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of the present application are executed in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user device, or other programmable devices. The computer program or instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer program or instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center in a wired or wireless manner. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or a data center integrating one or more available media. The available medium can be a magnetic medium, such as a floppy disk, a hard disk, or a magnetic tape; it can also be an optical medium, such as a digital video disc; or it can be a semiconductor medium, such as a solid-state drive. The computer-readable storage medium can be a volatile or non-volatile storage medium, or can include both volatile and non-volatile types of storage media.

[0482] In each of the embodiments of the embodiments of the present application, if there is no special description and logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced to each other. The technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships.

[0483] It can be understood that the various numerical numbers involved in the embodiments of the present application are only for the convenience of description and do not limit the scope of the embodiments of the present application. The magnitudes of the serial numbers of the above processes do not mean the sequence of execution. The execution sequence of each process should be determined by its function and internal logic.

Claims

1. A data forwarding method, characterized in that, it includes: obtaining first information, where the first information is used to configure a forwarding unit of a relay device to forward data from a first network device. Wherein, the forwarding unit is in a first state, and the forwarding unit forwards data from a second network device in the first state.

2. The method according to claim 1, characterized in that, the method further includes: maintaining the state of the forwarding unit as the first state; in the first state, controlling the forwarding unit to forward data sent from the first network device according to the first information.

3. The method according to claim 1 or 2, characterized in that, before obtaining the first information, the method further includes: sending second information, where the second information is used to instruct a forwarding unit of the relay device to forward data from the first network device.

4. The method according to any one of claims 1-3, characterized in that, the method further includes: controlling the forwarding unit to stop forwarding data from the second network device.

5. The method according to claim 4, characterized in that, the method further includes: receiving third information, where the third information is used to instruct the forwarding unit to stop forwarding data from the second network device.

6. The method according to any one of claims 1-5, characterized in that, the first information includes a first parameter, and the first parameter is used to indicate a beam used by the forwarding unit to forward data sent from the first network device.

7. The method according to claim 6, characterized in that, the first parameter is obtained from a second parameter, and the second parameter is used to indicate a beam used by the forwarding unit to forward data sent from the second network device.

8. The method according to any one of claims 1-7, characterized in that, the relay device is dual-connected to the first network device and the second network device, where there is a first control link between the relay device and the first network device, and there is a second control link between the relay device and the second network device.

9. The method according to any one of claims 1-7, characterized in that, there is a second control link and a second backhaul link between the relay device and the second network device; before obtaining the first information, controlling a mobile terminal unit of the relay device to perform cell handover or redirection to obtain a first control link between the relay device and the first network device; the obtaining of the first information includes: obtaining the first information through the first control link.

10. The method according to any one of claims 1-7, characterized in that, there is a second control link between the relay device and the second network device; the obtaining of the first information includes: obtaining the first information through the second control link.

11. A data forwarding method, characterized in that, it includes: Generate first information, where the first information is used to configure the forwarding unit of a relay device to forward data from a first network device in a first state, and in the first state, the forwarding unit forwards data sent by a second network device; Send the first information.

12. The method according to claim 11, wherein, the first information being used to configure the forwarding unit of the relay device to forward data from the first network device in the first state includes: the first information is used to configure the forwarding unit to forward data from the first network device while maintaining the first state.

13. The method according to claim 11 or 12, wherein, generating the first information includes: meeting a first condition to generate the first information; wherein the first condition includes at least one of the following conditions: sending fourth information, where the fourth information is used to request or determine that the forwarding unit forwards data from the first network device; receiving fifth information, where the fifth information is used to determine or request that the forwarding unit forwards data from the first network device.

14. The method according to any one of claims 11-13, wherein, the first information includes a first parameter, and the first parameter is used to indicate the beam used by the forwarding unit to forward data sent by the first network device.

15. The method according to claim 14, wherein, the method further includes: receiving sixth information from the second network device, where the sixth information carries a second parameter, and the second parameter is used to indicate the beam used by the forwarding unit to forward data sent by the second network device; obtaining the first parameter based on the second parameter.

16. The method according to any one of claims 11-15, wherein, the first network device and the second network device are network devices for dual connection of the mobile terminal unit of the relay device, and there is a first control link between the relay device and the first network device, and a second control link between the relay device and the second network device.

17. The method according to any one of claims 11-15, wherein, before sending the first information, perform cell handover or redirection through the mobile terminal unit of the relay device to obtain a first control link between the first network device and the relay device; sending the first information includes: sending the first information through the first control link.

18. The method according to claim 17, wherein, the method further includes: sending third information, where the third information is used to instruct the forwarding unit to stop forwarding data from the second network device.

19. A data forwarding method, wherein, it includes: trigger the first network device to generate first information, where the first information is used to configure the forwarding unit of the relay device to forward data from the first network device in a first state, and in the first state, the forwarding unit forwards data sent by the second network device.

20. The method according to claim 19, wherein, the first information is used to configure the forwarding unit of the relay device to forward data from the first network device in the first state, including: the first information is used to configure the forwarding unit to forward data from the first network device while maintaining the first state.

21. The method according to claim 19 or 20, wherein, triggering the first network device to generate the first information includes: meeting the first condition to trigger the first network device to generate the first information; wherein, the first condition includes at least one of the following conditions: receiving the fourth information, where the fourth information is used to request or determine that the forwarding unit forwards data from the first network device; sending the fifth information, where the fifth information is used to determine or request that the forwarding unit forwards data from the first network device.

22. The method according to any one of claims 19-21, wherein, the first information includes a first parameter, and the first parameter is used to indicate the beam used by the forwarding unit to forward data sent by the first network device.

23. The method according to claim 22, wherein, the first parameter is obtained from a second parameter, and the second parameter is used to indicate the beam used by the forwarding unit to forward data sent by the second network device; the method further includes: sending the sixth information, and the second parameter is carried in the sixth information.

24. The method according to any one of claims 19-23, wherein, before triggering the first network device to generate the first information, the method further includes: receiving the second information, where the second information is used to indicate that the forwarding unit of the relay device forwards data from the first network device.

25. The method according to any one of claims 19-24, wherein, the first network device and the second network device are network devices that are dual-connected to the mobile terminal unit of the relay device, where there is a first control link between the relay device and the first network device, and there is a second control link between the relay device and the second network device.

26. The method according to any one of claims 19-24, wherein, there is a second control link and a second backhaul link between the relay device and the second network device; before triggering the first network device to generate the first information, the method further includes: triggering the mobile terminal unit of the relay device to perform cell handover or redirection to obtain the first control link between the first network device and the relay device.

27. The method according to any one of claims 19-24, wherein, there is a second control link between the relay device and the second network device; the method further includes: sending the first information through the second control link.

28. The method according to any one of claims 19-25, 27, wherein, the method further includes: Send a third piece of information, where the third piece of information is used to instruct the forwarding unit to stop forwarding data from the second network device.

29. A data forwarding device, characterized in that it includes: At least one processor and a communication interface, where the communication interface is used to receive and / or send signals, and the processor is configured to enable the method described in any one of claims 1 to 10 to be executed; or, the processor is configured to enable the method described in any one of claims 11 to 18 to be executed; or, the processor is configured to enable the method described in any one of claims 19 to 28 to be executed.

30. A computer-readable storage medium, characterized in that instructions or programs are stored in the computer-readable storage medium, and when the instructions or programs run on a communication device, the communication device is caused to execute the method described in any one of claims 1-10; or, the communication device is caused to execute the method described in any one of claims 11-18; or, the communication device is caused to execute the method described in any one of claims 19-28.

Images