Method and apparatus for updating authorization status of mobile iab node

Abstract

Embodiments of the present application provide a method and apparatus for updating an authorized state of a mobile IAB node, the method comprising: receiving, by a first node, an XnAP message sent by a second node; and determining, by the first node, whether the second node has completed handover of a terminal device served by a mobile IAB node that is not authorized and / or release of an F1 interface of the mobile IAB node that is not authorized based on the XnAP message.

Description

Method and device for updating authorization status of mobile IAB node Technical Field

[0001] The present application relates to the field of communications. Background Art

[0002] Integrated access and backhaul (IAB) implements the wireless relay function in the next generation radio access network (NG-RAN). This relay node is called an IAB-node, which supports both access and backhaul (BH) through 5G NR (new radio). All IAB nodes are connected to an IAB-donor node through one or more hops. These multi-hop connections form a directed acyclic graph (DAG) topology with the IAB-donor node as the root node. The IAB-donor node is responsible for performing centralized resource management, topology management, and routing management in the IAB network topology.

[0003] The IAB node supports the functions of the gNB-distributed unit (gNB-DU), referred to as the IAB-DU, and can serve both standard UEs (user equipment) and IAB child nodes. The IAB node also supports some UE functions and is referred to as the IAB-MT (mobile termination). The IAB-MT supports functions such as the UE physical layer, access stratum (AS), radio resource control (RRC), and non-access stratum (NAS), and can connect to the IAB parent node. The network-side termination node, referred to as the IAB-donor, provides network access for the IAB-MT or UE via backhaul or access links. The IAB-donor is further divided into the IAB-donor-CU (central unit) and the IAB-donor-DU. The IAB-DU and IAB-donor-CU are connected via the F1 interface. In standalone networking scenarios, the gNB and IAB-donor-CU are connected via the Xn interface.

[0004] To support multi-hop routing of data packets, IAB introduces the BAP (Backhaul Adaptation Protocol) sublayer. Located above the RLC (radio link control) sublayer and below the IP (Internet Protocol) layer, the BAP sublayer supports functions such as selecting the destination node and path for data packets, routing and forwarding data packets, bearer mapping, flow control feedback, and notification of backhaul link failures.

[0005] In multi-hop scenarios, to relay data packets, the IAB node needs to determine the destination node for the packet, then determine the next hop node corresponding to the destination node based on the routing table and send the packet. In this scenario, the IAB-donor-CU (abbreviated as donor-CU, CU, or gNB-CU) configures the mapping of each F1-U (F1 user plane) tunnel, each non-UE associated F1AP message, each UE-associated F1AP message, and each non-F1 traffic message to a BAP routing identifier for uplink transmissions initiated from the IAB node via F1AP (F1 Application Protocol) signaling. The IAB node determines the BAP routing identifier corresponding to different types of uplink IP packets initiated from the IAB node based on this routing identifier mapping information and encapsulates these uplink IP packets with a BAP subheader containing the BAP routing identifier information. The IAB-donor-CU configures the mapping of different types of downlink data packets to BAP routing identifiers for the IAB-donor-DU (abbreviated as donor-DU) through F1AP signaling. The IAB-donor-DU determines the BAP routing identifier corresponding to the received downlink IP packets based on the routing identifier mapping information and encapsulates the BAP subheader containing the BAP routing identifier information for these downlink IP packets.

[0006] The BAP routing identifier includes the destination BAP address and the path identity from the IAB node to the IAB-donor-DU. The BAP address is also called the destination in the BAP header. Each IAB node and IAB-donor-DU is configured with a BAP address.

[0007] A mobile IAB (mIAB) node, also known as a Mobile Base Station Relay (MBSR), utilizes the IAB architecture and operates as a mobile IAB node when integrated into a serving PLMN (Public Land Mobile Network).

[0008] For the mobile IAB node, the subscription information stored in the HPLMN (Home PLMN) indicates whether it is authorized to operate as a mobile IAB node, as well as the corresponding location and time period. When the mobile IAB node (mIAB-MT) performs initial registration with the serving PLMN, it indicates a request to act as a mobile IAB node. The AMF (Access and Mobility Management Function) authorizes the mobile IAB node based on the subscription information, and provides a mobile IAB authorization indication to the mobile IAB node through the NAS, and to the NG-RAN through the NGAP (NG Application Protocol). When the mobile IAB node receives the authorization indication (authorized), it uses the configuration information for the mobile IAB operation to establish a connection to the OAM (Operation Administration and Maintenance) system.

[0009] It should be noted that the above introduction to the technical background is merely intended to provide a clear and complete description of the technical solutions of this application and facilitate understanding by those skilled in the art. Simply because these solutions are described in the background technology section of this application, it should not be assumed that the above technical solutions are well known to those skilled in the art.

[0010] Summary of the Invention

[0011] The inventors discovered that the mobility of a mobile IAB node or mobile relay over a large area faces a challenge: during movement, the authorization status of the mobile IAB node may frequently change due to location changes or time constraints, which can cause changes in the mobile IAB node's behavior. For example, when the authorization status changes to "unauthorized," the mobile IAB node must perform relevant operations to ensure that it does not serve any UEs. Conversely, when the authorization status changes to "authorized," the mobile IAB node must perform relevant operations to enable the function of serving UEs. However, currently, there is no definition of the process and behavior of a mobile IAB node when its authorization status changes, making it impossible to support the correct operation of the mobile IAB node under authorization status changes.

[0012] In response to at least one of the above problems or similar problems or similar problems in other scenarios, embodiments of the present application provide a method and apparatus for updating the authorization status of a mobile IAB node.

[0013] According to one aspect of an embodiment of the present application, a device for updating the authorization status of a mobile IAB node is provided, which is configured at a first node, wherein the device includes:

[0014] a first receiving unit, configured to receive an XnAP message sent by the second node;

[0015] A processing unit is configured to confirm, based on the XnAP message, whether the second node has completed the handover of the terminal device served by the unauthorized mobile IAB node and / or the release of the F1 interface of the unauthorized mobile IAB node.

[0016] According to another aspect of an embodiment of the present application, there is provided an apparatus for updating the authorization status of a mobile IAB node, configured at a first node, wherein the apparatus includes:

[0017] a receiving unit, configured to receive a first NGAP message sent by the AMF;

[0018] A processing unit is configured to establish a backhaul resource for the mobile IAB node when the first NGAP message includes an authorization status of the mobile IAB node with a value of "authorized", so that the mobile IAB node establishes an F1 connection with the second node using the backhaul resource.

[0019] According to another aspect of an embodiment of the present application, a device for updating the authorization status of a mobile IAB node is provided, which is configured in the mobile IAB node, wherein the device includes:

[0020] A sending unit, which sends a new authorization indication to the AS layer when receiving a UE configuration update command sent by the AMF and the UE configuration update command includes an IAB authorization status with a value of "authorized".

[0021] According to another aspect of an embodiment of the present application, a broadcast message apparatus supporting a mobile IAB node is provided, which is configured at a parent node of the mobile IAB node, wherein the apparatus includes:

[0022] a sending unit configured to send a SIB1 broadcast message, wherein the SIB1 broadcast message includes cell identification information, and the SIB1 broadcast message includes a mobileIAB-Support field and a gNB-ID-Length field, where the gNB-ID-Length field is optional;

[0023] Among them, when the mobileIAB-Support field in the SIB1 broadcast message appears, the gNB-ID-Length field in the SIB1 broadcast message must also appear.

[0024] One of the beneficial effects of the embodiments of the present application is that: according to the embodiments of the present application, the authorization problem of the mobile IAB node is solved, especially the authorization problem of the mobile IAB node when the mAB-MT and the collocated mAB-DU are connected to different donor-CUs.

[0025] With reference to the following description and accompanying drawings, specific embodiments of the present application are disclosed in detail, indicating the manner in which 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 appended claims, the embodiments of the present application include many variations, modifications and equivalents.

[0026] 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.

[0027] 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

[0028] 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.

[0029] 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:

[0030] FIG1 is a schematic diagram of an example of an IAB network topology;

[0031] FIG2 is a schematic diagram of a method for updating the authorization status of a mobile IAB node according to an embodiment of the present application;

[0032] FIG3 is a schematic diagram of another example of an IAB network topology;

[0033] FIG4 is a schematic diagram of a method for updating the authorization status of a mobile IAB node according to an embodiment of the present application;

[0034] FIG5 is a schematic diagram of a method for updating the authorization status of a mobile IAB node according to an embodiment of the present application;

[0035] FIG6 is a schematic diagram of a method for supporting broadcast messages of a mobile IAB node according to an embodiment of the present application;

[0036] FIG7 is a schematic diagram of a device for updating the authorization status of a mobile IAB node according to an embodiment of the present application;

[0037] FIG8 is another schematic diagram of a device for updating the authorization status of a mobile IAB node according to an embodiment of the present application;

[0038] FIG9 is another schematic diagram of an apparatus for updating the authorization status of a mobile IAB node according to an embodiment of the present application;

[0039] FIG10 is a schematic diagram of a broadcast message apparatus supporting a mobile IAB node according to an embodiment of the present application;

[0040] FIG11 is a schematic diagram of an IAB-donor node according to an embodiment of the present application;

[0041] FIG12 is a schematic diagram of an IAB node according to an embodiment of the present application. DETAILED DESCRIPTION

[0042] 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 the accompanying drawings, specific embodiments of the present application are disclosed in detail, which illustrate 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 appended claims.

[0043] 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.

[0044] 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.

[0045] 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 Long Term Evolution (LTE), enhanced Long Term Evolution (LTE-A, LTE-Advanced), Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), etc.

[0046] 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, New Radio (NR), etc., and / or other currently known or future communication protocols to be developed.

[0047] 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.

[0048] Base stations may include, but are not limited to, NodeB (NB), evolved NodeB (eNodeB or eNB), 5G base stations (gNB), NG-RAN nodes, IAB-donors, and more. 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.

[0049] 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.

[0050] Terminal devices may include, but are not limited to, cellular phones, personal digital assistants (PDAs), wireless modems, wireless communication devices, handheld devices, machine-type communication devices, laptop computers, cordless phones, smartphones, smart watches, digital cameras, and IAB-MT, etc.

[0051] 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.

[0052] In 3GPP TS 23.501, the AMF can notify the mobile IAB node (mIAB-MT) about its authorization status. This notification is implemented through NAS signaling. If the mobile IAB node is not authorized, the AMF can use the Mobile IAB Authorization Indication (not authorized) during the registration process to indicate to the mobile IAB node (mIAB-MT) that it is not allowed to operate as a mobile IAB node. In this case, the AMF also includes the Mobile IAB Authorization Indication (not authorized) to the donor-gNB (IAB-donor).

[0053] The inventors found that based on the needs of network coverage and QoS support, the F1 termination host and non-F1 termination host of the IAB node may be different, that is, the MT and DU of the IAB node may terminate at different IAB-donor-CUs.

[0054] FIG1 is a schematic diagram of an example of an IAB network topology structure, showing a situation where the MT and DU of an mIAB node (IAB node 1 in FIG1 ) are terminated to different donor-CUs.

[0055] The F1-terminating node refers to the donor-CU that terminates the F1 interface of the IAB node, such as donor-CU2 in Figure 1. In Figure 1, IAB-DU1 is terminated to donor-CU2 via an F1 connection, so donor-CU2 is the F1-terminating node of IAB node 1. The F1-terminating donor-CU is also called the donor-CU of the IAB-DU because the IAB-DU is configured by this CU.

[0056] Furthermore, a non-F1-terminating node refers to a CU with host functionality that does not terminate the F1 interface of an IAB node, such as donor-CU1 shown in Figure 1. Because a non-F1-terminating node has an RRC connection with the IAB-MT, a non-F1-terminating node can also be called a host node serving the IAB-MT, and a non-F1-terminating host CU can also be called an IAB-MT host CU or an RRC-terminating donor CU of an IAB node.

[0057] In Figure 1, IAB-MT1 is connected to its parent node, IAB Node 2, which then connects to donor-DU1 and donor-CU1. IAB-DU1 and donor-CU2 establish an F1 connection, but this F1 connection passes through IAB Node 2, donor-DU1, and ultimately to donor-CU2.

[0058] In the embodiments of this application, taking a 5G multi-hop IAB network deployment as an example, multiple UEs connect to an IAB-donor through multi-hop IAB nodes and ultimately access the 5G network. The IAB node to which the UE is connected can be mobile. When the mobile IAB node's MT and DU are connected to different IAB-donor-CUs, how do the nodes in the IAB network operate to ensure the correct configuration and operation of the mobile IAB node when the authorization status of the mIAB-MT changes?

[0059] In the embodiments of this application, a mobile IAB node is used as an example for illustration, but the application is not limited thereto. All embodiments of this application are also applicable to ordinary IAB nodes (non-mobile IAB nodes). That is, the descriptions in the following embodiments also apply to ordinary IAB nodes. For ordinary IAB nodes, the "authorization status information" described below refers to the IAB authorization status. The rest of the description is the same as for mobile IAB nodes.

[0060] Various embodiments of the present application are described below with reference to the accompanying drawings. These embodiments are merely illustrative and are not intended to limit the present application. In the following description, expressions such as "if...", "in the case of...", and "when..." have the same meaning and are interchangeable.

[0061] Embodiments of the first aspect

[0062] An embodiment of the present application provides a method for updating the authorization status of a mobile IAB node, which is explained from the side of the first node. The first node is the RRC termination node (RRC-terminating IAB-donor) of the mobile IAB node, and the F1 termination node (F1-terminating IAB-donor) of the mobile IAB node is called the second node. Taking the mobile IAB as the IAB node 1 in the scenario shown in Figure 1 as an example, the first node is Donor-CU1 in the scenario shown in Figure 1, abbreviated as CU1, and the second node is Donor-CU2 in the scenario shown in Figure 1, abbreviated as CU2.

[0063] FIG2 is a schematic diagram of a method for updating the authorization status of a mobile IAB node according to an embodiment of the present application. As shown in FIG2 , the method includes:

[0064] 210: The first node receives the XnAP message sent by the second node;

[0065] 220: The first node confirms, based on the XnAP message, whether the second node has completed the handover of the terminal device served by the unauthorized mobile IAB node and / or the release of the F1 interface of the unauthorized mobile IAB node.

[0066] It is worth noting that FIG2 above only schematically illustrates 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 content, and are not limited to the description of FIG2 above.

[0067] In the above embodiment, when the mobile IAB node's mIAB-MT and collocated mIAB-DU are connected to different IAB-donor-CUs, that is, when the RRC-terminating IAB-donor and F1-terminating IAB-donor are different, the RRC-terminating IAB-donor notifies the F1-terminating IAB-donor of the mobile IAB node's authorization status via XnAP signaling when the authorization status of the mobile IAB node is updated. If the authorization status is updated to "unauthorized," the F1-terminating IAB-donor needs to switch the terminal device served by the mobile IAB node and / or release the F1 interface of the mobile IAB node.

[0068] According to the above embodiment, the F1-terminating IAB-donor (second node) sends an XnAP message to the RRC-terminating IAB-donor (first node), allowing the RRC-terminating IAB-donor (CU1) to confirm whether it has completed the handover of the terminal device served by the mobile IAB node and / or the release of the F1 interface of the mobile IAB node, thereby reducing or avoiding UE service interruption. This solves the problem of changing the authorization status of the mobile IAB node to a certain extent, thereby supporting the configuration flexibility of the mobile IAB node, supporting the wide-area mobility of the mobile IAB node, and providing high-quality service to the UE served by the mobile IAB node.

[0069] In the above embodiment, the XnAP message is a message transmitted on the Xn interface. In the scenario of Figure 1, the interface between donor-CU1 and donor-CU2 is the Xn interface, and the control message transmitted between the two is called an XnAP message.

[0070] In some embodiments, the XnAP message is an IAB transport migration modification response (IAB TRANSPORT MIGRATION MODIFICATION RESPONSE) message, which is a reply message to an IAB transport migration modification request (IAB TRANSPORT MIGRATION MODIFICATION REQUEST) message sent from the first node to the second node. The IAB transport migration modification request message includes an IE Mobile IAB Authorization Status, and the value of the IE is "Not Authorized".

[0071] The IAB Transport Migration Modification Request message is the first message in the IAB Transport Migration Modification process initiated by the first node. The IAB Transport Migration Modification process is a UE association process (the mobile IAB-MT acts as the UE). The IAB Transport Migration Modification Request and Response messages contain the UE XnAP ID, which indicates the identity of the mobile IAB node.

[0072] In the above embodiment, the existing IAB TRANSPORT MIGRATION MODIFICATION RESPONSE message is reused for implicit indication, and the behavior of the first node (NG-RAN node) when receiving the IAB TRANSPORT MIGRATION MODIFICATION RESPONSE message is enhanced.

[0073] For example, if the IAB TRANSPORT MIGRATION MODIFICATION RESPONSE message received by the first node is a reply message to an IAB TRANSPORT MIGRATION MODIFICATION REQUEST message with the Mobile IAB Authorization Status IE value set to "Not Authorized," the second node is deemed to have completed the handover of the terminal device served by the unauthorized mobile IAB node and / or the release of the F1 interface of the unauthorized mobile IAB node. Therefore, the first node can proceed with subsequent actions.

[0074] According to the above embodiment, by reusing the IAB TRANSPORT MIGRATION MODIFICATION RESPONSE message for implicit indication, signaling is saved, implementation is easier, and forward compatibility is better.

[0075] In other embodiments, the above-mentioned XnAP message is an IAB transport migration modification response (IAB TRANSPORT MIGRATION MODIFICATION RESPONSE) message, which includes a first IE, which indicates an acknowledgment that the authorization status of the mobile IAB node has been changed to "unauthorized", and the first IE indicates the completion of the switching of the terminal device served by the unauthorized mobile IAB node and / or the release of the F1 interface of the unauthorized mobile IAB node.

[0076] In the above embodiment, a new IE (called the first IE) is added to the existing IAB TRANSPORT MIGRATION MODIFICATION RESPONSE message for explicit indication, and the behavior of the first node (NG-RAN node) when receiving the IAB TRANSPORT MIGRATION MODIFICATION RESPONSE message is enhanced.

[0077] For example, if the IAB TRANSPORT MIGRATION MODIFICATION RESPONSE message received by the first node includes the first IE, the second node is deemed to have completed the handover of the terminal device served by the unauthorized mobile IAB node and / or the release of the F1 interface of the unauthorized mobile IAB node. Therefore, the first node can proceed with subsequent actions.

[0078] In the above embodiment, the name of the first IE is not limited and may be, for example, called an IAB Release IE. The first IE indicates that the second node has acknowledged receipt of the change of the authorization status of the mobile IAB node to "unauthorized" and notifies the first node of the completion of handover of the UE served by the mobile IAB node and / or the completion of release of the F1 interface of the mobile IAB node (mIAB-DU).

[0079] According to the above embodiment, by adding the first IE in the IAB TRANSPORT MIGRATION MODIFICATION RESPONSE message for explicit indication, the indication is clearer and the fault tolerance rate is higher during implementation.

[0080] In some further embodiments, the XnAP message is an IAB transport migration management request (IAB TRANSPORT MIGRATION MANAGEMENT REQUEST) message, which includes a second IE, which indicates that the switching of the terminal device served by the unauthorized mobile IAB node and / or the release of the F1 interface of the unauthorized mobile IAB node is completed.

[0081] The IAB Transport Migration Management Request message is the first message in the IAB Transport Migration Management process initiated by the second node. This process is a UE association process (with the mobile IAB-MT acting as the UE). The IAB Transport Migration Management Request and Response messages contain the UE XnAP ID, which identifies the mobile IAB node. Furthermore, during the mIAB-DU migration process, the first IAB Transport Migration Management Request message uses the BAP address as the mIAB node's identifier.

[0082] In the above embodiment, since the second node takes some time to perform processes such as (one or more) UE handovers and F1 release, if the IAB Transport Migration Modification RESPONSE message is used to reply to the first node regarding the change in authorization message for the IAB mobile node after these processes are completed, the IAB Transport Migration Modification process may take too long, possibly causing the process to time out and thus fail. According to the above embodiment, the above notification is performed using a process initiated by the second node, thus avoiding this problem.

[0083] In the above embodiment, the IAB Transport Migration Management process in the XnAP process can be enhanced. For example, the aforementioned second IE can be added to the IAB Transport Migration Management Request message. This second IE indicates that the sender has completed the handover of the UE served by the mobile IAB node and / or released the F1 interface of the mobile IAB node (mIAB-DU). This application does not limit the name of the second IE; for example, it can be called the IAB Resource Release IE.

[0084] In the above embodiment, the above process may be performed after the second node completes UE handover to the mobile IAB node and / or completes F1 release, but the present application is not limited thereto. The above process may also be performed at a time deemed appropriate by the second node.

[0085] In the above embodiment, the behavior of the first node (NG-RAN node) when receiving the IAB TRANSPORT MIGRATION MANAGEMENT REQUEST message may also be enhanced. For example, when the first node receives the IAB TRANSPORT MIGRATION MANAGEMENT REQUEST message, if the IAB TRANSPORT MIGRATION MANAGEMENT REQUEST message includes the second IE, the first node confirms that the second node has completed the handover of the terminal device served by the unauthorized mobile IAB node and / or the release of the F1 interface of the unauthorized mobile IAB node, and the first node may perform subsequent actions.

[0086] In the above embodiment, optionally, the second IE can be included in the released traffic information (Traffic To Be Released Information) IE group, or included in the full release (Full Release) IE under the released traffic information IE group, etc., and this application does not impose any restrictions on this.

[0087] In the above embodiment, optionally, when the second IE exists, the All traffic indication IE is set to "true", indicating that the second node requests to release all traffic related to the mobile IAB node that is offloaded to the first node topology.

[0088] According to the above embodiment, by enhancing the IAB transmission migration management process in the XnAP process, process timeout or failure caused by excessive waiting time is avoided, thereby improving network performance.

[0089] In some further embodiments, the above-mentioned XnAP message is a message in a class 2 process initiated by the second node, and the message includes a third IE, which indicates that the switching of the terminal device served by the unauthorized mobile IAB node and / or the release of the F1 interface of the unauthorized mobile IAB node is completed.

[0090] In the above embodiment, notification is performed using a class 2 procedure (a one-way message procedure) initiated by the second node (F1-terminating IAB-donor). A new procedure can be used to define a new UE-associated message that includes a third IE. Alternatively, an existing message can be enhanced, such as by adding a third IE to the ACTIVITY NOTIFICATION message. This application does not impose any restrictions on the name or location of the third IE.

[0091] In the above embodiment, when the first node (NG-RAN node) receives the above message including the above third IE, it can confirm based on the third IE that the second node has completed the switching of the terminal device served by the unauthorized mobile IAB node and / or the release of the F1 interface of the unauthorized mobile IAB node, and then the first node can perform subsequent actions.

[0092] According to the above embodiment, the one-way message process initiated by the second node is used to perform the above notification, which requires less signaling and is easier to implement.

[0093] In some further embodiments, the above-mentioned XnAP message is a message in the non-UE association process initiated by the second node, and the message includes a fourth IE, which indicates that the switching of the terminal device served by the unauthorized mobile IAB node and / or the release of the F1 interface of the unauthorized mobile IAB node is completed.

[0094] In the above embodiment, notification is performed using a non-UE-associated process initiated by the second node (F1-terminating IAB-donor). This non-UE-associated process may not be targeted at a specific UE. Therefore, the process message may include the identifiers of one or more mobile IAB nodes. This allows simultaneous confirmation of authorization status changes for multiple mobile IAB nodes and notification of UE handover and / or F1 release information for the first node regarding multiple mobile IAB nodes.

[0095] In the above embodiment, the message may be a new message in the above non-UE association process, or may be an NG-RAN node configuration update message in the above non-UE association process.

[0096] For example, a new class 1 process is used to define a new message, and the initiated message (eg, a request message) includes the fourth IE and identifiers of one or more mobile IAB nodes, such as BAP addresses.

[0097] For another example, the messages in the existing non-UE-associated process can be enhanced, such as adding the above-mentioned fourth IE in the NG-RAN NODE CONFIGURATION UPDATE message.

[0098] This application does not limit the name and location of the fourth IE.

[0099] In the above embodiment, when the first node (NG-RAN node) receives the message with the above-mentioned fourth IE, it can confirm that the second node has completed the switching of the terminal device served by the unauthorized mobile IAB node corresponding to one or more node identifiers in the message and / or the release of the F1 interface of the unauthorized mobile IAB node corresponding to one or more node identifiers in the message, and the first node can perform subsequent actions.

[0100] According to the above embodiment, the non-UE-associated process initiated by the second node is used to perform the above notification, which can support the authorization status update of multiple mobile IAB nodes at the same time, and is more efficient to implement.

[0101] According to the methods of the aforementioned embodiments, the first node confirms whether the second node has completed the switching of the terminal device served by the unauthorized mobile IAB node and / or the release of the F1 interface of the unauthorized mobile IAB node based on the XnAP message from the second node. After confirming that the second node has completed the switching of the terminal device served by the unauthorized mobile IAB node and / or the release of the F1 interface of the unauthorized mobile IAB node, for example, after receiving the above-mentioned IAB transmission migration modification response message, or receiving the above-mentioned IAB transmission migration modification response message containing the first IE, or receiving the above-mentioned IAB transmission migration management request message containing the second IE, or receiving a message in the class 2 process containing the third IE, or receiving a message in the non-UE associated process containing the fourth IE, the first node can perform subsequent actions.

[0102] For example, the first node may release all traffic offloaded from the second node topology for the unauthorized mobile IAB node and / or release the backhaul resources of the unauthorized mobile IAB node. The backhaul resources herein include, for example, a BAP address, a TNL address (i.e., an IP address), a BH RLC channel configuration, a default BAP configuration, and the like. The default BAP configuration, also known as the default uplink mapping, includes a default uplink BAP route identifier, a default uplink BH RLC channel identifier, and the like. For details, please refer to the relevant art.

[0103] In the above example, the first node may also release the UE XnAP ID allocated to the mobile IAB-MT.

[0104] Since the authorization status may change frequently according to the location and time during the movement of the mobile IAB node, the first node may also choose not to release the backhaul resources of the unauthorized mobile IAB node, thereby directly using the saved backhaul resources when the authorization status changes, quickly establishing the DU, and thus serving the UE.

[0105] Alternatively, the first node may use a timer (referred to as a first timer) to retain the backhaul resources for a period of time, and only release the backhaul resources if the authorization status does not change. For example, the first timer may be started when the authorization status of the mobile IAB node changes to "unauthorized" and stopped when the authorization status changes to "authorized." When the first timer expires, all backhaul resources of the mobile IAB node are released.

[0106] In the above example, there is no restriction on the value of the first timer, for example, it can be in hours or other time units.

[0107] In some embodiments, as shown in FIG2 , the method may further include:

[0108] 200: The first node receives the new authorization status of the mobile IAB node sent by the AMF through a downlink NAS transmission message. The new authorization status is "not authorized".

[0109] 205: The first node sends an IAB transport migration modification request message to the second node, where the IAB transport migration modification request message indicates an updated authorization status of the mobile IAB node.

[0110] In the above embodiment, the AMF of the core network (5GC) notifies the NG-RAN node (the donor-CU of the mIAB-MT, i.e., donor-CU1, i.e., the aforementioned first node) of the new authorization status (i.e., unauthorized) through a downlink NAS transport (DOWNLINK NAS TRANSPORT) message. The downlink NAS transport message may also carry a NAS message of the IAB-MT of the mobile IAB node transparently transmitted through donor-CU1 (the first node) to inform the mobile IAB node of the authorization status and other information.

[0111] In the above embodiment, the RRC-terminating donor-CU of the mobile IAB node (i.e., the first node) sends an IAB transport migration modification request (IAB TRANSPORT MIGRATION MODIFICATION REQUEST) message to the F1-terminating donor-CU of the mobile IAB node (i.e., the second node), where the message contains the updated authorization status of the mobile IAB node.

[0112] In the above embodiment, the F1-terminating donor-CU (i.e., the second node) of the mobile IAB node can switch all UEs served by the mobile IAB node to other cells, and the F1-terminating donor-CU (i.e., the second node) of the mobile IAB node can release the F1 interface to the mIAB-DU of the mobile IAB node through the F1 removal process.

[0113] In the above embodiment, the XnAP message of operation 210 is the aforementioned IAB transport migration modification response message, which may carry the above-mentioned first IE or may not carry the above-mentioned first IE. Based on the IAB transport migration modification response message, the first node can confirm whether the second node has completed the switching of the terminal device served by the unauthorized mobile IAB node and / or the release of the F1 interface of the unauthorized mobile IAB node, and continue with subsequent actions.

[0114] Figure 3 is a schematic diagram of another example of an IAB network topology, illustrating the operational flow after the authorization status of a mobile IAB node is updated to "unauthorized." In the example of Figure 3 , IAB node 1 is a mobile IAB node, its RRC terminating donor CU is donor-CU1, referred to as the first node, and its F1 terminating donor CU is donor-CU2, referred to as the second node. As shown in Figure 3 , when the authorization status of a mobile IAB node changes to "unauthorized," the process includes:

[0115] 310: The AMF of the core network (5GC) notifies the first node of the new authorization status (i.e., unauthorized) through a downlink NAS transmission message;

[0116] 320: The first node sends an IAB transport migration modification request (IAB TRANSPORT MIGRATION MODIFICATION REQUEST) message to the second node, where the message includes the updated mobile IAB node authorization status.

[0117] 330: The second node switches all UEs served by the mobile IAB node to other cells;

[0118] 340: The second node releases the F1 interface of the mIAB-DU to the mobile IAB node through an F1 removal process;

[0119] 350: The second node sends an IAB transport migration modification response (IAB TRANSPORT MIGRATION MODIFICATION RESPONSE) message to the first node;

[0120] 360: The first node releases all offloaded traffic (from the F1-terminating donor-CU topology for the mobile IAB node) and releases all backhaul resources of the mobile IAB node, including the mobile IAB node's BAP address, TNL (Transport Network Layer) address, BH RLC channel configuration, default BAP configuration, etc. In addition, the first node may also release the UE XnAP ID allocated to the mobile IAB node (mIAB-MT).

[0121] In the above example, there is no restriction on the execution timing of operation 350 , for example, it can be executed after operation 340 , simultaneously with operation 340 , or before operation 340 , and so on.

[0122] In the above example, operations 310 and 320 are the same as the aforementioned operations 200 and 205 , the contents of which are incorporated herein.

[0123] In the above example, the purpose of operation 350 is to confirm receipt of the IAB transport migration modification request from the RRC-terminating donor-CU (first node) and to notify the first node that all UEs served by the mobile IAB node have been switched and the F1 interface of the mIAB-DU of the mobile IAB node has been released, so that the first node can perform subsequent actions.

[0124] In operation 350, the IAB TRANSPORT MIGRATION MODIFICATION RESPONSE is XnAP signaling. As previously described, this message may not include the first IE to implicitly indicate that the second node has completed the handover of the terminal device served by the unauthorized mobile IAB node and / or the release of the F1 interface of the unauthorized mobile IAB node. Alternatively, this message may include the first IE to explicitly indicate that the second node has completed the handover of the terminal device served by the unauthorized mobile IAB node and / or the release of the F1 interface of the unauthorized mobile IAB node. Thus, the XnAP protocol TS38.423 is enhanced to support the above notification.

[0125] 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.

[0126] According to the method of the embodiment of the present application, the problem of changing the authorization status of the mobile IAB node is solved to a certain extent, thereby supporting the configuration flexibility of the mobile IAB node, supporting the wide-area mobility of the mobile IAB node, and providing high-quality services for UEs served by the mobile IAB node.

[0127] Embodiments of the second aspect

[0128] An embodiment of the present application provides a method for updating the authorization status of a mobile IAB node, which is explained from the side of the first node. The first node is a non-F1 termination node of the mobile IAB node, and the F1 termination node of the mobile IAB node is called the second node. Taking the mobile IAB node as the IAB node 1 in the scenario shown in Figure 1 as an example, the first node is Donor-CU1 in the scenario shown in Figure 1, abbreviated as CU1, and the second node is Donor-CU2 in the scenario shown in Figure 1, abbreviated as CU2.

[0129] FIG4 is a schematic diagram of a method for updating the authorization status of a mobile IAB node according to an embodiment of the present application. As shown in FIG4 , the method includes:

[0130] 410: The first node receives the NGAP message sent by the AMF.

[0131] 420: When the NGAP message includes the authorization status of the mobile IAB node with a value of “authorized”, the first node establishes a backhaul resource for the mobile IAB node, so that the mobile IAB node uses the backhaul resource to establish an F1 connection with the second node.

[0132] It is worth noting that before operation 420, the mobile IAB node may not have established an F1 connection with the second node. That is, before operation 420, the second node is not the F1-terminating IAB-donor of the mobile IAB node, but can only be the F1-terminating IAB-donor that is about to become the mobile IAB node.

[0133] It is worth noting that FIG4 above only schematically illustrates 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 content, and are not limited to the description of FIG4 above.

[0134] According to the above embodiment, when the authorization status of the mobile IAB node changes from "unauthorized" to "authorized", if the F1 interface of the mobile IAB node has been released or has not yet been established, the IAB-donor (i.e., the first node) of the mobile IAB node establishes a backhaul resource for the mobile IAB node after receiving the above NGAP message. As a result, the mobile IAB node can use the backhaul resource to establish an F1 connection with the second node, thereby correctly serving the UE.

[0135] In the above embodiment, the NGAP message is a message transmitted on the NGAP interface. In the scenario of Figure 2, the interface between the 5G core network (5GC) and donor-CU1 or donor-CU2 is the NG interface, and the control message transmitted between the two is called an NGAP message.

[0136] In some embodiments, the NGAP message is at least one of the following: a UE Context Modification Request message, an Initial Context Setup Request message, or a DOWNLINK NAS TRANSPORT message.

[0137] In the above embodiment, when the UE context modification request, initial context establishment request or downlink NAS transmission message includes an IAB authorization state with a value of "authorized", the first node (NG-RAN node, i.e., the RRC-terminating IAB-donor of the mIAB-MT) establishes backhaul resources for the mobile IAB node (if not already configured).

[0138] In some embodiments, the backhaul resource may include at least one of the following: a TNL address, a BAP address, a default uplink BAP route identifier, a default uplink BH RLC channel identifier, and the like.

[0139] In the above embodiment, the mobile IAB node (IAB-DU) can use the default BAP route identifier and default BH RLC channel identifier for upstream traffic configured by the first node (RRC-terminating IAB-donor-CU) to initiate TNL establishment and F1 establishment (if not already established) to the second node (F1-terminating IAB-donor-CU). The determination of the second node and related configuration are configured by OAM for the mobile IAB node. For details, please refer to the relevant technology.

[0140] In the above embodiment, the default BAP route identifier and the default BH RLC channel identifier for upstream traffic are the default uplink mapping configuration, and are also the default BAP configuration.

[0141] In some embodiments, the first node and the second node are the same, that is, the RRC-terminating IAB-donor and the F1-terminating IAB-donor of the mobile IAB node are the same node.

[0142] In some embodiments, if there is a second node different from the first node, and the second node is the F1 termination node of the above-mentioned mobile IAB node, that is, the mobile IAB node has established an F1 interface with the second node, then the first node can send an IAB transmission migration modification request message containing the updated authorization status of the mobile IAB node to the second node, so that the second node performs corresponding operations to enable the mobile IAB node to serve the terminal device.

[0143] The above embodiment addresses the scenario where the F1 interface of the mobile IAB node (mIAB-DU) still exists, that is, there is an F1-terminating IAB-donor. This scenario applies to situations where an authorization change message from the mobile IAB node is received before the F1 interface is released, or where the F1 interface is not released when the authorization status of the mobile IAB node is "unauthorized."

[0144] In the above embodiment, if the UE context modification request, the initial context establishment request or the downlink NAS transport message includes an IAB authorization status with a value of "authorized", and there are different F1-terminating IAB-donors, the NG-RAN node that receives the above NGAP message (i.e., the RRC-terminating IAB-donor of the mIAB-MT, i.e., the first node) sends an IAB TRANSPORT MIGRATION MODIFICATION REQUEST message including the updated authorization status of the mobile IAB node to the F1-terminating IAB-donor-CU (the second node).

[0145] In the above embodiment, the first node (NG-RAN node) can establish backhaul resources for the mobile IAB node. The second node (F1-terminating IAB-donor-CU) can save the authorization status of the mobile IAB node and perform corresponding operations to enable the mobile IAB node to continue serving the UE.

[0146] In the above embodiment, the backhaul resource may include at least one of the following: a TNL address, a BAP address, a default uplink BAP route identifier, a default uplink BH RLC channel identifier, and the like.

[0147] In the above embodiment, the corresponding operation performed by the second node refers to an operation according to the current situation. For example, if the handover of UEs served by all mobile IAB nodes has not been completed, the handover can be stopped. If the F1 interface for the mIAB-DU has not been released, the F1 interface does not need to be released.

[0148] In the above embodiment, the criterion for the first node (NG-RAN node) to determine the existence of a different F1-terminating IAB-donor is: the existence of a UE association with another NG-RAN node for the mobile IAB node, such as whether a UE XnAP ID has been generated for the mIAB-MT of the mobile IAB node and has not been released. The criterion may also be: if backhaul resources are configured for the mobile IAB node and have not been released, and the NG-RAN node (first node) does not terminate the F1 interface of the mobile IAB node.

[0149] In some embodiments, the first node may also generate a SIB1 broadcast message, the SIB1 broadcast message including cell identification information, and the SIB1 broadcast message including a mobileIAB-Support field and a gNB-ID-Length field, where the gNB-ID-Length field is optional.

[0150] In the above embodiment, the SIB1 message generated by the first node may be broadcast through the parent node cell of the mobile IAB node (ie, the cell belonging to the parent node DU). The parent node may be the IAB node or the first node itself.

[0151] In the above embodiment, the gNB-ID-Length field is used by the mobile IAB node to obtain the base station identifier from the above cell identifier information, thereby performing DU migration.

[0152] In the above embodiment, during the mobile IAB node DU (mIAB-DU) migration process, when the target logical mIAB-DU sends an F1 Setup Request message to the target IAB-donor-CU, it must include information related to the mobile IAB node's RRC-terminating IAB-donor, such as the base station identifier (gNB ID) of the RRC-terminating IAB-donor-CU. This base station identifier is obtained by the collocated mIAB-MT by receiving the cell identifier (such as NCGI, NR Cell Global Identifier, or CellIdentity in NCGI) in the SIB1 (System Information Block) broadcast message of the parent cell, because the cell identifier includes the base station identifier of the donor-CU to which the cell belongs. To decode the base station identifier in the cell identifier, the mobile IAB node needs to know the number of bits in the base station identifier, that is, the bit length in the cell identifier. The SIB1 broadcast message includes the optional field gNB-ID-Length, which indicates the length of the gNB ID in the 36-bit cellIdentity.

[0153] To support DU migration for mobile IAB nodes, the parent cell of the mobile IAB node must ensure that the mobile IAB node receives the gNB-ID-Length broadcast information. During the cell selection process for the mobile IAB node (IAB-MT), a cell broadcasting "mobile IAB support" must be selected, effectively selecting that cell as the parent cell. Therefore, the broadcast message (SIB1 broadcast message) indicating "mobile IAB support" can be enhanced. Specifically, when the mobileIAB-Support field is present in the SIB1 broadcast message, the gNB-ID-Length field must also be present in the SIB1 broadcast message. This ensures that the mobile IAB node can obtain the base station identifier.

[0154] In the above embodiment, the mobileIAB-Support field and the gNB-ID-Length field may be included in the PLMN identity information (PLMN-IdentityInfo) and / or the NPN identity information list (NPN-IdentityInfoList) in the cell access related information (CellAccessRelatedInfo) IE in the above SIB1 broadcast message. The present application is not limited to this.

[0155] 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.

[0156] According to the method of the embodiment of the present application, the problem of changing the authorization status of the mobile IAB node is solved to a certain extent, thereby supporting the configuration flexibility of the mobile IAB node, supporting the wide-area mobility of the mobile IAB node, and providing high-quality services for UEs served by the mobile IAB node.

[0157] Embodiments of the third aspect

[0158] An embodiment of the present application provides a method for updating the authorization status of a mobile IAB node, which is explained from the side of the mobile IAB node. The mobile IAB node is, for example, the IAB node 1 in the scenario shown in Figure 1. The non-F1 termination node of the mobile IAB node is called the first node, for example, the Donor-CU1 in the scenario shown in Figure 1, abbreviated as CU1, and the F1 termination node of the mobile IAB node is called the second node, for example, the Donor-CU2 in the scenario shown in Figure 1, abbreviated as CU2.

[0159] FIG5 is a schematic diagram of a method for updating the authorization status of a mobile IAB node according to an embodiment of the present application. As shown in FIG5 , the method includes:

[0160] 510: When the mobile IAB node receives the UE Configuration Update Command sent by the AMF, and the UE Configuration Update Command includes the IAB authorization status with a value of "authorized", it sends a new authorization indication to the AS layer.

[0161] In the above embodiment, the AMF provides the mobile IAB node (mIAB-MT) with a new authorization indication and additional information. When the mobile IAB node receives a UE configuration update command containing an IAB authorization status of "Authorized," the mobile IAB node (mIAB-MT) provides the new authorization indication to the AS layer. This enables the mobile IAB node to correctly serve the UE.

[0162] In some embodiments, if the backhaul resources of the mobile IAB node have been configured, for example, by RRC, the DU of the mobile IAB node (mIAB-DU collocated with the mIAB-MT) can perform an F1 setup procedure on the donor-CU (second node) configured based on OAM, thereby establishing an F1 interface with the second node.

[0163] In some embodiments, if the backhaul resources of the mobile IAB node are not configured, the DU of the mobile IAB node (mIAB-DU collocated with mIAB-MT) can wait for RRC to configure mIAB-MT regarding the backhaul resources, and after the backhaul resources are reconfigured, perform the F1 establishment process on the second node.

[0164] In the above embodiment, the backhaul resources may include, for example, a TNL address, a BAP address, and a default uplink mapping, etc., which have been described in detail above and will not be repeated here.

[0165] In some embodiments, when the mobile IAB node receives the deregistration request message (DEREGISTRATION REQUEST) sent by the AMF, it performs the deregistration process if the deregistration conditions are met.

[0166] In the above embodiment, the deregistration condition may be, for example, that the F1 connection of the DU of the mobile IAB node is released; or that the backhaul resource of the mobile IAB node is released, and so on.

[0167] In the above embodiment, if the authorization status of the mobile IAB node changes from "authorized" to "unauthorized" and the AMF uses the deregistration procedure to update the mobile IAB node, the AMF sends a UE Context Modification message to the NG-RAN (first node) before triggering the deregistration procedure for the mobile IAB node and waits for a period of time (for example, based on the expiration of an AMF-configured timer) before triggering the deregistration procedure.

[0168] Since the mobile IAB node cannot serve the UE after deregistration, even if a period of time is used to trigger the deregistration process, it still cannot be guaranteed that all UEs of the mobile IAB node have completed the handover. In order to avoid the mobile IAB node (mIAB-MT) from deregistering too early, in the above embodiment, when the mIAB-MT of the mobile IAB node receives the deregistration request message from the AMF, it performs the deregistration process after the F1 connection of the collocated mIAB-DU is released. As a deregistration condition, the F1 of the collocated mIAB-DU is released to ensure that the UE served by the mIAB-DU completes the handover. Similarly, the deregistration condition can also be that the backhaul resources of the mIAB are released, which is completed by the RRC reconfiguration of the mIAB-MT.

[0169] 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.

[0170] According to the method of the embodiment of the present application, the problem of changing the authorization status of the mobile IAB node is solved to a certain extent, thereby supporting the configuration flexibility of the mobile IAB node, supporting the wide-area mobility of the mobile IAB node, and providing high-quality services for UEs served by the mobile IAB node.

[0171] Embodiments of the fourth aspect

[0172] An embodiment of the present application provides a broadcast message method supporting a mobile IAB node, which is explained from the side of the parent node of the mobile IAB node. The mobile IAB node is, for example, the IAB node 1 in the scenario shown in Figure 1, and the parent node of the mobile IAB node is, for example, the IAB node 2 in the scenario shown in Figure 1, or it can be the IAB-donor 1 (including donor-CU1 and donor-DU1) in the scenario shown in Figure 1, that is, the first node in the previous embodiment.

[0173] FIG6 is a schematic diagram of a method for supporting a mobile IAB node broadcast message according to an embodiment of the present application. As shown in FIG6 , the method includes:

[0174] 610: The parent node of the mobile IAB node sends a SIB1 broadcast message, where the SIB1 broadcast message includes cell identification information and includes a mobileIAB-Support field and a gNB-ID-Length field. The gNB-ID-Length field is optional. When the mobileIAB-Support field is present in the SIB1 broadcast message, the gNB-ID-Length field must also be present in the SIB1 broadcast message.

[0175] In the above embodiment, the gNB-ID-Length field is used by the mobile IAB node to obtain the base station identifier from the above cell identifier information, thereby performing DU migration.

[0176] In the above embodiment, during the DU (mIAB-DU) migration process of the mobile IAB node, when the target logical mIAB-DU (logical mIAB-DU) sends an F1 Setup Request message to the target IAB-donor-CU, it must include information related to the mobile IAB node's RRC-terminating IAB-donor, such as the base station identifier (gNB ID) of the RRC-terminating IAB-donor-CU. This base station identifier is obtained by the collocated mIAB-MT by receiving the cell identifier (NCGI, NR Cell Global Identifier) ​​in the SIB1 (System Information Block) broadcast message of the parent cell, because the NCGI includes the base station identifier of the donor-CU to which the cell belongs. To decode the base station identifier in the NCGI, the mobile IAB node needs to know the number of bits of the base station identifier, that is, the bit length in the NCGI. The SIB1 broadcast message contains the optional field gNB-ID-Length, which indicates the length of the gNB ID in the 36-bit cellIdentity field.

[0177] To support DU migration for mobile IAB nodes, the first node must ensure that the mobile IAB node receives the gNB-ID-Length broadcast information through the mobile IAB node's parent cell. During cell selection, the mobile IAB node (IAB-MT) must select a cell that broadcasts "support for mobile IAB," effectively selecting that cell as its parent cell. Therefore, the broadcast message (SIB1 broadcast message) indicating "support for mobile IAB" can be enhanced. Specifically, when the mobileIAB-Support field is present in the SIB1 broadcast message, the gNB-ID-Length field must also be present in the SIB1 broadcast message. This ensures that the mobile IAB node can obtain the base station identifier.

[0178] In the above embodiment, the mobileIAB-Support field and the gNB-ID-Length field may be included in the PLMN identity information (PLMN-IdentityInfo) and / or the NPN identity information list (NPN-IdentityInfoList) in the cell access related information (CellAccessRelatedInfo) IE in the above SIB1 broadcast message. The present application is not limited to this.

[0179] 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.

[0180] According to the method of the embodiment of the present application, the problem of changing the authorization status of the mobile IAB node is solved to a certain extent, thereby supporting the configuration flexibility of the mobile IAB node, supporting the wide-area mobility of the mobile IAB node, and providing high-quality services for UEs served by the mobile IAB node.

[0181] Embodiments of the fifth aspect

[0182] An embodiment of the present application provides a device for updating the authorization status of a mobile IAB node.

[0183] Figure 7 is a schematic diagram of a device for updating the authorization status of a mobile IAB node according to an embodiment of the present application. The device may be the aforementioned first node, or one or more parts or components in the aforementioned first node. The principle of solving the problem is the same as that of the embodiment of the first aspect, and the same contents will not be repeated.

[0184] As shown in FIG7 , the apparatus 700 includes:

[0185] A first receiving unit 710, which receives an XnAP message sent by a second node;

[0186] The processing unit 720 confirms, according to the XnAP message, whether the second node has completed the handover of the terminal device served by the unauthorized mobile IAB node and / or the release of the F1 interface of the unauthorized mobile IAB node.

[0187] In some embodiments, the XnAP message is an IAB transport migration modification response message, which is a reply message to the IAB transport migration modification request message sent by the first node to the second node. The IAB transport migration modification request message includes IE Mobile IAB Authorization Status, and the value of the IE is "Not Authorized".

[0188] According to the above embodiment, the second node implicitly notifies through the IAB transmission migration modification response message. When the processing unit 720 receives the above IAB transmission migration modification response message, it confirms that the second node has completed the switching of the terminal device served by the unauthorized mobile IAB node and / or the release of the F1 interface of the unauthorized mobile IAB node, and then the processing unit 720 can perform subsequent actions.

[0189] In other embodiments, the XnAP message is an IAB transport migration modification response message, and the IAB transport migration modification response message includes a first IE, which indicates confirmation that the authorization status of the mobile IAB node has been changed to "unauthorized", and the first IE indicates the completion of the switching of the terminal device served by the unauthorized mobile IAB node and / or the release of the F1 interface of the unauthorized mobile IAB node.

[0190] According to the above embodiment, the second node explicitly notifies through the IAB transport migration modification response message. When the received IAB transport migration modification response message contains the above-mentioned first IE, the processing unit 720 confirms that the second node has completed the switching of the terminal device served by the unauthorized mobile IAB node and / or the release of the F1 interface of the unauthorized mobile IAB node, and then the processing unit 720 can perform subsequent actions.

[0191] In some further embodiments, the XnAP message is an IAB transmission migration management request message, and the IAB transmission migration management request message includes a second IE, which indicates that the switching of the terminal device served by the unauthorized mobile IAB node and / or the release of the F1 interface of the unauthorized mobile IAB node is completed.

[0192] According to the above embodiment, the second node is notified through a spontaneous process (IAB transmission migration management request message). When the processing unit 720 receives the IAB transmission migration management request message containing the above second IE, it confirms that the second node has completed the switching of the terminal device served by the unauthorized mobile IAB node and / or the release of the F1 interface of the unauthorized mobile IAB node, and then the processing unit 720 can perform subsequent actions.

[0193] In the above embodiment, optionally, the second IE may be included in the released traffic information IE group, or included in all released IEs under the released traffic information IE group.

[0194] In the above embodiment, optionally, when the second IE exists, all traffic indication IEs are set to "true".

[0195] In some further embodiments, the XnAP message is a message in a class 2 process initiated by the second node, and the message includes a third IE, which indicates that the switching of the terminal device served by the unauthorized mobile IAB node and / or the release of the F1 interface of the unauthorized mobile IAB node is completed.

[0196] According to the above embodiment, the second node is notified through the class 2 process (one-way message process). When the processing unit 720 receives the message in the class 2 process containing the above third IE, it confirms that the second node has completed the switching of the terminal device served by the unauthorized mobile IAB node and / or the release of the F1 interface of the unauthorized mobile IAB node, and then the processing unit 720 can perform subsequent actions.

[0197] In some further embodiments, the XnAP message is a message in a non-UE association process initiated by the second node, and the message includes a fourth IE, which indicates that the switching of the terminal device served by the unauthorized mobile IAB node and / or the release of the F1 interface of the unauthorized mobile IAB node is completed.

[0198] According to the above embodiment, the second node is notified through the non-UE association process. When the processing unit 720 receives a message in the non-UE association process containing the above-mentioned fourth IE, it confirms that the second node has completed the switching of the terminal device served by the unauthorized mobile IAB node and / or the release of the F1 interface of the unauthorized mobile IAB node, and then the processing unit 720 can perform subsequent actions.

[0199] In the above embodiment, optionally, the message is a new message in the non-UE association process, or an NG-RAN node configuration update message in the non-UE association process.

[0200] In the above embodiment, optionally, the message further includes identifications of one or more mobile IAB nodes.

[0201] In some embodiments, the processing unit 720 performs subsequent actions including:

[0202] The processing unit 720 releases all traffic offloaded from the second node topology for the unauthorized mobile IAB node and / or releases backhaul resources of the unauthorized mobile IAB node.

[0203] In the above embodiment, the processing unit 720 may further release the UE XnAP ID allocated to the mobile IAB node (mIAB-MT).

[0204] In some embodiments, the processing unit 720 performs subsequent actions including:

[0205] The processing unit 720 does not release the backhaul resources of the unauthorized mobile IAB node, or,

[0206] The processing unit 720 releases the backhaul resource of the unauthorized mobile IAB node when a first timer times out, wherein the first timer is started when the status of the mobile IAB node becomes unauthorized.

[0207] In some embodiments, as shown in FIG7 , the apparatus 700 further includes:

[0208] The second receiving unit 730 receives a new authorization status of the mobile IAB node sent by the AMF through a downlink NAS transmission message, where the new authorization status is "not authorized".

[0209] In the above embodiment, as shown in FIG7 , the apparatus 700 further includes:

[0210] The sending unit 740 sends an IAB transport migration modification request message to the second node, where the IAB transport migration modification request message indicates an updated authorization status of the mobile IAB node.

[0211] Figure 8 is another schematic diagram of the device for updating the authorization status of the mobile IAB node in an embodiment of the present application. The device can be the aforementioned first node, or one or more parts or components in the aforementioned first node. The principle of solving the problem is the same as that of the embodiment of the second aspect, and the same content will not be repeated.

[0212] As shown in FIG8 , the apparatus 800 includes:

[0213] A receiving unit 810 receives an NGAP message sent by the AMF;

[0214] The processing unit 820 is configured to establish a backhaul resource for the mobile IAB node when the NGAP message includes the authorization status of the mobile IAB node with a value of “authorized”, so that the mobile IAB node establishes an F1 connection with the second node using the backhaul resource.

[0215] In some embodiments, the NGAP message is at least one of the following: a UE context modification request message, an initial context establishment request message, and a downlink NAS transmission message.

[0216] In some embodiments, the backhaul resource includes at least one of the following:

[0217] TNL address;

[0218] BAP address;

[0219] Default uplink BAP route identifier;

[0220] Default uplink BH RLC channel identifier.

[0221] In some embodiments, as shown in FIG8 , the apparatus 800 further includes:

[0222] The sending unit 830, when the second node exists and the second node is an F1-terminating IAB-donor of the mobile IAB node, sends an IAB transmission migration modification request message including the updated authorization status of the mobile IAB node to the second node, so that the second node performs corresponding operations to enable the mobile IAB node to serve the terminal device.

[0223] In some embodiments, as shown in FIG8 , the apparatus 800 further includes:

[0224] A generating unit 840 generates a SIB1 broadcast message, wherein the SIB1 broadcast message includes cell identification information, and the SIB1 broadcast message includes a mobileIAB-Support field and a gNB-ID-Length field, wherein the gNB-ID-Length field is optional; wherein when the mobileIAB-Support field in the SIB1 broadcast message is present, the gNB-ID-Length field in the SIB1 broadcast message must also be present.

[0225] In the above embodiment, optionally, the mobileIAB-Support field and the gNB-ID-Length field are included in the PLMN identification information and / or NPN identification information list in the cell access related information IE in the SIB1 broadcast message.

[0226] In the above embodiment, optionally, the gNB-ID-Length field is used by the mobile IAB node to obtain the base station identifier from the cell identifier information, thereby performing DU migration.

[0227] Figure 9 is another schematic diagram of the device for updating the authorization status of the mobile IAB node in an embodiment of the present application. The device can be the aforementioned mobile IAB node, or one or more parts or components in the aforementioned mobile IAB node. The principle of solving the problem is the same as that of the embodiment of the third aspect, and the same contents will not be repeated.

[0228] As shown in FIG9 , the apparatus 900 includes:

[0229] The sending unit 910 sends a new authorization indication to the AS layer when the mobile IAB node receives the UE configuration update command sent by the AMF, and the UE configuration update command includes an IAB authorization status with a value of "authorized".

[0230] In some embodiments, as shown in FIG9 , the apparatus 900 further includes:

[0231] The first processing unit 920, if the backhaul resources of the mobile IAB node have been configured, then the first processing unit 920 (DU of the mobile IAB node) performs an F1 establishment process on the second node.

[0232] In some embodiments, as shown in FIG9 , the apparatus 900 further includes:

[0233] The second processing unit 930, if the backhaul resource of the mobile IAB node is not configured, then the second processing unit 930 (DU of the mobile IAB node) performs an F1 establishment process on the second node after the backhaul resource is reconfigured.

[0234] In some embodiments, as shown in FIG9 , the apparatus 900 further includes:

[0235] The third processing unit 940, when the mobile IAB node receives the deregistration request message sent by the AMF, the third processing unit 940 performs a deregistration process if the deregistration condition is met.

[0236] In the above embodiment, optionally, the cancellation condition includes at least one of the following:

[0237] The F1 connection of the DU of the mobile IAB node is released;

[0238] The backhaul resources of the mobile IAB node are released.

[0239] In some embodiments, as shown in FIG9 , the apparatus 900 further includes:

[0240] The receiving unit 950 receives the UE configuration update command and / or deregistration request message.

[0241] An embodiment of the present application also provides a broadcast message device supporting a mobile IAB node.

[0242] Figure 10 is a schematic diagram of a broadcast message device supporting a mobile IAB node in an embodiment of the present application. The device can be a parent node of the aforementioned mobile IAB node, for example, also an IAB node or an IAB-donor node, etc., or it can be one or some parts or components in the parent node of the aforementioned mobile IAB node. The principle of solving the problem is the same as that of the embodiment of the fourth aspect, and the same content will not be repeated.

[0243] As shown in FIG10 , the apparatus 1000 includes:

[0244] A sending unit 1010 sends a SIB1 broadcast message, where the SIB1 broadcast message includes cell identification information, and the SIB1 broadcast message includes a mobileIAB-Support field and a gNB-ID-Length field, where the gNB-ID-Length field is optional; wherein, when the mobileIAB-Support field in the SIB1 broadcast message appears, the gNB-ID-Length field in the SIB1 broadcast message must also appear.

[0245] In some embodiments, the mobileIAB-Support field and the gNB-ID-Length field are included in the PLMN identification information and / or NPN identification information list in the cell access related information IE in the SIB1 broadcast message.

[0246] In some embodiments, the gNB-ID-Length field is used by the mobile IAB node to obtain the base station identifier from the cell identifier information, thereby performing DU migration.

[0247] 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 devices 700 to 1000 of the embodiments 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.

[0248] In addition, for the sake of simplicity, Figures 7 to 10 only illustrate 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.

[0249] According to the device of the embodiment of the present application, the problem of changing the authorization status of the mobile IAB node is solved to a certain extent, thereby supporting the configuration flexibility of the mobile IAB node, supporting the wide-area mobility of the mobile IAB node, and providing high-quality services for UEs served by the mobile IAB node.

[0250] Embodiments of the sixth aspect

[0251] An embodiment of the present application provides an IAB communication system, including an IAB node and an IAB-donor node. The IAB node includes a mobile IAB node. The non-F1 termination node of the mobile IAB node is configured to perform the method described in the first or second embodiment. The mobile IAB node is configured to perform the method described in the third embodiment. The parent node of the mobile IAB node (which may be an IAB node or an IAB-donor node, such as the non-F1 termination node of the mobile IAB node) has been described in detail in the embodiments of the first to fifth aspects, and its contents are incorporated herein and will not be repeated here.

[0252] An embodiment of the present application further provides an IAB-donor node, which may be the first node in the aforementioned embodiment, that is, a non-F1 termination node of the mobile IAB node, or the parent node of the mobile IAB node in the aforementioned embodiment, and includes a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the computer program to implement the method according to the embodiment of the first aspect or the second aspect.

[0253] Figure 11 is a schematic diagram of an IAB-donor node according to an embodiment of the present application. As shown in Figure 11, IAB-donor node 1100 may include a central processing unit (CPU) 1101 and a memory 1102; memory 1102 is coupled to CPU 1101. Memory 1102 can store various data and information processing programs, which are executed under the control of CPU 1101 to receive various information from IAB nodes and send various information to IAB nodes.

[0254] For example, the processor 1101 may be configured to execute a program to implement the method described in the embodiments of the first aspect or the second aspect.

[0255] Furthermore, as shown in Figure 11 , IAB-donor node 1100 may further include a transceiver 1103 and an antenna 1104. The functions of these components are similar to those in the prior art and are not further described here. It is worth noting that IAB-donor node 1100 does not necessarily include all of the components shown in Figure 11 . Furthermore, IAB-donor node 1100 may also include components not shown in Figure 11 , for which reference may be made to the prior art.

[0256] An embodiment of the present application further provides an IAB node, which is a mobile IAB node or a parent node of a mobile IAB node, including a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the computer program to implement the method according to the embodiment of the third aspect.

[0257] Figure 12 is a schematic diagram of an IAB node according to an embodiment of the present application. As shown in Figure 12 , IAB node 1200 may include a processor 1201 and a memory 1202. Memory 1202 stores data and programs and is coupled to processor 1201. It should be noted that this diagram is exemplary; other types of structures may be used to supplement or replace this structure to implement telecommunications or other functions.

[0258] For example, the processor 1201 may be configured to execute a program to implement the method described in the embodiments of the third aspect or the fourth aspect.

[0259] As shown in Figure 12 , the IAB node 1200 may further include: a communication module 1203, an input unit 1204, a display 1205, and a power supply 1206. 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 node 1200 does not necessarily include all of the components shown in Figure 12 , and these components are not essential. Furthermore, the IAB node 1200 may also include components not shown in Figure 12 , for which reference may be made to the prior art.

[0260] An embodiment of the present application further provides a computer-readable program, wherein when the program is executed in an IAB-donor node, the program causes a computer to execute the method described in the embodiment of the first aspect or the second aspect in the IAB-donor node.

[0261] 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 method described in the embodiment of the first aspect or the second aspect in an IAB-donor node.

[0262] An embodiment of the present application further provides a computer-readable program, wherein when the program is executed in an IAB node, the program enables a computer to execute the method described in the embodiment of the third invention or the fourth aspect in the IAB node.

[0263] 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 method described in the embodiment of the third aspect or the fourth aspect in an IAB node.

[0264] 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.

[0265] 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).

[0266] 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.

[0267] 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.

[0268] 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.

[0269] Regarding the above implementation methods disclosed in this embodiment, the following additional notes are also disclosed:

[0270] 1. A method for updating the authorization status of a mobile IAB node, wherein the method comprises:

[0271] The first node receives the XnAP message sent by the second node;

[0272] The first node confirms, according to the XnAP message, whether the second node has completed the handover of the terminal device served by the unauthorized mobile IAB node and / or the release of the F1 interface of the unauthorized mobile IAB node.

[0273] 2. The method according to Supplement 1, wherein:

[0274] The XnAP message is a message in a class 2 process initiated by the second node, and the message includes a third IE, which indicates that the switching of the terminal device served by the unauthorized mobile IAB node and / or the release of the F1 interface of the unauthorized mobile IAB node is completed.

[0275] 3. The method according to Supplement 1, wherein:

[0276] The XnAP message is a message in the non-UE association process initiated by the second node, and the message includes a fourth IE, which indicates that the switching of the terminal device served by the unauthorized mobile IAB node and / or the release of the F1 interface of the unauthorized mobile IAB node is completed.

[0277] 4. The method according to Supplement 3, wherein:

[0278] The message is an NG-RAN node configuration update message.

[0279] 5. A method for broadcasting messages supporting a mobile IAB node, wherein the method comprises:

[0280] The parent node of the mobile IAB node sends a SIB1 broadcast message, where the SIB1 broadcast message includes cell identification information and includes a mobileIAB-Support field and a gNB-ID-Length field. The gNB-ID-Length field is optional.

[0281] Among them, when the mobileIAB-Support field in the SIB1 broadcast message appears, the gNB-ID-Length field in the SIB1 broadcast message must also appear.

[0282] 6. The method according to Supplement 5, wherein:

[0283] The mobileIAB-Support field and the gNB-ID-Length field are included in the PLMN identification information and / or NPN identification information list in the cell access related information IE in the SIB1 broadcast message.

[0284] 7. The method according to Supplementary Note 6, wherein:

[0285] The gNB-ID-Length field is used by the mobile IAB node to obtain the base station identifier from the cell identifier information, thereby performing DU migration.

[0286] 8. An IAB-donor node, comprising a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the computer program to implement the method as described in any one of Notes 1 to 7.

[0287] 9. An IAB node, comprising a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the computer program to implement the method as described in any one of Notes 5 to 7.

[0288] 10. An IAB communication system, comprising an IAB node and an IAB-donor node, wherein the IAB node is configured to execute the method described in any one of Notes 5 to 7, and / or the IAB-donor node is configured to execute the method described in any one of Notes 1 to 7.

Claims

1. A device for updating the authorization status of a mobile IAB node, configured at a first node, wherein: The device comprises: A first receiving unit, which receives an XnAP message sent by the second node; A processing unit, which confirms whether the second node has completed the switching of the terminal equipment served by the unauthorized mobile IAB node and / or the release of the F1 interface of the unauthorized mobile IAB node according to the XnAP message.

2. The device according to claim 1, wherein: The XnAP message is an IAB transport migration modification response message, which is a reply message to the IAB transport migration modification request message sent by the first node to the second node. The IAB transport migration modification request message includes IE Mobile IAB Authorization Status, and the value of the IE is "not authorized".

3. The device according to claim 1, wherein: The XnAP message is an IAB transport migration modification response message, and the IAB transport migration modification response message includes a first IE, wherein the first IE indicates confirmation that the authorization status of the mobile IAB node has been changed to "unauthorized", and the first IE indicates completion of switching of the terminal device served by the unauthorized mobile IAB node and / or release of the F1 interface of the unauthorized mobile IAB node.

4. The device according to claim 1, wherein: The XnAP message is an IAB transmission migration management request message, and the IAB transmission migration management request message includes a second IE, and the second IE indicates that the switching of the terminal device served by the unauthorized mobile IAB node and / or the release of the F1 interface of the unauthorized mobile IAB node is completed.

5. The device according to claim 1, wherein: The processing unit releases all traffic unloaded from the second node topology for the unauthorized mobile IAB node and / or releases backhaul resources of the unauthorized mobile IAB node.

6. The device according to claim 5, wherein: The return resource includes at least one of the following: TNL address; BAP address; Default uplink BAP route identifier; Default uplink BH RLC channel identifier.

7. The device according to claim 1, wherein: The processing unit releases the UE XnAP ID allocated to the MT of the mobile IAB node.

8. The device according to claim 1, wherein: The device also includes: The second receiving unit receives a new authorization status of the mobile IAB node sent by the AMF through a downlink NAS transmission message, where the new authorization status is "not authorized".

9. The device according to claim 8, wherein: The device also includes: A sending unit is configured to send an IAB transport migration modification request message to the second node, wherein the IAB transport migration modification request message indicates an updated authorization status of the mobile IAB node.

10. The device according to claim 1, wherein: The processing unit does not release the backhaul resources of the unauthorized mobile IAB node, or, The processing unit releases the backhaul resource of the unauthorized mobile IAB node when a first timer times out, wherein the first timer is started when the state of the mobile IAB node becomes unauthorized.

11. A device for updating the authorization status of a mobile IAB node, configured at a first node, wherein: The device also includes: A receiving unit, which receives an NGAP message sent by the AMF; A processing unit, which, when the NGAP message includes the authorization state of the mobile IAB node with a value of "authorized", establishes a backhaul resource for the mobile IAB node, so that the mobile IAB node uses the backhaul resource to establish an F1 connection with the second node.

12. The device according to claim 11, wherein The NGAP message is at least one of the following: a UE context modification request message, an initial context establishment request message, and a downlink NAS transmission message.

13. The device according to claim 11, wherein: The return resource includes at least one of the following: TNL address; BAP address; Default uplink BAP route identifier; Default uplink BH RLC channel identifier.

14. The device according to claim 11, wherein: The device also includes: The sending unit, when the second node exists, and the second node is the mobile IAB node In the case of F1-terminating IAB-donor, the sending unit sends an IAB transport migration modification request message including an updated authorization status of the mobile IAB node to the second node, so that the second node performs corresponding operations to enable the mobile IAB node to serve the terminal device.

15. The device according to claim 11, wherein The device also includes: a generating unit, configured to generate a SIB1 broadcast message, wherein the SIB1 broadcast message includes cell identification information, and the SIB1 broadcast message includes a mobileIAB-Support field and a gNB-ID-Length field, wherein the gNB-ID-Length field is optional; Among them, when the mobileIAB-Support field in the SIB1 broadcast message appears, the gNB-ID-Length field in the SIB1 broadcast message must also appear.

16. A device for updating the authorization status of a mobile IAB node, configured in the mobile IAB node, wherein: The device comprises: The sending unit sends a new authorization indication to the AS layer when the mobile IAB node receives the UE configuration update command sent by the AMF and the UE configuration update command includes an IAB authorization state with a value of "authorized".

17. The device according to claim 16, wherein: The device also includes: The first processing unit performs an F1 establishment process on the second node if the backhaul resource of the mobile IAB node has been configured.

18. The device according to claim 16, wherein: The device also includes: The second processing unit, if the backhaul resource of the mobile IAB node is not configured, then the second processing unit performs an F1 establishment process on the second node after the backhaul resource is reconfigured.

19. The device according to claim 16, wherein: The device also includes: The third processing unit performs a deregistration process when the mobile IAB node receives the deregistration request message sent by the AMF and the deregistration condition is met.

20. The device according to claim 19, wherein The cancellation conditions include at least one of the following: The F1 connection of the DU of the mobile IAB node is released; The backhaul resources of the mobile IAB node are released.

Images