Configuration information exchange in integrated access and backhaul networks

Abstract

Methods, systems, and apparatuses are described for implementation in an integrated access and backhaul network (IAB). An example method for wireless communication includes transmitting, by a first network node connected to one or more second network nodes by one or more first wireless links, a system information message on a second wireless link, the system information message indicating all public land mobile networks to which the one or more second network nodes provide connectivity.

Description

Technical Field

[0001] This article mainly deals with wireless communication. Background Technology

[0002] Wireless communication technology is leading the world towards an increasingly interconnected and networked society. The rapid development and technological advancements in wireless communication have resulted in greater demands for capacity and connectivity. Other factors, such as energy consumption, equipment cost, spectrum efficiency, and latency, are also important for meeting the needs of various communication scenarios. Compared to existing wireless networks, next-generation systems and wireless communication technologies will support integrated access and backhaul networks. Summary of the Invention

[0003] This article relates to methods, systems, and devices in integrated access and backhaul (IAB) networks in mobile communication technologies, including 5G and new radio (NR) communication systems.

[0004] In one exemplary aspect, a wireless communication method is disclosed. The method includes: a first network node connected to one or more second network nodes via one or more first links transmitting a system information message on a second link, the system information message instructing the one or more second network nodes to provide it with access to all public terrestrial mobile networks.

[0005] In another exemplary aspect, a different wireless communication method is disclosed. The method includes: a first network node sending a first message to a second network node via a wireless link, the first message indicating that the first network node is capable of enabling wireless access network sharing features.

[0006] In another exemplary aspect, a different wireless communication method is disclosed. The method includes: receiving a message from a first network node on a wireless link by a second network node, the message indicating that the first network is capable of implementing wireless access network sharing features; and sending a message to the first network node regarding integrated access and backhaul operations based on information received from the first network node.

[0007] In another exemplary aspect, another wireless communication method is disclosed. The method includes: a first network node sending information from a first network node to one of a plurality of second network nodes having wired access to a core network or the Internet, the information relating to the first wireless node's ability to support RAN sharing by connecting to more than one second network node and a list of public terrestrial mobile networks supported by the first network node.

[0008] In another exemplary aspect, another wireless communication method is disclosed. The method includes: a second network node having a central capability to connect to a core network or the Internet receiving capability information of a first network node that allows it to connect to other network nodes having said central capability, and a list of public terrestrial mobile networks supported by the first network node; and the second network node transmitting a message regarding operation of an Integrated Access and Backhaul (IAB) network to a third network node among said other network nodes.

[0009] In another exemplary aspect, a different wireless communication method is disclosed. The method includes: a third network node receiving a message from a second network node regarding the Integrated Access and Backhaul (IAB) functionality of a first network node. The message is available to the third network node for further operation.

[0010] In another exemplary aspect, another wireless communication method is disclosed. The method includes: a first network node configured as an IAB node in an Integrated Access and Backhaul (IAB) network receiving an input packet on a first channel; and the first network node transmitting an output packet based on the input packet to a second network node operating as a Central Unit (CU) in the IAB network on a second channel.

[0011] In another exemplary aspect, a different wireless communication method is disclosed. The method includes operating a network node in an Integrated Access and Backhaul (IAB) network by providing bidirectional communication between an IAB node and an IAB host central unit (CU). The network node receives a first encapsulated F1-C service as a Radio Resource Control (RRC) message from the IAB node and forwards it to the IAB host CU as a first F1AP message. The network node receives a second F1AP message from the IAB host CU and forwards it to the IAB node as a second RRC message.

[0012] In another exemplary aspect, another wireless communication method is disclosed. The method includes: a second network node, configured as a central unit (CU) of an Integrated Access and Backhaul (IAB) network, receiving a message from a first network node operating as an IAB node, the message indicating that the first network node can communicate with the second network node using an output channel of a first distributed unit (DU) implementing a backhaul protocol or via a second (DU) without the backhaul protocol; and the second network node sending configuration information to the first network node regarding how to select the output channel.

[0013] In yet another exemplary aspect, the above-described method is implemented in the form of processor-executable code and stored in a computer-readable program medium.

[0014] In yet another exemplary embodiment, a device is disclosed that is configured or operable to perform the methods described above.

[0015] The above and other aspects and their implementations are described in more detail in the accompanying drawings, specification, and claims. Attached Figure Description

[0016] Figure 1 An example of an IAB network is shown;

[0017] Figure 2 An example of an IAB parent node in an IAB network is shown;

[0018] Figure 3 This illustrates the protocol stack implementation in the gNodeB of an IAB network;

[0019] Figure 4 This illustrates an example of packet processing across the protocol stack in an IAB network;

[0020] Figure 5 It is a block diagram representation of a part of a method and apparatus that can be used to implement the techniques disclosed herein;

[0021] Figures 6A to 6I An example of a method for wireless communication is shown. Detailed Implementation

[0022] The use of chapter headings in this document is merely for readability purposes and does not limit the scope of the embodiments and techniques disclosed in each chapter to that chapter. Examples using fifth-generation (5G) wireless protocols illustrate certain features. However, the applicability of the techniques disclosed herein is not limited to 5G wireless systems only.

[0023] The following abbreviations are used in this article.

[0024] 3GPP - Third Generation Partnership Project

[0025] 5G is the fifth-generation wireless protocol specified by 3GPP.

[0026] AMF - Access and Mobility Function

[0027] AP - Application Protocol

[0028] BAP - Backhaul Access Protocol

[0029] BH - Backhaul

[0030] CP - Control Plane

[0031] CU - Central Unit

[0032] DRB - Data Radio Bearer

[0033] DS - Differentiated Service

[0034] DSCP - Differentiated Services Code Point

[0035] DU - Distributed Unit

[0036] EN-DC-E-UTRAN New Radio

[0037] E-UTRAN - Evolved Universal Terrestrial Radio Access Network

[0038] F1 - Interface used for communication between gNB DU and gNB CU

[0039] gNB-gNodeB

[0040] IAB - Integrated Access and Backhaul

[0041] ID - Identifier

[0042] IP - Internet Protocol

[0043] IPSec - Internet Protocol Security

[0044] LTE - Long Term Evolution wireless standard

[0045] MAC - Medium Access Control

[0046] MCG - Master Cell Group

[0047] MIMO - Multiple-input multiple-output

[0048] MT - Mobile Termination

[0049] NDS - Network Domain Security

[0050] NR - New Radio standard specified by 3GPP

[0051] OAM - Operation Administration and Maintenance

[0052] PDCP - Packet Data Convergence Protocol

[0053] PDU - Protocol Data Unit

[0054] PHY - Physical Layer

[0055] PLMN - Public Land Mobile Network

[0056] RAN - Radio Access Network

[0057] RLC - Radio Link Control

[0058] RRC - Radio Resource Control

[0059] SCG - Secondary Cell Group

[0060] SDAP - Service Data Adaptation Protocol

[0061] SRB - Signaling Radio Bearer

[0062] STC - Synchronization Signal Block Transmission Configuration

[0063] UE - User Equipment

[0064] UP - User Plane

[0065] Compared to Long Term Evolution (LTE), systems based on the New Radio (NR) specification can utilize significantly more available bandwidth. The use of massive MIMO and multi-beam architectures enables integrated access and backhaul (IAB) links. Through radio backhaul and relay links, denser NR cell networks can be deployed more flexibly without requiring a corresponding increase in the density of the transport network. Figure 1 The diagram illustrates an example of a network deployed with integrated access and backhaul links, where A, B, and C are all access nodes. User equipment (UEs) can access nodes A, B, and C via access links, but only access node A has a wired connection to the core network; access nodes B and C do not have wired connections to the core network element. The access node that supports UE wireless access and transmits data wirelessly is called an IAB node. The access node that provides wireless backhaul functionality to the IAB node to enable UE connection to the core network is called an IAB host. UE data can be transmitted between access nodes via wireless backhaul links. For example, access node B can send data received from the UE to access node A via a wireless backhaul link, and then access node A sends the UE data to the core network element. For the downlink, the core network element can send UE data packets to access node A, and then access node A sends the UE data to access node B via a wireless backhaul link, and access node B sends the UE data to the UE via an access link. Access links and backhaul links can use the same or different carrier frequencies. Furthermore, UE data may need to be transmitted via multi-hop relay backhaul links between the access node and the core network. Additionally, supporting separate deployment of CU / DU is a key technical feature of NR. IAB functionality is supported in CU / DU separate deployment scenarios.

[0066] The examples used in this article from the 3GPP New Radio (NR) network architecture and 5G protocols are for the purpose of facilitating understanding only, and the disclosed technologies and embodiments can be practiced in other wireless systems using communication protocols different from the 3GPP protocols.

[0067] Wireless backhaul links and relay links enable the flexible deployment of high-density NR cell networks without the need for denser deployment of traditional transmission network components. Figure 1 An example of a network with an Integrated Access and Backhaul (IAB) link is shown. As illustrated, A (101), B (102), and C (103) are access nodes, and user equipment (UEs 111, 112, and 113) can communicate with access nodes A, B, and C via the access link. Only access node A has a wired connection to the core network; access nodes B and C do not have wired connections to the core network elements. The access node that supports the UE's radio access and transmits data wirelessly is called an IAB node (e.g., 102 or 103), while the access node that provides radio backhaul functionality to the IAB node to enable the UE to connect to the core network is called an IAB host (e.g., 101). Therefore, access nodes can transmit UE data via the radio backhaul link.

[0068] In one example, Access Node B can transmit data received from the UE to Access Node A via a wireless backhaul link, and then Access Node A transmits the UE data to the core network element. For the downlink, the core network element can send UE data packets to Access Node A, and then Access Node A transmits the UE data to Access Node B via the wireless backhaul link, and Access Node B transmits the UE data via the access link. In some embodiments, the access link and the backhaul link can use the same carrier frequency. In other embodiments, they can use different carrier frequencies. In some embodiments, UE data may need to be transmitted via a multi-hop relay backhaul link between the access node and the core network.

[0069] In some embodiments, an access node may include a control unit (CU) and one or more distributed units (DUs). In one example, the CU is a logical node that hosts the Radio Resource Control (RRC), Serving Data Adaptation Protocol (SDAP), and Packet Data Convergence Protocol (PDCP) of the access node, controlling the operation of one or more DUs. The DU is a logical node that hosts the Radio Link Control (RLC), Media Access Control (MAC), and Physical (PHY) layers of the access node. The CU and the DU(s) it controls are connected via an F1 interface. The F1 Application Protocol (F1-AP) is used to transmit lower-layer configuration information of radio bearers between the CU and DUs and to establish a GTP tunnel between the DU and CU for each radio bearer. The CU / DU separation supported in NR is also supported in IAB deployments.

[0070] In the future, it may be possible to deploy IAB-enabled devices or network nodes alongside those without IAB functionality in wireless networks. For example, LTE and current 5G base stations may not implement the Backhaul Access Protocol (BAP), which specifies the data format used on the backhaul link. Furthermore, even among network nodes that implement IAB functionality, several technical challenges exist. This document provides technical solutions that can be used in embodiments of IAB networks using IAB-enabled network nodes or IAB networks that also include nodes without IAB capabilities. Additionally, some embodiments can enable the sharing of multiple Radio Access Networks (RANs). Some embodiments can be used to implement control plane (CP) and user plane (UP) separation in IAB networks.

[0071] Exemplary Example 1

[0072] In this embodiment, an IAB-DU can be connected to only one host CU.

[0073] When an IAB node integrates into an IAB network, it can first select the parent node to connect to. If the IAB node supports sharing between different Public Land Mobile Networks (PLMNs), the CU to which the IAB node ultimately connects should also support RAN sharing. Furthermore, the PLMNs supported by the CU should cover the PLMN groups supported by the IAB node. If the IAB node performs parent node selection solely based on the received System Information Block (SIB1) information, it can connect to a CU that does not support RAN sharing or a CU that does not support the PLMNs supported by the IAB node. In this case, the following operations can be performed:

[0074] 1. The IAB node selects a parent node with IAB capabilities to connect to, and then the CU hands over the IAB node to the appropriate target CU.

[0075] 2. The system information broadcast by the parent node includes the PLMN IDs supported by all host CUs to which the parent node is connected.

[0076] The CU may need to know whether the IAB node supports sharing between different PLMNs. Therefore, the IAB-MT can send the following information to the CU. This information can be sent via higher-level messages (e.g., via Radio Resource Control (RRC) messages):

[0077] - An indication of whether the IAB node supports RAN sharing;

[0078] - Supported PLMN IDs (if any);

[0079] - The PLMN ID and AMF ID of the registered AMF.

[0080] The PLMN ID supported by the CU is sent to the parent node via RRC messages or F1 application protocol F1AP messages.

[0081] For RAN sharing, in some embodiments, F1 messages belonging to different PLMNs can be sent over the same transport network. In some embodiments, F1 messages belonging to different PLMNs can be sent over different transport networks. The Internet Protocol (IP) address encapsulating the packet belonging to PLMN 1's service can be the IP address of PLMN 1. Therefore, the IP addresses requested by the IAB-MT can be for each PLMN, meaning that the IAB-MT can send a list of supported PLMNs to the CU. This list can be sent via RRC messages. For each PLMN, the IAB-MT informs the CU of the number of IP addresses requested, the version of the IP addresses (e.g., v4 or v6), and the purpose of the IP addresses.

[0082] If the host DU is responsible for IP address allocation, the CU sends the following information to the host DU via F1AP message.

[0083] In some embodiments, the CU can send a list of PLMNs supported by the IAB-DU to the host DU.

[0084] In some embodiments, the IP address requested by the CU is for each PLMN.

[0085] Exemplary Example 2

[0086] This embodiment focuses on an IAB-DU connected to more than one host CU. In the following description, the case of an IAB-DU connected to two host CUs is used as an example, where CU1 is the primary CU and CU2 is the secondary CU.

[0087] When integrated into the network, IAB-MT can first perform parent node selection. The following parent node selection schemes can be considered:

[0088] Option 1: The IAB node has a pre-configured list of parent nodes, and then the parent node is selected from the list.

[0089] Option 2: The IAB node configures a list of parent nodes through OAM, and then selects a parent node from the list.

[0090] Option 3: Based on SIB information, which includes a list of PLMNs supported by the host CU.

[0091] After selecting the appropriate parent node 1, IAB-MT will establish an RRC connection with CU 1.

[0092] IAB-MT can notify CU1 of its support for or ability to share by connecting to a list of different host CUs and PLMNs supported by IAB-MT. CU1 can then configure the IAB-MT portion using measurement configuration to perform discovery, measurement, and measurement reporting of candidate gNBs. After receiving the measurement report, CU1 can select CU2 for IAB-MT and then execute the SgNB addition procedure. CU1 sends an IAB node indication to CU2 via the Xn interface. Finally, IAB-MT connects to CU2.

[0093] Regarding F1-C traffic delivery, the following options may be considered.

[0094] Option 1: IAB-DU sends the F1-C service to CU1 through parent node 1, and sends the F1-C service to CU2 through parent node 2.

[0095] Option 2: The IAB-DU sends the F1-C service to CU1 / CU2 via parent node 1. Specifically, the F1-C service to be sent to CU2 is contained in an F1AP message, which is decoded by CU1. When CU1 receives the F1AP message containing the F1-C service container, it sends the F1-C service container to CU2 via the Xn interface. Correspondingly, CU2 includes the F1-C service in the container and sends the F1-C service container to CU1 via the Xn interface. Then, CU1 sends the received F1-C service container to the IAB-DU via an F1AP message. In this way, the IAB-DU can receive the F1-C service generated by CU2.

[0096] The ability of CU1 and CU2 to exchange F1-C services can be transmitted through the Xn interface.

[0097] The IAB node reports to CU1 via RRC messages whether it supports option 2.

[0098] For F1-C services originating from / to CU2, CU1 determines whether to configure the IAB node using Option 1 and / or Option 2. When both options are configured, the IAB node implementation determines the method of F1-C service delivery. Configuration can be performed before the IAB-DU section is set up. The IAB host CU can also change its configuration after the IAB-DU section is set up.

[0099] Regarding IAB STC information configuration, if the following situations occur, a mechanism to avoid configuration conflicts needs to be considered.

[0100] Scenario 1: IAB-DU only sends IAB STC information to CU1. In this case, CU1 should send the IAB STC to CU2.

[0101] Scenario 2: IAB-DU sends IAB STC information to both CU1 and CU2. CU1 and / or CU2 plan to modify the IAB STC information.

[0102] For each shared cell, CU1 / CU2 provides CU2 / 1 with several candidate IAB STC configurations and corresponding indexes via the Xn interface. CU2 / CU1 selects one of the candidate IAB STC configurations and then sends the index corresponding to the selected IAB STC configuration to CU1 / 2 via the Xn interface.

[0103] If the IAB-DU does not send IAB STC information to the CU, the CU determines the IAB STC configuration. Considering potential configuration conflicts, for each shared cell, CU1 provides several candidate IAB STC configurations to CU2 via the Xn interface, and optionally provides the corresponding index. CU2 selects one IAB STC configuration from the candidates and then sends the index corresponding to the selected IAB STC configuration to CU1 via the Xn interface.

[0104] For IAB-DU resource configuration, considering the possibility of configuration conflicts, for each shared cell, CU1 provides CU2 with several candidate GNB-DU resource configurations via the Xn interface, and optionally provides the corresponding index. CU2 selects a GNB-DU resource configuration from the candidates, and then sends the selected resource configuration information or the index corresponding to the selected resource configuration to CU1 via the Xn interface.

[0105] CU2 can also send configuration information for all cells served by CU2, such as IAB STC information and resource configuration information, to CU1. In this case, CU2 will not send IAB STC information to IAB-DU and will not generate GNB-DU resource configuration messages. This means that IAB-DU only receives IAB STC information and resource configuration from messages sent by CU1, and only uses GNB-DU resource configuration acknowledgment messages to respond to CU1.

[0106] The methods described above can also be applied to child nodes.

[0107] Example 3

[0108] This embodiment focuses on IAB nodes with dual connectivity in frequency range 1 and frequency range 2, and FR1 / FR2 DC. Specifically, the IAB nodes in the NR-DC can be configured with FR1 primary cell group MCG provided by gNB DU without backhaul access protocol (BAP) capability and FR2 SCG through host DU with BAP capability. Figure 2 An example is shown in the figure.

[0109] Figure 2 An example of an IAB network is shown, where an IAB node (labeled IAB node 2) operates as a parent node. Figure 2 From left to right, UE1 is served by IAB5, which communicates with IAB node 2 through IAB node 4. Similarly, IAB node 3 communicates with IAB node 2. Another UE2 is directly connected by IAB node 2. Towards the core network, IAB node 2 has two possible channels through which it can communicate with the CU. The first channel is through IAB node 1, which connects to the CU via an IAB host DU. The second channel corresponds to a host DU that does not support or implement the IAB protocol, and is also coupled to the CU.

[0110] IAB Node 2 can send / receive services to / from Host CU through a Host DU or Host DU without BAP capability. IAB Node 2 can report its capability information to CU, i.e., whether it can deliver services to CU through a Host DU without BAP capability.

[0111] The host CU determines whether to configure only the FR1 tributary, only the FR2 tributary, or both for service delivery. Configuration can be performed before the IAB-DU section setup. The IAB host CU can also change the configuration after the IAB-DU section setup. If no configuration is performed before the IAB-DU section setup, the IAB node uses the FR2 tributary as the default tributary. When both the FR1 and FR2 tributaries are configured, the IAB node implementation selects the tributary for service delivery.

[0112] For FR1 and FR2 tributaries, separate IP address pairs should be used: {IP address of IAB-DU, IP address of CU}.

[0113] For F1-C services generated by IAB node 2, the IAB node encapsulates the uplink F1-C service in an NR RRC message and first sends it to the host DU without BAP capability. Then, the host DU without BAP capability sends the uplink F1-C service to the IAB host CU via the UE-associated F1AP message. For downlink, the IAB host CU encapsulates the F1-C service in an F1AP message and first sends it to the host DU without BAP capability. After receiving the F1AP message, the host DU without BAP capability uses an NR RRC message to send the contained F1-C service to the IAB-MT.

[0114] Figure 3The protocol stack for F1-C between the IAB-DU and the IAB host CU-CP is shown when F1-C services are sent through a host DU that does not have BAP capability.

[0115] Since CP services are transmitted via the FR1 tributary, CP services generated by downstream nodes should also be forwarded by IAB node 2 via the FR1 tributary.

[0116] For the F1-C service forwarded by IAB Node 2, in R16 IAB, once a BAP packet is received, IAB Node 2 should read the BAP header and confirm the egress node and egress BH RLC channel based on the mapping configuration. However, there are only signaling radio bearers (SRBs) and data radio bearers (DRBs) between IAB-MT 2 and the host DU. Therefore, IAB Node 2 cannot determine which RLC entity the BAP PDU should be delivered to.

[0117] To address this issue, IAB Node 2 decapsulates the BAP packets to obtain the IP packets. It then forwards the IP packets to the RRC layer. The IP packets are included in the RRC message. IAB-MT submits the RRC message to the lower layers for transmission. However, IAB Node 2 first needs to determine whether it should decapsulate the BAP packets. The following scheme can be considered (see reference). Figure 4 ):

[0118] 1) Because the IAB-DU is aware of the BH RLC channel used for CP signaling transmission, when a UL packet is received from the BH RLC channel used for CP signaling transmission, the IAB-DU decapsulates the BAP packet. This only applies when all CP signaling is transmitted through the FR1 tributary.

[0119] 2) The destination BAP address in the routing ID within the BAP header is equal to the BAP address of IAB node 2. This implicitly instructs IAB node 2 to decapsulate the BAP packet.

[0120] 3) Use one bit in the BAP header to indicate the CP service transmission type. For example, in some embodiments, a header value of "1" can indicate the FR1 tributary, and a header value of "0" can indicate the FR2 tributary. Once the CP service transmission type is set to 1, IAB node 2 decapsulates the BAP packet.

[0121] In the case of R16 EN-DC, all CP signaling is transmitted via SRB1. In R17 IAB, the following options are available.

[0122] Option 1: All CP signaling is transmitted via SRB1.

[0123] Option 2: Some CP signaling is transmitted via SRB1, while some is transmitted via SRB2. For example, the following embodiment can be used.

[0124] In some embodiments, SCTP-related signaling / IPsec-related signaling / non-UE-related signaling has a higher priority than UE-related signaling, so the BAP header can indicate "CP service priority = xx".

[0125] In some embodiments, packets with a large hop count are sent via SRB1, so the BAP header may include the "hop count," which helps in making decisions about transmission.

[0126] Accordingly, the CU should include the DL F1-C service in the RRC message and send it to the IAB node via the FR1 tributary. Upon receiving the RRC message, the IAB-MT should forward the IP packet to the IAB-DU. The IAB-DU performs service mapping from the IP layer to Layer 2. The service mapping information is configured by the IAB host CU via the F1AP message, which includes IP header information (e.g., IP address, flow label, DS / DSCP) and BH information, including the BAP route ID and a list of egress links and BH RLC channel pairs.

[0127] Service mappings can be configured as part of the UE context setting or UE context modification process. They can also be configured through a non-UE-associated BAP mapping configuration process.

[0128] Figure 5 This is a block diagram representation of a portion of an apparatus according to some embodiments of the techniques disclosed herein. Apparatus 505, such as a base station or wireless device (or UE), may include processor electronics 510, such as a microprocessor implementing one or more of the techniques described herein. Apparatus 505 may include transceiver electronics 515 for transmitting and / or receiving wireless signals via one or more communication interfaces, such as one or more antennas 520. Apparatus 505 may include other communication interfaces for transmitting and receiving data. Apparatus 505 may include one or more memories (not explicitly shown) configured to store information such as data and / or instructions. In some implementations, processor electronics 510 may include at least a portion of transceiver electronics 515. In some embodiments, apparatus 505 is used to implement at least some of the disclosed techniques, modules, or functions. The network node functions described herein may be implemented using a hardware platform similar to apparatus 505. In some cases, an IAB node may be configured with multiple antennas 520, respectively for access and backhaul.

[0129] The technical solutions described herein can be further described using the solutions listed below, which can preferably be implemented in some embodiments.

[0130] The following schemes can be implemented by IAB nodes, for example, as described with respect to Exemplary Example 1.

[0131] 1. A method for wireless communication (e.g., Figure 6A The method 600 described herein includes: a first network node connected to one or more second network nodes via one or more first links sending (602) a system information message on a second link, the system information message instructing the one or more second network nodes to provide connectivity to all public terrestrial mobile networks. The link may be a wired link or a wireless link.

[0132] For example, the first network node may be a parent IAB node, and the one or more second network nodes may be IAB nodes connected to the parent IAB node.

[0133] 2. The method according to Scheme 1, wherein the one or more first links operate in a suitable frequency band on a backhaul band or a wired channel, and wherein the second link operates in the backhaul band or another wired channel.

[0134] 3. The method according to any one of Schemes 1 to 3, wherein the first network node is a parent Integrated Access and Backhaul (IAB) node or an IAB Host Distributed Unit (DU).

[0135] The following schemes can be implemented by IAB nodes, for example, as described with respect to Exemplary Example 1.

[0136] 4. A method for wireless communication (e.g., Figure 6B The method 610 described herein includes: a first network node sending (612) a first message to a second network node via a wireless link, the first message indicating that the first network node is capable of realizing wireless access network sharing features.

[0137] In this scheme, the first network node can operate as an IAB node, and the second network node can be a CU.

[0138] 5. The method according to Scheme 4, wherein the first message identifies the Public Land Mobile Network (PLMN) that the first network node can support.

[0139] 6. The method according to any one of claims 4 to 5, comprising: the first network node receiving a second message from the second network node, the second message indicating a public land mobile network supported by the second network node.

[0140] 7. The method according to any one of schemes 4 to 6, wherein the first message is a Radio Resource Control (RRC) message.

[0141] 8. The method according to any one of schemes 4 to 6, wherein the second message is an RRC message or an F1AP message.

[0142] 9. The method according to any one of schemes 4 to 9 further includes: the first network node requesting an Internet Protocol (IP) address from the second network node on a per-public terrestrial mobile network basis.

[0143] The following schemes can be implemented by the CU, for example, as described with respect to Exemplary Example 1.

[0144] 10. A wireless communication method (e.g., Figure 6C The method 620 described herein includes: receiving (622) a message from a first network node on a wireless link by a second network node, the message indicating that the first network is capable of implementing wireless access network sharing features; and sending (624) a message to the first network node regarding integrated access and backhaul operations based on information received from the first network node.

[0145] In this scheme, the first network node can operate as an IAB node, and the second network node can be a CU.

[0146] 11. The method according to claim 10, wherein the message includes a list of Public Land Mobile Network (PLMN) identifiers supported by the second network device.

[0147] 12. The method according to Scheme 11, wherein the message is received via a Radio Resource Control (RRC) message or an FIAP message.

[0148] 13. The method according to any one of schemes 11 to 12, comprising: sending the list of PLMN identifiers from the second network node to a third network node operating as a host distributed unit (DU).

[0149] 14. The method according to any one of schemes 11 to 12, wherein the second network node requests an Internet Protocol (IP) address from a third network node operating as a Host Distributed Unit (DU) on a per PLMN basis.

[0150] The following schemes can be implemented by IAB nodes, for example, as described with respect to Exemplary Example 2.

[0151] 15. A method for wireless communication (e.g., Figure 6D The method 630 described herein includes: sending (632) information from a first network node to one of a plurality of second network nodes having wired access to a core network or the Internet, the information being about the first wireless node’s ability to support RAN sharing by connecting to other second network nodes and a list of public terrestrial mobile networks supported by the first network node.

[0152] 16. The method according to claim 15, wherein the information is sent as a Radio Resource Control (RRC) message.

[0153] The following schemes can be implemented by CU1, for example, as described with respect to exemplary embodiment 2.

[0154] 17. A data communication method (e.g., Figure 6E The method 640 described herein includes: receiving (642) capability information of the first network node that it can connect to other network nodes that have said central capability, and a list of public land mobile networks supported by the first network node, by a second network node having a central capability to connect to a core network or the Internet; and transmitting (644) a message about the operation of the Integrated Access and Backhaul (IAB) network from the second network node to a third network node among the other network nodes.

[0155] As mentioned above, the measurement report can be used for transmission (644) operation.

[0156] In this scheme, central capability can refer to the ability of a network node to be configured as a CU in the IAB.

[0157] In this scheme, the first network node can operate as an IAB node, and the second network node can be a CU.

[0158] 18. The method according to scheme 17, comprising: sending an IAB node indication, for example, from the first network node to the third network node from the second network node.

[0159] 19. The method according to Scheme 17 includes: the second network node forwarding a message received in a container format on the first interface to the third network node in another container format via a second interface.

[0160] 20. The method according to any one of schemes 17 to 19, comprising: transmitting a plurality of candidate synchronization signal block transmission configurations (STCs) for a shared cell from the second network node to the third network node, and transmitting IAB STC information received from the first network node from the second network node to the third network node. The latter can be performed only if CU1 has already received the IAB STC information.

[0161] 21. The method according to any one of Schemes 17 to 18, comprising: transmitting the resource configuration of multiple candidate base station distributed units (GNB-DU) of the shared cell from the second network node to the third network node.

[0162] 22. The method according to claim 20 or 21, wherein the transmission further includes transmitting configuration for providing a wireless connection to a network node or wireless device.

[0163] 23. The method according to claim 22, wherein the transmission further includes transmitting an index for providing a configuration for a wireless connection to a network node or wireless device.

[0164] 24. The method according to Scheme 17 includes: exchanging information between the second network node and the third network node regarding the transmission of F1-C services through the Xn interface.

[0165] 25. The method according to any one of schemes 17 to 24, comprising: configuring the first network by the second network node to encapsulate F1-C services destined for or from the third network node in an F1-AP message.

[0166] 26. The method according to Scheme 17 includes: receiving from the first network node by the second network node a capability indication that the first network node can encapsulate F1-C services destined for or from the third network node in an F1-AP message; and forwarding F1-C data from the first network node to the third network node on the Xn interface based on the capability indication.

[0167] The following schemes can be implemented by a CU, for example, as described with respect to CU2 in Exemplary Example 2.

[0168] 27. A wireless communication method (e.g., Figure 6F The method 650 described herein includes: receiving (652) a message from a second network node by a third network node regarding the integrated access and backhaul (IAB) functionality of a first network node, and providing (654) a connection to the first network node based on the message.

[0169] As described in Example 2, in some cases, the message may be based on the result of a measurement performed on the channel between the third network node and the second network node.

[0170] In this scheme, the first network node can operate as an IAB node, and the second network node can be a CU.

[0171] 28. The method according to Scheme 1, wherein the message is received on the Xn interface.

[0172] 29. The method according to Scheme 27 includes: the third network node receiving a message received on a first interface of the second network node from the second network node through a second interface to the third network node, wherein the message adopts a second format different from a first format on the first interface.

[0173] 30. The method according to any one of schemes 27 to 29, comprising: the third network node receiving a plurality of candidate synchronization signal block transmission configurations (STCs) of the shared cell from the second network node.

[0174] 31. The method according to any one of Schemes 27 to 28, comprising: the third network node receiving resource configuration of multiple candidate base station distributed units (GNB-DU) of the shared cell from the second network node.

[0175] 32. The method according to claim 30 or 31, wherein the receiving further includes receiving an index for providing a wireless connection to a network node or wireless device.

[0176] 33A. The method according to any one of Schemes 1 to 6, comprising: sending resource configuration of a cell serving a public land mobile network supported only by the third network node to the second network node.

[0177] 33B. The method according to any one of claims 32 to 33, comprising: selecting a configuration from a plurality of candidates; and sending the configuration or an index of the configuration to the second network node via an Xn interface; wherein the configuration includes an IAB STC or a resource configuration.

[0178] The following schemes can be implemented by IAB nodes, for example, as described with respect to exemplary embodiment 3.

[0179] 34. A wireless communication method (e.g., Figure 6GThe method 660 described herein includes: receiving (662) an input packet on a first channel by a first network node configured as an IAB node in an Integrated Access and Backhaul (IAB) network; and sending (664) an output packet based on the input packet by the first network node on a second channel to a second network node operating as a Central Unit (CU) in the IAB network.

[0180] 35. The method according to Scheme 34, wherein the first network node is coupled to the second network node by implementing a first distributed unit (DU) of the backhaul protocol and a second (DU) that does not have the backhaul protocol, the method comprising: sending from the first network node to the second network node an indication that the first network node is capable of sending and receiving F1 services and forwarded services with the second network node through the second DU.

[0181] 36. The method according to any one of schemes 34 to 35, wherein the use of the second channel to send and receive F1 services and the forwarded services is based on the configuration received by the first network node from the second network node.

[0182] 37. The method according to any one of claims 35 to 36, comprising: sending the F1-C service from the first network node to the second network node by encapsulating the F1-C service generated by the first network node in a first radio resource control message to the second DU.

[0183] 38. The method according to any one of claims 35 to 36, comprising: the first network node receiving an F1-C service from the second DU for the first network node, wherein the F1-C service is encapsulated in a second radio resource control message.

[0184] 39. The method according to any one of claims 34 to 36, wherein the output packet is obtained from the input packet by decapsulating the input packet. For example, the packet can be decapsulated into an Internet Protocol (IP) packet.

[0185] 40. The method according to Scheme 37, wherein the input packet is decapsulated to determine the output packet based on information in the header field.

[0186] 41. The method according to Scheme 38, wherein the information in the header field corresponds to the backhaul adaptation protocol address of the first network node.

[0187] 42. The method according to scheme 38, wherein the information in the header field indicates the transmission type for transmitting control plane packets.

[0188] 43. The method according to scheme 38, wherein the rule specifies that when the input packet carries control plane (CP) data, all output packets are transmitted through the second channel.

[0189] 44. The method according to scheme 34, wherein the rule specifies that the second channel is selected based on the characteristics of the control plane (CP) data carried by the input packets.

[0190] 45. The method according to scheme 42, wherein the characteristics of the input packet correspond to the service priority of the CP data carried.

[0191] 46. ​​The method according to scheme 42, wherein the characteristics of the input group correspond to the number of hops of the input group.

[0192] The following scheme can be implemented by a DU that does not implement BAP, for example, as described with respect to exemplary embodiment 3.

[0193] 47. A wireless communication method (e.g., Figure 6H The method 670 described herein includes: operating (672) a network node in an Integrated Access and Backhaul (IAB) network by providing bidirectional communication between an IAB node and an IAB host central unit (CU), wherein the network node receives a first encapsulated F1-C service as a Radio Resource Control (RRC) message from the IAB node and forwards it to the IAB host CU as a first F1AP message; and wherein the network node receives a second F1AP message from the IAB host CU and forwards it to the IAB node as a second RRC message.

[0194] 48. The method according to scheme 47, wherein the network node is a base station configured to operate without supporting the backhaul access protocol.

[0195] The following schemes can be implemented by the CU, for example, as described with respect to Exemplary Example 3 for the host CU.

[0196] 49. A wireless communication method (e.g., Figure 6IThe method 680 described herein includes: receiving (682) a message from a first network node operating as an IAB node by a second network node configured as a central unit (CU) of an integrated access and backhaul (IAB) network, the message indicating that the first network node is capable of communicating with the second network node using either a first distributed unit (DU) implementing a backhaul protocol or an output channel of a second (DU) not having said backhaul protocol; and sending (684) configuration information from the second network node to the first network node regarding the selection between using the first DU or the second DU to communicate with the second network node.

[0197] 50. The method according to scheme 49, comprising: receiving packets via the output channel, the packets comprising control plane (CP) data routed via the first DU or the second DU according to the configuration.

[0198] 51. A communication device comprising a processor and a transceiver, wherein the processor is configured to read code from the memory and implement the method according to any one of claims 1 to 49.

[0199] 52. A computer program product comprising computer-readable program medium code stored thereon, the code causing the processor, when executed by a processor, to perform the method according to any one of claims 1 to 49.

[0200] In this document, the term "connection" refers to a communication connection via a communication channel; unless otherwise specified, a physical connection is not required. The term "support" may describe a given device being configured to operate according to, or implementing, a specific feature or protocol, or being able to operate without errors in a specific network configuration.

[0201] Understandably, this document discloses techniques that can be implemented by network nodes to address various technical challenges in wireless IAB networks. One exemplary technique relates to how various network nodes can support multiple RANs by transmitting information about their capabilities. Another exemplary technique can be used to implement CP / UP separation in a CU, and for host DUs with and without BAP capabilities to transmit services to and from IAB nodes and CUs.

[0202] Some of the embodiments described herein are described in the general context of methods or processes that, in one embodiment, can be implemented by a computer program product embodied in a computer-readable medium, including computer-executable instructions, such as program code, that are executed by a computer in a networked environment. The computer-readable medium may include removable and non-removable storage devices, including but not limited to read-only memory (ROM), random access memory (RAM), optical disc (CD), digital versatile optical disc (DVD), etc. Therefore, the computer-readable medium may include non-transitory storage media. Typically, a program module may include routines, programs, objects, components, data structures, etc., that perform a particular task or implement a particular abstract data type. Computer or processor-executable instructions, associated data structures, and program modules represent examples of program code for performing steps of the methods disclosed herein. A particular sequence of such executable instructions or associated data structures represents examples of corresponding actions for implementing the functionality described in such steps or processes.

[0203] Some of the disclosed embodiments can be implemented as devices or modules using hardware circuitry, software, or a combination thereof. For example, hardware circuitry implementations may include discrete analog and / or digital components, which may be integrated, for example, as part of a printed circuit board. Alternatively or additionally, the disclosed components or modules may be implemented as application-specific integrated circuits (ASICs) and / or field-programmable gate arrays (FPGAs). Some implementations may additionally or alternatively include a digital signal processor (DSP), a special-purpose microprocessor whose architecture is optimized for the operational needs of digital signal processing associated with the functions disclosed herein. Similarly, the various components or sub-components within each module may be implemented in software, hardware, or firmware. Connections between modules and / or components within modules may be provided using any of the connection methods and media known in the art, including but not limited to communication over the Internet, wired networks, or wireless networks using appropriate protocols.

[0204] Although this document contains many specific details, these details should not be construed as limiting the scope of the claimed invention or the content that can be claimed, but rather as descriptions of features specific to particular embodiments. Some features described herein in the context of individual embodiments may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented separately in multiple embodiments, or in any suitable sub-combination. Furthermore, although features may be described above as functioning in certain combinations, and even initially claimed in this way, in some cases one or more features in a claimed combination may be removed from that combination, and a claimed combination may refer to a sub-combination or a variation of a sub-combination. Similarly, although operations are described in a specific order in the accompanying drawings, this should not be construed as requiring that these operations be performed in the specific order or sequence shown, or requiring that all operations shown be performed, in order to obtain the desired result.

[0205] Only some implementation methods and examples are described. Other implementation methods, improvements and changes can be made based on the descriptions and explanations in this disclosure.

Claims

1. A method for wireless communication, comprising: receiving, by a first network node, system information from a parent node of the first network node over a wireless link, the system information comprising an identifier, ID, of a public land mobile network, PLMN, supported by a central unit, CU, connected to the parent node; sending, by the first network node, a first message to a second network node over a wireless link, the first message indicating that the first network node supports a PLMN; and requesting, by the first network node, an Internet Protocol, IP, address from the second network node on a per public land mobile network basis, the request informing the second network node of a number of IP addresses requested, a version of the IP addresses, and a purpose of the IP addresses, and wherein the first network node is an integrated access and backhaul mobile termination, IAB-MT, node, the second network node is a central unit, CU, and the first message comprises the ID of the PLMN; wherein the IP addresses requested by the first network node correspond to one of the PLMNs supported by the first network node such that packets containing traffic belonging to the respective PLMN are encapsulated with the IP addresses, and wherein the PLMNs supported by the second network node cover the PLMNs supported by the first network node.

2. The method of claim 1, comprising: receiving, by the first network node, a second message from the second network node, the second message indicating public land mobile networks supported by the second network node.

3. The method of claim 1, wherein, the first message is a radio resource control, RRC, message.

4. The method of claim 2, wherein, the second message is a RRC message or a F1AP message.

5. An apparatus for wireless communication, comprising at least one processor configured to: receive, from a parent node of the apparatus over a wireless link, system information comprising an identifier, ID, of a public land mobile network, PLMN, supported by a central unit, CU, connected to the parent node; send, to a second network node over a wireless link, a first message, the first message indicating that the apparatus is capable of implementing a wireless access network sharing feature; and request, from the second network node, an Internet Protocol, IP, address on a per public land mobile network basis, the request informing the second network node of a number of IP addresses requested, a version of the IP addresses, and a purpose of the IP addresses; wherein the at least one processor causing the apparatus to operate as an integrated access and backhaul mobile termination, IAB-MT, node, the second network node is a central unit, CU, and the first message comprises the ID of the PLMN; wherein the IP addresses requested by the apparatus correspond to one of the PLMNs supported by the apparatus such that packets containing traffic belonging to the respective PLMN are encapsulated with the IP addresses, and wherein the PLMNs supported by the second network node cover the PLMNs supported by the apparatus.

6. The apparatus of claim 5, wherein, the at least one processor is further configured to receive, from the second network node, a second message, the second message indicating public land mobile networks supported by the second network node.

7. The apparatus of claim 5, wherein, The first message is a radio resource control, RRC, message.

8. The apparatus of claim 6, wherein, The second message is an RRC message or an F1AP message.

9. A computer storage medium having code stored thereon, the code, when executed by at least one processor, causing the at least one processor to operate as a first network node and perform a method comprising: receiving, by a first network node, system information from a parent node of the first network node over a wireless link, the system information comprising an identifier, ID, of a public land mobile network, PLMN, supported by a central unit, CU, connected to the parent node; sending, by the first network node, a first message to a second network node over a wireless link, the first message indicating that the first network node is capable of implementing a wireless access network sharing feature; and requesting, by the first network node, an internet protocol, IP, address from the second network node on a per public land mobile network basis, the request informing the second network node of a number of IP addresses requested, a version of the IP addresses, and a purpose of the IP addresses; wherein, the first network node is an integrated access and backhaul mobile termination, IAB-MT, node, the second network node is a central unit, CU, and the first message comprises the ID of the PLMN; wherein the IP address requested by the first network node corresponds to one of the PLMNs supported by the first network node such that packets belonging to the respective PLMN are encapsulated with the IP address, and wherein the PLMNs supported by the second network node cover the PLMNs supported by the first network node.

10. The computer storage medium of claim 9, wherein, The code further causes the at least one processor to receive, by the first network node, a second message from the second network node, the second message indicating public land mobile networks supported by the second network node.

11. The computer storage medium of claim 9, wherein, The first message is a radio resource control, RRC, message.

12. The computer storage medium of claim 10, wherein, The second message is an RRC message or an F1AP message.

13. A communications device comprising a processor and a transceiver, wherein, The processor is configured to read code from the memory and implement the method according to any of claims 1 to 4.

14. A computer program product comprising a computer readable program medium code stored thereon, the code, when executed by a processor, causing the processor to implement the method according to any of claims 1 to 4.

Images