CN112398959A

CN112398959A - RLC channel determination method and device

Info

Publication number: CN112398959A
Application number: CN201910755860.9A
Authority: CN
Inventors: 朱元萍; 戴明增; 曹振臻
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2019-08-15
Filing date: 2019-08-15
Publication date: 2021-02-23
Anticipated expiration: 2039-08-15
Also published as: CN112398959B; WO2021027858A1

Abstract

The application discloses a method and a device for determining an RLC channel, which relate to the field of communication and are used for determining which RLC channel is used for transmitting a message related to an IP address between an IAB node and an IAB host node (specifically, an IAB host DU). The RLC channel determination method comprises the following steps: a first access backhaul integrated IAB node receives first indication information from an IAB host node, wherein the first indication information is used for indicating a first Radio Link Control (RLC) channel which carries a first type of data packet between the first IAB node and a parent node of the first IAB node, the first type of data packet comprises a first type of message, and the first type of message is used for requesting an Internet Protocol (IP) address; and the first IAB node determines the first RLC channel according to the first indication information.

Description

RLC channel determination method and device

Technical Field

The present invention relates to the field of communications, and in particular, to a method and an apparatus for determining a Radio Link Control (RLC) channel.

Background

The fifth generation (5th generation, 5G) communication uses a high frequency carrier for wireless communication. On one hand, because the high-frequency carrier wave has poor propagation characteristics, serious shielding attenuation and narrow coverage range, a large number of base stations are required to be intensively deployed. On the other hand, to provide network coverage to remote areas, base stations are also deployed to remote areas. If the optical fiber return transmission is provided for the base station, the cost is high and the construction difficulty is high.

Therefore, an Integrated Access and Backhaul (IAB) technology is proposed, that is, both an access Link (access Link) and a backhaul Link (backhaul Link) adopt wireless transmission, so as to avoid data being transmitted back and forth by deploying optical fibers.

As shown in fig. 1, the IAB network includes a terminal device, an IAB node (node), and an IAB donor (node), and a link from the terminal device to the IAB donor node via the IAB node is a backhaul link. An F1 interface between a Distributed Unit (DU) similar to a base station and a Centralized Unit (CU) is established between an IAB node and an IAB host node, and a network layer between the IAB node and the IAB host node still transmits a data packet of a user plane or a control plane of the F1 interface based on an Internet Protocol (IP) protocol, but currently, it is not yet realized through which RLC channel the information related to the IP address is transmitted between the IAB node and the IAB host node (specifically, the IAB host DU).

Disclosure of Invention

The embodiment of the present application provides an RLC channel determining method and apparatus, which are used to determine through which RLC channel a message for acquiring an IP address is transmitted between an IAB node and an IAB host node (specifically, an IAB host DU).

In order to achieve the above purpose, the embodiment of the present application adopts the following technical solutions:

in a first aspect, an RLC channel determining method is provided, including: the method comprises the steps that a first access backhaul integrated IAB node receives first indication information from an IAB host node, wherein the first indication information is used for indicating a first Radio Link Control (RLC) channel which bears a first type of data packet between the first IAB node and a father node of the first IAB node, the first type of data packet comprises a first type of message, and the first type of message is used for requesting an Internet Protocol (IP) address; the first IAB node determines a first RLC channel according to the first indication information.

In the RLC channel determining method provided in the embodiment of the present application, the IAB host node configures an RLC channel of the first IAB node, and is configured to send, by the first IAB node, a message requesting an IP address to the IAB host node through the RLC channel, so that it is determined through which RLC channel the message related to the IP address is transmitted between the IAB node and the IAB host node (specifically, an IAB host DU).

In one possible embodiment, the first indication information includes an identification of the first RLC channel. The first RLC channel may be determined based on the identity of the first RLC channel.

In a possible embodiment, the first indication information further includes first condition information or type information of the first type message; the first condition information includes a first value or a first value range of one or more items in an IP five-tuple of the first type packet, the IP five-tuple includes a source IP address, a destination IP address, a source port number, a destination port number, and a transport layer protocol type, and the type information includes one or more of the following: dynamic Host Configuration Protocol (DHCP) messages, Router Solicitation (RS) messages, Router Advertisement (RA) messages, IP broadcast messages and IP multicast messages.

In one possible embodiment, the method further comprises: the first IAB node generates a first data packet; the first IAB node determining the first RLC channel according to the first indication information includes: when one or more items in the IP quintuple of the first data packet correspondingly meet the respective first values or first value ranges of one or more items in the IP quintuple of the first type data packet, determining that the first data packet is borne through a first RLC channel; or, when the message type of the first message included in the first data packet is one of the type information, determining to carry the first data packet through the first RLC channel. When the first RLC channel is not dedicated to carrying the first type of data packets, the first RLC channel carrying the first data packets may be determined according to the first condition information or the type information of the first type of message.

In a possible embodiment, the first indication information further comprises a target value of a preset field of the first type data packet.

In one possible embodiment, the method further comprises: the first IAB node generates a first data packet; when one or more items in the IP quintuple of the first data packet correspondingly meet the respective first values or first value ranges of one or more items in the IP quintuple of the first type data packet, or when the type of the message included in the first data packet is one of type information, setting the preset field of the first data packet as a target value; and when the value of the preset field of the first data packet is the target value, determining that the first data packet is carried through the first RLC channel.

In one possible implementation, the preset field is a differentiated services code point DSCP or a flow label.

In one possible embodiment, the first data packet further includes an identification of the first IAB node. The identity of the first IAB node may indicate to the intermediate IAB node and the IAB host node: the first data packet is from a first data packet.

In one possible embodiment, the identity of the first IAB node is carried in one or more fields of the following first data packet: the system comprises a client hardware address field, a DHCP unique identifier and a BAP address field of a backhaul adaptation protocol BAP layer.

In one possible embodiment, the method further comprises: the first IAB node receives second indication information from the IAB donor node, the second indication information indicating that the target node of the first type of packet on the wireless backhaul link is the IAB donor node.

In one possible embodiment, the second indication information further comprises an identification of the IAB hosting node.

In a possible implementation manner, the first type packet includes an identifier of the IAB host node, the second indication information further includes second condition information or type information of the first type message, the second condition information is a second value or a second value range of one or more items in an IP five-tuple of the first type packet, and the type information includes one or more of the following: DHCP messages, RS messages, RA messages, IP broadcast messages, and IP multicast messages. The intermediate IAB node can know that the target node of the first type data packet in the wireless backhaul link is the IAB host node, so that the intermediate IAB node can forward the first type data packet to the IAB host node.

In one possible embodiment, the method further comprises: the first IAB node generates a second data packet; when one or more items in the IP quintuple of the second packet correspondingly satisfy a second value or a second value range of one or more items in the IP quintuple of the first type packet, or when the type of the message included in the second packet is one of the type information, the second packet includes the identifier of the IAB host node.

In one possible embodiment, the method further comprises: the first IAB node receives a second type of packet, wherein the second type of packet includes a second type message indicating an IP address assigned to the first IAB node.

In a second aspect, an RLC channel determining method is provided, including: the method comprises the steps that a first indication information is determined by an access-return integrated IAB host node, and the first indication information is used for indicating a Radio Link Control (RLC) channel which bears a first type data packet between a first IAB node and a father node of the first IAB node, wherein the first type data packet comprises a first type message, and the first type message is used for the first IAB node to request an Internet Protocol (IP) address; the IAB host node sends the first indication information to the first IAB node.

In a possible embodiment, the first indication information further includes first condition information or type information of the first type message; the first condition information includes a first value or a first value range of one or more items in an IP five-tuple of the first type packet, the IP five-tuple includes a source IP address, a destination IP address, a source port number, a destination port number, and a transport layer protocol type, and the type information includes one or more of the following: dynamic Host Configuration Protocol (DHCP) messages, Router Solicitation (RS) messages, Router Advertisement (RA) messages, IP broadcast messages and IP multicast messages. When the first RLC channel is not dedicated to carrying the first type of data packets, the first RLC channel carrying the first data packets may be determined according to the first condition information or the type information of the first type of message.

In a possible embodiment, the first indication information further includes a target value of a preset field in the first type packet.

In one possible embodiment, the method further comprises: the IAB host node receives a first type data packet from a first IAB node; the IAB host node acquires an IP address distributed for the first IAB node; the IAB donor node sends a second type of data packet to the first IAB node, wherein the second type of data packet comprises a second type of message, and the second type of message is used for indicating an IP address allocated to the first IAB node.

In one possible embodiment, the method further comprises: the IAB host node determines a mapping relationship between the IP address and the identity of the first IAB node. When the next time the IAB host node acquires the data packet with the destination IP address as the above IP address, it knows that the data packet should be forwarded to the first IAB node.

In one possible embodiment, the method further comprises: the IAB host node sends second indication information to the first IAB node, wherein the second indication information indicates that the target node of the first type of data packet on the wireless backhaul link is the IAB host node.

In a possible implementation manner, the second indication information further includes second condition information or type information of the first type message, where the second condition information is a second value or a second value range of each of one or more items in the IP quintuple of the first type packet, and the type information includes one or more of the following: DHCP messages, RS messages, RA messages, IP broadcast messages, and IP multicast messages. The intermediate IAB node can know that the target node of the first type data packet in the wireless backhaul link is the IAB host node, so that the intermediate IAB node can forward the first type data packet to the IAB host node.

In a third aspect, a radio link control, RLC, channel determination method is provided, including: the access backhaul integrated IAB host distributed unit DU receives third indication information from the IAB host centralized unit CU, where the third indication information is used to indicate a second RLC channel, which carries a second type of data packet, between the IAB host DU and a child IAB node of the IAB host DU, where the second type of data packet includes a second type of message, the second type of message is used to indicate an internet protocol IP address allocated to the first IAB node, and the first IAB node is a child node of the IAB host DU or the first IAB node is connected to the IAB host DU through one or more intermediate IAB nodes; and the IAB host DU determines a second RLC channel according to the third indication information.

In the RLC channel determining method provided in the embodiment of the present application, the IAB host CU configures an RLC channel of the IAB host DU, and is configured to send a message indicating an IP address to a child node (for example, an IAB node) of the IAB host DU through the RLC channel by the IAB host DU, so that it is determined through which RLC channel the message related to acquiring the IP address is transmitted between the IAB node and the IAB host node (specifically, the IAB host DU).

In one possible embodiment, the third indication information includes an identification of the second RLC channel. The second RLC channel may be determined based on the identity of the second RLC channel.

In a possible implementation manner, the third indication information further includes third condition information or type information of the second type message, where the third condition information includes a third value or a third value range of one or more items in an IP five-tuple of the second type packet, the IP five-tuple includes a source IP address, a destination IP address, a source port number, a destination port number, and a transport layer protocol type, and the type information includes one or more of the following: dynamic Host Configuration Protocol (DHCP) messages, Router Solicitation (RS) messages, Router Advertisement (RA) messages, IP broadcast messages and IP multicast messages.

In a possible embodiment, the third indication information further includes a target value of a preset field of the second type packet.

In one possible embodiment, the method further comprises: generating a second data packet by the IAB host DU; when one or more items in the IP quintuple of the second data packet correspondingly satisfy a third value or a third value range of one or more items in the IP quintuple of the second type data packet, or when the type of the message included in the second data packet is one of the type information, setting a preset field of the second data packet as a target value; and when the value of the preset field of the second data packet is the target value, the second data packet is carried through the second RLC channel. And when the second RLC channel is not exclusively used for carrying the second type of data packets, determining the second RLC channel carrying the second data packets according to the third condition information or the type information of the third type of message.

In one possible embodiment, the method further comprises: the method comprises the steps that an IAB host DU receives a first type data packet from a child node of the IAB host DU, wherein the first type data packet comprises a first message, and the first message is used for a first IAB node to request an IP address; the IAB host DU acquires an IP address distributed for the first IAB node; the IAB host DU sends the second type of packet over the second RLC channel.

In one possible embodiment, the method further comprises: the IAB host DU determines the mapping between the IP address and the identity of the first IAB node. When the next time the IAB host DU acquires the data packet with the destination IP address as the above IP address, it knows that it should be forwarded to the first IAB node.

In a fourth aspect, a radio link control, RLC, channel determination method is provided, including: the access backhaul integrated IAB host centralized unit CU determines third indication information, where the third indication information is used to indicate a second RLC channel, which carries a second type of data packet, between the IAB host distributed unit DU and a child IAB node connected to the IAB host DU, where the second type of data packet includes a second type of message, the second type of message is used to indicate an internet protocol IP address allocated to the first IAB node, and the first IAB node is a child node of the IAB host DU or the first IAB node is connected to the IAB host DU through one or more intermediate IAB nodes; the IAB host CU sends third indication information to the IAB host DU.

In a possible implementation manner, the third indication information further includes third condition information or type information of the second type message, where the third condition information includes a third value or a third value range of one or more items in an IP five-tuple of the second type packet, the IP five-tuple includes a source IP address, a destination IP address, a source port number, a destination port number, and a transport layer protocol type, and the type information includes one or more of the following: dynamic Host Configuration Protocol (DHCP) messages, Router Solicitation (RS) messages, Router Advertisement (RA) messages, IP broadcast messages and IP multicast messages. And when the second RLC channel is not exclusively used for carrying the second type of data packets, determining the second RLC channel carrying the second data packets according to the third condition information or the type information of the third type of message.

In a possible embodiment, the third indication information further includes a target value of a preset field of the second type packet; wherein the preset field is a Differentiated Services Code Point (DSCP) or a flow label.

In a fifth aspect, a communication apparatus is provided, including: the device comprises a processing module and a transmitting-receiving module; the processing module and the transceiver module are adapted to perform the method according to the first aspect and any of the above.

In a sixth aspect, a communication apparatus is provided, including: the device comprises a processing module and a transmitting-receiving module; the processing module and the transceiver module are adapted to perform the method according to the second aspect and any of the above.

In a seventh aspect, a communication apparatus is provided, including: the device comprises a processing module and a transmitting-receiving module; the processing means and the transceiver means are adapted to perform the method according to the third aspect and any of the above.

In an eighth aspect, there is provided a communication apparatus comprising: the device comprises a processing module and a transmitting-receiving module; the processing module and the transceiver module are configured to perform the method according to the fourth aspect and any one of the above aspects.

In a ninth aspect, there is provided a communication device comprising a processor, a memory and a transceiver, the processor being coupled with the memory, the method as described in the first aspect and any one of the first aspect being performed when the processor executes computer programs or instructions in the memory.

In a tenth aspect, there is provided a communication device comprising a processor, a memory and a transceiver, the processor being coupled with the memory, the method according to the second aspect and any of the above being performed when the processor executes computer programs or instructions in the memory.

In an eleventh aspect, there is provided a communication device comprising a processor, a memory and a transceiver, the processor being coupled with the memory, the method according to the third aspect and any of the above being performed when the processor executes the computer program or instructions in the memory.

In a twelfth aspect, there is provided a communication device comprising a processor, a memory and a transceiver, the processor being coupled with the memory, the method according to the fourth aspect and any of the above being performed when the processor executes the computer program or instructions in the memory.

In a thirteenth aspect, there is provided a chip comprising: a processor and an interface for retrieving from a memory and executing a computer program stored in said memory, for performing a method according to the first aspect and any one thereof, or for performing a method according to the second aspect and any one thereof, or for performing a method according to the third aspect and any one thereof, or for performing a method according to the fourth aspect and any one thereof.

In a fourteenth aspect, there is provided a computer readable storage medium having stored therein instructions which, when run on a computer or processor, cause the computer or processor to perform a method as described in the first aspect and any one thereof, or to perform a method as described in the second aspect and any one thereof, or to perform a method as described in the third aspect and any one thereof, or to perform a method as described in the fourth aspect and any one thereof.

In a fifteenth aspect, there is provided a computer program product comprising instructions which, when run on a computer or processor, cause the computer or processor to perform the method according to the first aspect and any one thereof, or the method according to the second aspect and any one thereof, or the method according to the third aspect and any one thereof, or the method according to the fourth aspect and any one thereof.

A sixteenth aspect provides a communication system comprising a communication apparatus according to the fifth aspect and a communication apparatus according to the sixth aspect, or a communication apparatus according to the seventh aspect and a communication apparatus according to the eighth aspect, or a communication apparatus according to the ninth aspect and a communication apparatus according to the tenth aspect, or a communication apparatus according to the eleventh aspect and a communication apparatus according to the twelfth aspect.

Technical effects of the fifth to sixteenth aspects may be as described with reference to various possible implementations of the first to fourth aspects.

Drawings

Fig. 1 is a schematic architecture diagram of an IAB network according to an embodiment of the present application;

fig. 2 is a schematic architecture diagram of a communication system according to an embodiment of the present application;

fig. 3 is a schematic structural diagram of a network device according to an embodiment of the present application;

fig. 4A is a schematic diagram of interaction for requesting an IP address in a DHCP protocol based on IPv4 according to an embodiment of the present application;

fig. 4B is a schematic diagram of interaction of requesting an IP address in a DHCPv6 protocol based on IPv6 according to an embodiment of the present application;

fig. 4C is an interactive schematic diagram of requesting an IP address based on an IPv6 stateless address configuration manner according to an embodiment of the present application;

fig. 5 is a first flowchart illustrating an RLC channel determining method according to an embodiment of the present application;

fig. 6 is a flowchart illustrating a second RLC channel determining method according to an embodiment of the present application;

fig. 7 is a third flowchart illustrating an RLC channel determining method according to an embodiment of the present application;

fig. 8 is a fourth flowchart illustrating an RLC channel determining method according to an embodiment of the present application;

fig. 9 is a fifth flowchart illustrating an RLC channel determining method according to an embodiment of the present application;

fig. 10 is a sixth schematic flowchart of a RLC channel determining method according to an embodiment of the present application;

fig. 11 is a seventh flowchart illustrating a method for determining an RLC channel according to an embodiment of the present application;

fig. 12 is an eighth flowchart of a RLC channel determining method according to an embodiment of the present application;

fig. 13 is a schematic structural diagram of a communication device according to an embodiment of the present application;

fig. 14 is a schematic structural diagram of another communication device according to an embodiment of the present application;

fig. 15 is a schematic structural diagram of another communication device according to an embodiment of the present application;

fig. 16 is a schematic structural diagram of another communication device according to an embodiment of the present application.

Detailed Description

This application is intended to present various aspects, embodiments or features around a system that may include a number of devices, components, modules, and the like. It is to be understood and appreciated that the various systems may include additional devices, components, modules, etc. and/or may not include all of the devices, components, modules etc. discussed in connection with the figures. Furthermore, a combination of these schemes may also be used.

The network architecture and the service scenario described in the embodiment of the present application are for more clearly illustrating the technical solution of the embodiment of the present application, and do not form a limitation on the technical solution provided in the embodiment of the present application, and as a person of ordinary skill in the art knows that along with the evolution of the network architecture and the appearance of a new service scenario, the technical solution provided in the embodiment of the present application is also applicable to similar technical problems.

The embodiment of the present application is described by depending on a scenario of a 5G network in a wireless communication network, and it should be noted that the scheme in the embodiment of the present application may also be applied to other wireless communication networks, and corresponding names may also be replaced by names of corresponding functions in other wireless communication networks.

Various aspects are described in connection with a wireless network device, which may be a base station, and the base station may be configured to communicate with one or more terminal devices, and may also be configured to communicate with one or more base stations having some terminal device functions (e.g., communication between a macro base station and a micro base station, such as an access point); a base station may also be called, and may include some or all of the functionality of, an access point, a node B, an evolved node B (enb), or some other network entity. The base stations may communicate with the terminal devices over the air interface. The communication may be through one or more sectors. The base station may act as a router between the terminal device and the rest of the access network, including an Internet Protocol (IP) network, by converting received air-interface frames to IP packets. The base station may also coordinate the management of attributes for the air interface and may also be a gateway between a wired network and a wireless network.

As shown in fig. 2, a communication system provided in an embodiment of the present application includes: a first IAB node 21 and an IAB host node 23. Optionally, a second IAB node 22 may also be included.

The first IAB node 21 may be directly connected to the IAB donor node 23, or the first IAB node 21 may be connected to the second IAB node 22, and the second IAB node 22 is connected to the IAB donor node 23. The first IAB node 21, the second IAB node 22, and the IAB host node 23 are connected by wireless links. It should be noted that the number of the second IAB nodes 22 is not limited in the present application, that is, the first IAB node 21 may communicate with the IAB host node 23 through a plurality of second IAB nodes 22. For example, a first IAB node sends a data packet to at least one second IAB node, which forwards the data packet to an IAB host node via other second IAB nodes. Or, the IAB host node sends a data packet to at least one second IAB node, and the second IAB node forwards the data packet to the first IAB node through other second IAB nodes.

In the embodiment of the present application, an intermediate IAB node (second IAB node) between the first IAB node and the IAB host node is taken as an example for description, but the present invention is not intended to be limited thereto.

The first IAB node 21 or the second IAB node 22 may also be referred to as a Relay Node (RN), and may provide a wireless access service for the terminal device, where the service data of the terminal device is transmitted to the IAB host node by the IAB node through a wireless backhaul link.

The first IAB node 21 or the second IAB node 22 may include a Mobile Termination (MT) part and a Distributed Unit (DU) part. For example, when the first IAB node 21 or the second IAB node 22 faces its parent node, it may act as an end device, i.e., as an MT; when the first IAB node 21 or the second IAB node 22 faces its child node (which may be another IAB node or a common terminal device), it may act as a network device, i.e. as a DU for the base station.

The IAB host node 23 may also be referred to as a donor base station (donor gdnb), and the IAB host node 23 may be an access network element having a complete base station function, and may also be an access network element including an IAB host Distributed Unit (DU) 231 and an IAB host Centralized Unit (CU) 232. The IAB host DU 231 and the IAB host CU 232 may be connected by a wired link. The IAB host node 23 is connected to a network element of a core network (e.g., to a 5G core network, 5GC) serving the terminal device and provides a wireless backhaul function for the IAB node. It should be noted that the IAB host CU 232 may also be in a form in which a Control Plane (CP) and a User Plane (UP) are separated, for example, the IAB host CU 232 may further include one CU-CP and at least one CU-UP.

In the present embodiment, the second IAB node 22 is a neighboring node that provides backhaul service to the first IAB node 21, and therefore the second IAB node 22 is considered as a parent node of the first IAB node 21, and accordingly, the first IAB node 21 is considered as a child node of the second IAB node 22. If the first IAB node 21 is directly connected to the IAB host node 23, the IAB host node 23 is a parent node of the first IAB node 21, and the first IAB node 21 is a child node of the IAB host node 23.

The structure of the first IAB node 21, the second IAB node 22, and the IAB host node 23 is explained below.

The first IAB node 21, the second IAB node 22, and the IAB host node 23 described above may be collectively referred to as a network device.

As shown in fig. 3, the network device 30 includes a processor 301, a memory 302, and a transceiver 303. The transceiver 303 includes a transmitter 3031, a receiver 3032, and an antenna 3033.

The transmitter 3031 may be used to transmit data information via the antenna 3033 and the receiver 3032 may be used to receive data information via the antenna 3033. For example, the first IAB node 21 may transmit data to the second IAB node 22 through its transmitter and the first IAB node 21 may receive data from the second IAB node 22 through its receiver.

The memory 302 may be used to store software programs and data. Processor 301 performs various functions of network device 30 and data processing by executing software programs and/or data stored in memory 302. The memory 302 may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application program required for at least one function, and the like; the storage data area may store data created according to the use of the network device 30, and the like. Further, the memory 302 may include high speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device.

The processor 301 is a control center of the network device 30, connects various parts of the entire cellular phone with various interfaces and lines, and performs various functions of the network device 30 and processes data by running or executing software programs stored in the memory 302 and calling data stored in the memory 302. In some embodiments, processor 301 may include one or more processing units; the processor 301 may also be a System On Chip (SOC) that may integrate an application processor, a baseband processor, a Digital Signal Processor (DSP), and the like. Wherein, the application processor mainly processes an operating system, an application program and the like; the baseband processor mainly processes wireless communication; the DSP is mainly used to quickly implement various digital signal processing algorithms. It will be appreciated that the baseband processor described above may not be integrated into the processor 301. Processor 301 may perform the RLC channel determination methods described herein.

In this embodiment of the present application, if a Dynamic Host Configuration Protocol (DHCP) is used to allocate an IP address to an IAB node, the IAB host DU 231 may serve as a node for managing IP address allocation, for example, as a DHCP server; alternatively, the communication system may further include a DHCP server 24, the IAB host DU 231 serves as a DHCP relay or a DHCP proxy, and the IAB host DU 231 and the DHCP server 24 are connected by a wired link.

After the first IAB node 21 accesses the network through the cell served by the second IAB node 22, the first IAB node 21 needs to acquire an IP address for its DU part. The first IAB node 21 may act as a DHCP client requesting an IP address from the DHCP server 24 via the DHCP protocol. If the first IAB node 21 acquires the IP address by using the DHCP protocol, it needs to perform necessary configuration in advance on two wireless backhaul links (i.e. between the first IAB node 21 and the second IAB node 22, and between the second IAB node 22 and the IAB host DU 231), so that the first IAB node 21 can smoothly interact DHCP messages with the DHCP server through the second IAB node 22 and the IAB host DU 231.

Fig. 4A is a schematic diagram illustrating interaction of requesting an IP address in the DHCP protocol based on IPv 4. The whole interaction process comprises S401-S404:

s401, the DHCP client sends a DHCP discovery (DHCP Discover) message to the DHCP server.

When the DHCP client is started, its own IP address is automatically configured to 0.0.0.0, and since normal communication cannot be performed using 0.0.0.0, the client must acquire a legal address through the DHCP server. Since the client does not know the IP address of the DHCP server, it broadcasts a DHCP discover message using an address of 0.0.0.0 as a source IP address, a UDP68 port as a source port, 255.255.255.255 as a destination IP address, and a UDP67 port as a destination port to request an IP address.

S402, the DHCP server sends a DHCP pre-allocation (DHCP Offer) message to the DHCP client.

When the DHCP server receives the DHCP discovery message sent by the client, whether a legal IP address is allocated to the client is searched in the IP address pool. Because the DHCP client does not have an IP address, the DHCP server broadcasts DHCP pre-allocation information using its own IP address as the source IP address, a UDP67 port as the source port, a 255.255.255.255 port as the destination IP address, and a UDP68 port as the destination port. The DHCP pre-allocation message comprises: the MAC address of the DHCP client, the IP address assigned by the DHCP server, the subnet mask, a default gateway (route), the lease term, and the IP address of the DHCP server.

S403, the DHCP client sends a DHCP Request (DHCP Request) message to the DHCP server.

There may be multiple DHCP servers in a network and a DHCP client may receive multiple DHCP pre-allocation messages. The DHCP client selects the allocated IP address from the received first DHCP pre-allocation message, and the DHCP lease takes effect. The DHCP client still broadcasts the DHCP request message using an address of 0.0.0.0 as the source IP address, a UDP68 port as the source port, a 255.255.255.255 as the destination IP address, and a UDP67 port as the destination port. The DHCP request message includes a service identifier (e.g., IP address) of the server to which the DHCP client selects an IP address.

S404, the DHCP server sends a DHCP acknowledgement (DHCP Ack) message to the DHCP client.

After receiving the DHCP request message, the DHCP server broadcasts a DHCP acknowledge message using its own IP address as the source IP address, using the UDP67 port as the source port, using 255.255.255.255 as the destination IP address, and using the UDP68 port as the destination port. The DHCP acknowledge message includes a valid lease for the IP address and other possible configuration information. And when the DHCP client receives the DHCP confirmation message, configuring the allocated IP address and completing the interactive process of requesting the IP address.

Fig. 4B is an interactive diagram of requesting IP addresses based on the stateful address configuration method in the DHCPv6 protocol of IPv 6. The whole interaction process comprises S411-S414:

s411, the DHCP client sends a DHCPv6 solicitation (DHCPv6 Solicit) message to the DHCP server.

When sending the DHCPv6 solicitation message, the DHCP client uses a local link address (link-local addresses) as a source IP address. The IPv6 protocol specifies that each IPv6 interface has a local link address, and a FE 80:/10 address block is used, which is similar to a 169.254.0.0/16 network segment in IPv4, when a DHCP client is started, a local link address is automatically configured, so that the client communicates with a DHCP server by using the local link address to acquire a legal address. Since the client does not know the IP address of the DHCP server, the DHCPv6 solicitation message is sent using the multicast address (e.g., FF02::1:2 for all servers and relay nodes within the broadcast domain, or FF05::1:3 for all servers within the broadcast domain) as the destination IP address to request the IP address. The DHCP client sends the DHCPv6 solicitation message using UDP port 546 as the source port and UDP port 547 as the destination port.

Optionally, the DHCPv6 solicitation message may carry a rapid commit (rapid commit) option, which indicates that the DHCP client needs the DHCP server to be able to rapidly allocate an address (or prefix) and network configuration parameters to the DHCP client.

S412, the DHCP server sends a DHCPv6 notify (DHCPv6Advertise) message to the DHCP client.

When the DHCP server receives a DHCPv6 solicitation message sent by the client, an unallocated IPv6 address (or prefix) is selected from an IPv6 address (or prefix) pool and allocated to the DHCP client, a DHCP notification message is sent to the DHCP client to notify the DHCP client of the IPv6 address (or prefix) and network configuration parameters which can be allocated to the DHCP client, and the DHCP server uses a local link address of the DHCP server as a source IP address and uses a local link address of the DHCP client as a destination IP address. The DHCP server sends the DHCPv6 notify message using UDP port 547 as the source port and UDP port 546 as the destination port.

Optionally, if the DHCP server supports two-step interaction and carries a rapid commit (rapid commit) option in the received DHCPv6 solicitation message, the DHCP server may directly perform step S414 without performing steps S412 and S413.

S413, the DHCP client sends a DHCPv6 Request (DHCPv6 Request) message to the DHCP server.

If the DHCP client receives the DHCPv6 notification message replied by the plurality of DHCP servers, one of the DHCP servers is selected according to the configured policy (such as the message receiving sequence, the server priority and the like), and a DHCPv6 request message is sent to the DHCP server to request the DHCP server to confirm the distributed IPv6 address (or prefix) and the network configuration parameters.

When the DHCP client sends the DHCPv6 request message, it can still use its own local link address as the source IP address, a multicast address (e.g., FF02::1:2 for all servers and relay nodes within the broadcast domain, or FF05::1:3 for all servers within the broadcast domain) as the destination IP address, UDP port 546 as the source port, and UDP port 547 as the destination port.

Or, if the DHCPv6 notification message carries a server unicast (server unicast) option and the DHCP client also supports the server unicast, the DHCP client sends a DHCPv6 request message to the DHCP server in a unicast manner, and the DHCP client uses its own local link address as a source IP address, uses the local link address of the DHCP server as a destination IP address, uses the UDP port 546 as a source port, and uses the UDP port 547 as a destination port.

S414, the DHCP server sends a DHCPv6 Reply (DHCPv6 Reply) message to the DHCP client.

The DHCP server sends a DHCPv6 reply message to the DHCP client confirming that the DHCP client is allocated an IPv6 address (or prefix) and network configuration parameters for use. When the DHCP server sends the DHCPv6 reply message to the DHCP client, the DHCP server uses its own local link address as the source IP address, uses the DHCP client's local link address as the destination IP address, uses the UDP port 547 as the source port, and uses the UDP port 546 as the destination port.

Fig. 4C is an interactive schematic diagram of acquiring an IP address based on an IPv6 stateless address configuration mode. The whole interaction process comprises S421-S422:

s421, the device needing to obtain the IP address sends a router Request (RS) message to the IPv6 router.

The device that needs to obtain the IP address sends a router solicitation message with the purpose of obtaining network prefix information and other parameters of the local network, and when sending the message, the local link address of the device is used as the source IP address, and the multicast address (e.g. the multicast addresses FF02::2 of all routers) is used as the destination IP address.

S422, the IPv6 router sends a Router Advertisement (RA) message to the equipment needing to acquire the IP address.

The router advertisement message carries an IPv6 address prefix, and is used for generating a global IPv6 address by a device that needs to acquire an IP address. The router sends the router advertisement message using the IPv6 address of the router (e.g., the local link address of the router) as the source IP address, may use a multicast address (e.g., the multicast addresses FF02::1 of all nodes of the local link) as the destination IP address, or may use the local link address of the device sending the router solicitation message as the destination IP address.

If the IAB node is used as a device that needs to acquire an IP address, and a stateless address configuration mode is adopted, the IAB host DU may be used as an IPv6 router to send a router advertisement message to the IAB node.

As mentioned before, it is not currently implemented over which RLC channel IP address related messages are transmitted between an IAB node and an IAB hosting node (IAB hosting DU). In the embodiment of the present application, based on the DHCP protocol, the DHCPv6 protocol, or the stateless address configuration mode of IPv6, the interaction of the IP address between the IAB node and the IAB host node (IAB host DU) is implemented, and it is first required to determine which RLC channel the IAB node carries the data packet sent to the IAB host node (IAB host DU) and determine which RLC channel the IAB host node (IAB host DU) carries the data packet sent to the IAB node, so as to complete the interaction.

Specifically, an IAB host CU 232 of the IAB host node 23 configures an uplink wireless backhaul link for the first IAB node 21, so that the first IAB node 21 determines a first RLC channel, where the first RLC channel is used to carry a first type of data packet between the first IAB node and a parent node of the first IAB node. After the first IAB node 21 accesses the network through the cell served by the second IAB node 22, the first IAB node 21 sends a DHCP message or a router solicitation message requesting an IP address to the IAB host DU 231 through the first RLC channel. Specifically, if there is no intermediate IAB node between the first IAB node 21 and the IAB host DU 231, the first IAB node 21 directly sends the DHCP message or the router solicitation message to the IAB host DU 231 through the first RLC channel; if there is an intermediate IAB node between the first IAB node and the IAB host DU 231, the first IAB node 21 sends the DHCP message or the router solicitation message to the intermediate IAB node through the first RLC channel, and then the intermediate IAB node forwards the DHCP message or the router solicitation message to the IAB host DU 231.

The IAB home DU 231 of the IAB home node 23 serves as a DHCP server or a DHCP proxy or an IPv6 router in stateless address configuration, and allocates an IP address or prefix (i.e., IPv6 address prefix) to the first IAB node 21; alternatively, the IAB host DU 231 of the IAB host node 23 may acquire the IP address or prefix allocated to the first IAB node 21 from the DHCP server as a DHCP relay. The IAB host CU 232 of the IAB host node 23 configures the downlink wireless backhaul link to the IAB host DU 231, so that the IAB host DU 231 determines a second RLC channel, and the second RLC channel is used for carrying the second-type data packet between the IAB host DU and the sub-IAB node of the IAB host DU. The IAB host DU 231 transmits a DHCP message or a router advertisement message indicating an IP address to the first IAB node 21 through the second RLC channel. Thereby enabling the first IAB node 21 to acquire the IP address assigned to it by the DHCP server. Specifically, if there is no intermediate IAB node between the first IAB node 21 and the IAB host DU 231, the IAB host DU 231 directly sends the DHCP message or the router advertisement message to the first IAB node 21 through the second RLC channel; if there is an intermediate IAB node between the first IAB node and the IAB host DU 231, the IAB host DU 231 sends the DHCP message or the router advertisement message to the intermediate IAB node through the second RLC channel, and the intermediate IAB node forwards the DHCP message or the router advertisement message to the first IAB node 21.

In the present application, the DHCP message for requesting an IP address may be one or more of the following: a DHCP Discover (DHCP Discover) message, a DHCP Request (DHCP Request) message, a DHCPv6 solicitation (DHCPv6 Solicit) message, a DHCPv6 Request (DHCPv6 Request) message. The DHCP message for requesting the IP address may also be a DHCP message sent by another DHCP client to the DHCP server, such as a DHCP Release (DHCP Release) message, a DHCPv6 Release (DHCPv6 Release) message, a DHCP notify (DHCP Inform) message, a DHCP Decline (DHCP Decline) message, a DHCPv6Decline (DHCPv6Decline) message, a DHCPv6 acknowledge (DHCPv6Confirm) message, a DHCPv6 update (DHCPv6 Renew) message, a DHCPv6 rebinding (DHCPv6 Rebind) message, and the like.

The DHCP message for indicating an IP address may include one or more of the following: a DHCP acknowledge (DHCP Ack) message, a DHCP pre-allocate (DHCP Offer) message, a DHCPv6 notify (DHCPv6Advertise) message, a DHCPv6 Reply (DHCPv6 Reply) message. The DHCP message for requesting the IP address may also be a DHCP message sent by another DHCP server to the DHCP client, such as a DHCP non-acknowledgement (DHCP NAK) message, a DHCPv6 reconfiguration (DHCPv6 reconfiguration) message, and the like, which is not limited in this application.

It should be noted that, in the embodiment of the present application, if the IAB donor node is not in the CU and DU separation form, the IAB donor node performs the above configuration function on the first IAB node; if the IAB host node is in a CU and DU separated form, the IAB host node CU performs the configuration function on the first IAB node and the IAB host DU; if the IAB host CU is in CP and UP split form, then it is the IAB host CU-CP that performs the above-described configuration functions for the first IAB node and the IAB host DU.

Currently, a Radio Bearer (RB) at a terminal side corresponds to an upper protocol layer (e.g., PDCP layer) section and a lower protocol layer (e.g., RLC layer and MAC layer) section. For an IAB node, the channel between the RLC layer and upper protocol layers (e.g., PDCP layer, BAP layer, depending on the upper protocol layer of the RLC layer in particular) may be referred to as an RLC channel. A channel between the RLC layer and a lower protocol layer (e.g., MAC layer) may be referred to as a logical channel, and a logical channel may also be referred to as a MAC logical channel. The RLC layer entity and the MAC logical channel may be collectively referred to as an RLC bearer.

In this embodiment of the present application, the related RLC channel is an RLC channel of the IAB node in the wireless backhaul link, and because the RLC channel of the IAB node in the wireless backhaul link corresponds to an RLC layer entity, an RLC bearer (RLC bearer), and a logical channel (LCH for short) one to one, the RLC channel in this embodiment of the present application may also be replaced by a backhaul RLC channel, a backhaul RLC bearer (backhaul RLC bearer), a backhaul bearer (backhaul bearer), and a logical channel, which are not limited in this application.

In the embodiment of the present application, the first RLC channel is referred to as an uplink RLC channel, that is, an RLC channel in a direction from the first IAB node to the IAB host node. The second RLC channel refers to the downlink RLC channel, i.e., the RLC channel in the direction from the IAB host node to the first IAB node. The first RLC channel and the second RLC channel may be the same RLC channel if there is no intermediate IAB node between the first IAB node and the IAB host node and the same RLC channel can be used for both uplink and downlink transmissions.

As shown in fig. 5, the RLC channel determining method includes:

s501, the IAB host node determines first indication information for the first IAB node.

Specifically, this step may be performed by the IAB host node, the IAB host CU of the IAB host node, or the IAB host CU-CP of the IAB host node.

The first indication information is used to indicate a first Radio Link Control (RLC) channel carrying a first type of packet between the first IAB node and a parent node of the first IAB node. In an embodiment of the present application, the parent node of the first IAB node may be the second IAB node. When the first IAB node is directly connected to the IAB host node (which may be understood as not passing through other intermediate IAB nodes), the parent node of the first IAB node may be the IAB host node or the IAB host DU.

It can be understood that the first type packet refers to a certain type packet, and the first indication information may indicate characteristics of the type packet, so that after the first IAB node generates the packet, it may determine whether the generated packet satisfies the characteristics of the first type packet, and if so, the generated packet is carried through the first RLC channel.

The first type of packet may comprise a first type of message for the first IAB node to request an IP address. For example, the first type packet may be an IP packet, and the first type message is a payload portion of the IP packet, and may be a self-defined IP address Request message, or may be a DHCP discover message in the DHCP protocol, a DHCP Request message, or may be a DHCPv6 solicitation (DHCPv6 Solicit) message in the DHCPv6 protocol, or a DHCPv6 Request (DHCPv6 Request) message. Alternatively, the first type packet may be a BAP packet, and the first type message may be a payload portion of the BAP packet, and may be an IP broadcast message or an IP multicast message, which may be used to request an IP address. It should be noted that the IP broadcast message or the IP multicast message may also be used for other purposes, and the application is not limited in this application.

The first RLC channel may be dedicated to carrying a first type of data packet, and may also be used to carry other types of data packets, which is not limited in this application.

The first indication information may include an identification of the first RLC channel for uniquely identifying the first RLC channel on the first IAB node and its parent node link. Optionally, the first indication information may further include a first mapping rule in addition to the identifier of the first RLC channel. And when the data packet to be sent meets the first mapping rule, mapping the data packet to be sent to the first RLC channel. For example, if the first RLC channel is not dedicated for transmitting the first type of data packet, it may also be used for transmitting other types of messages, and when the data packet to be transmitted satisfies the first mapping rule, the data packet to be transmitted is mapped to the first RLC channel. The first mapping rule will be described in detail in the following steps.

S502, the IAB host node sends first indication information to the first IAB node.

Accordingly, the first IAB node receives the first indication information from the IAB host node.

The first indication information may be carried in a Radio Resource Control (RRC) message, such as an RRC message sent by the IAB host node to the MT part of the first IAB node.

S503, the first IAB node determines the first RLC channel according to the first indication information.

The first IAB node may determine the first RLC channel based on an identity of the first RLC channel when the first RLC channel is dedicated to transmitting the first type of packet.

Optionally, the first indication information may further include the following first mapping rule:

optionally, in a possible implementation, the first indication information may further include first condition information or type information of the first type message. The type information of the first type message may include one or more of the following: DHCP messages, RS messages, RA messages, IP broadcast messages, IP multicast messages, and the like. The first condition information may include a first value or a first value range of one or more items in an IP five-tuple of the first type packet, where the IP five-tuple includes a source IP address, a destination IP address, a source port number, a destination port number, and a transport layer protocol type.

After the first IAB node generates a first data packet (the first data packet may refer to a data packet to be sent by the first IAB node to a parent node of the first IAB node, and hereinafter referred to as a data packet to be sent for short), when a message type of a message included in the first data packet is one of type information of a first type message, the first IAB node may determine to carry the first data packet through the first RLC information according to an identifier of the first RLC channel; or, when one or more of the IP quintuple of the first packet correspondingly satisfies a first value or a first value range of one or more of the IP quintuple of the first type packet, the first IAB node may determine to bear the first packet through the first RLC channel according to the identifier of the first RLC channel.

Exemplarily, taking the DHCP protocol based on IPv4 as an example, for the DHCP discover message and the DHCP request message, the destination IP address is an IP broadcast address (IPv 4 address 255.255.255.255 with each bit being 1), and the first mapping rule may be: mapping a data packet with a target IP address as a broadcast address to a specified first RLC channel for transmission; or, mapping the data packet whose destination IP address is an IP broadcast address, whose transport layer protocol type is User Datagram Protocol (UDP), whose source port number is 68, and whose destination port number is 67, onto a specified first RLC channel for transmission.

For example, taking the IPv 6-based DHCPv6 protocol as an example, for a DHCPv6 solicitation message and a DHCPv6 request message, the destination IP address is a multicast address, and the first mapping rule may be that a packet whose destination IP address is a multicast address is mapped to a specified first RLC channel for transmission; or, the data packet whose destination IP address is a multicast address, whose transport layer protocol type is a user datagram protocol, whose source port number is 546 and whose destination port number is 547 is mapped to the specified first RLC channel for transmission.

For example, taking the IPv 6-based stateless address configuration as an example, for a router solicitation RS message, the destination IP address may be a multicast address or a local link address of a router, and the first mapping rule may be: and mapping the data packet with the destination IP address being the multicast address or the local link address of the router to the appointed first RLC channel for transmission.

Optionally, in another possible implementation, the first indication information may include a first target value of a preset field of the first type packet. Further, the first indication information may further include a mapping relationship between the first target value and the identifier of the first RLC channel, or carry the mapping relationship between the first target value and the identifier of the first RLC channel in another message. The preset field may be a Differentiated Services Code Point (DSCP) and/or a flow label (flow label, included in an IP header of IPv 6).

After the first IAB node generates a first data packet (the first data packet may refer to a data packet to be sent by the first IAB node to a parent node of the first IAB node, and hereinafter referred to as a data packet to be sent for short), when a message type of a message included in the first data packet is one of type information of a first type message, or when one or more items in an IP five-tuple of the first data packet correspondingly satisfy a first value or a first value range of one or more items in the IP five-tuple of the first type data packet, the first IAB node may further set a value of a preset field in the first data packet to a first target value; or, when the value of the preset field in the first data packet is the first target value, the first IAB node may determine, according to the identifier of the first RLC channel, to carry the first data packet through the first RLC channel.

It should be noted that the first target value is not limited to the target value of one of the DSCP and the flow label, and the first target value may also include the target value of the DSCP and the target value of the flow label.

Optionally, the first data packet may further include an identifier of the first IAB node. Wherein the identity of the first IAB node may be carried in one or more of the following fields: the first type of packet includes a client hardware address (client hardware address) field when the payload part is a DHCP message, a DHCP Unique Identifier (DUID) field when the payload part is a DHCPv6 message, and a BAP address field of a BAP layer of the first type of packet.

In addition, the configuration content is not limited to be carried in one configuration message, and may be carried in a plurality of configuration messages respectively. For example, the first indication information, the first condition information, or the type information of the first type message may be carried in one or more configuration messages; the first indication information, the first target value, the mapping relationship between the first target value and the identity of the first RLC channel may be carried in one or more configuration messages.

Optionally, on the basis of fig. 5, as shown in fig. 6, the RLC channel determining method may further include:

s601, the IAB host node sends second indication information to the first IAB node.

Accordingly, the first IAB node receives the second indication information from the IAB host node. The second indication information is used for indicating that the target node of the first type of data packet in the wireless backhaul link is an IAB host node.

Optionally, the second indication information may include an identification of the IAB host node. For example, the identity of the IAB host node may be an identity of the IAB host node in a Backhaul Adaptation Protocol (BAP) layer, an identity of a gNB-DU of the IAB host node, an identity of a cell served by the IAB host node (new air interface cell identity (NCI), new air interface cell global identity (NCGI)), or the like.

Optionally, the second indication information may further include second condition information or type information of the first type message, where the second condition information is a second value or a second value range of one or more items in the IP five-tuple of the first type packet. The type information of the first type message may include one or more of the following: DHCP messages, router solicitation RS messages, router advertisement RA messages, IP broadcast messages and IP multicast messages. The relevant description of the type information about the first type message is referred to the previous steps and will not be repeated here.

It should be noted that the second condition information may be the same as or different from the first condition information. For example, for the case that the first type message is a DHCP message, if both the first condition information in the first indication information and the second condition information in the second indication information are values for the same field, the first value of the first condition information and the second value of the second condition information may be the same. If the first condition information in the first indication information and the second condition information in the second indication information are both value ranges for the same field, a first value range of the first condition information and a second value range of the second condition information may be different, for example, one value range is larger than the other value range.

After the first IAB node generates the second data packet (the second data packet may refer to a data packet to be sent by the first IAB node to a parent node of the first IAB node, and hereinafter referred to as a data packet to be sent for short), when the message type of the message included in the second data packet is one of the type information of the first type message, or when one or more items in the IP five-tuple of the second data packet correspondingly satisfy a second value or a second value range of one or more items in the IP five-tuple of the first type data packet, the first type data packet may include the identifier of the IAB host node. The inclusion of the identifier of the IAB donor node in the first-type packet is effective to facilitate an intermediate IAB node (e.g., a second IAB node) to know that a target node of the first-type packet in the wireless backhaul link is the IAB donor node, so that the intermediate IAB node forwards the first-type packet to the IAB donor node.

Optionally, the second indication information may further include an identifier of a next hop node of the first type packet, where the identifier of the next hop node may be an identifier of a parent node (e.g., a second IAB node) of the first IAB node, for example, a BAP identifier of the parent node of the first IAB node, a cell identifier served by the parent node of the first IAB node, an IAB DU identifier of the parent node of the first IAB node, a cell group (cell group) identifier of the parent node of the first IAB node for the first IAB node, and the like.

As shown in fig. 7, an embodiment of the present application provides an RLC channel determining method, where the method includes:

and S701, determining third indication information by the IAB host CU.

Specifically, this step may be performed by the IAB host CU of the IAB host node or the IAB host CU-CP of the IAB host node.

The third indication information is used to indicate a second RLC channel carrying the second type of data packets between the IAB host DU and the child IAB node of the IAB host DU. In the embodiment of the present application, the child IAB node of the IAB host DU may be the second IAB node. When the first IAB node is directly connected to the IAB home node (which may be understood as not passing through other intermediate IAB nodes), the child IAB node of the IAB home DU may be the first IAB node.

It can be understood that the second type packet refers to a certain type packet, and the third indication information may indicate the characteristics of the type packet, so that after the IAB host DU acquires the packet, it may be determined whether the acquired packet satisfies the characteristics of the second type packet, and if so, the acquired packet is carried through the second RLC channel.

The second type of packet may include a second type of message indicating an IP address assigned to the first IAB node. The first IAB node is a child node of the IAB host DU or the first IAB node is connected to the IAB host DU through one or more intermediate IAB nodes. For example, the second type packet may be an IP packet, the second type message is a payload part of the IP packet, may be a self-defined IP address indication message, or may be a DHCP pre-allocation message in the DHCP protocol or a DHCP acknowledgement message, or a DHCPv6 notification message in the DHCPv6 protocol or a DHCPv6 reply message. Alternatively, the second type packet may be a BAP packet, and the second type message may be a payload portion of the BAP packet, and may be an IP broadcast message or an IP multicast message, and the IP broadcast message or the IP multicast message may be used to indicate an IP address. It should be noted that the IP broadcast message or the IP multicast message may also be used for other purposes, and the application is not limited in this application.

The second RLC channel may be dedicated to carrying the second type of data packets, and may also be used to carry other types of data packets, which is not limited in this application.

The third indication information includes an identification of the second RLC channel for uniquely identifying the second RLC channel. Optionally, the third indication information may further include a second mapping rule in addition to the identifier of the second RLC channel. And when the data packet to be sent meets the second mapping rule, mapping the data packet to be sent to the second RLC channel. For example, if the second RLC channel is not dedicated to transmitting the second type of data packet, it can also be used to transmit other types of messages, and when the data packet to be transmitted satisfies the second mapping rule, the data packet to be transmitted is mapped to the second RLC channel. The second mapping rule will be described in detail in the following steps.

S702, the IAB host CU sends the third indication information to the IAB host DU.

Accordingly, the IAB host DU receives the third indication information from the IAB host CU.

The third indication information may be carried in an F1 application protocol (F1 application protocol, F1AP) message.

And S703, determining the second RLC channel by the IAB host DU according to the third indication information.

The IAB host DU may determine the second RLC channel based on the identity of the second RLC channel when the second RLC channel is dedicated to transmitting the second type of packet.

Optionally, the third indication information may further include the following second mapping rule:

optionally, in a possible implementation, the third indication information may further include third condition information or type information of the second type message. The type information of the second type message may include one or more of the following: DHCP messages, RS messages, RA messages, IP broadcast messages, and IP multicast messages. The third condition information may include a third value or a third value range of one or more items in an IP five-tuple of the second type packet, where the IP five-tuple includes a source IP address, a destination IP address, a source port number, a destination port number, and a transport layer protocol type.

After the IAB host DU generates a second data packet (the second data packet may refer to a data packet to be sent by the IAB host DU to a child node of the IAB host DU, and hereinafter referred to as a data packet to be sent for short), when the message type of the message included in the second data packet is one of type information of a second type message, the IAB host DU may determine to carry the second data packet through the second RLC information according to the identifier of the second RLC channel; or, when one or more items in the second data packet correspondingly satisfy a third value or a third value range of one or more items in the IP quintuple of the second type data packet, the IAB host DU may determine to carry the second data packet through the second RLC information according to the identifier of the second RLC channel.

For example, taking the DHCP protocol based on IPv4 as an example, for the DHCP acknowledge message and the DHCP pre-allocation message, the destination IP address is an IP broadcast address (the IPv4 address 255.255.255.255 with each bit being 1), and the second mapping rule may be: mapping the data packet with the destination IP address as the broadcast address to a specified second RLC channel for transmission; or, mapping the data packet whose destination IP address is an IP broadcast address, whose transport layer protocol type is User Datagram Protocol (UDP), whose source port number is 67, and whose destination port number is 68, onto a specified second RLC channel for transmission.

For example, taking the DHCPv6 protocol based on IPv6 as an example, for the DHCPv6 notification message and the DHCPv6 reply message, the destination IP address is the client local link address, and the second mapping rule may be: mapping the data packet with the destination IP address as the multicast address to a specified second RLC channel for transmission; or, the data packet whose destination IP address is the client local link address, whose transport layer protocol type is the user datagram protocol, whose source port number is 547 and whose destination port number is 546 is mapped to the designated second RLC channel for transmission.

For example, taking the IPv 6-based stateless address configuration as an example, for the router advertisement RA message, the destination IP address may be a local link address or an IP multicast address of the device requesting the IP address, and the second mapping rule may be: and mapping the data packet with the destination IP address being the multicast address or the local link address of the equipment to a specified second RLC channel for transmission.

Optionally, in another possible implementation, the third indication information may further include a second target value of a preset field of the second type packet. The third indication information may further include a mapping relationship between the second target value and an identifier of the second RLC channel, or the mapping relationship between the second target value and the identifier of the second RLC channel is carried in another message. The preset field may be a Differentiated Services Code Point (DSCP) and/or a flow label (flow label, included in an IP header of IPv 6).

After the IAB host DU generates a second data packet (the second data packet may refer to a data packet to be sent by the IAB host DU to a child node of the IAB host DU, and hereinafter referred to as a data packet to be sent for short), when the message type of the message included in the second data packet is one of type information of a second type message, or when one or more items in the IP five-tuple of the second data packet correspondingly satisfy a third value or a third value range of one or more items in the IP five-tuple of the second type data packet, the IAB host DU may further set the value of the preset field in the second data packet as a second target value; or, when the value of the preset field in the second data packet is the second target value, the IAB host DU may determine to carry the second data packet through the second RLC channel according to the identifier of the second RLC channel.

It should be noted that the second target value is not limited to the target value of one of the DSCP and the flow label, and the second target value may also include the target value of the DSCP and the target value of the flow label.

In addition, the configuration content is not limited to be carried in one configuration message, and may be carried in a plurality of configuration messages respectively. For example, the third indication information, the third condition information, or the type information of the second type message may be carried in one or more configuration messages; the third indication information, the second target value, the mapping relationship between the second target value and the identity of the second RLC channel may be carried in one or more configuration messages.

Optionally, on the basis of fig. 7, as shown in fig. 8, the RLC channel determining method may further include:

s801, the IAB host CU sends the fourth indication information to the IAB host DU.

Accordingly, the IAB host DU receives the fourth indication information from the IAB host CU. The fourth indication information is used to indicate that the target node of the second type of data packet on the wireless backhaul link is the first IAB node.

Optionally, the fourth indication information may include an identity of the first IAB node. For example, the identity of the first IAB node may be the identity of the first IAB node at the BAP layer.

Optionally, the fourth indication information may include an identity of a next-hop node on a wireless backhaul link from the IAB host DU to the first IAB node.

Optionally, the fourth indication information may include other identifiers for identifying the first IAB node, and for example, the identifiers may include: an identifier allocated by the parent node of the first IAB node to the first IAB node (e.g., a cell radio network temporary identifier (C-RNTI) of the first IAB node in the parent node cell) and an identifier of the parent node of the first IAB node (e.g., a BAP identifier of the parent node of the first IAB node, an IAB DU identifier of the parent node of the first IAB node, a cell identifier served by the parent node of the first IAB node for the first IAB node, etc.). Through the above manner, the IAB host DU can acquire the identifier of the first IAB node, and the identifier of the first IAB node is added to the data packet sent to the first IAB node, so that other intermediate IAB nodes can forward the data packet to the first IAB node.

Optionally, on the basis of fig. 5 to fig. 8, as shown in fig. 9, the RLC channel determining method may further include:

s901, the first IAB node sends a first type data packet to the IAB host node through a first RLC channel.

Accordingly, the IAB donor node receives the first type of packet from the child node of the IAB donor node. It should be noted that the first IAB node may be directly connected to the IAB host node, i.e. a child node of the IAB host node; alternatively, the connection to the IAB host node (IAB host DU) may be via one or more intermediate IAB nodes, and the child nodes of the IAB host node may forward the first type packet sent by the first IAB node.

Specifically, when the IAB host node is in a CU-DU separation form, the first IAB node sends the first type packet to the IAB host DU of the IAB host node through the first RLC channel, and accordingly, the IAB host DU of the IAB host node receives the first type packet from the child IAB node of the IAB host DU.

It should be noted that, if the first IAB node is a child node of the IAB host node, the first IAB node directly sends the first type data packet to the IAB host node through the first RLC channel, and correspondingly, the IAB host node receives the first type data packet through the second RLC channel. If there is at least one intermediate IAB node between the first IAB node and the IAB host node, the first IAB node sends a first type data packet to the IAB host node through a first RLC channel, and the first type data packet needs to be sent to a child node of the IAB host node through the first RLC channel and then forwarded to the IAB host node by the child node of the IAB host node.

S902, the IAB host node acquires the IP address distributed for the first IAB node.

Specifically, when the IAB host node is in a CU-DU separated form, the IAB host DU of the IAB host node acquires an IP address allocated to the IAB node connected to the IAB host DU.

The IAB host node assigns an IP address to the first IAB node if the IAB host node can act as a DHCP server or DHCP proxy. And if the IAB host node is used as a DHCP relay, the IAB host node acquires the IP address allocated to the first IAB node from a DHCP server.

Optionally, the IAB host node determines a mapping relationship between the IP address and an identity of the IAB node connected to the IAB host DU. Specifically, the IAB host DU determines the mapping relationship between the IP address and the identity of the IAB node connected to the IAB host DU. The IAB host node (or the IAB host DU) may determine that the packet should be transmitted to the IAB node connected to the IAB host DU when the IAB host node subsequently receives a packet whose destination IP address is the IP address of the IAB node connected to the IAB host DU.

And S903, the IAB host node sends the second type data packet to the first IAB node through a second RLC channel.

Specifically, when the IAB donor node is in a CU-DU separation form, the IAB donor DU of the IAB donor node sends the second type packet to the first IAB node through the second RLC channel.

Accordingly, the first IAB node receives the second type of packet from the IAB host node. Wherein the second type of packet includes a second type of message indicating an IP address assigned to the first IAB node.

It should be noted that, if the first IAB node is a child node of the IAB host node, the IAB host node directly sends the second type data packet to the IAB node through the second RLC channel, and correspondingly, the IAB node receives the second type data packet through the second RLC channel. If there is at least one intermediate IAB node between the first IAB node and the IAB host node, the IAB host node sends the second type data packet to the first IAB node through the second RLC channel, and the second type data packet needs to be sent to the child node of the IAB host node through the second RLC channel and then forwarded to the first IAB node by the child node of the IAB host node.

As shown in fig. 10, the following takes as an example that after the first IAB node determines the first RLC channel and the IAB host DU determines the second RLC channel, the first IAB node and the IAB host DU acquire an IP address through an IP address allocation procedure in the DHCP protocol, and further describes the above embodiment:

s1001, the first IAB node sends an uplink data packet including a DHCP discover message to the IAB host DU through the first RLC channel.

In the header of the BAP layer of the uplink data packet, the identity of the IAB host DU may be added as a target node for wireless backhaul link uplink transmission.

Based on the above-described configuration of the first IAB node, the first IAB node may select an appropriate first RLC channel for the DHCP discovery message, and then send an uplink packet including the DHCP discovery message to the parent node through the first RLC channel. The father node of the first IAB node may be the IAB host DU, or the father node of the first IAB node is another IAB node, and the father node of the first IAB node will continue to forward the uplink data packet containing the DHCP discover message to the IAB host DU.

Optionally, in a possible embodiment, in order to make the IAB host DU know which IAB node requesting the IP address is, the first IAB node may carry an identity of the first IAB node in an uplink data packet (for example, in a DHCP discovery message or in a header of a BAP layer of the uplink data packet), where the identity of the first IAB node may be, for example, a BAP layer identity of the first IAB node, or may also be a C-RNTI of the first IAB node and an identity of a parent node (such as the second IAB node in fig. 2) of the first IAB node (for example, a cell identity of the second IAB node, a DU identity of the second IAB node, a BAP layer identity of the second IAB node, and the like).

In another possible embodiment, the first IAB node may carry both the BAP layer identity of the first IAB node in the BAP layer header of the upstream packet and the remaining type identity of the first IAB node in the DHCP discover message. Further optionally, if the DHCP discovery message includes the identifier of the first IAB node, the identifier of the first IAB node may be carried in a "client hardware address" field, and for a case that the length of the field is greater than the identifier of the first IAB node (for example, the identifier of the first IAB node is a BAP layer identifier), some bits in the field may be specified as the identifier of the first IAB node, and the remaining bits are padding bits and may be padded to all 0 s. Alternatively, the identifier of the first IAB node may be a virtual hardware identifier of the first IAB node, where the virtual hardware identifier may be preconfigured in the first IAB node (for example, preconfigured in the first IAB node at factory time), or preconfigured to the first IAB node by the IAB host CU/IAB host CU-CP through an RRC message, or configured after the first IAB node obtains from an operation, administration, and main (OAM) server of the first IAB node, and the virtual hardware identifier may be the same as a Media Access Control (MAC) address length in other types of wireless networks or wired networks (e.g., IEEE 802 series networks: ethernet, wireless local area network, wireless personal area network, etc.), for example, the virtual hardware identifier may be the same as a "client hardware address" field length in a DHCP message.

For how the first IAB node triggers sending the DHCP discover message, there may be several possible scenarios: the configuration may be performed after the BAP layer of the MT part of the first IAB node is configured, or after the RLC channel between the first IAB node and the parent node is configured, or determined by a specific implementation of the first IAB node, which is not limited in this application.

It should be noted that if there are intermediate IAB nodes (e.g., second IAB nodes) between the first IAB node and the IAB host DU, these intermediate IAB nodes may perform routing on the data packets (including the uplink data packet and the downlink data packet) including the DHCP message according to the information in the BAP layer header to determine the next-hop node. The intermediate IAB node can determine the RLC channel for forwarding the data packet according to the RLC channel for receiving the data packet and the configured mapping rule without sensing that DHCP information is carried in the forwarded data packet.

S1002, the IAB host DU acquires the IP address distributed for the first IAB node.

After the IAB host DU receives the DHCP discover message sent by the first IAB node, if the IAB host DU can act as a DHCP server or a DHCP proxy, it processes the DHCP discover message of the first IAB node by itself and allocates an IP address to the first IAB node. If the IAB host DU serves as a DHCP relay, the IAB host DU may forward the DHCP discover message to the DHCP server, and acquire the IP address allocated to the first IAB node from the DHCP server. When forwarding the DHCP discover message to the DHCP server, the IAB host DU may serve as a general router, a DHCP relay, or a DHCP proxy, which is not limited in this application.

S1003, the IAB host DU sends a downlink data packet containing the DHCP pre-allocation message to the first IAB node through the second RLC channel.

The DHCP pre-allocation message includes an IP address that the DHCP server is ready to allocate to the first IAB node. The DHCP pre-allocation message may be generated by the DHCP server and then forwarded to the first IAB node by the IAB host DU, or may be generated when the IAB host DU is used as a DHCP server or a DHCP proxy.

If the IAB host DU is used as a DHCP relay, a DHCP proxy, or a DHCP server, the IAB host DU may check the identity of the first IAB node included in the DHCP pre-allocation message (e.g., the identity of the first IAB node included in the "client hardware address" field), then select the next hop node, add the BAP layer identity of the first IAB node in the BAP layer header, and send the downlink data packet including the DHCP pre-allocation message to the RLC entity corresponding to the RLC channel for sending the downlink DHCP message. The downlink data packet is processed by an RLC layer, an MAC layer, and a Physical (PHY) layer, and then transmitted to the first IAB node. The IAB host DU may send the downlink data packet to the first IAB node directly through the second RLC channel, or send the downlink data packet to a next hop node (e.g., the second IAB node) through the second RLC channel, and then forward the downlink data packet to the first IAB node by the second IAB node.

Optionally, the IAB host DU may record a correspondence between an identity (e.g., a BAP layer identity) of the first IAB node and an IP address allocated to the first IAB node in the DHCP pre-allocation message. Thus, when the IAB host DU subsequently receives a data packet whose destination IP address is the IP address of the first IAB node, it may determine that the data packet should be sent to the first IAB node, and after adding the identifier of the first IAB node to the data packet (for example, adding the BAP layer identifier of the first IAB node to the BAP layer header of the data packet), the IAB host DU may send the data packet to the next hop node on the path between the IAB host DU and the first IAB node.

S1004, the first IAB node sends an uplink data packet including a DHCP request message to the IAB host DU through the first RLC channel.

The first IAB node may add the identity of the IAB host DU to the header of the BAP layer of the uplink packet as a target node for wireless backhaul link uplink transmission.

Similar to step S1001, the uplink data packet may further include an identifier of the first IAB node.

It should be noted that the first RLC channel in step S1004 may be the same as or different from the first RLC channel in step S1001.

S1005, the IAB host DU sends a data packet containing a DHCP acknowledge message to the first IAB node through the second RLC channel.

The DHCP acknowledgement message includes an IP address acknowledging the assignment to the first IAB node.

After the IAB host DU receives the DHCP request message sent by the first IAB node, if the IAB host DU can act as a DHCP server or a DHCP proxy, it processes the DHCP request message of the first IAB node by itself. The IAB host DU may forward the DHCP request message to the DHCP server if the IAB host DU is acting as a DHCP relay. When forwarding the DHCP request message to the DHCP server, the IAB host DU may serve as a general router, a DHCP relay, or a DHCP proxy, which is not limited in this application.

The DHCP acknowledge message may be generated by the DHCP server and then forwarded to the first IAB node by the IAB host DU, or may be generated when the IAB host DU is used as a DHCP server or a DHCP proxy.

If the IAB host DU is used as a DHCP relay, a DHCP proxy, or a DHCP server, the IAB host DU may check the identity of the first IAB node included in the DHCP acknowledge message (e.g., the identity of the first IAB node included in the "client hardware address" field), then select the next hop node, add the BAP layer identity of the first IAB node in the BAP layer header, and send the downlink data packet including the DHCP acknowledge message to the RLC entity corresponding to the RLC channel for sending the downlink DHCP message. The downlink data packet is processed by an RLC layer, an MAC layer and a PHY layer and then is sent to the first IAB node. The IAB host DU may send the downlink data packet to the first IAB node directly through the second RLC channel, or send the downlink data packet to a next hop node (e.g., the second IAB node) through the second RLC channel, and then forward the downlink data packet to the first IAB node by the second IAB node.

Optionally, the IAB host DU may record a correspondence between an identity (e.g., a BAP layer identity) of the first IAB node and an IP address allocated to the first IAB node in the DHCP acknowledge message. Thus, when the IAB host DU subsequently receives a data packet whose destination IP address is the IP address of the first IAB node, it may determine that the data packet should be sent to the first IAB node, and after adding the identifier of the first IAB node to the data packet (for example, adding the BAP layer identifier of the first IAB node to the BAP layer header of the data packet), the IAB host DU may send the data packet to the next hop node on the path between the IAB host DU and the first IAB node.

Through the above steps, the first IAB node may obtain an IP address allocated by the DHCP server, may configure the obtained IP address to the DU portion of the first IAB node, and then may perform data transmission using the IP address, for example, TNL (transport network layer) coupling or Stream Control Transport Protocol (SCTP) coupling between IAB host CUs (or IAB host CU-CP), F1 connection establishment procedure between IAB host CUs (or IAB host CU-CP), F1 interface user plane data transmission between IAB host CUs (or IAB host CU-UP), F1 interface control plane data transmission between IAB host CUs (or IAB host CU-CP), connection and communication between OAM server, and the like.

It should be noted that the second RLC channel in step S1005 may be the same as or different from the second RLC channel in step S1003.

As shown in fig. 11, the following takes an example that after the first IAB node determines the first RLC channel and the IAB host DU determines the second RLC channel, the first IAB node and the IAB host DU acquire an IP address through an IP address allocation procedure in the DHCPv6 protocol, and further describes the above embodiment:

s1101, the first IAB node sends an uplink data packet including the DHCPv6 solicitation message to the IAB host DU through the first RLC channel.

Based on the above-described configuration of the first IAB node, the first IAB node may select an appropriate first RLC channel for the DHCPv6 solicitation message, and then transmit an uplink packet including the DHCPv6 solicitation message to the parent node through the first RLC channel. The father node of the first IAB node may be the IAB host DU, or the father node of the first IAB node is another IAB node, and the father node of the first IAB node will continue to forward the uplink data packet containing the DHCPv6 solicitation message to the IAB host DU.

Optionally, in a possible embodiment, in order to make the IAB host DU know which IAB node requesting the IP address is, the first IAB node may carry an identity of the first IAB node in an uplink data packet (e.g., in the DHCPv6 solicitation message or in a header of a BAP layer of the uplink data packet), where the identity of the first IAB node may be, for example, a BAP layer identity of the first IAB node, or may also be a C-RNTI of the first IAB node and an identity of a parent node (e.g., the second IAB node in fig. 2) of the first IAB node (e.g., a cell identity of the second IAB node, a DU identity of the second IAB node, a BAP layer identity of the second IAB node, and the like).

In another possible embodiment, the first IAB node may carry both the BAP layer identity of the first IAB node in the BAP layer header of the upstream packet and the remaining type identity of the first IAB node in the DHCPv6 solicitation message. Further optionally, if the identifier of the first IAB node is included in the DHCPv6 solicitation message, the identifier of the first IAB node may be carried in a "client DUID" field, and for a case that the field length is greater than the identifier of the first IAB node (for example, the identifier of the first IAB node is a BAP layer identifier), some bits in the field may be specified as the identifier of the first IAB node, and the remaining bits are padding bits and may be padded to all 0 s. Alternatively, the identifier of the first IAB node may be a virtual hardware identifier of the first IAB node, the virtual hardware identifier may be preconfigured in the first IAB node (for example, preconfigured in the first IAB node at factory time), or preconfigured to the first IAB node by the IAB host CU/IAB host CU-CP through an RRC message, or configured after the first IAB node obtains from an OAM server of the first IAB node, and the virtual hardware identifier may be the same as the MAC address length in other types of wireless networks or wired networks (e.g., IEEE 802 series networks: ethernet, wireless local area network, wireless personal area network, etc.), for example, the same as the length of the "client DUID" field in the DHCPv6 solicitation message.

There are several possible scenarios for how the first IAB node triggers sending the DHCPv6 solicitation message: the configuration may be performed after the BAP layer of the MT part of the first IAB node is configured, or after the RLC channel between the first IAB node and the parent node is configured, or determined by a specific implementation of the first IAB node, which is not limited in this application.

It should be noted that, if there are intermediate IAB nodes (e.g., second IAB nodes) between the first IAB node and the IAB host DU, these intermediate IAB nodes may determine the next-hop node by routing the data packets (including the uplink data packet and the downlink data packet) containing the DHCP message according to the information in the BAP layer header. The intermediate IAB node can determine the RLC channel for forwarding the data packet according to the RLC channel for receiving the data packet and the configured mapping rule without sensing that DHCP information is carried in the forwarded data packet.

Optionally, if the first IAB node carries the BAP layer identifier of the first IAB node in the BAP layer header of the uplink data packet, after receiving the data packet containing the DHCPv6 solicitation message sent by the first IAB node, the IAB host DU may record a corresponding relationship between the source IP address used by the first IAB node to send the DHCPv6 solicitation message and the BAP layer identifier of the first IAB node, that is, a corresponding relationship between the home link address of the first IAB node and the BAP layer identifier thereof. Thus, when the IAB host DU subsequently receives a data packet (e.g., a DHCPv6 notification message sent in a unicast manner or a DHCPv6 reply message sent in a unicast manner) whose destination IP address is the home link address of the first IAB node, it may determine that the data packet should be sent to the first IAB node, and after adding the identifier of the first IAB node to the data packet (e.g., adding the BAP layer identifier of the first IAB node to the BAP layer header of the data packet), the IAB host DU may send the data packet to the next hop node on the path between the IAB host DU and the first IAB node.

S1102, the IAB host DU acquires the IP address allocated to the first IAB node.

After receiving the DHCPv6 solicitation message sent by the first IAB node, if the IAB host DU can act as a DHCP server or a DHCP proxy, the IAB host DU processes the DHCPv6 solicitation message of the first IAB node by itself, and allocates an IP address or prefix (i.e., an IPv6 address prefix) to the first IAB node. If the IAB host DU is used as a DHCP relay, the IAB host DU may forward the DHCPv6 solicitation message to the DHCP server, and acquire the IP address allocated for the first IAB node from the DHCP server. When forwarding the DHCPv6 solicitation message to the DHCP server, the IAB host DU may be used as a general router, DHCP relay, or DHCP proxy, which is not limited in this application.

S1103, the IAB host DU sends a downlink packet including the DHCPv6 notification message to the first IAB node through the second RLC channel.

The DHCPv6 notify message includes the IP address or prefix (i.e., IPv6 address prefix) that the DHCP server is ready to assign to the first IAB node. The DHCPv6 notification message may be generated by the DHCP server and then forwarded to the first IAB node by the IAB host DU, or may be generated when the IAB host DU is used as a DHCP server or a DHCP proxy.

If the IAB host DU receives the notification message containing the DHCPv6 in a unicast manner, where the destination IP address contained in the notification message is the home link address of the first IAB node, the IAB host DU may determine the identifier of the first IAB node (specifically, the BAP layer identifier) according to the correspondence between the home link address of the first IAB node and the BAP layer identifier recorded before; alternatively, if the IAB host DU is acting as a DHCP relay, DHCP proxy, or DHCP server, the IAB host DU may look at the identity of the first IAB node contained in the DHCPv6 notification message (e.g., the identity of the first IAB node contained in the "client DUID" field). The IAB host DU selects a next hop node according to the identification of the first IAB node, and sends a downlink data packet containing a DHCPv6 notification message to an RLC entity after the BAP layer identification of the first IAB node is added to the BAP layer header, wherein the RLC entity is an RLC layer entity corresponding to an RLC channel for sending a downlink DHCP message. The downlink data packet is processed by an RLC layer, an MAC layer, and a Physical (PHY) layer, and then transmitted to the first IAB node. The IAB host DU may send the downlink data packet to the first IAB node directly through the second RLC channel, or send the downlink data packet to a next hop node (e.g., the second IAB node) through the second RLC channel, and then forward the downlink data packet to the first IAB node by the second IAB node.

Optionally, the IAB host DU may record a correspondence between an identity (e.g., BAP layer identity) of the first IAB node and an IP address allocated to the first IAB node in the DHCPv6 notification message. Thus, when the IAB host DU subsequently receives a data packet whose destination IP address is the IP address of the first IAB node, it may determine that the data packet should be sent to the first IAB node, and after adding the identifier of the first IAB node to the data packet (for example, adding the BAP layer identifier of the first IAB node to the BAP layer header of the data packet), the IAB host DU may send the data packet to the next hop node on the path between the IAB host DU and the first IAB node.

S1104, the first IAB node sends an uplink data packet including the DHCPv6 request message to the IAB host DU through the first RLC channel.

Similar to step S1101, the uplink data packet may further include an identifier of the first IAB node.

It should be noted that the first RLC channel in step S1104 may be the same as or different from the first RLC channel in step S1101.

S1105, the IAB host DU sends a downlink packet including the DHCPv6 reply message to the first IAB node through the second RLC channel.

The DHCPv6 reply message includes an IP address or prefix (i.e., IPv6 address prefix) confirming assignment to the first IAB node.

After receiving the DHCPv6 request message sent by the first IAB node, the IAB home DU processes the DHCPv6 request message of the first IAB node by itself if the IAB home DU can act as a DHCP server or a DHCP proxy. If the IAB home DU acts as a DHCP relay, the IAB home DU may forward the DHCPv6 request message to the DHCP server. When forwarding the DHCPv6 request message to the DHCP server, the IAB host DU may be used as a general router, a DHCP relay, or a DHCP proxy, which is not limited in this application.

The DHCPv6 reply message may be generated by the DHCP server and then forwarded to the first IAB node by the IAB host DU, or may be generated when the IAB host DU is used as a DHCP server or a DHCP proxy.

If the IAB host DU receives the reply message containing the DHCPv6 in a unicast form, where the destination IP address contained in the reply message is the home link address of the first IAB node, the IAB host DU may determine the identity of the first IAB node (specifically, the BAP layer identity) according to the correspondence between the home link address of the first IAB node and the BAP layer identity recorded before; alternatively, if the IAB host DU is acting as a DHCP relay, DHCP proxy, or DHCP server, the IAB host DU may look at the identity of the first IAB node contained in the DHCPv6 reply message (e.g., the identity of the first IAB node contained in the "client DUID" field). And then selecting a next hop node, and after adding the BAP layer identification of the first IAB node to the BAP layer header, sending a downlink data packet containing the DHCPv6 reply message to an RLC entity, wherein the RLC entity is an RLC layer entity corresponding to an RLC channel for sending a downlink DHCP message. The downlink data packet is processed by an RLC layer, an MAC layer and a PHY layer and then is sent to the first IAB node. The IAB host DU may send the downlink data packet to the first IAB node directly through the second RLC channel, or send the downlink data packet to a next hop node (e.g., the second IAB node) through the second RLC channel, and then forward the downlink data packet to the first IAB node by the second IAB node.

Optionally, the IAB host DU may record a correspondence between an identity (e.g., BAP layer identity) of the first IAB node and an IP address allocated to the first IAB node in the DHCPv6 reply message. Thus, when the IAB host DU subsequently receives a data packet whose destination IP address is the IP address of the first IAB node, it may determine that the data packet should be sent to the first IAB node, and after adding the identifier of the first IAB node to the data packet (for example, adding the BAP layer identifier of the first IAB node to the BAP layer header of the data packet), the IAB host DU may send the data packet to the next hop node on the path between the IAB host DU and the first IAB node.

Optionally, if the reply message of the DHCPv6 carries an IPv6 address prefix, the IAB node generates an IPv6 address together with its own interface address as a suffix.

After the above steps, the first IAB node obtains an IP address, may configure the obtained IP address to the DU portion of the first IAB node, and may then perform data transmission using the IP address, for example, TNL coupling (association) or Stream Control Transmission Protocol (SCTP) coupling between IAB host CUs (or IAB host CU-CP), F1 connection establishment procedure between the IAB host CUs (or IAB host CU-CP), F1 interface user plane data transmission between the IAB host CUs (or IAB host CU-UP), F1 interface control plane data transmission between the IAB host CU (or IAB host CU-CP), connection and communication between an OAM server, and the like.

Optionally, after the first IAB node obtains the IP address configured to its DU part, the IP address may be reported to the IAB host CU (or CU-CP), and then the IAB host CU (or CU-CP) may establish an F1 connection with the IAB node by using the IP address, and the IAB host CU (or CU-CP) may further configure a corresponding relationship between the IP address and the BAP layer id of the first IAB node to the IAB host DU, so that when a subsequent IAB host DU receives a packet whose destination IP address is the IP address of the first IAB node (specifically, the DU part of the first IAB node), the BAP layer id of the first IAB node is added to the packet, so that the packet is forwarded to the first IAB node by a correct route over the wireless backhaul link.

It should be noted that the second RLC channel in step S1105 may be the same as or different from the second RLC channel in step S1103.

As shown in fig. 12, the following takes an example that after the first IAB node determines the first RLC channel and the IAB host DU determines the second RLC channel, the first IAB node and the IAB host DU acquire an IP address in a stateless address configuration manner based on IPv6, and further describes the above embodiment:

s1201, the first IAB node sends an uplink data packet including a router solicitation message to the IAB host DU through the first RLC channel.

In the header of the BAP layer of the uplink data packet, the identity of the IAB host DU may be added as a target node for wireless backhaul link transmission.

Based on the above-described configuration of the first IAB node, the first IAB node may select an appropriate first RLC channel for the router solicitation message, and then transmit an uplink packet including the router solicitation message to the parent node through the first RLC channel. The parent node of the first IAB node may be the IAB home DU, or the parent node of the first IAB node is another IAB node, and the parent node of the first IAB node will continue to forward the packet containing the router solicitation message to the IAB home DU.

Optionally, in a possible embodiment, in order to make the IAB host DU know which IAB node requesting the IP address is, the first IAB node may carry an identity of the first IAB node in an uplink packet (e.g., in a BAP layer header of the packet, or in an IP layer header, or in a router solicitation message), where the identity of the first IAB node may be, for example, a BAP layer identity of the first IAB node, or may also be a C-RNTI of the first IAB node and an identity of a parent node (e.g., the second IAB node in fig. 2) of the first IAB node (e.g., a cell identity of the second IAB node, a DU identity of the second IAB node, a BAP layer identity of the second IAB node, etc.).

In another possible embodiment, the first IAB node may carry both the BAP layer identity of the first IAB node in the BAP layer header of the upstream packet and the remaining type identity of the first IAB node in the router solicitation message or IP header (e.g., the source IP address in the IP header assumes the home link address of the first IAB node). Further optionally, when a field in the router solicitation message or in the IP header carries the identifier of the first IAB node, for a case that the length of the field is greater than the identifier of the first IAB node (for example, the identifier of the first IAB node is a BAP layer identifier), some bits in the field may be specified as the identifier of the first IAB node, and the remaining bits are padding bits and may be padded to all 0 s. Alternatively, the identifier of the first IAB node may be a virtual hardware identifier of the first IAB node, where the virtual hardware identifier may be preconfigured in the first IAB node (for example, preconfigured in the first IAB node at factory), or preconfigured to the first IAB node by the IAB host CU/IAB host CU-CP through an RRC message, or configured after the first IAB node obtains from an OAM server of the first IAB node, and the virtual hardware identifier may be the same as the MAC address length in other types of wireless networks or wired networks (e.g., IEEE 802 series networks: ethernet, wireless local area network, wireless personal area network, etc.).

There are several possible scenarios for how the first IAB node triggers sending the router solicitation message: the configuration may be performed after the BAP layer of the MT part of the first IAB node is configured, or after the RLC channel between the first IAB node and the parent node is configured, or determined by a specific implementation of the first IAB node, which is not limited in this application.

It should be noted that if there are intermediate IAB nodes (e.g., second IAB nodes) between the first IAB node and the IAB host DU, these intermediate IAB nodes may determine the next hop node by routing the data packet (including the uplink data packet and the downlink data packet) including the router solicitation message according to the information in the BAP layer header. The intermediate IAB node may determine the RLC channel to forward the data packet according to the RLC channel to receive the data packet and the configured mapping rule, without sensing that the forwarded data packet carries the router solicitation message.

Optionally, if the first IAB node carries the BAP layer identifier of the first IAB node in the BAP layer header of the uplink data packet, after receiving the data packet containing the router solicitation message sent by the first IAB node, the IAB host DU may record a correspondence between a source IP address used by the first IAB node to send the router solicitation message and the BAP layer identifier of the first IAB node, that is, a correspondence between a local link address of the first IAB node and the BAP layer identifier thereof. In this way, the IAB host DU may determine that a packet should be sent to the first IAB node when subsequently sending a packet (e.g., a router advertisement message sent in unicast) whose destination IP address is the home link address of the first IAB node. The IAB host DU may add the identity of the first IAB node to the packet (e.g., add the BAP layer identity of the first IAB node to the BAP layer header of the packet), and then send the packet to the next hop node on the path between the IAB host DU and the first IAB node.

S1202, the IAB host DU sends a downlink data packet including a router advertisement message to the first IAB node through the second RLC channel.

The router advertisement message carries the IPv6 address prefix.

After receiving the router solicitation message sent by the first IAB node, the IAB home DU generates a router advertisement message and sends the router advertisement message to the first IAB node if the IAB home DU can be used as a router for sending the router advertisement message. Or, the IAB host DU may forward the router advertisement message to the router in an IP unicast or IP multicast format, and other routers in the network generate the router advertisement message, and forward the router advertisement message to the first IAB node through the IAB host DU, which is not limited in this application.

If the IP packet containing the router advertisement message generated or received by the IAB host DU is a unicast packet, where the destination IP address contained in the unicast packet is the local link address of the first IAB node, the IAB host DU may determine the identifier of the first IAB node (specifically, the BAP layer identifier) according to the correspondence between the local link address of the first IAB node and the BAP layer identifier recorded before, then select the next hop node, and send the downlink packet containing the router advertisement message to the RLC entity after adding the BAP layer identifier of the first IAB node to the BAP layer header, where the RLC entity is an RLC layer entity corresponding to the RLC channel used for sending the router advertisement message. The downlink data packet is processed by an RLC layer, an MAC layer and a PHY layer and then is sent to the first IAB node. The IAB host DU may send the downlink data packet to the first IAB node directly through the second RLC channel, or send the downlink data packet to a next hop node (e.g., the second IAB node) through the second RLC channel, and then forward the downlink data packet to the first IAB node by the second IAB node.

The router announcement message carries an IPv6 address prefix, and then the IAB node generates an IPv6 address together by taking an interface address (interface ID) of the IAB node as a suffix.

Optionally, after the first IAB node obtains the IP address of the DU part configured to the first IAB node, the IP address may be reported to the IAB host CU (or CU-CP), and then the IAB host CU (or CU-CP) may establish an F1 connection with the IAB node by using the IP address, and the IAB host CU (or CU-CP) may further configure a corresponding relationship between the IP address and the BAP layer id of the first IAB node to the IAB host DU, so that when a packet whose destination IP address is the IP address of the first IAB node (which may be specifically the DU part of the first IAB node) is received by a subsequent IAB host, the BAP layer id of the first IAB node is added to the packet, so that the packet is forwarded to the first IAB node by a correct route over the wireless backhaul link.

It should be noted that the second RLC channel in step S1202 may be the same as or different from the first RLC channel in step S1201.

It is to be understood that, in the above embodiments, the methods and/or steps implemented by the IAB node may also be implemented by a component (e.g., a chip or a circuit) available to the IAB node, and the methods and/or steps implemented by the IAB hosting node may also be implemented by a component available to the IAB hosting node.

The above-mentioned scheme provided by the embodiment of the present application is introduced mainly from the perspective of interaction between network elements. Correspondingly, the embodiment of the application also provides a communication device, and the communication device is used for realizing the various methods. The communication device may be an IAB node in the above method embodiment, or a device including the above IAB node, or a chip or a functional module in the IAB node; alternatively, the communication device may be an IAB hosting node in the foregoing method embodiment, or a device including the foregoing IAB hosting node, or a chip or a functional module in the IAB hosting node; alternatively, the communication device may be the IAB host DU in the above method embodiment, or a device including the above IAB host DU, or a chip or a functional module in the IAB host DU; alternatively, the communication device may be the IAB hosting CU in the above method embodiment, or a device including the above IAB hosting CU, or a chip or a functional module within the IAB hosting CU. It is to be understood that the communication device comprises corresponding hardware structures and/or software modules for performing the respective functions in order to realize the above-mentioned functions. Those of skill in the art would readily appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as hardware or combinations of hardware and computer software. Whether a function is performed as hardware or computer software drives hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

In the embodiment of the present application, the communication apparatus may be divided into functional modules according to the method embodiments, for example, each functional module may be divided according to each function, or two or more functions may be integrated into one processing module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode. It should be noted that, in the embodiment of the present application, the division of the module is schematic, and is only one logic function division, and there may be another division manner in actual implementation.

For example, the communication device is taken as the first IAB node in the above method embodiment. Fig. 13 shows a schematic structural diagram of a communication device 130. The communication device 130 includes a processing module 1301 and a transceiver module 1302. The transceiver module 1302, which may also be referred to as a transceiver unit, includes a transmitting unit and/or a receiving unit, which may be, for example, a transceiver circuit, a transceiver, or a communication interface, to implement the transmitting and/or receiving functions of the first IAB node in the above method embodiments. For example, step S502 in fig. 5, steps S502 and S601 in fig. 6, steps S901 and S903 in fig. 9, steps S1001, S1003, S1004 and S1005 in fig. 10, steps S1101, S1103, S1104 and S1105 in fig. 11, and steps S1201 and S1202 in fig. 12 are performed. The processing module 1301 is configured to perform data processing, so as to implement the function of the first IAB node in the foregoing method embodiment to perform processing, for example, to execute step S503 in fig. 5 and step S503 in fig. 6.

Illustratively, the transceiver module 1302 is configured to receive first indication information from the IAB donor node, where the first indication information is used to indicate that a first radio link control, RLC, channel carrying a first type of data packet is located between the first IAB node and a parent node of the first IAB node, where the first type of data packet includes a first type message, and the first type message is used to request an internet protocol, IP, address; a processing module 1301, configured to determine the first RLC channel according to the first indication information.

In one possible embodiment, the first indication information includes an identification of the first RLC channel.

In a possible implementation, the processing module 1301 is further configured to generate a first data packet; when one or more items in the IP quintuple of the first data packet correspondingly meet the respective first values or first value ranges of one or more items in the IP quintuple of the first type data packet, determining that the first data packet is borne through a first RLC channel; or, when the message type of the first message included in the first data packet is one of the type information, determining to carry the first data packet through the first RLC channel.

In a possible implementation, the processing module 1301 is further configured to generate a first data packet; when one or more items in the IP quintuple of the first data packet correspondingly meet the respective first values or first value ranges of one or more items in the IP quintuple of the first type data packet, or when the type of the message included in the first data packet is one of type information, setting the preset field of the first data packet as a target value; and when the value of the preset field of the first data packet is the target value, determining that the first data packet is carried through the first RLC channel.

In one possible embodiment, the first data packet further includes an identification of the first IAB node.

In a possible implementation, the transceiver module 1302 is further configured to receive second indication information from the IAB donor node, where the second indication information indicates that the target node of the first type of packet on the wireless backhaul link is the IAB donor node.

In a possible implementation, the processing module 1301 is further configured to generate a second data packet; when one or more items in the IP quintuple of the second packet correspondingly satisfy a second value or a second value range of one or more items in the IP quintuple of the first type packet, or when the type of the message included in the second packet is one of the type information, the second packet includes the identifier of the IAB host node.

In a possible implementation, the transceiver module 1302 is further configured to receive a second type of packet, where the second type of packet includes a second type message, and the second type message is used to indicate an IP address assigned to the first IAB node.

In the present embodiment, the communication device 130 is presented in a form of dividing each functional module in an integrated manner. A "module" herein may refer to a particular ASIC, a circuit, a processor and memory that execute one or more software or firmware programs, an integrated logic circuit, and/or other device that provides the described functionality. In a simple embodiment, one skilled in the art may appreciate that the communication device 130 may take the form of the network device 30 shown in fig. 3.

For example, the processor 301 in the network device 30 shown in fig. 3 may execute the RLC channel determination method in the above method embodiment by calling a computer stored in the memory 302 to execute the instructions.

Specifically, the functions/implementation procedures of the processing module 1301 and the transceiver module 1302 in fig. 13 can be implemented by the processor 301 in the network device 30 shown in fig. 3 calling the computer execution instructions stored in the memory 302. Alternatively, the function/implementation procedure of the processing module 1301 in fig. 13 may be implemented by the processor 301 in the network device 30 shown in fig. 3 calling a computer executing instruction stored in the memory 302, and the function/implementation procedure of the transceiver module 1302 in fig. 13 may be implemented by the transceiver 303 in the network device 30 shown in fig. 3.

Since the communication apparatus 130 provided in this embodiment can execute the RLC channel determining method, the technical effect obtained by the communication apparatus 130 may refer to the method embodiment, and is not described herein again.

For example, the communication device is taken as the IAB host node in the above method embodiment. Fig. 14 shows a schematic structural diagram of a communication device 140. The communication device 140 comprises a processing module 1401 and a transceiver module 1402. The transceiver module 1402, which may also be referred to as a transceiver unit, includes a transmitting unit and/or a receiving unit, which may be, for example, a transceiver circuit, a transceiver, or a communication interface, to implement the transmitting and/or receiving functions of the IAB host node in the above method embodiments. For example, step S502 in fig. 5, steps S502, S601 in fig. 6, and steps S901, S903 in fig. 9 are performed. The processing module 1401 is configured to perform data processing, so as to implement the function of processing performed by the IAB host node in the foregoing method embodiment, for example, to execute step S501 in fig. 5, step S501 in fig. 6, and step S902 in fig. 9.

Illustratively, the processing module 1401 is configured to determine first indication information, where the first indication information is used to indicate a radio link control, RLC, channel carrying a first type of data packet between the first IAB node and a parent node of the first IAB node, where the first type of data packet includes a first type of message, and the first type of message is used for the first IAB node to request an internet protocol, IP, address; a transceiver module 1402 configured to send the first indication information to the first IAB node.

In a possible embodiment, the transceiver module 1402 is further configured to receive a first type packet from a first IAB node; a processing module 1401, further configured to obtain an IP address allocated to the first IAB node; the transceiver module 1402 is further configured to send a second type of packet to the first IAB node, where the second type of packet includes a second type message, and the second type message is used to indicate an IP address assigned to the first IAB node.

In one possible embodiment, the processing module 1401 is further configured to determine a mapping relationship between the IP address and the identity of the first IAB node.

In a possible embodiment, the transceiver module 1402 is further configured to send second indication information to the first IAB node, where the second indication information indicates that the target node of the first type of packet on the wireless backhaul link is an IAB donor node.

In the present embodiment, the communication device 140 is presented in a form of dividing each functional module in an integrated manner. A "module" herein may refer to a particular ASIC, a circuit, a processor and memory that execute one or more software or firmware programs, an integrated logic circuit, and/or other device that provides the described functionality. In a simple embodiment, those skilled in the art will appreciate that the communication device 140 may take the form of the network device 30 shown in fig. 3.

Specifically, the functions/implementation procedures of the processing module 1401 and the transceiver module 1402 in fig. 14 may be implemented by the processor 301 in the network device 30 shown in fig. 3 calling the computer execution instructions stored in the memory 302. Alternatively, the function/implementation procedure of the processing module 1401 in fig. 14 may be implemented by the processor 301 in the network device 30 shown in fig. 3 calling a computer executing instruction stored in the memory 302, and the function/implementation procedure of the transceiver module 1402 in fig. 14 may be implemented by the transceiver 303 in the network device 30 shown in fig. 3.

Since the communication device 140 of the present embodiment can execute the RLC channel determining method, the technical effect obtained by the communication device 140 of the present embodiment can refer to the method embodiment, and is not described herein again.

For example, the communication device is taken as the IAB host DU in the above method embodiment. Fig. 15 shows a schematic structural diagram of a communication device 150. The communication device 150 includes a processing module 1501 and a transceiver module 1502. The transceiver module 1502, which may also be referred to as a transceiver unit, includes a sending unit and/or a receiving unit, which may be, for example, a transceiver circuit, a transceiver, or a communication interface, to implement the sending and/or receiving functions of the IAB host DU in the above method embodiments. For example, step S702 in fig. 7, steps S702 and S801 in fig. 8, steps S1001, S1003, S1004 and S1005 in fig. 10, steps S1101, S1103, S1104 and S1105 in fig. 11, and steps S1201 and S1202 in fig. 12 are performed. The processing module 1501 is configured to perform data processing, so as to implement the function of processing the IAB host DU in the foregoing method embodiment, for example, execute step S703 in fig. 7, step S703 in fig. 8, step S1002 in fig. 10, and step S1102 in fig. 11.

Illustratively, the transceiver module 1502 is configured to receive third indication information from the IAB hosting centralized unit CU, where the third indication information is used to indicate a second RLC channel carrying a second type of packet between the IAB hosting DU and a child IAB node of the IAB hosting DU, where the second type of packet includes a second type of message, and the second type of message is used to indicate an internet protocol IP address allocated to the first IAB node, and the first IAB node is a child node of the IAB hosting DU or the first IAB node is connected to the IAB hosting DU through one or more intermediate IAB nodes.

And the processing module 1501 is configured to determine the second RLC channel according to the third indication information by the IAB host DU.

In one possible embodiment, the third indication information includes an identification of the second RLC channel.

In a possible implementation, the processing module 1501 is further configured to: a second data packet is generated. And when one or more items in the IP quintuple of the second data packet correspondingly meet the respective third values or third value ranges of one or more items in the IP quintuple of the second type data packet, or when the type of the message included in the second data packet is one of the type information, setting the preset field of the second data packet as the target value. And when the value of the preset field of the second data packet is the target value, the second data packet is carried through the second RLC channel.

In a possible implementation, the transceiver module 1502 is further configured to receive a first type data packet from the child node of the IAB host DU by the IAB host DU, where the first type data packet includes a first message, and the first message is used for the first IAB node to request an IP address. The processing module 1501 is further configured to acquire an IP address allocated to the first IAB node. The transceiving module 1502 is further configured to transmit the second type of data packet through the second RLC channel.

In a possible implementation, the processing module 1501 is further configured to determine a mapping relationship between the IP address and the identity of the first IAB node by the IAB host DU.

In the present embodiment, the communication device 150 is presented in a form of dividing each functional module in an integrated manner. A "module" herein may refer to a particular ASIC, a circuit, a processor and memory that execute one or more software or firmware programs, an integrated logic circuit, and/or other device that provides the described functionality. In a simple embodiment, one skilled in the art can appreciate that the communication device 150 can take the form of the network device 30 shown in fig. 3.

Specifically, the functions/implementation procedures of the processing module 1501 and the transceiver module 1502 in fig. 15 can be implemented by the processor 301 in the network device 30 shown in fig. 3 calling the computer execution instructions stored in the memory 302. Alternatively, the function/implementation procedure of the processing module 1501 in fig. 15 may be implemented by the processor 301 in the network device 30 shown in fig. 3 calling a computer executing instruction stored in the memory 302, and the function/implementation procedure of the transceiver module 1502 in fig. 15 may be implemented by the transceiver 303 in the network device 30 shown in fig. 3.

Since the communication device 150 provided in this embodiment can execute the RLC channel determining method, the technical effect obtained by the communication device 150 can refer to the method embodiment, and is not described herein again.

For example, the communication device is taken as the IAB host CU in the above method embodiment. Fig. 16 shows a schematic structural diagram of a communication device 160. The communication device 160 includes a processing module 1601 and a transceiver module 1602. The transceiver module 1602, which may also be referred to as a transceiver unit, includes a sending unit and/or a receiving unit, which may be, for example, a transceiver circuit, a transceiver, or a communication interface, and is configured to implement the sending and/or receiving functions of the IAB host DU in the foregoing method embodiments. For example, step S702 in fig. 7 and step S702 in fig. 8 are performed. The processing module 1601 is configured to perform data processing to implement the function of processing performed by the IAB host CU in the above method embodiment, for example, to execute step S701 in fig. 7 and step S701 in fig. 8.

Illustratively, the processing module 1601 is configured to determine third indication information, where the third indication information is used to indicate a second RLC channel carrying a second type of packet between the IAB-hosting distributed unit DU and a child IAB node connected to the IAB-hosting DU, where the second type of packet includes a second type of message, and the second type of message is used to indicate an internet protocol IP address allocated to the first IAB node, and the first IAB node is a child node of the IAB-hosting DU or the first IAB node is connected to the IAB-hosting DU through one or more intermediate IAB nodes.

The transceiver module 1602 is configured to send the third indication information to the IAB host DU.

In a possible implementation, the third indication information further includes third condition information or type information of the second type message, where the third condition information includes a third value or a third value range of one or more items in an IP five-tuple of the second type packet, the IP five-tuple includes a source IP address, a destination IP address, a source port number, a destination port number, and a transport layer protocol type, and the type information includes one or more of the following: dynamic Host Configuration Protocol (DHCP) messages, Router Solicitation (RS) messages, Router Advertisement (RA) messages, IP broadcast messages and IP multicast messages.

In the present embodiment, the communication device 160 is presented in a form of dividing each functional module in an integrated manner. A "module" herein may refer to a particular ASIC, a circuit, a processor and memory that execute one or more software or firmware programs, an integrated logic circuit, and/or other device that provides the described functionality. In a simple embodiment, those skilled in the art will appreciate that the communication device 160 may take the form of the network device 30 shown in fig. 3.

Specifically, the functions/implementation procedures of the processing module 1601 and the transceiver module 1602 in fig. 16 may be implemented by the processor 301 in the network device 30 shown in fig. 3 calling the computer execution instructions stored in the memory 302. Alternatively, the function/implementation procedure of the processing module 1601 in fig. 16 may be implemented by the processor 301 in the network device 30 shown in fig. 3 calling a computer executing instruction stored in the memory 302, and the function/implementation procedure of the transceiver module 1602 in fig. 16 may be implemented by the transceiver 303 in the network device 30 shown in fig. 3.

Since the communication device 160 provided in this embodiment can execute the RLC channel determining method, the technical effect obtained by the communication device 160 can refer to the method embodiment, and is not described herein again.

Embodiments of the present application also provide a communication apparatus, which includes a processor, a memory, and a transceiver, wherein the processor is coupled to the memory, and when the processor executes a computer program or instructions in the memory, an RLC channel determination method corresponding to the first IAB node, the IAB host DU, or the IAB host CU in fig. 5 to 12 is performed.

An embodiment of the present application further provides a chip, including: a processor and an interface, which are used to call and run the computer program stored in the memory from the memory, and execute the RLC channel determination method corresponding to the first IAB node, the IAB host DU, or the IAB host CU in fig. 5-12.

An embodiment of the present application further provides a computer-readable storage medium, which stores instructions that, when executed on a computer or a processor, cause the computer or the processor to execute an RLC channel determination method corresponding to the first IAB node, the IAB host DU, or the IAB host CU in fig. 5 to 12.

Embodiments of the present application further provide a computer program product containing instructions, which when executed on a computer or a processor, cause the computer or the processor to execute the RLC channel determination method corresponding to the first IAB node, the IAB host DU, or the IAB host CU in fig. 5 to 12.

An embodiment of the present application provides a chip system, where the chip system includes a processor, and is configured to enable a communication device to execute an RLC channel determination method corresponding to a first IAB node, an IAB host DU, or an IAB host CU in fig. 5 to 12.

In one possible design, the system-on-chip further includes a memory for storing program instructions and data necessary for the terminal device. The chip system may include a chip, an integrated circuit, and may also include a chip and other discrete devices, which is not specifically limited in this embodiment of the present application.

The communication apparatus, the chip, the computer storage medium, the computer program product, or the chip system provided in the present application are all configured to execute the RLC channel determining method described above, and therefore, the beneficial effects achieved by the communication apparatus, the chip, the computer storage medium, the computer program product, or the chip system may refer to the beneficial effects in the embodiments provided above, and are not described herein again.

The processor related to the embodiment of the application may be a chip. For example, the Field Programmable Gate Array (FPGA) may be an Application Specific Integrated Circuit (ASIC), a system on chip (SoC), a Central Processing Unit (CPU), a Network Processor (NP), a digital signal processing circuit (DSP), a Micro Controller Unit (MCU), a Programmable Logic Device (PLD) or other integrated chips.

The memory referred to in embodiments of the present application may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory may be a read-only memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an electrically Erasable EPROM (EEPROM), or a flash memory. Volatile memory can be Random Access Memory (RAM), which acts as external cache memory. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic Random Access Memory (SDRAM), double data rate SDRAM, enhanced SDRAM, SLDRAM, Synchronous Link DRAM (SLDRAM), and direct rambus RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to comprise, without being limited to, these and any other suitable types of memory.

It should be understood that, in the various embodiments of the present application, the sequence numbers of the above-mentioned processes do not mean the execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus, and method may be implemented in other ways. For example, the above-described device embodiments are merely illustrative, and for example, the division of the units is only one logical functional division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.

In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented using a software program, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. The procedures or functions described in accordance with the embodiments of the present application are all or partially generated upon loading and execution of computer program instructions on a computer. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored on a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website, computer, server, or data center to another website, computer, server, or data center via wire (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or can comprise one or more data storage devices, such as a server, a data center, etc., that can be integrated with the medium. The usable medium may be a magnetic medium (e.g., floppy Disk, hard Disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., Solid State Disk (SSD)), among others.

The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A method for radio link control, RLC, channel determination, comprising:

a first access backhaul integrated IAB node receives first indication information from an IAB host node, wherein the first indication information is used for indicating a first RLC channel which carries a first type data packet between the first IAB node and a parent node of the first IAB node, the first type data packet comprises a first type message, and the first type message is used for requesting an Internet Protocol (IP) address;

and the first IAB node determines the first RLC channel according to the first indication information.

2. The method of claim 1, wherein the first indication information comprises an identification of the first RLC channel.

3. The method of claim 2, wherein the first indication information further comprises first condition information or type information of the first type message;

the first condition information includes a first value or a first value range of one or more items in an IP five-tuple of the first type packet, the IP five-tuple includes a source IP address, a destination IP address, a source port number, a destination port number, and a transport layer protocol type, and the type information includes one or more of the following: dynamic Host Configuration Protocol (DHCP) messages, Router Solicitation (RS) messages, Router Advertisement (RA) messages, IP broadcast messages and IP multicast messages.

4. The method of claim 3, further comprising:

the first IAB node generates a first data packet;

the determining, by the first IAB node, the first RLC channel according to the first indication information includes:

when one or more items in the IP quintuple of the first data packet correspondingly meet the respective first value or first value range of one or more items in the IP quintuple of the first type data packet, determining that the first data packet is borne through the first RLC channel; alternatively, the first and second electrodes may be,

and when the message type of a first message included in the first data packet is one of the type information, determining that the first data packet is carried through the first RLC channel.

5. The method of claim 3, wherein the first indication information further comprises a target value of a preset field of the first type packet.

6. The method of claim 5, further comprising:

the first IAB node generates a first data packet;

when one or more items in the IP quintuple of the first packet correspondingly satisfy a first value or a first value range of one or more items in the IP quintuple of the first type packet, or when the type of the message included in the first packet is one of the type information, setting the preset field of the first packet to be the target value;

and when the value of the preset field of the first data packet is the target value, determining that the first data packet is carried through the first RLC channel.

7. The method according to claim 5 or 6, wherein the predetermined field is a Differentiated Services Code Point (DSCP) or a flow label.

8. The method of any of claims 4 or 6, wherein the first data packet further comprises an identification of the first IAB node.

9. The method of claim 8, wherein the identity of the first IAB node is carried in one or more fields of the first packet: the system comprises a client hardware address field, a DHCP unique identifier and a BAP address field of a backhaul adaptation protocol BAP layer.

10. The method according to any one of claims 1-9, further comprising:

the first IAB node receives second indication information from the IAB donor node, the second indication information indicating that a target node of the first type of data packet on the wireless backhaul link is the IAB donor node.

11. The method of claim 10, wherein the second indication information further comprises an identification of the IAB host node.

12. The method according to claim 10 or 11, wherein the first type packet includes an identifier of the IAB host node, the second indication information further includes second condition information or type information of the first type message, the second condition information is a second value or a second value range of one or more items in an IP five-tuple of the first type packet, and the type information includes one or more of the following: DHCP messages, RS messages, RA messages, IP broadcast messages, and IP multicast messages.

13. The method of claim 12, further comprising:

the first IAB node generates a second data packet;

and when one or more items in the IP quintuple of the second data packet correspondingly satisfy a second value or a second value range of one or more items in the IP quintuple of the first type data packet, or when the type of the message included in the second data packet is one of the type information, the second data packet includes the identifier of the IAB host node.

14. The method according to any one of claims 1-13, further comprising:

the first IAB node receives a second type of packet, wherein the second type of packet includes a second type of message indicating an IP address assigned to the first IAB node.

15. A method for radio link control, RLC, channel determination, comprising:

the method comprises the steps that an access backhaul integration IAB host node determines first indication information, wherein the first indication information is used for indicating a first RLC channel which carries a first type data packet between a first IAB node and a father node of the first IAB node, the first type data packet comprises a first type message, and the first type message is used for the first IAB node to request an Internet Protocol (IP) address;

the IAB host node sends the first indication information to the first IAB node.

16. The method of claim 15, wherein the first indication information comprises an identification of the first RLC channel.

17. The method of claim 16, wherein the first indication information further comprises first condition information or type information of the first type message;

18. The method of claim 17, wherein the first indication information further comprises a target value of a preset field in the first type packet.

19. The method of claim 18, wherein the predetermined field is a Differentiated Services Code Point (DSCP) or a flow label.

20. The method according to any one of claims 15-19, further comprising:

the IAB host node receiving the first type of packet from a first IAB node;

the IAB host node acquires an IP address distributed for the first IAB node;

the IAB donor node sends a second type of data packet to the first IAB node, wherein the second type of data packet comprises a second type of message, and the second type of message is used for indicating an IP address allocated to the first IAB node.

21. The method of claim 20, further comprising:

the IAB host node determines a mapping relationship between the IP address and the identity of the first IAB node.

22. The method according to any one of claims 15-21, further comprising:

the IAB donor node sends second indication information to the first IAB node, where the second indication information indicates that a target node of the first type data packet on the wireless backhaul link is the IAB donor node.

23. The method of claim 22, wherein the second indication information further comprises an identification of the IAB host node.

24. The method of claim 22, wherein the second indication information further includes second condition information or type information of the first type message, the second condition information being a second value or a second value range of one or more items in an IP five tuple of the first type packet, and the type information including one or more of the following: DHCP messages, RS messages, RA messages, IP broadcast messages, and IP multicast messages.

25. A communications apparatus comprising a processor coupled to a memory, the memory for storing a computer program or instructions, the processor for executing the computer program or instructions in the memory such that the method of any of claims 1 to 24 is performed.

26. A computer storage medium storing a program or instructions for implementing the method of any one of claims 1 to 24.