IAB node device, IAB host device and transport address determination method
Patent Information
- Application Number
- CN202280094501.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2022-04-12
- Publication Date
- 2024-11-15
AI Technical Summary
During the migration process, the IAB node cannot effectively distinguish and transmit services belonging to the F1 termination point topology domain and non-F1 termination point topology domain, and lacks corresponding configuration solutions.
By receiving and sending RRC reconfiguration messages, the IP address of the IAB node is configured to distinguish the IP addresses of the F1 termination point topology domain and the non-F1 termination point topology domain, ensuring that the IAB node can correctly transmit services belonging to different topology domains.
It realizes the service transmission of IAB nodes between different topology domains, solves the problem of service differentiation during node migration and topology domain switching, and improves the flexibility and reliability of the network.
Smart Images

Figure CN118975316A_ABST
Abstract
Description
IAB node device, IAB host device, and transmission address determination method Technical Field
[0001] The embodiments of the present application relate to the field of communications. Background Art
[0002] Future seamless cellular network deployment requires highly flexible and ultra-dense new radio (NR) cell deployment. Ultra-dense networks are one of the goals of 5G, and deploying an NR network without wired backhaul is crucial to achieving these ultra-dense 5G networks. Because 5G millimeter waves reduce cell coverage, wireless self-backhaul systems require multiple hops to meet deployment requirements. 5G's high bandwidth, massive multiple-input multiple-output (MIMO), and beamforming make it easier to develop ultra-dense NR cell wireless self-backhaul systems for 5G than for LTE. To develop this multi-hop system with wireless self-backhaul, 3GPP initiated research and standardization of the Integrated Access and Backhaul (IAB) project in Rel-16.
[0003] Figure 1 is a schematic diagram of the IAB system. As shown in Figure 1, in the IAB system, access and backhaul adopt NR's Uu air interface wireless transmission. The relay node supports both access and backhaul functions. The relay node multiplexes the access link and backhaul link in the time domain, frequency domain, or spatial domain. The access link and backhaul link can use the same or different frequency bands.
[0004] In the IAB network architecture, the relay node is referred to as the IAB-node, which supports both access and backhaul functions. The last-hop access node on the network side is called the IAB-donor, which supports gNB functions and access to the IAB-node. All UE data is backhauled to the IAB-donor via one or more hops via the IAB-node.
[0005] The IAB-node's functions are divided into two parts: the gNB-DU (gNB-DU) and the UE (mobile terminal) functions. The IAB-DU implements network-side device functions, connects to downstream child IAB-nodes (child IAB-nodes), provides NR air interface access to the UE and downstream child IAB-nodes, and establishes an F1 connection with the IAB donor-CU (host centralized unit). The IAB-MT implements some terminal device functions and connects to the upstream parent IAB-node or IAB donor-DU. The IAB-MT includes physical layer, layer 2, radio resource control (RRC), and non-access stratum (NAS) layer functions, and is indirectly connected to the IAB donor-CU and the core network (CN).
[0006] In the IAB system, an IAB-node can access the network in either standalone (SA) or non-standalone (EN-DC) mode. Figure 2 shows the IAB architecture in SA mode. Figure 3 shows the IAB architecture in EN-DC mode.
[0007] Figure 4 illustrates an IAB node, its parent IAB node, and its child IAB node. As shown in Figure 4, the IAB-DU of the IAB node connects to the IAB-MT of the child node on the network side, while the IAB-MT of the IAB node connects to the IAB-DU of the parent node on the terminal side.
[0008] Figure 5 shows the F1 user plane (F1-U) protocol stack between the IAB-DU and the IAB donor-CU. Figure 6 shows the F1 control plane (F1-C) protocol stack between the IAB-DU and the IAB donor-CU. As shown in Figures 5 and 6, F1-U and F1-C are built on the transport (IP) layer between the IAB-DU and the IAB donor-CU. In these figures, the two-hop wireless backhaul and one-hop wired backhaul are used.
[0009] On the backhaul link, the transport (IP) layer is carried on the Backhaul Adaptation Protocol (BAP) sublayer. The BAP entity in the IAB node implements the routing function of the IAB system, and the IAB donor-CU provides the routing table. BAP PDUs (Protocol Data Units) are transmitted on the backhaul link's RLC (Radio Link Control) channel. The IAB donor can configure multiple RLC channels on the backhaul link to carry services of different priorities and QoS (Quality of Service). The BAP entity maps BAP PDUs to different backhaul RLC channels.
[0010] It should be noted that the above introduction to the technical background is only for the convenience of providing a clear and complete description of the technical solutions of this application and for the convenience of understanding by those skilled in the art. It cannot be considered that the above technical solutions are well known to those skilled in the art simply because these solutions are explained in the background technology part of this application.
[0011] Summary of the Invention
[0012] The inventors discovered that if all or part of an IAB node's services need to be migrated from the F1-terminating topology domain or configured to a non-F1-terminating topology domain, the routing IDs of all or part of the IAB node's services will belong to the non-F1-terminating topology domain. This means that the IAB node will need to simultaneously transmit services with routing IDs belonging to the F1-terminating topology domain and services with routing IDs belonging to the non-F1-terminating topology domain. However, there is currently no solution for enabling the IAB node to separately transmit services with routing IDs belonging to the F1-terminating topology domain and services with routing IDs belonging to the non-F1-terminating topology domain.
[0013] In order to solve at least one of the above problems, embodiments of the present application provide an IAB node device, an IAB host device, and a method for determining a transmission address.
[0014] According to one aspect of an embodiment of the present application, an integrated access and backhaul IAB node device is provided, the device comprising:
[0015] a first receiving unit configured to receive a first RRC reconfiguration message, where the first RRC reconfiguration message includes at least one IP address configuration for the IAB node;
[0016] The at least one IP address configuration includes IP address information of an F1 termination point topology domain, or includes IP address information of a non-F1 termination point topology domain.
[0017] According to another aspect of an embodiment of the present application, an integrated access and backhaul IAB host device is provided, which is applied to a first IAB host. The device includes:
[0018] A first sending unit, configured to send a first RRC reconfiguration message, wherein the first RRC reconfiguration message includes at least one IP address configuration for an IAB node; or send at least one IP address configuration of the IAB node;
[0019] The at least one IP address configuration includes IP address information of an F1 termination point topology domain, or includes IP address information of a non-F1 termination point topology domain;
[0020] The F1 connection of the IAB node is terminated at the first IAB host, and the IAB node has an RRC connection with a second IAB host.
[0021] According to another aspect of an embodiment of the present application, an integrated access and backhaul IAB host device is provided, which is applied to a second IAB host. The device includes:
[0022] a second sending unit configured to send a first RRC reconfiguration message, wherein the first RRC reconfiguration message includes at least one IP address configuration for an IAB node; or to send at least one IP address configuration for an IAB node;
[0023] The at least one IP address configuration includes IP address information of an F1 termination point topology domain, or includes IP address information of a non-F1 termination point topology domain.
[0024] The F1 connection of the IAB node is terminated at the first IAB host, and the IAB node has an RRC connection with the second IAB host.
[0025] One of the beneficial effects of the embodiments of the present application is that: the IP address of the non-F1 termination point topology domain or the IP address of the F1 termination point topology domain can be configured to the IAB node through the first RRC reconfiguration message. In this way, for the routing ID of the non-F1 termination point topology domain, the IAB node can use the IP address of the non-F1 termination point topology domain, and for the routing ID of the F1 termination point topology domain, the IP address of the F1 termination point topology domain can be used.
[0026] With reference to the description and accompanying drawings that follow, specific embodiments of the present application are disclosed in detail, indicating how the principles of the present application can be employed. It should be understood that the embodiments of the present application are not limited in scope. Within the spirit and scope of the accompanying notes, the embodiments of the present application include many variations, modifications, and equivalents.
[0027] Features described and / or illustrated with respect to one embodiment may be used in the same or similar manner in one or more other embodiments, combined with features in other embodiments, or substituted for features in other embodiments.
[0028] It should be emphasized that the term "include / comprising" when used herein refers to the presence of features, integers, steps or components, but does not exclude the presence or addition of one or more other features, integers, steps or components. BRIEF DESCRIPTION OF THE DRAWINGS
[0029] The elements and features described in one figure or one embodiment of the present application can be combined with the elements and features shown in one or more other figures or embodiments. In addition, in the accompanying drawings, similar reference numerals represent corresponding parts in several figures and can be used to indicate corresponding parts used in more than one embodiment.
[0030] The included drawings are used to provide a further understanding of the embodiments of the present application, which constitute a part of the specification, are used to illustrate the implementation methods of the present application, and together with the text description, explain the principles of the present application. Obviously, the drawings described below are only some embodiments of the present application. For those skilled in the art, other drawings can be obtained based on these drawings without inventive work. In the drawings:
[0031] FIG1 is a schematic diagram of an IAB system;
[0032] FIG2 is a schematic diagram of the IAB architecture in SA mode;
[0033] FIG3 is a schematic diagram of the IAB architecture of the EN-DC mode;
[0034] FIG4 is a schematic diagram of a parent IAB-node and a child IAB-node;
[0035] FIG5 is a schematic diagram of the F1-U protocol stack of the IAB system;
[0036] FIG6 is a schematic diagram of the F1-C protocol stack of the IAB system;
[0037] FIG7 is a schematic diagram of IAB system routing;
[0038] FIG8 is a schematic diagram of network topology adaptation;
[0039] FIG9 is a schematic diagram of an IAB device according to an embodiment of the present application;
[0040] FIG10 is a schematic diagram of a method for determining a transmission address according to an embodiment of the present application;
[0041] Figure 11 is a schematic diagram of a switching scene;
[0042] FIG12 is a schematic diagram of a dual connection scenario;
[0043] FIG13 is a schematic diagram of a dual connection scenario 2;
[0044] FIG14 is a schematic diagram of a method for determining a transmission address according to an embodiment of the present application;
[0045] FIG15 is a schematic diagram of a method for determining a transmission address according to an embodiment of the present application;
[0046] FIG16 is a schematic diagram of an IAB node device according to an embodiment of the present application;
[0047] FIG17 is a schematic diagram of an IAB host device according to an embodiment of the present application;
[0048] FIG18 is a schematic diagram of an IAB host device according to an embodiment of the present application. DETAILED DESCRIPTION
[0049] The above and other features of the present application will become apparent through the following description with reference to the accompanying drawings. In the description and drawings, specific embodiments of the present application are disclosed in detail, which show some embodiments in which the principles of the present application can be adopted. It should be understood that the present application is not limited to the described embodiments. On the contrary, the present application includes all modifications, variations and equivalents that fall within the scope of the attached notes.
[0050] In the embodiments of the present application, the terms "first", "second", etc. are used to distinguish different elements from the name, but do not indicate the spatial arrangement or temporal order of these elements, and these elements should not be limited by these terms. The term "and / or" includes any one and all combinations of one or more of the associated listed terms. The terms "comprising", "including", "having", etc. refer to the presence of the stated features, elements, components or components, but do not exclude the presence or addition of one or more other features, elements, components or components.
[0051] In the embodiments of this application, the singular forms "a," "the," etc. include plural forms and should be broadly understood to mean "a" or "a type" rather than being limited to "one." Furthermore, the term "said" should be understood to include both singular and plural forms, unless the context clearly indicates otherwise. Furthermore, the term "according to" should be understood to mean "at least in part based on...", and the term "based on" should be understood to mean "at least in part based on...", unless the context clearly indicates otherwise.
[0052] In the embodiments of the present application, the term "communication network" or "wireless communication network" may refer to a network that complies with any of the following communication standards, such as New Radio (NR), Long Term Evolution (LTE), Enhanced Long Term Evolution (LTE-A, LTE-Advanced), Wideband Code Division Multiple Access (WCDMA), High-Speed Packet Access (HSPA), etc.
[0053] Furthermore, communication between devices in the communication system may be carried out according to communication protocols of any stage, for example, including but not limited to the following communication protocols: 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G and future 5G, 6G, etc., and / or other communication protocols currently known or to be developed in the future.
[0054] In the embodiments of the present application, the term "network device" refers to, for example, a device in a communication system that connects a terminal device to the communication network and provides services to the terminal device. Network devices may include, but are not limited to, the following devices: base station (BS), access point (AP), transmission reception point (TRP), broadcast transmitter, mobile management entity (MME), gateway, server, radio network controller (RNC), base station controller (BSC), etc.
[0055] Base stations may include, but are not limited to, NodeB (NB), evolved NodeB (eNodeB or eNB), and 5G base stations (gNB), among others. They may also include remote radio heads (RRHs), remote radio units (RRUs), relays, or low-power nodes (e.g., femto, pico, etc.). The term "base station" may include some or all of their functions, and each base station may provide communication coverage for a specific geographic area. The term "cell" may refer to a base station and / or its coverage area, depending on the context in which the term is used.
[0056] In the embodiments of the present application, the term "user equipment" (UE) refers to, for example, a device that accesses a communication network through a network device and receives network services, and may also be referred to as "terminal equipment" (TE). Terminal equipment may be fixed or mobile, and may also be referred to as a mobile station (MS), terminal, user, subscriber station (SS), access terminal (AT), station, etc.
[0057] Among them, terminal devices may include but are not limited to the following devices: cellular phones, personal digital assistants (PDAs), wireless modems, wireless communication devices, handheld devices, machine-type communication devices, laptop computers, cordless phones, smart phones, smart watches, digital cameras, etc.
[0058] For another example, in scenarios such as the Internet of Things (IoT), the terminal device can also be a machine or device for monitoring or measurement, including but not limited to: machine type communication (MTC) terminal, vehicle-mounted communication terminal, device-to-device (D2D) terminal, machine-to-machine (M2M) terminal, and so on.
[0059] Signaling radio bearers SRB include SRB0, SRB1, SRB2, and SRB3, among which SRB0, SRB1, and SRB2 are directed to the MN, and SRB3 is directed to the SN. Signaling radio bearers are radio bearers used to transmit RRC and NAS messages. SRB0 transmits RRC messages using the common control channel (CCCH) logical channel. SRB1 transmits RRC messages (which may include piggybacked NAS messages) and NAS messages before SRB2 is established, using the dedicated control channel (DCCH) logical channel. SRB2 transmits NAS messages and RRC messages including log measurement messages, using the DCCH logical channel. SRB2 has a lower priority than SRB1 and can be configured by the network after access stratum (AS) security activation. SRB3 is used for specific RRC messages when the UE is in (NG)EN-DC or NR-DC, using the DCCH logical channel.
[0060] The routing function of the IAB system is implemented by the BAP layer. Each IAB node stores the routing configuration (BH routing configuration) and the RLC channel mapping configuration (BH RLC Channel Mapping Configuration). The BAP entity performs routing based on the routing configuration, RLC channel mapping configuration, and the routing ID in the BAP layer packet header. The Routing ID contains the destination BAP address and the path identifier.
[0061] The routing configuration includes the mapping relationship between the Routing ID and the next-hop node BAP address. The RLC channel mapping configuration includes the mapping relationship between the prior-hop node BAP address, the ingress link RLC channel ID, and the next-hop node BAP address and the egress link RLC channel ID.
[0062] Figure 7 is a schematic diagram of IAB system routing. As shown in Figure 7, for each data packet, the next-hop node BAP address can be found from the routing configuration using the routing ID in the packet header. The previous-hop node BAP address and the ingress link RLC channel ID are both known. Once the next-hop node BAP address is determined, the outgress link RLC channel ID can be found using the RLC channel mapping configuration based on the previous-hop node BAP address, the ingress link RLC channel ID, and the next-hop node BAP address.
[0063] The IAB-donor DU stores the routing configuration (BH routing configuration) and the downlink RLC channel mapping configuration (Downlink Traffic to BH RLC Channel Mapping Configuration). The IAB-donor DU is routed based on the routing configuration, RLC channel mapping configuration, and the Routing ID in the BAP layer packet header. The routing configuration includes the mapping between the Routing ID and the next-hop node address. The downlink RLC channel mapping configuration includes the mapping between the destination IP address, DSCP (Differentiated Services Code Point), and the next-hop node address and the egress link RLC channel ID.
[0064] For each downlink data packet arriving at the IAB-donor DU, the IAB-donor DU uses the Routing ID in the packet header to query the next-hop node address from the routing configuration. Once the next-hop node address is determined, the outbound link RLC channel ID is retrieved from the downlink RLC channel mapping configuration based on the packet's IP address and DSCP.
[0065] The access IAB node stores uplink backhaul information (BH information), including the routing ID used by the service, the uplink backhaul RLC channel ID, and the next-hop node address. Based on the uplink BH information, the access IAB node configures the routing ID in the BAP layer packet header of the uplink service and selects the BH RLC channel and next-hop node for uplink service transmission.
[0066] The above schematically illustrates the routing and BH RLC channel mapping of the IAB system. The following describes the network topology update of the IAB system. Rel-16 NR has standardized the topology adaptation process when an IAB-node moves under the same donor-CU.
[0067] Figure 8 is a schematic diagram of intra-CU topology adaptation. When an IAB-node changes its parent node (from IAB-node 1 to IAB-node 2), the donor-CU configures the IAB-node with path migration-related configurations through an RRC reconfiguration message, enabling the IAB-node to migrate the F1 transmission path.
[0068] Path migration configuration includes updating the default BH RLC channel for uplink F1-C, F1-U, and non-F1 data, updating the default BAP routing ID, and updating the IP address used to route to the Donor-DU. These path migration configurations are applied when the IAB-node connects to a new parent node. The same path migration configuration is applied to the IAB-node's child nodes.
[0069] 3GPP Rel-17 supports network topology updates and backhaul (BH) radio link failure (RLF) recovery when an IAB-node moves between different donor-CUs. The IAB-node can switch or reestablish from the parent node served by the source donor-CU (also known as the F1-terminating CU or the first donor-CU) to the parent node served by the target donor-CU (also known as the non-F1-terminating CU or the second donor-CU). All services of the IAB-node (and the services of its child nodes) need to be migrated to the topology of the non-F1-terminating CU. Rel-17 also supports topology redundancy when the IAB-node establishes dual connectivity with the non-F1-terminating CU. The transmission path of some services of the IAB-node can be migrated to the non-F1-terminating CU topology.
[0070] After an IAB-node switches from donor-CU 1 (F1-terminating CU) to donor-CU 2 (non-F1-terminating CU) after handover / RLF recovery, or after establishing an RRC connection with donor-CU 2, only the IAB-MT's RRC connection remains with donor-CU 2, while the F1 interface still terminates at donor-CU 1. In this case, the IAB-node is also called a boundary node. The RRC connection and F1 interface of the subnodes it serves still belong to donor-CU 1. Therefore, the routing ID, BH RLC channel, and next-hop BAP address of the subnode services still belong to the F1-terminating topology domain.
[0071] The routing IDs of all or some services on a boundary node may belong to the non-F1-terminating topology domain. This means that the boundary node must simultaneously transmit services with routing IDs belonging to the F1-terminating topology domain and services with routing IDs belonging to the non-F1-terminating topology domain. However, there is currently no solution for enabling the boundary node to separately transmit services with routing IDs belonging to the F1-terminating topology domain and services with routing IDs belonging to the non-F1-terminating topology domain.
[0072] In the embodiments of this application, unless otherwise specified, an IAB node device includes a migration node or its child nodes. Furthermore, "resources established in the donor-CU's topological domain for servicing the IAB node's services" may also be referred to as "migrating the IAB node's services to the donor-CU's topological domain," etc., and this application is not limited to these expressions. The embodiments of this application are further described below.
[0073] Embodiments of the first aspect
[0074] An embodiment of the present application provides a method for determining a transmission address, which is described from the perspective of an IAB node device.
[0075] FIG10 is a schematic diagram of a method for determining a transmission address according to an embodiment of the present application. As shown in FIG10 , the method includes:
[0076] 1001. The IAB node receives a first RRC reconfiguration message, which includes at least one IP address configuration for the IAB node; the at least one IP address configuration includes IP address information of an F1 termination point topology domain, or includes IP address information of a non-F1 termination point topology domain.
[0077] It is worth noting that FIG10 above is merely a schematic illustration of an embodiment of the present application, and the present application is not limited thereto. For example, the execution order of the various operations may be appropriately adjusted, and other operations may be added or some operations may be reduced. Those skilled in the art may make appropriate modifications based on the above description, and are not limited to the description of FIG10 above.
[0078] Since the routing ID for the non-F1-terminating topology domain, the boundary node needs to use the IP address of the non-F1-terminating topology domain, that is, the IP address of the donor-DU anchored in the non-F1-terminating topology domain; for the routing ID of the F1-terminating topology domain, the IP address of the F1-terminating topology domain needs to be used, that is, the IP address of the donor-DU anchored in the F1-terminating topology domain. It can be seen from the above embodiment that the IP address of the non-F1 termination point topology domain or the IP address of the F1 termination point topology domain can be configured to the IAB node through the first RRC reconfiguration message. In this way, the boundary node can transmit services whose routing ID belongs to the F1-terminating topology domain and services whose routing ID belongs to the non-F1-terminating topology domain respectively.
[0079] In some embodiments, the IAB node includes a migration node or its child nodes. For example, when the IAB node is a migration node (also known as a border node), the F1 connection of the IAB node terminates at a first IAB host (e.g., a first IAB donor-CU), and the IAB node has an RRC connection with a second IAB host (e.g., a second IAB donor-CU). For example, the IAB-MT of the IAB node maintains an RRC connection with the second IAB host. Hereinafter, the first IAB host is also referred to as an F1 termination point host (e.g., an F1 termination point donor-CU), and the second IAB host is also referred to as a non-F1 termination point host (e.g., a non-F1 termination point donor-CU). The F1 termination point host refers to an IAB host that terminates the F1 interface of the border IAB node and its child IAB nodes, i.e., the first IAB host. A non-F1 termination point host refers to a host with host functionality that does not terminate the F1 interface of the border IAB node and its child IAB nodes, such as the second IAB host.
[0080] In some embodiments, the IP address refers to the IP address anchored to the donor-DU configured for the IAB node. The at least one IP address configuration in the first RRC reconfiguration message may be an IP address configuration of at least two donor-DUs, or at least one IP address configuration of a donor-DU. Each IP address configuration may include an IP address index and a corresponding IP address. The embodiments of the present application are not limited to this.
[0081] In the embodiment of the present application, "IP address anchored to IAB donor-DU" can be understood as "IP address assigned by donor-DU" or "TNL address (TNL address(es) that is (are) routable via the IAB-donor-DU"". The above terms can be interchangeable with each other. The present application is not limited thereto. For example, the IP address of the donor-DU in the non-F1 termination point topology domain configured for the IAB node refers to the transport network layer (TNL) address that is (are) routable via the donor-DU in the non-F1 termination point topology domain configured for the IAB node.
[0082] In some embodiments, the method may further include:
[0083] 1002: The IAB node determines that the IP address configuration includes the IP address information of the F1 termination point topology domain or the IP address information of the non-F1 termination point topology domain.
[0084] In some embodiments, it may be implicitly indicated whether the configured IP address belongs to a non-F1 termination point topology domain. In 1002, the IAB node may determine, based on the host providing the IP address information, whether the IP address configuration includes IP address information of the F1 termination point topology domain or IP address information of the non-F1 termination point topology domain. For example, if the host providing the IP address information is an F1 termination point host, the IP address configuration may be determined to include IP address information of the F1 termination point topology domain. If the host providing the IP address information is a non-F1 termination point host, the IP address configuration may be determined to include IP address information of the non-F1 termination point topology domain.
[0085] In some embodiments, it is possible to explicitly indicate (for example, explicitly indicate according to the first indication information) whether the configured IP address belongs to a non-F1 termination point topology domain. In 1002, the IAB node can determine, based on the first indication information, that the IP address configuration contains IP address information of the F1 termination point topology domain or IP address information of the non-F1 termination point topology domain. For example, the first indication information is used to indicate that the IP address configuration contains IP address information of the non-F1 termination point topology domain. When the IAB node receives the first indication information, it determines that the IP address configuration contains IP address information of the non-F1 termination point topology domain. When the first indication information is not received, it determines that the IP address configuration contains IP address information of the F1 termination point topology domain. However, the embodiments of the present application are not limited to this. The carrying method of the first indication information and specific examples will be described later. As can be seen from the above embodiments, through implicit or explicit indications, the IAB node can distinguish whether the configured IP address is a non-F1 termination point topology domain or an F1 termination point topology domain.
[0086] The following describes implicit and explicit instructions in combination with different scenarios.
[0087] (1) Switching scenes
[0088] In some embodiments, FIG11 is a schematic diagram of a handover scenario. As shown in FIG11 , in the handover scenario, all services of the border node are migrated to a non-F1 termination point topology domain. The F1 termination point host is the source host for the IAB node handover, and the non-F1 termination point host is the target host for the IAB node handover. The IP address of the non-F1 termination point topology domain can be configured during the handover process, or after the handover is complete. During the handover process, the first RRC reconfiguration message is a handover command RRC message generated by a second IAB host and forwarded by the first IAB host. After the handover process, the first RRC reconfiguration message is an RRC message sent directly by the second IAB host to the IAB node. The first RRC reconfiguration message includes at least one IP address configuration for the IAB node. The at least one IP address configuration includes IP address information for the non-F1 termination point topology domain. The IP address of the non-F1 termination point topology domain is the IP address anchored to donor-DU2. The at least one IP address configuration may be carried by a handover command RRC message, for example, the at least one IP address configuration carried in the RRC reconfiguration information in the reconfigurationWithSync information field in the primary cell group information. The IAB node may determine that the at least one IP address configuration configured by the handover command RRC message includes IP address information of a non-F1 termination point topology domain, or the IAB node may determine that the at least one IP address configuration in the RRC message sent by the target host includes IP address information of a non-F1 termination point topology domain.
[0089] (i) Implicit indication
[0090] For example, during the switching process, since the switching command RRC message is generated by the target host (that is, the host providing the IP address information is the target host), and the target host is a non-F1 termination point, the IAB node can determine that at least one IP address configuration carried by the switching command RRC message is the IP address information of the non-F1 termination point topology domain after receiving the switching command RRC message.
[0091] For example, after the handover is completed, the target host may directly send an RRC message to the IAB node. After receiving the RRC message, the IAB node may determine that at least one IP address configuration carried by the RRC message is IP address information of a non-F1 termination point topology domain.
[0092] (ii) Explicit Instructions
[0093] For example, during the switching process, when the target host generates a switching command RRC message, it can introduce a new information element, namely, the first indication information non-F1-terminating. Therefore, after the IAB node receives the switching command RRC message, that is, when the switching command RRC message contains the first indication information, it determines that at least one IP address configuration carried by the switching command RRC message is the IP address information of the non-F1 termination point topology domain.
[0094] For example, after the handover is completed, the target host can send an RRC message directly to the IAB node, and can introduce a new information element therein, namely, the first indication information non-F1-terminating-Indication. After receiving the RRC message, that is, when the handover command RRC message includes the first indication information, the IAB node can determine that at least one IP address configuration carried by the RRC message is the IP address information of the non-F1 termination point topology domain.
[0095] In some embodiments, the first indication information may be included in a newly added information element of the RRC reconfiguration message, or included in an IP address configuration list information element of the RRC reconfiguration message, or included in an IP address configuration information element of the RRC reconfiguration message, or included in an IP address index information element of the RRC reconfiguration message. Examples are given below to illustrate each of these.
[0096] 1) Add a new information element non-F1-terminating-Indication to the first RRC reconfiguration message to indicate that at least one IP address configuration carried by the RRC message is IP address information of a non-F1 termination point topology domain, or to indicate that the at least one IP address configuration is generated by a non-F1 termination point host.
[0097] The first RRC reconfiguration message may be represented as follows using the Abstract Syntax Notation (ASN.1) data format:
[0098]
[0099] 2) Add a new information element non-F1-terminating-Indication to the IP address configuration list information element IAB-IP-AddressConfigurationList of the first RRC reconfiguration message to indicate that at least one IP address configuration carried by the RRC message is IP address information of a non-F1 termination point topology domain, or to indicate that the at least one IP address configuration is generated by a non-F1 termination point host.
[0100] The IP address configuration list information element can be expressed in the abstract syntax notation ASN.1 data format as follows:
[0101]
[0102]
[0103] Through the indication methods in 1) and 2) above, all configured IP address information can be uniformly indicated as being IP address information of a non-F1 termination point topology domain, thereby saving information bits.
[0104] 3) Add a new information element non-F1-terminating-Indication to the IP address configuration information element IAB-IP-AddressConfiguration of the first RRC reconfiguration message to indicate that a certain IP address configuration carried by the RRC message is the IP address information of a non-F1 termination point topology domain, or to indicate that the IP address configuration is generated by a non-F1 termination point host.
[0105] The IP address configuration information element can be expressed in the abstract syntax notation ASN.1 data format as follows:
[0106]
[0107] 4) Add a new information element non-F1-terminating-Indication to the IP address index information element IAB-IP-AddressIndexInfo of the first RRC reconfiguration message to indicate that a certain IP address configuration carried by the RRC message is the IP address information of a non-F1 termination point topology domain, or to indicate that the IP address configuration is generated by a non-F1 termination point host.
[0108] The IP address index information element can be expressed in the abstract syntax notation ASN.1 data format as follows:
[0109]
[0110] Through the indication methods in 3) and 4) above, the granularity of indication can be targeted at the IP address information of each configuration, and the indication method is more flexible.
[0111] (2) For dual connection scenario 1
[0112] In some embodiments, FIG12 is a schematic diagram of a dual-connection scenario 1. As shown in FIG12 , in the dual-connection scenario 1, the first IAB host (F1 termination point host) is the primary node MN of the IAB node, and the second IAB host (non-F1 termination point host) is the secondary node SN of the IAB node. After establishing the dual connection, part of the services of the border node can be migrated to the non-F1 termination point topology domain, and part of the services remain in the F1 termination point host topology domain. The IP address of the non-F1 termination point topology domain refers to the IP address anchored to donor-DU2. The IP address of the non-F1 termination point topology domain can be configured during the dual connection establishment process, or the IP address of the non-F1 termination point topology domain or the IP address of the F1 termination point topology domain can be configured after the dual connection establishment is completed. In the case of implicit indication, the IAB node may determine that the at least one IP address configuration in the RRC message received through SRB3 contains IP address information of a non-F1 termination point topology domain, or may determine that the at least one IP address configuration in the secondary cell group configuration information received through SRB1 contains IP address information of a non-F1 termination point topology domain, or may determine that the at least one IP address configuration in the RRC message received through SRB1 contains IP address information of an F1 termination point topology domain. In the case of explicit indication, the IAB node may determine that the at least one IP address configuration in the secondary cell group configuration information received through SRB1 contains IP address information of a non-F1 termination point topology domain when receiving the first indication information, and determine that the at least one IP address configuration in the secondary cell group configuration information received through SRB1 contains IP address information of an F1 termination point topology domain when not receiving the first indication information. The following explains the different cases.
[0113] In some embodiments, an IP address of a non-F1 termination point topology domain is configured during the process of adding a secondary cell group. The first RRC reconfiguration message is an RRC reconfiguration message carried by the secondary cell group configuration (mrdc-SecondaryCellGroupConfig field) of the RRC reconfiguration message, and is completely generated by the second host and carried by a second RRC reconfiguration message sent by the first IAB host. The IAB node receives the second RRC reconfiguration message sent by the first IAB host via SRB1. The first RRC reconfiguration message includes at least one IP address configuration for the IAB node, and the at least one IP address configuration includes IP address information of the non-F1 termination point topology domain. The IP address of the non-F1 termination point topology domain refers to an IP address anchored to donor-DU2.
[0114] The ASN.1 structure of the RRC reconfiguration message is shown below, which includes the secondary cell group configuration (mrdc-SecondaryCellGroupConfig field).
[0115]
[0116]
[0117] (i) Implicit indication
[0118] For example, the SN generates a secondary cell group configuration RRC message and sends it to the MN in a secondary cell group addition response message. After receiving the secondary cell group configuration RRC message sent by the SN, the MN generates a second RRC reconfiguration message, places the secondary cell group configuration RRC message in the mrdc-SecondaryCellGroupConfig field of the second RRC reconfiguration message, and forwards it to the IAB node. Therefore, after receiving the second RRC reconfiguration message through SRB1, the IAB node can obtain the RRC reconfiguration message contained in the mrdc-SecondaryCellGroupConfig field carried therein. The IAB node knows that the RRC reconfiguration message contained in the mrdc-SecondaryCellGroupConfig field is generated by the SN (that is, at least one IP address configuration is provided by the SN), and the SN is a non-F1 termination point. Therefore, the IAB node determines that the at least one IP address configuration carried by the RRC reconfiguration message contained in the mrdc-SecondaryCellGroupConfig field is the IP address information of the non-F1 termination point topology domain. That is, the IAB node determines that at least one IP address configuration in the RRC reconfiguration message included in the mrdc-SecondaryCellGroupConfig field received through SRB1 includes IP address information of a non-F1 termination point topology domain.
[0119] (ii) Explicit Instructions
[0120] For example, when the SN generates a secondary cell group configuration RRC message, it can introduce a new information element therein, namely the first indication information non-F1-terminating, and send it to the MN in the secondary cell group addition response message. After receiving the secondary cell group configuration RRC message sent by the SN, the MN generates a second RRC reconfiguration message, places the secondary cell group configuration RRC message in the mrdc-SecondaryCellGroupConfig field in the second RRC reconfiguration message, and forwards it to the IAB node. Therefore, after receiving the second RRC reconfiguration message through SRB1, the IAB node can obtain the RRC reconfiguration message of the mrdc-SecondaryCellGroupConfig field carried therein and the first indication information contained therein, so the IAB node determines that at least one IP address configuration carried by the RRC reconfiguration message of the mrdc-SecondaryCellGroupConfig field is the IP address information of the non-F1 termination point topology domain. The example of introducing the first indication information in the secondary cell group configuration RRC message is similar to the aforementioned 1)-4) and will not be repeated here.
[0121] For example, the SN generates a secondary cell group configuration RRC message and sends it to the MN in a secondary cell group add response message. After receiving the secondary cell group configuration RRC message sent by the SN, the MN generates a second RRC reconfiguration message and can introduce a new information element, namely, the first indication information non-F1-terminating, into the second RRC reconfiguration message. The secondary cell group configuration RRC message is placed in the second RRC reconfiguration message and forwarded to the IAB node. Therefore, after receiving the second RRC reconfiguration message through SRB1, the IAB node can obtain the RRC reconfiguration message of the mrdc-SecondaryCellGroupConfig field and the first indication information carried therein. Therefore, the IAB node determines that at least one IP address configuration carried by the RRC reconfiguration message of the mrdc-SecondaryCellGroupConfig field is IP address information of a non-F1 termination point topology domain. The example of the second RRC reconfiguration message introducing the first indication information is similar to the above 1), except that when generating the second RRC reconfiguration message, its own information element iab-IP-AddressConfigurationList-r16 related to the IP address configuration may not be included.
[0122] In some embodiments, the IP address of the non-F1 termination point topology domain can be configured (modified) after the dual connectivity is established. The first RRC reconfiguration message is sent directly to the IAB node by the second IAB host; the IAB node receives the first RRC reconfiguration message sent by the second IAB host via SRB3. The first RRC reconfiguration message includes at least one IP address configuration for the IAB node, and the at least one IP address configuration includes IP address information of the non-F1 termination point topology domain. The IP address of the non-F1 termination point topology domain refers to the IP address anchored to donor-DU2.
[0123] (i) Implicit indication
[0124] For example, the IAB node receives the first RRC reconfiguration message via SRB3. The IAB node knows that the first RRC reconfiguration message is generated by the SN (i.e., at least one IP address configuration is provided by the SN), and the SN is a non-F1 termination point. Therefore, the IAB node determines that the at least one IP address configuration carried by the first RRC reconfiguration message is IP address information of a non-F1 termination point topology domain. In other words, the IAB node determines that at least one IP address configuration in the first RRC reconfiguration message received via SRB1 includes IP address information of a non-F1 termination point topology domain.
[0125] (ii) Explicit Instructions
[0126] For example, when the SN generates the first RRC reconfiguration message, it can introduce a new information element, namely, the first indication information non-F1-terminating, into the message. The IAB node receives the first RRC reconfiguration message and the first indication information therein through SRB3. Therefore, the IAB node determines that at least one IP address configuration carried by the first RRC reconfiguration message is IP address information of a non-F1 termination point topology domain. The example of introducing the first indication information into the first RRC reconfiguration message is similar to the aforementioned 1)-4) and will not be repeated here.
[0127] In some embodiments, after the dual connection is established, the IP address of the non-F1 termination point topology domain can be configured (modified) in the process of modifying the secondary cell group. The first RRC reconfiguration message is an RRC reconfiguration message contained in the mrdc-SecondaryCellGroupConfig field and is carried by the second RRC reconfiguration message sent by the first IAB host; the IAB node receives the second RRC reconfiguration message sent by the first IAB host through SRB1. The first RRC reconfiguration message includes at least one IP address configuration for the IAB node, and the at least one IP address configuration includes IP address information of the non-F1 termination point topology domain. The IP address of the non-F1 termination point topology domain refers to the IP address anchored to donor-DU2.
[0128] (i) Implicit indication
[0129] For example, the SN generates a secondary cell group configuration RRC message and places it in a secondary cell group modification request message and sends it to the MN. After receiving the secondary cell group configuration RRC message sent by the SN, the MN generates a second RRC reconfiguration message and places the secondary cell group configuration RRC message in the mrdc-SecondaryCellGroupConfig field in the second RRC reconfiguration message and forwards it to the IAB node. Therefore, after receiving the second RRC reconfiguration message through SRB1, the IAB node can obtain the RRC reconfiguration message contained in the mrdc-SecondaryCellGroupConfig field carried therein. The IAB node knows that the RRC reconfiguration message contained in the mrdc-SecondaryCellGroupConfig field is generated by the SN (that is, at least one IP address configuration is provided by the SN), and the SN is a non-F1 termination point. Therefore, the IAB node determines that the at least one IP address configuration carried by the secondary cell group configuration RRC message is the IP address information of the non-F1 termination point topology domain. That is, the IAB node determines that at least one IP address configuration in the RRC reconfiguration message included in the mrdc-SecondaryCellGroupConfig field received through SRB1 includes IP address information of a non-F1 termination point topology domain.
[0130] (ii) Explicit Instructions
[0131] For example, when the SN generates a secondary cell group configuration RRC message, it can introduce a new information element therein, namely the first indication information non-F1-terminating, and put it in the secondary cell group modification request message and send it to the MN. After receiving the secondary cell group configuration RRC message sent by the SN, the MN generates a second RRC reconfiguration message, puts the secondary cell group configuration RRC message in the mrdc-SecondaryCellGroupConfig field in the second RRC reconfiguration message and forwards it to the IAB node. Therefore, after receiving the second RRC reconfiguration message through SRB1, the IAB node can obtain the RRC reconfiguration message contained in the mrdc-SecondaryCellGroupConfig field carried therein and the first indication information carried therein. Therefore, the IAB node determines that at least one IP address configuration carried by the RRC reconfiguration message contained in the mrdc-SecondaryCellGroupConfig field is the IP address information of the non-F1 termination point topology domain. The example of introducing the first indication information in the secondary cell group configuration RRC message is similar to the above 1)-4) and will not be repeated here.
[0132] For example, the SN generates a secondary cell group configuration RRC message and places it in a secondary cell group modification request message and sends it to the MN. After receiving the secondary cell group configuration RRC message sent by the SN, the MN generates a second RRC reconfiguration message and can introduce a new information element in the second RRC reconfiguration message, namely the first indication information non-F1-terminating, and places the secondary cell group configuration RRC message in the mrdc-SecondaryCellGroupConfig field of the second RRC reconfiguration message and forwards it to the IAB node. Therefore, after receiving the second RRC reconfiguration message through SRB1, the IAB node can obtain the RRC reconfiguration message and the first indication information contained in the mrdc-SecondaryCellGroupConfig field therein, so the IAB node determines that at least one IP address configuration carried by the RRC reconfiguration message contained in the mrdc-SecondaryCellGroupConfig field is the IP address information of the non-F1 termination point topology domain. The example of introducing the first indication information in the second RRC reconfiguration message is similar to the above 1), except that when generating the second RRC reconfiguration message, its own information element iab-IP-AddressConfigurationList-r16 related to the IP address configuration may not be included.
[0133] In some embodiments, after the dual connectivity is established, the IP address of the non-F1 termination point topology domain may be reconfigured during the IAB transport migration management process and sent by the MN to the IAB node.
[0134] (i) Implicit indication
[0135] The first RRC reconfiguration message is an RRC reconfiguration message contained in the mrdc-SecondaryCellGroupConfig field. Since the IAB transport migration management process does not support the SN generating a secondary cell group configuration RRC message, the first RRC reconfiguration message is generated by the first IAB host instead of the second IAB host and is carried by the second RRC reconfiguration message sent by the first IAB host. The IAB node receives the second RRC reconfiguration message sent by the first IAB host through SRB1. The first RRC reconfiguration message includes at least one IP address configuration for the IAB node, and the at least one IP address configuration includes IP address information of a non-F1 termination point topology domain. The IP address of the non-F1 termination point topology domain refers to an IP address anchored to donor-DU2.
[0136] For example, the SN provides at least one IP address configuration and sends it to the MN in the IAB transmission migration management response message. After receiving the at least one IP address configuration, the MN generates a first RRC reconfiguration message on behalf of the second IAB host, and places the first RRC reconfiguration message in the second RRC reconfiguration message and forwards it to the IAB node. Therefore, after receiving the second RRC reconfiguration message through SRB1, the IAB node can obtain the RRC reconfiguration message contained in the mrdc-SecondaryCellGroupConfig field carried therein. The IAB node knows that at least one IP address configuration in the RRC reconfiguration message contained in the mrdc-SecondaryCellGroupConfig field is provided by the SN, and the SN is a non-F1 termination point. Therefore, the IAB node determines that the at least one IP address configuration carried by the secondary cell group configuration RRC message is the IP address information of the non-F1 termination point topology domain. That is, the IAB node determines that at least one IP address configuration in the RRC reconfiguration message contained in the mrdc-SecondaryCellGroupConfig field received through SRB1 contains the IP address information of the non-F1 termination point topology domain.
[0137] (ii) Explicit Instructions
[0138] The SN provides at least one IP address configuration to the MN, where the first RRC reconfiguration message is generated by the MN. The IAB node receives the second RRC reconfiguration message sent by the first IAB host via SRB1. The first RRC reconfiguration message includes at least one IP address configuration for the IAB node, where the at least one IP address configuration includes IP address information of a non-F1 termination point topology domain, where the IP address of the non-F1 termination point topology domain is an IP address anchored to donor-DU2.
[0139] For example, the SN provides at least one IP address configuration and sends it to the MN in an IAB transmission migration management response message. After receiving the at least one IP address configuration, the MN generates a first RRC reconfiguration message, in which a new information element can be introduced, namely, the first indication information non-F1-terminating. The first RRC reconfiguration message is sent to the IAB node. Therefore, after receiving the first RRC reconfiguration message through SRB1, the IAB node can obtain the at least one IP address information and the first indication information carried therein. Therefore, the IAB node determines that the at least one IP address configuration carried by the first RRC reconfiguration message is the IP address information of the non-F1 termination point topology domain. The example of the first RRC reconfiguration message introducing the first indication information is similar to the above 1)-4) and will not be repeated here.
[0140] In some embodiments, after dual connectivity is established, the IP address of the non-F1 termination point topology domain can be reconfigured during the IAB transport migration management process. The first RRC reconfiguration message is generated by the SN and sent directly by the second IAB host to the IAB node. The IAB node receives the first RRC reconfiguration message sent by the second IAB host via SRB3. The first RRC reconfiguration message includes at least one IP address configuration for the IAB node, and the at least one IP address configuration includes IP address information of the non-F1 termination point topology domain. The IP address of the non-F1 termination point topology domain is an IP address anchored to donor-DU2.
[0141] (i) Implicit indication
[0142] For example, the IAB node receives the first RRC reconfiguration message via SRB3. The IAB node knows that the first RRC reconfiguration message is generated by the SN (i.e., at least one IP address configuration is provided by the SN), and the SN is a non-F1 termination point. Therefore, the IAB node determines that the at least one IP address configuration carried by the first RRC reconfiguration message is IP address information of a non-F1 termination point topology domain. In other words, the IAB node determines that at least one IP address configuration in the first RRC reconfiguration message received via SRB1 includes IP address information of a non-F1 termination point topology domain.
[0143] (ii) Explicit Instructions
[0144] For example, when the SN generates the first RRC reconfiguration message, it may introduce a new information element, namely, first indication information non-F1-terminating, therein. The IAB node receives the first RRC reconfiguration message and the first indication information therein via SRB3. Therefore, the IAB node determines that at least one IP address configuration carried by the first RRC reconfiguration message is IP address information of a non-F1 termination point topology domain. The first RR example is similar to the aforementioned 1)-4) and will not be repeated here.
[0145] In some embodiments, after the dual connectivity is established, the IP address of the F1 termination point topology domain can be configured (modified) during the process of modifying the secondary cell group. The first RRC reconfiguration message is generated by the MN and sent directly to the IAB node by the first IAB host; the IAB node receives the first RRC reconfiguration message sent by the first IAB host through SRB1. The first RRC reconfiguration message includes at least one IP address configuration for the IAB node, and the at least one IP address configuration includes IP address information of the F1 termination point topology domain. The IP address of the F1 termination point topology domain refers to the IP address anchored to donor-DU1.
[0146] (i) Implicit indication
[0147] For example, the IAB node receives the first RRC reconfiguration message via SRB1. The IAB node knows that the first RRC reconfiguration message is generated by the MN (i.e., the at least one IP address configuration is provided by the MN), and the MN is the F1 termination point. Therefore, the IAB node determines that the at least one IP address configuration carried by the first RRC reconfiguration message is IP address information of the F1 termination point topology domain. In other words, the IAB node determines that the at least one IP address configuration in the first RRC reconfiguration message received via SRB1 includes IP address information of the F1 termination point topology domain.
[0148] (ii) Explicit Instructions
[0149] For example, when the MN generates the first RRC reconfiguration message, it does not need to introduce a new information element, that is, the first indication information non-F1-terminating. The IAB node receives the first RRC reconfiguration message through SRB1. Since it does not contain the first indication information, that is, the IAB node does not receive the first indication information, the IAB node determines that at least one IP address configuration carried by the first RRC reconfiguration message is the IP address information of the F1 termination point topology domain.
[0150] (3) For dual connection scenario 2
[0151] In some embodiments, FIG13 is a schematic diagram of a dual-connection scenario 2. As shown in FIG13 , in dual-connection scenario 2, the first IAB host (the F1 termination point host) is the primary node SN of the IAB node, and the second IAB host (the non-F1 termination point host) is the secondary node MN of the IAB node. After establishing dual connectivity, some services of the border node can be migrated to the non-F1 termination point topology domain, while some services remain in the F1 termination point host topology domain. The IP address of the non-F1 termination point topology domain refers to the IP address anchored to donor-DU1, and the IP address of the F1 termination point topology domain refers to the IP address anchored to donor-DU2. Since the F1 connection is completed after the dual connectivity is established, unlike dual connectivity scenario 1, the IP address of the non-F1 termination point topology domain cannot be configured during the dual connectivity establishment process. The IP address of the non-F1 termination point topology domain or the IP address of the F1 termination point topology domain can only be configured after the dual connectivity is established. In the case of implicit indication, the IAB node may determine that the at least one IP address configuration in the RRC message received through SRB1 contains IP address information of a non-F1 termination point topology domain, or may determine that the at least one IP address configuration in the secondary cell group configuration information received through SRB1 contains IP address information of an F1 termination point topology domain, or may determine that the at least one IP address configuration in the RRC message received through SRB3 contains IP address information of an F1 termination point topology domain. In the case of explicit indication, the IAB node may determine that the at least one IP address configuration in the first RRC reconfiguration message contains IP address information of a non-F1 termination point topology domain when receiving the first indication information, and determine that the at least one IP address configuration in the first RRC reconfiguration message contains IP address information of an F1 termination point topology domain when not receiving the first indication information. The following explains the different cases.
[0152] In some embodiments, the IP address of the non-F1 termination point topology domain can be configured (modified) after the dual connectivity is established. The first RRC reconfiguration message is sent by the second IAB host to the IAB node; the IAB node receives the first RRC reconfiguration message sent by the second IAB host through SRB1. The first RRC reconfiguration message includes at least one IP address configuration for the IAB node, and the at least one IP address configuration includes IP address information of the non-F1 termination point topology domain. The IP address of the non-F1 termination point topology domain refers to the IP address anchored to donor-DU1.
[0153] (i) Implicit indication
[0154] For example, the IAB node receives the first RRC reconfiguration message via SRB1. The IAB node knows that the first RRC reconfiguration message is generated by the MN (i.e., the at least one IP address configuration is provided by the MN), and the MN is a non-F1 termination point. Therefore, the IAB node determines that the at least one IP address configuration carried by the first RRC reconfiguration message is IP address information of a non-F1 termination point topology domain. In other words, the IAB node determines that the at least one IP address configuration in the first RRC reconfiguration message received via SRB1 includes IP address information of a non-F1 termination point topology domain.
[0155] (ii) Explicit Instructions
[0156] For example, when the MN generates the first RRC reconfiguration message, a new information element, namely, first indication information non-F1-terminating, may be introduced therein. The IAB node receives the first RRC reconfiguration message and the first indication information therein through SRB1. Therefore, the IAB node determines that at least one IP address configuration carried by the first RRC reconfiguration message is IP address information of a non-F1 termination point topology domain. The example of introducing the first indication information into the first RRC reconfiguration message is similar to the aforementioned 1)-4) and will not be repeated here.
[0157] In some embodiments, after the dual connectivity is established, the IP address of the F1 termination point topology domain can be configured (modified) during the process of modifying the secondary cell group. The first RRC reconfiguration message is generated by the first IAB host; the IAB node receives the first RRC reconfiguration message sent by the first IAB host via SRB3. The first RRC reconfiguration message includes at least one IP address configuration for the IAB node, and the at least one IP address configuration includes IP address information of the F1 termination point topology domain. The IP address of the F1 termination point topology domain refers to the IP address anchored to donor-DU2.
[0158] (i) Implicit indication
[0159] For example, the IAB node receives the first RRC reconfiguration message via SRB3. The IAB node knows that the first RRC reconfiguration message is generated by the SN (i.e., at least one IP address configuration is provided by the SN), and the SN is the F1 termination point. Therefore, the IAB node determines that the at least one IP address configuration carried by the first RRC reconfiguration message is IP address information of the F1 termination point topology domain. In other words, the IAB node determines that the at least one IP address configuration in the first RRC reconfiguration message received via SRB3 includes IP address information of the F1 termination point topology domain.
[0160] (ii) Explicit Instructions
[0161] For example, when the SN generates the first RRC reconfiguration message, it does not need to introduce a new information element, that is, the first indication information non-F1-terminating. The IAB node receives the first RRC reconfiguration message through SRB3. Since the IAB node does not receive the first indication information, it determines that at least one IP address configuration in the first RRC reconfiguration message received through SRB3 contains the IP address information of the F1 termination point topology domain.
[0162] In some embodiments, after the dual connection is established, the IP address of the F1 termination point topology domain can be configured (modified) in the process of modifying the secondary cell group. The first RRC reconfiguration message is an RRC reconfiguration message contained in the mrdc-SecondaryCellGroupConfig field of the RRC reconfiguration message, which is completely generated by the first IAB host and carried by the third RRC reconfiguration message sent by the second IAB host; the IAB node receives the third RRC reconfiguration message sent by the second IAB host through SRB1. The first RRC reconfiguration message includes at least one IP address configuration for the IAB node, and the at least one IP address configuration includes IP address information of the F1 termination point topology domain. The IP address of the F1 termination point topology domain refers to the IP address anchored to donor-DU2.
[0163] (i) Implicit indication
[0164] For example, the SN generates a secondary cell group configuration RRC message and places it in a secondary cell group modification request message and sends it to the MN. After receiving the secondary cell group configuration RRC message sent by the SN, the MN generates a third RRC reconfiguration message, places the secondary cell group configuration RRC message in the mrdc-SecondaryCellGroupConfig field in the third RRC reconfiguration message and forwards it to the IAB node. Therefore, after receiving the third RRC reconfiguration message through SRB1, the IAB node can obtain the RRC reconfiguration message contained in the mrdc-SecondaryCellGroupConfig field carried therein. The IAB node knows that the RRC reconfiguration message contained in the mrdc-SecondaryCellGroupConfig field is generated by the SN (that is, at least one IP address configuration is provided by the SN), and the SN is the F1 termination point. Therefore, the IAB node determines that the at least one IP address configuration carried by the RRC reconfiguration message contained in the mrdc-SecondaryCellGroupConfig field is the IP address information of the F1 termination point topology domain. That is, the IAB node determines that at least one IP address configuration in the secondary cell group configuration RRC message received through SRB1 includes IP address information of the F1 termination point topology domain.
[0165] (ii) Explicit Instructions
[0166] For example, when the SN generates a secondary cell group configuration RRC message, it does not need to introduce a new information element, namely, the first indication information non-F1-terminating, and places the secondary cell group configuration RRC message in a secondary cell group modification request message and sends it to the MN. After receiving the secondary cell group configuration RRC message sent by the SN, the MN generates a third RRC reconfiguration message, places the secondary cell group configuration RRC message in the mrdc-SecondaryCellGroupConfig field of the third RRC reconfiguration message and forwards it to the IAB node. Therefore, after receiving the third RRC reconfiguration message through SRB1, the IAB node can obtain the RRC reconfiguration message contained in the mrdc-SecondaryCellGroupConfig field carried therein. However, since neither the first RRC reconfiguration message nor the third RRC reconfiguration message contains the first indication information, that is, the IAB node does not receive the first indication information, the IAB node determines that the at least one IP address configuration carried by the secondary cell group configuration RRC message is the IP address information of the F1 termination point topology domain.
[0167] In some embodiments, after dual connectivity is established, the IP address of the non-F1 termination point topology domain can be configured (modified) during the IAB transport migration management process. The first RRC reconfiguration message is generated by the second IAB host and sent by the second IAB host to the IAB node. The IAB node receives the first RRC reconfiguration message sent by the second IAB host via SRB1. The first RRC reconfiguration message includes at least one IP address configuration for the IAB node, and the at least one IP address configuration includes IP address information of the non-F1 termination point topology domain. The IP address of the non-F1 termination point topology domain refers to the IP address anchored to donor-DU1.
[0168] (i) Implicit indication
[0169] For example, the SN sends an IAB transmission migration management request message to the MN. After receiving the request message, the MN (the second IAB host, the non-F1 termination point host) generates a first RRC reconfiguration message, in which the at least one IP address configuration includes the IP address information of the non-F1 termination point topology domain, and sends the first RRC reconfiguration message to the IAB node. Therefore, after receiving the first RRC reconfiguration message through SRB1, the IAB node can obtain the at least one IP address configuration carried therein. The IAB node knows that the at least one IP address configuration is provided by the MN, and the MN is a non-F1 termination point. Therefore, the IAB node determines that the at least one IP address configuration carried by the first RRC reconfiguration message is the IP address information of the non-F1 termination point topology domain. That is, the IAB node determines that the at least one IP address configuration in the first RRC reconfiguration message received through SRB1 includes the IP address information of the non-F1 termination point topology domain.
[0170] (ii) Explicit Instructions
[0171] For example, SN sends an IAB transmission migration management request message to MN. After receiving the request message, MN (the second IAB host, non-F1 termination point host) generates a first RRC reconfiguration message, in which a new information element can be introduced, namely, the first indication information non-F1-terminating, and the first RRC reconfiguration message is sent to the IAB node. Therefore, after receiving the first RRC reconfiguration message through SRB1, the IAB node can obtain at least one IP address information and the first indication information carried therein. Therefore, the IAB node determines that the at least one IP address configuration carried by the first RRC reconfiguration message is the IP address information of the non-F1 termination point topology domain. The example of the first RRC reconfiguration message introducing the first indication information is similar to the above 1)-4) and will not be repeated here.
[0172] In some embodiments, after dual connectivity is established, the IP address of the F1 termination point topology domain can be configured (modified) during the IAB transport migration management process. The first RRC reconfiguration message is generated by the second IAB host instead of the first IAB host and sent by the second IAB host to the IAB node. The IAB node receives the first RRC reconfiguration message sent by the second IAB host via SRB1. The first RRC reconfiguration message includes at least one IP address configuration for the IAB node, and the at least one IP address configuration includes IP address information of the F1 termination point topology domain. The IP address of the F1 termination point topology domain refers to the IP address anchored to donor-DU2.
[0173] (i) Implicit indication
[0174] For example, the SN provides at least one IP address configuration (including the IP address information of the F1 termination point topology domain) and places it in an IAB transport migration modification request message and sends it to the MN (the second IAB host, not the F1 termination point host). After receiving the request message, the MN generates a secondary cell configuration RRC message on behalf of the SN, wherein the at least one IP address configuration includes the IP address information of the F1 termination point topology domain, and generates a third RRC reconfiguration message, and places the first RRC reconfiguration message in the mrdc-SecondaryCellGroupConfig field in the third RRC reconfiguration message and forwards it to the IAB node. Therefore, after receiving the third RRC reconfiguration message through SRB1, the IAB node can obtain the RRC reconfiguration message contained in the mrdc-SecondaryCellGroupConfig field carried therein. The IAB node knows that the at least one IP address configuration in the RRC reconfiguration message contained in the mrdc-SecondaryCellGroupConfig field is provided by the SN, and the SN is the F1 termination point host. Therefore, the IAB node determines that the at least one IP address configuration carried by the first RRC reconfiguration message is the IP address information of the F1 termination point topology domain. That is, the IAB node determines that at least one IP address configuration of the RRC reconfiguration message contained in the mrdc-SecondaryCellGroupConfig field in the first RRC reconfiguration message received through SRB1 includes IP address information of the F1 termination point topology field.
[0175] (ii) Explicit Instructions
[0176] The SN provides at least one IP address configuration (including the IP address information of the F1 termination point topology domain) and places it in an IAB transport migration modification request message and sends it to the MN (the second IAB host, not the F1 termination point host). After receiving the request message, the MN generates a first RRC reconfiguration message, wherein the at least one IP address configuration includes the IP address information of the F1 termination point topology domain. However, there is no need to introduce the first indication information in the first RRC reconfiguration message. Since the first RRC reconfiguration message does not include the first indication information, that is, the IAB node does not receive the first indication information, the IAB node determines that the at least one IP address configuration carried by the RRC message is the IP address information of the F1 termination point topology domain.
[0177] The above describes how to configure and indicate an IP address in a non-F1 termination topology domain or an F1 termination topology domain, and how an IAB node distinguishes whether the configured IP address is in a non-F1 termination topology domain or an F1 termination topology domain. In the above embodiments, the IAB node can determine whether the MN or SN is an F1 termination host or a non-F1 termination host. For example, the IAB node can determine whether the MN or SN is an F1 termination host based on which host provided the received BAP configuration information (bap-config-r16 field).
[0178] In the above explicit indications, whether the first indication information is received is used as an example to illustrate how to determine whether the configured IP address is a non-F1 termination point topology domain or an F1 termination point topology domain, but the present application is not limited to this. For example, the first indication information is used to indicate whether the IP address configuration contains IP address information of a non-F1 termination point topology domain, or the first indication information is used to indicate whether the IP address configuration contains IP address information of a non-F1 termination point topology domain or IP address information of an F1 termination point topology domain. For example, when the IAB receives the first indication information and the value of the first indication information is the first value (true or 1), it is determined that the IP address configuration contains IP address information of a non-F1 termination point topology domain; when the value of the first indication information is the second value (false or 0), it is determined that the IP address configuration contains IP address information of an F1 termination point topology domain. The specific process is the same as above and will not be given one by one here.
[0179] The above signaling process is merely an illustrative example of the present application, but the present application is not limited thereto. For more specific information about the signaling process, please refer to the relevant art. Furthermore, for example, the execution order of the various operations may be appropriately adjusted, and other operations may be added or some operations may be reduced. Those skilled in the art may make appropriate modifications based on the above content, and are not limited to the description in FIG. 10 .
[0180] The above embodiments are merely exemplary of the present invention, but the present invention is not limited thereto. Appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.
[0181] It can be seen from the above embodiment that the IP address of the non-F1 termination point topology domain or the IP address of the F1 termination point topology domain can be configured to the IAB node through the first RRC reconfiguration message. In this way, the boundary node can transmit services whose routing ID belongs to the F1-terminating topology domain and services whose routing ID belongs to the non-F1-terminating topology domain respectively.
[0182] Embodiments of the second aspect
[0183] The embodiment of the present application provides a method for determining a transmission address, which is described from the perspective of a first IAB host. The contents that are the same as those in the embodiment of the first aspect are not repeated here.
[0184] FIG14 is another schematic diagram of a method for determining a transmission address according to an embodiment of the present application. As shown in FIG14 , the method includes:
[0185] 1401. The first IAB host sends a first RRC reconfiguration message, where the first RRC reconfiguration message includes at least one IP address configuration for an IAB node; or sends at least one IP address configuration for the IAB node.
[0186] The at least one IP address configuration includes IP address information of an F1 termination point topology domain, or includes IP address information of a non-F1 termination point topology domain;
[0187] In some embodiments, the first IAB host may send the first RRC reconfiguration message to the IAB node or a second IAB host, the F1 connection of the IAB node is terminated at the first IAB host, and the IAB node has an RRC connection with the second IAB host.
[0188] In some embodiments, it may be implicitly indicated whether the configured IP address belongs to a non-F1 termination point topology domain, or it may be explicitly indicated whether the configured IP address belongs to a non-F1 termination point topology domain. For example, the first IAB host indicates through the first indication information that the IP address configuration includes IP address information of the F1 termination point topology domain, or includes IP address information of the non-F1 termination point topology domain.
[0189] In some embodiments, the IP address configuration includes IP address information of a non-F1 termination point topology domain.
[0190] In some embodiments, the first IAB host is a source host for the IAB node switching, the second IAB host is a target host for the IAB node switching, and the first RRC reconfiguration message is a switching command RRC message; the method may further include: the first IAB host receiving the first RRC reconfiguration message sent by the second IAB host, and in 1401, the first IAB host forwarding the first RRC reconfiguration message generated by the second IAB host to the IAB node.
[0191] In some embodiments, the first IAB host is a master node MN of the IAB node, and the second IAB host is a secondary node SN of the IAB node.
[0192] For example, the first RRC reconfiguration message is an RRC reconfiguration message included in the secondary cell group configuration field in the RRC reconfiguration message and is carried by a second RRC reconfiguration message sent by the first IAB host; the first IAB host sends the second RRC reconfiguration message to the IAB node through SRB1.
[0193] The method further includes: the first IAB host receiving the first RRC reconfiguration message sent by the second IAB host (the first RRC reconfiguration message is generated by the second IAB host). Furthermore, in 1401, the first IAB host sends the second RRC reconfiguration message (the second RRC reconfiguration message is generated by the first IAB host) to the IAB node via SRB1, where the second RRC reconfiguration message carries the first RRC reconfiguration message.
[0194] Alternatively, the method may further include: the first IAB host receiving the IP address configuration provided by the second IAB host, and generating the first RRC reconfiguration message on behalf of the second IAB host, and, in 1401, the first IAB host sending the second RRC reconfiguration message to the IAB node through SRB1 (the second RRC reconfiguration message is also generated by the first IAB host), and the second RRC reconfiguration message carries the first RRC reconfiguration message.
[0195] For example, the method may further include: the first IAB host receiving the IP address configuration provided by the second IAB host and generating a first RRC reconfiguration message. In 1401, the first IAB host sends the first RRC reconfiguration message to the IAB node through SRB1.
[0196] In the above embodiment, the IP address configuration includes IP address information of a non-F1 termination point topology domain. When explicitly indicated, the first IAB host indicates that the IP address configuration includes IP address information of a non-F1 termination point topology domain by including the first indication information in the first RRC reconfiguration message or the second RRC reconfiguration message. The first indication information is included in a newly added information element of the first RRC reconfiguration message or the second RRC reconfiguration message, or in an IP address configuration list information element of the first RRC reconfiguration message or the second RRC reconfiguration message, or in an IP address configuration information element of the first RRC reconfiguration message or the second RRC reconfiguration message, or in an IP address index information element of the first RRC reconfiguration message or the second RRC reconfiguration message.
[0197] In some embodiments, the IP address configuration includes IP address information of the F1 termination point topology domain.
[0198] In some embodiments, the first IAB host is the SN of the IAB node, and the second IAB host is the MN of the IAB node.
[0199] For example, in 1401, the first IAB host sends the first RRC reconfiguration message to the IAB node through SRB3.
[0200] For example, in 1401, the first IAB host sends the first RRC reconfiguration message to the second IAB host, wherein the first RRC reconfiguration message is a secondary cell group configuration RRC message.
[0201] For example, in 1401, the first IAB host sends the IP address configuration to the second IAB host. The IP address configuration is carried by an IAB transport migration modification request message.
[0202] In some embodiments, the first IAB host is a master node MN of the IAB node, and the second IAB host is a secondary node SN of the IAB node.
[0203] For example, the first IAB host sends the first RRC reconfiguration message to the IAB node through SRB1.
[0204] In the above embodiment, the IP address configuration includes the IP address information of the F1 termination topology domain. In the case of explicit indication, the first IAB host indicates that the IP address configuration includes the IP address information of the F1 termination topology domain by not including the first indication information in the first RRC reconfiguration message.
[0205] It is worth noting that FIG14 above is merely a schematic illustration of an embodiment of the present application, and the present application is not limited thereto. For example, the execution order of the various operations may be appropriately adjusted, and other operations may be added or some operations may be reduced. Those skilled in the art may make appropriate modifications based on the above description, and are not limited to the description of FIG14 above.
[0206] It can be seen from the above embodiment that the IP address of the non-F1 termination point topology domain or the IP address of the F1 termination point topology domain can be configured to the IAB node through the first RRC reconfiguration message. In this way, the boundary node can transmit services whose routing ID belongs to the F1-terminating topology domain and services whose routing ID belongs to the non-F1-terminating topology domain respectively.
[0207] Embodiments of the third aspect
[0208] The embodiment of the present application provides a method for determining a transmission address, which is described from the perspective of a second IAB host.
[0209] FIG15 is a schematic diagram of a method for determining a transmission address according to an embodiment of the present application. As shown in FIG15 , the method includes:
[0210] 1501. The second IAB host sends a first RRC reconfiguration message, where the first RRC reconfiguration message includes at least one IP address configuration for an IAB node; or sends at least one IP address configuration for an IAB node;
[0211] The at least one IP address configuration includes IP address information of an F1 termination point topology domain, or includes IP address information of a non-F1 termination point topology domain.
[0212] In some embodiments, the second IAB host may send the first RRC reconfiguration message to the IAB node or the first IAB host, the F1 connection of the IAB node is terminated at the first IAB host, and the IAB node has an RRC connection with the second IAB host.
[0213] In some embodiments, it may be implicitly indicated whether the configured IP address belongs to a non-F1 termination point topology domain, or it may be explicitly indicated whether the configured IP address belongs to a non-F1 termination point topology domain. For example, the second IAB host indicates through the first indication information that the IP address configuration includes IP address information of the F1 termination point topology domain, or includes IP address information of the non-F1 termination point topology domain.
[0214] In some embodiments, the IP address configuration includes IP address information of a non-F1 termination point topology domain.
[0215] In some embodiments, the first IAB host is a source host for the IAB node switching, the second IAB host is a target host for the IAB node switching, the first RRC reconfiguration message is a switching command RRC message, and, in 1501, the second IAB host sends the first RRC reconfiguration message to the first IAB host.
[0216] In some embodiments, the first IAB host is a master node MN of the IAB node, and the second IAB host is a secondary node SN of the IAB node.
[0217] For example, in 1501, the second IAB host sends a first RRC reconfiguration message to the first IAB host; or,
[0218] For example, in 1501, the second IAB host sends the IP address configuration to the first IAB host.
[0219] For example, in 1501, the second IAB host sends the first RRC reconfiguration message to the IAB node through SRB3.
[0220] In some embodiments, the second IAB host is a primary node MN of the IAB node, and the first IAB host is a secondary node SN of the IAB node.
[0221] For example, in 1501, the second IAB host sends the first RRC reconfiguration message to the IAB node through SRB1.
[0222] In the above embodiment, the IP address configuration includes IP address information of a non-F1 termination point topology domain. When explicitly indicated, the second IAB host indicates that the IP address configuration includes IP address information of a non-F1 termination point topology domain by including the first indication information in the first RRC reconfiguration message. The first indication information is included in a newly added information element of the first RRC reconfiguration message, or in an IP address configuration list information element of the first RRC reconfiguration message, or in an IP address configuration information element of the first RRC reconfiguration message, or in an IP address index information element of the first RRC reconfiguration message.
[0223] In some embodiments, the IP address configuration includes IP address information of the F1 termination point topology domain.
[0224] In some embodiments, the first IAB host is the SN of the IAB node, and the second IAB host is the MN of the IAB node.
[0225] For example, the first RRC reconfiguration message is the RRC reconfiguration message included in the secondary cell group configuration field in the RRC reconfiguration message, and is carried by the third RRC reconfiguration message sent by the second IAB host; in 1501, the second IAB host sends the third RRC reconfiguration message to the IAB node through SRB1.
[0226] The method further includes: receiving, by the second IAB host, a first RRC reconfiguration message sent by the first IAB host.
[0227] For example, in 1501, the second IAB host receives the IP address configuration provided by the first IAB host, and generates the first RRC reconfiguration message on behalf of the first IAB host.
[0228] For example, the method may further include: the second IAB host receiving the IP address configuration sent by the first IAB host; in 1501, the second IAB host sending the first RRC reconfiguration message to the IAB node through SRB1.
[0229] In the above embodiment, the IP address configuration includes the IP address information of the F1 termination topology domain. In the case of explicit indication, the first IAB host indicates that the IP address configuration includes the IP address information of the F1 termination topology domain by not including the first indication information in the first RRC reconfiguration message or the third RRC reconfiguration message.
[0230] It is worth noting that FIG15 above is merely a schematic illustration of an embodiment of the present application, and the present application is not limited thereto. For example, the execution order of the various operations may be appropriately adjusted, and other operations may be added or some operations may be removed. Those skilled in the art may make appropriate modifications based on the above description, and are not limited to the description of FIG15 above.
[0231] The above embodiments are merely exemplary of the present invention, but the present invention is not limited thereto. Appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.
[0232] It can be seen from the above embodiment that the IP address of the non-F1 termination point topology domain or the IP address of the F1 termination point topology domain can be configured to the IAB node through the first RRC reconfiguration message. In this way, the boundary node can transmit services whose routing ID belongs to the F1-terminating topology domain and services whose routing ID belongs to the non-F1-terminating topology domain respectively.
[0233] Embodiments of the fourth aspect
[0234] The present embodiment provides an IAB node device. Details similar to those in the first aspect are not repeated here. The device may be, for example, an IAB node in an IAB system (such as the edge node in the first aspect), or one or more components, assemblies, or modules configured in the IAB node.
[0235] FIG16 is a schematic diagram of an IAB node device according to an embodiment of the present application. As shown in FIG16 , the IAB node device 1600 includes:
[0236] A first receiving unit 1601 is configured to receive a first RRC reconfiguration message, where the first RRC reconfiguration message includes at least one IP address configuration for the IAB node;
[0237] The at least one IP address configuration includes IP address information of an F1 termination point topology domain, or includes IP address information of a non-F1 termination point topology domain.
[0238] In some embodiments, the F1 connection of the IAB node is terminated at a first IAB host, and the IAB node has an RRC connection with a second IAB host.
[0239] In some embodiments, the device further comprises:
[0240] The first processing unit 1602 determines whether the IP address configuration includes the IP address information of the F1 termination point topology domain or the IP address information of the non-F1 termination point topology domain.
[0241] In some embodiments, the first processing unit determines, according to the first indication information, that the IP address configuration includes IP address information of an F1 termination point topology domain or IP address information of a non-F1 termination point topology domain.
[0242] In some embodiments, the first processing unit determines that the IP address configuration includes IP address information of a non-F1-terminating topology domain.
[0243] In some embodiments, the first IAB host is a source host of the IAB node handover, and the second IAB host is a target host of the IAB node handover; the first RRC reconfiguration message is a handover command RRC message generated by the second IAB host and forwarded by the first IAB host.
[0244] In some embodiments, the first IAB host is a master node MN of the IAB node, and the second IAB host is a secondary node SN of the IAB node.
[0245] For example, the first RRC reconfiguration message is an RRC reconfiguration message included in a secondary cell group configuration field in the RRC reconfiguration message and is carried by a second RRC reconfiguration message sent by the first IAB host; the first receiving unit receives the second RRC reconfiguration message sent by the first IAB host via SRB1. Optionally, the first RRC reconfiguration message is generated by the first IAB host instead of the second IAB host.
[0246] For example, the first receiving unit receives the first RRC reconfiguration message sent by the second IAB host through SRB3.
[0247] For example, the first receiving unit receives the first RRC reconfiguration message sent by the first IAB host through SRB1.
[0248] In some embodiments, the first IAB host is the SN of the IAB node, and the second IAB host is the MN of the IAB node; the first receiving unit receives the first RRC reconfiguration message sent by the second IAB host through SRB1.
[0249] In some embodiments, when the first RRC reconfiguration message or the second RRC reconfiguration message includes the first indication information, the first processing unit determines that the IP address configuration includes IP address information of a non-F1 end-point topology domain. The first indication information is included in a newly added information element of the first RRC reconfiguration message or the second RRC reconfiguration message, or included in an IP address configuration list information element of the first RRC reconfiguration message or the second RRC reconfiguration message, or included in an IP address configuration information element of the first RRC reconfiguration message or the second RRC reconfiguration message, or included in an IP address index information element of the first RRC reconfiguration message or the second RRC reconfiguration message.
[0250] In some embodiments, the first processing unit determines that the IP address configuration includes IP address information of an F1-terminating topology domain.
[0251] In some embodiments, the first IAB host is a master node MN of the IAB node, and the second IAB host is a secondary node SN of the IAB node; the first receiving unit receives the first RRC reconfiguration message sent by the first IAB host through SRB1.
[0252] In some embodiments, the first IAB host is the SN of the IAB node, and the second IAB host is the MN of the IAB node.
[0253] For example, the first RRC reconfiguration message is an RRC reconfiguration message included in a secondary cell group configuration field in the RRC reconfiguration message and carried by a third RRC reconfiguration message sent by the second IAB host; the first receiving unit receives the third RRC reconfiguration message sent by the second IAB host via SRB1. Optionally, the first RRC reconfiguration message is generated by the second IAB host instead of the first IAB host.
[0254] For example, the first receiving unit receives the first RRC reconfiguration message sent by the first IAB host through SRB3.
[0255] For example, the first receiving unit receives the first RRC reconfiguration message sent by the second IAB host through SRB1.
[0256] In some embodiments, when the first RRC reconfiguration message or the third RRC reconfiguration message does not include the first indication information, the first processing unit determines that the IP address configuration includes IP address information of the F1 end-point topology domain.
[0257] The above embodiments are merely exemplary of the present invention, but the present invention is not limited thereto. Appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.
[0258] It is worth noting that the above only describes the components or modules related to this application, but this application is not limited thereto. The IAB node device 1600 of the embodiment of this application may also include other components or modules. For the specific contents of these components or modules, please refer to the relevant art.
[0259] In addition, for the sake of simplicity, FIG16 only illustrates the connection relationship or signal direction between various components or modules. However, it should be clear to those skilled in the art that various related technologies such as bus connection can be used. The above-mentioned components or modules can be implemented by hardware facilities such as processors, memories, transmitters, and receivers; the implementation of this application is not limited to this.
[0260] It can be seen from the above embodiment that the IP address of the non-F1 termination point topology domain or the IP address of the F1 termination point topology domain can be configured to the IAB node through the first RRC reconfiguration message. In this way, the boundary node can transmit services whose routing ID belongs to the F1-terminating topology domain and services whose routing ID belongs to the non-F1-terminating topology domain respectively.
[0261] Embodiments of the fifth aspect
[0262] This embodiment of the present application provides an IAB host device. Details common to the embodiment of the second aspect are omitted. This device may be, for example, an IAB donor-CU in an IAB system (e.g., the first IAB host in the embodiments of the first, second, and third aspects), or one or more components, assemblies, or modules configured within the IAB donor-CU.
[0263] FIG17 is a schematic diagram of an IAB host device according to an embodiment of the present application. As shown in FIG17 , the IAB host device 1700 includes:
[0264] A first sending unit 1701 is configured to send a first RRC reconfiguration message, where the first RRC reconfiguration message includes at least one IP address configuration for an IAB node; or send at least one IP address configuration for the IAB node;
[0265] The at least one IP address configuration includes IP address information of an F1 termination point topology domain, or includes IP address information of a non-F1 termination point topology domain;
[0266] The F1 connection of the IAB node is terminated at the first IAB host, and the IAB node has an RRC connection with a second IAB host.
[0267] In some embodiments, the IAB host device indicates through the first indication information that the IP address configuration includes IP address information of an F1 termination point topology domain, or includes IP address information of a non-F1 termination point topology domain.
[0268] In some embodiments, the IP address configuration includes IP address information of a non-F1 termination point topology domain.
[0269] In some embodiments, the first IAB host is a source host of the IAB node handover, the second IAB host is a target host of the IAB node handover, and the first RRC reconfiguration message is a handover command RRC message;
[0270] The device further includes (not shown): a second receiving unit, which receives a first RRC reconfiguration message sent by the second IAB host, and the first sending unit forwards the first RRC reconfiguration message generated by the second IAB host to the IAB node.
[0271] In some embodiments, the first IAB host is a master node MN of the IAB node, and the second IAB host is a secondary node SN of the IAB node.
[0272] For example, the first RRC reconfiguration message is an RRC reconfiguration message included in the secondary cell group configuration field in the RRC reconfiguration message, and is carried by a second RRC reconfiguration message sent by the first IAB host;
[0273] The first sending unit sends the second RRC reconfiguration message to the IAB node through SRB1.
[0274] In some embodiments, the device further includes: (not shown)
[0275] A third receiving unit receives the first RRC reconfiguration message sent by the second IAB host.
[0276] In some embodiments, the device further includes: (not shown)
[0277] a fourth receiving unit, configured to receive the IP address configuration provided by the second IAB host;
[0278] A second processing unit is configured to generate the first RRC reconfiguration message on behalf of the second IAB host.
[0279] In some embodiments, the device further includes: (not shown)
[0280] The fifth receiving unit receives the IP address configuration provided by the second IAB host, and the first sending unit sends the first RRC reconfiguration message through SRB1.
[0281] In some embodiments, the IAB host device includes the first indication information through the first RRC reconfiguration message or the second RRC reconfiguration message to indicate that the IP address configuration includes IP address information of a non-F1 end-point topology domain.
[0282] In some embodiments, the IP address configuration includes IP address information of the F1 termination point topology domain.
[0283] In some embodiments, the first IAB host is the SN of the IAB node, and the second IAB host is the MN of the IAB node.
[0284] For example, the first sending unit sends the first RRC reconfiguration message to the IAB node through SRB3.
[0285] For example, the first sending unit sends the first RRC reconfiguration message to the second IAB host, wherein the first RRC reconfiguration message is a secondary cell group configuration RRC message; or,
[0286] The first sending unit sends the IP address configuration to the second IAB host.
[0287] In some embodiments, the first IAB host is a master node MN of the IAB node, and the second IAB host is a secondary node SN of the IAB node; the first sending unit sends the first RRC reconfiguration message to the IAB node through SRB1.
[0288] In some embodiments, the IAB host device indicates that the IP address configuration includes IP address information of the F1 end-point topology domain by not including the first indication information in the first RRC reconfiguration message.
[0289] In some embodiments, the first indication information is included in a newly added information element of the first RRC reconfiguration message or the second RRC reconfiguration message, or is included in the IP address configuration list information element of the first RRC reconfiguration message or the second RRC reconfiguration message, or is included in the IP address configuration information element of the first RRC reconfiguration message or the second RRC reconfiguration message, or is included in the IP address index information element of the first RRC reconfiguration message or the second RRC reconfiguration message.
[0290] The above embodiments are merely exemplary of the present invention, but the present invention is not limited thereto. Appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.
[0291] It is worth noting that the above only describes the components or modules related to the present application, but the present application is not limited thereto. The IAB host device 1700 of the embodiment of the present application may also include other components or modules. For the specific contents of these components or modules, reference may be made to the relevant art.
[0292] In addition, for the sake of simplicity, FIG17 only illustrates the connection relationship or signal direction between various components or modules. However, it should be clear to those skilled in the art that various related technologies such as bus connection can be used. The above-mentioned components or modules can be implemented by hardware facilities such as processors, memories, transmitters, and receivers; the implementation of this application is not limited to this.
[0293] It can be seen from the above embodiment that the IP address of the non-F1 termination point topology domain or the IP address of the F1 termination point topology domain can be configured to the IAB node through the first RRC reconfiguration message. In this way, the boundary node can transmit services whose routing ID belongs to the F1-terminating topology domain and services whose routing ID belongs to the non-F1-terminating topology domain respectively.
[0294] Embodiments of the sixth aspect
[0295] This embodiment of the present application provides an IAB host device. Details common to the third aspect of the embodiment are omitted. This device may be, for example, an IAB donor-CU in an IAB system (e.g., the second IAB host in the first, second, and third aspects of the embodiment), or one or more components, assemblies, or modules configured within the IAB donor-CU.
[0296] FIG18 is a schematic diagram of an IAB host device according to an embodiment of the present application. As shown in FIG18 , the IAB host device 1800 includes:
[0297] A second sending unit 1801 is configured to send a first RRC reconfiguration message, where the first RRC reconfiguration message includes at least one IP address configuration for an IAB node; or to send at least one IP address configuration for an IAB node;
[0298] The at least one IP address configuration includes IP address information of an F1 termination point topology domain, or includes IP address information of a non-F1 termination point topology domain.
[0299] The F1 connection of the IAB node is terminated at the first IAB host, and the IAB node has an RRC connection with the second IAB host.
[0300] In some embodiments, the IAB host device indicates through the first indication information that the IP address configuration includes IP address information of an F1 termination point topology domain, or includes IP address information of a non-F1 termination point topology domain.
[0301] In some embodiments, the IP address configuration includes IP address information of a non-F1 termination point topology domain.
[0302] In some embodiments, the first IAB host is a source host for the IAB node switching, the second IAB host is a target host for the IAB node switching, the first RRC reconfiguration message is a switching command RRC message, and the second sending unit sends the first RRC reconfiguration message to the first IAB host.
[0303] In some embodiments, the first IAB host is a master node MN of the IAB node, and the second IAB host is a secondary node SN of the IAB node.
[0304] For example, the second sending unit sends a first RRC reconfiguration message to the first IAB host; or sends the IP address configuration to the first IAB host.
[0305] For example, the second sending unit sends the first RRC reconfiguration message to the IAB node through SRB3.
[0306] In some embodiments, the first IAB host is the SN of the IAB node, and the second IAB host is the MN of the IAB node; the second sending unit sends the first RRC reconfiguration message to the IAB node through SRB1.
[0307] In some embodiments, the IAB host device includes the first indication information in the first RRC reconfiguration message to indicate that the IP address configuration includes IP address information of a non-F1 end-point topology domain.
[0308] In some embodiments, the IP address configuration includes IP address information of the F1 termination point topology domain.
[0309] In some embodiments, the first IAB host is the SN of the IAB node, and the second IAB host is the MN of the IAB node.
[0310] For example, the first RRC reconfiguration message is the RRC reconfiguration message included in the secondary cell group configuration field in the RRC reconfiguration message, and is carried by the third RRC reconfiguration message sent by the second IAB host; the second sending unit sends the third RRC reconfiguration message to the IAB node through SRB1.
[0311] In some embodiments, the device further includes: (not shown)
[0312] A sixth receiving unit is configured to receive a first RRC reconfiguration message sent by the first IAB host.
[0313] In some embodiments, the device further includes: (not shown)
[0314] a seventh receiving unit, configured to receive the IP address configuration provided by the first IAB host;
[0315] The second processing unit generates the first RRC reconfiguration message on behalf of the first IAB host.
[0316] In some embodiments, the device further includes: (not shown)
[0317] An eighth receiving unit receives the IP address configuration sent by the first IAB host, and the second sending unit sends the first RRC reconfiguration message to the IAB node through SRB1.
[0318] In some embodiments, the IAB host device indicates that the IP address configuration includes the IP address information of the F1 termination point topology domain by not including the first indication information through the first RRC reconfiguration message or the third RRC reconfiguration message.
[0319] In some embodiments, the first indication information is included in a newly added information element of the first RRC reconfiguration message or the second RRC reconfiguration message, or is included in the IP address configuration list information element of the first RRC reconfiguration message or the second RRC reconfiguration message, or is included in the IP address configuration information element of the first RRC reconfiguration message or the second RRC reconfiguration message, or is included in the IP address index information element of the first RRC reconfiguration message or the second RRC reconfiguration message.
[0320] The above embodiments are merely exemplary of the present invention, but the present invention is not limited thereto. Appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.
[0321] It is worth noting that the above only describes the components or modules related to the present application, but the present application is not limited thereto. The IAB host device 1800 of the embodiment of the present application may also include other components or modules. For the specific contents of these components or modules, reference may be made to the relevant art.
[0322] In addition, for the sake of simplicity, FIG18 only illustrates the connection relationship or signal direction between various components or modules. However, it should be clear to those skilled in the art that various related technologies such as bus connection can be used. The above-mentioned components or modules can be implemented by hardware facilities such as processors, memories, transmitters, and receivers; the implementation of this application is not limited to this.
[0323] It can be seen from the above embodiment that the IP address of the non-F1 termination point topology domain or the IP address of the F1 termination point topology domain can be configured to the IAB node through the first RRC reconfiguration message. In this way, the boundary node can transmit services whose routing ID belongs to the F1-terminating topology domain and services whose routing ID belongs to the non-F1-terminating topology domain respectively.
[0324] Embodiments of the seventh aspect
[0325] An embodiment of the present application provides a communication system, including a first IAB host (donor) device of the fourth aspect embodiment, a second IAB host device of the fifth aspect embodiment, and an IAB node (IAB-node) device of the third aspect embodiment; regarding the network architecture of the host (donor) device and the IAB node device, reference can also be made to related technologies, and the description is omitted here.
[0326] An embodiment of the present application further provides an IAB device, which may be an IAB host device or an IAB node device (a migration node or a child node).
[0327] Figure 9 is a schematic diagram of an IAB device according to an embodiment of the present application. As shown in Figure 9 , IAB device 900 may include a processor (e.g., a central processing unit (CPU)) 901 and a memory 902 ; the memory 902 is coupled to the processor 901 . The memory 902 may store various data and may also store an information processing program 905 , which is executed under the control of the CPU 901 .
[0328] For example, the processor 901 may be configured to execute a program to implement the transmission address determination method in the embodiment of the first aspect.
[0329] For another example, the processor 901 may be configured to execute a program to implement the transmission address determination method in the embodiment of the second aspect.
[0330] For another example, the processor 901 may be configured to execute a program to implement the transmission address determination method in the embodiment of the third aspect.
[0331] As shown in FIG9 , the IAB device 900 may further include a transceiver 903 and an antenna 904. The functions of these components are similar to those in the prior art and are not further described here. It is worth noting that the IAB device 900 does not necessarily include all of the components shown in FIG9 . Furthermore, the IAB device 900 may also include components not shown in FIG9 , for which reference may be made to the prior art.
[0332] An embodiment of the present application further provides a computer-readable program, wherein when the program is executed in an IAB device, the program causes a computer to execute the transmission address determination method in the embodiments of the first to third aspects in the IAB device.
[0333] An embodiment of the present application further provides a storage medium storing a computer-readable program, wherein the computer-readable program enables a computer to execute the transmission address determination method in the embodiments of the first to third aspects in an IAB device.
[0334] The above devices and methods of the present application can be implemented by hardware or by a combination of hardware and software. The present application relates to such a computer-readable program that, when executed by a logic component, enables the logic component to implement the devices or components described above, or enables the logic component to implement the various methods or steps described above. The logic component is, for example, a field programmable logic component, a microprocessor, a processor used in a computer, etc. The present application also relates to a storage medium for storing the above program, such as a hard disk, a magnetic disk, an optical disk, a DVD, a flash memory, etc.
[0335] The method / device described in conjunction with the embodiments of the present application can be directly embodied as hardware, a software module executed by a processor, or a combination of the two. For example, one or more of the functional block diagrams shown in the figure and / or one or more combinations of functional block diagrams can correspond to various software modules of the computer program flow or to various hardware modules. These software modules can respectively correspond to the various steps shown in the figure. These hardware modules can be implemented by solidifying these software modules, for example, using a field programmable gate array (FPGA).
[0336] The software module may be located in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. A storage medium may be coupled to a processor so that the processor can read information from the storage medium and write information to the storage medium; or the storage medium may be an integral part of the processor. The processor and the storage medium may be located in an ASIC. The software module may be stored in the memory of the mobile terminal or in a memory card that can be inserted into the mobile terminal. For example, if the device (such as a mobile terminal) uses a large-capacity MEGA-SIM card or a large-capacity flash memory device, the software module may be stored in the MEGA-SIM card or the large-capacity flash memory device.
[0337] One or more of the functional blocks and / or one or more combinations of functional blocks described in the accompanying drawings may be implemented as a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, or any appropriate combination thereof for performing the functions described in this application. One or more of the functional blocks and / or one or more combinations of functional blocks described in the accompanying drawings may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in communication with a DSP, or any other such configuration.
[0338] The present application has been described above in conjunction with specific embodiments. However, those skilled in the art should understand that these descriptions are merely illustrative and are not intended to limit the scope of protection of the present application. Those skilled in the art may make various modifications and variations to the present application based on the spirit and principles of the present application, and such modifications and variations are also within the scope of the present application.
[0339] Regarding the above implementation methods disclosed in this embodiment, the following additional notes are also disclosed:
[0340] Boundary Node
[0341] 1. A method for determining a transmission address, applied to access and backhaul IAB node devices, characterized in that the method comprises:
[0342] The IAB node receives a first RRC reconfiguration message, where the first RRC reconfiguration message includes at least one IP address configuration for the IAB node;
[0343] The at least one IP address configuration includes IP address information of an F1 termination point topology domain, or includes IP address information of a non-F1 termination point topology domain.
[0344] 2. The method according to Note 1, wherein the F1 connection of the IAB node is terminated at a first IAB host, and the IAB node has an RRC connection with a second IAB host.
[0345] 3. The method according to Supplementary Note 2, wherein the method further comprises:
[0346] The IAB node determines that the IP address configuration includes IP address information of an F1 termination point topology domain or IP address information of a non-F1 termination point topology domain.
[0347] 4. The method according to Note 3, wherein the IAB node determines, based on the first indication information, that the IP address configuration includes IP address information of an F1 termination point topology domain or IP address information of a non-F1 termination point topology domain.
[0348] 5. The method according to Note 3 or 4, wherein the IAB node determines that the IP address configuration includes IP address information of a non-F1-terminating topology domain.
[0349] 6. The method according to Supplementary Note 5, wherein the first IAB host is a source host of the IAB node handover, and the second IAB host is a target host of the IAB node handover;
[0350] The first RRC reconfiguration message is a handover command RRC message generated by the second IAB host and forwarded by the first IAB host.
[0351] 7. The method according to Note 5, wherein the first IAB host is a master node MN of the IAB node, and the second IAB host is a secondary node SN of the IAB node.
[0352] 8. The method according to Note 7, wherein the first RRC reconfiguration message is an RRC reconfiguration message included in a secondary cell group configuration field in the RRC reconfiguration message and is carried by a second RRC reconfiguration message sent by the first IAB host;
[0353] The IAB node receives the second RRC reconfiguration message sent by the first IAB host through SRB1.
[0354] 9. The method according to Note 8, wherein the first RRC reconfiguration message is generated by the first IAB host instead of the second IAB host.
[0355] 10. The method according to Note 7, wherein the IAB node receives the first RRC reconfiguration message sent by the second IAB host through SRB3.
[0356] 11. The method according to Note 7, wherein the IAB node receives the first RRC reconfiguration message sent by the first IAB host through SRB1.
[0357] 12. The method according to Supplementary Note 5, wherein the first IAB host is the SN of the IAB node, and the second IAB host is the MN of the IAB node;
[0358] The IAB node receives the first RRC reconfiguration message sent by the second IAB host through SRB1.
[0359] 13. The method according to any one of Notes 5 to 12, wherein, when the IAB node includes the first indication information in the first RRC reconfiguration message or the second RRC reconfiguration message, it determines that the IP address configuration includes IP address information of a non-F1 end-point topology domain.
[0360] 14. The method according to Note 3 or 4, wherein the IAB node determines that the IP address configuration includes IP address information of an F1-terminating topology domain.
[0361] 15. The method according to Supplementary Note 14, wherein the first IAB host is a primary node MN of the IAB node, and the second IAB host is a secondary node SN of the IAB node;
[0362] The IAB node receives the first RRC reconfiguration message sent by the first IAB host through SRB1.
[0363] 16. The method according to note 11, wherein the first IAB host is the SN of the IAB node, and the second IAB host is the MN of the IAB node.
[0364] 17. The method according to Note 16, wherein the first RRC reconfiguration message is an RRC reconfiguration message included in a secondary cell configuration field in the RRC reconfiguration message and is carried by a third RRC reconfiguration message sent by the second IAB host;
[0365] The IAB node receives the third RRC reconfiguration message sent by the second IAB host through SRB1.
[0366] 18. The method according to Note 17, wherein the first RRC reconfiguration message is generated by the second IAB host instead of the first IAB host.
[0367] 19. The method according to Note 16, wherein the IAB node receives the first RRC reconfiguration message sent by the first IAB host through SRB3.
[0368] 20. The method according to Note 16, wherein the IAB node receives the first RRC reconfiguration message sent by the second IAB host through SRB1.
[0369] 21. A method according to any one of Notes 14 to 20, wherein, when the first indication information is not included in the first RRC reconfiguration message or the third RRC reconfiguration message, the IAB node determines that the IP address configuration includes the IP address information of the F1 end-point topology domain.
[0370] 22. The method according to Note 13, wherein the first indication information is included in a newly added information element of the first RRC reconfiguration message or the second RRC reconfiguration message, or included in the IP address configuration list information element of the first RRC reconfiguration message or the second RRC reconfiguration message, or included in the IP address configuration information element of the first RRC reconfiguration message or the second RRC reconfiguration message, or included in the IP address index information element of the first RRC reconfiguration message or the second RRC reconfiguration message.
[0371] 23. An IAB node (donor) device, comprising a memory and a processor, wherein the memory stores a computer program, wherein the processor is configured to execute the computer program to implement the transmission address determination method as described in any one of Notes 1 to 22.
[0372] First donor CU node side
[0373] 1. A method for determining a transport address, applied to a first IAB host, comprising:
[0374] The first IAB host sends a first RRC reconfiguration message, where the first RRC reconfiguration message includes at least one IP address configuration for the IAB node; or sends the IP address configuration of at least one of the IAB nodes;
[0375] The at least one IP address configuration includes IP address information of an F1 termination point topology domain, or includes IP address information of a non-F1 termination point topology domain;
[0376] The F1 connection of the IAB node is terminated at the first IAB host, and the IAB node has an RRC connection with a second IAB host.
[0377] 2. The method according to Note 1, wherein the first IAB host indicates through first indication information that the IP address configuration includes IP address information of an F1 termination point topology domain, or includes IP address information of a non-F1 termination point topology domain.
[0378] 3. The method according to Note 1 or 2, wherein the IP address configuration includes IP address information of a non-F1 termination point topology domain.
[0379] 4. The method according to Note 3, wherein the first IAB host is a source host of the IAB node handover, the second IAB host is a target host of the IAB node handover, and the first RRC reconfiguration message is a handover command RRC message;
[0380] The first IAB host receives the first RRC reconfiguration message sent by the second IAB host, and forwards the first RRC reconfiguration message generated by the second IAB host to the IAB node.
[0381] 5. The method according to Note 3, wherein the first IAB host is a master node MN of the IAB node, and the second IAB host is a secondary node SN of the IAB node.
[0382] 6. The method according to Note 5, wherein the first RRC reconfiguration message is an RRC reconfiguration message included in a secondary cell group configuration field in the RRC reconfiguration message and carried by a second RRC reconfiguration message sent by the first IAB host;
[0383] The first IAB host sends the second RRC reconfiguration message to the IAB node through SRB1.
[0384] 7. The method according to Supplementary Note 6, wherein the method further comprises:
[0385] The first IAB host receives the first RRC reconfiguration message sent by the second IAB host.
[0386] 8. The method according to Supplementary Note 6, further comprising:
[0387] The first IAB host receives the IP address configuration provided by the second IAB host, and generates the first RRC reconfiguration message on behalf of the second IAB host.
[0388] 9. The method according to Supplementary Note 5, further comprising:
[0389] The first IAB host receives the IP address configuration provided by the second IAB host, and sends the first RRC reconfiguration message through SRB1.
[0390] 10. A method according to any one of Notes 3 to 9, wherein the first IAB host includes the first indication information through the first RRC reconfiguration message or the second RRC reconfiguration message to indicate that the IP address configuration includes IP address information of a non-F1 end-point topology domain.
[0391] 11. The method according to Note 1 or 2, wherein the IP address configuration includes IP address information of the F1 termination point topology domain.
[0392] 12. The method according to note 11, wherein the first IAB host is the SN of the IAB node, and the second IAB host is the MN of the IAB node.
[0393] 13. The method according to Supplement 12, wherein:
[0394] The first IAB host sends the first RRC reconfiguration message to the IAB node through SRB3.
[0395] 14. The method according to Note 12, wherein the first IAB host sends the first RRC reconfiguration message to the second IAB host, wherein the first RRC reconfiguration message is a secondary cell group configuration RRC message; or
[0396] The first IAB host sends the IP address configuration to the second IAB host.
[0397] 15. The method according to Supplementary Note 11, wherein the first IAB host is a master node MN of the IAB node, and the second IAB host is a secondary node SN of the IAB node;
[0398] The first IAB host sends the first RRC reconfiguration message to the IAB node through SRB1.
[0399] 17. The method according to any one of Notes 11 to 15, wherein the first IAB host indicates that the IP address configuration includes IP address information of the F1 end-point topology domain through the first RRC reconfiguration message not including the first indication information.
[0400] 18. The method according to Note 10, wherein the first indication information is included in a newly added information element of the first RRC reconfiguration message or the second RRC reconfiguration message, or included in the IP address configuration list information element of the first RRC reconfiguration message or the second RRC reconfiguration message, or included in the IP address configuration information element of the first RRC reconfiguration message or the second RRC reconfiguration message, or included in the IP address index information element of the first RRC reconfiguration message or the second RRC reconfiguration message.
[0401] 19. An IAB donor device, comprising a memory and a processor, wherein the memory stores a computer program, wherein the processor is configured to execute the computer program to implement the transmission address determination method as described in any one of Notes 1 to 17.
[0402] Second donor CU node side
[0403] 1. A method for determining a transport address, applied to a second IAB host, comprising:
[0404] The second IAB host sends a first RRC reconfiguration message, where the first RRC reconfiguration message includes at least one IP address configuration for the IAB node; or sends at least one IP address configuration for the IAB node;
[0405] The at least one IP address configuration includes IP address information of an F1 termination point topology domain, or includes IP address information of a non-F1 termination point topology domain.
[0406] The F1 connection of the IAB node is terminated at the first IAB host, and the IAB node has an RRC connection with the second IAB host.
[0407] 2. The method according to Note 1, wherein the second IAB host indicates through the first indication information that the IP address configuration includes IP address information of an F1 termination point topology domain, or includes IP address information of a non-F1 termination point topology domain.
[0408] 3. The method according to Note 1 or 2, wherein the IP address configuration includes IP address information of a non-F1 termination point topology domain.
[0409] 4. The method according to Note 3, wherein the first IAB host is a source host of the IAB node handover, the second IAB host is a target host of the IAB node handover, the first RRC reconfiguration message is a handover command RRC message, and
[0410] The second IAB host sends the first RRC reconfiguration message to the first IAB host.
[0411] 5. The method according to Note 3, wherein the first IAB host is a master node MN of the IAB node, and the second IAB host is a secondary node SN of the IAB node.
[0412] 6. The method according to Note 5, wherein the second IAB host sends a first RRC reconfiguration message to the first IAB host; or
[0413] Send the IP address configuration to the first IAB host.
[0414] 7. The method according to Note 5, wherein the second IAB host sends the first RRC reconfiguration message to the IAB node via SRB3.
[0415] 8. The method according to Supplementary Note 3, wherein the first IAB host is the SN of the IAB node, and the second IAB host is the MN of the IAB node;
[0416] The second IAB host sends the first RRC reconfiguration message to the IAB node through SRB1.
[0417] 9. The method according to any one of Notes 3 to 8, wherein the second IAB host includes the first indication information through the first RRC reconfiguration message to indicate that the IP address configuration includes IP address information of a non-F1 end-point topology domain.
[0418] 10. The method according to Note 1 or 2, wherein the IP address configuration includes IP address information of the F1 termination point topology domain.
[0419] 11. The method according to note 10, wherein the first IAB host is the SN of the IAB node, and the second IAB host is the MN of the IAB node.
[0420] 12. The method according to Note 11, wherein the first RRC reconfiguration message is an RRC reconfiguration message included in a secondary cell group configuration field in the RRC reconfiguration message and is carried by a third RRC reconfiguration message sent by the second IAB host;
[0421] The second IAB host sends the third RRC reconfiguration message to the IAB node through SRB1.
[0422] 13. The method according to Supplementary Note 12, further comprising:
[0423] The second IAB host receives a first RRC reconfiguration message sent by the first IAB host.
[0424] 14. The method according to Note 12, wherein the second IAB host receives the IP address configuration provided by the first IAB host, and generates the first RRC reconfiguration message on behalf of the first IAB host.
[0425] 15. The method according to Supplementary Note 11, further comprising:
[0426] The second IAB host receives the IP address configuration sent by the first IAB host, and sends the first RRC reconfiguration message to the IAB node through SRB1.
[0427] 16. A method according to any one of Notes 11 to 15, wherein the second IAB host indicates that the IP address configuration includes IP address information of the F1 termination point topology domain through the first RRC reconfiguration message or the third RRC reconfiguration message without including the first indication information.
[0428] 17. The method according to Note 9, wherein the first indication information is included in a newly added information element of the first RRC reconfiguration message or the second RRC reconfiguration message, or included in the IP address configuration list information element of the first RRC reconfiguration message or the second RRC reconfiguration message, or included in the IP address configuration information element of the first RRC reconfiguration message or the second RRC reconfiguration message, or included in the IP address index information element of the first RRC reconfiguration message or the second RRC reconfiguration message.
[0429] 18. An IAB donor device, comprising a memory and a processor, wherein the memory stores a computer program, wherein the processor is configured to execute the computer program to implement the transmission address determination method as described in any one of Notes 1 to 17.
[0430] Boundary Node
[0431] 1. An IAB node device, comprising:
[0432] a first receiving unit configured to receive a first RRC reconfiguration message, where the first RRC reconfiguration message includes at least one IP address configuration for the IAB node;
[0433] The at least one IP address configuration includes IP address information of an F1 termination point topology domain, or includes IP address information of a non-F1 termination point topology domain.
[0434] 2. The apparatus according to note 1, wherein the F1 connection of the IAB node is terminated at a first IAB host, and the IAB node has an RRC connection with a second IAB host.
[0435] 3. The device according to Supplementary Note 2, wherein the device further comprises:
[0436] The first processing unit determines whether the IP address configuration includes the IP address information of the F1 termination point topology domain or the IP address information of the non-F1 termination point topology domain.
[0437] 4. The device according to Note 3, wherein the first processing unit determines, based on the first indication information, that the IP address configuration includes IP address information of an F1 termination point topology domain or IP address information of a non-F1 termination point topology domain.
[0438] 5. The device according to Note 3 or 4, wherein the first processing unit determines that the IP address configuration includes IP address information of a non-F1-terminating topological domain.
[0439] 6. The device according to Supplementary Note 5, wherein the first IAB host is a source host of the IAB node handover, and the second IAB host is a target host of the IAB node handover;
[0440] The first RRC reconfiguration message is a handover command RRC message generated by the second IAB host and forwarded by the first IAB host.
[0441] 7. The device according to note 5, wherein the first IAB host is a master node MN of the IAB node, and the second IAB host is a secondary node SN of the IAB node.
[0442] 8. The device according to Note 7, wherein the first RRC reconfiguration message is an RRC reconfiguration message included in a secondary cell group configuration field in the RRC reconfiguration message and is carried by a second RRC reconfiguration message sent by the first IAB host;
[0443] The first receiving unit receives the second RRC reconfiguration message sent by the first IAB host through SRB1.
[0444] 9. The device according to Note 8, wherein the first RRC reconfiguration message is generated by the first IAB host instead of the second IAB host.
[0445] 10. The device according to Note 7, wherein the first receiving unit receives the first RRC reconfiguration message sent by the second IAB host through SRB3.
[0446] 11. The device according to Note 7, wherein the first receiving unit receives the first RRC reconfiguration message sent by the first IAB host through SRB1.
[0447] 12. The device according to Supplementary Note 5, wherein the first IAB host is a SN of the IAB node, and the second IAB host is a MN of the IAB node;
[0448] The first receiving unit receives the first RRC reconfiguration message sent by the second IAB host through SRB1.
[0449] 13. The device according to any one of Notes 5 to 12, wherein the first processing unit determines that the IP address configuration includes IP address information of a non-F1 end-point topology domain when the first indication information is included in the first RRC reconfiguration message or the second RRC reconfiguration message.
[0450] 14. The device according to Note 3 or 4, wherein the first processing unit determines that the IP address configuration includes IP address information of an F1-terminating topology domain.
[0451] 15. The device according to supplementary note 14, wherein the first IAB host is a master node MN of the IAB node, and the second IAB host is a secondary node SN of the IAB node;
[0452] The first receiving unit receives the first RRC reconfiguration message sent by the first IAB host through SRB1.
[0453] 16. The device according to note 11, wherein the first IAB host is a SN of the IAB node, and the second IAB host is a MN of the IAB node.
[0454] 17. The device according to note 16, wherein the first RRC reconfiguration message is an RRC reconfiguration message included in a secondary cell configuration field in the RRC reconfiguration message and is carried by a third RRC reconfiguration message sent by the second IAB host;
[0455] The first receiving unit receives the third RRC reconfiguration message sent by the second IAB host through SRB1.
[0456] 18. The device according to Note 17, wherein the first RRC reconfiguration message is generated by the second IAB host instead of the first IAB host.
[0457] 19. The device according to Note 16, wherein the first receiving unit receives the first RRC reconfiguration message sent by the first IAB host through SRB3.
[0458] 20. The device according to Note 16, wherein the first receiving unit receives the first RRC reconfiguration message sent by the second IAB host through SRB1.
[0459] 21. The device according to any one of Notes 14 to 20, wherein the first processing unit determines that the IP address configuration includes IP address information of the F1 end-point topology domain when the first indication information is not included in the first RRC reconfiguration message or the third RRC reconfiguration message.
[0460] 22. The device according to Note 13, wherein the first indication information is contained in a newly added information element of the first RRC reconfiguration message or the second RRC reconfiguration message, or is contained in the IP address configuration list information element of the first RRC reconfiguration message or the second RRC reconfiguration message, or is contained in the IP address configuration information element of the first RRC reconfiguration message or the second RRC reconfiguration message, or is contained in the IP address index information element of the first RRC reconfiguration message or the second RRC reconfiguration message.
[0461] First donor CU node side
[0462] 1. An IAB host device, applied to a first IAB host, characterized in that the device comprises:
[0463] A first sending unit, configured to send a first RRC reconfiguration message, wherein the first RRC reconfiguration message includes at least one IP address configuration for an IAB node; or send at least one IP address configuration of the IAB node;
[0464] The at least one IP address configuration includes IP address information of an F1 termination point topology domain, or includes IP address information of a non-F1 termination point topology domain;
[0465] The F1 connection of the IAB node is terminated at the first IAB host, and the IAB node has an RRC connection with a second IAB host.
[0466] 2. The device according to Note 1, wherein the IAB host device indicates through first indication information that the IP address configuration includes IP address information of an F1 termination point topology domain, or includes IP address information of a non-F1 termination point topology domain.
[0467] 3. The device according to Note 1 or 2, wherein the IP address configuration includes IP address information of a non-F1 termination point topology domain.
[0468] 4. The device according to Supplementary Note 3, wherein the first IAB host is a source host of the IAB node handover, the second IAB host is a target host of the IAB node handover, and the first RRC reconfiguration message is a handover command RRC message;
[0469] The device further includes: a second receiving unit configured to receive a first RRC reconfiguration message sent by the second IAB host, and the first sending unit forwards the first RRC reconfiguration message generated by the second IAB host to the IAB node.
[0470] 5. The device according to note 3, wherein the first IAB host is a master node MN of the IAB node, and the second IAB host is a secondary node SN of the IAB node.
[0471] 6. The device according to note 5, wherein the first RRC reconfiguration message is an RRC reconfiguration message included in a secondary cell configuration field in the RRC reconfiguration message and is carried by a second RRC reconfiguration message sent by the first IAB host;
[0472] The first sending unit sends the second RRC reconfiguration message to the IAB node through SRB1.
[0473] 7. The device according to Supplementary Note 6, wherein the device further comprises:
[0474] A third receiving unit is configured to receive the first RRC reconfiguration message sent by the second IAB host.
[0475] 8. The device according to Supplementary Note 6, wherein the device further comprises:
[0476] a fourth receiving unit, configured to receive the IP address configuration provided by the second IAB host;
[0477] A second processing unit is configured to generate the first RRC reconfiguration message on behalf of the second IAB host.
[0478] 9. The device according to Supplementary Note 5, wherein the device further comprises:
[0479] A fifth receiving unit receives the IP address configuration provided by the second IAB host, and the first sending unit sends the first RRC reconfiguration message through SRB1.
[0480] 10. The device according to any one of Notes 3 to 9, wherein the IAB host device includes the first indication information through the first RRC reconfiguration message or the second RRC reconfiguration message to indicate that the IP address configuration includes IP address information of a non-F1 end-point topology domain.
[0481] 11. The device according to Note 1 or 2, wherein the IP address configuration includes IP address information of the F1 termination point topology domain.
[0482] 12. The device according to note 11, wherein the first IAB host is a SN of the IAB node, and the second IAB host is a MN of the IAB node.
[0483] 13. The device according to Note 12, wherein:
[0484] The first sending unit sends the first RRC reconfiguration message to the IAB node through SRB3.
[0485] 14. The device according to note 12, wherein the first sending unit sends the first RRC reconfiguration message to the second IAB host, wherein the first RRC reconfiguration message is a secondary cell configuration RRC message; or
[0486] The first sending unit sends the IP address configuration to the second IAB host.
[0487] 15. The device according to supplementary note 11, wherein the first IAB host is a master node MN of the IAB node, and the second IAB host is a secondary node SN of the IAB node;
[0488] The first sending unit sends the first RRC reconfiguration message to the IAB node through SRB1.
[0489] 17. The device according to any one of Notes 11 to 15, wherein the IAB host device indicates that the IP address configuration includes IP address information of the F1 end-point topology domain by not including the first indication information through the first RRC reconfiguration message.
[0490] 18. The device according to Note 10, wherein the first indication information is contained in a newly added information element of the first RRC reconfiguration message or the second RRC reconfiguration message, or is contained in the IP address configuration list information element of the first RRC reconfiguration message or the second RRC reconfiguration message, or is contained in the IP address configuration information element of the first RRC reconfiguration message or the second RRC reconfiguration message, or is contained in the IP address index information element of the first RRC reconfiguration message or the second RRC reconfiguration message.
[0491] Second donor CU node side
[0492] 1. An IAB host device, used as a second IAB host, comprising:
[0493] a second sending unit configured to send a first RRC reconfiguration message, wherein the first RRC reconfiguration message includes at least one IP address configuration for an IAB node; or to send at least one IP address configuration for an IAB node;
[0494] The at least one IP address configuration includes IP address information of an F1 termination point topology domain, or includes IP address information of a non-F1 termination point topology domain.
[0495] The F1 connection of the IAB node is terminated at the first IAB host, and the IAB node has an RRC connection with the second IAB host.
[0496] 2. The device according to Note 1, wherein the IAB host device indicates through first indication information that the IP address configuration includes IP address information of an F1 termination point topology domain, or includes IP address information of a non-F1 termination point topology domain.
[0497] 3. The device according to Note 1 or 2, wherein the IP address configuration includes IP address information of a non-F1 termination point topology domain.
[0498] 4. The device according to Note 3, wherein the first IAB host is a source host of the IAB node handover, the second IAB host is a target host of the IAB node handover, the first RRC reconfiguration message is a handover command RRC message, and
[0499] The second sending unit sends the first RRC reconfiguration message to the first IAB host.
[0500] 5. The device according to note 3, wherein the first IAB host is a master node MN of the IAB node, and the second IAB host is a secondary node SN of the IAB node.
[0501] 6. The device according to Supplement 5, wherein the second sending unit sends a first RRC reconfiguration message to the first IAB host; or
[0502] Send the IP address configuration to the first IAB host.
[0503] 7. The device according to Note 5, wherein the second sending unit sends the first RRC reconfiguration message to the IAB node via SRB3.
[0504] 8. The device according to Supplementary Note 3, wherein the first IAB host is a SN of the IAB node, and the second IAB host is a MN of the IAB node;
[0505] The second sending unit sends the first RRC reconfiguration message to the IAB node through SRB1.
[0506] 9. The device according to any one of Notes 3 to 8, wherein the IAB host device includes the first indication information through the first RRC reconfiguration message to indicate that the IP address configuration includes IP address information of a non-F1 end-point topology domain.
[0507] 10. The device according to Note 1 or 2, wherein the IP address configuration includes IP address information of the F1 termination point topology domain.
[0508] 11. The device according to supplementary note 10, wherein the first IAB host is a SN of the IAB node, and the second IAB host is a MN of the IAB node.
[0509] 12. The device according to note 11, wherein the first RRC reconfiguration message is an RRC reconfiguration message included in a secondary cell configuration field in the RRC reconfiguration message and is carried by a third RRC reconfiguration message sent by the second IAB host;
[0510] The second sending unit sends the third RRC reconfiguration message to the IAB node through SRB1.
[0511] 13. The device according to Supplementary Note 12, wherein the device further comprises:
[0512] A sixth receiving unit is configured to receive a first RRC reconfiguration message sent by the first IAB host.
[0513] 14. The device according to Note 12, wherein the device further comprises:
[0514] a seventh receiving unit, configured to receive the IP address configuration provided by the first IAB host;
[0515] A third processing unit is configured to generate the first RRC reconfiguration message on behalf of the first IAB host.
[0516] 15. The device according to Supplementary Note 11, wherein the device further comprises:
[0517] An eighth receiving unit receives the IP address configuration sent by the first IAB host, and the second sending unit sends the first RRC reconfiguration message to the IAB node through SRB1.
[0518] 16. The device according to any one of Notes 11 to 15, wherein the IAB host device indicates that the IP address configuration includes IP address information of the F1 termination point topology domain through the first RRC reconfiguration message or the third RRC reconfiguration message without including the first indication information.
[0519] 17. The device according to Note 9, wherein the first indication information is included in a newly added information element of the first RRC reconfiguration message or the second RRC reconfiguration message, or included in the IP address configuration list information element of the first RRC reconfiguration message or the second RRC reconfiguration message, or included in the IP address configuration information element of the first RRC reconfiguration message or the second RRC reconfiguration message, or included in the IP address index information element of the first RRC reconfiguration message or the second RRC reconfiguration message.
Claims
1. An integrated access and backhaul IAB node device, characterized in that: The device comprises: a first receiving unit configured to receive a first RRC reconfiguration message, where the first RRC reconfiguration message includes at least one IP address configuration for the IAB node; The at least one IP address configuration includes IP address information of an F1 termination point topology domain, or includes IP address information of a non-F1 termination point topology domain.
2. The device according to claim 1, wherein The F1 connection of the IAB node is terminated at a first IAB host, and the IAB node has an RRC connection with a second IAB host.
3. The device according to claim 2, wherein The device further comprises: The first processing unit determines whether the IP address configuration includes the IP address information of the F1 termination point topology domain or the IP address information of the non-F1 termination point topology domain.
4. The device according to claim 3, wherein The first processing unit determines, according to the first indication information, that the IP address configuration includes IP address information of an F1 termination point topology domain or IP address information of a non-F1 termination point topology domain.
5. The device according to claim 3 or 4, wherein The first processing unit determines that the IP address configuration includes IP address information of a non-F1-terminating topology domain.
6. The device according to claim 5, wherein The first IAB host is a master node MN of the IAB node, and the second IAB host is a secondary node SN of the IAB node.
7. The apparatus according to claim 6, wherein The first RRC reconfiguration message is an RRC reconfiguration message included in the secondary cell group configuration field in the RRC reconfiguration message and is carried by a second RRC reconfiguration message sent by the first IAB host; The first receiving unit receives the second RRC reconfiguration message sent by the first IAB host through SRB1.
8. The apparatus according to claim 5, wherein The first IAB host is the SN of the IAB node, and the second IAB host is the MN of the IAB node; The first receiving unit receives the first RRC reconfiguration message sent by the second IAB host through SRB1.
9. The apparatus according to claim 5, wherein When the first RRC reconfiguration message or the second RRC reconfiguration message includes the first indication information, the first processing unit determines that the IP address configuration includes IP address information of a non-F1 end-point topology domain.
10. The apparatus according to claim 3 or 4, wherein: The first processing unit determines that the IP address configuration includes IP address information of an F1-terminating topology domain.
11. The apparatus according to claim 10, wherein The first IAB host is the SN of the IAB node, and the second IAB host is the MN of the IAB node.
12. The apparatus according to claim 11, wherein The first RRC reconfiguration message is an RRC reconfiguration message included in the secondary cell configuration field in the RRC reconfiguration message and is carried by a third RRC reconfiguration message sent by the second IAB host; The first receiving unit receives the third RRC reconfiguration message sent by the second IAB host through SRB1.
13. The apparatus according to claim 12, wherein When the first RRC reconfiguration message or the third RRC reconfiguration message does not include the first indication information, the first processing unit determines that the IP address configuration includes the IP address information of the F1 end point topology domain.
14. The apparatus according to claim 5, wherein The first IAB host is a source host of the IAB node switching, and the second IAB host is a target host of the IAB node switching; The first RRC reconfiguration message is a handover command RRC message generated by the second IAB host and forwarded by the first IAB host.
15. The apparatus according to claim 7, wherein The first RRC reconfiguration message is generated by the first IAB host instead of the second IAB host.
16. The apparatus according to claim 12, wherein The first RRC reconfiguration message is generated by the second IAB host instead of the first IAB host.
17. The apparatus according to claim 9, wherein The first indication information is included in a newly added information element of the first RRC reconfiguration message or the second RRC reconfiguration message, or included in the IP address configuration list information element of the first RRC reconfiguration message or the second RRC reconfiguration message, or included in the IP address configuration information element of the first RRC reconfiguration message or the second RRC reconfiguration message, or included in the IP address index information element of the first RRC reconfiguration message or the second RRC reconfiguration message.
18. The apparatus according to claim 10, wherein The first IAB host is a master node MN of the IAB node, and the second IAB host is a secondary node SN of the IAB node; The first receiving unit receives the first RRC reconfiguration message sent by the first IAB host through SRB1.
19. An integrated access and backhaul IAB host device, applied to a first IAB host, characterized in that: The device comprises: A first sending unit, configured to send a first RRC reconfiguration message, wherein the first RRC reconfiguration message includes at least one IP address configuration for an IAB node; or send at least one IP address configuration of the IAB node; The at least one IP address configuration includes IP address information of an F1 termination point topology domain, or includes IP address information of a non-F1 termination point topology domain; The F1 connection of the IAB node is terminated at the first IAB host.
20. An integrated access and backhaul IAB host device, applied to a second IAB host, characterized in that: The device comprises: a second sending unit configured to send a first RRC reconfiguration message, wherein the first RRC reconfiguration message includes at least one IP address configuration for an IAB node; or to send at least one IP address configuration for an IAB node; The at least one IP address configuration includes IP address information of an F1 termination point topology domain, or includes IP address information of a non-F1 termination point topology domain. The F1 connection of the IAB node is terminated at the first IAB host.
