Radio network node with wireless access backhaul and method therein

Abstract

Various embodiments provide a radio network node with wireless access backhaul and a method therein. In one embodiment, a method performed by a radio network node with wireless access backhaul includes including wireless access backhaul (WAB) related information of the radio network node with wireless access backhaul in a message sent to a core network node, wherein the WAB related information includes at least a first indication to indicate that the radio network node is a radio network node with wireless access backhaul.

Description

Technical Field

[0001] Embodiments of this disclosure generally relate to wireless communication, and more specifically to radio network nodes having wireless access backhaul and methods therein. Background Technology

[0002] 3GPP TS 22.261 defines a mobile base station relay, which acts as a relay between user equipment (UE) and the fifth-generation (5G) network. Specifically, it provides UEs with a New Radio (NR) access link and connects wirelessly (using NR) to the 5G core network (5GC) via a donor NG-RAN. Assume this mobile base station relay is installed on a mobile vehicle and provides services to UEs that may be located inside or outside the vehicle. For this purpose, the relay node can consist of UEs co-located with a full gNB. The gNB on the relay node establishes an N2 / N3 interface with the Access and Mobility Management Function (AMF) residing in the 5GC through Protocol Data Unit (PDU) sessions.

[0003] Figure 1 A network architecture with Wireless Access Backhaul (WAB) deployment is shown. Figure 1 In this architecture, the Mobile Base Station with Radio Access Backhaul (MWAB) acts as a relay node between the User Equipment (UE) and the 5G Core Network (5GC), and can consist of a gNB (denoted as MWAB-gNB) and a mobile terminal (denoted as MWAB-UE) capable of providing radio connectivity for NR backhaul (BH). The PDU session established by the MWAB-UE to the 5GC provides backhaul connectivity to the MWAB-gNB, and this BH PDU session tunnels the N2 / N3 interface of the MWAB-gNB. When a UE connects to the MWAB, the UE treats the MWAB cell as a normal cell and can establish a PDU session to the 5GC using existing signaling procedures. Therefore, WAB deployment is transparent to the UE and does not require enhancement of legacy UEs.

[0004] If a MWAB establishes a backhaul connection via another MWAB hosted by a gNB, a multi-hop trunking scenario arises. Therefore, there is a problem of limiting or enabling a MWAB's ability to use another MWAB as a network node providing backhaul PDU session connections, i.e., avoiding or enabling multi-hop trunking scenarios. It is desirable to allow MWABs or Public Land Mobile Networks (PLMNs) to avoid or enable multi-hop trunking for backhaul connections, i.e., to enable MWABs or PLMNs to control whether multi-hop trunking scenarios are allowed. Summary of the Invention

[0005] This summary is provided to introduce, in a simplified form, some concepts that will be further described in the detailed embodiments described below. This summary is not intended to identify key or essential features of the claimed subject matter, nor is it intended to limit the scope of the claimed subject matter.

[0006] According to a first aspect of this disclosure, a radio network node with wireless access backhaul is provided. The radio network node with wireless access backhaul includes one or more processors and one or more memories storing instructions, which, when executed by the one or more processors, cause the radio network node with wireless access backhaul to include, at least in messages sent to a core network node, wireless access backhaul (WAB) related information of the radio network node with wireless access backhaul, wherein the WAB related information includes at least a first indication indicating that the radio network node is a radio network node with wireless access backhaul.

[0007] According to a second aspect of this disclosure, a core network node is provided. The core network node includes one or more processors and one or more memories storing instructions, which, when executed by the one or more processors, cause the core network node to at least: receive from a radio network node having a radio access backhaul (WAB) information, including information related to the radio network node having a WAB, wherein the WAB information includes at least a first indication indicating that the radio network node is a radio network node having a WAB; and store the received WAB information in association with the radio network node having a WAB.

[0008] According to a third aspect of this disclosure, a method is provided performed by a radio network node having a radio access backhaul. The method includes including, in a message sent to a core network node, radio access backhaul (WAB) related information of the radio network node having a radio access backhaul, wherein the WAB related information includes at least a first indication indicating that the radio network node is a radio network node having a radio access backhaul.

[0009] According to a fourth aspect of this disclosure, a method performed by a core network node is provided. The method includes: receiving from a radio network node having a radio access backhaul a message including radio access backhaul (WAB) related information of the radio network node having a radio access backhaul, wherein the WAB related information includes at least a first indication indicating that the radio network node is a radio network node having a radio access backhaul; and storing the received WAB related information in association with the radio network node having a radio access backhaul.

[0010] According to a fifth aspect of this disclosure, a radio network node with wireless access backhaul is provided, which includes components for performing any step of any method according to a third aspect.

[0011] According to a sixth aspect of this disclosure, a core network node is provided, which includes components for performing any step of any method according to any aspect of the fourth aspect.

[0012] According to a seventh aspect of this disclosure, a computer-readable storage medium having program instructions stored thereon is provided, wherein the instructions, when executed by at least one processor, cause at least one processor to perform any method according to a third or fourth aspect.

[0013] According to the eighth aspect of this disclosure, a computer program product including program instructions is provided, which, when executed by at least one processor, cause at least one processor to perform any method according to the third or fourth aspect.

[0014] According to a ninth aspect of this disclosure, a computer program is provided that includes program instructions that, when executed by at least one processor, cause at least one processor to perform any method according to a third or fourth aspect.

[0015] The embodiments described above provide solutions for avoiding / accepting multi-hops in communication networks including radio network nodes with wireless access backhaul. These solutions allow control over whether multi-hops are permitted for backhaul connections.

[0016] It should be understood that the summary portion is not intended to identify key or essential features of the embodiments of this disclosure, nor is it intended to limit the scope of this disclosure. Other features of this disclosure will become readily apparent from the following description. Attached Figure Description

[0017] Some exemplary embodiments will now be described with reference to the accompanying drawings, in which: Figure 1 This is a diagram illustrating a network architecture with WAB deployment; Figure 2 This is a flowchart depicting a method performed by a radio network node having a wireless access backhaul according to some embodiments of the present disclosure; Figure 3 This is a flowchart depicting a method performed by a core network node according to some embodiments of the present disclosure; Figure 4 An example NG connection establishment process according to some embodiments of this disclosure is shown; Figure 5 This is a flowchart depicting another method performed by a radio network node with wireless access backhaul according to some embodiments of the present disclosure; Figure 6 This is a flowchart depicting another method performed by a core network node according to some embodiments of the present disclosure; Figure 7 An example registration process according to some embodiments of this disclosure is shown; Figure 8 This is a flowchart depicting another method performed by a radio network node with wireless access backhaul according to some embodiments of the present disclosure; Figure 9 This is a flowchart depicting another method performed by a core network node according to some embodiments of the present disclosure; Figure 10 An example N2 switching process according to some embodiments of this disclosure is shown; Figure 11 This is a flowchart depicting another method performed by a radio network node with wireless access backhaul according to some embodiments of the present disclosure; Figure 12 This is a flowchart depicting another method performed by a radio network node with wireless access backhaul according to some embodiments of the present disclosure; Figure 13 An example Xn switching process according to some embodiments of this disclosure is shown; Figure 14 An example signaling diagram of broadcasting WAB-related information according to some embodiments of this disclosure is shown; Figure 15 This is a flowchart depicting another method performed by a radio network node with wireless access backhaul according to some embodiments of the present disclosure; Figure 16 This is a flowchart depicting another method performed by a radio network node with wireless access backhaul according to some embodiments of the present disclosure; Figure 17 Example signaling diagrams illustrating the application of WAB-related information during RRC procedures according to some embodiments of this disclosure are shown; and Figure 18 A simplified block diagram of an apparatus according to some embodiments of the present disclosure is shown. Detailed Implementation

[0018] Some exemplary embodiments will now be described more fully below with reference to the accompanying drawings, which illustrate some, but not all, of the embodiments. In fact, exemplary embodiments may take many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided to enable this disclosure to meet applicable legal requirements. The same reference numerals throughout refer to the same elements.

[0019] In the following description and claims, unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains.

[0020] References to "an embodiment," "embodiment," "example embodiment," etc., in this disclosure indicate that the described embodiment may include a particular feature, structure, or characteristic, but not every embodiment must include that particular feature, structure, or characteristic. Furthermore, these phrases do not necessarily refer to the same embodiment. Moreover, when a particular feature, structure, or characteristic is described in conjunction with an example embodiment, those skilled in the art will understand how to implement that feature, structure, or characteristic in conjunction with other embodiments, whether explicitly described or not.

[0021] It should be understood that although the terms “first” and “second”, etc., may be used herein to describe various elements, these elements should not be limited by these terms. These terms are used only to distinguish one element from another. For example, without departing from the scope of the exemplary embodiments, a first element may be referred to as a second element, and similarly, a second element may be referred to as a first element. As used herein, the term “and / or” includes any and all combinations of one or more of the listed terms.

[0022] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the exemplary embodiments. As used herein, unless the context clearly indicates otherwise, the singular forms “a,” “an,” and “the” are also intended to include the plural forms. It should also be understood that the terms “comprises,” “comprising,” “has,” “having,” “includes,” and / or “including” as used herein indicate the presence of the stated features, elements, and / or components, but do not preclude the presence or addition of one or more other features, elements, components, and / or combinations thereof.

[0023] As used in this application, the term "circuit" may refer to one or more of the following: (a) Hardware circuit implementation only (such as implementation in analog and / or digital circuits only) and (b) A combination of hardware circuitry and software, such as (if applicable): (i) A combination of (multiple) analog and / or digital hardware circuits with software / firmware; and (ii) Any part of a hardware processor (including (multiple) digital signal processors), software, and (multiple) memories that work together to enable a device, such as a mobile phone or server, to perform various functions; and (c) (a ...

[0024] This definition of "circuit" applies to all uses of the term in this application (including in any claim). As another example, as used in this application, the term "circuit" also covers only hardware circuitry or processors (or processors), or a portion of hardware circuitry or processors and their accompanying software and / or firmware. The term "circuit" also covers, for example and if applicable to a particular claim element, baseband integrated circuits or processor integrated circuits for mobile devices, or similar integrated circuits in servers, cellular network devices, or other computing or network devices.

[0025] As used herein, the term "communication network" refers to a network that conforms to any suitable communication standard, such as Long Term Evolution (LTE), LTE-A Advanced, Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), Narrowband Internet of Things (NB-IoT), New Radio (NR), etc. Furthermore, communication between terminal devices and network devices in a communication network can be performed according to any suitable generation of communication protocols, including but not limited to first-generation (1G), second-generation (2G), 2.5G, 2.75G, third-generation (3G), fourth-generation (4G), 4.5G, 5G, future sixth-generation (6G) communication protocols, and / or any other currently known or future-developed protocols. Embodiments of this disclosure are applicable to a variety of communication systems. Given the rapid development of communication technologies, future types of communication technologies and systems embodying this disclosure will naturally emerge. The scope of this disclosure should not be construed as limited to the systems described above.

[0026] As used herein, the term "terminal device" means any terminal device capable of accessing a communication network and receiving services therefrom. By way of example and not limitation, a terminal device may refer to a user equipment (UE) or other suitable device. In the following description, the terms "terminal device," "user equipment," and "UE" are used interchangeably.

[0027] As used herein, the term "radio network node with radio access backhaul" refers to any radio network node capable of providing access to terminal devices and also capable of providing backhaul connections to core network nodes. By way of example and not limitation, a radio network node with radio access backhaul can be a mobile base station (MWAB) or a vehicular repeater (VMR) node with radio access backhaul.

[0028] 3GPP TS23.501 specifies that a Mobile Base Station Relay (MBSR) will only attempt to register and operate as an MBSR if it is served by a donor gNB that has announced its support for MBSR capabilities. In fact, the NG Radio Access Network (RAN) needs to be upgraded to provide services to an MBSR. For example, if... Figure 2 The network architecture shown does not require an NG-RAN upgrade, so the gNB will not broadcast its MWAB support capability. Therefore, the MWAB may be treated as a normal cell and used by another MWAB to attempt a connection and obtain a PDU session for backhaul. However, multi-hop trunking scenarios for backhaul connections may not be desirable.

[0029] Therefore, various embodiments of this disclosure propose solutions for enabling radio network nodes with wireless access backhaul to avoid or enable multi-hop relays for backhaul connections.

[0030] Figure 2 This is a flowchart depicting a method 200 performed by a radio network node with wireless access backhaul according to some embodiments of the present disclosure. In some embodiments, the radio network node with wireless access backhaul may be a MWAB or a VMR node. Note that the operations within the dashed boxes are optional.

[0031] like Figure 2 As shown in block 210, a radio network node with radio access backhaul includes its WAB-related information in a message sent to the core network node. In some embodiments, the core network node may be an Access and Mobility Management Function (AMF) node. Furthermore, the WAB-related information may include at least a first indication that the radio network node is a radio network node with radio access backhaul.

[0032] In some embodiments, WAB-related information may also include a multi-hop policy indicating whether any other radio network node with a radio access backhaul is allowed to connect via the radio network node with the radio access backhaul, i.e., whether the radio network node with the radio access backhaul allows multi-hop relay for backhaul connections.

[0033] Alternatively or additionally, in some embodiments, WAB-related information may include a status indication indicating whether the radio network node with wireless access backhaul is static or mobile. In some embodiments, if the radio network node with wireless access backhaul is static, it allows multi-hop relay. If the radio network node with wireless access backhaul is mobile, it does not allow multi-hop relay.

[0034] Alternatively or additionally, in some embodiments, WAB-related information may also include an indication of whether service is preferred from another radio network node with wireless access backhaul.

[0035] Alternatively or additionally, in some embodiments, the WAB-related information may also include a second indication indicating whether a radio network node with a radio access backhaul is available to serve any other radio network node with a radio access backhaul.

[0036] Figure 3 This is a flowchart depicting a method 300 performed by a core network node according to some embodiments of the present disclosure. In some embodiments, the core network node may be an AMF node.

[0037] like Figure 3 As shown, in block 310, the core network node receives a message from a radio network node with a radio access backhaul, including WAB-related information about the radio network node with the radio access backhaul. In block 320, the core network node stores the received WAB-related information in association with the radio network node with the radio access backhaul.

[0038] In some embodiments, WAB-related information may include a first indication and at least one of a multi-hop policy, a status indication, a preference indication, or a second indication, as described above.

[0039] The transmission and application of WAB-related information will now be described in detail based on some embodiments of this disclosure.

[0040] Figure 4 An example NG connection establishment process according to some embodiments of this disclosure is illustrated. In this example, the radio network nodes with radio access backhaul are MWAB consisting of MWAB-gNB and MWAB-UE, and the core network node is an AMF node.

[0041] The MWAB-gNB can include WAB-related information in the message sent during NG connection establishment with the AMF node to indicate that it is a MWAB, and optionally indicate whether it accepts other MWABs connecting through it, and optionally indicate whether the MWAB is static or mobile. WAB-related information can be included in Next Generation (NG) Application Protocol (AP) messages, such as the NG SETUP REQUEST message. Upon receiving the WAB-related information, the AMF node can store the received WAB-related information in association with the MWAB. Subsequently, the MWAB-UE will act according to the instructions of the AMF node for future attempts to register as a MWAB via the MWAB-gNB.

[0042] like Figure 4As shown, when the MWAB1 gNB establishes an NG connection to AMF1, the MWAB1 gNB sends an NG SETUPREQUEST message. This message includes a first indication that it is a MWAB, and may include a multi-hop policy that allows or disallows the UE to register as a MWAB via uplink (UL) non-access stratum (NAS) transmission over the NG connection; and / or includes a status indication indicating whether the MWAB is static or mobile; and / or includes other indications mentioned above. AMF1 stores this information and responds with an NG SETUP RESPONSE message. Therefore, an NG connection can be established between the MWAB1 gNB and AMF1.

[0043] Figure 5 This is a flowchart depicting another method 500 performed by a radio network node with wireless access backhaul according to some embodiments of the present disclosure. Figure 5 The method 500 shown involves a radio network node with wireless access backhaul registering via an NG connection established by another radio network node with wireless access backhaul.

[0044] like Figure 5 As shown, in block 510, the radio network node with radio access backhaul includes WAB-related information of the radio network node with radio access backhaul in a registration request message sent to the core network node. In one embodiment, the registration request message can be sent via an NG connection established between the second radio network node with radio access backhaul and the core network node. As described above, the WAB-related information may include a first indication and a multi-hop policy and / or status indication and / or preference indication and / or a second indication. Then, in block 520, the radio network node with radio access backhaul receives a registration response message from the core network node indicating whether registration is accepted or rejected. The core network node can determine whether to accept or reject registration based on the WAB-related information included in the registration request message and the WAB-related information of the second radio network node with radio access backhaul previously provided to the core network node during NG connection establishment. In one embodiment, registration can be accepted if the multi-hop policy indication of the second radio network node with radio access backhaul allows multi-hop relay. In one embodiment, if the multi-hop policy of the second radio network node with wireless access backhaul indicates that multi-hop relay is not allowed, registration can be refused using a reason code indicating that the refusal is due to the multi-hop policy.

[0045] Figure 6 This is a flowchart depicting another method 600 performed by a core network node according to some embodiments of the present disclosure. Figure 6The method 600 shown involves a core network node processing registrations from radio network nodes with wireless access backhaul.

[0046] like Figure 6 As shown, in block 610, the core network node receives a registration request message from a first radio network node with a radio access backhaul. In one embodiment, the registration request message can be received via an NG connection established between the core network node and a second radio network node with a radio access backhaul. The registration request message may include WAB-related information of the first radio network node with a radio access backhaul. Then, in block 620, the core network node determines whether to accept or reject registration based on its configured policies and the WAB-related information of the first radio network node with a radio access backhaul included in the received registration request message. In block 630, based on this determination, the core network node sends a registration response message to the first radio network node indicating whether registration is accepted or rejected. Additionally, in some embodiments, if registration is accepted, the core network node may store the received WAB-related information included in the registration request.

[0047] In some embodiments, the configured policies of the core network node may include a predefined multi-hop policy that indicates whether any radio network node with a radio access backhaul can connect via another radio network node with a radio access backhaul, and / or a policy that indicates whether to apply a stored multi-hop policy from each radio network node with a radio access backhaul or to apply a predefined multi-hop policy.

[0048] In some embodiments, where multi-hop relay is generally permitted, the predefined multi-hop policy can also be based on the status indications in the WAB-related information of both the first and second radio network nodes. For example, when a first radio network node with a radio access backhaul attempts to register via an NG connection established between a second radio network node with a radio access backhaul and a core network node, the predefined multi-hop policy may be as follows: Multi-hop relay is not allowed when both the first radio network node with wireless access backhaul and the second radio network node with wireless access backhaul are mobile. Multi-hop relay is not allowed when the first radio network node with wireless access backhaul is static and the second radio network node with wireless access backhaul is mobile. Multi-hop relay is allowed when the first radio network node with wireless access backhaul is mobile and the second radio network node with wireless access backhaul is static; and Multi-hop relay is allowed when both the first radio network node with wireless access backhaul and the second radio network node with wireless access backhaul are static.

[0049] Figure 7 An example registration process according to some embodiments of the present disclosure is illustrated. In this example, MWAB1 has established an NG connection with AMF1, and MWAB2 attempts to register with AMF1 through the NG connection established by MWAB1.

[0050] like Figure 7 As shown, the MWAB2 UE sends a Registration Request message containing its WAB-related information to AMF1 via the NG connection between MWAB1 and AMF1. AMF1 then detects that this is an attempt by the MWAB2 UE to authorize registration for MWAB, and that the registration request is received through the NG connection established by MWAB1. Based on its configured policies and WAB-related information from MWAB1 and MWAB2, AMF1 can decide whether to accept or reject the registration. If registration is accepted, AMF1 sends a Registration Accept message to the MWAB2 UE. If registration is rejected, AMF1 sends a Registration Reject message with a reason code indicating that the MWAB2 UE was not authorized for MWAB due to multi-hop reasons. This rejection can be based on the configured policies at AMF1, which may consider status indications from both MWAB1 and MWAB2 indicating whether the MWAB is static or mobile, and the multi-hop policy from MWAB1. After receiving a Registration Rejected message, the MWAB2 UE can decide to choose another cell for (initial) registration.

[0051] Alternatively, the MWAB1 gNB may indicate in the NG-AP UL NAS transmission message or the NG-AP initial UE message carrying a Registration Request message from the MWAB2 UE that the NG connection is associated with the MWAB gNB. Therefore, the AMF1 can determine how to handle registrations from other MWABs besides MWAB1 via the NG connection established by MWAB1.

[0052] In some embodiments, there is a situation where a MWAB connects to a gNB, and the gNB can initiate an Xn handover to the MWAB cell of that MWAB. The Xn handover is an inter-gNB handover performed between the source gNB and the target gNB via the Xn interface. If the target gNB is a MWAB, a multi-hop relay scenario may occur. Therefore, it is proposed to transmit an indication during the Xn establishment process that indicates whether the source gNB is a MWAB-gNB.

[0053] Figure 8 This is a flowchart depicting another method 800 performed by a radio network node with wireless access backhaul according to some embodiments of the present disclosure. Figure 8 The method 800 shown relates to the operation of the radio network node with radio access backhaul during an N2 handover process (i.e., a handover prepared and performed via the N2 interface between the gNB and the AMF, as defined in TS23.502 Clause 4.9.1.3 “N2 handover between NG-RAN nodes”), rather than a handover performed via the Xn interface between gNBs, and the radio network node with radio access backhaul operates as the target radio network node.

[0054] like Figure 8 As shown, in block 810, a radio network node with radio access backhaul receives a handover request message from a core network node. This handover request message includes an indication that the terminal device to be handed over is a mobile terminal of another radio network node with radio access backhaul. The handover request message may also include any associated WAB-related information stored in the core network node. Then, in block 820, the radio network node with radio access backhaul can determine whether to confirm or deny the handover based on the indication and / or associated WAB-related information included in the handover request message and its multi-hop policy. If the multi-hop policy of the radio network node with radio access backhaul indicates that multi-hop relay is allowed, the radio network node with radio access backhaul can determine to confirm the handover; if the multi-hop policy indicates that multi-hop relay is not allowed, the radio network node with radio access backhaul can determine to deny the handover. Then, in block 830, based on this determination, the radio network node with radio access backhaul sends a handover response message to the core network node indicating whether the handover was confirmed or denied. In one embodiment, based on the determination to confirm the handover, the radio network node with radio access backhaul sends a handover response message confirming the handover. In one embodiment, based on a determined handover rejection, the radio network node with radio access backhaul sends a handover response message indicating handover failure with a reason code indicating that the failure was caused by a multi-hop strategy.

[0055] Figure 9This is a flowchart depicting another method 900 performed by a core network node according to some embodiments of the present disclosure. Figure 9 The method 900 shown relates to the operation of core network nodes during the N2 handover process.

[0056] like Figure 9 As shown, in block 910, the core network node sends a handover request message to the target radio network node. This handover request message includes an indication that the terminal device to be handed over is a mobile terminal of a radio network node with radio access backhaul. The target radio network node can be a regular gNB or a MWAB-gNB. In block 920, the core network node receives a handover response message from the target radio network node indicating whether the handover is acknowledged or rejected. In one embodiment, if the target radio network node is a regular gNB, it can send a handover response message acknowledging the handover, and the core network node receives the handover response message accordingly. In one embodiment, if the target radio network node is a MWAB, it can determine whether to acknowledge or reject the handover based on a multi-hop policy. If the multi-hop policy indicates that multi-hop relay is allowed, the target network node can send a handover response message acknowledging the handover, and the core network node receives the handover response message accordingly. If the multi-hop policy indicates that multi-hop relay is not allowed, the target network node can send a handover response message indicating handover failure with a reason code, and the core network node receives the handover response message indicating handover failure with a reason code accordingly.

[0057] Figure 10 An example N2 handover process according to some embodiments of this disclosure is illustrated. In this example, the radio network node with wireless access backhaul is a MWAB and operates as the target radio network node. Figure 10 As shown, the AMF node indicates in the HANDOVER REQUEST message that the UE to be handed over is a MWAB UE. The MWAB UE indication can be located in the new NG-AP IE of the handover request. Since the target radio network node is the MWAB-gNB, it determines whether to confirm or reject the handover based on the multi-hop policy. If the multi-hop policy indicates that multi-hop relay is allowed, the MWAB-gNB confirms the handover and sends a handover response message confirming the handover. If the multi-hop policy indicates that multi-hop relay is not allowed, the MWAB-gNB rejects the handover and sends a handover response message indicating that the handover failed with the reason code "MWAB UE not accepted".

[0058] Figure 11 This is a flowchart depicting another method 1100 performed by a radio network node with wireless access backhaul according to some embodiments of the present disclosure. Figure 11 The method 1100 shown relates to the operation of a radio network node with wireless access backhaul during Xn handover, and the operation of the radio network node with wireless access backhaul as the target radio network node.

[0059] like Figure 11 As shown, at block 1110, a radio network node with radio access backhaul receives a handover request message from a source radio network node. This handover request message includes an indication that the terminal device to be handed over is a mobile terminal of the radio network node with radio access backhaul. Note that the source radio network node can be a normal gNB or a MWAB-gNB. Then, at block 1120, the radio network node with radio access backhaul determines whether to acknowledge or deny the handover based on the indication in the handover request message and its multi-hop policy. In an embodiment, if the multi-hop policy indicates that multi-hop relay is allowed, the target network node can determine to acknowledge the handover. In an embodiment, if the multi-hop policy indicates that multi-hop relay is not allowed, the target network node can determine to deny the handover. At block 1130, based on this determination, the radio network node with radio access backhaul sends a handover response message to the source radio network node indicating whether the handover is acknowledged or denied. In an embodiment, based on the determination to acknowledge the handover, the radio network node with radio access backhaul sends a handover response message indicating that the handover is acknowledged. In one embodiment, based on a determined rejection of handover, a radio network node with radio access backhaul sends a handover response message indicating handover failure with a reason code indicating that the failure was caused by a multi-hop strategy.

[0060] Figure 12 This is a flowchart depicting another method 1200 performed by a radio network node with wireless access backhaul according to some embodiments of the present disclosure. Figure 12 The method 1200 shown relates to the operation of a radio network node with wireless access backhaul during Xn handover, and the radio network node with wireless access backhaul operates as a source radio network node.

[0061] like Figure 12As shown, in block 1210, a radio network node with radio access backhaul sends a handover request message to a target radio network node. This handover request message includes an indication that the terminal device to be handed over is a mobile terminal belonging to the radio network node with radio access backhaul. The target radio network node can be a regular gNB or a MWAB-gNB. Then, in block 1220, the radio network node with radio access backhaul receives a handover response message from the target radio network node indicating whether the handover is acknowledged or rejected, depending on the target radio network node. If the target radio network node is a regular gNB, the handover can be acknowledged. If the target radio network node is a MWAB-gNB, the handover can be rejected if the multi-hop policy indicates that multi-hop relay is not allowed, and acknowledged if the multi-hop policy indicates that multi-hop relay is allowed.

[0062] Figure 13 An example Xn switching process according to some embodiments of this disclosure is shown. For example... Figure 13 As shown, the source NG-RAN node will indicate in the Handover Request that the UE to be handed over is a MWAB. The source NG-RAN node can be a regular gNB or a MWAB. The MWAB UE indication can be located in the new NG-AP IE of the handover request. If the target NG-RAN node is not a MWAB, it will confirm the handover. If the target NG-RAN node is a MWAB-gNB, it will reject or confirm the handover based on the multi-hop policy. If the multi-hop policy indicates that multi-hop relay is allowed, the target NG-RAN node can confirm the handover. If the multi-hop policy indicates that multi-hop relay is not allowed, the target NG-RAN node can reject the handover using the reason code "MWAB UE not accepted".

[0063] Note that Xn handover requires the source RAN node to know that the UE is a MWAB-UE. Therefore, when a UE is authorized as a MWAB UE, it needs to receive the UE context in the RAN and the indication that the UE is a MWAB-UE from the AMF node in the UE context management message.

[0064] return Figure 2 In box 220, radio network nodes with wireless access backhaul broadcast WAB-related information in the System Information Block (SIB). Figure 14 Example signaling diagrams for broadcasting WAB-related information according to some embodiments of this disclosure are shown. Figure 14 As shown, the MWAB announces its WAB-related information in the SIB, enabling UEs, including the MWAB-UE, to receive the WAB-related information from the MWAB and decide whether to use the MWAB.

[0065] Figure 15This is a flowchart depicting another method 1500 performed by a radio network node with wireless access backhaul according to some embodiments of the present disclosure. Figure 15 As shown, in block 1510, the radio network node with radio access backhaul receives WAB-related information broadcast in the SIB from another radio network node with radio access backhaul. Then, in block 1520, the radio network node with radio access backhaul determines, based on the WAB-related information received from the other radio network node with radio access backhaul, whether to register with the network via the other radio network node with radio access backhaul. If the received WAB-related information indicates acceptance of multi-hop relay, the radio network node with radio access backhaul may decide not to use the other radio network node with radio access backhaul to avoid multi-hop, or use the other radio network node with radio access backhaul if its policy so specifies.

[0066] Figure 16 This is a flowchart depicting another method 1600 performed by a radio network node with wireless access backhaul according to some embodiments of the present disclosure. Figure 16 The method 1600 shown relates to the Radio Resource Control (RRC) process.

[0067] like Figure 16 As shown, in box 1610, during the establishment of an RRC connection with a terminal device, the radio network node with radio access backhaul receives an indication from the terminal device indicating that the terminal device is a mobile terminal belonging to another radio network node with radio access backhaul. Then, in box 1620, the radio network node with radio access backhaul determines whether to accept the RRC connection based on the indication received from the terminal device. Based on the determination that the RRC connection is not accepted, in box 1630, the radio network node with radio access backhaul transmits an RRC connection release message with a reason code to the terminal device. The reason code may indicate that multi-hop relay is not allowed.

[0068] Figure 17 Example signaling diagrams illustrating the application of WAB-related information during RRC procedures according to some embodiments of this disclosure are shown. Figure 17As shown, during the establishment of an RRC connection between the MWAB and the UE, the MWAB receives an indication that the UE is an MWAB-UE. For example, the MWAB indication may be included in an RRC connection establishment complete (MSG5) message. Upon receiving this indication, the MWAB can determine that it will not accept the RRC connection based on a multi-hop policy that disallows multi-hop relays, and then send an RRC connection release message with a reason code (e.g., multi-hop not allowed). Furthermore, after receiving the RRC connection release, the MWAB-UE should not attempt to register with that cell again. In this method, multi-hops can be avoided at an earlier stage (because the rejection is given by the MWAB itself, eliminating the need to send a registration request to the AMF node and have the AMF node reject the registration), thus allowing the MWAB-UE to begin attempting to select another cell.

[0069] Although some exemplary embodiments of this disclosure have been described above, those skilled in the art will understand that the above embodiments can be combined in any way.

[0070] Now for reference Figure 18 , Figure 18 A simplified block diagram of an apparatus 1800, which may be embodied as a radio network node or core network node with wireless access backhaul, is shown. Apparatus 1800 may include at least one processor 1801 (e.g., a data processor (DP)) and at least one memory (MEM) 1802 coupled to at least one processor 1801. Apparatus 1800 may also include transmitting and receiving units 1903 coupled to one or more processors 1801.

[0071] As a non-limiting example, processor 1801 can be any type suitable for the local technical environment and can include one or more of the following: general-purpose computer, special-purpose computer, microprocessor, digital signal processor (DSP), and processor based on a multi-core processor architecture.

[0072] As a non-limiting example, the (multiple) memory (MEM) 1802 can be of any type suitable for the local technical environment and can be implemented using any suitable data storage technology, such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory.

[0073] The memory (MEM) 1802 stores a program (PROG) 1804. PROG 1804 may include instructions that, when executed on the associated processor 1801, enable the device 1800 to operate according to embodiments of this disclosure, such as performing... Figure 2 , 3The methods 200, 300, 500, 600, 800, 900, 1000, 1200, 1500, and 1600, or any combination thereof, shown in 5, 6, 8, 9, 11, 12, 15, and 16. A combination of at least one processor 1801 and at least one memory (MEM) 1802 can form a processing circuit or component 1805 suitable for implementing various embodiments of this disclosure.

[0074] Various embodiments of this disclosure may be implemented by computer programs, software, firmware, hardware, or combinations thereof that can be executed by one or more of processors 1801.

[0075] Generally, various example embodiments can be implemented in hardware or dedicated circuitry, software, logic, or any combination thereof. For example, some aspects may be implemented in hardware, while others may be implemented in firmware or software executable by a controller, microprocessor, or other computing device, but the invention is not limited thereto. While various aspects of the example embodiments of this disclosure may be shown and described as block diagrams, flowcharts, or other graphical representations, it should be understood that, as non-limiting examples, these blocks, apparatuses, systems, techniques, or methods described herein may be implemented in hardware, software, firmware, dedicated circuitry or logic, general-purpose hardware or controllers or other computing devices, or some combination thereof.

[0076] Therefore, it should be understood that at least some aspects of the exemplary embodiments of this disclosure can be implemented in various components such as integrated circuit chips and modules. Therefore, it should be understood that the exemplary embodiments of this disclosure can be implemented in a device embodied as an integrated circuit, wherein the integrated circuit may include circuitry (and possibly firmware) embodying at least one or more of a data processor, a digital signal processor, baseband circuitry, and radio frequency circuitry, configured to operate according to the exemplary embodiments of this disclosure.

[0077] It should be understood that at least some aspects of the exemplary embodiments of this disclosure may be embodied as computer-executable instructions, executable by one or more computers or other devices, such as as one or more program modules. Typically, program modules include routines, programs, objects, components, data structures, etc., that perform a specific task or implement a specific abstract data type when executed by a processor in a computer or other device. The computer-executable instructions may be stored on a computer-readable medium, such as a non-transitory computer-readable medium, such as a hard disk, optical disk, removable storage medium, solid-state memory, RAM, etc. As those skilled in the art will understand, the functionality of program modules may be combined or distributed as needed in various embodiments. Furthermore, this functionality may be embodied, in whole or in part, as firmware or a hardware equivalent such as an integrated circuit, a field-programmable gate array (FPGA), etc.

[0078] Furthermore, while operations are described in a specific order, this should not be construed as requiring these operations to be performed in the specific order shown or sequentially, or requiring the execution of all shown operations to obtain the desired result. In some cases, multitasking and parallel processing may be advantageous. Similarly, while several specific implementation details are contained in the foregoing discussion, these details should not be construed as limiting the scope of this disclosure, but rather as descriptions of features that may be specific to particular embodiments. Certain features described in the context of different embodiments may also be combined and implemented in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented separately in multiple embodiments or in any suitable sub-combination.

[0079] This disclosure includes any novel features or combinations of features expressly disclosed herein, or any generalization thereof. Various modifications and adjustments to the exemplary embodiments of this disclosure may become apparent to those skilled in the art when read in conjunction with the accompanying drawings, in view of the foregoing description. However, any and all modifications will still fall within the scope of the non-limiting exemplary embodiments of this disclosure.

Claims

1. A radio network node with wireless access backhaul, comprising: One or more processors; as well as One or more memories storing instructions that, when executed by the one or more processors, cause the radio network node having wireless access backhaul to at least: The message sent to the core network node includes radio access backhaul (WAB) related information of the radio network node having radio access backhaul, wherein the WAB related information includes at least a first indication indicating that the radio network node is a radio network node with radio access backhaul.

2. The radio network node with wireless access backhaul according to claim 1, wherein the WAB related information further includes a multi-hop policy indicating whether any other radio network node with wireless access backhaul is allowed to connect via the radio network node with wireless access backhaul.

3. The radio network node with wireless access backhaul according to claim 1 or 2, wherein the WAB related information further includes a status indication for indicating whether the radio network node with wireless access backhaul is static or mobile.

4. A radio network node with wireless access backhaul according to any one of claims 1 to 3, wherein the WAB-related information is included by the radio network node with wireless access backhaul in a Next Generation (NG) Application Protocol (AP) message.

5. The radio network node with wireless access backhaul according to claim 4, wherein the NG-AP message is an NG establishment request message when establishing an NG connection with the core network node.

6. The radio network node with wireless access backhaul according to claim 4, wherein the NG-AP message is an NG-AP uplink non-access stratum (NAS) transmission message or an NG-AP initial UE message to the core network node.

7. A radio network node with wireless access backhaul according to any one of claims 1 to 6, wherein the radio network node with wireless access backhaul is further configured such that: Receive a handover request message from the core network node, the handover request message including: Indication indicating that the terminal device to be switched is a mobile terminal with a wireless access backhaul from another radio network node, and associated WAB-related information stored in the core network node. The decision to confirm or reject the handover is made based on the indication in the handover request message; as well as Based on the determination, a handover response message indicating whether the handover is confirmed or rejected is sent to the core network node.

8. A radio network node with wireless access backhaul according to any one of claims 1 to 6, wherein the radio network node with wireless access backhaul is further configured such that: Receive a handover request message from the source radio network node, the handover request message including an indication that the terminal device to be handed over is a mobile terminal of a radio network node with radio access backhaul. The decision to confirm or reject the handover is made based on the indication in the handover request message; as well as Based on the determination, a handover response message indicating whether the handover was confirmed or rejected is sent to the source radio network node.

9. A radio network node with wireless access backhaul according to any one of claims 1 to 6, wherein the radio network node with wireless access backhaul is further configured such that: A handover request message is sent to the target radio network node, the handover request message including an indication that the terminal device to be handed over is a mobile terminal of a radio network node with radio access backhaul; and Receive a handover response message from the target radio network node indicating whether the handover is acknowledged or rejected.

10. A radio network node with wireless access backhaul according to any one of claims 1 to 9, wherein the radio network node with wireless access backhaul is further configured to broadcast the WAB-related information in a System Information Block (SIB).

11. The radio network node with wireless access backhaul according to claim 10, wherein the WAB related information further includes a second indication for indicating whether the radio network node with wireless access backhaul can be used to serve any other radio network node with wireless access backhaul.

12. A radio network node with wireless access backhaul according to any one of claims 1 to 11, wherein the radio network node with wireless access backhaul is further configured such that: Receive WAB-related information broadcast in the SIB from another radio network node having a wireless access backhaul; and Based on the WAB-related information received from the other radio network node with wireless access backhaul, it is determined whether to register with the network via the other radio network node with wireless access backhaul.

13. A radio network node with wireless access backhaul according to any one of claims 1 to 12, wherein the radio network node with wireless access backhaul is further configured such that: During the establishment of a radio resource control (RRC) connection with a terminal device, an indication is received from the terminal device indicating that the terminal device is a mobile terminal of another radio network node with radio access backhaul; Whether to accept the RRC connection is determined based on the indication received from the terminal device; as well as Based on the determination that the RRC connection is not accepted, an RRC connection release message with a reason code is transmitted to the terminal device.

14. The radio network node with wireless access backhaul according to claim 13, wherein the indication of the terminal device is received in the RRC connection establishment completion message.

15. A radio network node with wireless access backhaul according to any one of claims 1 to 14, wherein the radio network node with wireless access backhaul is further configured such that: The registration request message sent to the core network node includes WAB-related information of the radio network node with wireless access backhaul; and The registration response message is received from the core network node. The registration response message indicates whether the registration is accepted or rejected based on the WAB-related information included in the registration request message.

16. A radio network node with wireless access backhaul according to any one of claims 1 to 15, wherein the WAB-related information further includes an indication of whether service is preferred from another radio network node with wireless access backhaul.

17. A radio network node with wireless access backhaul according to any one of claims 1 to 16, wherein the radio network node with wireless access backhaul is a mobile base station (MWAB) or a vehicle-mounted relay node with wireless access backhaul.

18. A radio network node with wireless access backhaul according to any one of claims 1 to 17, wherein the core network node is an Access and Mobility Management Function (AMF) node.

19. A core network node, comprising: One or more processors; as well as One or more memories store instructions that, when executed by the one or more processors, cause the core network node to at least: Receive a message from a radio network node having a radio access backhaul, including radio access backhaul (WAB) related information of the radio network node having a radio access backhaul, wherein the WAB related information includes at least a first indication indicating that the radio network node is a radio network node having a radio access backhaul; and The received WAB-related information is stored in association with the radio network node having wireless access backhaul.

20. The core network node of claim 19, wherein the WAB-related information further includes a multi-hop policy indicating whether any other radio network node with a radio access backhaul is allowed to connect via the radio network node with the radio access backhaul.

21. The core network node of claim 19 or 20, wherein the WAB-related information further includes a status indication for indicating whether the radio network node with wireless access backhaul is static or mobile.

22. The core network node according to any one of claims 19 to 21, wherein the WAB-related information is included in a Next Generation (NG) Application Protocol (AP) message by a radio network node having a radio access backhaul.

23. The core network node of claim 22, wherein the NG-AP message is an NG establishment request message when establishing an NG connection with the radio network node.

24. The core network node according to claim 22, wherein the NG-AP message is an NG-AP uplink non-access stratum (NAS) transmission message or an NG-AP initial UE message.

25. The core network node according to any one of claims 19 to 23, wherein the core network node is further configured to: A registration request message is received from a first radio network node with a wireless access backhaul, the registration request message including the WAB-related information of the first radio network node with a wireless access backhaul; Based on the configured policies of the core network node and the WAB-related information of the first radio network node with wireless access backhaul included in the received registration request message, determine whether to accept or reject the registration. Based on the determination to accept the registration, the received WAB-related information, including that included in the registration request message, is stored in the core network node, and Based on the determination, a registration response message indicating whether the registration is accepted or rejected is sent to the first radio network node with wireless access backhaul.

26. The core network node according to any one of claims 19 to 25, wherein the WAB-related information further includes an indication of whether service is preferred from another radio network node with wireless access backhaul.

27. The core network node of claim 25 or 26, wherein the configured policy of the core network node includes at least one of the following: a predefined multi-hop policy indicating whether any radio network node with a radio access backhaul can connect via another radio network node with a radio access backhaul; or a policy indicating whether to apply the multi-hop policy in the stored WAB-related information or to apply the predefined multi-hop policy.

28. The core network node of claim 27, wherein the predefined multi-hop policy is based on the status indication in the WAB-related information of both the first radio network node and the second radio network node.

29. The core network node according to any one of claims 19 to 28, wherein the core network node is further configured to: A handover request message is sent to the target radio network node, the handover request message including an indication that the terminal device to be handed over is a mobile terminal of a radio network node with radio access backhaul; and Receive a handover response message from the target radio network node indicating whether the handover is acknowledged or rejected.

30. The core network node according to any one of claims 19 to 29, wherein the core network node is an Access and Mobility Management Function (AMF) node.

31. The core network node according to any one of claims 19 to 30, wherein the radio network node having radio access backhaul is a mobile base station (MWAB) with radio access backhaul.

32. A method performed by a radio network node having wireless access backhaul, comprising: The message sent to the core network node includes radio access backhaul (WAB) related information of the radio network node having radio access backhaul, wherein the WAB related information includes at least a first indication indicating that the radio network node is a radio network node with radio access backhaul.

33. The method of claim 32, wherein the WAB-related information further includes a multi-hop policy indicating whether any other radio network node with a radio access backhaul is allowed to connect via the radio network node with the radio access backhaul.

34. The method of claim 32 or 33, wherein the WAB related information further includes a status indication for indicating whether the radio network node with wireless access backhaul is static or mobile.

35. The method according to any one of claims 32 to 34, wherein the WAB-related information is included in a Next Generation (NG) Application Protocol (AP) message by the radio network node having a wireless access backhaul.

36. The method of claim 35, wherein the NG-AP message is an NG establishment request message when establishing an NG connection with the core network node.

37. The method of claim 35, wherein the NG-AP message is an NG-AP uplink non-access stratum (NAS) transmission message or an NG-AP initial UE message to the core network node.

38. The method according to any one of claims 32 to 37, further comprising: The handover request message is received from the core network node. The handover request message includes: an indication that the terminal device to be handed over is a mobile terminal of another radio network node with radio access backhaul, and associated WAB related information stored in the core network node. Based on the indication in the handover request message, determine whether to confirm or reject the handover; and Based on the determination, a handover response message indicating whether the handover is confirmed or rejected is sent to the core network node.

39. The method according to any one of claims 32 to 37, further comprising: Receive a handover request message from the source radio network node, the handover request message including an indication that the terminal device to be handed over is a mobile terminal of a radio network node with radio access backhaul. The decision to confirm or reject the handover is made based on the indication in the handover request message; as well as Based on the determination, a handover response message indicating whether the handover was confirmed or rejected is sent to the source radio network node.

40. The method according to any one of claims 32 to 37, further comprising: Send a handover request message to the target radio network node, the handover request message including an indication that the terminal device to be handed over is a mobile terminal of a radio network node with radio access backhaul; as well as Receive a handover response message from the target radio network node indicating whether the handover is acknowledged or rejected.

41. The method according to any one of claims 32 to 40, further comprising: Broadcast the WAB-related information in the System Information Block (SIB).

42. The method of claim 41, wherein the WAB related information further includes a second indication for indicating whether the radio network node having a wireless access backhaul is available to serve any other radio network node having a wireless access backhaul.

43. The method according to any one of claims 32 to 42, further comprising: Receive WAB-related information of the other radio network node with wireless access backhaul broadcast in the SIB from the other radio network node with wireless access backhaul. as well as Based on the WAB-related information received from the other radio network node with wireless access backhaul, it is determined whether to register with the network via the other radio network node with wireless access backhaul.

44. The method according to any one of claims 32 to 43, further comprising: During the establishment of a radio resource control (RRC) connection with a terminal device, an indication is received from the terminal device indicating that the terminal device is a mobile terminal of another radio network node with radio access backhaul; Whether to accept the RRC connection is determined based on the indication received from the terminal device; as well as In response to determining that the RRC connection is not accepted, an RRC connection release message with a reason code is transmitted to the terminal device.

45. The method of claim 44, wherein the indication of the terminal device is received in the RRC connection establishment complete message.

46. ​​The method according to any one of claims 32 to 45, further comprising: The registration request message sent to the core network node includes the WAB-related information of the radio network node with wireless access backhaul; as well as The registration response message is received from the core network node. The registration response message indicates whether the registration is accepted or rejected based on the WAB-related information included in the registration request message.

47. The method according to any one of claims 32 to 46, wherein the WAB-related information further includes an indication of whether service is preferred from another radio network node having a wireless access backhaul.

48. The method according to any one of claims 32 to 47, wherein the radio network node having a wireless access backhaul is a mobile base station (MWAB) or a vehicle-mounted relay node with a wireless access backhaul.

49. The method according to any one of claims 32 to 48, wherein the core network node is an Access and Mobility Management Function (AMF) node.

50. A method executed by a core network node, comprising: Receive a message from a radio network node having a radio access backhaul, including radio access backhaul (WAB) related information of the radio network node having a radio access backhaul, wherein the WAB related information includes at least a first indication indicating that the radio network node is a radio network node having a radio access backhaul; and The received WAB-related information is stored in association with the radio network node having wireless access backhaul.

51. The method of claim 50, wherein the WAB-related information further includes a multi-hop policy indicating whether any other radio network node with a radio access backhaul is allowed to connect via the radio network node with the radio access backhaul.

52. The method of claim 50 or 51, wherein the WAB related information further includes a status indication for indicating whether the radio network node with wireless access backhaul is static or mobile.

53. The method according to any one of claims 50 to 52, wherein the WAB-related information is included in a Next Generation (NG) Application Protocol (AP) message by a radio network node having a wireless access backhaul.

54. The method of claim 53, wherein the NG-AP message is an NG establishment request message when establishing an NG connection with the radio network node.

55. The method of claim 53, wherein the NG-AP message is an NG-AP uplink non-access stratum (NAS) transport message or an NG-AP initial UE message.

56. The method according to any one of claims 50 to 55, further comprising: A registration request message is received from a first radio network node with wireless access backhaul via an NG connection established between a second radio network node with wireless access backhaul and the core network node. The registration request message includes the WAB-related information of the first radio network node with wireless access backhaul. Based on the configured policies of the core network node and the WAB-related information of the first radio network node with wireless access backhaul included in the received registration request message, determine whether to accept or reject the registration. Based on the acceptance of the registration, the received WAB-related information is stored in the core network node; as well as Based on the determination, a registration response message indicating whether the registration is accepted or rejected is sent to the first radio network node with wireless access backhaul.

57. The method according to any one of claims 50 to 56, wherein the WAB-related information further includes an indication of whether service is preferred from another radio network node having a wireless access backhaul.

58. The method of claim 56 or 57, wherein the configured policy of the core network node includes at least one of the following: a predefined multi-hop policy indicating whether any radio network node with a radio access backhaul can connect via another radio network node with a radio access backhaul; or a policy indicating whether to apply the multi-hop policy in the stored WAB-related information or to apply the predefined multi-hop policy.

59. The method of claim 58, wherein the predefined multi-hop policy is based on the status indication in the WAB-related information of both the first radio network node and the second radio network node.

60. The method according to any one of claims 50 to 59, further comprising: Send a handover request message to the target radio network node, the handover request message including an indication that the terminal device to be handed over is a mobile terminal of a radio network node with radio access backhaul; as well as Receive a handover response message from the target radio network node indicating whether the handover is acknowledged or rejected.

61. The method according to any one of claims 50 to 60, wherein the core network node is an Access and Mobility Management Function (AMF) node.

62. The method according to any one of claims 50 to 61, wherein the radio network node having wireless access backhaul is a mobile base station (MWAB) or a vehicle-mounted relay node with wireless access backhaul.

63. A radio network node with wireless access backhaul, comprising components for performing any step of the method according to any one of claims 32 to 49.

64. A core network node comprising components for performing any step of the method according to any one of claims 50 to 62.

65. A computer-readable medium storing program instructions that, when executed by one or more processors, cause the one or more processors to perform the method according to any one of claims 32 to 62.

66. A computer program product comprising program instructions that, when executed by one or more processors, cause the one or more processors to perform the method according to any one of claims 32 to 62.

67. A computer program comprising program instructions that, when executed by one or more processors, cause the one or more processors to perform the method according to any one of claims 32 to 62.

Images