Managing network connectivity in a wireless communication system

Abstract

A method for use in managing connectivity of a wireless access backhaul, WAB, node, 630 connected or to be connected to at least one core network 620 via a backhaul gNB 610, the WAB node including a gNB component, 632 and a Mobile Termination component, 631, the method at the WAB node comprising: Sending, 601 information associated with the WAB node, the information including at least one of: an indication that the information is associated with a WAB node; information associated with one or more capabilities supported by the WAB node; information for indicating that the WAB node comprises both the gNB component and the Mobile Termination component; and information indicating local services of the WAB node. The information associated with one or more capabilities supported by the WAB node may include at least one of: information indicating whether the WAB node is configured to operate while moving; information related to the mobility of the WAB node; information indicating whether the WAB node is configured to operate as a Femto node; information indicating the load capability of the WAB node, and information indicating the levels of quality of service. The WAB node may be a mobile WAB (MWAB) node.

Description

Field of the Invention The present invention generally relates to managing network connectivity in a wireless communication system. Particularly, the present invention relates to managing network connectivity- in a wireless communication system including at least one Wireless Access Backhaul, WAB, node. More particularly, the present invention relates to managing network connectivity in a wireless communication system including at least one mobile Wireless Access Backhaul, WAB, node. Background Wireless communication systems are largely deployed to address a wide range of applications, from mobile broadband, massive machine type communications to Ultra Reliable Low Latency Communications (URLLC). Such systems allow a plurality of user equipment (UE) or mobile terminals to share the wireless medium to exchange several types of data content (e.g., video, voice, messaging ...) over a radio access network (RAN) through one or more base stations. The base stations are conventionally wired-connected (e.g., through fiber) to a core network, forming an intermediate network, named backhaul (BH). Examples of such wireless multiple-access communication systems include systems based on 3rd generation partnership project (3GPP - RTM) standards, such as fourth-generation (4G) Long Term Evolution (LTE) or recent fifth-generation (5G) New Radio (NR) systems, or systems-based IEEE 802.11 standards, such as WiFi. The demand for network densification increases due to the rising number of users and higher throughput requirement. Facing the issues of high deployment costs and time of the wired backhaul networks with network densification, 3GPP lias proposed, in recent release 16 for 5G NR, a wireless backhaul, also known as Integrated Access and Backhaul, IAB, where part of the wireless (i.e., radio) spectrum is used for the backhaul connection of base stations instead of fiber. The wireless backhaul communications (between base stations) may use the same radio resources as access communications (between a base station and UEs). IAB turns out to be a competitive alternative to the fiber-based backhauling in dense areas or areas difficult to cover, as it allows scalable and rapid installations without the burden of cabling the base stations. IAB is most likely to operate in the millimeter wave (mmWave) band to achieve the required Gbps (gigabits per second) data rate. Urban environments are usually characterized by a high density-- of users along with the presence of a significant number of vehicles (e.g., public / private passenger transportation, goods delivery, food trucks ...). The speed of some of the vehicles may be pretty low or at least similar to pedestrian speed and some of these vehicles may even be temporarily stationary. Some of these vehicles (e.g., buses, trains or trams), may have predictable routes and / or limited mobility areas (e.g., some vehicles, such as food trucks or promotional vehicles, may be located outside stadiums or show venues) while others may have predictable stationary locations (e.g., taxis). 3GPP is considering that such vehicles could offer an opportunity to increase network coverage and connectivity to the UEs inside the vehicles, or even to UEs in proximity to the vehicles, by installing on these vehicles on-board base stations (or base station elements) that would act as relays. These relays would rely on 5G wireless backhaul (typically IAB, or Integrated Access &Backhaul) for connecting to a fixed donor device. Thus, based upon the fixed IAB foundations set out in Releases 16 and 17, 3GPP is now considering Mobile IAB systems and architecture, as a part of the Release 18 framework, in order to address scenarios focusing on mobile lAB-nodes mounted on vehicles (for example, a bus, a train, a taxi). In such scenarios, mobile lAB-nodes can also be referred to as Vehicle Mounted Relays (VMR), providing 5G coverage / capacity to on-board and / or surrounding UEs. The technical benefits of using vehicle relays include, among others, the ability of the relay vehicle to get better coverage than the nearby UE, thanks to better RF / antenna capabilities, thus providing the UE with a better link to the macro network. Additionally, a vehicle relay is expected to have less stringent power / battery constraints than the UEs. Some enhancements of the existing wireless access backhauling, WAB, systems and architecture arc further considered by 3GPP for Release 19 and further, considering the need for 5G access for UEs onboard aircrafts, cruise ships, helicopters and vehicles in remote areas with limited sky visibility (e.g. where terrestrial cellular coverage or Wi-Fi coverage is not available), support for onboard / on-site mobile edge computing (MEC), local services, and direct local inter-UE communications or local Next Generation Node B (gNB) deployment in public safety or disaster recover}- scenarios. The backhauling links the base stations providing 5G access in such scenarios, which base station are referred to as mobile wireless access backhauling (MWAB) nodes, would then be operated over either a terrestrial network (TN), as of Release 18, or a non-terrestrial network (NTN), with a possibility to handover communications from a terrestrial network to a non-terrestrial network and vice-versa. As part of these wireless backhauling enhancements, 3GPP is also considering some evolution to the former LTE-based Femto framework, including a new 5G Femto or 5g Femtocell that would offer 5G indoor coverage improvement while allowing High bandwidth and throughput at home for new immersive applications such as AR / VR / MR gaming, e-sports, UHD 8K video, telepresence, etc. A WAB (WAB) node is made of a Mobile Termination, WAB-MT, part used for connecting to some fixed existing infrastructure. The WAB, WAB, node also embeds a gNB, WAB-gNB, used to provide backhauling connectivity as previously discussed. WAB nodes may be referred to as mobile Wireless Access Backhaul (MWAB) nodes. Reference to MWAB nodes should be taken to refer to WAB nodes. As a given wireless access backhauling system (made of NG-RAN network nodes or base stations, gNB, and Core Network entities) may, at some point, be made up of base stations / Core functions (belonging to former Releases) which do not have any ability to differentiate a MWAB node from any legacy Mobile Terminal, and more recent base stations / Core functions (belonging to release 19 and further) having the ability to handle MWAB nodes connectivity, it is important for the NG-RAN network nodes (i.e., base stations, gNB) and / or the Core Network Functions to differentiate such kinds of Mobile Terminals. This is particularly true as, on one side, MWAB node may require specific functionalities, e.g., in terms of mobility management, that only a limited set of NG-RAN network nodes or Core Network functions are able to provide while, on the other side, a mobile WAB, MWAB, node is likely to serve a significant number of UEs, which may induce a significant load that not all the serving base station / Core functions are to support. Therefore, it is desirable to provide solutions to address at least some of the aforementioned issues, while limiting the complexity of the processing at a MWAV node as well as the latency that would result from such processing. Summary The invention generally relates to managing connectivity of a MWAB nodes in or to a wireless communication system, preferably managing the establishment of an MWAB node to a core network via backhaul base station or to other MWAB nodes. The invention generally docs this by signalling information associated with an MWAB node, e.g. MWAB information, preferable through a message exchanges, to various nodes or entities within a communication system including a WAB system and a core network to allow the nodes or entities to know about the nature of the MWAB node and make a determination on whether the node or entity may support, serve or service the MWAB node. The determination being either about compatibility with MWAB nodes and / or the load from the MWAB node once connected. The invention also generally relates to nodes or entities advertising, through signalling information associated with MWAB nodes, their support of MWAB nodes. That is to say their capability to serve the MWAB nodes or, put another way, their compatibility- with MWAB nodes. This allows for the MWAB nodes or nodes (such as BH gNB) or entities to know which nodes or entities are able to provide support. The invention has particular relevance to a mobile communication network (e.g. 5G) utilizing MWAB nodes. By signalling the MWAB information the invention is able to perform load management and ensure that the correct nodes or entities are connected to support the MWAB node and any UEs connected. This is especially useful as it allows the appropriate entities or nodes within the core network to be found which can provide support for all the features of the MWAB node or, in some cases, some of the features of the MWAB node. A first aspect of the present invention is set out in claim 1. Some preferable features of the first aspect are set out in dependent claims 2 to 16 and 36 to 54. Preferable features described in relation to the other aspects of the invention may be preferable features of the first aspect. An apparatus, computer program, and computer-readable medium of the first aspect are provided in claims 55, 56 and 57 respectively. A second aspect of the present invention is provided in claim 17. Preferable features of the second aspect are set out in dependent claims 18 to 24 and 36 to 54. Preferable features described in relation to the other aspects of the invention may be preferable features of the second aspect. An apparatus, computer program, and computer-readable medium of the second aspect are provided in claims 58, 59 and 60 respectively. A third aspect of the present invention is provided in claims 25. Preferable features of the third aspect are set out in dependent claims 26 to 31 and 36 to 54. Preferable features described in relation to the other aspects of the invention may be preferable features of the third aspect. An apparatus, computer program, and computer-readable medium of the third aspect are provided in claims 61, 62 and 63 respectively. A fourth aspect of the present invention is provided in claims 32. Preferable features of the fourth aspect are set out in dependent claims 33 to 54. Preferable features described in relation to the other aspects of the invention may be preferable features of the fourth aspect. An apparatus, computer program, and computer-readable medium of the fourth aspect arc provided in claims 64, 65 and 66 respectively. A fifth aspect of the present invention is provided in claims 67. Preferable features of the fifth aspect are set out in dependent claims 68 to 76. Preferable features described in relation to the other aspects of the invention may be preferable features of the fifth aspect. An apparatus, computer program, and computer-readable medium of the fifth aspect are provided in claims 77, 78 and 79 respectively. A sixth aspect of the present invention is provided in claims 80. Preferable features of the sixth aspect are set out in dependent claims 81 to 86. Preferable features described in relation to the other aspects of the invention may be preferable features of the sixth aspect. An apparatus, computer program, and computer-readable medium of tire sixth aspect are provided in claims 87, 88 and 89 respectively. A seventh aspect of the present invention provides a method for use in managing connectivity of a wireless access backhaul (WAB) node in a wireless communication system, the WAB node including a gNB component and a mobile termination component, the method comprising: sending, directly or indirectly, from a first node or entity of the wireless communication system to a second wireless node or entity of the wireless communication system, information associated with the WAB node, the information including at least one of: an indication that the information is associated with a WAB node; information associated with one or more capabilities supported by the WAB node; information for indicating that the WAB node comprises both the gNB component and the mobile termination component; information indicating local services of the WAB node; and information indicating a node or entity is capable of serving a WAB node. Preferably, the seventh aspect, or any other aspect, may further comprise receiving, by the first node or entity from the second node or entity, directly or indirectly, a connection message comprising connection information based on the information associated with the WAB node received from the first node or entity. Preferably, in the case that the second node or entity is unable to serve the WAB node, the connection infomiation indicates a rejection of connection; and wherein, in the case that the second node or entity is able to serve the WAB node, the connection information indicates an acceptance of connection. In some cases, it may be based on whether the second node or entity may serve, service or support the WAB node. Preferably, tire connection infomiation, in the case the second node or entity is unable to serve the WAB node, comprises information indicating the cause of rejection. More preferably, the connection message is a CONNECTION CONFIRMATION message. Preferably, in the case the second node or entity is unable to serve the WAB node, Preferably, the first node or entity of the wireless communication system comprises the WAB node and the second wireless node or entity comprises a node or entity of a core network of the wireless communication system. More preferably, the second node or entity may comprise one of Access and Mobility Management Function (AMF) entity, User Plane Function (UPF) entity or backhaul gNB. Preferably, in the case the case of the second node or entity comprising an AMF and the AMF is unable to serve the WAB node, the CONNECTION CONFIRMATION message is at least one of: registration reject and NG setup failure. Preferably, in the case the second node or entity comprises a gNB and the gNB is unable to service the WAB node, the connection confirmation message is at least one of RRCReject and RRCReconfiguration. Preferably, the seventh aspect, or any other aspect, further comprises receiving, by a third node or entity of the wireless communication system from the first node, the information associated with the WAB node; and sending, by the third node or entity to the second node or entity, the information associated with the WAB node. The third node or entity may be considered an intermediate node or entity. The third node or entity may relay at least some of the received information to the second node or entity. Preferably, the third node or entity may comprise a backhaul gNB. Preferably, the third node or entity comprises anode or entity of a core network of the wireless communication system. Preferably, the third node or entity may comprise a User Plane Function (UPF) entity Preferably, the aspects may further comprise receiving, by the first node or entity, a connection confirmation message from the third node or entity, the connection confinnation message comprising connection information based on the infomiation associated with the WAB node received from the first node or entity. More preferably, in the case that the third node or entity is unable to serve the WAB node, the connection information indicates a rejection of connection; and wherein, in the case that the third node or entity is able to serve the WAB node, the connection information indicates an acceptance of connection. Preferably, in the case the third node or entity includes information on the capability of tire second node or entity, tire connection information indicates either a rejection of connection or an acceptance of connection based on whether the second node or entity is capable to serve the WAB node. Further preferable features of the seventh aspect are set out in the dependent claims. Preferable features described in relational to the other aspects of the invention may be preferable features of the seventh aspect. An apparatus, computer program and a computer-readable medium may be provided for the seventh aspect. Any feature or element in one aspect of the invention may be applied to other aspects of tire invention, in any appropriate combination. In particular, but not exclusively, method aspects may be applied to apparatus / device / unit aspects, and vice versa. In the aspects of the invention, the information associated with the WAB node may just be at least one of capability information associated with the WAB node and status information associated with the WAB node, but the invention is set out in the specific numbered aspects is most preferable, i.e. that it provides at least one of a specific type of capability information. Furthermore, features implemented m hardware may be implemented in software, and vice versa. Any reference to software and hardware features herein should be construed accordingly. For example, in accordance with other aspects of the invention, there are provided a computer program comprising instructions which, when the program is executed by one or more processing units, cause the one or more processing units to carry out the method of any aspect or example described above or below and a computer readable storage medium carrying the computer program. Brief Description of the Drawings Different aspects of the invention will now be described, by way of example only, and with reference to the following drawings in which: Figure 1 is a schematic diagram illustrating an example wireless communication system in which the present invention may be implemented according to one or more embodiments; Figure 2 is a block schematic diagram illustrating an example wireless communication system (or Wireless Access Backhaul system) in which the present invention may be implemented according to one or more embodiments; Figure 3 is a block schematic diagram illustrating an example wireless communication system (or Wireless Access Backhaul system) in which the present invention may be implemented according to one or more embodiments; Figure 4 shows a block schematic representation of a wireless communication device in accordance with embodiments of the present invention; Figure 5 is a block schematic diagram illustrating an example arrangement of a wireless communication system (or Wireless Access Backhaul system) in which the present invention may be implemented according to one or more embodiments; Figure 6 and Figure 7 are schematic and simplified diagrams illustrating example message flows for use in managing network connectivity in a wireless communication system including at least one Wireless Access Backhaul, WAB, node in accordance with one or more embodiments of the present invention and which may be used for managing the advertising by a WAB node of its mobility capability and status; Figure 8 is a schematic and simplified diagram illustrating example message flow for use in managing network connectivity in a wireless communication system including at least one Wireless Access Backhaul, WAB, node in accordance with one or more embodiments of the present invention and which may be used for managing the advertising by a base station of its capability and status; Figure 9 is schematic and simplified diagram illustrating example message flow for use in managing network connectivity in a wireless communication system including at least one Wireless Access Backhaul (WAB) node in accordance with one or more embodiments of the present invention and which may be used for managing the advertising by a WAB node of its mobility capability7 and status; Figure 10 is a flowchart of an example method for managing a Wireless Access Backhaul (WAB) node connectivity according to one or more embodiments of the present invention; Figure 11 is a flowchart of an example method performed at a wireless communication device in accordance with one or more embodiments of the present invention; and Figure 12 is a flowchart of an example method performed at a wireless communication device in accordance with one or more embodiments of the present invention. Detailed Description Figure 1 illustrates an example communication system 100 in which the present invention may be implemented according to one or more embodiments. As depicted, the example system 100 is a wireless communication system, in particular a mobile radio communication system such as a fifth-generation (5G) New Radio (NR) system including a Wireless Access Backhaul (WAB) communication system or network. Although in the following description, embodiments and examples of embodiments of the present invention will be described with respect to a 5G NR system, it will be appreciated that it is not intended that the present invention is necessarily limited to 5G NR systems and may be used in any wireless communication systems having an integrated access and backhaul communication system which shares radio resources for wireless access links and wireless backhaul links. The system 100 comprises a plurality of UEs (User Equipment) 111, 112, 113, 121, 122, 123, 131, 132, 133, 134, 141, 142, 143, 151, 152, 153 and 154, a communication satellite 160, a satellite dish 101, a remote core network 170, three fixed Base Stations 102, 103 and 104, a plurality7 of Mobile Wireless Access Backhaul (MWAB) nodes 110, also referred to as mobile wireless access backhaul devices, (mounted on plane 161), 120a and 120b (mounted on train 162), 130 (mounted on a house 163), 140 (mounted on a Unmanned Aerial Vehicle (UAV) 164) and 150 (mounted on a backpack 165 or other carrier that can be carried by a user (e.g. is a disaster zone)). In more general terms, the MWAB node may be mounted on or in a vehicle (such as a train, bus, taxi, tram, etc.) and / or an aircraft or flying vehicle (such as a plane, UAV, helicopter, etc. ) and / or a building (such as a house, enterprise / company / office building, hotel building, airport building, sports / event buildings, shopping center building, etc..) and / or a portable carrier that can be carried by a user, for example, in a disaster zone or for public safety (such as a backpack, bag, etc), and / or public infrastructure elements or units (such as lamp posts, traffic lights, etc.). In an example where the MWAB node is implemented in a 5G femto network, the MWAB node functions as a 5G femto node and may be mounted at a building (such as a house, enterprise / company / office building, hotel building, airport building, sports / event buildings, shopping center building, etc..) and / or public infrastructure elements or units (such as lamp posts, traffic lights, etc.). In some cases, particularly but not exclusively when a MWAB node 130 is mounted to a fixed structure, e.g. when the MWAB node is functioning as a 5G femto node, the MWAB node 130 may be considered a WAB node, which also may be referred to as a Home gNB despite based on the same architecture as the MWAB node, i.e. the Home gNB comprising the Mobile Terminal and gNB required to be a Wireless Access Backhaul node. Some examples ofUEs include smartphoncs / tablcts (such as UEs 111, 123, 134, 142, 152), XR headsets (such as UEs 112, 122, 132), cameras (such as UEs 141 and 151), fixed video cameras (such as UEs 113, 121, 133, 153) or mobile / wearable video cameras (such as UEs 143 and 154). In general, the UE may be any portable or handheld or mobile telephone, a smartphone, a tablet, a portable or fixed computer, fixed or mobile camera, portable television, other smart devices or other similar wireless communication device. In the following description, the term UE will be used and it is not intended to limit the description to any particular type of wireless communication device. Base stations 102, 103 and 104 are interconnected through a wired link infrastructure 180, preferably based on optical fiber or any other wired means. Base stations 102, 103 and 104 are also connected to the core network 170 through a wired link infrastructure 190, preferably based on optical fiber or any other wired means. In some embodiments, base stations 102, 103 and 104 are 5G NR base stations (referred to as a gNB), as defined in 3GPP TS 38.300 vl8.0.0 specification document. Satellite dish 101 (e.g. satellite gateway) is also connected to wired link infrastructure 180 or 190, or to both infrastructures 180, 190. That is to say, the satellite dish 110 is connected to one or more of the wired link infrastructures 180, 190. While infrastructure 180 and 190 are referred to as separate, it should be understood that it may be the same infrastructure. In order to extend the network coverage of base stations 102, 103 and 104 and reach the remote UEs 111, 112, 113, 121, 122, 123, 131, 132, 133, 134, 141, 142, 143, 151, 152, 153 and 154, MWAB nodes, or MWAB-nodes, 110, 120a, 120b, 130, 140 and 150, have been installed on vehicles / mobile equipment 161, 162, 163, 164 and 165. By acting as relaying nodes between the base stations 102, 103 and 104 and the UEs 111, 112, 113, 121, 122, 123, 131, 132, 133, 134, 141, 142, 143, 151, 152, 153 and 154, MWAB-nodes 110, 120a, 120b, 130, 140 and 150 allow overcoming the reachability issue resulting from limited sky visibility while ensuring support for onboard / on-site mobile edge computing (MEC), local services, and direct local inter-UE communications. This allows further communication between base stations 102, 103 and 104 and the UEs 111, 112, 113, 121, 122, 123, 131, 132, 133, 134, 141, 142, 143, 151, 152, 153 and 154 and / or communications between the UEs served by a same MWAB-node (e.g., UEs 151, 152, 153 and 154 connected to MW AB node 150). The base stations 102, 103 and 104, the MWAB nodes 110, 120a, 120b, 130, 140 and 150, the satellite 160, the satellite dish 101 are thus forming a backhaul network or WAB network (also referred to as WAB topology), or MWAB network (also referred to as MWAB topology), which accommodates UEs 111, 112, 113, 121, 122, 123, 131, 132, 133, 134, 141, 142, 143, 151, 152, 153 and 154. The terms WAB network, MWAB network, WAB topology and MWAB topology will be used interchangeably in the following. The WAB network forms the Radio Access Network (RAN) or as referred to with respect to 5G, Next Generation (NG) RAN. The WAB network forms the Radio Access Network (RAN) or as referred to with respect to 5G, the Next Generation (NG) RAN. The base stations 102, 103 and 104, the MWAB nodes 110, 120a, 120b, 130, 140 and 150, the satellite 160, the satellite dish 101, and the core network 170 are thus forming a WAB system, or MWAB system, which accommodates UEs 111, 112, 113, 121, 122, 123, 131, 132, 133, 134, 141, 142, 143,151, 152,153 and 154. The terms WAB system and MWAB system will be used interchangeably in the following. A base station, or gNB, such as base station 102, 103 or 104, is a logical node that provides the NR-connectivity, hosting both higher layer protocols, such as PDCP (Packet Data Convergence Protocol) and RRC (Radio Resource Control) protocols, and lower layer protocols, such as the RLC, MAC and physical layer protocols. The MWAB nodes 110, 120a, 120b, 130, 140 and 150, which may serve multiple radio sectors, are wireless backhauled to the base station 102, 103 or 104, via a single logical hop associated to a single radio link (i.e., radio links D104 la. D1041b, D1031, D1022, DI021), or split into two radio links in the case of satellite relaying (radio links D1601a and D1601b). Although a single logical hop is shown in figure 1, it will be appreciated that the MWAB nodes could be wireless backhauled to the base station over multiple logical hops (for example, similar to the multiple hops provided in an IAB network). Each MWAB node consists of a MWAB-gNB, or also referred to as a MWAB base station, and an WAB-MT, or MWAB-Mobile Termination. The MWAB-gNB functionality on an MWAB-node allows or enables the connection to a UE. The MWAB-MT functionality includes, e.g., physical layer, layer-2, RRC and Non Access Stratum (NAS) functionalities and allows or enables connection to a fixed base station, orgNB, such as base station 102, 103 or 104. MWAB nodes 110, 120a, 120b, 140 and 150 are intended to be mobile devices that will move along with the vehicle they are mounted on. However, these MWAB nodes may remain at a fixed location for a significant duration when their associated vehicle is remaining still (e.g., a train may stop at a railway station, a plane may be parked at an airport for a while, a car / truck / fire engine, or similar appropriate vehicle may be parked, for example nearby a disaster area). MWAB node 130 is likely to remain at fixed location and may be a 5G Femto node, which provides NR access at home or at enterprise premises. In such case, the 5G Femto node 130 may have a direct connection DI700 to the Core Network 170 through the wired link infrastructure 190, which is preferably based on optical fiber or any other wired means. Figure 2 is a simplified schematic diagram of a 5G system 200 in which the present invention may be implemented according to one or more embodiments. This figure illustrates the possible standardized interfaces between the various elements composing the system. First, it represents a User Equipment (UE) 201 having a Uu interface with the New Generation (NG) Radio Access Network (RAN or NG-RAN) 202, and a N1 interface with an Access and Mobility management Function (AMF) entity or AMF 212 in a 5G core network (5GC) 210. Each base station composing the RAN 202 has a N2 interface with one or more Access and Mobility management Function (AMF) entity or AMF, like AMF 212, and a N3 interface with one or more User Plane Function (UPF) entity or UPF, like UPF 211. The N1 interface is used to convey Non-Access Stratum (NAS) protocol messages between a UE 201 and an AMF 212. NAS messages are used for the signaling between the UE and the core network for various procedures such as registration, session establishment, security, and mobility management. Actually, NAS messages are conveyed through the Uu interface between the UE 201 and the RAN 202, and the N2 interface between the RAN 202 and the AMF 212. An AMF 212 is responsible for handling registration, authentication, connection and mobility management tasks for a UE. There may be several AMFs in a 5G core network, a standardized interface N14 enables the communications between AMFs. When a UE registers to the network through a serving base station, the serving base station will connect to an AMF suitable to handle the UE. When the UE 201 is registered, one or more Protocol Data Unit (PDU) session(s) can be set up to transfer data flows between the UE 201 and the Data Network (DN) 220 providing internet access. A PDU session is established between a UE 201 and a User Plane Function (UPF) 211 in the 5G core network 210. In the user plane, the UPF 211 connects to the Data Network (DN) 220 through the interface N6, and it is responsible for data packets routing with the required Quality of Service (QoS). There may be several UPFs on the data path with a N9 interface between UPFs. The user data between a UE 201and tire Data Network 220 are thus conveyed through interfaces Uu, N3, N6 and potentially N9. In the control plane, the setup of PDU sessions is handled through NAS messages involving the Session Management Function (SMF) entity or SMF 213 in the 5G core network 210. The NAS messages are still exchanged between the UE 201 and the AMF 212 through the N1 interface, but an additional interface Nil between an AMF 212 and the SMF 213 is used to reach the SMF 213. In a 5G core network, the SMF is responsible for the setup, modification, and release of PDU sessions for a UE, as well as the Internet Protocol (IP) address allocation for the UE. To manage a PDU session, the SMF 213 controls the UPF 211 (configuration) based on QoS policy defined for the PDU session. For this purpose, a N4 interface exists between the SMF 213 and the UPF 211. A base station in RAN 202 operating in a first Public Land Mobile Network (PLMN) may serve a UE having a subscription for a second PLMN (called home PLMN) different from the first PLMN (called visited PLMN). hi such a roaming case, there are two options to provide the UE 201 with an access to the Data Network 220. In a first option called home routed, the UPF and its controlling SMF to access the Data Network 220 are located in the 5G core network for the home PLMN. However, the SMF of the visited PLMN controls the intermediate UPF(s) of the visited PLMN, and interacts with the SMF of the home PLMN. In a second option called local breakout, the UPF and its controlling SMF to access the Data Network 220 are located in the 5G core network for the visited PLMN. However, the SMF interacts with the home 5G core network to get QoS policies associated with the UE’s PDU session(s). Figure 3 is a simplified schematic diagram of a 5G system 300 involving a Mobile Wireless Access Backhaul (MWAB) node, and in which the present invention may be implemented according to one or more embodiments. This figure first represents a User Equipment (UE) 301 served by a MWAB node 310 through the Uu interface. The MWAB node 310 is composed of or includes a MWAB-MT unit 311 (also called MWAB-UE), and a MWAB-gNB unit 312. Through the MWAB-gNB 312, a MWAB node acts as a gNB for UEs providing access to the 5G network, i.e., providing a NR access link to the UEs that can be located inside or outside the entity, such as a vehicle, equipped with the MWAB node 310 (e.g. on entering / leaving the vehicle). In other words, the MWAB-gNB 312 includes full base station or gNB function (including both Central Unit (CU) and distributed unit (DU)) and MT function, where the gNB function is used to communicate with UEs for access service and the MT function is used to communicate with another gNB for backhauling purposes. The MWAB node 310 wirelessly connects to the 5G Core Network (using NR Uu interface) through an IP connectivity provided by PDU session(s) established by the MWAB-MT 311 via a gNB 320, which can be called a backhaul base station, backhaul gNB or BH gNB. Acting as a legacy UE, the MWAB-MT 311 connects via a NG-RAN cell of the BH gNB 320, through a backhaul link that may be a direct link or via a satellite (e.g., when the MWAB node 310 is embedded in an airplane). Thus, a PDU session is provided either by a Terrestrial Network (TN) or by a N on-Terrestrial Network (NTN). In addition, the MWAB node 310 may embed some core network functions, like a UPF 313, to enable local services to the served UEs 301. The traffic associated to these local services does not need to use the links to / from the core network via the BH gNB 320, which has the advantages to reduce the load on these links and to run applications having very low latency requirements. For example, where the MWAB node 310 includes a UPF 313, the MWAB node can connect to one or more local servers (e.g. mounted at the same entity as the MWAB 310, e.g. the same vehicle as the MWAB node) enabling a UE served by the MWAB access to local services provided by the local servers with no traffic required outside of the MWAB node / server environment. The BH gNB 320 provides N3 and N2 interfaces so that the MWAB-MT 311 can access to the functions of its 5G core network 330. Indeed, a MWAB-MT 311 may have access to some or several PLMNs through the appropriate subscriptions, and it may connect in a non-roaming manner to one PLMN, e.g., PLMN1 supported by the BH gNB 320, and may then have access to the corresponding 5G core network 330. In particular the MWAB-MT 311 interacts with the AMF 332, which can be called the MWAB AMF, and establishes PDU session(s) with the UPF 331, which can be called the MWAB UPF. The MWAB UPF 331 is controlled by the SMF 333 (through N4 interface), which can be called the MWAB SMF, and which also interacts with the MWAB AMF 332 (through N4 interface). There may be one or several intermediate UPFs between the BH gNB 320 and the MWAB UPF 331 as mentioned in the Figure 2. An interface internal to the MWAB node 310 exists between the MWAB-gNB 312 and the MWAB-MT 311, which may be implemented on different or the same hardware resources. For instance, these two functions arc implemented on tire same processing unit 402 of Figure 4, and interactions exist between the two functions. Once the MWAB-MT 311 has established a PDU session with the MWAB UPF 331, the MWAB node is ready to serve UEs and the MWAB-gNB 312 can start operating as a legacy gNB. The MWAB-gNB may support various PLMNs and the UE 301 connects to one PLMN, e.g., PLMN2, which may be different from the PLMN that the MWAB-MT 311 connects to, e.g. PLMN1. In the case where PLMN 1 and PLMN2 are different, the UE 301 connects to the 5G core network 340, including a UPF 341, which can be called the UE UPF, an AMF 342, which can be called the UE AMF, and a SMF 343, which can be called the UE SMF. The UE SMF 343 interacts with the UE AMF 342 (through Nil interface) and the UE UPF 341 (through N4 interface). In the case where the PLMN 1 and the PLMN2 are the same, the UE UPF 341, the UE AMF 342, the UE SMF 343, the MWAB UPF 331, the MWAB AMF 332, and the MWAB SMF 333 belong to the same 5G core network 350. In addition, the UE UPF 341 and the MWAB UPF 331 may be the same UPF, the UE AMF 342 and the MWAB AMF 332 may be the same AMF, the UE SMF 343 and the MWAB SMF 333 may be the same SMF. The connections between the UE 301 to the UE UPF 341 and to the UE AMF 342 are possible thanks to the N6 interface between the UE UPF 341 and the MWAB UPF 331, and thanks to the N6 interface between the MWAB UPF 331 and the UE AMF 342. These N6 interfaces enable the establishment of N2 interface between the MWAB-gNB 312 and the UE AMF 342, and the establishment of N3 interface between the MWAB-gNB 312 and the UE UPF 341, which allows the UE 301 to access the Data Network 360. In case the MWAB-MT 311 connects to the 5G network in a roaming manner corresponding to the home routed option, then the PLMN1 is the visited PLMN and the MWAB UPF 331 connects to another UPF not represented in the Figure 3 in the home PLMN through a N9 interface. It is this other UPF that provides the connection to the UE UPF 341 and the UE AMF 342 through N6 interfaces. In case the MWAB-MT 311 connects to the 5G network in a roaming manner corresponding to the local breakout option, then the PLMN1 is the visited PLMN and the MWAB UPF 331 directly connects to the UE UPF 341 and the UE AMF 342 through N6 interfaces as shown in the Figure 3. Figure 4 is a block schematic diagram of an example network node or base station 400, such as base stations or gNBs or MWAB nodes shown in Figure I or WAB nodes, in accordance with one or more embodiments of the invention. Each of a MWAB node IIO, 120a, 120b, 130, 140, or 150 of figure 1 may comprise the elements of the base station of figure 3. In the following description, the network node 400 will be referred to generally as a base station. As will be apparent to a skilled person, Figure 4 is a simplified schematic diagram and shows only some of the functional components of an example base station 400 for use in describing the one or more embodiments of the invention. The base station 400 includes components for transmitting and receiving communications. As shown in Figure 4, the base station 400 includes a processing unit 402, a wireless interface 404, one or more antennas 410, a network interface 432, and memory 418. The network interface 432 manages communications of the base station 400 with the core network, other base stations, local network functions (like UPF), or local servers. It may provide a standardized interface, wired (e.g. fiber) or wireless, to support these communications. Through this network interface 432, the base station 400 may implement the standardized interfaces N2 (based on NGAP protocol) and N3 (based on GPRS tunneling protocol) with the core network, and the standardized interface Xn (based on XbnAP protocol) with other base station of the Radio Access Network (RAN), all defined by the 3GPP standard. The network interface 432 may not be present or active in case the base station 400 is a MWAB node that does not support local services, that is not used as a legacy base station like base station 102, 104 in Figure 1, and that is not used as a home base station providing Femto cells like base station 130 in Figure 1. The wireless interface 404 is configured to provide wireless communication via communication links (414) with other wireless devices, such as one or more UEs, e.g. link 1041b between base station 104 and the MT / UE unit of MWAB node 120b, or link 1202 between the gNB unit of MWAB node 120b and the UE 122. In case of MWAB node, the wireless interface 410 may then be used both for tire wireless backhaul link(s) with backhaul base station(s) and for the wireless link(s) with the UE(s) served by the MWAB node. The wireless interface 404 may be compliant with a fifth-generation (5G) New Radio (NR) system and thus implementing the Uu interface defined by 3GPP standard, or with other wireless communication system. The wireless interface 404 is coupled to the processing unit 402 and typically includes one or more antennas (such as the antenna 410), a receiving unit 406 and a transmitting unit 408. The configuration of the wireless interface 404 may be limited to connect to one antenna, but preferably several antennas are used, in order to provide beamforming capability. Although not shown in Figure 4, the receiving unit 406 typically includes elements such as a receiver, demodulator, decoder, and the transmitting unit 408 typically includes elements such as a transmitter, modulator, coder. The receiving unit 406 and transmitting unit 408 may together be referred to as a transceiver. The processing unit 402 is configured to carrying out processing for operation of the base station 400. The processing unit 402 may be a single processor (e.g. Central Processing Unit) or may comprise two or more processors. The number of processors and the allocation of processing functions to the processors is a matter of design choice for a skilled person. The base station 400 includes memory 418 for storing data and computer programs containing instructions for the operation of the base station 400. Memory 418 includes RAM (Random Access Memory ), ROM (Read Only Memory), or combination of both or as a non-limiting example a mass storage device such as a disk or a Solid-State Drive. Memory 418 includes a program memory in which are stored programs containing processor instructions for operation of the base station 400 and for implementing the methods in accordance with one or more embodiments of the invention. The programs may contain a number of different program elements or sub-routines containing processor instructions for a variety-- of different tasks, for example, for: establishing, controlling and releasing communications with the UEs (e.g. implementing the Uu interface); processing data and signalling received at the receiving unit 406; processing signalling (e.g., paging messages, System Information Blocks) and data for transmission by the transmitting unit 408. Memory 418 may further include memory- (e.g. RAM) for storing information. For example, information stored in memory 418 may further include information associated with the mobile WAB node, such as information elements 420 related to a MW AB node, including MWAB information. The infonnation elements may be static information elements and / or dynamic information elements. The information elements 420 may be associated to the base station 400 (when the base station is a MWAB node), and may be communicated to any network node or entity when necessary. The information elements may also be related to a MWAB node (which is not the base station 400), and stored after reception from the MWAB node or from another network node or entity. Other nodes or entities described, such as the gNB, AMF and UPF, may comprise information elements stored in their own respective memories. These information elements being related to a MWAB node (including MWAB information) or their capability to serve a MWAB node. Specific program elements / sub-routines stored in program memory may include one or more of the following: elements for sending a request for a backhaul RAN node (or gNB, AMF or UPF) to serve a mobile WAB node, the request including information associated with the mobile WAB node, elements for receiving a request for serving a mobile WAB node and for receiving information associated with the mobile WAB node, an element for accepting or rejecting the request for serving the mobile WAB node based on the received information, an element for receiving a request to provide information related to the mobile WAB node, an element for sending a response to the request to provide information, the response including information associated with the mobile WAB node (see, for example, the methods described below with reference to figures 6-9). In an example arrangement, a communication bus 424 provides communication and interoperability between the various elements included in the base station 400 or connected to it. The representation of the bus is not limiting and in particular, the processing unit 402 is operable to communicate instructions to any element of the base station 400 directly or by means of another element of the base station 400. In an example implementation, the base station 400 may be or may include an apparatus comprising one or more processing units or processors for performing or implementing the methods in accordance with one or more embodiments of the invention. In other words, the apparatus may be capable of performing one or more functions of the base station including performing the methods in accordance with one or more embodiments of the invention by means of the one or more processing units. For example, the one or more processing units uses software to implement the one or more embodiments of the invention as described above with reference to the processing unit 402 of Figure 4. Instructions may be executed by one or more processors, such as one or more digital signal processors (DSPs), general purpose microprocessors, a CPU of a microcontroller Unit (MCU), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), or other equivalent integrated (e.g. on an Integrated Circuit) or discrete logic circuitry. However, alternatively, the one or more processing units for performing or implementing the methods may be implemented in hardware: for example, in the form of an Application Specific Integrated Circuit or ASIC or other hardware comprising logic element (s). Accordingly, the term “processing unit” as used herein may refer to any of the foregoing structure or any other structure suitable for implementation of the techniques described herein. Figure 5 illustrates an example of a wireless communication system 500, including a WAB network or WAB network system, according to some embodiments. Tire WAB network or WAB network system may be considered a mobile WAB network or a mobile WAB network system. A WAB network will also be referred to as a WAB network system, WAB topology, WAB system, topology or system and so in this application, the terms WAB network system, WAB network, WAB topology, WAB system, topology or system will be used interchangeably. The WAB network system of Figure 5, is composed of or comprises three base stations 501, 502 and 503, also referred to as Backhaul base stations, or backhaul gNBs (also referred to as BH-gNB), two core networks 510 and 520, with the respective AMF entities 511a and 511b (for Core Network 510) and 521a and 521b (for Core Network 520) and the respective UPF entities 512a and 512b (for Core Network 510) and 522a and 522b (for Core Network 520), and two MWAB nodes 530 and 540. A wired backhaul IP network 590 interconnects the base stations 501, 502 and 503 and the Core Networks 510 and 520. For instance, this wired link consists of optical fiber cable(s). As discussed above, each MWAB node comprises a Mobile Termination (MT) part or unit or component (MWAB-MT 531 for MWAB node 530 and MWAB-MT 541 for MWAB node 540) and a base station part or unit or component (MWAB-gNB 532 for MWAB node 530 and MWAB-MT 542 for MWAB node 540). MWAB node 530 and MWAB node 540 may also embed a UPF entity, respectively UPF entity 533 and UPF 543, as previously discussed in relation to figure 3, allowing MWAB-node 530 to provide UEs 551, 552 and 561 with at least some local services, such as for instance inter-UE communication where the user data exchanged between the two UEs would be routed through UPF entity 533 instead of being routed through a UPF entity belonging to Core Network 510 or 520. In some embodiments, the UPF entity of the MWAB node may be configured for one or more local services. MWAB node 530 is connected to the serving backhaul base station BH-BS1, also referred to as BH-gNBl, 501 through BH link 5011. MWAB node 540 may be connected to the serving backhaul base station BH-BS2, also referred to as BH-gNB2, 502 through BH link 5021 or to the serving backhaul base station BH-BS3, also referred to as BH-gNB3, 503 through BH link 5031 or, m case of dual connectivity-, to both the serving backhaul base station BH-BS2, also referred to as BH-gNB2, 502 through BH link 5021 and the serving backhaul base station BH-BS3, also referred to as BH-gNB3, 503 through BH link 5031. MWAB-gNB 532 of MWAB node 530 is also connected to UE 551 through communication link or radio link 5301 and to UE 552 through communication link or radio link 5302. Similarly, MWAB-gNB 542 of MWAB node 540 is also connected to UE 561 through communication link or radio link 5401. Although Figure 5 shows only one UE 561 connected to MWAB node 540, it will be appreciated that there may be a plurality of UEs connected to MWAB nodes of the wireless communication system. Similarly, Figure 5 shows a plurality of UEs 551, 552, connected to MWAB node 530 but it will be appreciated that there may be one UE connected. MWAB-gNB 532 and MWAB-MT 531 may be connected to a same AMF function or entity7 (e.g., AMF 51 la) or to different AMF functions or entities belonging to the same Core Network (e.g., AMF 511a and AMF 51 lb) or to different Core Networks (e.g., AMF 51 la and AMF 521a). Some AMF functions may be implementing MWAB-specific features for managing a MWAB node (e.g., advanced mobility features). Some AMF functions may not implement such features but may still be capable of serving a MWAB node with a limited set of basic features. Some AMF functions may not be capable of serving a MWAB node. The processes for managing one or more network connections in a wireless communication system including one or more mobile WAB (MWAB) nodes will now be described according to some embodiments of the present invention. Figure 10 is a flowchart of an example method 1000 for managing a Wireless Access Backhaul, WAB, node connectivity according to one or more embodiments. The method 1000 of Figure 10 is performed at the mobile Wireless Access Backhaul, MWAB, node. For example, with reference to the wireless communication system shown in and described with respect to Figure 5, the MWAB node performing the method 1000 may be the MWA-node 530, which comprises MWAB-MT 531 and MWAB-gNB 532, of WAB system 500. The method 1000 as shown in and described with respect to Figure 10 may be performed by software elements and / or hardware elements. The MWAB node may be implemented in a communication device 400 as shown in and described with reference to Figure 4 with the method as shown in and described with respect to Figure 10 being performed by one or more processing units, such as the processing unit 402. Briefly, in a first step 1001, the Mobile Termination (MT) part of the MWAB node establishes connection set up with a fixed Backhaul Base Station such as backhaul gNB 501, and a Core Network entity7, such as AMF 51 la of Core Network 510. To do so, the MWAB-MT may send to the backhaul gNB 501 a BACKHAUL INFORMATION message, as discussed in figure 6, where BACKHAUL INFORMATION message 601 may include some MWAB information related to the capability of the MWAB node sending the message, i.e. the MWAB node that the MWAB-MT belongs to. The BACKHAUL INFORMATION message, may be any message capable of having information incorporated therein, for example the RCC SETUP COMPLETE message. Preferably the BACKHAUL INFORMATION MESSAGE may be any message(s) defined in the 3GPP standards and / or 5G NR standards which is capable of having MWAB information incorporated therein or having other information which may be associated with MWAB information incorporated therein. The message(s) discussed in relation to embodiment(s) described herein are preferable messages. More details of the MWAB information included in the BACKHAUL INFORMATION message 601 sent by the MWAB-MT is given hereafter in relation to Figure 11. The MWAB information may be further forwarded by the backhaul gNB 501 to the AMF 511a, as further discussed in figure 6. In a second step 1002, the MWAB node, preferably the MWAB-MT, may receive from the fixed base station and / or from the Core Network some information on whether the connection is accepted or rejected. This information may be received in CONNECTION CONFIRMATION message 604, as shown in Figure 6 and discussed herein. Figure 11 is a flowchart of an example method performed at a wireless communication device in accordance with one or more embodiments. The method 1100 of Figure 11 is performed at the mobile Wireless Access Backhaul, MWAB, node. For example, with reference to the wireless communication system shown in and described with respect to Figure 5, the MWAB node performing the method 1100 may be the MWA-node 530, which comprises MWAB-MT 531 and MWAB-gNB 532, of WAB system 500. The method 1100 as shown in and described with respect to Figure 11 may be performed by software elements and / or hardware elements. The MWAB node may be implemented in a communication device 400 as shown in and described with reference to Figure 4 with the method as shown in and described with respect to Figure 10 being performed by one or more processing units, such as the processing unit 402. Briefly, in a first step 1101, a MWAB node shares with a wireless access backhaul system entity some MWAB information related to the capability of the MWAB node that shares the information, e.g. the capability of MWAB node that the MWAB-MT belongs to. In some embodiments, the MWAB information may be shared by the Mobile Termination (MT), or MWAB-MT, part of the MWAB node. The MWAB information may be shared from the MWAB-MT with an entity in the core network and / or a BH node, and / or the MWAB-gNB part. In some embodiments, the MWAB information may be shared by the MWAB base station, or MWAB-gNB, part of the MWAB node. The MWAB information may be shared from the MWAB-gNB entity with an entity in the core network and / or a BH entity, and / or the MWAB-MT part. In some embodiments, the MWAB node may share MWAB information with a backhaul base station, or backhaul gNB or BH gNB, such as backhaul base station 501. In some embodiments, the MWAB-MT may share MWAB information with an AMF entity, or other entity, in the Core Network, such as AMF 511a. The MWAB information includes at least one of: MWAB node capability information and MWAB node status information. The MWAB node capability information may indicate one or more capabilities supported by the MWAB node and may also indicate MWAB-gNB capability information. The MWAB-gNB capability information indicates one or more capabilities supported by the MWAB-gNB included in the MWAB node. Put another way, information associated with one or more capabilities supported by the mobile WAB node. In one example, the MWAB node capability information includes at least one of: a MWAB indication information, which indicates that the Mobile Termination (MT) unit or the MWAB-gNB which has sent the MWAB information belongs to a Mobile Wireless Access Backhaul Device / Node. That is to say, an indication that the information sent is associated with a mobile WAB node. MWAB local services support information, which indicates that the MWAB node supports local services and / or which local services are actually supported. Put another way information indicating local services of the mobile WAB node. MWAB co-location information, which allows identifying the MWAB-gNB and / or the Mobile Termination (MT) unit of the MWAB node. That is to say information for indicating that the base station of the mobile WAB node and the mobile termination of the WAB node are disposed to the same mobile WAB node. Put another way, information for indicating that the mobile WAB node comprises both the base station and mobile termination. Femto Capability, which indicates if the WAB node can be configured and behave as a Femto node. Put another way information indicating whether the WAB node is configured to operate as a Femto node. Mobility capability information, which indicates if the WAB node can be a mobile WAB, MWAB, node. Put another way, information related to the mobility of the WAB node, preferably information indicating whether the WAB node is configurable to operate while moving. Mobility Profile information, which indicates the mobility capability of the MWAB node. The mobility profile information may also be considered to be information related to the mobility of the WAB node. The Mobility Profile information may include at least one of: speed information indicating a speed capability of the MWAB node (e.g., min., average or max speed); mobility range information indicating a mobility area or mobility area type of the MWAB node; itinerary information, which may indicate a sequence of mobility and static periods, for an itinerary the MWAB node may follow. Information indicating the levels of quality of service. QoS capability information, which indicates levels of Quality of Service (QoS) the MWAB-gNB, or the MWAB node more generally, is able to manage when serving UEs. Information indicating the load capability of the mobile WAB node. The information indicating the load capability of the mobile WAB node may comprise MWAB-gNB capability information. The information indicating the load capability may include at least one of a Load capability information, which provides information on the load the MWAB-gNB, or the MWAB node more generally, may handle when serving UEs. The MWAB node status information may indicate the current operating status of the MWAB node. The MWAB node status information may include the operating status of the MWAB-gNB capability information, which may indicate one or more capabilities supported by the MWAB-gNB included in the MWAB node. In one example, the MWAB node status information includes at least one of: a Mobility status information, which indicates whether the MWAB node is currently moving or is remaining at a fixed location, e.g., a static location. Put another way, information related to the mobility of the WAB node. a Femto status information, which indicates if the MWAB node has been configured to operate as a 5G Femto node, having therefore a direct wired connection to the Core Network. Put another way, the information indicating whether the mobile WAB node is configured to operate as a Femto node. The method 1100 of Figure 11 may also be performed at the backhaul base station, or backhaul gNB. For example, with reference to the wireless communication system shown in and described with respect to Figure 5, and in relation with figure 8, the backhaul base station performing the method 1100 may be the backhaul base station 501. In such cases, in step 1101, the backhaul base station may share with a wireless access backhaul system entity, such as an AMF, or a MWAB node or other node in its vicinity, some MW AB information. This allows the system entity or other MWAB node or other node to be aware of other MWAB nodes, i.e., be aware of the presence of other nodes. The MWAB information may be related to the capability of the base station part of a mobile wireless access backhaul node (MWAB-gNB). More generally, the backhaul base station, such as 501, may share the MWAB information related to a MWAB node, such as 530. Put another way a wireless access backhaul (WAB) system entity, such as the backhaul base station (BH gNB), may share MWAB information with is an AMF entity of the Core Network such as AMF 51 la, or a MWAB node in its vicinity or other node in its vicinity. When sharing the MWAB information with a MWAB node or other node in its vicinity, the backhaul base station may broadcast the MWAB information. That is to say that the backhaul base station may broadcast the information related to the MWAB node to another entity or node. In some embodiments, the MWAB information shared by the backhaul base station may include at least a MWAB support indication information, which indicates that the backhaul base station is capable of serving a Mobile Wireless Access Backhaul (MWAB) node. That is to say, that MWAB support indication information may in some cases be considered MWAB information as it is associated with whether the backhaul base station supports mobile WAB nodes. Figure 12 is a flowchart of an example method performed at a wireless communication device in accordance with one or more embodiments. The method 1200 of Figure 12 is performed at tire mobile Wireless Access Backhaul (MWAB) node. For example, with reference to the wireless communication system shown in and described with respect to Figure 5, the MWAB node performing the method 1200 may be the MWAB node 530, which comprises MWAB-MT 531 and MWAB-gNB 532, of WAB system 500. The MWAB-gNB may be served by a Core Network entity, such as an AMF 51 la of WAB system 500. The method 1200 as shown in and described with respect to Figure 12 may be performed by software elements and / or hardware elements. The MWAB node may be implemented in a communication device 400 as shown in and described with reference to Figure 4 with the method as shown in and described with respect to Figure 12 being performed by one or more processing units, such as the processing unit 402. Briefly, in a first step 1201, a MWAB node receives from the AMF Core Network entity an authorization to broadcast MWAB information to the surrounding MWAB nodes in the vicinity through a BACKHAUL INDICATION AUTHORIZATION message 902, as shown in Figure 9 and discussed herein. In a second step 1202, the MWAB-gNB of the MWAB node broadcasts a BACKHAUL INFORMATION message 901, as shown in Figure 9 and discussed herein, to the surrounding MWAB nodes in the vicinity. The BACKHAUL INFORMAHON message 901 may include at least one or some of the MWAB information, particularly but not exclusively the MWAB information related to the capability of the MWAB node making the broadcast.. The MWAB information sent in message 901 may include at least one of: a MWAB indication information, which indicates that the base station that sends the MWAB capability information is a MWAB-gNB that belongs to a MWAB node; MWAB local services support information, which indicates that tire MWAB node supports local services and / or which local services are actually supported; MWAB node capability information, which indicates one or more capabilities supported by the MWAB node; and MWAB-gNB capability infonnation, which indicates one or more capabilities supported by the MWAB-gNB included in the MWAB node. The MWAB information in message 901 may include other information as discussed above. The MWAB node capability information, if included in the message 901, may include at least one of: a Mobility status information, which indicates whether the MWAB node is currently moving or is remaining at a fixed location; a Femto status information, which indicates if the MWAB node has been configured to operate as a 5G Femto node, having therefore a direct wired connection to the Core Network; a Mobility Profile information, which indicates the mobility capability of the MWAB node. In an example, the Mobility Profile infonnation includes at least one of: speed information indicating a speed capability of the MWAB node (e.g., min., average or max speed); mobility range information indicating a mobility area or mobility area type of the MWAB node; and itinerary information, which may indicate a sequence of mobility and static periods, for an itinerary the MWAB node may follow. Hie MWAB node capability information may include other information as discussed above. The MWAB-gNB capability information, if included in message 901, may include at least one of: a Load capability information, which provides infonnation on the load the MWAB-gNB may handle when serving UEs; and QoS capability information, which indicates levels of Quality of Service (QoS) the MWAB-gNB is able to manage when serving UEs. Referring to Figure 6, a schematic and simplified diagram illustrating an example message flow for use in managing network connectivity in a wireless communication system including at least one Wireless Access Backhaul (WAB) node in accordance with one or more embodiments and which may be used for managing the advertising by a WAB node of its mobility capability and status is shown. A mobile Wireless Access Backhaul (MWAB) node 630 (which may correspond to MWAB node 120a of Figure 1 and MWAB node 530 of Figure 5 as described above, or correspond to other descriptions of MWAB nodes discussed herein) may share MWAB capability’ information with its serving backhaul base station, or backhaul gNB 610 (which may correspond to base station 104 of Figure 1 and backhaul base station 501 of Figure 5 as described above, or correspond to other descriptions of backhaul base stations discussed herein) by sending MWAB information through a BACKHAUL INFORMATION message 601. In one embodiment the BACKHAUL INFORMATION message 601 may be sent by the MWAB-MT 631 of MW AB node 630. In other embodiments, the BACKHAUL INFORMATION message 601 may be sent by the MWAB-gNB 632. In some embodiments, the sharing of the MW AB infonnation is performed upon or as part of MW AB node RRC setup. In one example, the MWAB information sharing may be performed upon RRC connection establishment, in such cases, the BACKHAUL INFORMATION message 601 is the RRCSetupRequest message used to initiate the RRC connection establishment process, as specified in 3GPP TS 38.331. In another example, the BACKHAUL INFORMATION message 601 is the RRCSetupComplete message used to complete the RRC connection establishment process, as specified in 3GPP TS 38.331. In some embodiments, the MWAB information may be embedded in a field of the message. For example, the MWAB information may be embedded in a dedicatedNAS-Message field within the RRCSetupComplete message, as defined in 3GPP TS 38.331 and 3GPP TS 23.502. In some embodiments, the MWAB information may be embedded in a NAS Registration Request message within the dedicatedNAS-Message field, as defined in 3GPP TS 38.331 and 3GPP TS 23.502. The MWAB information contained in the BACKHAUL INFORMATION message sent from the MWAB node 630 to the BH gNB 610 is forwarded to an AMF 620 in the core network through a further BACKHAUL MESSAGE 602, the AMF 620 storing the received MWAB information. For example, the dedicatedNAS-Message field infonnation embedding the MWAB information is further forwarded by the backhaul base station 610 through BACKHAUL INFORMATION message 602 to the AMF 620, which will then store this MWAB information. The backhaul gNB may, in some embodiments, also store the MWAB information upon reception of the BACKHAUL INFORMATION message 601. The MWAB information may, in some embodiments, include at least one of: MWAB node capability information and MWAB node status information. The MWAB node capability information may, in some embodiments, include at least one of: - Mobile Wireless Access Backhaul indication, orMWAB indication, information. This information indicates that the node is a MWAB node. In the embodiment shown in figure 6, this information indicates that the Mobile Termination (MT) unit 631 belongs to a Mobile Wireless Access Backhaul (MWAB) node / device; - Mobile Wireless Access Backhaul local services support, or MWAB local services support, information. This information indicates that Mobile Wireless Access Backhaul node, which the Mobile Termination (MT) unit 631 belongs to, supports local services and / or which local services are supported. That is to say that the MWAB node / device supports local services and / or which local services are supported. In some embodiments, this information may indicate the capability of the MWAB node 630 to perform Mobile Edge Computing (MEC) along with associated computing capacity information. In some embodiments, this information may indicate whether the MWAB node 630 comprises a UPF entity, i.e., an embedded UPF entity, such as UPF entity 533 of figure 5, for instance for the purpose of direct local inter-UE communications (e.g., direct communication of UEs 551 and 552 via UPF entity 533). - Mobile Wireless Access Backhaul co-localion. or MWAB co-location, information. This information allows identifying the MWAB-gNB 632 that is co-located, or disposed, to the same Mobile Wireless Access Backhaul node 630 as the Mobile Termination (MT) unit 631. That is to say, that the co-location information may comprise information identifying the existence of the other component of the MWAB node that did not send the information, i.e., the other of the MWAB gNB or the MWAB-MT. For example, it may include an ID for the other of the MWAB gNB or the MWAB-MT. In some embodiments, the MWAB co-location information is the gNB identifier, or gNB ID, as defined in 3GPP TS 38.300. The co-location information may comprise the identifier, or ID, for both the MWAB-gNB and MWAB-MT. The co-location information may comprise information identifying the existence of both components of the MWAB node, i.e., both the MWAB-gNB and the MWAB-MT. - Femto Capability information. This information indicates if the WAB node 630 can be configured and behave as a Femto node 630. - Mobility capability’ information. This information indicates if the WAB node can be a mobile WAB, MWAB, node 630. - Mobility’ Profile information. This information indicates the mobility capability of the MWAB node 630. In some embodiments, the Mobility Profile information includes at least one of: speed information indicating a speed capability of the MWAB node (e.g., min., average or max speed), mobility range information indicating a mobility area (e.g., an area defined by some GPS coordinates or other positioning or area defining systems or schemes) or mobility area type of the MWAB node (e.g., limited area (e.g., below 1 km2), medium area (e.g., between 1 and 10 km2) large area (e.g., greater than 10 km2), put another way an extent of area), itinerary information, which may indicate a sequence of mobility and static periods, for an itinerary tire MWAB node may follow. In some embodiments, the mobility profile information may be determined, for example from determining an average speed of the MWAB node over a given time, or it may be set, for example by inputting necessary details, for example maximum speed of the vehicle to which the MWAB is disposed. In both cases, the information may be updated on a regular basis, but in the determining embodiment this may be done dynamically. - Mobile Wireless Access Backhaul base station capability, or MWAB-gNB capability, information. This information indicates one or more capabilities supported by the MWAB-gNB 632 that is co-located to the same Mobile Wireless Access Backhaul node 630 as the Mobile Termination (MT) unit 631. In some embodiments, the MWAB-gNB capability information may include all or some of the following information: o Load capability information. This information provides information on the load the MWAB-gNB 632 may handle when serving UEs. This information may indicate the maximum number of UEs the MWAB-gNB 632 is capable of serving, and / or a maximum throughput the MWAB-gNB is capable of handling, and / or a maximum computation power, etc. o QoS capability information. Tliis information indicates levels of Quality of Service (QoS) the MWAB-gNB 632 is able to manage when serving UEs. The MWAB node status information may, in some embodiments, include at least one of: - Mobility status information. This information indicates whether the MWAB node 630 is currently moving or is remaining at a fixed location. Tliis information may also include some information on the time period the MWAB node 630 will remain at a fixed location. - Femto status information. This information indicates if the MWAB node 630 has been configured to operate as a 5G Femto node, having therefore a direct wired connection to the Core Network. Based upon the MWAB information received from the MWAB-MT 631, the AMF 620 may decide to accept or reject the connection requested by the MWAB-MT 631 by sending a CONNECTION CONFIRMATION message 603 to the MWAB-MT 631. In some embodiments, the CONNECTION CONFIRMATION message 603 is the Registration Reject message, as defined in 3GPP TS 23.501 and 3GPP TS 23.502. In some embodiments, the CONNECTION CONFIRMATION message 603 may include a Reject Cause indication, which explains the reason why the AMF 620 has decided to reject the connection requested by the MWAB-MT 631. The AMF may decide to reject the MWAB-MT 631 connection request because it does not support MWAB or 5G Femto features, and / or because it cannot support the load indicated by the Load capability information in the MWAB-gNB capability information, and / or because itinerary information in the Mobility Profile information indicates that another AMF which has a more relevant geographical coverage is preferable to serve the MWAB-MT. The rejection based on the Mobility Profile information may be in consideration of the mobility area or mobility area type of the MWAB node. Based upon the MWAB information received from the MWAB-MT 631, the backhaul gNB 610 may decide to accept or reject the connection requested by the MWAB-MT 631 by sending a CONNECTION CONFIRMATION message 604 to the MWAB-MT 631. In some embodiments, the CONNECTION CONFIRMATION message 604 may be the RRCReject message, as defined in 3GPP TS 38.331. In some embodiments, the CONNECTION CONFIRMATION message 604 may be the RRCReconfiguration message, as defined in 3GPP TS 38.331. In some embodiments, the CONNECTION CONFIRMATION message 604 may include a Reject Cause indication, which explains the reason why the backhaul gNB 610 has decided to reject the connection requested by the MWAB-MT 631. The backhaul gNB 610 may decide to reject the MWAB-MT connection request because it does not support MW AB or 5G Femto features, and / or because it cannot support the load indicated by the Load capability information in the MWAB-gNB capability information, and / or because it can only support fixed MWAB nodes. Referring to Figure 7, a schematic and simplified diagram illustrating an example message flow for use in managing network connectivity in a wireless communication system including at least one Wireless Access Backhaul (WAB) node in accordance with one or more embodiments of the invention and which may be used for managing the advertising by a WAB node of its mobility capability and status is shown. The MWAB-gNB unit 732 of a mobile Wireless Access Backhaul (WAB) node 730 (which may correspond to MWAB node 120a of Figure I and MWAB node 530 of Figure 5 as described above, or correspond to other descriptions of MWAB nodes discussed herein) may share MWAB capability information with its serving AMF entity (which may correspond to AMF 511a of Figure 5 as described above, or correspond to other descriptions of AMFs discussed herein). Tire MWAB-gNB node may send MWAB information through a BACKHAUL INFORMATION message 701 to its co-located MWAB-MT entity 731. The MWAB information embedded m BACKHAUL INFORMATION message 701 is forwarded by the MWAB-MT 731 to the AMF entity 720 via UPF entity 740. The whole BACKHAUL INFORMATION message 701 is forwarded by the MWAB-MT 731 through a PDU session previously established with UPF 740, as discussed in figure 2. The UPF entity 740 forwards the BACKHAUL INFORMATION message 702, as BACKHAUL INFORMATION message 703 to the AMF entity 720. In some embodiments, the BACKHAUL INFORMATION message 701 may be a NG SETUP REQUEST message, as specified in 3GPP TS 38.413. The NG SETUP REQUEST message being used to exchange application-level data needed for the MWAB-gNB node and the AMF to correctly interoperate on the NG-Control (NG-C) interface. In other embodiments, other messages specified in 3GPP may be used. The BACKHAUL INFORMATION message 702 may be provided in a PDU session conveying the NG SETUP REQUEST message, as specified in 3GPP TS 38.413. That is to say that the message between the MWAB-MT 731 and the UPF 740 may be a NG SETUP REQUEST message, as specified in 3GPP TS 38.413. In other embodiments, other messages specified in 3GPP may be used. The BACKHAUL INFORMATION message 703 may be a NG SETUP REQUEST message, as specified in 3GPP TS 38.413. That is to say, that the message between UPF 740 and the AMG 720 maybe a NG SETUP REQUEST message, as specified in 3GPP TS 38.413. In other embodiments, other message specified m 3GPP may be used. The AMF entity 720 may store the MWAB information upon reception of the BACKHAUL INFORMATION message 703. In some embodiments, the MWAB information carried in message 701, 702 and 703 includes at least one of: MWAB node capability information and MWAB node status information. The MWAB node capability information may, in some embodiments, include at least one of: - Mobile Wireless Access Backhaul indication, orMWAB indication, information. This information indicates that the node is a MWAB node. In the embodiment shown in figure 7, this information indicates that the MWAB-gNB 732 belongs to a Mobile Wireless Access Backhaul (MWAB) node / Device. - Mobile Wireless Access Backhaul local services support, or MWAB local services support, information. This information indicates that the MWAB node 730, that the MWAB-gNB belongs to, supports local services and / or which local services are actually supported. In some embodiments, this information may indicate the capability of the MWAB node 730 to perform Mobile Edge Computing (MEC) along with associated computing capacity information. in some embodiments, this information may indicate whether the MWAB node 730 comprises a UPF entity, i.e., an embedded UPF entity, such as UPF entity 533 of figure 5, for instance for the purpose of direct local inter-UE communications (e.g., direct communication of UEs 551 and 552 via UPF entity 533). - Mobile Wireless Access Backhaul co-location, or MWAB co-location, information. This information allows identifying the Mobile Termination (MT) unit, MWAB-MT, 731 that is colocated to the same Mobile Wireless Access Backhaul node / device 730 as the MWAB-gNB 732. That is to say, that the co-location information may comprise information identifying the existence of the other component of the MWAB node that did not send the information, i.e. the other of the MWAB gNB or the MWAB-MT. For example, it may include an ID for the other of the MWAB gNB or the MWAB-MT. In some embodiments, the MWAB co-location information is the C-RNTI, as defined in 3GPP TS 38.300. - Femto Capability information. This information indicates if the WAB node 730 can be configured and behave as a Femto node. - Mobility! capability information. This information indicates ifthe WAB node 730 can be a mobile WAB, MW AB. node. - Mobility Profile information. This information indicates the mobility capability of the MWAB node 730. In some embodiments, the Mobility Profile information includes at least one of: speed information indicating a speed capability of the MWAB node (e.g., min., average or max speed), mobility range information indicating a mobility area (e.g., an area defined by some GPS coordinates or other positioning or area defining systems or schemes) or mobility area type of the MWAB node (e.g., limited area (e.g., below 1 km2), medium area (e.g., between 1 and 10 km2) large area (e.g., greater than 10 km2), put another way an extent of area), itinerary' information, which may indicate a sequence of mobility and static periods, for an itinerary-’ the MWAB node may follow. In some embodiments, the mobility profile information may be determined, for example from determining an average speed of the MWAB node over a given time, or it may be set, for example by inputting necessary details, for example maximum speed of the vehicle to yvhich the MWAB is disposed. In both cases, the information may be updated on a regular basis, but in the determining embodiment this may be done dynamically. - Mobile Wireless Access Backhaul base station capability, or MWAB-gNB capability, information. This information indicates one or more capabilities supported by the MWAB-gNB 732. In some embodiments, the MWAB-gNB capability information may include all or some of the following information: o Load capability information. Uris information provides information on the load the MWAB-gNB 732 may handle when serving UEs. This information may indicate the maximum number of UEs the MWAB-gNB 732 is capable of serving, and / or a maximum throughput the MWAB-gNB is capable of handling, and / or a maximum computation power, etc. o QoS capability’ information. This information indicates levels of Quality of Service (QoS) the MWAB-gNB 732 is able to manage when serving UEs. The MWAB node status information may, in some embodiments, include at least one of: - Mobility’ status information. This information indicates whetherthe MWAB node 730 is currently moving or is remaining at a fixed location. This information may also include some information on the time period the MWAB node 730 will remain at a fixed location. - Femto status information. This information indicates if the MWAB node 730 has been configured to operate as a 5G Femto node, having therefore a direct wired connection to the Core Network. Based upon the MWAB information received from the MWAB-gNB 732, the AMF 720 may decide to accept or reject the connection requested by the MWAB-gNB 732 by sending a CONNECTION CONFIRMATION message 704 to the MWAB-gNB 732. In an embodiment, the CONNECTION CONFIRMATION message 704 may be a NG SETUP FAILURE message, as specified in 3GPP TS 38.413. In an embodiment, the CONNECTION CONFIRMATION message 704 may include a Reject Cause indication, which explains the reason why the AMF 720 has decided to reject the connection requested by the MWAB-gNB 732. The AMF 720 may decide to reject the MWAB-gNB 732 connection request because it does not support MWAB or 5G Femto features, and / or because it cannot support the load induced by the Load capability information in the MWAB-gNB capability information, and / or because itineraiy information in the Mobility Profile information indicates that another AMF which has a more relevant geographical coverage is preferable to serve the MWAB-gNB 732. The rejection based on the Mobility Profile information may be in consideration of the mobility area or mobility area type of the MWAB node. Referring to Figure 8, a schematic and simplified diagram illustrating example message flow for use in managing network connectivity in a wireless communication system including at least one Wireless Access Backhaul (WAB) node in accordance with one or more embodiments of the invention and which may be used for managing the advertising by a base station of its capability and status is shown. A base station 810 (which may correspond to base station 102 of Figure 1 and BH-gNB 501 of Figure 5 as described above, or correspond to other descriptions of BH-gNB discussed herein) may share MWAB support information with its serving AMF entity 820 (which may correspond to AMF 51 la of Figure 5 as described above, or correspond to other descriptions of AMFs discussed herein) by sending MWAB support information through a BACKHAUL SUPPORT INFORMATION message 801. In some embodiments, the BACKHAUL SUPPORT INFORMATION message 801 may be the NG SETUP REQUEST message, used to exchange application-level data needed for the base station 810 and the AMF entity 820 to correctly interoperate on the NG-Control (NG-C) interface, as specified in 3GPP TS 38.413. In some embodiments, the BACKHAUL SUPPORT INFORMATION message 801 may be the RAN CONFIGURATION UPDATE message, used to update application-level configuration data needed for the base station 810 and the AMF entity 820 to correctly interoperate on the NG-Control (NG-C) interface, as specified in 3GPP TS 38.413. In other embodiments, other suitable messages may be used. The base station 810 may also broadcast MWAB information. The base station 820 may broadcast the MWAB information to the surrounding MWAB nodes in the vicinity by broadcasting a BACKHAUL INFORMATION message 802. That is to say that the base station 810 may broadcast a BACKHAUL INFORMAHON message 802 which is capable of being received by nodes or entities monitoring for broadcasts, for example by a MWAB node. The broadcast allows nodes or entities receiving in the BACKHUAL INFORMATION message 802 to be aware of the presence of a MWAB node. In some embodiments, the BACKHAUL INFORMATION message 802 may be a SIB1 message, as defined in 3GPP TS 38.331. In other embodiments, other messages specified in 3GPP or 5G NR standards may be used. The MWAB information shared by the backhaul base station (BH gNB) may include at least: - Mobile Wireless Access Backhaul support indication, orMWAB support indication, information. This information indicates that the backhaul base station is capable of serving a Mobile Wireless Access Backhaul (MWAB) node. Referring to Figure 9, a schematic and simplified diagram illustrating example message flow for use in managing network connectivity in a wireless communication system including at least one Wireless Access Backhaul (WAB) node in accordance with one or more embodiments of the invention and which may be used for managing the advertising by a WAB node of its mobility capability and status is shown. An AMF entity 920 (which may correspond to AMF 511a of Figure 5 as described above, or correspond to other descriptions of AMFs discussed herein) may authorize a MWAB-gNB 932 (which may correspond to MWAB-gNB 532 of Figure 5 as described above, or correspond to other descriptions of MWAB-gNBs discussed herein) by sending a MWAB indication authorization information through a BACKHAUL INDICAHON AUTHORIZATION message 902. That is to say that the AMF entity 920 may send a BACKHAUL INDICATION AUTHRIZATION message 902 to authorize the MWAB-gNB 923 of the MWAB node / device 930. The BACKHAUL INDICATION AUTHORIZATION message 902 used by the AMF entity to send an authorization to broadcast MWAB capability information may be a UE Configuration Update, defined in 3GPP TS 23.502. In other embodiments, other messages specified in 3GPP or 5G NR standards may be used. The BACKHAUL INDICATION AUTHORIZATION message 902 may be the Registration Accept message, as defined in 3GPP TS 23.501 and 3GPP TS 23.502. In other embodiments, other messages specified in 3GPP or 5G NR standards may be used. Upon reception of the BACKHAUL INDICATION AUTHORIZATION message 902 from the AMF entity 920, MWAB-gNB 932 may start broadcasting MWAB information to the surrounding MWAB nodes in the vicinity by broadcasting a BACKHAUL INFORMATION message 901. In some embodiments, the BACKHAUL INFORMATION message 901 may be a SIB1 message, as defined in 3GPP TS 38.331. In other embodiments, other messages specified in 3GPP or 5G NR standards may be used. The broadcasted MW AB information may include at least one of: MWAB node capability information and MWAB node status information. The MWAB node capability information may, in some embodiments, include at least one of: - Mobile Wireless Access Backhaul indication., orMWAB indication, information. This information indicates that the base station that sends the MWAB capability information is a MWAB-gNB that belongs to a MWAB node. - Mobile Wireless Access Backhaul local services support, or MWAB local services support, information. This information indicates that the Mobile Wireless Access Backhaul (MWAB) node / device 930 the MWAB-gNB 932 belongs to supports local services and / or which local services are actually supported. In some embodiments, this information may indicate the capability of the MWAB node 930 to perform Mobile Edge Computing (MEC) along with associated computing capacity information. In some embodiments, this information may indicate whether the MWAB node 930 comprises a UPF entity, i.e., an embedded UPF, such as UPF entity’ 533, for instance for the purpose of direct local inter-UE communications (e.g., direct communication of UEs 551 and 552 via UPF entity 533). - Femto Capability information. This information indicates if the WAB node 930 can be configured and behave as a Femto node. - Mobility capability information. This information indicates if the WAB node 930 can be a mobile WAB, MWAB, node. - Mobility Profile information. This information indicates the mobility’ capability of the MWAB node 930. In some embodiments, the Mobility Profile information includes at least one of: speed information indicating a speed capability of the MWAB node (e.g., min., average or max speed), mobility range information indicating a mobility area (e.g., an area defined by some GPS coordinates or other positioning or area defining systems or schemes) or mobility area type of the MWAB node (e.g., limited area (e.g., beloyv 1 km2), medium area (e.g., between 1 and 10 km2) large area (e.g., greater than 10 km2), put another way an extent of area), itinerary information, which may indicate a sequence of mobility and static periods, for an itinerary the MWAB node may follow. In some embodiments, the mobility profile information may be determined, for example from determining an average speed of the MWAB node over a given time, or it may be set, for example by inputting necessary’ details, for example maximum speed of the vehicle to which the MWAB is disposed. In both cases, the information may be updated on a regular basis, but in the determining embodiment this may be done dynamically. - Mobile Wireless Access Backhaul base station capability, or MWAB-gNB capability, information. This information indicates one or more capabilities supported by the MWAB-gNB 932. In some embodiments, the MWAB-gNB capability information may include all or some of the following information: o Load capability information. This information provides information on the load the MWAB-gNB 930 may handle when serving UEs. In some embodiments, this information may indicate the maximum number of UEs the MWAB-gNB is capable of serving, and / or a maximum throughput the MWAB-gNB is capable of handling, and / or a maximum computation power, etc. o QoS capability information. This information indicates levels of Quality of Service (QoS) the MWAB-gNB 930 is able to manage when serving UEs. The MWAB node status information may, in some embodiments, include at least one of: - Mobility status information. This information indicates whetherthe MWAB node 930 is currently moving or is remaining at a fixed location, i.e. static. This information may also include some information on the time period the MWAB node will remain at a fixed location. - Femto status information. This information indicates if the MWAB node has been configured to operate as a 5G Femto node, having therefore a direct wired connection to the Core Network. While the above description refers to different reference numerals for the same features or elements between different figures, it does not necessarily indicate that the features or elements between the figures are different. Reference to MWAB node / device, or mobile WAB node / device, throughout the description should be considered to also refer to WAB node / device. Typically a WAB node may be understood to refer particularly but not exclusively to the node / device being non-mobile, i.e. disposed to a fixed, i.e. static, structure, for example, MWAB node 130 may be considered a WAB node 130 because it is mounted to a building. In most cases, as is understood from the forgoing, mobile may be understood to mean capable of moving, i.e. capable of changing geographical location, and still operating. For example, by being attached to a vehicle or person which is capable of moving. Discussion of capability information in relation to one embodiment shown in the figures may be applicable to capability information discussed in relation to an embodiment shown in a different figure. Discussion of status information in relation to one embodiment shown in the figures may be applicable to status information discussed in relation to an embodiment shown in a different figure. While the present invention has been described with reference to examples and embodiments, it is to be understood that the invention is not limited to the disclosed examples and embodiments. It will be appreciated by those skilled in the art that various changes and modification might be made without departing from the scope of the invention, as defined in the appended claims. All of the features disclosed in this specification (including any accompanying claims, abstract and drawings), and / or all of the steps of any method or process so disclosed, may be combined in any combination, except combinations where at least some of such features and / or steps are mutually exclusive. Each feature disclosed in this specification (including any accompanying claims, abstract and drawings) may be replaced by alternative features serving the same, equivalent or similar purpose, unless expressly stated otherwise. Thus, unless expressly stated otherwise, each feature disclosed is one example only of a generic series of equivalent or similar features. In the claims, the word “comprising” does not exclude other elements or steps, and the indefinite article “a” or “an” does not exclude a plurality. The mere fact that different features are recited in mutually different dependent claims does not indicate that a combination of these features cannot be advantageously used. In the preceding embodiments, the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored on or transmitted over, as one or more instructions or code, a computer-readable medium and executed by a hardware-based processing unit. Computer-readable media may include computer-readable storage media, which corresponds to a tangible medium such as data storage media, or communication media including any medium that facilitates transfer of a computer program from one place to another, e.g., according to a communication protocol. In this manner, computer-readable media generally may correspond to (1) tangible computer-readable storage media which is non-transitory or (2) a communication medium such as a signal or carrier wave. Data storage media may be any available media that can be accessed by one or more computers or one or more processors to retrieve instructions, code and / or data structures for implementation of the techniques described in this disclosure. A computer program product may include a computer-readable medium. By way of example, and not limitation, such computer-readable storage media can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage, or other magnetic storage devices, flash memory, or any other medium that can be used to store desired program code in the form of instructions or data structures and that can be accessed by a computer. Also, any connection is properly termed a computer-readable medium. For example, if instructions are transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave may be included in the definition of medium. It should be understood, however, that computer-readable storage media and data storage media do not include connections, carrier waves, signals, or other transient media, but are instead directed to non-transient, tangible storage media. Disk and disc, as used herein, includes compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc, where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.

Claims

1. A method for use in managing connectivity of a wireless access backhaul, WAB, node connected or to be connected to at least one core network via a backhaul gNB, the WAB node including a gNB component and a Mobile Tennination component, the method at the WAB node comprising:sending information associated with the WAB node, the information including at least one of: an indication that the information is associated with a WAB node;information associated with one or more capabilities supported by the WAB node;information for indicating that the WAB node comprises both the gNB component and the Mobile Tennination component; andinformation indicating local services of the WAB node.

2. A method as claimed in claim 1, further comprisingreceiving, by the WAB node, a connection message comprising connection information based on the information associated with the WAB node.

3. A method as claimed in claim 2, wherein, in the case that a node or entity of the at least one core network or the backhaul gNB is unable to serve the WAB node, the connection information indicates a rejection of connection; and wherein, in the case that the node or entity of the at least one core network or the backhaul gNB is able to serve the WAB node, the connection information indicates an acceptance of connection.

4. A method as claimed in claim 3, wherein the connection information, in the case the node or entity of the core network or the backhaul gNB is unable to serve the WAB node, comprises information indicating the cause of rejection.

5. A method as claimed in any one of claims 2 to 4, wherein the connection message is a CONNECTION CONFIRMATION message.

6. A method as claimed in claim 5, wherein, in the case the node or entity of the core network is unable to service the WAB node, the CONNECTION CONFIRMATION message is at least one of: registration reject message; and NG setup failure.

7. A method as claimed in any one of claims 2 to 4, wherein, in the case tire backhaul gNB is unable to service the WAB node, the connection confirmation message is at least one of: RRCReject; andRRCReconfiguration.

8. A method as claimed in any one of the preceding claims, further comprising controlling the Mobile Termination component of the WAB node to send the information associated with the WAB node.

9. A method as claimed in any one of the preceding claims, further comprising controlling the gNB component of the WAB node to send the information associated with the WAB node.

10. A method as claimed in any one of the preceding claims, further comprising controlling the gNB component of the WAB node to send the information associated with the WAB node to the Mobile Termination component of the WAB node.

11. A method as claimed in any one of the preceding claims, further comprising receiving, by the WAB node, authorization information for indicating that the WAB node is authorized to perform a function.

12. A method as claimed in claim 11, wherein a backhaul indication authorization message includes the authorization information.

13. A method as claimed in claim 12, wherein the backhaul indication authorization message is a message defined for use in the 5G New Radio standard.

14. A method as claimed in claim 12 or claim 13, wherein the backhaul indication authorization message is one of:UE Configuration Update;Registration Accept;AMF configuration update; and CONNECTION CONFIRMATION.

15. A method as claimed in any one of claims 11 to 14, wherein the authorization information comprises broadcast authorization information for authorizing the WAB node to broadcast information associated with the WAB node.

16. A method as claimed in claim 15, further comprising controlling the WAB node to send information associated with the WAB node through a broadcast.

17. A method for use in managing connectivity of a wireless access backhaul,WAB, node connected or to be connected to at least one core network via a backhaul gNB, the WAB node including a gNB component and a Mobile Termination component, the method at the backhaul gNB comprising:receiving information associated with the WAB node, the information including at least one of: an indication that the information is associated with a WAB node;information associated with one or more capabilities supported by the WAB node;information for indicating that the WAB node comprises both the gNB component and the Mobile Termination component; andinformation indicating local services of the WAB node.

18. A method as claimed in claim 17, further comprising sending at least some of the information associated with the WAB node to an entity of the core network.

19. A method as claimed in claims 17 or claim 18, further comprising storing the received information associated with the WAB node.

20. A method as claimed in any one of claims 17 to 19, wherein the backhaul gNB receives the information from the Mobile Termination component of the WAB node.

21. A method as claimed in any one of claims 17 to 20, further comprisingsending a connection message comprising connection information based on the received information associated with the WAB node.

22. A method as claimed in claim 21, wherein, in the case that the backhaul gNB is unable to serve the WAB node, the connection information indicates a rejection of connection.

23. A method as claimed in claim 21 or claim 22, wherein the connection information, in the case tire backhaul gNB is unable to serve the WAB node, comprises information indicating the cause of rejection.

24. A method as claimed in any one of claims 21 to 23, wherein, in the case the backhaul gNB is unable to serve the WAB node, the connection confirmation message is at least one of:RRCReject; andRRCReconfiguration.

25. A method for use in managing connectivity of a wireless access backhaul, WAB, node connected or to be connected to at least one core network via a backhaul gNB, the WAB node including a gNBcomponent and a Mobile termination component, the method at an AMF entity of the core network comprising:receiving information associated with the WAB node, the information including at least one of: an indication that the information is associated with a WAB node;information associated with one or more capabilities supported by the WAB node;information for indicating that the WAB node comprises both the gNB component and the Mobile Termination component; andinformation indicating local services of the WAB node.

26. A method as claimed in claim 25, further comprising storing the received information associated with the WAB node.

27. A method as claimed in claim 25 or claim 26, further comprisingsending a connection message comprising connection information based on the received information associated with the WAB node.

28. A method as claimed in claim 27, wherein, in the case that the AMF entity is unable to serve the WAB node, the connection information indicates a rejection of connection.

29. A method as claimed in claim 27 or claim 28, wherein the connection information, in the case the AMF entity is unable to serve the WAB node, comprises information indicating the cause of rejection.

30. A method as claimed in any one of claims 27 to 29, wherein the connection message is a CONNECTION CONFIRMATION message.

31. A method as claimed in any of claims 27 to 30, wherein, in the case the AMF entity is unable to serve the WAB node, the CONNECTION CONFIRMATION message is at least one of:registration reject message; and- NG setup failure.

32. A method for use in managing connectivity of a wireless access backhaul, WAB, node connected or to be connected to at least one core network via a backhaul gNB, the WAB node including a gNB component and a Mobile Termination component, the method at an UPF entity of the core network comprising:receiving information associated with the WAB node, the information including at least one of: an indication that the information is associated with a WAB node;information associated with one or more capabilities supported by the WAB node;information for indicating that the WAB node comprises both the gNB component and the Mobile Termination component; andinformation indicating local services of the WAB node.

33. A method as claimed in claim 32, further comprising sending at least some of the information associated with the WAB node to another entity of the core network.

34. A method as claimed in claim 32 or claim 33, wherein the information associated with the WAB node is received during a PDU session.

35. A method as claimed in any one of claims 32 to 34, wherein the information associated with the WAB node is received from the Mobile Termination component of the WAB node.

36. A method as claimed in any one of the preceding claims, wherein the information indicating local services of the WAB node includes information indicating whether the WAB node is configured to provide local sendees.

37. A method as claimed in any one of the preceding claims, wherein the information indicating local services of the WAB node includes information identifying the local services the WAB node is configured to provide.

38. A method as claimed in any one of the preceding claims, wherein the information indicating local services of the WAB node includes information indicating the WAB node is configured to perform Mobile Edge Computing and information indicating computer processing capability.

39. A method as claimed in any one of the preceding claims, wherein the information indicating local services of the WAB node includes information indicating the WAB node includes a User Plane Function, UPF).

40. A method as claimed in any one of the preceding claims, wherein the information for indicating that the WAB node comprises both the gNB component and the Mobile Termination component comprises information identifying either one or both the gNB component of the WAB node and the Mobile Termination component of the WAB node.

41. A method as claimed in any one of the preceding claims, where the information for indicating that the WAB node comprises both the gNB component and the Mobile Termination component is colocation information.

42. A method as claimed in any one of the preceding claims, wherein the information for indicating that the WAB node comprises both the gNB component and the Mobile Termination component is provided as C-RNTI information.

43. A method as claimed in any one of the preceding claims, wherein the information associated with one or more capabilities supported by the WAB node includes at least one of:information indicating whether the WAB node is configured to operate while moving;information related to the mobility of the WAB node;information indicating whether the WAB node is configured to operate as a Femto node; information indicating the load capability of the WAB node; and information indicating the levels of quality of service.

44. A method as claimed in any preceding claim, wherein the information associated with the WAB node includes at least one of information related to the current status of the WAB node.

45. A method as claimed in claim 44, wherein the information related to the current status of the WAB node include at least one of:- Information indicating whether the WAB node is moving or static;- Information indicating a time that the WAB node is moving or static;- Information indicating that the WAB node is operating as a femto node.

46. A method as claimed in any one of claims 43 to 45, wherein the information related to the mobility of the WAB node includes at least one of: information indicating a speed capability of the WAB node, infonuation indicating range of mobility, information indicating mobility area, information indicating mobility area type, information indicating itinerary of the WAB node.

47. A method as claimed in any one of claims 43 to 46, wherein the information indicating the load capability of the WAB node includes at least one of: information indicating the maximum number of User Equipment (UE) capable of being serve by the WAB node, the maximum throughput of the WAB node, maximum computation power, and computer processing information.

48. A method as claimed in any of claims 43 to 47, wherein the information indicating the load capability of the WAB node includes load capability of the base station of the WAB node.

49. A method as claimed in any preceding claim, wherein a backhaul information message comprises the information associated with the WAB node.

50. A method as claimed in claim 49, wherein in the backhaul information message is one of the messages defined in the 5G New Radio standard.

51. A method as claimed in claim 49 or claim 50, wherein the backhaul information message is at least one of:RCCsetupRequest;RRC Setup Complete;NAS Registration Request;NG Setup Request;NGAP Initial UE;AMF CONFIGURATION UPDATE; andSIB1.

52. A method as claimed in any one of claims 49 to 51, wherein a field of the backhaul information message comprises the information associated with the WAB node.

53. A method as claimed in claim 52, wherein the field of the backhaul information message is a dcdicatcdNAS-mcssagc field.

54. A method as claimed in any one of the preceding claims, wherein the WAB node is a mobile WAB node.

55. An apparatus for a wireless access backhaul, WAB, node, the apparatus comprising at least one processing unit configured to perform a method according to any one of claims 1 to 16 and 36 to 54.

56. A computer program comprising instructions which, when executed by at least one processor unit, causes the at least one processor unit to carry out a method according to any one of claims 1 to 16 and 36 to 54.

57. A computer-readable medium carrying a computer program according to claim 56.

58. An apparatus for a backhaul gNB connected to or to be connected to a wireless access backhaul, WAB, node, the apparatus comprising at least one processing unit configured to perform a method according to any one of claims 17 to 24 and 36 to 54.

59. A computer program comprising instructions which, when executed by at least one processor unit, causes the at least one processor unit to carry out a method according to any one of claims 17 to 24 and 36 to 54.

60. A computer-readable medium carrying a computer program according to claim 59.

61. An apparatus for an AMF entity connected to or to be connected to a wireless access backhaul, WAB, node, the apparatus comprising at least one processing unit configured to perform a method according to any one of claims 25 to 31 and 36 to 54.

62. A computer program comprising instructions which, when executed by at least one processor unit, causes the at least one processor unit to cany out a method according to any one of claims 25 to 31 and 36 to 54.

63. A computer-readable medium carrying a computer program according to claim 62.

64. An apparatus for an UPF entity connected to or to be connected to a wireless access backhaul, WAB, node, the apparatus comprising at least one processing unit configured to perform a method according to any one of claims 32 to 54.

65. A computer program comprising instructions which, when executed by at least one processor unit, causes the at least one processor unit to carry out a method according to any one of claims 32 to 54.

66. A computer-readable medium cawing a computer program according to claim 65.

67. A method for use in managing connectivity of a wireless access backhaul .WAB, node connected or to be connected to at least one core network via a backhaul gNB, the WAB node including a gNB component and a Mobile Tennination component, the method at the backhaul gNB comprising: sending information indicating that the backhaul base station is capable of serving a WAB node.

68. A method as claimed in claim 67, wherein the backhaul gNB sends the information to a node or entity of the wireless communication system.

69. A method as claimed in claim 68, wherein the node or entity of the wireless communication system comprises a node or entity of at least one core network of the wireless communication system.

70. A method as claimed in claim 68 or claim 69, wherein the node or entity is an Access and Mobility Management Function, AMF, entity.

71. A method as claimed in any one of claims 67 to 70, wherein the information is provided in a Backhaul Support Information message.

72. A method as claimed in claim 71, wherein the backhaul support information message is one is consistent with message defined in the 5G New Radio standard.

73. A method as claimed in claim 71 or claim 72, wherein the backhaul support information message is at least one of:RAN Configuration update;NG Setup request message;Xn Setup Request; andSIB1.

74. A method as claimed in any one of claims 67 to 73, wherein sending the information indicating that the backhaul base station is capable of serving a WAB comprises broadcasting the information.

75. A method as claimed in any one of claims 67 to 74, wherein the node or entity of the wireless communication system is a further backhaul gNB.

76. A method as claimed in any one of claims 67 to 75, wherein the node or entity of the wireless communication system is the WAB node or a mobile WAB node.

77. An apparatus for a backhaul gNB in a wireless communication system, the apparatus comprising at least one processing unit configured to perform a method according to any one of claims 67 to 76.

78. A computer program comprising instructions which, when executed by at least one processor unit, causes the at least one processor unit to cany out a method according to any one of claims 67 to 76.

79. A computer-readable medium carrying a computer program according to claim 78.

80. A method for use in managing connectivity of a wireless access backhaul, WAB, node in a wireless communication system, the WAB node including a gNB component and a Mobile Termination component, tire method comprising:sending, from a node or entity of a wireless communication system to a WAB node, authorization information for indicating that the WAB node is authorized to perform a function.

81. A method as claimed in claim 80, wherein the node or entity of the wireless communication system comprises a node or entity of a core network of the wireless communication system.

82. A method as claimed in claim 80 or claim 81, wherein the node or entity of the wireless communication system is an Access and Mobility Management Function, AMF, entity.

83. A method as claimed in any one of claims 80 to 82, wherein a backhaul indication authorization message includes the authorization information.

84. A method as claimed in claim 83, wherein the backhaul indication authorization message is a message defined for use in the 5G New Radio standard.

85. A method as claimed in claim 83 or claim 84, wherein the backhaul indication authorization message is one of:UE Configuration Update message;Registration Accept message;AMF configuration update message; andCONNECTION CONFIRMATION message.

86. A method as claimed in any one of claims 83 to 85, wherein the authorization information comprises broadcast authorization information for authorizing the WAB node to broadcast information associated with the WAB node.

87. An apparatus for managing a wireless access backhaul, WAB, node, the apparatus comprising at least one processing unit configured to perform a method according to any one of claims 80 to 87.

88. A computer program comprising instructions which, when executed by at least one processor unit, causes the at least one processor unit to carry out a method according to any one of claims 80 to 87.

89. A computer-readable medium carrying a computer program according to claim 88.

Images