Communication method and apparatus

Abstract

A communication method and apparatus. The communication method is applied to a first relay node. The first relay node comprises a first mobile terminal and a first access network node. The communication method comprises: acquiring first information, wherein the first information is configured to indicate at least one piece of address information; and sending second information on the basis of the at least one piece of address information. The second information is configured to indicate a request for establishing a first communication interface and / or a second communication interface, wherein the first communication interface is a communication interface between a first access network node and a first core network node, and the second communication interface is a communication interface between the first access network node and an adjacent access network node. The first core network node provides a communication service for a terminal device that accesses the first relay node. In the present application, the first relay node can acquire the address information so as to send, on the basis of the address information, the second information for establishing communication interfaces. Therefore, the first access network node in the first relay node can directly establish logical interfaces with different network devices, thereby improving the communication efficiency.

Description

Communication method and device

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office on March 29, 2024, with application number "202410385506.2" and invention name "Communication Method and Device", the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of communications, and in particular to communication methods and devices. Background Art

[0003] Vehicle-mounted mobile relays (VAMs), such as relay nodes deployed on vehicles or aircraft, provide wireless coverage for terminals inside the vehicle or aircraft, overcoming poor wireless signal conditions. Relay nodes can connect to macro base stations (MBSs) via wireless backhaul. Macro base stations are also called macro base stations or donor base stations.

[0004] The mobile integrated access and backhaul (IAB) solution was proposed within the 3rd Generation Partnership Project (3GPP). Relay nodes can be mobile IAB nodes. These IAB nodes are based on an architecture that separates centralized units (CUs) and distributed units (DUs). An IAB node does not possess CU functionality. When an IAB node communicates with the core network, it must be backhauled to an IAB host node via one or more hops. The IAB host node then sends the corresponding information to the core network, enabling interaction between the IAB node and the core network. An IAB host node can be considered an access network node with complete access network functionality, namely, both CU and DU functionality. An IAB node connects to an IAB node or IAB host node, which in turn connects to a core network node. An IAB node is typically referred to as an IAB-node, and an IAB host node as an IAB-donor.

[0005] Because IAB nodes lack CU functionality, they can be considered Layer 2 relays. They don't involve higher-level communications like radio resource control (RRC) and simply serve as an extension of the IAB host node's coverage. Consequently, IAB nodes lack logical communication interfaces with core network nodes or other access network nodes.

[0006] To enhance the capabilities of mobile relay nodes, consideration is being given to introducing CU functionality into them, enabling them to possess complete access network functionality. However, as these mobile relay nodes move, the relationships between their adjacent access and core network nodes vary. Therefore, establishing communication interfaces between these mobile relay nodes and their adjacent access and core network nodes remains an open question. Summary of the Invention

[0007] The embodiments of the present application provide a communication method and apparatus, which improve communication efficiency by acquiring address information to establish a logical interface between a first relay node and different network devices.

[0008] To achieve the above objectives, this application adopts the following technical solutions:

[0009] In a first aspect, a communication method is provided, which is applied to a first relay node, wherein the first relay node includes a first mobile terminal (MT) and a first access network node. The method includes: obtaining first information. The first information is used to indicate at least one address information, and the at least one address information is used to establish a first communication interface and / or a second communication interface. The first communication interface is a communication interface between the first access network node and the first core network node, and the second communication interface is a communication interface between the first access network node and an adjacent access network node. The first core network node provides communication services for terminal devices accessing the first relay node. Second information is sent based on the at least one address information. The second information is used to indicate a request to establish the first communication interface and / or the second communication interface.

[0010] In the present application, the first relay node can obtain address information so as to send second information for establishing a communication interface according to the address information, so that the first access network node in the first relay node can directly establish a logical interface with different network devices, thereby improving communication efficiency.

[0011] In one possible design, the first information includes at least one of the following address information: a first Internet Protocol (IP) address. The first IP address is the IP address of the first access network node. The first IP address is used to establish the first communication interface and / or the second communication interface. A second IP address. The second IP address is the IP address of the adjacent access network node. The second IP address is used to establish the second communication interface.

[0012] The present application may provide the IP address of the first relay node and / or the IP address of the adjacent access network node, so that the first relay node can accurately establish a logical interface with the first core network node and / or the adjacent access network node based on the above address information.

[0013] In one possible design, the first information is determined by at least one of the following network devices: a network management device; a second core network node, wherein the second core network node provides communication services for the first relay node; the first core network node; a first host node, wherein the first host node is a host node of the first relay node; and a radio access network intelligent controller (RIC).

[0014] The present application provides a variety of network devices for determining the first information to be applicable to different network scenarios. Address information can be configured for the first relay device through appropriate network devices in the corresponding network scenarios.

[0015] In one possible design, the method further includes: sending third information, wherein the third information is used to request the network device to obtain the first information.

[0016] In the present application, the first relay node may actively request to obtain the first information, so that the address information may be configured for the first relay node more flexibly.

[0017] In one possible design, the first information includes the first IP address, and the third information also includes: identification information of the second core network node and / or identification information of the first host node.

[0018] The present application can send identification information of different nodes so that the network device can determine a more appropriate anchor point according to the identification information to configure an appropriate first IP address.

[0019] In one possible design, the anchor point corresponding to the first IP address is the second core network node, and / or the anchor point corresponding to the first IP address is the first host node.

[0020] This application provides possible situations of multiple anchor points of the first IP address, so that in the communication scenarios between the first relay node and different nodes, the first IP address corresponding to the appropriate anchor point can be configured for the first relay node, thereby improving the communication efficiency between the first relay node and other nodes.

[0021] In one possible design, the first IP address and the IP address of the anchor point are in the same IP network segment, or the first IP address is the IP address of the anchor point.

[0022] This application provides multiple relationships between the first IP address and the IP address of the anchor point, so that the first IP address can be configured in an appropriate manner in different communication scenarios.

[0023] In one possible design, the first information includes the second IP address, and the method further includes: obtaining a first identifier. The first identifier is a cell identifier of a cell managed by the adjacent access network node, or the first identifier is an identifier of the adjacent access network node. Sending the first identifier. The first identifier is used to request the IP address of the adjacent access network node corresponding to the first identifier.

[0024] The present application can determine the IP address of the adjacent access network node by using the first identifier obtained by measuring the first cell, so that the first relay node can establish a communication interface with the access network node of the first cell, thereby improving communication efficiency.

[0025] In one possible design, obtaining the first identifier includes: measuring the first cell to obtain the first identifier. The first cell is a cell managed by the adjacent access network node. Or, receiving the first identifier from the terminal device.

[0026] This application provides multiple ways to measure the first identifier, so that the first identifier can be measured in an appropriate way in different scenarios, thereby improving universality.

[0027] In one possible design, the adjacent access network node is at least one of the following access network nodes: the adjacent access network node that has a logical interface with the first core network node; the adjacent access network node that has a logical interface with the second core network node; the adjacent access network node that has a logical interface with the first host node; the adjacent access network node that is reachable by IP routing to the first core network node; the adjacent access network node that is reachable by IP routing to the second core network node; and the adjacent access network node that is reachable by IP routing to the first host node.

[0028] The adjacent access network node that can establish a communication interface in the present application can be an adjacent access network node that has a logical interface and / or IP routing reachable with the network device. This ensures that normal communication with the adjacent access network node can be achieved after establishing a communication interface with the first relay node, thereby avoiding communication failures.

[0029] In one possible design, the first information includes the second IP address, and the method further includes: obtaining a second identifier. The second identifier is an identifier of the adjacent access network node. Sending the second identifier. The second identifier is used to request the IP address of the adjacent access network node.

[0030] In the embodiment of the present application, the identifier of the adjacent access network node that has a logical interface and / or IP route to the network device can be obtained, so that the communication interface established by the first relay node can communicate normally with the adjacent access network node, avoiding the situation where communication is impossible.

[0031] In one possible design, the adjacent access network node is located within the coverage area of ​​the registration area of ​​the terminal device or the first relay node.

[0032] The adjacent access network nodes in the embodiment of the present application can be access network nodes within the registration area of ​​the terminal device or the first relay node, thereby ensuring that the first relay node establishes a communication interface with the adjacent access network nodes within a certain range, improving network security while saving resource consumption caused by establishing the communication interface.

[0033] In one possible design, the host node of the first relay node is switched from the second host node to the first host node, and obtaining the first information includes: obtaining the first information from the second host node.

[0034] The present application can also be applied to the scenario where the first relay node switches the host node, so that in this scenario the first relay node can also establish a communication interface with other network devices to improve the stability of communication.

[0035] In one possible design, the adjacent access network node is a non-second relay node, where the non-second relay node is any access network node other than the second relay node, and the second relay node includes the second MT and the second access network node. In other words, the adjacent access network node is not the second access network node.

[0036] In the present application, the establishment of a communication interface between the access network node in the first relay node and the access network node in the second relay node is avoided, thereby avoiding waste of resources.

[0037] In a second aspect, a communication method is provided, the method being applied to a first relay node, the first relay node comprising a first mobile terminal and a first access network node. The method comprises: obtaining a second IP address. The second IP address is the IP address of the adjacent access network node. The second IP address is used to establish the second communication interface. The second communication interface is the communication interface between the first access network node and the adjacent access network node. The adjacent access network node corresponding to the second IP address is a second relay node, and second information is not sent. The second information is used to indicate a request to establish the first communication interface and / or the second communication interface. The second relay node comprises a second mobile terminal and a second access network node.

[0038] In the present application, the first relay node can dynamically determine whether to send the second information based on the node type of the node corresponding to the second IP address, which can improve the efficiency of the first relay node in establishing the communication interface.

[0039] In one possible design, the method further includes: measuring the first cell to obtain first type information of the first cell. The first cell is a cell managed by the adjacent access network node. Or, receiving first type information of the first cell from the terminal device. Or, receiving second type information of the adjacent access network node from a network device. The first type information is used to indicate that the first cell is a cell managed by the second access network node. The second type information is used to indicate that the adjacent access network node belongs to a second relay node, that is, the adjacent access network node is the second access network node.

[0040] The present application provides multiple ways to determine the node type of an adjacent access network node, so as to determine whether the adjacent access network node is a second relay node in an appropriate manner in different scenarios.

[0041] In one possible design, the first information is determined by at least one of the following network devices: a network management device; a second core network node, wherein the second core network node provides communication services for the first relay node; the first core network node; a first host node, wherein the first host node is the host node of the first relay node; and RIC.

[0042] According to a third aspect, a communication method is provided. The method is applied to a network device, wherein the network device establishes a communication connection with a first relay node, wherein the first relay node includes a first mobile terminal and a first access network node. The method includes: sending first information. The first information is used to indicate at least one piece of address information. The at least one piece of address information is used to establish a first communication interface and / or a second communication interface. The first communication interface is a communication interface between the first access network node and a first core network node, and the second communication interface is a communication interface between the first access network node and an adjacent access network node. The first core network node provides communication services for terminal devices accessing the first relay node.

[0043] In the present application, the first relay node can obtain address information so as to send second information for establishing a communication interface according to the address information, so that the first access network node in the first relay node can directly establish a logical interface with different network devices, thereby improving communication efficiency.

[0044] In one possible design, the first information includes at least one of the following address information: a first IP address. The first IP address is the IP address of the first access network node. The first IP address is used to establish the first communication interface and / or the second communication interface. A second IP address. The second IP address is the IP address of the adjacent access network node. The second IP address is used to establish the second communication interface.

[0045] In one possible design, the network device includes at least one of the following devices: a network management device; a second core network node, wherein the second core network node provides communication services for the first relay node; the first core network node; a first host node, wherein the first host node is the host node of the first relay node; and RIC.

[0046] In one possible design, the method further includes: obtaining third information. The third information is used to indicate that the first relay node requests to obtain the first information. The first information is determined based on the third information.

[0047] In one possible design, the first information includes the first IP address, and the third information also includes: identification information of the second core network node and / or identification information of the first host node.

[0048] In one possible design, the anchor point corresponding to the first IP address is the first core network node, and / or the anchor point corresponding to the first IP address is the first host node.

[0049] In one possible design, the first IP address and the IP address of the anchor point are in the same IP network segment, or the first IP address is the IP address of the anchor point.

[0050] In one possible design, the method further includes: obtaining fourth information. The fourth information is used to indicate a request to establish the first communication interface and / or the second communication interface. In response to the fourth information, determining the first IP address. Replacing the source IP address in the fourth information with the first IP address to obtain second information. The second information is used to indicate a request to establish the first communication interface and / or the second communication interface. Sending the second information.

[0051] The network device of the present application can also dynamically configure the first IP address when forwarding the interface establishment information and replace the source IP address of the interface establishment information with a new IP address. This can ensure normal communication after the subsequent interface is established and avoid interface establishment failure caused by IP address errors.

[0052] In one possible design, the first information includes the second IP address, and the method further includes: obtaining a first identifier. The first identifier is used to indicate that the first relay node requests to obtain the IP address of the adjacent access network node corresponding to the first identifier. The second IP address is determined based on the first identifier. The first identifier is the cell identifier of the cell managed by the adjacent access network node, or the first identifier is the identifier of the adjacent access network node.

[0053] In one possible design, the first identifier is obtained by measuring the first relay node, or the first identifier is obtained by measuring the terminal device.

[0054] In one possible design, the adjacent access network node is at least one of the following access network nodes: the adjacent access network node that has a logical interface with the first core network node; the adjacent access network node that has a logical interface with the second core network node; the adjacent access network node that has a logical interface with the first host node; the adjacent access network node that is reachable by IP routing to the first core network node; the adjacent access network node that is reachable by IP routing to the second core network node; and the adjacent access network node that is reachable by IP routing to the first host node.

[0055] In one possible design, the first information includes the second IP address, and the method further includes: obtaining a second identifier, the second identifier being used to request obtaining the IP address of the adjacent access network node, wherein the second identifier is an identifier that identifies the adjacent access network node. The second IP address is determined based on the second identifier, the second IP address being the IP address of the adjacent access network node.

[0056] In one possible design, the adjacent access network node is located within the coverage area of ​​the registration area of ​​the terminal device or the first relay node.

[0057] In one possible design, the network device is a second core network node and / or the first host node, and the host node of the first relay node is switched from the second host node to the first host node. The method further includes: receiving fifth information from the second host node. The fifth information includes a third IP address. The third IP address is the IP address of the first access network node before the first relay node is switched. Sending sixth information. The sixth information is used to indicate the correspondence between the third IP address and the first IP address.

[0058] The network device of the present application can indicate the correspondence between the third IP address corresponding to the second host node and the first IP address of the first host node when the first relay node switches the host node, so that the first relay node can also establish a communication interface during the switching process to ensure communication stability.

[0059] In one possible design, the method further includes: obtaining seventh information. The seventh information is used to indicate the IP address of the adjacent access network node. The adjacent access network node is a non-second relay node, and the second IP address includes the IP address of the adjacent access network node, wherein the non-second relay node is any access network node other than the second relay node, and the second relay node includes a second MT and a second access network node. In other words, the adjacent access network node is not the second access network node.

[0060] The network device of the present application can avoid feeding back the second IP address belonging to the second relay node to the first relay node, so as to avoid establishing a communication interface between the access network node in the first relay node and the access network node in the second relay node, thereby avoiding wasting resources.

[0061] In a fourth aspect, a communication device is provided, which is applied to a first relay node, wherein the first relay node includes a first MT and a first access network node. The device includes: a transceiver unit, which is used to obtain first information. The first information is used to indicate at least one address information, and the at least one address information is used to establish a first communication interface and / or a second communication interface. The first communication interface is a communication interface between the first access network node and the first core network node, and the second communication interface is a communication interface between the first access network node and an adjacent access network node. The first core network node provides communication services for terminal devices accessing the first relay node. A processing unit is used to send second information based on the at least one address information. The second information is used to indicate a request to establish the first communication interface and / or the second communication interface.

[0062] In the present application, the first relay node can obtain address information so as to send second information for establishing a communication interface according to the address information, so that the first access network node in the first relay node can directly establish a logical interface with different network devices, thereby improving communication efficiency.

[0063] In one possible design, the first information includes at least one of the following address information: a first IP address. The first IP address is the IP address of the first access network node. The first IP address is used to establish the first communication interface and / or the second communication interface. A second IP address. The second IP address is the IP address of the adjacent access network node. The second IP address is used to establish the second communication interface.

[0064] In one possible design, the first information is determined by at least one of the following network devices: a network management device; a second core network node, wherein the second core network node provides communication services for the first relay node; the first core network node; a first host node, wherein the first host node is the host node of the first relay node; and RIC.

[0065] In one possible design, the transceiver unit is further configured to send third information, wherein the third information is used to request the network device to obtain the first information.

[0066] In one possible design, the first information includes the first IP address, and the third information also includes: identification information of the second core network node and / or identification information of the first host node.

[0067] In one possible design, the anchor point corresponding to the first IP address is the second core network node, and / or the anchor point corresponding to the first IP address is the first host node.

[0068] In one possible design, the first IP address and the IP address of the anchor point are in the same IP network segment, or the first IP address is the IP address of the anchor point.

[0069] In one possible design, the first information includes the second IP address, and the transceiver unit is further used to: obtain a first identifier. The first identifier is a cell identifier of a cell managed by the adjacent access network node, or the first identifier is an identifier of the adjacent access network node. Send the first identifier. The first identifier is used to request the IP address of the adjacent access network node corresponding to the first identifier.

[0070] In one possible design, the processing unit is further configured to measure the first cell to obtain the first identifier. The first cell is a cell managed by the adjacent access network node. Alternatively, the transceiver unit is further configured to receive the first identifier from the terminal device.

[0071] In one possible design, the adjacent access network node is at least one of the following access network nodes: the adjacent access network node that has a logical interface with the first core network node; the adjacent access network node that has a logical interface with the second core network node; the adjacent access network node that has a logical interface with the first host node; the adjacent access network node that is reachable by IP routing to the first core network node; the adjacent access network node that is reachable by IP routing to the second core network node; and the adjacent access network node that is reachable by IP routing to the first host node.

[0072] In one possible design, the first information includes the second IP address, and the transceiver unit is further used to: obtain a second identifier. The second identifier is an identifier of the adjacent access network node. Send the second identifier. The second identifier is used to request the IP address of the adjacent access network node.

[0073] In one possible design, the adjacent access network node is located within the coverage area of ​​the registration area of ​​the terminal device or the first relay node.

[0074] In one possible design, the host node of the first relay node is switched from the second host node to the first host node, and the transceiver unit is further used to obtain the first information from the second host node.

[0075] In one possible design, the adjacent access network node is a non-second relay node, where the non-second relay node is any access network node other than the second relay node, and the second relay node includes the second MT and the second access network node. In other words, the adjacent access network node is not the second access network node.

[0076] In a fifth aspect, a communication device is provided, which is applied to a first relay node, wherein the first relay node includes a first MT and a first access network node. The device includes: a transceiver unit, which is used to obtain a second IP address. The second IP address is the IP address of the adjacent access network node. The second IP address is used to establish the second communication interface. The second communication interface is the communication interface between the first access network node and the adjacent access network node. The adjacent access network node corresponding to the second IP address is a second relay node, and a processing unit is used to control the transceiver unit not to send second information. The second information is used to indicate a request to establish the first communication interface and / or the second communication interface. The second relay node includes a second MT and a second access network node.

[0077] In the present application, the first relay node can dynamically determine whether to send the second information based on the node type of the node corresponding to the second IP address, which can improve the efficiency of the first relay node in establishing the communication interface.

[0078] In one possible design, the processing unit is further configured to measure the first cell to obtain first type information of the first cell. The first cell is a cell managed by the adjacent access network node. Alternatively, the transceiver unit is further configured to receive first type information of the first cell from the terminal device. Alternatively, the transceiver unit is further configured to receive second type information of the adjacent access network node from a network device. The first type information is used to indicate that the first cell is a cell managed by the second access network node. The second type information is used to indicate that the adjacent access network node belongs to a second relay node, that is, the adjacent access network node is the second access network node.

[0079] In one possible design, the first information is determined by at least one of the following network devices: a network management device; a second core network node, wherein the second core network node provides communication services for the first relay node; the first core network node; a first host node, wherein the first host node is the host node of the first relay node; and RIC.

[0080] In a sixth aspect, a communication device is provided, which is applied to a network device, wherein the network device establishes a communication connection with a first relay node, and the first relay node includes a first MT and a first access network node. The device includes: a transceiver unit, which is used to send first information. The first information is used to indicate at least one address information. The at least one address information is used to establish a first communication interface and / or a second communication interface. The first communication interface is a communication interface between the first access network node and the first core network node, and the second communication interface is a communication interface between the first access network node and an adjacent access network node. The first core network node provides communication services for terminal devices accessing the first relay node.

[0081] In the present application, the first relay node can obtain address information so as to send second information for establishing a communication interface according to the address information, so that the first access network node in the first relay node can directly establish a logical interface with different network devices, thereby improving communication efficiency.

[0082] In one possible design, the first information includes at least one of the following address information: a first IP address. The first IP address is the IP address of the first access network node. The first IP address is used to establish the first communication interface and / or the second communication interface. A second IP address. The second IP address is the IP address of the adjacent access network node. The second IP address is used to establish the second communication interface.

[0083] In one possible design, the network device includes at least one of the following devices: a network management device; a second core network node, wherein the second core network node provides communication services for the first relay node; the first core network node; a first host node, wherein the first host node is the host node of the first relay node; and RIC.

[0084] In one possible design, the transceiver unit is further configured to: obtain third information. The third information is configured to indicate that the first relay node requests to obtain the first information. The first information is determined based on the third information.

[0085] In one possible design, the first information includes the first IP address, and the third information also includes: identification information of the second core network node and / or identification information of the first host node.

[0086] In one possible design, the anchor point corresponding to the first IP address is the first core network node, and / or the anchor point corresponding to the first IP address is the first host node.

[0087] In one possible design, the first IP address and the IP address of the anchor point are in the same IP network segment, or the first IP address is the IP address of the anchor point.

[0088] In one possible design, the apparatus further includes a processing unit. The transceiver unit is further configured to obtain fourth information. The fourth information is used to indicate a request to establish the first communication interface and / or the second communication interface. The processing unit is configured to determine the first IP address in response to the fourth information. The processing unit is further configured to replace the source IP address in the fourth information with the first IP address to obtain second information. The second information is used to indicate a request to establish the first communication interface and / or the second communication interface. The second information is transmitted.

[0089] In one possible design, the first information includes the second IP address, and the transceiver unit is further used to obtain a first identifier. The first identifier is used to indicate that the first relay node requests to obtain the IP address of the adjacent access network node corresponding to the first identifier. The processing unit is also used to determine the second IP address based on the first identifier. The first identifier is the cell identifier of the cell managed by the adjacent access network node, or the first identifier is the identifier of the adjacent access network node.

[0090] In one possible design, the first identifier is obtained by measuring the first relay node, or the first identifier is obtained by measuring the terminal device.

[0091] In one possible design, the adjacent access network node is at least one of the following access network nodes: the adjacent access network node that has a logical interface with the first core network node; the adjacent access network node that has a logical interface with the second core network node; the adjacent access network node that has a logical interface with the first host node; the adjacent access network node that is reachable by IP routing to the first core network node; the adjacent access network node that is reachable by IP routing to the second core network node; and the adjacent access network node that is reachable by IP routing to the first host node.

[0092] In one possible design, the first information includes the second IP address, and the transceiver unit is further configured to obtain a second identifier, where the second identifier is used to request the IP address of the adjacent access network node, wherein the second identifier is an identifier that identifies the adjacent access network node. The processing unit is further configured to determine the second IP address based on the second identifier, where the second IP address is the IP address of the adjacent access network node.

[0093] In one possible design, the adjacent access network node is located within the coverage area of ​​the registration area of ​​the terminal device or the first relay node.

[0094] In one possible design, the network device is a second core network node and / or the first host node, the host node of the first relay node is switched from the second host node to the first host node, and the transceiver unit is further used to: receive fifth information from the second host node. The fifth information includes a third IP address. The third IP address is the IP address of the first access network node before the first relay node is switched. Send sixth information. The sixth information is used to indicate the correspondence between the third IP address and the first IP address.

[0095] In one possible design, the transceiver unit is further configured to: obtain seventh information. The seventh information is used to indicate the IP address of the adjacent access network node. The adjacent access network node is a non-second relay node, and the second IP address includes the IP address of the adjacent access network node, wherein the non-second relay node is any access network node other than the second relay node, and the second relay node includes a second MT and a second access network node. In other words, the adjacent access network node is not the second access network node.

[0096] In a seventh aspect, a communication device is provided, which is applied to a first relay node, wherein the first relay node includes a first MT and a first access network node. The device includes: a transceiver, which is used to obtain first information. The first information is used to indicate at least one address information, and the at least one address information is used to establish a first communication interface and / or a second communication interface. The first communication interface is a communication interface between the first access network node and the first core network node, and the second communication interface is a communication interface between the first access network node and an adjacent access network node. The first core network node provides communication services for terminal devices accessing the first relay node. A processor is used to send second information based on the at least one address information. The second information is used to indicate a request to establish the first communication interface and / or the second communication interface. In some examples, the transceiver may also be referred to as an interface circuit.

[0097] In the present application, the first relay node can obtain address information so as to send second information for establishing a communication interface according to the address information, so that the first access network node in the first relay node can directly establish a logical interface with different network devices, thereby improving communication efficiency.

[0098] In one possible design, the first information includes at least one of the following address information: a first IP address. The first IP address is the IP address of the first access network node. The first IP address is used to establish the first communication interface and / or the second communication interface. A second IP address. The second IP address is the IP address of the adjacent access network node. The second IP address is used to establish the second communication interface.

[0099] In one possible design, the first information is determined by at least one of the following network devices: a network management device; a second core network node, wherein the second core network node provides communication services for the first relay node; the first core network node; a first host node, wherein the first host node is the host node of the first relay node; and RIC.

[0100] In one possible design, the transceiver is further configured to: send third information, wherein the third information is used to request the network device to obtain the first information.

[0101] In one possible design, the first information includes the first IP address, and the third information also includes: identification information of the second core network node and / or identification information of the first host node.

[0102] In one possible design, the anchor point corresponding to the first IP address is the second core network node, and / or the anchor point corresponding to the first IP address is the first host node.

[0103] In one possible design, the first IP address and the IP address of the anchor point are in the same IP network segment, or the first IP address is the IP address of the anchor point.

[0104] In one possible design, the first information includes the second IP address, and the transceiver is further used to: obtain a first identifier. The first identifier is a cell identifier of a cell managed by the adjacent access network node, or the first identifier is an identifier of the adjacent access network node. Send the first identifier. The first identifier is used to request the IP address of the adjacent access network node corresponding to the first identifier.

[0105] In one possible design, the processor is further configured to measure a first cell to obtain the first identifier. The first cell is a cell managed by the adjacent access network node. Alternatively, the transceiver is further configured to receive the first identifier from the terminal device.

[0106] In one possible design, the adjacent access network node is at least one of the following access network nodes: the adjacent access network node that has a logical interface with the first core network node; the adjacent access network node that has a logical interface with the second core network node; the adjacent access network node that has a logical interface with the first host node; the adjacent access network node that is reachable by IP routing to the first core network node; the adjacent access network node that is reachable by IP routing to the second core network node; and the adjacent access network node that is reachable by IP routing to the first host node.

[0107] In one possible design, the first information includes the second IP address, and the transceiver is further used to: obtain a second identifier. The second identifier is an identifier of the adjacent access network node. Send the second identifier. The second identifier is used to request the IP address of the adjacent access network node.

[0108] In one possible design, the adjacent access network node is located within the coverage area of ​​the registration area of ​​the terminal device or the first relay node.

[0109] In one possible design, the host node of the first relay node is switched from the second host node to the first host node, and the transceiver is further used to obtain the first information from the second host node.

[0110] In one possible design, the adjacent access network node is a non-second relay node, where the non-second relay node is any access network node other than the second relay node, and the second relay node includes the second MT and the second access network node. In other words, the adjacent access network node is not the second access network node.

[0111] In an eighth aspect, a communication device is provided, which is applied to a first relay node, wherein the first relay node includes a first MT and a first access network node. The device includes: a transceiver, which is used to obtain a second IP address. The second IP address is the IP address of the adjacent access network node. The second IP address is used to establish the second communication interface. The second communication interface is the communication interface between the first access network node and the adjacent access network node. The adjacent access network node corresponding to the second IP address is a second relay node, and a processor is used to control the transceiver not to send the second information. The second information is used to indicate a request to establish the first communication interface and / or the second communication interface. The second relay node includes a second MT and a second access network node. In some examples, the transceiver can also be referred to as an interface circuit.

[0112] In the present application, the first relay node can dynamically determine whether to send the second information based on the node type of the node corresponding to the second IP address, which can improve the efficiency of the first relay node in establishing the communication interface.

[0113] In one possible design, the processor is further configured to measure the first cell to obtain first type information of the first cell. The first cell is a cell managed by the adjacent access network node. Alternatively, the transceiver is further configured to receive first type information of the first cell from the terminal device. Alternatively, the transceiver is further configured to receive second type information of the adjacent access network node sent from a network device. The first type information is used to indicate that the first cell is a cell managed by the second access network node. The second type information is used to indicate that the adjacent access network node belongs to a second relay node, that is, the adjacent access network node is the second access network node.

[0114] In one possible design, the first information is determined by at least one of the following network devices: a network management device; a second core network node, wherein the second core network node provides communication services for the first relay node; the first core network node; a first host node, wherein the first host node is the host node of the first relay node; and RIC.

[0115] In a ninth aspect, a communication device is provided, which is applied to a network device, and the network device establishes a communication connection with a first relay node, and the first relay node includes a first MT and a first access network node. The device includes: a transceiver for sending first information. The first information is used to indicate at least one address information. The at least one address information is used to establish a first communication interface and / or a second communication interface. The first communication interface is a communication interface between the first access network node and the first core network node, and the second communication interface is a communication interface between the first access network node and an adjacent access network node. The first core network node provides communication services for terminal devices accessing the first relay node. In some examples, the transceiver may also be referred to as an interface circuit.

[0116] In the present application, the first relay node can obtain address information so as to send second information for establishing a communication interface according to the address information, so that the first access network node in the first relay node can directly establish a logical interface with different network devices, thereby improving communication efficiency.

[0117] In one possible design, the first information includes at least one of the following address information: a first IP address. The first IP address is the IP address of the first access network node. The first IP address is used to establish the first communication interface and / or the second communication interface. A second IP address. The second IP address is the IP address of the adjacent access network node. The second IP address is used to establish the second communication interface.

[0118] In one possible design, the network device includes at least one of the following devices: a network management device; a second core network node, wherein the second core network node provides communication services for the first relay node; the first core network node; a first host node, wherein the first host node is the host node of the first relay node; and RIC.

[0119] In one possible design, the transceiver is further configured to: obtain third information, wherein the third information is configured to indicate that the first relay node requests to obtain the first information, and determine the first information based on the third information.

[0120] In one possible design, the first information includes the first IP address, and the third information also includes: identification information of the second core network node and / or identification information of the first host node.

[0121] In one possible design, the anchor point corresponding to the first IP address is the first core network node, and / or the anchor point corresponding to the first IP address is the first host node.

[0122] In one possible design, the first IP address and the IP address of the anchor point are in the same IP network segment, or the first IP address is the IP address of the anchor point.

[0123] In one possible design, the apparatus further includes a processor. The transceiver is further configured to obtain fourth information. The fourth information is configured to indicate a request to establish the first communication interface and / or the second communication interface. The processor is configured to determine the first IP address in response to the fourth information. The processor is further configured to replace the source IP address in the fourth information with the first IP address to obtain second information. The second information is configured to indicate a request to establish the first communication interface and / or the second communication interface. The second information is then transmitted.

[0124] In one possible design, the first information includes the second IP address, and the transceiver is further used to obtain a first identifier. The first identifier is used to indicate that the first relay node requests to obtain the IP address of the adjacent access network node corresponding to the first identifier. The processor is also used to determine the second IP address based on the first identifier. The first identifier is a cell identifier of a cell managed by the adjacent access network node, or the first identifier is an identifier of the adjacent access network node.

[0125] In one possible design, the first identifier is obtained by measuring the first relay node, or the first identifier is obtained by measuring the terminal device.

[0126] In one possible design, the adjacent access network node is at least one of the following access network nodes: the adjacent access network node that has a logical interface with the first core network node; the adjacent access network node that has a logical interface with the second core network node; the adjacent access network node that has a logical interface with the first host node; the adjacent access network node that is reachable by IP routing to the first core network node; the adjacent access network node that is reachable by IP routing to the second core network node; and the adjacent access network node that is reachable by IP routing to the first host node.

[0127] In one possible design, the first information includes the second IP address, and the transceiver is further configured to obtain a second identifier, where the second identifier is used to request the IP address of the adjacent access network node, wherein the second identifier is an identifier that identifies the adjacent access network node. The processor is further configured to determine the second IP address based on the second identifier, where the second IP address is the IP address of the adjacent access network node.

[0128] In one possible design, the adjacent access network node is located within the coverage area of ​​the registration area of ​​the terminal device or the first relay node.

[0129] In one possible design, the network device is a second core network node and / or the first host node, the host node of the first relay node is switched from the second host node to the first host node, and the transceiver is further used to: receive fifth information from the second host node. The fifth information includes a third IP address. The third IP address is the IP address of the first access network node before the first relay node is switched. Send sixth information. The sixth information is used to indicate the correspondence between the third IP address and the first IP address.

[0130] In one possible design, the transceiver is further configured to: obtain seventh information. The seventh information is used to indicate the IP address of the adjacent access network node. The adjacent access network node is a non-second relay node, and the second IP address includes the IP address of the adjacent access network node, wherein the non-second relay node is any access network node other than the second relay node, and the second relay node includes a second MT and a second access network node. In other words, the adjacent access network node is not the second access network node.

[0131] In a tenth aspect, a communication device is provided, which includes a processor for supporting the communication device to implement the functions involved in any of the above aspects.

[0132] In a possible design, the communication device further includes a memory, which is used to store program instructions and data necessary for the communication device.

[0133] In one possible design, the communication device further includes: a communication interface for receiving and / or sending signals. In some examples, the communication interface can also be understood as a transceiver or an interface circuit.

[0134] The present application provides a communication device, including modules, units, or means for implementing any one of the above methods.

[0135] In an eleventh aspect, a communication system is provided, which includes a first relay node that executes any method of any of the above aspects, and a network device that executes any method of any of the above aspects.

[0136] In the twelfth aspect, a chip system is provided, which includes a processor and an input / output port, the processor is used to implement the processing functions involved in the communication method of any aspect of the above aspects, and the input / output port is used to implement the transceiver functions involved in the communication method of any aspect of the above aspects.

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

[0138] The chip system can be composed of one or more chips, or it can include a chip and other discrete devices. The memory can be located on the chip or as a discrete device.

[0139] In a thirteenth aspect, a computer-readable storage medium is provided. The computer-readable storage medium stores computer instructions; when the computer instructions are executed on a computer, the computer executes the communication method designed in any of the above aspects.

[0140] In a fourteenth aspect, a computer program product is provided, which includes a computer program or instructions, and when the computer program or instructions are run on a computer, the computer is caused to execute the communication method as designed in any of the above aspects. BRIEF DESCRIPTION OF THE DRAWINGS

[0141] FIG1 is an exemplary diagram of the architecture of a communication system provided in an embodiment of the present application;

[0142] FIG2 is a schematic diagram of a VAM scenario provided in an embodiment of the present application;

[0143] FIG3 is a schematic diagram of an IAB scenario provided in an embodiment of the present application;

[0144] FIG4 is a schematic diagram of an IAB network structure provided in an embodiment of the present application;

[0145] FIG5 is a schematic diagram of a long-term evolution relay architecture;

[0146] FIG6 is a schematic diagram of a relay network structure provided in an embodiment of the present application;

[0147] FIG7 is a schematic diagram of a communication method provided in an embodiment of the present application;

[0148] FIG8 is a schematic diagram of a relay network interface provided in an embodiment of the present application;

[0149] FIG9 is a schematic diagram of a relay network interface in an open wireless access network scenario provided by an embodiment of the present application;

[0150] FIG10 is a schematic diagram of another communication method provided in an embodiment of the present application;

[0151] FIG11 is a schematic diagram of another communication method provided in an embodiment of the present application;

[0152] FIG12 is a schematic diagram of another communication method provided in an embodiment of the present application;

[0153] FIG13 is a schematic diagram of another communication method provided in an embodiment of the present application;

[0154] FIG14 is a schematic diagram of a communication device provided in an embodiment of the present application;

[0155] FIG15 is a schematic diagram of another communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0156] The network architecture and business scenarios described in the embodiments of the present application are intended 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 in the embodiments of the present application. Ordinary technicians in this field will know that with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0157] The network architecture and business scenarios described in the embodiments of the present application are intended 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 in the embodiments of the present application. Ordinary technicians in this field will know that with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0158] The terms "first" and "second" in the description and drawings of the embodiments of the present application are used to distinguish different objects, or to distinguish different treatments of the same object. Words such as "first" and "second" can distinguish between identical or similar items with substantially the same functions and effects. For example, the first device and the second device are merely used to distinguish different devices and do not limit their order. Those skilled in the art will understand that words such as "first" and "second" do not limit the quantity and execution order, and words such as "first" and "second" do not necessarily limit differences.

[0159] In the description of the embodiments of the present application, unless otherwise specified, " / " indicates that the objects associated before and after are in an "or" relationship, for example, A / B can represent A or B; "and / or" in the embodiments of the present application is merely a description of the association relationship of associated objects, indicating that three relationships may exist, for example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural.

[0160] In the description of the embodiments of the present application, unless otherwise specified, "at least one" means one or more, and "more than one" means two or more than two. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can mean: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or plural.

[0161] Furthermore, the terms "including," "having," and any variations thereof, mentioned in the description of the embodiments of the present application are intended to cover non-exclusive inclusions. For example, a process, method, system, product, or apparatus comprising a series of steps or units is not limited to the listed steps or units, but may optionally include other steps or units not listed, or may optionally include other steps or units inherent to the process, method, product, or apparatus.

[0162] In the embodiments of this application, words such as "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described as "exemplary" or "for example" in the embodiments of this application should not be construed as being preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner to facilitate understanding.

[0163] It will be understood that the “embodiment” mentioned throughout the specification means that the specific features, structures or characteristics related to the embodiment are included in at least one embodiment of the embodiment of the present application. Therefore, the various embodiments in the entire 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 will be understood that in the various embodiments of the embodiment of the present application, the size of the sequence number of each process does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiment of the present application.

[0164] It can be understood that in the embodiments of the present application, "when" and "if" both mean that corresponding processing will be performed under certain objective circumstances, and do not limit the time, nor do they require any judgment action when implementing, nor do they mean that there are other limitations.

[0165] It is understood that some optional features in the embodiments of the present application may, in certain scenarios, be implemented independently of other features, such as the solution on which they are currently based, to solve corresponding technical problems and achieve corresponding effects. In certain scenarios, they may also be combined with other features as needed. Accordingly, the devices provided in the embodiments of the present application may also implement these features or functions accordingly, which will not be described in detail here.

[0166] In the embodiments of the present application, unless otherwise specified, the same or similar parts between the various embodiments can refer to each other. In the various embodiments of the present application, and the various implementation methods / implementation methods / implementation methods in the various embodiments, if there is no special explanation and logical conflict, the terms and / or descriptions between different embodiments and the various implementation methods / implementation methods / implementation methods in the various embodiments are consistent and can be referenced to each other. The technical features in different embodiments and the various implementation methods / implementation methods / implementation methods in the various embodiments can be combined to form new embodiments, implementation methods, implementation methods, or implementation methods according to their inherent logical relationships. The implementation methods of the embodiments of the present application described below do not constitute a limitation on the scope of protection of the embodiments of the present application.

[0167] FIG1 is an example diagram of the architecture of a communication system provided in an embodiment of the present application.

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

[0169] Terminal 110 and repeater 120 communicate wirelessly, and repeater 120 and network device 130 communicate wirelessly. Network device 130 may be a wireless access network device. Terminals and wireless access network devices may be connected to each other via wired or wireless means. Figure 1 is merely a schematic diagram. The communication system may also include other network devices, such as wireless backhaul equipment and core network equipment, which are not shown in Figure 1. The connection relationships between devices are not limited to the methods listed above.

[0170] The wireless access network device may be a base station, an evolved NodeB (eNodeB / eNB), a transmission reception point (TRP), a next generation NodeB (gNodeB / gNB) in a fifth generation (5G) mobile communication system, a next generation base station in a sixth generation (6G) mobile communication system, a base station in a future mobile communication system, or an access node in a WiFi system, etc.; it may also be a module or unit that performs part of the functions of a base station, for example, a centralized unit (CU) or a distributed unit (DU). The wireless access network device may be a macro base station, a micro base station or an indoor station, a relay node or a donor node, etc. In other embodiments, the wireless access network device may also be an access network device in an open radio access network (O-RAN). In O-RAN, the CU can be referred to as an open CU (O-CU), the DU can be referred to as an open DU (O-DU), and the RU can be referred to as an open RU (O-RU). The embodiments of this application do not limit the specific technologies and device forms used by the radio access network equipment. Radio access network equipment is sometimes also referred to as network equipment. For ease of description, the following description uses a base station as an example of a radio access network equipment.

[0171] A relay may also be referred to as a relay device, relay apparatus, relay node, etc. For example, it may be a wireless relay device. For example, it may be a relay device that has both full access network node functionality and mobile terminal functionality. The embodiments of this application do not limit the specific technology or device form used by the relay.

[0172] A terminal may also be referred to as a terminal device, user equipment (UE), mobile station, mobile terminal, etc. Terminal devices can be widely used 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 wearable, smart transportation, smart city, etc. Terminal devices can be mobile phones, tablet computers, computers with wireless transceiver functions, wearable devices, vehicles, drones, helicopters, airplanes, ships, robots, robotic arms, smart home devices, etc. The embodiments of the present application do not limit the specific technology and specific device form adopted by the terminal devices.

[0173] Base stations, repeaters, and terminals can be fixed or mobile. They can be deployed on land, indoors or outdoors, handheld or vehicle-mounted; on water; or in the air on aircraft, balloons, and satellites. The embodiments of this application do not limit the application scenarios of base stations and terminal devices.

[0174] Communication between base stations and repeaters, between repeaters and terminals, between base stations and base stations, and between terminals can be carried out through authorized spectrum, through unlicensed spectrum, or through both authorized spectrum and unlicensed spectrum at the same time; communication can be carried out through spectrum below 6 gigahertz (GHz), through spectrum above 6 GHz, or through spectrum below 6 GHz and spectrum above 6 GHz at the same time. The embodiments of the present application do not limit the spectrum resources used for wireless communication.

[0175] In an embodiment of the present application, the function of the base station may also be performed by a module (such as a chip) in the base station, or by a control subsystem including a base station function. The control subsystem including the base station function here may be a control center in the application scenarios of the above-mentioned terminal devices such as smart grid, industrial control, intelligent transportation, smart city, etc. The function of the repeater may also be performed by a module (such as a chip or a modem) in the repeater, or by a device including a relay function. The function of the terminal may also be performed by a module (such as a chip or a modem) in the terminal, or by a device including a terminal function.

[0176] A wireless communication system includes communication devices, which can communicate wirelessly using air interface resources. Communication devices can include network devices and terminal devices. Network devices can also be referred to as base station devices. Air interface resources can include at least one of time domain resources, frequency domain resources, code resources, and spatial resources. Communication devices can also be referred to as communication devices.

[0177] The solutions provided in the embodiments of this application can be applied to wireless communications between communication devices. Wireless communications can include wireless communications between network devices and terminals, wireless communications between network devices, and wireless communications between terminals. In the embodiments of this application, the term "wireless communications" can also be simply referred to as "communication," which can also be described as "data transmission," "information transmission," or "transmission."

[0178] The embodiments of the present application can be used for possible communication links such as uplink (UL), downlink (DL), access link, and backhaul link, and the embodiments of the present application are not limited here. From the perspective of business scenarios, the embodiments of the present application are applicable to various scenarios, such as extended reality (XR) business, artificial intelligence (AI) business, large-capacity scenarios, etc., and the embodiments of the present application are not limited here.

[0179] Referring to the VMR scenario shown in Figure 2, assume that a VAM 220 is deployed on a moving vehicle. VAM 220 connects to a host node 230 via wireless backhaul and provides wireless coverage for a terminal 210 within the vehicle. Regarding relay nodes in VAM scenarios, related technologies have proposed using an IAB as a mobile relay node. An IAB node can include a mobile terminal (MT) and a DU. When facing its parent node, the IAB node can function as a mobile terminal, or MT. When facing its child node, the IAB node can function as a network device, or DU. It can be understood that a parent node can be considered the previous-hop node of the IAB node, and a child node can be considered the next-hop node of the IAB node. The parent node of an IAB node can be another IAB node or an IAB host node. The child node of an IAB node can be another IAB node or a terminal device. It can be understood that the terminal 210 in FIG. 2 may be the terminal 110 in FIG. 1 , the VAM 220 may be the repeater 120 in FIG. 1 , and the host node 230 may be the network device 130 in FIG. 1 .

[0180] It is understood that mobile terminal and terminal device have the same meaning and can both be referred to as terminal. To facilitate the distinction between an independent terminal and the terminal function implemented in a relay device, in each embodiment of the present application, an independent terminal is referred to as a terminal device, and the terminal function implemented in a relay device is referred to as an MT.

[0181] The above behavior is taken as an example in conjunction with the IAB scenario shown in Figure 3. The terminal device accesses the IAB-DU of IAB node 1, and the IAB-MT belonging to the same IAB node transmits the terminal device's data back to the IAB-DU of the previous hop, that is, back to the IAB-DU of IAB node 2. The IAB-MT of IAB node 2 then transmits the data back to the IAB-DU of the previous hop, and so on. Until it is transmitted back to the DU of the IAB host node, that is, the donor-DU. Among them, Figure 3 only shows two IAB nodes, and more or fewer IAB nodes can be included according to actual conditions. The embodiment of the present application is not limited here. It is sent by the CU of the IAB host node to the core network node. Among them, a new radio (NR) Uu interface, referred to as the Uu interface, can be established between the terminal device and the IAB node. Among them, the Uu interface is the communication interface between the terminal device and the access network node. It can be understood that communication between different IAB nodes and between the IAB node and the IAB host node is also carried out through the Uu interface. It can be considered that there is a logical F1 interface between the IAB host node and each IAB node. It can also be considered that there is an F1 interface between the CU and DU inside the IAB host node. For details, please refer to the IAB network structure shown in Figure 4. The F1 interface can be considered as a logical interface between the CU of the IAB host node and the DU of each IAB node. The F1 interface is actually still implemented through the Uu interface between each IAB node and the IAB host node. The IAB host node communicates with the access network node through the Xn interface. The core network node communicates with the access network node and the IAB host node through the NG interface. The core network node in Figure 3 is the 5G core network (5g core, 5GC) in Figure 4. For downlink communication, the data sending direction is opposite to the downlink, and the communication process is similar. The embodiments of the present application will not be repeated here.

[0182] The terminal devices in Figures 3 and 4 may be terminal 110 in Figure 1; the IAB nodes and IAB host nodes in Figures 3 and 4 may be relay 120 in Figure 1; and the access network nodes, core network nodes, and IAB host nodes in Figures 3 and 4 may be network devices 130 in Figure 1. It will be appreciated that the IAB host node can be considered as network device 130 when facing an IAB node, and can be considered as relay 120 when facing an access network node or core network node.

[0183] In some examples, the core network node may include an access and mobility management function (AMF) entity, a session management function (SMF) entity, a user plane function (UPF) entity, a sensing service control function (SSCF), a sensing data processing function (SDPF), a unified data management (UDM), and the like.

[0184] Among them, the AMF can be responsible for handling functions related to terminal device authentication and security. For example, the AMF can be responsible for user identity authentication, security policy enforcement, user security configuration, etc. The SMF can be responsible for managing and controlling data sessions of terminal devices. For example, the SMF can be responsible for session management, user policy enforcement, data transmission routing, functional service support, etc. The UPF can be responsible for handling data transmission and traffic management between different terminal devices. For example, the UPF can be responsible for data forwarding, flow control, quality of service (QoS) assurance, data policy processing, etc.

[0185] Of course, the core network node may also include other more or fewer entities, which is not limited in the embodiments of the present application.

[0186] It will be understood that in each embodiment of the present application, “device,” “network element,” “node,” and “entity” can be used interchangeably.

[0187] IAB is a Layer 2 relay, meaning it cannot send higher-layer signaling like RRC. This is because IAB nodes lack CU functionality. They operate below the Packet Data Convergence Protocol (PDCP) layer and lack higher-layer protocol stack functionality.

[0188] In some embodiments, it is considered that relay nodes have complete access network functionality, that is, the CU functionality is introduced. This allows such relay nodes to be considered Layer 3 relays. Of course, such Layer 3 relays also have MT functionality and provide backhaul.

[0189] In related technologies, an LTE relay technology is proposed in a long-term evolution (LTE) communication scenario. Referring to Figure 5 , the relay node (RN) in this scenario can be understood as consisting of a UE and an eNB. The UE portion of the RN can also be referred to as an RN-MT, the eNB portion of the RN can also be referred to as an RN-eNB, and the donor node in this scenario can be referred to as a donor eNB (DeNB). An air interface connection exists between the RN-MT and the DeNB, referred to as the Un interface; the interface through which a terminal device accesses the RN can be the Uu interface. An S1 interface, an S11 interface, and the like can exist between the DeNB and the core network node. The S1 interface can be considered a control plane interface, and the S11 interface a user plane interface. Logical interfaces, such as the X2 interface and the S1 interface, can exist between the RN-eNB and the DeNB. Of course, the X2 interface, the S1 interface, and the like between the RN-eNB and the DeNB are actually implemented using data radio bearers (DRBs) on the Un interface. The RN, donor node, and access network node in FIG5 may be considered to belong to an evolved universal terrestrial radio access network (E-UTRAN).

[0190] In the scenario shown in Figure 5, the RN accesses the DeNB, and the RN is invisible to the adjacent access network nodes or core network nodes. For the RN, the DeNB can be regarded as a core network node, in which case it can correspond to the S1 interface; or it can be regarded as an eNB, in which case it corresponds to the X2 interface. The core network node needs to use the S1 interface with the DeNB, or the access network node needs to use the X2 interface with the DeNB to update the process in order to discover some cells managed by the DeNB. However, the core network node and the access network node will not be aware of the RN accessing the DeNB. For example, when a new RN accesses the DeNB, the access network node or the core network node can discover some new cells added by the DeNB through the interface update process. These new cells are actually the cells corresponding to the new RN, but the access network node or the core network node cannot perceive the new RN and instead thinks that the DeNB has added some new cells.

[0191] For a terminal device connected to the RN, after the message sent by the terminal device reaches the DeNB, the DeNB will update the information of both the sender and receiver of the message. Taking the X2 interface as an example, there is an X2 interface between the RN-eNB and the DeNB, and there is an X2 interface between the DeNB and other access network nodes. When the DeNB receives an A message from the RN-eNB that it wants to send to the access network node 1, the DeNB retains the main content of the A message and modifies the sender identifier, the transport layer address of the sender, and the general packet radio service tunneling protocol (GTP)-user plane (U) tunnel endpoint identifier (TEID) of the sender in the message to its own node. Among them, the A message can be an X2 application protocol (AP) message, and the sender identifier can be an X2AP UE identifier (ID). The receiver identifier, the transport layer address of the receiver, and the GTP-U TEID of the receiver still remain those of the access network node 1. The DeNB forwards the X2AP message generated by the RN-eNB through the X2AP message with the access network node 1. Similarly, for user-plane communications, X2-U data sent by the RN to access network node 1 can be sent to the DeNB via the GTP-U tunnel carried on the Un interface. The DeNB then sends the data to access network node 1 via the GTP-U tunnel between the DeNB and access network node 1. In other words, the DeNB needs to maintain a correspondence between the GTP-U tunnel between the RN and DeNB and the GTP-U tunnel between the DeNB and access network node 1. In other words, the DeNB needs to maintain a correspondence between the two GTP-U tunnels. This allows the DeNB, acting as a transit point, to complete data communication between the RN and access network node 1.

[0192] As for the access network node 1, the access network node 1 believes that what it has received is the X2-U data from the DeNB, and does not perceive the RN.

[0193] In the embodiments of the present application, a relay node with complete access network node functions and MT functions is introduced based on a 5G communication network. For example, such a relay node can be called a wireless access and backhaul (WAB) node. Of course, a relay node with complete access network functions and MT functions can also be called an NR RN, a 5G RN, etc. The embodiments of the present application do not limit the specific names of such relay nodes.

[0194] Next, the embodiments of the present application are described by taking a relay node with complete access network node functions and MT functions, which is called a WAB node, as an example.

[0195] Referring to the network structure shown in Figure 6, a WAB node can include complete access network node functions, such as gNB functions, as well as MT functions. In a CU / DU separation architecture, gNB functions can be implemented by combining CU functions with DU functions. Terminal devices can access the WAB-gNB via NR, such as via the Uu interface. For the WAB node, the WAB-MT can encapsulate control plane data or user plane data sent by the terminal device in a WAB-MT protocol data unit (PDU) session. The WAB-MT sends this data to the host node via the Uu interface, which then forwards it to the WAB-MT's core network node, such as the WAB-MT's UPF. The Uu interface between the WAB-MT and the host node corresponds to the backhaul link. An NG interface can exist between the host node and the AMF in the WAB core network. The WAB-MT's UPF can parse the packet header information of the data sent by the MT to obtain a packet header related to the terminal device. The data is then sent to the terminal device's core network node, such as the terminal device's AMF, SMF, or UPF, based on Internet Protocol (IP) routing. The core network nodes of the terminal device represent those core network nodes that provide services to the terminal device. The core network nodes of the WAB-MT represent those core network nodes that provide services to the WAB-MT. In some examples, the core network node of the terminal device and the core network node of the WAB-MT can be the same node or different nodes, which is not limited in this embodiment of the present application.

[0196] Logically speaking, a non-access stratum (NAS) connection can be considered to be established between the terminal device and the AMF of the terminal device for sending control plane data. A PDU session is established between the terminal device and the UPF of the terminal device, namely the access PDU conversation in Figure 6, for sending user plane data. Among them, the above two types of data are wrapped in the PDU session of WAB-MT and sent to the core network node of the terminal device. The PDU session of WAB-MT is the backhaul (BH) PDU conversation in Figure 6. Among them, the BH PDU conversation can be realized through communication between WAB-MT and the host node, and communication between the host node and the UPF of the WAB core network.

[0197] In contrast, in an IAB network, although the IAB-MT backhauls the end-device data, this data is not encapsulated in the IAB-MT PDU session. Instead, it is carried directly on the IAB-MT Layer 2 logical channel and reaches the IAB-donor through hop-by-hop logical channel mapping. The IAB-donor sees the end-device data. In a WAB network, however, the end-device data is directly encapsulated in the WAB-MT PDU session. During the WAB-MT backhaul process, this data is treated as the WAB-MT's own user-plane data. It is then backhauled to the WAB-donor via the WAB-MT's DRB. The WAB-donor sees the WAB-MT data, not the end-device data. This data is not sent to the WAB-MT UPF until the WAB-MT-related packet headers are parsed, resulting in the packet header information specific to the end-device, which is then forwarded to the end-device's core network node.

[0198] Of course, the interface-level data communication process between the WAB-gNB and the core network node of the terminal device is similar to the communication process between the terminal device and the core network node of the terminal device in the WAB network. It also needs to be sent to the UPF of the WAB-MT through the PDU session of the WAB-MT, and then routed to the core network node of the terminal device. For the convenience of description, the embodiment of this application will not be repeated here.

[0199] In some embodiments, the WAB node is a layer 3 architecture, and the access link and backhaul link of the WAB node can be decoupled from each other. Among them, the link between the terminal device and the WAB node can be called an access link, and the link between the WAB node and the WAB-donor can be called a backhaul link. Unlike the IAB node, the access link and the backhaul link need to be controlled by the IAB-donor-CU and need to belong to the same operator. For example, the same public land mobile network (PLMN) needs to be configured. For the WAB node, the operators of the access link and the backhaul link are different. For example, the WAB node is deployed on an aircraft. The access link can be operated by operator A, and the backhaul link corresponding to the WAB-MT can be operated by operator B. In this way, the terminal device on the aircraft does not have to be a subscriber of operator B, and the interaction between the terminal device and the core network node can be completed. This is more conducive to flexible deployment and stimulates more diversified business models.

[0200] In the next-generation radio access network (NG-RAN), NG-RAN nodes are typically fixed nodes, or considered static nodes. For a given NG-RAN node, its adjacent NG-RAN nodes and core network nodes are also fixed. Based on pre-configuration, an NG-RAN node can obtain the IP addresses of itself, adjacent NG-RAN nodes, and core network nodes to establish corresponding Xn and N2 interfaces. The N2 interface is also referred to as the NG interface.

[0201] In the WAB network architecture, backhaul links are implemented using WAB-MT PDU sessions. WAB-donors do not perform proxy-like processing on the DRB data in these backhaul PDU sessions. Furthermore, given the mobility of WAB nodes, their neighboring access and core network nodes are not static. Consequently, WAB nodes cannot correctly establish logical interfaces with other access and core network nodes.

[0202] Therefore, the present application provides a communication method, by configuring address information for a first relay node including an MT and an access network node, so that a communication interface between the first relay node and adjacent access network nodes and / or core network nodes can be established based on the address information to improve communication efficiency.

[0203] FIG7 is a flow chart of a communication method provided in an embodiment of the present application.

[0204] As shown in Figure 7, the communication process can be applicable to but not limited to the communication scenarios shown in Figures 1, 2, and 6. The method can be applied to a first relay node and a network device. The first relay node can be the relay mentioned above. The first relay node can include a first MT and a first access network node. In some examples, the first relay node can also be considered to include a first functional entity and a second functional entity. The first functional entity is used to implement the MT function, and the second functional entity is used to implement the complete function or all functions of the access network. It can be understood that the first MT and the first access network node in the first relay node can be two different functional modules in one device, or two independent devices. The first access network node can be composed of a CU and a DU, and the CU and the DU can be two different functional modules in one device, or two independent devices. This application does not limit the specific implementation method of the first MT and the first access network node in the first relay node.

[0205] In some examples, the first relay node may be referred to as a WAB node. Of course, the first relay node may also be referred to as any other possible name, which is not limited in the embodiments of the present application. The method may include the following steps: the network device sends first information to the first relay node; the first relay node sends second information to the first core network node and / or the adjacent access network node based on the first information. Specifically:

[0206] S101: A network device sends first information to a first relay node.

[0207] Correspondingly, the first relay node receives the above-mentioned first information.

[0208] In some embodiments, the network device determines the first information and sends the first information to the first intermediate node. The first relay node may receive the first information determined by the network device from the first intermediate node. In other words, the first information may be indirectly sent to the first relay node via forwarding by the first intermediate node. In some examples, the first intermediate node may be a host node of the first relay node or other possible network device. It will be understood that the first intermediate node may be any network device capable of forwarding the first information. In other embodiments, the first relay node may directly receive the first information sent by the network device.

[0209] In some embodiments, the first relay node includes a first mobile equipment (MT) and a first access network node. Taking the first relay node as a WAB as an example, the first MT can be referred to as a WAB-MT, and the first access network node can be referred to as a WAB-gNB. In other embodiments, the first relay node can also include some UPF functions so that the first relay node has more service functions, such as edge computing and perception. In some examples, the first relay node can also be referred to as a mobile WAB node. The embodiments of the present application do not limit the name of the first relay node.

[0210] In some embodiments, the first information can be used to indicate at least one piece of address information. The at least one piece of address information can be used to establish a first communication interface and / or a second communication interface. For example, the address information can be address information used to uniquely identify an entity, device, or unit. For example, the address information can be any possible network protocol address, transport layer information, identification information, and the like. In some examples, the address information can be an IP address. It will be understood that the embodiments of the present application are described using the IP address as an example of address information, and of course, it can be replaced with any possible address information used to uniquely identify an entity, device, or unit according to actual circumstances, and the embodiments of the present application are not limited thereto.

[0211] The first communication interface may be a communication interface between the first access network node and the first core network node. For example, if the first relay node is a WAB, the first communication interface may be a communication interface between the WAB-gNB and the first core network node. The first core network node may be a core network node that provides communication services to terminal devices accessing the first relay node. In other words, the first core network node may be referred to as a core network node for terminal devices. Of course, the terminal devices referred to here are terminal devices accessing the first relay node. For example, terminal devices accessing the WAB-gNB via an air interface. In some examples, the first communication interface may also be referred to as an NG interface or an N2 interface. The second communication interface may be a communication interface between the first access network node and an adjacent access network node. For example, if the first relay node is a WAB, the first communication interface may be a communication interface between the WAB-gNB and the adjacent access network node. In some examples, the first communication interface may be referred to as an NG interface. In some examples, the second communication interface may also be referred to as an Xn interface.

[0212] Referring to Figure 8 , the logical interface between the first access network node and the first core network node in the first relay node is a first communication interface. The logical interface between the first access network node and an adjacent access network node in the first relay node is a second communication interface. In some examples, the first host node, which is the host node of the first relay node, also has complete access network node functionality. Therefore, the first host node can be considered an adjacent access network node of the first relay node. A second communication interface can also be established between the first access network node and the first host node. For example, if the first relay node is a WAB node, the first host node can be a WAB-donor.

[0213] At the same time, a first PDU session can be established between the terminal device and the first core network node in Figure 8, and the first PDU session can be called a UE PDU session. For example, the first PDU session can be the access PDU session in Figure 6. For another example, the second core network node may include a UPF that provides business data services to the first MT, and a second PDU session can be established between the first MT in the first relay node and the UPF of the first MT. The second PDU session can be called an MT PDU session. For example, the second PDU session can be the BH PDU session in Figure 6. There can also be an Xn interface between the first host node and the adjacent access network node. The specific implementation method can refer to the process of establishing an interface between access network nodes in the relevant technology, and the embodiments of the present application will not be repeated here. For the interface between some nodes in Figure 8, refer to the relevant description in Figure 6.

[0214] In some examples, the first information may include a first IP address. The first IP address is the IP address of the first access network node. The first IP address is used to establish the first communication interface and / or the second communication interface. For example, if the first relay node is a WAB, the first IP address may be the IP address of the WAB-gNB. In some examples, the first IP address may be an unencrypted IP address, an encrypted IP address, or the encrypted IP address of the corresponding gateway.

[0215] In some examples, the first information may include one or more first IP addresses. For example, the multiple first IP addresses may include a first IP address used to establish a first communication interface and / or a first IP address used to establish a second communication interface. For example, the first IP address may include a first IP address used to establish an NG interface and a first IP address used to establish an Xn interface; or, the first IP address may include multiple first IP addresses used to establish an NG interface or an Xn interface, and so on.

[0216] For another example, the multiple first IP addresses may include a first IP address for establishing a first communication interface and / or a second communication interface related to the user plane, and a first IP address for establishing a first communication interface and / or a second communication interface related to the control plane. For example, a first IP address for establishing an NG-U interface and / or an Xn-U interface, and a first IP address for establishing an NG-C interface and / or an Xn-C interface.

[0217] For another example, the multiple first IP addresses may include a first communication interface for establishing a user plane, a first IP address for establishing a second communication interface for establishing a user plane, a first communication interface for establishing a control plane, and a first IP address for establishing a second communication interface for establishing a control plane. For example, the first IP address for establishing an NG-U interface, the first IP address for establishing an Xn-U interface, the first IP address for establishing an NG-C interface, and the first IP address for establishing an Xn-C interface.

[0218] In other examples, the first information may include a second IP address. The second IP address is the IP address of a neighboring access network node. The second IP address is used to establish a second communication interface. The neighboring access network node (neighbor gNB) may be an access network node adjacent to the first relay node, such as an access network node adjacent to a WAB-gNB. The definition of neighboring may be determined by physical distance, such as access network nodes within a range of A1 meters or A2 kilometers around the WAB-gNB. Alternatively, the definition of neighboring may be determined by the number of hops of the network node, such as access network nodes that can be reached within A3 hops with the WAB-gNB as the initial device. Of course, neighboring may also be determined by any other feasible method, which may be specifically determined by referring to relevant technologies or setting according to actual conditions, and is not limited in the embodiments of the present application.

[0219] In some examples, the first information may include one or more second IP addresses. For example, the multiple second IP addresses may include the second IP addresses of one or more adjacent access network nodes used to establish a second communication interface related to the user plane, and the second IP addresses of one or more adjacent access network nodes used to establish a second communication interface related to the control plane, such as a second IP address used to establish an Xn-U interface and a second IP address used to establish an Xn-C interface.

[0220] In some other examples, the first information may include a first IP address and a second IP address. For example, the first information may include one or more first IP addresses and one or more second IP addresses. For specific implementations, reference may be made to the descriptions of the embodiments related to the first IP address and the second IP address, and the present embodiments will not be further elaborated herein.

[0221] The embodiment of the present application can provide the IP address of the first relay node and / or the IP address of the adjacent access network node, so that the first relay node can accurately establish a logical interface with the first core network node and / or the adjacent access network node based on the above address information.

[0222] In some embodiments, the network device may be one or more of: a network management device, a second core network node, a first core network node, a first host node, and a radio access network intelligent controller (RIC).

[0223] In some examples, the network device may be a network management device. For example, the network management device may be an operations administration and maintenance (OAM) entity. The network management device may be considered a network management device for the first relay node and may be responsible for managing and maintaining the first relay node. For example, the OAM determines the first information and sends the first information to the first relay node.

[0224] In other examples, the network device may be a second core network node. The second core network node may be a core network node that provides communication services to the first relay node. For example, if the first relay node is a WAB node, the second core network node may be a core network node that provides communication services to a WAB-MT, and may also be referred to as a WAB-MT core network node. For example, the WAB-MT core network node determines first information and sends the first information to the first relay node.

[0225] In some further examples, the network device may be a first core network node. For example, the core network node of the terminal device determines the first information and sends the first information to the first relay node.

[0226] It is understandable that the core network nodes involved in each embodiment of the present application, such as the first core network node and the second core network node, can be used to perform authentication, mobility association, PDU session management, etc. for the corresponding terminal. For example, it can include functional entities or network elements such as AMF, SMF, and UPF.

[0227] In some further examples, the network device may be a first host node. The first host node may be a host node of a first relay node. For example, if the first relay node is a WAB node, the first host node may be a WAB-donor. For example, the first host node may be considered a donor gNB that supports access to the first relay node. The first host node may be used to backhaul service data of a first mobile station in the first relay node. For example, the first host node may forward data sent by the first mobile station to a core network node of the first mobile station. In some examples, the WAB-donor may determine first information and send the first information to the first relay node.

[0228] In some other examples, the network device may be a RIC. For example, the RIC determines the first information and sends the first information to the first relay node.

[0229] In yet other embodiments, the network device that determines the first information may include: a network management device and a second core network node; a network management device, a second core network node, and a first host node; a network management device, a second core network node, a first core network node, and a first host node; a network management device, a second core network node, a first core network node, a first host node, and a RIC. Of course, the above example is only one possible combination, and the network device may also include any two, three, or four of the above items, which are not limited in this embodiment of the present application. It is understood that the different network devices described above may be used to determine different first information. For example, the network management device may be used to determine the first IP address, and the first host node may be used to determine the second IP address. For another example, the network management device may be used to determine the first IP address of the user plane, the second core network node may be used to determine the first IP address of the control plane, and the first host node may be used to determine the second IP address of the control plane, and so on.

[0230] In various embodiments of the present application, during communication between a first relay node and a network device, the communication data may be forwarded via a first intermediate node. The first intermediate node may be any network device other than the network device communicating with the first relay node. For example, if the first relay node communicates with a second core network node, the first host node may be the first intermediate node; for another example, if the first relay node communicates with a first core network node, the first host node may be the first intermediate node, and the second core network node may also be the first intermediate node; for another example, if the first relay node communicates with a first core network node, the first host node may be the first intermediate node, the second core network node may also be the first intermediate node, the RIC may also be the first intermediate node, and so on. It will be understood that the above description of the first intermediate node is merely a limited example. The specific form of the first intermediate node may be adaptively selected based on the specific network device with which the first relay node communicates, and the embodiments of the present application do not limit this.

[0231] The embodiments of the present application provide a variety of network devices for determining the first information to be applicable to different network scenarios. In the corresponding network scenarios, the address information can be configured for the first relay device through appropriate network devices.

[0232] In some examples, during communication between the first relay node and other nodes, the first relay node may send data to the anchor point, which may then be forwarded to the other nodes via the anchor point. Conversely, data sent by other nodes may first be sent to the anchor point, which may then be forwarded to the first relay node by the anchor point.

[0233] In some embodiments, the anchor point corresponding to the first IP address is a second core network node. For example, the second core network node can be used as the anchor point corresponding to the first IP address. For example, the core network node of the WAB-MT can be used as the anchor point corresponding to the IP address of the WAB-gNB. In some examples, for any of the possible network devices mentioned above, the anchor point corresponding to the first IP address determined by the device can be the second core network node. In other examples, for any of the possible network devices mentioned above, except the first host node, the anchor point corresponding to the first IP address determined by the device can be the second core network node.

[0234] In some examples, the anchor point is a first IP address of the second core network node, which can be used to establish the first communication interface and / or the second communication interface.

[0235] In other embodiments, the anchor point corresponding to the first IP address is the first host node. For example, the first host node can be used as the anchor point corresponding to the first IP address. For example, the WAB-donor can be used as the anchor point corresponding to the IP address of the WAB-gNB. In some examples, the anchor point corresponding to the first IP address determined by any of the possible network devices mentioned above can be the first host node.

[0236] In some further embodiments, when the first information includes multiple first IP addresses, the multiple first IP addresses may include a first IP address corresponding to the second core network node as the anchor point, and a first IP address corresponding to the first host node as the anchor point.

[0237] In some examples, the anchor point is a first IP address of the first host node, which can be used to establish the second communication interface.

[0238] It can be understood that in this way, the second core network node and / or the first host node serving as the anchor point can maintain the corresponding relationship between the first access network node and the first MT. That is, when the second core network node and / or the first host node receives data sent to the first access network node, it can determine, based on the corresponding relationship, which PDU session or radio bearer with which first MT to backhaul. Among them, the radio bearer may include a DRB, a signaling radio bearer (SRB), etc.

[0239] The embodiment of the present application provides possible situations of multiple anchor points of the first IP address, so that in the communication scenarios between the first relay node and different nodes, the first IP address corresponding to the appropriate anchor point can be configured for the first relay node, thereby improving the communication efficiency between the first relay node and other nodes.

[0240] In some examples, the first IP address and the IP address of the anchor point are in the same IP network segment, or the first IP address is the IP address of the anchor point.

[0241] For example, the first IP address may have the same IP network segment as the anchor point's IP address. Assume the anchor point's IP address is 192.168.xx and the first IP address is 192.168.yy. Clearly, the first IP address and the anchor point's IP address have the same network segment, "192.168." It can be understood that because the first IP address and the anchor point's IP address have the same network segment, the first access network node of the first relay node, such as the WAB-gNB, can be found through the anchor point.

[0242] For another example, the IP address of the anchor point can be directly used as the first IP address. In this case, the first IP address can be considered the gateway IP address of the first access network node. Data from other nodes is sent to the anchor point based on the first IP address, and can be forwarded by the anchor point to the first access network node. It is understood that in this case, the actual IP address of the first access network node can be stored in the anchor point.

[0243] The embodiments of the present application provide multiple relationships between the first IP address and the IP address of the anchor point, so that the first IP address can be configured in an appropriate manner in different communication scenarios.

[0244] In some implementations, before the network device sends the first information to the first relay node, the first relay node may send third information to the network device. The third information is used to request the network device to obtain the first information. The network device may determine the first information based on the third information and send the first information to the first relay node.

[0245] In other words, one scenario is that the network device proactively sends the first information to the first relay node. For example, when the first relay node joins the network, the network device may be triggered to send the first information to the first relay node. For another example, the network device may send the first information to the first relay node at certain specific times. Of course, in other scenarios, the first relay node may request the first information from the network device. For example, the first relay node may send third information to the network device, requesting the network device to configure the first information for the first relay node. The network device may generate the first information based on the first relay node's request and send the first information to the first relay node.

[0246] In the embodiment of the present application, the first relay node may actively request to obtain the first information, thereby configuring address information for the first relay node more flexibly.

[0247] In some embodiments, when the first information includes the first IP address, the third information also includes: identification information of the second core network node and / or identification information of the first host node. For example, the third information includes the identification information of the second core network node. In this case, the first IP address obtained by the first relay node may have its anchor point be the second core network node. For another example, the third information includes the identification information of the first host node. In this case, the first IP address obtained by the first relay node may have its anchor point be the first host node. Of course, if the third information includes the identification information of the second core network node and the identification information of the first host node, the first relay node may obtain multiple first IP addresses. The multiple first IP addresses may include a first IP address whose anchor point is the second core network node and a first IP address whose anchor point is the first host node.

[0248] In some examples, taking the network device as a network management device, such as an OAM, and taking the first relay node as a WAB node and the network device as an OAM, the WAB node may send identification information of a core network node serving the WAB-MT and / or identification information of a WAB-donor to the OAM.

[0249] For example, the identification information of the core network node serving WAB-MT may include one or more of the following: identification information of the AMF serving WAB-MT; identification information of the SMF serving WAB-MT; identification information of the UPF serving WAB-MT; IP address of the UPF serving WAB-MT; GTP-U TEID assigned by the UPF serving WAB-MT; data network name (DNN); UE NGAP ID assigned to WAB-MT by the AMF serving WAB-MT; subscription permanent identifier (SUPI) of WAB-MT, permanent equipment identifier (PEI) of WAB-MT; 5G globally unique temporary identifier (5G-GUTI) of WAB-MT; PDU session ID of WAB-MT. Among them, NGAP can be considered as an AP message sent on the NG interface. In some examples, the identification information of the AMF serving the WAB-MT may include a globally unique AMF ID (GUAMI).

[0250] For another example, the identification information of the WAB-donor may include one or more of the following: the gNB ID of the WAB-donor; the NR cell global identifier (NCGI) of the WAB-donor management cell; the physical cell identifier (PCI) of the WAB-donor management cell; the tracking area identity (TAI) to which the WAB-donor belongs; and the IP address of the WAB-donor.

[0251] In each embodiment of the present application, the identifier involved may be an identity or an index.

[0252] In some examples, the first relay node sends the OAM any one or more of the aforementioned identification information of the core network node serving the WAB-MT, and the OAM can determine the first IP address based on this information. The anchor point for the first IP address can be a core network node of the WAB-MT, such as the UPF serving the first MT. In this case, NG data and / or Xn data sent by the WAB-gNB can be forwarded through the WAB-MT's UPF.

[0253] In other examples, the first relay node sends any one or more of the aforementioned WAB-donor identification information to the OAM, and the OAM can determine the first IP address based on this information. The anchor point for the first IP address can be the WAB-donor. In this case, the Xn data sent by the WAB-gNB can be forwarded via the WAB-donor.

[0254] In some possible ways, the first relay node can forward the third information to the network management device through the first host node, and the network management device can determine the first IP address based on the third information. In this case, the network management device can send the first IP address directly to the first relay node. Alternatively, the network management device can send the first IP address to the first host node, and the first host node forwards the first IP address to the first relay node. It can be understood that in this case, the first host node is the first intermediate node mentioned above. For example, the first host node can indicate the first IP address to the first MT through an RRC message, and the first access network node can obtain the first IP address through internal interaction of the first relay node. Of course, the first intermediate node can also be other network devices for forwarding the third information and / or the first IP address. For details, please refer to the aforementioned description of the first intermediate node, and the embodiments of the present application will not be repeated here.

[0255] In other examples, the network device is a second core network node. For example, the first relay node is a WAB node, and the network device is a WAB-MT core network node. The WAB-MT core network node can determine its own first IP address as the anchor point based on its own node. The WAB-MT core network node can also determine the first IP address of the WAB-donor as the anchor point based on the WAB-donor's identification information.

[0256] For example, WAB-MT can provide the identification information of the WAB-donor to the core network node of WAB-MT through an uplink NAS message. Or the WAB-donor provides the identification information of its own node to the core network node of WAB-MT. In some cases, when the WAB-gNB determines that an Xn interface needs to be established with an adjacent access network node, the WAB-MT can be triggered to send the identification information of the WAB-donor to the core network node of WAB-MT. For another example, the identification information of the WAB node can be provided to the core network node of WAB-MT when WAB-MT joins the network. The identification information can be a WAB indication. WAB-donor can also report the user location information (ULI) of WAB-MT. The core network node of WAB-MT can determine the current service cell identification of WAB-MT, the TAI to which WAB-MT belongs, and other information based on the identification information of the WAB node and the ULI of WAB-MT, that is, determine the identification information of the WAB-donor.

[0257] In some cases, the core network node of the WAB-MT can directly determine the first IP address of the WAB-donor based on the WAB-donor's identification information. For example, the AMF of the WAB-MT can directly determine the first IP address of the WAB-donor based on the WAB-donor's identification information. In another example, the AMF of the WAB-MT can forward the WAB-donor's identification information to the SMF of the WAB-MT or the UPF of the WAB-MT, and the SMF of the WAB-MT or the UPF of the WAB-MT can determine the first IP address of the WAB-donor based on the WAB-donor's identification information. In this case, the SMF of the WAB-MT or the WAB-MT sends the determined first IP address to the AMF of the WAB-MT. In another example, the AMF of the WAB-MT can obtain the first IP address of the WAB-donor based on the WAB-donor's identification information indicated by the WAB-MT from the WAB-donor. In this case, the first IP address is determined by the WAB-donor. The identification information of the WAB-donor indicated by the WAB-MT is the identification information of the WAB-donor provided by the WAB-MT to the core network node of the WAB-MT in various ways in the above example.

[0258] In some examples, the WAB-MT's core network node can directly send its determined first IP address to the WAB-MT via a downlink NAS message. In other examples, the WAB-MT's core network node can indicate its determined first IP address to the WAB-donor via an NGAP message. The WAB-donor can then indicate the first IP address to the WAB-MT via an RRC message. For the WAB node, the first IP address can be transmitted to the WAB-gNB through internal interaction within the WAB node.

[0259] In some other examples, the network device is a first core network node. For example, the first relay node is a WAB node, and the network device is a core network node of a terminal device. The WAB node can send identification information of the core network node serving the WAB-MT and / or identification information of the WAB-donor to the core network node of the terminal device.

[0260] For example, the WAB node can forward the identification information of the core network node serving the WAB-MT, and / or the identification information of the WAB-donor, to the core network of the terminal device through the core network of the WAB-MT, so that the core network of the terminal device can determine the first IP address based on the above information. The implementation process of the core network of the terminal device determining the first IP address can refer to the embodiment corresponding to the network device being a network management device. For the convenience of description, the embodiments of the present application will not be repeated here. In some examples, the core network of the terminal device can send the first IP address it determines to the core network of the WAB-MT. And indicate it to the WAB node through the core network of the WAB-MT. The implementation process of the core network of the WAB-MT indicating the first IP address to the WAB node can refer to the description of the above-mentioned related examples.

[0261] In other examples, the network device is a first host node. For example, the first relay node is a WAB node and the network device is a WAB-donor. The WAB node can send identification information of a core network node serving the WAB-MT to the first host node. The WAB-donor can determine, based on the identification information of the core network node serving the WAB-MT, that the anchor point is the first IP address of the core network node of the WAB-MT.

[0262] For example, the WAB-donor may also determine the anchor point as its own first IP address based on its own node.

[0263] For example, the WAB-donor may determine, based on the fourth information sent by the WAB-gNB to the neighboring access network node, that the anchor point is located in the core network of the WAB-MT and / or the first IP address of the WAB-donor. The fourth information may be used to indicate a request to establish the first communication interface and / or the second communication interface. For example, the fourth information may be an Xn setup request. In some examples, the fourth information may be the first Xn setup request sent by the WAB-gNB to the neighboring access network node. Alternatively, the WAB-MT may send a request requesting the WAB-donor to allocate the first IP address to the WAB-gNB via an RRC message. Based on this request, the WAB-donor determines that the anchor point is located in the core network of the WAB-MT and / or the first IP address of the WAB-donor. The WAB-donor may send its determined first IP address to the WAB node.

[0264] For another example, when the WAB-donor determines that a WAB node has joined the network, the WAB-donor determines that the anchor point is located in the core network of the WAB-MT and / or the WAB-donor's first IP address. The WAB-donor may indicate the first IP address to the WAB-MT via an RRC message. Alternatively, when the WAB-donor determines that an Xn interface has been established with the WAB-gNB, the WAB-donor may indicate the first IP address to the WAB-gNB via an RRC message or an XnAP message. In this case, the Xn interface between the WAB-donor and the WAB-gNB may be preconfigured.

[0265] In some examples, if the fourth information is sent to other access network nodes, such as access network nodes other than the WAB-donor and the WAB-gNB, the WAB-donor can determine the first IP address upon receiving the fourth information. The WAB-donor can also replace the source IP address in the fourth information with the first IP address. The WAB-donor can forward the information with the updated IP address to other access network nodes. Optionally, the WAB-donor can also indicate the determined first IP address to the WAB-gNB via an RRC message or an XnAP message.

[0266] The network device of the embodiment of the present application can also dynamically configure the first IP address when forwarding the interface establishment information and replace the source IP address of the interface establishment information with a new IP address. This can ensure normal communication after the subsequent interface is established and avoid interface establishment failure caused by IP address errors.

[0267] In some other examples, taking the network device as an RIC, for example, the first relay node is a WAB node and the network device is a RIC, the WAB node may send identification information of a core network node serving the WAB-MT and / or identification information of a WAB-donor to the RIC.

[0268] For example, the WAB node can send the identification information of the core network node serving the WAB-MT and / or the identification information of the WAB-donor to the RIC. In one case, the RIC can determine the first IP address based on the above information. The implementation process of the RIC determining the first IP address can refer to the embodiment corresponding to the network device being a network management device. For the convenience of description, the embodiments of this application will not be repeated here. In another case, the RIC can act as a forwarding device to forward the identification information of the core network node serving the WAB-MT and / or the identification information of the WAB-donor to other network devices, such as the network management device, the first core network node, the second core network node, the first host node, etc. The first IP address is then determined by the other network devices. The first IP address can be sent directly to the WAB node by the network device or forwarded to the WAB node via the RIC. The specific process of determining the first IP address can refer to the embodiment corresponding to the determination of the first IP address by the corresponding network device. The embodiments of this application will not be repeated here.

[0269] The embodiment of the present application can send identification information of different nodes so that the network device can determine a more appropriate anchor point based on the identification information to configure an appropriate first IP address.

[0270] In some embodiments, when the first information includes the second IP address, the network device may configure the second IP address and / or an identifier of a neighboring access network node for the first relay node. The identifier of the neighboring access network node may be an ID of another gNB. For example, the network device may be an OAM.

[0271] In some examples, the network device may also configure a second IP address and / or an identifier of an adjacent access network node for the first relay node based on the third information. For example, the third information sent by the first relay node may include the first identifier.

[0272] In some embodiments, when the first information includes a second IP address, the first relay node may obtain a first identifier. The first identifier may be a cell identifier of a cell managed by the adjacent access network node, or the first identifier may be an identifier of the adjacent access network node. The first relay node may send the obtained first identifier. The first identifier may be used to request the IP address of the adjacent access network node corresponding to the first identifier. That is, the first identifier may be used to request the second IP address corresponding to the first identifier.

[0273] In some examples, the first relay node can directly measure the first cell to obtain the first identifier. The first cell can be a cell managed by an adjacent access network node. For example, the WAB-MT can measure the first cell. In some examples, the WAB-donor can instruct the WAB-MT to measure the first cell through an RRC message when receiving the identity identifier of the WAB node sent when the WAB node accesses. In other words, it can be considered that the WAB-donor configures the measurement for the WAB-MT through an RRC message. The WAB-MT measures the first cell based on the RRC message for indicating cell measurement. In other examples, the WAB-MT can measure the first cell when it determines to establish a second communication interface with the adjacent access network node.

[0274] For example, the first identifier may include a cell identifier of a cell managed by the adjacent access network node. For example, the PCI, NCGI, etc. of the cell managed by the adjacent access network node. For another example, the first identifier may include an identifier of the adjacent access network node. For example, the ID of the adjacent gNB.

[0275] For example, the WAB-MT can use the automatic neighbor relation (ANR) feature to obtain the neighboring cell's NCGI from neighboring cell broadcasts. For another example, if the broadcast includes the gNB ID length, the WAB-MT can determine the gNB ID of the neighboring cell based on the neighbor's NCGI and the gNB ID length.

[0276] In other examples, the first identifier can be measured by a terminal device, and the terminal device transmits the measured first identifier to the first relay node. It is understood that the terminal device is a terminal device connected to the first access network node. The terminal device can also be measured and configured by the first access network node. The specific implementation method is similar to the configuration of a WAB-donor for a WAB-MT and will not be further described in this embodiment of the application.

[0277] The embodiments of the present application provide multiple methods for measuring the first identifier, so that the first identifier can be measured in an appropriate manner in different scenarios, thereby improving universality.

[0278] In some examples, the first relay node may send a first identifier to a network management device, a first host node, a second core network node, and / or a first core network node. This allows the network management device, the first host node, the second core network node, and / or the first core network node to configure a second IP address and inform the first relay node of the second IP address. The first identifier may be known or unknown to the first relay node. If the first relay node already knows certain first identifiers, it can be considered that the first relay node recognizes these first identifiers. For example, some first identifiers are pre-recorded in the first relay node. Conversely, a first identifier not recorded in the first relay node can be considered as a first identifier that the first relay node does not recognize.

[0279] For example, the WAB node sends all first identifiers to the OAM, which determines the second IP address and feeds it back to the WAB node.

[0280] For another example, the WAB-MT sends the first identifier to the WAB-donor via an RRC message. The WAB-donor then obtains the second IP address from the OAM. Alternatively, the WAB-donor directly obtains the second IP address from a neighboring access network node. The WAB-donor can obtain the second IP address from a neighboring access network node that is reachable via XnAP or IP routing.

[0281] It is understood that XnAP reachability can be considered to mean that there is an Xn interface between the WAB-donor and the adjacent access network node. IP route reachability can be considered to mean that the WAB-donor can communicate with the adjacent access network node via the IP address. In other words, it can be considered that the network connection between the WAB-donor and the adjacent access network node is unobstructed, as measured by an Internet packet groper (ping).

[0282] For another example, WAB-MT sends the first identifier to WAB-donor through an RRC message. WAB-donor forwards the first identifier to the core network of WAB-MT through an NGAP message. For example, the transfer can be configured through the uplink radio access network (RAN). The core network of WAB-MT can obtain the second IP address from OAM, or the core network of WAB-MT can obtain the second IP address from an adjacent access network node. The core network of WAB-MT can feed back the second IP address to WAB-MT. Of course, the specific way in which the core network of WAB-MT feeds back the second IP address to WAB-MT can refer to the way in which the first IP address is fed back, and the embodiments of the present application will not be repeated here.

[0283] For another example, the WAB-gNB sends the first identifier provided by the terminal device to the core network node of the terminal device. In this case, the first identifier can be sent to the core network node of the WAB-MT via the WAB-MT, and then forwarded by the core network of the WAB-MT to the core network node of the terminal device. This allows the core network node of the terminal device to determine the second IP address. The core network node of the terminal device can send the second IP address it has determined to the WAB-gNB. The implementation process of the core network node of the terminal device sending the second IP address is similar to that of sending the first identifier, differing only in the transposition of the sending and receiving ends. Alternatively, the WAB-MT can send the first identifier it has measured to the core network node of the WAB-MT, which then forwards it to the core network node of the terminal device. The specific method by which the core network node of the terminal device determines the second IP address and the process of sending the second IP address to the WAB-gNB are described in the above example and will not be further described in detail in this embodiment of the present application.

[0284] In the embodiment of the present application, the IP address of the adjacent access network node can be determined by measuring the first identifier obtained from the first cell, so that the first relay node can establish a communication interface with the access network node of the first cell, thereby improving communication efficiency.

[0285] In some embodiments, the adjacent access network node can be at least one of the following access network nodes: an adjacent access network node that has a logical interface with the first core network node; an adjacent access network node that has a logical interface with the second core network node; an adjacent access network node that has a logical interface with the first host node; an adjacent access network node that is reachable by IP routing to the first core network node; an adjacent access network node that is reachable by IP routing to the second core network node; and an adjacent access network node that is reachable by IP routing to the first host node.

[0286] For example, if the network device is a second core network node, the second core network node can determine a neighboring access network node with which it has a logical interface, and / or the second core network node can determine a neighboring access network node with which it is IP-routable. For example, a logical interface, such as an NG interface, exists between the second core network node and the neighboring access network node. It can also be considered that the second core network node and the neighboring access network node are NGAP-reachable. For another example, the second core network node can address the neighboring access network node using an IP address to achieve communication.

[0287] For another example, if the network device is a first host node, the first host node can determine a neighboring access network node with which it has a logical interface, and / or the first host node can determine a neighboring access network node with which it has an IP route. For example, a logical interface, such as an Xn interface, exists between the first host node and the neighboring access network node. Alternatively, it can be considered that the first host node and the neighboring access network node are reachable via XnAP. For another example, the first host node can address the neighboring access network node using an IP address to achieve communication.

[0288] For another example, if the network device is a first core network node, the first core network node can determine a neighboring access network node with which it has a logical interface, and / or the first core network node can determine a neighboring access network node with which it is IP-routable. For example, a logical interface, such as an NG interface, exists between the first core network node and the neighboring access network node. It can also be considered that the first core network node and the neighboring access network node are NGAP-reachable. For another example, the first core network node can address the neighboring access network node using an IP address to achieve communication.

[0289] In the embodiment of the present application, the adjacent access network node that can establish a communication interface can be an adjacent access network node that has a logical interface and / or IP route reachable with the network device. This ensures that the first access network node can communicate normally with the adjacent access network node after establishing the communication interface, thereby avoiding communication failures.

[0290] In some embodiments, the network device may obtain a second identifier. The second identifier is an identifier of an adjacent access network node. The adjacent access network node indicated by the second identifier is, in the aforementioned embodiments, an adjacent access network node that has a logical interface and / or IP routing reachable to the network device. The network device may send the second identifier to the first relay node. The second identifier is used by the first relay node to request the IP address of the adjacent access network node from the network device.

[0291] For example, when the network device is a first host node, the first host node can indicate the IP address and / or node identifier of the neighboring access network node to the first MT via an RRC message after the first MT joins the network. Alternatively, when the first host node establishes an Xn interface with the first access network node, the first host node can indicate the IP address and / or node identifier of the neighboring access network node to the first access network node via the Xn interface. It will be understood that the node identifier can be a second identifier.

[0292] In some examples, for the first MT and / or the first access network node in the first relay node, when only the second identifier is obtained, the first relay node may send the second identifier to other network devices, such as a network management device, a first host node, a first core network node, or a second core network device, so as to obtain the IP address of the adjacent access network node corresponding to the second identifier, i.e., the second IP address, from the other network devices.

[0293] It is understandable that, when the network device is a network management device, a first host node, a first core network node, and / or a second core network node, the network device can send the second IP address and / or the second identifier to the first relay node. The specific process of each network device sending the second IP address and / or the second identifier to the first relay node can refer to the above-mentioned interaction process between each network device and the first relay node, and the embodiments of the present application will not be repeated here.

[0294] In some examples, after obtaining the second identifier, the network device may also obtain a second IP address from another network device based on the second identifier, and then send the second IP address to the first relay node.

[0295] For example, when the network device is the first host node, the first host node can send the second identifier it obtained to the network management device, the first core network node or the second core network device, so as to obtain the IP address of the adjacent access network node corresponding to the second identifier from other network devices.

[0296] It is worth noting that the second identifier in each embodiment of the present application can be considered as an identifier of a logical interface and / or an adjacent access network node reachable by IP routing on the network device, and the first identifier can be an identifier obtained through cell measurement. In other words, the first identifier and the second identifier are obtained by different methods.

[0297] In the embodiment of the present application, the identifier of the adjacent access network node that has a logical interface and / or IP route to the network device can be obtained, so that the communication interface established by the first relay node can communicate normally with the adjacent access network node, avoiding the situation where communication is impossible.

[0298] In some embodiments, the adjacent access network node may be an access network node located within the coverage area of ​​the terminal device or the first relay node.

[0299] For example, when a terminal device is performing cell measurement, the terminal device may determine the corresponding first identifier based on the terminal device's registration area. In this example, if the first identifier is an identifier of a neighboring access network node, the neighboring access network node indicated by the first identifier may be an access network node within the coverage area corresponding to the terminal device's registration area.

[0300] For another example, when the first MT performs cell measurement, the corresponding first identifier can be determined based on the registration area of ​​the first MT. In this example, if the first identifier is an identifier of a neighboring access network node, then the neighboring access network node indicated by the first identifier can be an access network node within the coverage area corresponding to the registration area of ​​the first MT.

[0301] For another example, when determining the second identifier, the network device may determine the corresponding first identifier based on the registration area of ​​the first relay node. In this example, the adjacent access network node indicated by the first identifier may be an access network node within the coverage area corresponding to the registration area of ​​the first relay node and having a logical interface and / or IP route reachable to the network device.

[0302] The adjacent access network nodes in the embodiment of the present application can be access network nodes within the registration area of ​​the terminal device or the first relay node, thereby ensuring that the first relay node establishes a communication interface with the adjacent access network nodes within a certain range, improving network security while saving resource consumption caused by establishing the communication interface.

[0303] In some examples, consider the case where the adjacent access network node is of the same node type as the first relay node, for example, the adjacent access network node is a non-second relay node. A non-second relay node is any access network node other than the second relay node, and the second relay node includes the second MT and the second access network node. In other words, the adjacent access network node is not the second access network node.

[0304] Assume that the adjacent access point is a second access network node. In this case, this adjacent access network node may be a mobile relay node, namely a second relay node. There is a possibility that within a short period of time, this adjacent access network node may no longer qualify as a neighboring access network node for the first relay node. If a communication interface is still established between the first access network node in the first relay node and this adjacent access network node, the efficiency of this communication interface may be very low, and the maintenance of the communication interface will be increased, resulting in unnecessary waste of resources.

[0305] Therefore, in the embodiment of the present application, when establishing a communication interface with the first relay node, if the adjacent access network node is a second relay node, establishing a communication interface between the first access network node in the first relay node and the second access network node in the second relay node will not be considered. In other words, in each embodiment of the present application, the adjacent access network node that establishes a communication interface with the first access network node of the first relay node is not a second relay node, that is, the adjacent access network node does not belong to the second relay node.

[0306] In some examples, when the first relay node obtains the second IP address using the first identifier, the second IP address includes the IP address of the second access network node that is not the second relay node. In other words, the second IP address does not include the IP address of the second access network node that is the second relay node.

[0307] In some examples, for the case where the WAB node obtains the first identifier, if the WAB-MT determines through the neighboring cell broadcast during the neighboring cell measurement process that the neighboring cell is a cell managed by the second access network node, such as a WAB type cell. For example, the WAB cell identifier in the neighboring system information block (SIB) 1, then the WAB-MT will not send this type of first identifier to the network device, and the WAB-MT will send other first identifiers to the network device except the first identifier related to the above-mentioned WAB type cell. In other examples, the measurement situation for the terminal device is similar. The terminal device will not send this type of first identifier to the WAB-gNB, and the terminal device will send other first identifiers to the WAB-gNB except the first identifier related to the above-mentioned WAB type cell.

[0308] In other examples, in the case where the aforementioned network device obtains the second IP address, the network device may obtain seventh information. The seventh information is used to indicate the IP address of the adjacent access network node, that is, the second IP address. Assume that the adjacent access network node corresponding to the second IP address is not the second relay node. Then the second IP address fed back by the network device to the first relay node may include such a second IP address belonging to a non-second relay node. However, in the case where the adjacent access network node corresponding to the second IP address is the second relay node, the second IP address fed back by the network device to the first relay node does not include such a second IP address belonging to the second relay node.

[0309] For example, if the network device is a core network node of a WAB-MT, the WAB-MT core network node can determine, via the NG interface, whether the adjacent access network node connected to it is of the WAB type, that is, whether it is a second relay node. For example, the adjacent access network node can indicate whether it is a second relay node in an NG interface-level message sent to the WAB-MT core network node.

[0310] For another example, the network device is a WAB-donor. The WAB-donor can interact with Xn to determine whether the neighboring cell type is a WAB cell, or determine whether the neighboring access network node is a WAB node, that is, whether it is a second relay node. For example, the Xn interface-level message sent by the neighboring access network node to the WAB-donor indicates that there is a cell belonging to the second relay node type in the cell it manages, or indicates that the node type is a second relay node. Alternatively, the WAB-donor determines that the neighboring access network node is co-located with other WAB-MTs that have established an RRC connection with itself, that is, determines that the neighboring access network node belongs to the second relay node. Alternatively, the WAB-donor determines that the anchor point used by the neighboring access network node to establish the second communication interface is its own node. Then the neighboring access network node can be considered to be a second relay node. The WAB-donor will not feedback the second IP address of this type of neighboring access network node to the WAB node.

[0311] It is understood that the WAB cell can be understood as a cell type, which can be the cell type of the cell managed by the second access network node. Of course, it can also be called a second cell, a second cell type, or any other possible name, which is not limited in this embodiment of the present application.

[0312] The network device of the embodiment of the present application can avoid feeding back the second IP address belonging to the second relay node to the first relay node, and can avoid establishing a communication interface between the first access network node and the second access network node, thereby avoiding wasting resources.

[0313] S102: The first relay node sends second information to the first core network node and / or the adjacent access network node.

[0314] Correspondingly, the first core network node and / or the adjacent access network node receives the second information sent by the first relay node.

[0315] In some embodiments, the first relay node may send second information to the first core network node and / or the adjacent access network node based on the at least one address information acquired in S101. The second information is used to indicate a request to establish a first communication interface and / or a second communication interface. In other words, the second information is used to request the first access network node to establish a first communication interface with the first core network node, and / or to request the first access network node to establish a second communication interface with the adjacent access network node.

[0316] In some examples, the first IP address obtained by the first relay node can be used as the source IP address of the second information. The second IP address obtained by the first relay node can be used as the destination IP address in the second information.

[0317] In some embodiments, considering the second IP address obtained by the first relay device, some of the adjacent access network nodes corresponding to the second IP address may still be second relay nodes. In this case, the first relay node may not send the second information if it determines that the adjacent access network node corresponding to the second IP address is a second relay node. In other words, the first relay node does not send the second information to the second relay node. Alternatively, the first access network node in the first relay node does not send the second information to the second access network node in the second relay node.

[0318] In some examples, the first MT may obtain the first type of information of the first cell during the process of measuring the first cell, for example, through broadcasting.

[0319] In other examples, the terminal device may obtain the first type information of the first cell during measurement of the first cell. The terminal device may also carry the first type information indicating the first cell when sending the first identifier to the first relay node, and inform the first relay node of the first type information.

[0320] The first type information may be used to indicate that the first cell is a cell managed by the second access network node.

[0321] In some other examples, when sending the second IP address, the network device may further indicate second type information of the adjacent access network node corresponding to the second IP address, such as whether the adjacent access network node corresponding to the second IP address is a second relay node or whether it is a WAB type.

[0322] The second type information may be used to indicate that the adjacent access network node belongs to the second relay node. In other words, the adjacent access network node is the second access network node.

[0323] In the embodiment of the present application, the first relay node can dynamically determine whether to send the second information based on the node type of the node corresponding to the second IP address, thereby improving the efficiency of the first relay node in establishing the communication interface.

[0324] In some embodiments, for embodiments in which the WAB-donor replaces the IP address, the information after the WAB-donor replaces the IP address can be considered the second information. In this case, the first relay node may send fourth information for establishing a communication interface to the first core network node and / or the adjacent access network node before obtaining the address information. The WAB-donor replaces the source IP address in the fourth information with the first IP address and then continues forwarding it to the first core network node and / or the adjacent access network node.

[0325] In the embodiment of the present application, the first relay node can obtain address information so as to send second information for establishing a communication interface according to the address information, so that the first access network node in the first relay node can directly establish a logical interface with different network devices, thereby improving communication efficiency.

[0326] In the communication method provided in the embodiment of the present application, it is also possible to consider the case where the first relay node switches from the second host node to the first host node. For example, the first relay node switches from the second host node to the first host node during movement. In this case, the first relay node can also obtain the first information from the second host node. In this embodiment, the second host node can be considered as the source WAB-donor, and the first host node can be considered as the target WAB-donor.

[0327] In some examples, the first information can be determined based on information about the target WAB-donor. For example, identification information related to the first host node may be required when determining the first IP address. In this case, the first IP address can be determined based on the identification information of the target WAB-donor. For example, the target WAB-donor can determine the first information, and when the first relay node switches to the target WAB-donor, the target WAB-donor sends the first information to the first relay node via an RRC reconfiguration message.

[0328] In some embodiments, when the network device is a second core network node and / or a first host node, the network device may receive fifth information from the second host node. The fifth information includes a third IP address. The third IP address is the IP address of the first access network node before the first relay node is handed over. After determining the first IP address, the network device may establish a correspondence between the third IP address and the first IP address. The network device may send sixth information to the second host node, where the sixth information is used to indicate the correspondence between the third IP address and the first IP address.

[0329] For example, the source WAB-donor sends a handover (HO) request message. The handover request message may be a first handover request message or a second handover request message. In the case where an Xn interface is established between the source WAB-donor and the target WAB-donor, the source WAB-donor may directly send a first handover request message to the target WAB-donor. The first handover request message may be a HO request message. In the case where an Xn interface is not established between the source WAB-donor and the target WAB-donor, the first relay node is switched from the source WAB-donor to the target WAB-donor through the core network node of the WAB-MT. In this case, the source WAB-donor may send a second handover request message to the core network node of the WAB-MT. The second handover request message may be a HO required message.

[0330] The handover request message may carry a third IP address. The third IP address may be considered as the source IP address used to establish the communication interface before the first relay node switches to the donor node. After the target WAB-donor determines the new source IP address, it may indicate the new source IP address to the source WAB-donor via an HO request acknowledgement message or an HO command message. In this case, the source WAB-donor may also update the new source IP address to the first MT via an RRC reconfiguration message. It will be understood that the anchor point of the new source IP address may be the first IP address located at the target WAB-donor.

[0331] In the embodiment of the present application, the network device can indicate the correspondence between the third IP address corresponding to the second host node and the first IP address of the first host node when the first relay node switches the host node. This allows the first relay node to establish a communication interface during the switching process, thereby ensuring communication stability.

[0332] In some examples, if the first relay node switches its host node, the address information may not change if the anchor point is located at the second core network node. This is because the core network of the WAB-MT may not necessarily change during the movement of the first relay node, but the host node may change. Therefore, if the anchor point of the first IP address is located at the second core network node, it is possible that the first IP address does not need to be updated if the second core network node remains unchanged. In the case where the anchor point of the first IP address is located at the first host node, the address information can be updated.

[0333] Of course, the process of re-determining the first IP address and the second IP address can refer to the description of the above embodiments, and the embodiments of the present application will not be repeated here.

[0334] In some embodiments, for the case of obtaining the first identifier to determine the second IP address, in the scenario where the first relay node switches the host node, the second IP address can be determined based on the first identifier measured by the WAB-MT before the first relay node switches the host node, or the first IP address can be determined based on the first identifier measured by the WAB-MT after the first relay node switches the host node. The embodiments of the present application are not limited here. Similarly, the same applies to the first identifier measured by the terminal device. For example, based on the first identifier measured by the terminal device before the first relay node switches the host node, or based on the first identifier measured by the terminal device after the first relay node switches the host node.

[0335] The embodiment of the present application can also be applied to the scenario where the first relay node switches the host node, so that in this scenario the first relay node can also establish a communication interface with other network devices to improve the stability of communication.

[0336] The communication method provided in the embodiments of this application can also be considered for application in O-RAN scenarios. That is, as mentioned in the aforementioned embodiments, the network device may be a RIC. The RIC can be used to collect network information and perform necessary optimization tasks. The RIC can communicate with the CU and DU of each access network node via the E2 interface, which can be considered a logical interface. The RIC can directly control the DU of the access network node or indirectly control its DU through the CU of the access network node.

[0337] For example, as shown in FIG9 , the RIC may establish an E2 interface with the CU and DU of each node.

[0338] In some examples, the RIC may function solely as a forwarding node. Specifically, in conjunction with the implementations of the aforementioned embodiments, the RIC may serve as an intermediate node in communications between the first relay node and other nodes. For example, the first relay node may first send data to the RIC, which then forwards the data to the corresponding node. The reverse is also true.

[0339] In other examples, the RIC can serve as a node for determining the first information. For example, the first relay node can send third information to the RIC to request the first information. Alternatively, the RIC can proactively notify the first relay node of the first information based on configuration. In another example, the first relay node can send information about the first relay node and / or information about the first host node to the RIC to determine the first IP address. In another example, the first relay node can send a first identifier and / or a second identifier to the RIC to determine the second IP address.

[0340] The RIC may be directly indicated to the first relay node via the E2 interface; or, the RIC may be indicated to the first host node via the E2 interface, and the first host node may indicate to the first relay node via an RRC message.

[0341] For example, the first IP address and / or the second IP address may be configured for the first relay node through the RIC after the first relay node joins the network.

[0342] For another example, the RIC may determine an adjacent access network node with which an E2 interface exists and / or an IP route is reachable, and determine a second IP address and / or a second identifier of such an access network node.

[0343] In some instances, for the scenario where the first relay node switches the host node, the RIC may directly indicate the new first information to the first relay node through the E2 interface; or, the RIC may indicate the new first information to the host node through the E2 interface, for example, it may indicate it to the second host node before the switch, and indicate it to the first host node after the switch, and then the host node indicates it to the first relay node through an RRC message.

[0344] Of course, for the implementation process in the O-RAN scenario, reference can be made to the description of the aforementioned embodiments, and the embodiments of the present application will not be repeated here.

[0345] It is understood that the access network nodes involved in the various embodiments of the present application may be access network nodes in a CU / DU separation architecture. In other words, the access network nodes may include a CU and a DU.

[0346] Next, the embodiment of the present application will be described by taking the first relay node as a WAB node, the first host node as a WAB-donor, the second core network node as an access network of a WAB-MT, and the network management device as an OAM as an example.

[0347] Referring to FIG10 , the method is described by taking obtaining the first IP address as an example. The method may include the following steps:

[0348] S201, WAB node accesses the network.

[0349] In some embodiments, the WAB node can access the WAB-donor and the core network serving the WAB-MT through the WAB-MT, thereby completing the WAB node network access process. The specific implementation process can refer to the process of terminal device network access, and the embodiments of this application will not be repeated here.

[0350] In some examples, a WAB-MT can indicate its identity to network equipment when joining the network. For example, it can indicate to the WAB-donor that it is a WAB node via an RRC message. The WAB-donor then indicates to the core network serving the WAB-MT that the UE is a WAB node via a UE-related NGAP message, such as an initial UE message. This indicates that the UE is not an ordinary UE, but a WAB-MT. For another example, when joining the network, the WAB-MT indicates that it is a WAB node to the core network serving the WAB-MT via an uplink NAS message.

[0351] The WAB node may obtain the first information through various implementations, where the first information includes the first IP address. Different implementations will be described below.

[0352] Implementation method 1 of the WAB node obtaining the first information:

[0353] S202: The WAB node sends third information to the OAM.

[0354] Correspondingly, the OAM receives the third information sent by the WAB node.

[0355] In some examples, the third information may include information of a core network serving the WAB-MT and / or information of a WAB-donor. It can be understood that the third information is used to request the first information.

[0356] It can be understood that S202 is an optional step.

[0357] S203: The OAM sends first information to the WAB node.

[0358] Correspondingly, the WAB node receives the first information sent by the OAM.

[0359] In some examples, the WAB node can send information about the core network serving the WAB-MT and / or WAB-donor information to the WAB node's OAM. Based on this information, the OAM then provides the WAB node with a corresponding IP address. For example, if the OAM receives information about the core network serving the WAB-MT from the WAB node, it will provide the WAB node with the IP address of the WAB-gNB used to establish the N2 / Xn interface. The anchor point for this IP address can be the UPF of the WAB-MT. In this case, the WAB-gNB's N2 / Xn data can be forwarded through the UPF of the WAB-MT.

[0360] For example, if OAM receives information about a WAB-donor from a WAB node, it will provide the WAB node with the IP address of the WAB-gNB used to establish the Xn interface. The anchor point of this IP address may be the WAB-donor. In this case, the WAB-gNB's Xn data can be forwarded through the WAB-donor.

[0361] The IP address of the UPF or WAB-donor anchoring the WAB-MT can be in the same network segment as the UPF or WAB-donor, or it can be the same IP address as the UPF or WAB-donor. In this case, the UPF or WAB-donor of the WAB-MT is required to maintain the correspondence between the WAB-gNB and the WAB-MT. This ensures that after receiving N2 / Xn data sent to the WAB-gNB, the UPF or WAB-donor of the WAB-MT knows which WAB-MT PDU session DRB or SRB to use for backhaul. Optionally, the allocated IP address can be the gateway IP address. Optionally, the IP address can be divided into IP addresses for the control plane, such as N2-C or Xn-C, or for the user plane, such as N2-U or Xn-U.

[0362] Alternatively, the WAB-donor may send the WAB-MT's core network information and / or WAB-donor information to the OAM. Based on this information, the OAM then determines the IP address of the WAB-gNB used to establish the N2 / Xn interface. The IP address may be sent directly to the WAB node. Alternatively, the OAM may determine the IP address and send it to the WAB-donor, which then indicates it to the WAB-MT via an RRC message.

[0363] In some examples, the core network information serving the WAB-MT and / or the WAB-donor information may also be pre-configured in the OAM; or, the OAM directly sends the first information to the WAB node according to a preset condition.

[0364] Implementation method 2 for the WAB node to obtain the first information:

[0365] S204: The WAB node sends third information to the core network of the WAB-MT.

[0366] Correspondingly, the core network of the WAB-MT receives the third information sent by the WAB node.

[0367] In some examples, the third information may include WAB-donor information. The third information is used to request the AMF serving the WAB-MT to obtain the IP address of the WAB-donor anchor. For example, the WAB-MT may provide the WAB-donor information to the AMF serving the WAB-MT via an uplink NAS message. Optionally, this process may be triggered when the WAB-gNB wishes to establish an Xn interface with a neighboring station.

[0368] S205: The core network of the WAB-MT determines the first information.

[0369] In some examples, the core network of the WAB-MT can obtain the WAB-MT's current serving cell identifier and its TAI (i.e., WAB-donor information) based on the WAB node's identifier and the ULI reported by the WAB-donor when the WAB-MT joins the network. The WAB node's identifier can be carried in the WAB indication. Based on the WAB-donor information, the core network of the WAB-MT can determine the IP address assigned to the WAB-gNB, with the anchor point located at the WAB-donor, for establishing the Xn interface.

[0370] For example, the AMF of WAB-MT directly determines the IP address of the anchor point at the WAB-donor; or the AMF notifies the SMF / UPF to determine the IP address of the anchor point at the WAB-donor; or the AMF asks the WAB-donor for the IP address of the anchor point at the WAB-donor based on the information of the WAB-donor.

[0371] In other examples, the core network of the WAB-MT may independently determine the IP address of the anchor point for establishing the Xn and / or N2 interface at the UPF of the WAB-MT.

[0372] Then, the core network of the WAB-MT indicates to the WAB node that the anchor point for establishing the Xn and / or N2 interface is located at the IP address of the UPF of the WAB-MT; or indicates that the anchor point for establishing the Xn interface is located at the IP address of the WAB-donor, and / or the anchor point for establishing the N2 interface is located at the IP address of the UPF of the WAB-MT.

[0373] S206: The core network of the WAB-MT sends first information to the WAB node.

[0374] Correspondingly, the WAB node receives the first information sent by the core network of the WAB-MT.

[0375] In some examples, the AMF of the WAB-MT directly indicates it to the WAB-MT through a downlink NAS message.

[0376] In other examples, the AMF of the WAB-MT first indicates the above IP address to the WAB-donor through an NGAP message, and then the WAB-donor indicates it to the WAB-MT through an RRC message.

[0377] Implementation method 3 of the WAB node obtaining the first information:

[0378] S207: The WAB node sends the third information or the fourth information to the WAB-donor.

[0379] Correspondingly, the WAB-donor receives the third information or the fourth information sent by the WAB node.

[0380] In some examples, the WAB-MT may send third information via an RRC message, where the third information is used to request the WAB-donor to allocate an IP address for the WAB-gNB to establish an Xn interface, where the anchor point is located at the WAB-donor.

[0381] In other examples, the WAB-gNB may send a fourth message, which may be the first Xn Setup request message to another gNB or a WAB-donor-gNB. The other gNB may be any gNB other than the WAB-gNB and the WAB-donor-gNB.

[0382] S208, WAB-donor determines the first information.

[0383] In some examples, the WAB-donor may allocate an IP address at the WAB-donor, where the anchor point for establishing the Xn interface is located, to the WAB-gNB upon receiving the third information or the fourth information sent by the WAB-gNB.

[0384] In some cases, if the fourth information is sent to another gNB, the WAB-donor can also update the source IP address in the Xn packet sent by the WAB-gNB to the new IP address allocated by the WAB-donor to the WAB-gNB, and then forward the XnAP message.

[0385] S209: The WAB-donor sends first information to the WAB node.

[0386] Correspondingly, the WAB node receives the first information sent by the WAB-donor.

[0387] In some examples, when the WAB node is confirmed to have joined the network, the WAB-donor may indicate to the WAB-MT via an RRC message the IP address of the WAB-gNB at the WAB-donor's location as the anchor point for establishing the Xn interface. Alternatively, when the WAB-donor determines that an Xn interface has been established between it and the WAB-gNB, the IP address used by the WAB-gNB for establishing the Xn interface may be preconfigured. The WAB-donor may indicate to the WAB-gNB via an RRC message or an XnAP message the IP address of the WAB-donor at the WAB-donor's location as the anchor point for establishing the Xn interface.

[0388] In some examples, the WAB-donor may also indicate the new IP address updated in S208 to the WAB node via an RRC message or an XnAP message.

[0389] It can be understood that the above-mentioned implementation methods 1 to 3 for the WAB node to obtain the first information can select any one or more implementation methods to determine the first information, and the embodiment of the present application does not limit this.

[0390] S210: The WAB node sends second information to the core network and / or the adjacent access network node of the terminal device.

[0391] Correspondingly, the core network and / or the adjacent access network node of the terminal device receives the second information sent by the WAB node.

[0392] In some examples, the second information is used to establish the first communication interface and / or the second communication interface.

[0393] Considering WAB node handover, the IP address used to establish the Xn / N2 interface may need to be updated after the WAB node switches from the source donor to the target donor. For example, if the Xn interface IP address is anchored on the donor side, this IP address needs to be updated after the handover. If the anchor point is at the UPF of the WAB-MT, this IP address also needs to be updated if the UPF of the WAB-MT is replaced.

[0394] In some embodiments, the new IP address of the WAB node after the handover can be obtained from the OAM based on the new WAB-donor information and / or the UPF information of the WAB-MT.

[0395] In some embodiments, the new IP address of the WAB node after the handover can be obtained from the core network of the WAB-MT based on the new WAB-donor information and / or the UPF information of the WAB-MT.

[0396] In some embodiments, when the source WAB-donor sends a handover request message, it may carry the old IP address used to establish the Xn interface. The target WAB-donor then determines that the anchor point for the WAB node is located at the IP address of the target WAB-donor, and indicates this to the source WAB-donor through an HO request confirmation message. The source WAB-donor updates the message to the WAB-MT through an RRC reconfiguration message. Alternatively, when a handover is performed via the core network node of the WAB-MT, the source WAB-donor sends a handover request message to the core network node of the WAB-MT. In this case, the old IP address used to establish the Xn interface may be carried. The target WAB-donor then determines that the anchor point for the WAB node is located at the IP address of the target WAB-donor, and indicates this to the source WAB-donor through an HO command message. The source WAB-donor updates the message to the WAB-MT through an RRC reconfiguration message.

[0397] In some embodiments, after the WAB node is switched to the target WAB-donor, the target WAB-donor determines an IP address of the target WAB-donor as the anchor point for the WAB node, and updates the IP address to the WAB-MT through an RRC reconfiguration message.

[0398] The method described in Figure 10 can enable the WAB node to obtain the IP address of the WAB-gNB for establishing the Xn interface and / or N2 interface, thereby ensuring that the WAB node can establish an Xn interface with the neighboring station or establish an N2 interface with the UE's core network, which is conducive to the flexible deployment of the WAB network architecture.

[0399] It can be understood that the specific implementation process of each step from S201 to S210 in Figure 10 can refer to the description of the aforementioned embodiment, and the embodiment of the present application will not be repeated here.

[0400] Referring to FIG11 , the method is described by taking obtaining the second IP address as an example. The method may include the following steps:

[0401] S301, WAB node accesses the network.

[0402] Among them, the implementation process of S301 is the same as that of S201. Please refer to the description of S201 for details, and the embodiments of this application will not be repeated here.

[0403] The WAB node may obtain the first information through various implementations, where the first information includes the second IP address. Different implementations will be described below.

[0404] Implementation method 4 of the WAB node obtaining the first information:

[0405] S302: The WAB node sends third information to the OAM.

[0406] Correspondingly, the OAM receives the third information sent by the WAB node.

[0407] It is understandable that S302 is an optional step, wherein the third information is used to request the first information.

[0408] S303: The OAM sends first information to the WAB node.

[0409] Correspondingly, the WAB node receives the first information sent by the OAM.

[0410] In some examples, OAM pre-configures the WAB node with the IP address and / or identifier of a possible neighboring station for establishing the Xn interface. The identifier of the neighboring station may be, for example, the gNB ID of the adjacent access network node.

[0411] In some examples, the IP address used by the neighboring station to establish the Xn interface may be the IP address of the gateway used by the neighboring station to establish the Xn interface.

[0412] In other examples, IP addresses that are used to distinguish between Xn-C and Xn-U may also be configured.

[0413] Implementation method 5 of the WAB node obtaining the first information:

[0414] S304, the WAB-donor sends measurement configuration information to the WAB node.

[0415] Correspondingly, the WAB node receives the measurement configuration information sent by the WAB-donor.

[0416] In some examples, the WAB-donor may instruct the WAB-MT to measure the first cell through an RRC message based on the received identity sent by the WAB node, such as a WAB indication, or the WAB-donor may configure measurement for the WAB-MT through an RRC message.

[0417] S305: The WAB node measures the first cell and obtains a first identifier.

[0418] In some cases, the WAB-MT can obtain neighboring cell identifiers, such as PCI and NCGI, or the identifier of the base station to which the neighboring cell belongs, such as the gNB ID, through measurements. The neighboring cell is the first cell mentioned above. For example, the WAB-MT can obtain the neighboring cell's NCGI from neighboring cell broadcasts using the ANR function. If the broadcast also includes the gNB ID length, the WAB-MT can also deduce the gNB ID to which the neighboring cell belongs based on the neighboring cell's NCGI and gNB ID length.

[0419] In some examples, the WAB-MT may perform neighbor measurements when determining to establish an Xn interface with a neighboring station.

[0420] In other examples, measurements can also be performed by a UE connected to a WAB-gNB. In other words, the WAB-MT can be replaced by a UE connected to a WAB-gNB, the WAB-donor can be replaced by a WAB-gNB, and the core network of the WAB-MT can be replaced by the core network of the UE.

[0421] S306: The network device determines first information based on the first identifier.

[0422] It is understood that the WAB node can send the first identifier to the network device, so that the network device determines the first information based on the first identifier, and then the network device sends the first information to the WAB node. It is understood that the network device can include any network device involved in the above embodiments.

[0423] For example, after obtaining the cell identifier and / or the identifier of the base station to which the WAB node belongs, there are multiple scenarios for obtaining the IP address of the neighboring station for establishing the Xn interface. The first identifier sent by the WAB node can be carried in the third information. In other words, it can also be understood that the first identifier is carried in the third information to obtain the first information.

[0424] Case 1: The WAB node obtains the IP address of the neighboring station for establishing the Xn interface:

[0425] The WAB node sends the cell identifiers and / or base station identifiers of all or unknown neighboring cells to the OAM, and the OAM feeds back the IP address of the neighboring cell for establishing the Xn interface to the WAB node.

[0426] Case 2: The WAB node obtains the IP address of the neighboring station for establishing the Xn interface:

[0427] The WAB-MT sends the cell identifiers and / or base station identifiers of all or unknown neighboring cells to the WAB-donor via RRC messages. The WAB-donor then contacts the OAM or these neighboring stations to request the IP address used to establish the Xn interface. In some cases, the WAB-donor can request the IP address of a neighboring station that is reachable through an XnAP or IP.

[0428] It can be understood that the neighboring station is the adjacent access network node mentioned above.

[0429] Case 3: The WAB node obtains the IP address of the neighboring station for establishing the Xn interface:

[0430] WAB-MT sends the cell identifiers of all or unknown neighboring cells and / or the identifiers of their base stations to WAB-donor through RRC messages. Then WAB-donor can send the cell identifiers of neighboring cells and / or the identifiers of their base stations to the core network of WAB-MT through NGAP messages. For example, through uplink RAN ​​configuration transmission messages. The core network of WAB-MT goes to OAM or these neighboring stations to request the IP addresses used to establish the Xn interface. After obtaining the IP addresses, the core network of WAB-MT will feed these IP addresses back to WAB-MT. Please refer to the aforementioned embodiments for the two possible feedback methods, and the embodiments of this application will not be repeated here.

[0431] Case 4: The WAB node obtains the IP address of the neighboring station for establishing the Xn interface:

[0432] The WAB-gNB sends the cell identifiers and / or base station identifiers of all or unknown neighboring cells to the UE's core network via an NGAP message. For example, this is done via an uplink RAN ​​configuration transmission message. The UE's core network then contacts the OAM or these neighboring cells to obtain the IP addresses used to establish the Xn interface. After obtaining the IP addresses, the UE's core network can feed these IP addresses back to the WAB-gNB. The feedback method is described in the previous embodiment and will not be further detailed in this embodiment.

[0433] Implementation method 6 of the WAB node obtaining the first information:

[0434] S307: The WAB node sends third information to the core network of the WAB-MT.

[0435] Correspondingly, the core network of the WAB-MT receives the third information sent by the WAB node.

[0436] It can be understood that S307 is an optional step.

[0437] S308: The core network of the WAB-MT determines the first information or the second identifier.

[0438] In some examples, the core network of the WAB-MT determines a base station with which an NG interface is established and / or with which the base station is reachable via an IP address.

[0439] In some examples, the core network of the WAB-MT sends the determined IP address of the base station for establishing the Xn interface to the WAB-MT.

[0440] For example, refer to Case 3 in S306. Alternatively, the WAB-MT core network sends the determined base station identifier to the WAB-MT, such as the gNB ID or NCGI. The interaction between the WAB-MT core network and the WAB-MT can refer to the aforementioned embodiment. The WAB node then searches for the IP address of the neighboring station for the OAM to use to establish the Xn interface based on the neighboring station identifier.

[0441] In some examples, the core network of the WAB-MT may also send the IP address and / or base station identifier of the base station in the registration area of ​​the WAB-MT for establishing the Xn interface to the WAB-MT according to the registration area of ​​the WAB-MT.

[0442] In some examples, the core network of the WAB-MT may directly determine the first information according to pre-configuration.

[0443] S309: The core network of the WAB-MT sends the first information or the second identifier to the WAB node.

[0444] Correspondingly, the WAB node receives the first information or the second identifier sent by the core network of the WAB-MT.

[0445] In some examples, the WAB-MT core network can directly send the first information to the WAB node. In other examples, the WAB-MT core network can also send a second identifier to the WAB node, which then sends the second identifier to other network devices to obtain the first information determined by the other network devices based on the second identifier. For example, the WAB node can send the second identifier to network devices such as the OAM and WAB-donor to obtain the first information.

[0446] Implementation method 7 of the WAB node obtaining the first information:

[0447] S310: The WAB node sends third information to the WAB-donor.

[0448] Correspondingly, the WAB-donor receives the third information sent by the WAB node.

[0449] It can be understood that S310 is an optional step.

[0450] S311, WAB-donor determines the first information or the second identifier.

[0451] In some examples, the WAB-donor determines neighboring stations with which it has established Xn interfaces and / or IP addresses.

[0452] In some examples, the WAB-donor sends its own IP address and / or the IP address of the identified neighboring station for establishing the Xn interface to the WAB node. Alternatively, the WAB-donor sends its own IP address and / or the IP address of the identified neighboring station to the WAB node, such as the gNB ID or NCGI. The WAB node then requests the OAM for the IP address of the neighboring station for establishing the Xn interface based on the neighboring station identifier.

[0453] The interaction process between the WAB-donor and the WAB node can be referred to in S208. For example, after the WAB-MT joins the network, the WAB-donor can indicate its own IP address / base station identifier and / or the neighboring station's IP address / base station identifier to the WAB-MT via an RRC message. Alternatively, after the WAB-gNB establishes an Xn interface with the WAB-donor, the WAB-gNB can indicate the IP address / base station identifier of other neighboring stations to the WAB-gNB via the Xn interface.

[0454] In some examples, the WAB-donor may directly determine the first information according to pre-configuration.

[0455] S312: The WAB-donor sends the first information or the second identifier to the WAB node.

[0456] Correspondingly, the WAB node receives the first information or the second identifier sent by the WAB-donor.

[0457] In some examples, the WAB-donor can directly send the first information to the WAB node. In other examples, the WAB-donor can also send a second identifier to the WAB node, which then sends the second identifier to other network devices to obtain the first information determined by the other network devices based on the second identifier. For example, the WAB node can send the second identifier to network devices such as the OAM and WAB-MT core network to obtain the first information.

[0458] It can be understood that the above-mentioned implementation methods 4 to 7 for the WAB node to obtain the first information can select any one or more implementation methods to determine the first information, and the embodiment of the present application does not limit this.

[0459] S313: The WAB node sends second information to the core network and / or the adjacent access network node of the terminal device.

[0460] Correspondingly, the core network and / or the adjacent access network node of the terminal device receives the second information sent by the WAB node.

[0461] Among them, the implementation process of S313 is the same as that of S210. Please refer to the description of S210 for details, and the embodiment of this application will not be repeated here.

[0462] Similarly, considering the switching of the WAB node, after the WAB node switches from the source WAB-donor to the target WAB-donor, the neighboring station may change, and the IP address used by the neighboring station to establish the Xn interface may also need to be updated.

[0463] In some embodiments, the WAB node obtains the IP address of the new neighboring station used to establish the Xn interface after the handover from the OAM.

[0464] In some embodiments, the WAB node requests the IP address of the new neighboring station for establishing the Xn interface from the OAM or WAB-MT core network based on the cell identifier and / or base station identifier of the new neighboring cell measured before or after the handover. For example, before the handover, the WAB node interacts with the WAB-MT core network through the source WAB-donor, and after the handover, the WAB node interacts with the WAB-MT core network through the target WAB-donor.

[0465] Alternatively, the UE accessing the WAB-gNB requests the IP address of the new neighboring station for establishing the Xn interface from the OAM or the UE's core network based on the measured cell identifier and / or base station identifier of the new neighboring cell, and the IP address is sent to the WAB node by the OAM or the UE's core network.

[0466] In some embodiments, after the WAB node is switched to the target WAB-donor, the core network of the WAB-MT re-determines the IP address of the new neighboring station for establishing the Xn interface.

[0467] In some embodiments, after the WAB node is switched to the target WAB-donor, the target WAB-donor re-determines the IP address of a new neighboring station for the WAB node to establish the Xn interface.

[0468] Furthermore, to reduce unnecessary Xn interface maintenance, in some embodiments, a WAB-gNB does not establish an Xn interface with a neighboring WAB node. In other words, no Xn interface is established between two WAB-gNBs.

[0469] Regarding implementation mode 4 in the aforementioned embodiment: when OAM learns that the neighboring station is a WAB node type, the IP address of the neighboring station used to establish the Xn interface will not be indicated to the WAB node.

[0470] For implementation method 5 in the aforementioned embodiment: When measuring a neighboring cell, if the WAB-MT learns through the neighboring cell broadcast that the neighboring cell is a WAB type cell. For example, the WAB-cell identifier in the neighboring cell SIB 1, then the cell identifier and / or base station identifier of the neighboring cell will not be reported to the WAB-donor. Or after the WAB-MT provides the cell identifier and / or base station identifier of the neighboring cell to the core network of the WAB-donor / OAM / WAB-MT, after they determine that it is a WAB-gNB, they do not provide the corresponding IP address for establishing the Xn interface. For how the WAB-donor determines this, please refer to "Implementation Method 7" below, and for how the core network of the WAB-MT determines this, please refer to "Implementation Method 6" below.

[0471] Regarding Implementation 6 in the aforementioned embodiment, the WAB-MT core network can determine whether the base station is a WAB type based on NGAP interaction with the base station. For example, the base station indicates that the node type is a WAB node in an NG interface-level message sent to the WAB-MT core network. The WAB-MT core network does not indicate to the WAB-MT the IP address of the WAB node type base station used to establish the Xn interface.

[0472] Regarding implementation method 7 in the aforementioned embodiment: the WAB-donor can know that the neighboring cell type is a WAB-cell or the neighboring station is a WAB node based on the Xn interaction. For example, the neighboring station indicates in the Xn interface-level message sent to the WAB-donor that there is a cell of the WAB node type in the managed cell and / or indicates that the node type is a WAB node; or, the WAB-donor finds that the neighboring station of the WAB-gNB is co-located with other WAB-MTs that have established an RRC connection with itself; or, the WAB-donor determines that the anchor point of the IP address used by the neighboring station to establish the Xn interface is also itself. Then the WAB-donor will not indicate the IP address of the neighboring station of the WAB node type used to establish the Xn interface to the WAB node.

[0473] The method described in FIG11 can enable the WAB node to obtain the IP address of the neighboring station for establishing the Xn interface, thereby ensuring that the WAB node can establish the Xn interface with the neighboring station, which is conducive to the flexible deployment of the WAB network architecture.

[0474] It can be understood that the specific implementation process of each step from S301 to S313 in Figure 11 can refer to the description of the aforementioned embodiment, and the embodiment of the present application will not be repeated here.

[0475] Considering that the solutions of the various embodiments of this application can also be applied to O-RAN scenarios, the implementation process after the introduction of RIC is roughly similar to the solutions described in Figures 10 and 11. The following will describe the differences between the implementation process after the introduction of RIC and Figures 10 and 11. For the same implementation process, please refer to the corresponding descriptions in Figures 10 and 11 and will not be repeated.

[0476] Among them, the interaction between RIC and WAB node can be the interaction between RIC and WAB-CU or WAB-DU; the interaction between RIC and WAB-donor can be the interaction between RIC and WAB-donor-CU or WAB-donor-DU, which is not limited in the embodiments of the present application.

[0477] Based on the comparison with FIG. 10 , referring to FIG. 12 , there are differences between the implementation manner 1 and the implementation manner 3 in the aforementioned embodiment, namely, the implementation manner 1 ′ and the implementation manner 3 ′ in FIG. 12 .

[0478] The differences from the implementation method 1 in the above embodiment can be referred to implementation method 1':

[0479] S401: The WAB node sends third information to the RIC.

[0480] It can be understood that the implementation process of S401 is similar to that of S201. For details, please refer to the relevant description of S201, and the embodiments of this application will not be repeated here.

[0481] S402: The RIC sends first information to the WAB node.

[0482] In some examples, the WAB or WAB-donor can send the WAB-MT's core network information and / or WAB-donor information to the RIC. The RIC determines the IP address of the WAB-gNB used to establish the N2 / Xn interface. For example, the RIC can determine this independently based on the above information or obtain it from the OAM. After the RIC determines the IP address, it can directly indicate it to the WAB node via an E2 interface message; or the RIC can first indicate it to the WAB-donor via an E2 interface message, and the WAB-donor can then indicate it to the WAB node via an RRC message.

[0483] In some examples, the core network information serving the WAB-MT and / or the WAB-donor information may also be pre-configured in the RIC; or, the RIC directly sends the first information to the WAB node according to a preset condition.

[0484] The difference between this embodiment and implementation 3 in the above embodiment can be referred to implementation 3':

[0485] S403: The WAB node sends the third information or the fourth information to the WAB-donor.

[0486] S404, WAB-donor determines the first information.

[0487] Among them, S403 is similar to S207, and S404 is similar to S208, which will not be repeated in the embodiment of this application.

[0488] S405, WAB-donor sends first information to RIC.

[0489] S406: The RIC sends first information to the WAB node.

[0490] In some examples, after the WAB-donor determines the IP address for establishing the Xn interface between the WAB-gNB and the WAB-donor, it can first indicate it to the RIC through an E2 interface message, and then the RIC sends the IP address to the WAB node through the E2 interface message.

[0491] In some embodiments, when the first relay node switches to a donor node, the RIC can indicate the updated IP address to the WAB node via an E2 interface message. For example, the RIC can directly indicate the IP address to the WAB node; or the RIC can first indicate the IP address to the WAB-donor via an E2 interface message, which then indicates the IP address to the WAB-MT via an RRC message. The IP address can be indicated to the source WAB-donor before the switch and to the target WAB-donor after the switch.

[0492] Compared with FIG. 11 , referring to FIG. 13 , there are differences between implementations 4 to 7 in the aforementioned embodiments, namely, implementations 4 ′ to 7 ′ in FIG. 13 .

[0493] The difference between this embodiment and the implementation method 4 in the above embodiment can be referred to implementation method 4':

[0494] S501: The WAB node sends third information to the RIC.

[0495] S502: The RIC sends first information to the WAB node.

[0496] In some examples, after a WAB node joins the network, the RIC configures the WAB node with the IP addresses of potential neighboring nodes for establishing the Xn interface. For example, the RIC can obtain these from the OAM. In some examples, after joining the network, the WAB node can indicate its node type to the RIC via the E2 interface, such as through a WAB indicator.

[0497] It can be understood that S501 is an optional step.

[0498] The difference between this embodiment and the implementation method 5 in the above embodiment can be referred to implementation method 5':

[0499] S503: The WAB-donor sends measurement configuration information to the RIC.

[0500] In some embodiments, the measurement configuration sent by the WAB-donor to the WAB node may be first indicated to the RIC via an E2 interface message, and then indicated to the WAB node by the RIC via an E2 interface message.

[0501] S504: The RIC sends measurement configuration information to the WAB node.

[0502] S505: The WAB node measures the first cell and obtains a first identifier.

[0503] S506: The network device determines first information based on the first identifier.

[0504] In some embodiments, the WAB node may send a first identifier to the network device so that the network device determines first information based on the first identifier, and then the network device sends the first information to the WAB node. For example, after measuring the cell identifier of the neighboring station and / or the identifier of the base station to which it belongs, the WAB may send the above information to the RIC via an E2 interface message, and the RIC configures the IP address of the neighboring station to the WAB node. For example, the RIC may send the IP address directly to the WAB node via an E2 interface message, or the RIC may first send the IP address to the WAB-donor via an E2 interface message, and then the WAB-donor indicates it to the WAB node via an RRC message or an XnAP message. It can be understood that the network device may include any network device involved in the aforementioned embodiments.

[0505] The difference between this embodiment and implementation 6 in the above embodiment can be referred to implementation 6':

[0506] S507: The WAB node sends third information to the RIC.

[0507] It is understandable that S507 is similar to S501, and reference may be made to the description of S501, which will not be repeated herein in the embodiment of the present application.

[0508] S508: The RIC determines the first information or the second identifier.

[0509] S509: The RIC sends the first information or the second identifier to the WAB node.

[0510] In some embodiments, the RIC determines that there are E2 interfaces and / or IP-reachable base stations, and indicates the IP addresses and / or base station identifiers of these base stations used to establish Xn interfaces to the WAB node through an E2 interface message.

[0511] The difference between this embodiment and implementation 7 in the above embodiment can be seen in implementation 7':

[0512] S510: The WAB node sends third information to the WAB-donor.

[0513] It is understandable that S510 is similar to S310, and reference may be made to the description of S310, which will not be repeated herein in the embodiment of the present application.

[0514] S511, WAB-donor determines the first information or the second identifier.

[0515] S512, the WAB-donor sends the first information or the second identifier to the RIC.

[0516] S513: The RIC sends the first information or the second identifier to the WAB node.

[0517] In some embodiments, the IP address of the neighboring station sent by the WAB-donor to the WAB node for establishing the Xn interface may be first sent to the RIC via an E2 interface message, and then indicated to the WAB node by the RIC via an E2 message. In other examples, the second identifier sent by the WAB-donor to the WAB node, such as an identifier of the WAB-donor's Xn interface and / or IP-reachable base station, may be first sent to the RIC via an E2 interface message, and then indicated to the WAB node by the RIC via an E2 message.

[0518] In some embodiments, when the first relay node switches to a donor node, the RIC may indicate the IP address of the new neighboring station used to establish the Xn interface to the WAB node via an E2 interface message. For example, the RIC may indicate the IP address directly to the WAB node; or the RIC may first indicate the IP address to the WAB-donor via an E2 interface message, which then indicates the IP address to the WAB-MT via an RRC message. The IP address may be indicated to the source WAB-donor before the switch and to the target WAB-donor after the switch.

[0519] Based on the solutions described in Figures 12 and 13, the RIC can indicate to the WAB node the IP address of the WAB-gNB used to establish the N2 / Xn interface, as well as the IP address of the neighboring station used to establish the Xn interface, through indications on the E2 interface. This ensures that the WAB node can establish an Xn interface with the neighboring station or an N2 interface with the UE's core network, facilitating flexible deployment of the WAB network architecture.

[0520] 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 process of each method embodiment are optionally combined, and / or the order of some operations is optionally changed. In addition, 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. Ordinary technicians in this field will think of many ways to reorder the operations of this article. In addition, it should be pointed out that the process details involved in a certain embodiment of this article are also applicable to other embodiments in a similar manner, or different embodiments can be used in combination.

[0521] It is understood that in order to implement the functions in the above embodiments, the base station and the terminal include hardware structures and / or software modules that perform the corresponding functions. Those skilled in the art should readily appreciate that, in combination with the units and method steps of the various examples described in the embodiments disclosed in the present application, the embodiments of the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in hardware or in a computer software-driven hardware manner depends on the specific application scenario and design constraints of the technical solution.

[0522] Figures 14 and 15 are schematic diagrams of the structures of possible communication devices provided in embodiments of the present application. These communication devices can be used to implement the functions of any possible transmitting end in the above-mentioned method embodiments, thereby also achieving the beneficial effects of the above-mentioned method embodiments. In the embodiments of the present application, the communication device can be a first relay node or network device, or a module applied to the first relay node or network device. For example, a chip.

[0523] As shown in FIG. 14 , the communication device 1400 includes a processing unit 1410 .

[0524] In a possible implementation, the communication device 1400 may further include a transceiver unit 1420 .

[0525] In a possible implementation, the communication device 1400 may further include a storage unit 1430 .

[0526] In a possible implementation, the communication device 1400 may further include a transceiver unit 1420 and a storage unit 1430 .

[0527] The communication device 1400 is used to implement the functions of any node in the method embodiments shown in Figures 7 and 10 to 13 above.

[0528] When the communication device 1400 is used to implement the functions of the first relay node in the method embodiment shown in FIG7 : the transceiver unit 1420 is used to obtain first information. The processing unit 1410 is used to control the transceiver unit 1420 to send second information based on at least one address information. The processing unit 1410 is also used to perform all operations performed by the communication device 1400 in the embodiment shown in FIG7 , except for the transceiver operations, and / or other processes used to support the technology described herein. The storage unit 1430 is used to store any data, computer instructions, and / or computer programs that may be involved in the various embodiments of this application.

[0529] When communication device 1400 is used to implement the functions of the network device in the method embodiment shown in FIG7 , transceiver unit 1420 is used to send the first information. Processing unit 1410 is also used to perform all operations performed by communication device 1400 in the embodiment shown in FIG7 , except for the transceiver operations, and / or other processes used to support the technology described herein. Storage unit 1430 is used to store any data, computer instructions, and / or computer programs that may be involved in the various embodiments of this application.

[0530] For a more detailed description of the processing unit 1410 and the transceiver unit 1420, please refer to the relevant description of the method embodiments shown in Figures 7, 10 to 13. The processing unit 1410 and the transceiver unit 1420 may also perform other steps, and the specific implementation can refer to the method embodiments, which will not be repeated here.

[0531] Optionally, the transceiver unit 1420 may be a transceiver, which may include an antenna and a radio frequency circuit, etc.

[0532] The processing unit 1410 may be a processor (or a processing circuit), such as a baseband processor, which may include one or more CPUs.

[0533] As shown in FIG15 , the communication device 1500 includes at least one processor 1510. In one possible implementation, the communication device 1500 may further include an interface circuit 1520.

[0534] In a possible implementation, the communication device 1500 may further include a memory 1530 .

[0535] In a possible implementation, the communication device 1500 may further include a memory 1530 and an interface circuit 1520 .

[0536] In some embodiments, the processor 1510 and the memory 1530 are coupled to each other; and / or the processor 1510 and the interface circuit 1520 are coupled to each other. It will be appreciated that the interface circuit 1520 may be a transceiver or an input / output interface. The memory 1530 may be used to store computer instructions executed by the processor 1510, or to store input data required by the processor 1510 to execute the computer instructions, or to store data generated by the processor 1510 after executing the computer instructions.

[0537] When the communication device 1500 is used to implement the method shown in Figures 7, 10 to 13, the processor 1510 can be used to implement the functions of the above-mentioned processing unit 1410, and / or the interface circuit 1520 can be used to implement the functions of the above-mentioned transceiver unit 1420, and / or the memory 1530 can be used to implement the functions of the above-mentioned storage unit 1430.

[0538] The communication device shown in FIG. 14 or 15 is merely an example, and in actual applications the communication device may have more or fewer components than those shown in FIG. 14 or 15 , may combine two or more components, or may have a different component configuration.

[0539] In the embodiments of the present application, when entity A sends information to entity B, A may send the information directly to B or indirectly to B through another entity. Similarly, when entity B receives information from entity A, entity B may directly receive the information sent by entity A or indirectly receive the information sent by entity A through another entity. Entities A and B herein may be RAN nodes or terminals, or modules within a RAN node or terminal. The sending and receiving of information may be information exchange between a RAN node and a terminal, for example, information exchange between a network device and a terminal; the sending and receiving of information may also be information exchange between two RAN nodes, for example, information exchange between a CU and a DU; the sending and receiving of information may also be information exchange between different modules within a device, for example, information exchange between a terminal chip and other modules of the terminal, or information exchange between a network device chip and other modules within the network device.

[0540] In the embodiments of the present application, a network device sends downlink signals or downlink information to a terminal device, and the downlink information is carried on a downlink channel. The terminal device sends uplink signals or uplink information to the network device, and the uplink information is carried on an uplink channel. To communicate with the network device, the terminal device needs to establish a wireless connection with a cell controlled by the network device. The cell with which the terminal device has established a wireless connection is called the serving cell of the terminal device.

[0541] It is understood that the processor in the embodiments of the present application may be a central processing unit (CPU), or may be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA), 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.

[0542] The method steps in the embodiments of the present application can be implemented in hardware or in software instructions that can be executed by a processor. The software instructions can be composed of corresponding software modules, and the software modules can be stored in random access memory, flash memory, read-only memory, programmable read-only memory, erasable programmable read-only memory, electrically erasable programmable read-only memory, registers, hard disk, mobile hard disk, 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 can also be an integral part of the processor. The processor and storage medium can be located in an ASIC. In addition, the ASIC can be located in a network device or a terminal. The processor and storage medium can also exist in a network device or a terminal as discrete components.

[0543] In the above embodiments, all or part of the embodiments may be implemented using software, hardware, firmware, or any combination thereof. When implemented using software, all or part of the embodiments may be implemented in the form of a computer program product. 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 performed in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user device, or other programmable device. The computer program or instructions may be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the computer program or instructions may be transferred from one website, computer, server, or data center to another website, computer, server, or data center via wired or wireless means. The computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or data center that integrates one or more available media. The available medium may be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; an optical medium, such as a digital video disk; or a semiconductor medium, such as a solid-state drive. The computer-readable storage medium may be a volatile or nonvolatile storage medium, or may include both volatile and nonvolatile types of storage media.

[0544] In each embodiment of the present application, unless otherwise specified or provided by logic, 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 a new embodiment based on their inherent logical relationships.

[0545] It is understood that the various numbers used in the embodiments of this application are merely for ease of description and are not intended to limit the scope of the embodiments of this application. The order of the sequence numbers of the above-mentioned processes does not necessarily imply a specific order of execution; the order of execution of the processes should be determined by their functions and inherent logic.

Claims

1. A communication method, characterized in that: The method is applied to a first relay node, where the first relay node includes a first mobile terminal MT and a first access network node; the method includes: Obtaining first information, where the first information is used to indicate at least one address information, and the at least one address information is used to establish a first communication interface and / or a second communication interface, wherein the first communication interface is a communication interface between the first access network node and a first core network node, and the second communication interface is a communication interface between the first access network node and an adjacent access network node, and the first core network node provides communication services for a terminal device accessing the first relay node; Second information is sent based on the at least one address information, where the second information is used to indicate a request to establish the first communication interface and / or the second communication interface.

2. The method according to claim 1, characterized in that The first information includes at least one of the following address information: a first Internet Protocol (IP) address, wherein the first IP address is the IP address of the first access network node, and the first IP address is used to establish the first communication interface and / or the second communication interface; A second IP address, wherein the second IP address is the IP address of the adjacent access network node, and the second IP address is used to establish the second communication interface.

3. The method according to claim 2, characterized in that The first information is determined by at least one of the following network devices: Network management equipment; a second core network node, wherein the second core network node provides communication services for the first relay node; the first core network node; A first host node, where the first host node is a host node of the first relay node.

4. The method according to claim 3, characterized in that The method further comprises: Sending third information, where the third information is used to request the network device to obtain the first information.

5. The method according to claim 4, characterized in that The first information includes the first IP address, and the third information further includes: identification information of the second core network node and / or identification information of the first host node.

6. The method according to any one of claims 2 to 4, characterized in that The anchor point corresponding to the first IP address is the second core network node, and / or the anchor point corresponding to the first IP address is the first host node.

7. The method according to any one of claims 3 to 6, characterized in that The first information includes the second IP address, and the method further includes: Acquire a first identifier, where the first identifier is a cell identifier of a cell managed by the neighboring access network node, or the first identifier is an identifier of the neighboring access network node; The first identifier is sent, where the first identifier is used to request the IP address of the adjacent access network node corresponding to the first identifier.

8. The method according to claim 7, characterized in that The obtaining of the first identifier includes: measuring a first cell to obtain the first identifier, wherein the first cell is a cell managed by the adjacent access network node; or A first identifier is received from the terminal device.

9. The method according to any one of claims 3 to 6, characterized in that: The adjacent access network node is at least one of the following access network nodes: the adjacent access network node having a logical interface with the first core network node; the adjacent access network node having a logical interface with the second core network node; the adjacent access network node having a logical interface with the first host node; The adjacent access network node that is reachable by IP routing to the first core network node; The adjacent access network node that is reachable by IP routing to the second core network node; The adjacent access network node that is reachable to the first host node via IP routing.

10. The method according to claim 9, characterized in that The first information includes a second IP address, and the method further includes: Acquire a second identifier, where the second identifier is an identifier of the adjacent access network node; Send the second identifier, where the second identifier is used to request to obtain the IP address of the adjacent access network node.

11. The method according to any one of claims 1 to 10, characterized in that The adjacent access network node is located within the coverage area of ​​the registration area of ​​the terminal device or the first relay node.

12. The method according to any one of claims 3 to 11, characterized in that: The host node of the first relay node is switched from the second host node to the first host node, and the acquiring of the first information includes: acquiring the first information from the second host node.

13. The method according to any one of claims 1 to 12, characterized in that The adjacent access network node is a non-second relay node, wherein the non-second relay node is any access network node other than the second relay node, and the second relay node includes the second MT and the second access network node.

14. A communication method, characterized in that: The method is applied to a network device, wherein the network device establishes a communication connection with a first relay node, wherein the first relay node includes a first mobile terminal MT and a first access network node; The method comprises: Sending first information, where the first information is used to indicate at least one address information, and the at least one address information is used to establish a first communication interface and / or a second communication interface, wherein the first communication interface is a communication interface between the first access network node and the first core network node, and the second communication interface is a communication interface between the first access network node and an adjacent access network node, and the first core network node provides communication services for terminal devices accessing the first relay node.

15. The method according to claim 14, characterized in that The first information includes at least one of the following address information: a first Internet Protocol (IP) address, wherein the first IP address is the IP address of the first access network node, and the first IP address is used to establish the first communication interface and / or the second communication interface; A second IP address, wherein the second IP address is the IP address of the adjacent access network node, and the second IP address is used to establish the second communication interface.

16. The method according to claim 15, characterized in that The network device includes at least one of the following devices: Network management equipment; a second core network node, wherein the second core network node provides communication services for the first relay node; the first core network node; A first host node, where the first host node is a host node of the first relay node.

17. The method according to claim 16, characterized in that The method further comprises: Acquire third information, where the third information is used to instruct the first relay node to request to acquire the first information; The first information is determined based on the third information.

18. The method according to claim 16 or 17, characterized in that The anchor point corresponding to the first IP address is the first core network node, and / or the anchor point corresponding to the first IP address is the first host node.

19. The method according to any one of claims 15 to 18, characterized in that: The method further comprises: Acquire fourth information, where the fourth information is used to indicate a request to establish the first communication interface and / or the second communication interface; In response to the fourth information, determining the first IP address; Replacing the source IP address in the fourth information with the first IP address to obtain second information, where the second information is used to indicate a request to establish the first communication interface and / or the second communication interface; The second information is sent.

20. The method according to any one of claims 15 to 19, characterized in that The first information includes the second IP address, and the method further includes: Obtaining a first identifier, where the first identifier is used to instruct the first relay node to request obtaining the IP address of the adjacent access network node corresponding to the first identifier; Determine the second IP address based on the first identifier; The first identifier is a cell identifier of a cell managed by the adjacent access network node, or the first identifier is an identifier of the adjacent access network node.

21. The method according to any one of claims 16 to 18, characterized in that The adjacent access network node is at least one of the following access network nodes: the adjacent access network node having a logical interface with the first core network node; the adjacent access network node having a logical interface with the second core network node; the adjacent access network node having a logical interface with the first host node; The adjacent access network node that is reachable by IP routing to the first core network node; The adjacent access network node that is reachable by IP routing to the second core network node; The adjacent access network node that is reachable to the first host node via IP routing.

22. The method according to claim 21, characterized in that The first information includes the second IP address, and the method further includes: Obtain a second identifier, where the second identifier is used to request the IP address of the adjacent access network node, wherein the second identifier is an identifier that identifies the adjacent access network node; The second IP address is determined based on the second identifier, where the second IP address is the IP address of the adjacent access network node.

23. The method according to any one of claims 14 to 22, characterized in that The adjacent access network node is located within the coverage area of ​​the registration area of ​​the terminal device or the first relay node.

24. The method according to any one of claims 16 to 18, 21 and 22, characterized in that The network device is a second core network node and / or the first host node, the host node of the first relay node is switched from the second host node to the first host node, and the method further includes: receiving fifth information from the second host node, the fifth information including a third IP address, where the third IP address is the IP address of the first access network node before the first relay node is switched; Send sixth information, where the sixth information is used to indicate a correspondence between the third IP address and the first IP address.

25. The method according to any one of claims 14 to 24, characterized in that The method further comprises: Acquire seventh information, where the seventh information is used to indicate the IP address of the adjacent access network node; The adjacent access network node is a non-second relay node, and the second IP address includes the IP address of the adjacent access network node, wherein the non-second relay node is any access network node other than the second relay node, and the second relay node includes the second MT and the second access network node.

26. A communication device, characterized in that: include: processing unit and transceiver unit; The transceiver unit is used to receive and / or send signals, and the processing unit is configured to enable the method of any one of claims 1 to 13 to be executed, or the processing unit is configured to enable the method of any one of claims 14 to 25 to be executed.

27. A communication device, characterized in that: include: At least one processor, the at least one processor being coupled to a memory, the memory being used to store computer instructions, the processor being configured to execute the computer instructions so that the communication device performs the method according to any one of claims 1 to 13, or so that the communication device performs the method according to any one of claims 14 to 25.

28. A communication system, characterized in that: The system includes: a first relay node executing the method according to any one of claims 1 to 13, or a network device executing the method according to any one of claims 14 to 25.

29. A computer-readable storage medium, characterized in that The computer-readable storage medium stores instructions or programs, which, when executed on a communication device, enable the communication device to execute the method according to any one of claims 1 to 13, or enable the communication device to execute the method according to any one of claims 14 to 25.

30. A computer program product, characterized in that The computer program product comprises a computer program or instructions, and when the computer program or instructions are run on a computer, the computer is caused to perform the method according to any one of claims 1 to 13, or the computer is caused to perform the method according to any one of claims 14 to 25.

Images