Network node, mobile base station and methods therein, in a wireless communications network

Abstract

A method performed by a network node 110, 130 is provided. The method is for controlling a mobile Base Station (mBS) in a wireless communications network. The network node 110, 130 obtains (201) a User equipment Mobility Profile (UMP), of respective one or more UEs served or expected to be served by the mBS in a first region, R1. The network node 110, 130 obtains (202) a UE Operational Status (UOS) of the respective one or more UEs. The respective UOS comprises one or more of a UE radio access status and a target quality of service. The network node 110, 130 determines (204) a mBS Operational Profile (MOP) of the mBS based on the obtained UMP and the UOS. The MOP comprises a second region, R2 and a mBS Mobility Profile (MMP). The MMP will be used by the mBS for operating in R2, and the MOP will be used by the mBS for performing one or more operational tasks in R2 for serving the at least one out of the one or more UEs.

Description

[0001] NETWORK NODE, MOBILE BASE STATION AND METHODS THEREIN, IN A WIRELESS COMMUNICATIONS NETWORK

[0002] TECHNICAL FIELD

[0003] Embodiments herein relate to a network node, a mobile Base Station (mBS), and methods therein. In some aspects, they relate to controlling the mBS in a wireless communications network.

[0004] BACKGROUND

[0005] In a typical wireless communication network, wireless devices, also known as wireless communication devices, mobile stations, stations (STA) and / or User Equipment (UE), communicate via a Wide Area Network or a Local Area Network such as a Wi-Fi network or a cellular network comprising a Radio Access Network (RAN) part and a Core Network (CN) part. The RAN covers a geographical area which is divided into service areas or cell areas, which may also be referred to as a beam or a beam group, with each service area or cell area being served by a radio network node 110, 130 such as a radio access node e.g., a Wi-Fi access point, a Base Station (BS) or a radio base station (RBS), which in some networks may also be denoted, for example, a Base Station (BS), a NodeB, eNodeB (eNB), or gNodeB (gNB) as denoted in Fifth Generation (5G) telecommunications. A service area or cell area is a geographical area where radio coverage is provided by the radio network node 110, 130. The radio network node 110, 130 communicates over an air interface operating on a radio frequency with the wireless devices within the range of the radio network node 110, 130.

[0006] 3rd Generation Partnership Project (3GPP) is the standardization body for specifying the standards for the cellular system evolution, e.g., including 3G, 4G, 5G and the future evolutions. Specifications for Evolved Universal Terrestrial Radio Access (E- UTRA) and Evolved Packet System (EPS) have been completed within the 3GPP. In 4G also called a Fourth Generation (4G) network, EPS is core network and E-UTRA is radio access network. In 5G, 5G Core (5GC) is core network, NR is radio access network. As a continued network evolution, the new release of 3GPP specifies a 5G network also referred to as 5G New Radio (NR) and 5GC.

[0007] Frequency bands for 5G NR are being separated into two different frequency ranges, Frequency Range 1 (FR1) and Frequency Range 2 (FR2). FR1 comprises sub-6 GHz frequency bands. Some of these bands are bands traditionally used by legacy standards but have been extended to cover potential new spectrum offerings from 410 MHz to 7125 MHz. FR2 comprises frequency bands from 24.25 GHz to 52.6 GHz. Bands in this millimeter wave range have shorter range but higher available bandwidth than bands in the FR1.

[0008] Multi-antenna techniques may significantly increase the data rates and reliability of a wireless communication system. For a wireless connection between a single user, such as UE, and a Base Station (BS), the performance is in particular improved if both the transmitter and the receiver are equipped with multiple antennas, which results in a Multiple-Input Multiple-Output (MIMO) communication channel. This may be referred to as Single-User (SU)-MIMO. In the scenario where MIMO techniques is used for the wireless connection between multiple users and the base station, MIMO enables the users to communicate with the base station simultaneously using the same time-frequency resources by spatially separating the users, which increases further the cell capacity. This may be referred to as Multi-User (MU)-MIMO. Note that MU-MIMO may benefit when each UE only has one antenna. The cell capacity can be increased linearly with respect to the number of antennas at the BS side. Due to that, more and more antennas are employed in BS. Such systems and / or related techniques are commonly referred to as massive MIMO.

[0009] Network deployment

[0010] A Terrestrial Network (TN) is traditionally deployed using fixed BSs, which do not move. Therefore, a fixed BS is statically deployed in a certain location within a specific coverage area. A cell planning for the static deployment is based on a two-dimensional deployment. Typically, the cell planning is based on traditional hexagonal cells with directional antennas to secure radio coverage and radio performance.

[0011] The mBSs on the other hand, may move from one location to another. Therefore, the introduction of an mBS enables dynamic deployment of the BSs based on the need. These mBSs may be part of a TN, such as e.g., cell or BS on wheels or may be a part of non-terrestrial networks, e.g., aerial base stations, platforms such as High altitude platform International mobile telecommunications Base Station (HIBS), base station deployed on movable vehicle (e.g. truck, lorry etc), drone base stations, Integrated Access and Backhaul (IAB)s on airplanes etc. From time to time, such mBS in the air may be semi statically deployed by positioning them in certain locations for certain time period. The mBS may also be in the air all the time, hovering over a certain location or change positions constantly.

[0012] The combination of statically deployed base stations and base stations that is dynamically deployed opens new ways to perform base station deployments and dynamically adjust radio performance.

[0013] SUMMARY

[0014] As part of developing embodiments herein, the inventors identified some problems that first will be described.

[0015] In an existing solution, a mBS serves one or more UEs especially in location which lacks static Base Station (sBS) coverage or when the system load is temporarily and unexpectedly very high during some events, such as e.g., large congregation, recreational activity such as outdoor concert, sports event etc. In some scenarios, the system load, e.g., the number of UEs to be served, required system throughput, may vary in the same broader coverage area e.g., within a stadium, car race etc. Currently, a such scenario is addressed, wherein a drone base station serving UEs adjust its own position based on the radio link quality of the UEs with respect to the drone BS. While this may help serve the UEs with low radio link quality, a drawback is that the user bit rate of some other UEs will decrease as the drone will move away from those UEs. In a worst case, some of the UEs may even loose connection with respect to the drone BS. In this case additional drone BSs may be required to serve the remaining UEs thereby increasing the cost, increasing the interference due to more drone BSs in the same geographical region and delay due to re-establishment of connections and / or handovers etc.

[0016] An object of embodiments herein is to improve the performance of a wireless communications network using mBSs.

[0017] According to an aspect of embodiments herein, the object is achieved by a method performed by a network node 110, 130. The method is for controlling a mobile Base Station, mBS, in a wireless communications network. The network node 110, 130 obtains a User Equipment, UE, Mobility Profile, UMP, of respective one or more UEs served or expected to be served by the mBS in a first region, R1 . The network node 110, 130 obtains a UE Operational Status, UOS, of the respective one or more UEs. The respective UOS comprises one or more of a UE radio access status and a target quality of service. The network node 110, 130 determines a mBS Operational Profile, MOP, of the mBS based on the obtained UMP and the UOS. The MOP comprises a second region, R2, and a mBS Mobility Profile, MMP. The MMP will be used by the mBS for operating in R2. The MOP will be used by the mBS for performing one or more operational tasks in R2 for serving the at least one out of the one or more UEs.

[0018] According to an aspect of embodiments herein, the object is achieved by a method performed by a mobile Base Station, mBS, in a wireless communications network. The mBS serves one or more UEs in a first region, R1 . The mBS receives a mBS Operational Profile, MOP, for the mBS from a network node 110, 130. The MOP is based on a UE Mobility Profile, UMP, and a UE Operational Status, UOS, of the respective one or more UEs. The MOP comprises a second region, R2, and a mBS Mobility Profile, MMP. The mBS operates in R2 according to the MMP for serving at least one out of the one or more UEs. The mBS performs the one or more operational tasks in R2 according to the received MOP.

[0019] According to another aspect of embodiments herein, the object is achieved by a network node 110, 130. The network node 110, 130 is configured to control a mobile Base Station, mBS, in a wireless communications network. The network node 110, 130 is further configured to:

[0020] - Obtain a User Equipment, UE, Mobility Profile, UMP, of respective one or more UEs to be served or expected to be served by the mBS in a first region, R1 .

[0021] - Obtain a UE Operational Status, UOS, of the respective one or more UEs. The respective UOS is adapted to comprise one or more of a UE radio access status and a target quality of service,

[0022] - Determine a mBS Operational Profile, MOP, of the mBS based on the obtained UMP and the UOS. The MOP is adapted to comprise a second region, R2, and a mBS Mobility Profile, MMP. The MMP is adapted to be used by the mBS for operating in R2. The MOP is adapted to be used by the mBS for performing one or more operational tasks in R2 for serving the at least one out of the one or more UEs.

[0023] According to an aspect of embodiments herein, the object is achieved by a mobile Base Station, mBS, in a wireless communications network. The mBS is configured to serve one or more UEs in a first region, R1 . The mBS is further being configured to: - Receive from a network node 110, 130, a mBS Operational Profile, MOP, for the mBS. The MOP is adapted to be based on a UE Mobility Profile, UMP, and a UE Operational Status, UOS, of the respective one or more UEs. The MOP is adapted to comprise a second region, R2, and a mBS Mobility Profile, MMP.

[0024] Operate in R2 according to the MMP, for serving at least one out of the one or more UEs. The mBS is further configured to perform the one or more operational tasks in R2 according to the received MOP.

[0025] Embodiments herein may provide one or more of the following advantages:

[0026] They enhance overall wireless communications network performance, e.g. increase in system capacity, by enabling the mBS to operate and serve UEs regardless of their mobility status.

[0027] They especially enhance the system performance especially in scenarios where the traffic requirement and / or number of active UEs rapidly change.

[0028] They reduce overall interference and cost of operation since the same mBS or fewer mBSs may serve and satisfy UEs even in very dynamic environment.

[0029] They reduce overall power consumption of the mBS and UEs thanks to dynamic adaptation of the mBS trajectory based on factors such as knowledge of the UEs’ mobility profile and static and / or dynamic capabilities, e.g. transmit power, transceiver, antennas etc.

[0030] BRIEF DESCRIPTION OF THE DRAWINGS

[0031] Examples of embodiments herein are described in more detail with reference to attached drawings in which:

[0032] Figure 1 is a schematic block diagram illustrating embodiments of a wireless communications network.

[0033] Figure 2 is a flowchart depicting an embodiment of a method in a network node 110, 130.

[0034] Figure 3 is a flowchart depicting an embodiment of a method in a mBS.

[0035] Figure 4 is a schematic block diagram illustrating an example scenario according to embodiments herein.

[0036] Figure 5 is a schematic block diagram illustrating an example scenario according to embodiments herein.

[0037] Figure 6 is a schematic block diagram illustrating embodiments of a network node 110, 130. Figure 7 is a schematic block diagram illustrating embodiments of a mBS. Figure 8 schematically illustrates embodiments of a communication system. Figure 9 is a generalized block diagram of embodiments of a UE.

[0038] Figure 10 is a generalized block diagram of embodiments of a network node 110, 130.

[0039] Figure 11 is a generalized block diagram of embodiments of a host.

[0040] Figure 12 is a generalized block diagram of embodiments of a virtualization environment.

[0041] Figure 13 is a generalized block diagram of embodiments of a communication diagram of a host.

[0042] DETAILED DESCRIPTION

[0043] As mentioned above, an object of embodiments herein is to improve the performance of a wireless communications network using mBSs. The wireless communication networks may be deployed in various ways with combinations of stationary and mobile base stations.

[0044] Example embodiments herein provide a comprehensive way to serve UEs by a mBS in a scenario in which the system load of the densely located UEs rapidly changes in some extra ordinary events e.g., large temporary gathering of UEs requiring high data services such as high-quality real-time audio / video clips etc.

[0045] Examples of embodiments herein provide a method in a network node 110, 130, which manages or controls an mBS. The network node 110, 130 may in some embodiments be the mBS itself and in other embodiments a control node. The method performed by the network node 110, 130 may in some embodiments comprise the following actions:

[0046] • Obtaining a UE Mobility Profile (UMP) of one or more UEs served by the mBS in a first area or region (R1); wherein the UMP comprises one or more of a UE speed, a UE direction of motion, a UE trajectory, a UE location.

[0047] • Obtaining a UE Operational Status (UOS) of one or more UEs served by the mBS in R1 ; wherein the UOS comprises one or more of a UE radio access status, e.g. transmit power, receive antenna status, transmit antenna status, bandwidth etc., and a target quality of service, e.g., user bit rate, delay sensitivity such as best effort, real time video etc. • Determining an mBS Operational Profile (MOP) of the mBS based on the obtained UMP and the UOS; where the MOP comprises a second area or region (R2) and a mBS Mobility Profile (MMP) with which the mBS is going to operate in R2. And

[0048] • Using the determined MOP for performing one or more operational tasks.

[0049] Examples of embodiments herein further provide a method in an mBS. The method performed by the mBS may comprise the following actions:

[0050] • Receiving from a network node 110, 130, an information related to an MOP comprising a second area or region (R2) and an MMP with which the mBS is going to operate in R2. ; And

[0051] • Operating the mBS for serving one or more UEs in R2 according to the received information related to MOP.

[0052] Figure 1 is a schematic overview depicting a wireless communications network 100 wherein embodiments herein may be implemented. The wireless communications network 100 comprises one or more RANs, one or more CNs and a conversation AR network 105. The communications network 100 may use 5G NR but may further use a number of other different technologies, such as, 6G, Wi-Fi, Long Term Evolution (LTE), LTE-Advanced, Wideband Code Division Multiple Access (WCDMA), Global System for Mobile communications / enhanced Data rate for GSM Evolution (GSM / EDGE), Worldwide Interoperability for Microwave Access (WiMax), or Ultra Mobile Broadband (UMB), just to mention a few possible implementations.

[0053] Network node 110, 130s, which e.g., may be base stations such as an mBS 110, operate in the RAN the communications network 100. The base stations, may each be a transmission and reception point e.g. a radio access network node 110, 130 such as a base station, e.g. a radio base station such as a NodeB, an evolved Node B (eNB, eNode B), an NR Node B (gNB), a base transceiver station, a radio remote unit, an Access Point Base Station, a base station router, a transmission arrangement of a radio base station, a stand-alone access point, a Wireless Local Area Network (WLAN) access point or an Access Point Station (AP STA), an access controller, or any other network unit capable of communicating with UEs.

[0054] According to embodiments herein, the mBS 110 is operable in different regions such as e.g., a first region R1 and a second region R2. Thus, the mBS 110 is capable of communicating with UEs, such as the UEs 121 , 122, 123 within the regions, such as the first region R1 and the second region R2, served by the mBS 110. The respective mBS 110 may be referred to as a serving radio network node 110, 130 and may communicate with the UEs 121 , 122, 123 with Downlink (DL) transmissions to the UEs 121 , 122, 123, and in Uplink (UL) transmissions from the UEs 121 , 122, 123. A region when used herein may comprise a geographical area, a radio coverage area, a zone.

[0055] One or more UEs operate in the wireless communication network 100, such as e.g. the UEs 121, 122, 123. The UEs 121 , 122, 123 may e.g. be a respective remote UE, a wireless device, an NR device, a mobile station, a wireless terminal, an NB-loT device, an MTC device, an eMTC device, a CAT-M device, a WiFi device, an LTE device and an a non-access point (non-AP) STA, a STA, that communicates via a base station such as e.g. the mBS 110, one or more Access Networks (AN), e.g. a RAN, to one or more core network (CN) nodes, in one or more CNs.

[0056] It should be understood by the skilled in the art that “UE” is a non-limiting term which means any terminal, client, mobile client, IMS client, wireless communication terminal, user equipment, Device to Device (D2D) terminal, or node e.g. smart phone, laptop, mobile phone, sensor, relay, mobile tablets or even a car or any small base station communicating within a cell and / or a region such as e.g., the first region R1 and the second region R2, served by the mBS 110.

[0057] Network node 110, 130s, such as a control node 130, operate in the wireless communications network 100. In some embodiments herein the control node 130 controls the mBS 110. The control node 130, may e.g., be a radio network node 110, 130 or a node in a core network or a separate server.

[0058] Methods according to one aspect of embodiments herein are performed by a network node 110, 130 such as e.g. the mBS 110 or the control node 130. The network node 110, 130 is therefore referred to as the network node 110, 130. Thus the mBS 110 may be controlled by the control node 130 or may be controlled by itself.

[0059] Methods according to another aspect of embodiments herein are performed by the mBS 110.

[0060] Methods according to embodiments herein are performed by the IMS node 130 and the PS CN node 151. This node may be Distributed Nodes (DN)s and functionality, e.g. comprised in a cloud 170 as shown in Figure 4. Terminologies

[0061] In this disclosure, the term node is used, which may be a user equipment (UE) or a network node 110, 130.

[0062] In some embodiments the non-limiting term “user equipment” (UE) is used and it refers to any type of wireless device communicating with a network node 110, 130 and / or with another UE in a cellular or mobile communication system. The UE can also be an aerial vehicle, which can be any type of flying object equipped with a UE. Examples of UE are target device, device to device (D2D) UE, machine type UE or UE capable of machine to machine (M2M) communication, PDA, tablet computer, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles, ProSe UE, V2V UE, V2X UE, MTC UE, eMTC UE, FeMTC UE, UE Cat 0, UE Cat M1 or M2, narrowband Internet of Things (NB-loT) UE, UE Cat NB1 or NB2, passive loT device, ambient loT device, aerial UE (AUE), e.g., UE operating above certain height), AUE is also called as drone UE or aerial vehicle etc.

[0063] The term ‘network node 110, 130’ refers to any type of node which communicates with a UE and / or with another network node 110, 130, e.g., with a BS). Examples of network node 110, 130s are NodeB, base station (BS), multi-standard radio (MSR) radio node such as MSR BS, eNodeB, gNodeB, MeNB, SeNB, location measurement unit (LMU), integrated access backhaul (IAB) node, network controller, radio network controller (RNC), base station controller (BSC), relay, donor node controlling relay, base transceiver station (BTS), Central Unit, e.g., in a gNB), Distributed Unit, e.g., in a gNB), Baseband Unit, Centralized Baseband, C-RAN, access point (AP), transmission points, transmission nodes, transmission reception point (TRP), RRU, RRH, nodes in distributed antenna system (DAS), core network node 110, 130, e.g., MSC, MME etc., O&M, OSS, SON, positioning node, e.g., E-SMLC) etc.

[0064] The term “static base station (sBS)” used in some embodiments refers to a base station whose geographical location does not change over time. The sBS may also be called as stationary BS, fixed BS or immovable BS.

[0065] The term “mobile base station (mBS)” used in some embodiments refers to a base station whose geographical location may change over time or at least have the capability to change its geographical location. For example, the mBS 110 has necessary circuitry and aerodynamic capability which enables it to physically fly or move in the air or in 3- dimensional space in any direction. The mBS 110 can however also remain stationary for certain time-period. The mBS 110 can be an independent node or it can be located or housed in another node or device, e.g., on a satellite etc. The movement of the mBS 110 may be controlled by another node or autonomously, e.g., based on pre-configured information such as of the event such as planned race). The mBS 110 may also be called as non-stationary BS, drone BS, non-terrestrial network (NTN) node, movable BS or high- altitude platform station (HAPS).

[0066] According to examples of embodiments herein, the network node 110, 130 determines an operational profile of the mBS 110 serving one or more UEs 121 , 122, 123 based on the UEs 121 , 122, 123 mobility profile, their static and dynamic capability status and their target quality of service.

[0067] The network node 110, 130 enables the mBS 110 to operate and serve the users according to the determined operational profile, e.g. in certain region such as any of the the first region R1 and the second region R2, and with certain mobility profile etc. The mBS’s 110 operational profile may be determined by the mBS 110 itself or by another network node 110, 130 such as the control node 130 controlling or managing the mBS.

[0068] A number of embodiments will now be described, some of which may be seen as alternatives, while some may be used in combination.

[0069] A method according to embodiments will first be described more in general as seen from the view of the network node 110, 130 together with Figure 2, and then as seen from the view of the mBS 110 together with Figure 3. This will be followed by a more detailed description with definitions and some examples of embodiments herein.

[0070] Figure 2 shows exemplary embodiments of a method performed by the by a network node 110, 130. The method is for controlling the mBS 110 in the wireless communications network 100. As mentioned above, in some embodiments, the network node 110, 130 is represented by the mBS 110. In some other embodiments, the network node 110, 130 is represented by a control node 130.

[0071] The method comprises the following actions, which actions may be taken in any suitable order. Optional actions are referred to as dashed boxes in Figure 2.

[0072] An example scenario comprises a first region referred to as R1 , such as e.g., a first coverage area, zone or geographical region, in which one or more of the UEs 121 , 122, 123 are served or expected to be served by the mBS 110. The mBS 110 may serve the UEs 121 , 122, 123 in R1 in one or more cells, e.g., co-located cells on different carrier frequencies. The first region R1 may be linear or multi-dimensional geographical zone.

[0073] Action 201. The network node 110, 130 obtains a UE Mobility Profile (UMP), of respective one or more UEs 121 , 122, 123 served or expected to be served by the mBS 110 in a first region, R1 . A UMP of each UE may comprises one or more parameters defining the mobility characteristic or aspect of the UE.

[0074] In some embodiments, the UMP of the respective one or more UEs 121 , 122, 123 comprises one or more out of, e.g., one or more parameters out of: a UE speed, a UE direction of motion, a UE acceleration, a UE trajectory, and a UE location.

[0075] Action 202. The network node 110, 130 obtains a UE Operational Status (UOS) of the respective one or more UEs 121 , 122, 123. The respective UOS comprises one or more of a UE radio access status and a target quality of service.

[0076] In some embodiments, the respective UE radio access status comprises any one or more out of a transmit power, a receive antenna status, a transmit antenna status, and a bandwidth.

[0077] In some embodiments, the respective target quality of service comprises any one or more out of: a UE bit rate, a Block Error Rate (BLER) delay sensitivity, a round trip delay and a packet transmission delay.

[0078] Action 203. In some embodiments, the network node 110, 130 may determine R2 based on the obtained UMP and the UOS.

[0079] In one example, if the number of UEs 121 , 122, 123, served by the mBS 110, larger than certain threshold is distributed or expected to be distributed outside or at the boundary of their original region R1 , then the network node 110, 130 may determine that the second region R2 shall be larger than the first region R1 .

[0080] In another example, if the number of UEs 121 , 122, 123, served by the mBS 110, larger than certain threshold, is concentrated or expected to be concentrated well inside their original first region R1 , then the network node 110, 130 may determine that the second region R2 shall be smaller than the first region R1.

[0081] On the other hand, if the number of UEs 121 , 122, 123, served by the mBS 110, larger than certain threshold, is concentrated or expected to be concentrated well outside their original first region R1 , then the network node 110, 130 determines that the second region R2 shall be in a region which does not overlap with the first region R1 . Action 204. The network node 110, 130 determines an mBS Operational Profile, (MOP) of the mBS 110 based on the obtained UMP and the UOS. The MOP comprises the second region R2, and an mBS Mobility Profile (MMP).

[0082] The MMP will be used by the mBS 110 for operating in R2. The MOP will be used by the mBS 110 for performing one or more operational tasks in R2 for serving the at least one out of the one or more UEs 121 , 122, 123. The MOP may e.g., be optimized for at least the one or more UEs 121 , 122, 12. However, the mBS 110 may also has to serve other UEs if there are e.g. new UEs entering. The MOP is determined semi-statically so new UEs may come, therefore the MOP is for serving the “ at least” one out of the one or more UEs 121 , 122, 123. In some embodiments, the determining of the MOP of the mBS is performed when one or more of the following conditions are met:

[0083] - according to a periodicity,

[0084] - after a duration over which the determined MOP is valid,

[0085] - when the UOS of the one or more UEs 121 , 122, 123 is changed,

[0086] - when a number of the one or more UEs 121 , 122, 123 and / or other UEs served by the mBS 110 is changed, e.g. increased or decreased, by a certain threshold; and

[0087] - upon receiving a message from the mBS 110 requesting to receive its MOP.

[0088] In some embodiments, the one or more operational tasks in R2 for serving the one or more UEs 121 , 122, 123 comprises serving the at least one out of the one or more UEs 121 , 122, 123 in R2.

[0089] Action 205. In some embodiments, the network node 110, 130 is represented by a control node 130. In these embodiments, the network node 110, 130 may send to the mBS 110, information related to the MOP. The MOP may comprise information about the R2 and the MMP. The MMP may be used by the mBS 110 for operating in R2. The MOP may be used by the mBS 110 for performing one or more operational tasks in R2 for serving the one or more UEs 121 , 122, 123.

[0090] Action 206. In some other embodiments, the network node 110, 130 is represented by the mBS 110. In these embodiments, the network node 110, 130 may operate in R2 for serving the one or more UEs 121 , 122, 123 according to the MMP. Action 207. In some embodiments, the network node 110, 130 is represented by the mBS 110. In these embodiments, the network node 110, 130 may perform the one or more operational tasks in R2 according to the determined MOP.

[0091] Figure 3 shows exemplary embodiments of a method performed by the mBS 110 in the wireless communications network 100. The mBS 110 serves one or more UEs 121 , 122, 123 in a first region, R1.

[0092] An example scenario, a similar scenario as described above, comprises a first region R1 , in which the one or more of the UEs 121 , 122, 123 are served or expected to be served by the mBS 110. The mBS 110 may serve the UEs 121 , 122, 123 in R1 in one or more cells, e.g., co-located cells on different carrier frequencies. The first region R1 may be linear or multi-dimensional geographical zone.

[0093] The method comprises the following actions, which actions may be taken in any suitable order. Optional actions are referred to as dashed boxes in Figure 3.

[0094] The network node 110, 130 may in these embodiments be represented by the control node 130. The mBS 110 may in these embodiments be controlled by the control node 130.

[0095] Action 301. The mBS 110 may in some embodiments send a request to the network node 110, 130 130, requesting to receive an mBS Operational Profile (MOP) for the mBS 110 for performing one or more operational tasks in R2.

[0096] Action 302. The mBS 110 receives from the network node 110, 130 130, a MOP for the mBS 110, e.g. as requested. The MOP is based on a UE Mobility Profile (UMP) and a UE Operational Status (UOS) of the respective one or more UEs 121 , 122, 123. The MOP comprises a second region R2, and a mBS Mobility Profile (MMP). The UMP and UOS of the one or more UEs 121 , 122, 123 may in some cases not be known to the wireless communications network 1100 before mBS 110 receives the MOP for R2.

[0097] In some embodiments, the one or more UEs 121 , 122, 123 are assigned a respective UMP and a respective UOS. In these embodiments, the respective UOS comprises one or more of a UE radio access status and a target quality of service.

[0098] The respective UE radio access status may comprise any one or more out of a transmit power, a receive antenna status, a transmit antenna status, and a bandwidth. In some embodiments, the respective target quality of service comprises any one or more out of: UE bit rate, Block Error Rate, BLER, delay sensitivity, round trip delay, and packet transmission delay.

[0099] In some embodiments, the respective UMP of the one or more UEs 121 , 122, 123 comprises one or more out of a UE speed, a UE direction of motion, a UE acceleration, a UE trajectory, and a UE location.

[0100] Action 303. The mBS 110 operates in R2 according to the MMP, for serving at least one out of the one or more UEs 121 , 122, 123.

[0101] Action 304. The mBS 110 performs the one or more operational tasks in R2 according to the received MOP. In some embodiments, the one or more operational tasks in R2 comprises serving the one or more UEs 121 , 122, 123 in R2.

[0102] In this way, by performing the above method, the mBS 110 is e.g., capable of serving the UEs 121 , 122, 123 even when their coverage and location changes rapidly e.g. large number of UEs move from one location to another location in the same arena, stadium etc. Yet another advantage is that the mBS 110 enables the continuity of the ongoing service for the UEs 121 , 122, 123 even if their location changes. Yet another advantage is that on the average the mBS 110 is able to serve the UEs with lower amount of resources (e.g. lower transmit power etc) by physically moving closer to the UEs 121 , 122, 123, e.g., to large cluster of the UEs. This in turn enhances the system throughput and also decreases the interference in the wireless communications network 100.

[0103] Embodiments herein such as the embodiments mentioned above will now be further described and exemplified. The text below is applicable to and may be combined with any suitable embodiment described above.

[0104] Scenario

[0105] As mentioned above an example scenario comprises a first coverage area, zone or geographical region referred to as first region R1 , in which the one or more UEs 121 , 122, 123 are served or expected to be served by a mBS 110. The mBS 110 may serve the UEs 121 , 122, 123 in the first region R1 in one or more cells, e.g., co-located cells on different carrier frequencies. The first region R1 , may be linear or multi-dimensional geographical zone. Figure 4 depicts an example illustrating the UEs 121 , 122, 123 and further UE4, UE5 and UEn, and served or expected to be served by the mBS 110 in certain geographical region, the first region R1.

[0106] In one example, the mBS 110 operates, e.g. trajectory, speed etc., independently or autonomously in the first region R1 for serving the one or more UEs 121 , 122, 123. In another example, the mBS 110 operation, e.g. trajectory, speed etc., may be fully or partially controlled or managed by another network node 110, 130, such as the control node 130, which may be a radio network node 110, 130 or a node in a core network or an separate server.

[0107] The above described actions are described below in details with examples.

[0108] First embodiments of the method actions performed by the network node 110, 130. Will now be described.

[0109] Action 201. The network node 110, 130, obtaining an UMP.

[0110] In this action the network node 110, 130 obtains a UE mobility profile (UMP) of the one or more UEs 121 , 122, 123 served by or expected to be served by a mBS 110 in the first region R1 . For example, the mBS 110 may currently be operating or is configured to operate in R1 , which may be 1-dimensional, 2-dimensional or 3-dimensinal region in Euclidean space.

[0111] The UMP of each UE 121 , 122, 123 may comprise one or more parameters defining the mobility characteristic or aspect of the UE121 , 122, 123. Examples of such parameters are any one or more out of:

[0112] • UE speed. It may be expressed in physical speed of the UE 121 , 122, 123, e.g. in distance per unit time such as X11 km / hour, X12 m / second etc., and / or in Doppler frequency, e.g., X13 Hz etc. of the carrier frequency on which the UE 121 , 122, 123 operates.

[0113] • UE direction of motion. It is expressed in angular orientation of the UE 121 , 122, 123 wrt a reference direction e.g. X31 degrees wrt reference direction in azimuth plane and / or X32 degrees wrt reference direction in zenith / elevation plane etc.

[0114] • UE trajectory. It may be expressed in terms of a set of two or more waypoints or multiple locations which the UE 121 , 122, 123 will pass along its trajectory. Each waypoint comprises at least one set of geographical coordinates. • UE acceleration: It is the change in the speed and may be expressed in terms of e.g. X21 m / s2.

[0115] • UE location. It is expressed in terms of geographical coordinates of the UE 121 , 122, 123 at its current location.

[0116] The network node 110, 130 may obtain one or more parameters related to the UMP of the UE 121 , 122, 123 based on one or more of the following mechanisms:

[0117] • By receiving it directly from the UE. For example, the UE 121 , 122, 123 may determine its UMP and transmit it to the network node 110, 130. The UE 121 , 122, 123 may determine its UMP based on measurements performed by the UE 121 , 122, 123 on the signals transmitted between the UE 121 , 122, 123 and one or more base stations.

[0118] • By autonomously determining the UMP of the UE. For example, the network node 110, 130 may determine the UMP of the UE 121 , 122, 123 based on measurements performed by the network node 110, 130 on signals transmitted between the UE 121 , 122, 123 and the network node 110, 130. This mechanism may be used if the network node 110, 130 is also the serving base station of the UE 121 , 122, 123, e.g. the mBS 110.

[0119] • By receiving it from another node e.g., serving base station, location server, e.g., LMF etc. For example, the other network node 110, 130 may determine the UMP of the UE 121 , 122, 123 based on the measurements received from the UE 121 , 122, 123 and / or the UE’s serving base station. The measurements are performed by the UE 121 , 122, 123 and / or by the serving base station on the signals transmitted between the UE 121 , 122, 123 and one or more base stations.

[0120] Action 202. The network node 110, 130 obtaining UOS

[0121] In this action the network node 110, 130 obtains a UE Operational Status (UOS) of one or more UEs 121 , 122, 123 served by or expected to be served by the mBS 110 in R1. The UOS of each UE 121 , 122, 123 may comprise at least one of the following aspects:

[0122] • UE radio access status (RAS). It indicates the UE 121 , 122, 123’s radio access capability, which may be static, semi-static or dynamic. Examples of the parameters defining the RAS of the UE 121 , 122, 123 are transmit power, e.g. current transmit power, average transmit power over certain time period etc., maximum output power (Pmax), e.g., supported power class such as 23 dBm, 26 dBm etc., power headroom, e.g., difference between Pmax and available transmit power in dB, number of supported receive (Rx) antennas, Rx antenna status, e.g., number of currently used Rx antennas, number of currently available Rx antennas etc., number of supported transmit (Tx) antennas, Tx antenna status, e.g., number of currently used Tx antennas, number of currently available Tx antennas etc., reception bandwidth (BW), transmission BW, UL and / or DL beamforming capability, e.g., number of supported MIMO layers in UL and / or in DL etc., number of beams / layers currently used or available for use, UL and / or DL multi-carrier (MC) capability, e.g., UL and / or DL carrier aggregation etc., number of component carriers currently used or available for use, bandwidth part (BWP) related parameter, e.g., BW of the DL BWP and / or BW of the UL BWP) etc.; and

[0123] • target quality of service. It indicates the desired / expected performance of the UE 121 , 122, 123’s service. It may be expressed in terms of one or more of target user bit rate, e.g., average bit rate, maximum bit rate, minimum bit rate etc., target maximum packet delay, target maximum packet loss rate, characteristic or type of service, e.g., delay sensitivity level such as best effort, real time video etc.

[0124] The network node 110, 130 obtains one or more parameters related to the UOS of the UE 121 , 122, 123 based on one or more of the following mechanisms:

[0125] • By receiving it directly from the UE. For example, the UE 121 , 122, 123 may transmit one or more radio access related parameters and / or the quality of service to the network node 110, 130 via signalling, e.g., RRC, MAC or DCI message. If the network node 110, 130 is located in or is part of the core network then it may receive the UOS parameter, e.g., quality of service etc. via NAS signalling message. In one example, the UE 121 , 122, 123 may transmit the UOS as part of the radio access capability, e.g., via RRC if the parameter is static or semi-static such as the UE 121 , 122, 123 output power class. In another example, the UE 121 , 122, 123 may transmit the UOS as part of the UE 121 , 122, 123 assistance information (UAI) especially if the parameter is dynamic or semi-static such as the currently available Rx antennas etc. In another example, the UE 121 , 122, 123 may transmit the UOS via dynamic signalling, e.g., via DCI or MAC) if the parameter is dynamic such as power headroom etc.

[0126] • By autonomously determining the UOS of the UE. For example, the network node 110, 130 may determine the UOS of the UE 121 , 122, 123 based on historical data or past statistics. This mechanism may be used if the network node 110, 130 has logged or stored the previously used UOS related parameters of the UE 121 , 122, 123.

[0127] • By receiving it from another node e.g., serving base station, core network node 110, 130, e.g., AMF etc. For example, the network node 110, 130 may receive the one or more UOS related parameters from another network node 110, 130 which has information about the UOS of the UE 121 , 122, 123. For example, the AMF may contain the radio access capability information of the UE 121 , 122, 123 and transmit it to the network node 110, 130 e.g. serving base station such as the mBS 110.

[0128] Action 204. The network node 110, 130 obtaining a MOP

[0129] In this action the network node 110, 130 determines a mBS 110 operational profile (MOP) of the mBS 110 based on the obtained UMP and the obtained UOS in the previous actions.

[0130] The MOP of the mBS 110 may comprise at least the following two characteristics:

[0131] • a second area or region (R2). R2 may be 1 -dimensional, 2-dimensional or 3-dimensinal region in Euclidean space. R2 may be the same as R1 or it may be different than R1 . In the latter case, R2 may be larger than R1 or less than R1 . R2 may be static or it may change semi-statically or dynamically after certain time period. R2 may further comprises two or more sub-regions, e.g., R21 , R22, R23 etc. if at least certain number of the one or more UEs 121 , 122, 123 are distributed in different parts of R2; and

[0132] • a mBS 110 mobility profile (MMP). The MMP comprises one or more of the same parameters used for defining the UMP, as described above. In addition, the MMP may further comprise of the dwell time or sojourn time (Ts) of the mBS

[0133] 110 in different sub-regions of R2. The Ts may be expressed in absolute duration, e.g., Y11 seconds in R21 , Y12 seconds in R22 etc. and / or in relative duration wrt the total time, e.g., Y21 percent of time in R21 , Y22 percent of time in R22 etc. The MMP may further comprise of two or more values of the same parameter to serve different sets of UEs in different sub-regions of R2 and / or different sets of UEs requiring different QoS / data rate in the same region or different sub-regions of R2. For example, the MMP may comprise of the mBS 110 speed vector, instead of single speed, e.g., comprising two or more speed levels of the mBS 110 associated with different sub-regions of R2. In another example, the MMP may comprise of the mBS 110 trajectory vector consisting of two or more trajectories, e.g., 2-dimensional matrix of waypoints) for serving the one or more UEs 121 , 122, 123 located in different sub, -regions of R2.

[0134] The determined MOP enables the mBS 110 or is used by the mBS 110 to operate, e.g., serve UEs 121 , 122, 123 in the determined R2 according to the determined MMP during certain time period e.g. over the next time period, T11 , e.g., starting from a reference time (Tr). T11 may be finite value or unlimited time. Tr may be the current time or certain future time. Examples of Tr are cell time, e.g., slot number, subframe number, frame number, SFN number etc., universal time, e.g., UTC time etc. etc.

[0135] The determination of the MOP based on the UMP and the UOS is based on one or more rules or principles, which are described below with examples:

[0136] 1. In some examples of the rule, if the number of UEs 121 , 122, 123 larger than certain threshold is distributed or expected to be distributed outside or at the boundary of their original region, R1 , then the network node 110, 130 creates R2 larger than R1. On the other hand, if the number of UEs 121 , 122, 123 larger than certain threshold is concentrated or expected to be concentrated well inside their original region, R1 , then the network node 110, 130 creates R2 smaller than R1 . On the other hand if the number of UEs 121 , 122, 123 larger than certain threshold UEs is concentrated or expected to be concentrated well outside their original region, R1 , then the network node 110, 130 creates R2 in a region which does not overlap with R1 .

[0137] 2. In another example of the rule, if the speed of number of UEs 121 , 122, 123 larger than certain threshold is above certain margin then the network node 110, 130 also sets the mBS 110 speed, as part of its MMP, above certain threshold. If the number of UEs 121 , 122, 123 larger than certain threshold is also distributed in different sub-regions, e.g., R21 , R22, R23 etc. of the determined R2 then the network node 110, 130 also sets the mBS 110 acceleration, as part of its MMP, above certain threshold for quickly moving across the sub-regions to serve the UEs 121 , 122, 123 across the different sub-regions.

[0138] 3. In another example of the rule, the network node 110, 130 may determine R2 and / or the MMP based on the radio access status of the UEs 121 , 122, 123 as follows. For example, if the available transmit power and / or the maximum output power of at least certain number of UEs 121 , 122, 123 is above their respective thresholds then the network node 110, 130 may determine the second region R2 larger than certain threshold, otherwise the network node 110, 130 may determine the second region R2 smaller than certain threshold. In the former case the mBS 110 may provide better coverage to the UEs 121 , 122, 123 due to their higher UE transmit power. In another example, if the number of Rx antennas and / or number of Tx antennas of at least certain number of UEs 121 , 122, 123 is above their respective thresholds then the network node 110, 130 may determine the second region R2 larger than certain threshold, otherwise the network node 110, 130 may determine R2 smaller than certain threshold. In the former case the mBS 110 may provide better coverage to the UEs 121 , 122, 123 by means of Rx and / or Tx beamforming as it requires two or more Rx / Tx antennas.

[0139] 4. In another example of the rule, the network node 110, 130 may determine the second region R2 and / or the MMP based on the target quality of service of the UEs 121 , 122, 123 as follows. For example, if the number of UEs 121 , 122, 123 requiring high bit rate above certain threshold then the network node 110, 130 may determine the second region R2 smaller than certain threshold and / or may determine the speed of the mBS 110 larger than certain threshold. In another example, the network node 110, 130 may determine two or more trajectories within the second region R2 for serving UEs 121 , 122, 123 requiring different quality of service e.g., for one set of UEs 121 , 122, 123 using best effort service, for another set of UEs 121 , 122, 123 using high quality real video service etc. In another example, if the required user bit rate of at least two set of UEs 121 , 122, 123 differ by more than certain threshold and they are also located in different sub-regions then the network node 110, 130 may determine two or more sojourn time values, e.g., Ts1 , Ts2 etc. within R2 for serving these different sets of the UEs 121 , 122, 123; otherwise the network node 110, 130 may determine the same sojourn time value for serving all the UEs 121 , 122, 123 in different sub-regions of the second region R2.

[0140] 5. In another example of the rule, if the UEs 121 , 122, 123 are concentrated in two or more sub-regions regions within the second region R2 and their target quality of service is the same then in one example the network node 110, 130 may determine a static or quasi-static MMP of the mBS 110 e.g., the mBS 110 may stay static between the sub-regions or oscillate with low speed between the sub-regions. This approach guarantees that all UEs 121 , 122, 123 achieve acceptable average bit rate. In another example the network node 110, 130 may determine trajectory and speed of the mBS 110 such that all UEs 121 , 122, 123 consistently achieve at least certain minimum bit rate. But in addition, when the mBS 110 moves closer to certain sub-region then the UEs 121 , 122, 123 in that region are served / scheduled with higher data rate e.g., due to high SINR etc. Therefore, in the second approach all UEs 121 , 122, 123 may be occasionally or periodically served with high data rate.

[0141] Action 207 and 304. The network node 110, 130 is using determined MOP for operational tasks.

[0142] In this action the network node 110, 130, such as e.g., the mBS 110, uses the determined MOP of the mBS 110 in a previous action for performing one or more operational tasks. Examples of such tasks are:

[0143] • Transmitting information about the determined MOP to another network node 110, 130. For example, if the network node 110, 130 is a centralized network node 110, 130 then it sends the MOP information to the mBS 110 or to a network node 110, 130 which may configure the mBS 110 to serve the UEs 121 , 122, 123 in certain region. The information may further include the time period during which the MOP is applicable. The information may further request the mBS 110 (or another node managing the mBS 110 to operate according to the transmitted MOP information over the indicated time period.

[0144] • Using the determined MOP for operating the mBS 110 in the determined region, R2 and with a mobility profile according to the determined MMP. For example, if the network node 110, 130 is the mBS 110 itself then the mBS 110 configures its mobility profile based on MMP and starts serving the UEs 121 , 122, 123 in the region R2.

[0145] Figure 5 illustrates an example in which the mBS 110 serves the UEs 121 , 122, 123, which are mainly concentrated in three different sub-regions R21 , R22 and R23 within the main region, the second region R2, which is the serving cell. The figure shows that the mBS 110 movement trajectory is adapted to the UEs 121 , 122, 123 distribution within R2 and is determined based on the mBS 110 MOP, which in turn is determined by the network node 110, 130, e.g., a centralized node or the mBS 110 itself.

[0146] Second embodiments of the method actions performed by the mBS 110 for serving one or more UEs 121 , 122, 123 will now be described, wherein the mBS 110 is receiving and using the mBS 110 operational profile for serving UEs 121 , 122, 123.

[0147] In these embodiments it may be assumed that the MOP of the mBS 110 is determined by another network node 110, 130 using the principles as described in the first embodiments. The mBS 110 therefore receives the information about its MOP from the network node 110, 130, e.g., via signalling message. See Action 302 described above. The contents of the message are the same as described in the first embodiments, e.g., information about the second region R2, sub-regions, e.g., R21 , R22, etc. within R2, MMP of the mBS 110, sojourn time, such as e.g., a temporary stay, in R2, sojourn times for different sub-regions, reference start time (Trs) from when the indicated MOP is or going to become valid etc. The message needs to be standardized.

[0148] The mBS 110 after receiving the information configures itself with one or more parameters within the MOP message. The mBS 110 starts serving the UEs 121 , 122, 123 according to the configured one or more parameters within the MOP e.g., starting from Trs. See Actions 303 and 304 described above.

[0149] The mBS 110 may further inform the network node 110, 130 after serving the UEs

[0150] 121 , 122, 123 in region R2 after the indicated sojourn time.

[0151] To perform the method actions above, the network node 110, 130 is configured to control a mobile Base Station, mBS, 110 in a wireless communications network 100.

[0152] The network node 110, 130 may comprise an arrangement depicted in Figure 6.

[0153] The network node 110, 130 130 may comprise an input and output interface 600 configured to communicate in the communications network 100, e.g., with the mBS 110. The input and output interface 600 may comprise a wireless receiver not shown, and a wireless transmitter not shown.

[0154] The network node 110, 130 is further configured to obtain a UMP of respective one or more UEs 121 , 122, 123 to be served or expected to be served by the mBS 110 in a first region, R1.

[0155] The network node 110, 130 is further configured to obtain a UOS of the respective one or more UEs 121 , 122, 123 wherein the respective UOS is adapted to comprise one or more of a UE radio access status and a target quality of service.

[0156] The network node 110, 130 is further configured to determine a MOP of the mBS 110 based on the obtained UMP and the UOS. The MOP is adapted to comprise a second region, R2, and an MMP. The MMP is adapted to be used by the mBS 110 for operating in R2. The MOP is adapted to be used by the mBS 110 for performing one or more operational tasks in R2 for serving the at least one out of the one or more UEs 121 ,

[0157] 122, 123.

[0158] The network node 110, 130 may further be configured to determine R2 based on the obtained UMP and the UOS. In some embodiments, the network node 110, 130 is represented by the mBS 110. In those embodiments, the network node 110, 130 is further configured to operate in R2 for serving the one or more UEs 121 , 122, 123 according to the MMP and perform the one or more operational tasks in R2 according to the determined MOP.

[0159] In some other embodiments, the network node 110, 130 is represented by a control node 130. In those embodiments, the network node 110, 130 is further configured to send to the mBS 110, information related to the MOP. The MOP may be adapted to comprise information about the R2 and the MMP. The MMP is adapted to be used by the mBS 110 for operating in R2. The MOP is adapted to be used by the mBS 110 for performing one or more operational tasks in R2 for serving the one or more UEs 121 , 122, 123.

[0160] The respective UMP of the one or more UEs 121 , 122, 123 may be adapted to comprise one or more out of: a UE speed, a UE direction of motion, a UE acceleration, a UE trajectory, and a UE location.

[0161] In some embodiments, the respective UE radio access status is adapted to comprise any one or more out of: a transmit power, a receive antenna status, a transmit antenna status, and a bandwidth.

[0162] The respective target quality of service may be adapted to comprise any one or more out of: UE bit rate, BLER delay sensitivity, and round trip delay and packet transmission delay.

[0163] The network node 110, 130 may further be configured to determine the MOP of the mBS when one or more of the following conditions are met: according to a periodicity, after a duration over which the determined MOP is valid, when the UOS of the one or more UEs 121 , 122, 123 is changed, when a number of the one or more UEs 121 , 122, 123 and / or other UEs served by the mBS 110 is changed by a certain threshold; and upon receiving a message from the mBS 110 requesting to receive its MOP.

[0164] In some embodiments, the one or more operational tasks in R2 for serving the one or more UEs 121 , 122, 123 is adapted to comprise serving the at least one out of the one or more UEs 121 , 122, 123 in R2.

[0165] To perform the method actions above, the mBS 110 in the wireless communications network 100 is configured to serve one or more UEs 121 , 122, 123 in a first region, R1.

[0166] The mBS 110 may comprise an arrangement depicted in Figure 7. The mBS 110 may comprise an input and output interface 700 configured to communicate in the communications network 100, e.g., with the network node 110, 130 130. The input and output interface 700 may comprise a wireless receiver not shown, and a wireless transmitter not shown.

[0167] The mBS 110 is further being configured to receive from a network node 110, 130 130, a MOP, for the mBS 110. The MOP is adapted to be based on a UMP, and a UOS of the respective one or more UEs 121 , 122, 123. The MOP is adapted to comprise a second region R2, and an MMP.

[0168] The mBS 110 is further being configured to operate in R2 according to the MMP, for serving at least one out of the one or more UEs 121 , 122, 123.

[0169] The mBS 110 is further being configured to perform the one or more operational tasks in R2 according to the received MOP.

[0170] In some embodiments, the one or more UEs 121 , 122, 123 are adapted to be assigned a respective UMP and a respective UOS. In those embodiments, the respective UOS is adapted to comprise one or more of a UE radio access status and a target quality of service.

[0171] In some embodiments, the one or more operational tasks in R2 is adapted to comprise serving the one or more UEs 121 , 122, 123 in R2.

[0172] The mBS 110 may further be configured to send a request to the network node 110, 130 130, requesting to receive the MOP for the mBS 110 for performing the one or more operational tasks in R2.

[0173] The respective UMP of the one or more UEs 121 , 122, 123 may be adapted to comprise one or more out of a UE speed, a UE direction of motion, a UE acceleration, a UE trajectory, and a UE location.

[0174] In some embodiments, the respective UE radio access status is adapted to comprise any one or more out of a transmit power, a receive antenna status, a transmit antenna status, and a bandwidth.

[0175] In some embodiments, the respective target quality of service is adapted to comprise any one or more out of: UE bit rate, BLER delay sensitivity, round trip delay, and packet transmission delay.

[0176] The network node 110, 130 may be represented by a control node 130.

[0177] Embodiments herein may be implemented through a respective processor or one or more processors, such as the respective processor 610 of a processing circuitry in the network node 110, 130 depicted in Figure 6, and processor 710 of a processing circuitry in the mBS 110 depicted in Figure 7 together with respective computer program code for performing the functions and actions of the embodiments herein. The program code mentioned above may also be provided as a computer program product, for instance in the form of a data carrier carrying computer program code for performing the embodiments herein when being loaded into the respective network node 110, 130 and mBS 110. One such carrier may be in the form of a CD ROM disc. It is however feasible with other data carriers such as a memory stick. The computer program code may furthermore be provided as pure program code on a server and downloaded to the respective network node 110, 130 and mBS 110.

[0178] The network node 110, 130 and mBS 110 may further comprise a respective memory 620 and memory 720 comprising one or more memory units. The respective memory 620 and memory 720 comprises instructions executable by the processor in the respective network node 110, 130 and mBS 110. The respective memory 620 and memory 720 are arranged to be used to store e.g., media functions, indications, tags, information, data, configurations, communication data, and applications to perform the methods herein when being executed in the respective network node 110, 130 and mBS 110.

[0179] In some embodiments, a respective computer program 630 and computer program 730 comprises instructions, which when executed by the respective at least one processor 610 and processor 710, cause the at least one processor of respective network node 110, 130 and mBS 110 to perform the actions above.

[0180] In some embodiments, a respective carrier 640 and carrier 740 comprises the respective computer program 630 and computer program 730, wherein the respective carrier 640 and carrier 740 is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer-readable storage medium.

[0181] Those skilled in the art will appreciate that units in the respective network node 110, 130 and mBS 110 described above may refer to a combination of analog and digital circuits, and / or one or more processors configured with software and / or firmware, e.g. stored in the respective network node 110, 130 and mBS 110, that when executed by the respective one or more processors such as the processors described above. One or more of these processors, as well as the other digital hardware, may be included in a single Application-Specific Integrated Circuitry ASIC, or several processors and various digital hardware may be distributed among several separate components, whether individually packaged or assembled into a System-on-a-Chip (SoC). ADDITIONAL EXPLANATION

[0182] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0183] Figure 8 shows an example of a communication system QQ100 in accordance with some embodiments.

[0184] In the example, the communication system QQ100 includes a telecommunication network QQ102 that includes an access network QQ104, such as a radio access network (RAN), and a core network QQ106, which includes one or more core network node 110, 130s QQ108. The access network QQ104 includes one or more access network node 110, 130s, such as network node 110, 130s QQ110a and QQ110b (one or more of which may be generally referred to as network node 110, 130s QQ110), or any other similar 3rd Generation Partnership Project (3GPP) access nodes or non-3GPP access points. Moreover, as will be appreciated by those of skill in the art, a network node 110, 130 is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network node 110, 130s include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunication network QQ102 includes one or more Open-RAN (ORAN) network node 110, 130s. An ORAN network node 110, 130 is a node in the telecommunication network QQ102 that supports an ORAN specification, e.g.,, a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other nodes to implement one or more functionalities of any node in the telecommunication network QQ102, including one or more network node 110, 130s QQ110 and / or core network node 110, 130s QQ108.

[0185] Examples of an ORAN network node 110, 130 include an open radio unit (O-RU), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O-CU-CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near- real time or non-real time) hosting software or software plug-ins, such as a near-real time control application, e.g.,, xApp) or a non-real time control application, e.g.,, rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). The network node 110, 130 may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an A1 , F1 , W1 , E1 , E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN access node may be a logical node in a physical node. Furthermore, an ORAN network node 110, 130 may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an 0-2 interface defined by the O-RAN Alliance or comparable technologies. The network node 110, 130s QQ110 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 121 , QQ112a, QQ112b, QQ112c, and QQ112d (one or more of which may be generally referred to as UEs QQ112) to the core network QQ106 over one or more wireless connections.

[0186] Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system QQ100 may include any number of wired or wireless networks, network node 110, 130s, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals whether via wired or wireless connections. The communication system QQ100 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0187] The UEs QQ112 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with the network node 110, 130s QQ110 and other communication devices. Similarly, the network node 110, 130s QQ110 are arranged, capable, configured, and / or operable to communicate directly or indirectly with the UEs QQ112 and / or with other network node 110, 130s or equipment in the telecommunication network QQ102 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunication network QQ102.

[0188] In the depicted example, the core network QQ106 connects the network node 110, 130s QQ110 to one or more hosts, such as host QQ116. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network node 110, 130s may be directly coupled to hosts. The core network QQ106 includes one more core network node 110, 130s, e.g.,, core network node 110, 130 QQ108) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network node 110, 130s, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 110, 130 QQ108. Example core network node 110, 130s include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).

[0189] The host QQ116 may be under the ownership or control of a service provider other than an operator or provider of the access network QQ104 and / or the telecommunication network QQ102, and may be operated by the service provider or on behalf of the service provider. The host QQ116 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

[0190] As a whole, the communication system QQ100 of Figure 8 enables connectivity between the UEs, network node 110, 130s, and hosts. In that sense, the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard, e.g.,, 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox.

[0191] In some examples, the telecommunication network QQ102 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network QQ102 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network QQ102. For example, the telecommunications network QQ102 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and / or Massive Machine Type Communication (mMTC)ZMassive loT services to yet further UEs.

[0192] In some examples, the UEs QQ112 are configured to transmit and / or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network QQ104 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network QQ104. Additionally, a UE may be configured for operating in single- or multi- RAT or multi-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).

[0193] In the example, the hub QQ114 communicates with the access network QQ104 to facilitate indirect communication between one or more UEs, e.g.,, UE QQ112c and / or QQ112d) and network node 110, 130s, e.g.,, network node 110, 130 QQ110b). In some examples, the hub QQ114 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub QQ114 may be a broadband router enabling access to the core network QQ106 for the UEs. As another example, the hub QQ114 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network node 110, 130s QQ110, or by executable code, script, process, or other instructions in the hub QQ114. As another example, the hub QQ114 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub QQ114 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub QQ114 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node 110, 130, which the hub QQ114 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub QQ114 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.

[0194] The hub QQ114 may have a constant / persistent or intermittent connection to the network node 110, 130 QQ110b. The hub QQ114 may also allow for a different communication scheme and / or schedule between the hub QQ114 and UEs, e.g.,, UE QQ112c and / or QQ112d), and between the hub QQ114 and the core network QQ106. In other examples, the hub QQ114 is connected to the core network QQ106 and / or one or more UEs via a wired connection. Moreover, the hub QQ114 may be configured to connect to an M2M service provider over the access network QQ104 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network node 110, 130s QQ110 while still connected via the hub QQ114 via a wired or wireless connection. In some embodiments, the hub QQ114 may be a dedicated hub - that is, a hub whose primary function is to route communications to / from the UEs from / to the network node 110, 130 QQ110b. In other embodiments, the hub QQ114 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 110, 130 QQ110b, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0195] Figure 9 shows a UE QQ200 in accordance with some embodiments. As used herein, a UE refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes such as e.g. the network node 110, 130 and / or other UEs, such as e.g., the one or more UEs 121 , 122, 123. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle, vehicle-mounted or vehicle embedded / integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-loT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

[0196] A UE may support device-to- device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, a UE may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user, e.g.,, a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user, e.g.,, a smart power meter).

[0197] The UE QQ200 includes processing circuitry QQ202 that is operatively coupled via a bus QQ204 to an input / output interface QQ206, a power source QQ208, a memory QQ210, a communication interface QQ212, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure 9. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0198] The processing circuitry QQ202 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory QQ210. The processing circuitry QQ202 may be implemented as one or more hardware-implemented state machines, e.g.,, in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry QQ202 may include multiple central processing units (CPUs).

[0199] In the example, the input / output interface QQ206 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into the UE QQ200. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera, e.g.,, a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device. In some embodiments, the power source QQ208 is structured as a battery or battery pack. Other types of power sources, such as an external power source, e.g.,, an electricity outlet), photovoltaic device, or power cell, may be used. The power source QQ208 may further include power circuitry for delivering power from the power source QQ208 itself, and / or an external power source, to the various parts of the UE QQ200 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source QQ208. Power circuitry may perform any formatting, converting, or other modification to the power from the power source QQ208 to make the power suitable for the respective components of the UE QQ200 to which power is supplied.

[0200] The memory QQ210 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory QQ210 includes one or more application programs QQ214, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data QQ216. The memory QQ210 may store, for use by the UE QQ200, any of a variety of various operating systems or combinations of operating systems.

[0201] The memory QQ210 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and / or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUlCC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory QQ210 may allow the UE QQ200 to access instructions, application programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory QQ210, which may be or comprise a device-readable storage medium. The processing circuitry QQ202 may be configured to communicate with an access network or other network using the communication interface QQ212. The communication interface QQ212 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna QQ222. The communication interface QQ212 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication, e.g.,, another UE or a network node 110, 130 in an access network). Each transceiver may include a transmitter QQ218 and / or a receiver QQ220 appropriate to provide network communications, e.g.,, optical, electrical, frequency allocations, and so forth). Moreover, the transmitter QQ218 and receiver QQ220 may be coupled to one or more antennas, e.g.,, antenna QQ222) and may share circuit components, software or firmware, or alternatively be implemented separately.

[0202] In the illustrated embodiment, communication functions of the communication interface QQ212 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented in according to one or more communication protocols and / or standards, such as IEEE 802.11 , Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / internet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

[0203] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface QQ212, via a wireless connection to a network node 110, 130. Data captured by sensors of a UE can be communicated through a wireless connection to a network node 110, 130 via another UE. The output may be periodic, e.g.,, once every 15 minutes if it reports the sensed temperature), random, e.g.,, to even out the load from reporting from several sensors), in response to a triggering event, e.g.,, when moisture is detected an alert is sent), in response to a request, e.g.,, a user initiated request), or a continuous stream, e.g.,, a live video feed of a patient).

[0204] As another example, a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node 110, 130 via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.

[0205] A UE, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an loT device comprises circuitry and / or software in dependence of the intended application of the loT device in addition to other components as described in relation to the UE QQ200 shown in Figure 9.

[0206] As yet another specific example, in an loT scenario, a UE may represent a machine or other device that performs monitoring and / or measurements, and transmits the results of such monitoring and / or measurements to another UE and / or a network node 110, 130. The UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the UE may implement the 3GPP NB-loT standard. In other scenarios, a UE may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.

[0207] In practice, any number of UEs may be used together with respect to a single use case. For example, a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE may adjust the throttle on the drone, e.g., by controlling an actuator) to increase or decrease the drone’s speed. The first and / or the second UE can also include more than one of the functionalities described above. For example, a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.

[0208] Figure 10 shows a network node 110, 130 QQ300 in accordance with some embodiments. As used herein, network node 110, 130 refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network node 110, 130s or equipment, in a telecommunication network. Examples of network node 110, 130s include, but are not limited to, access points (APs), e.g.,, radio access points), base stations (BSs), e.g.,, radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)), O-RAN nodes or components of an O- RAN node, e.g.,, O-RU, O-DU, O-CU).

[0209] Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node 110, 130 may also include one or more (or all) parts of a distributed radio base station such as centralized digital units, distributed units, e.g.,, in an O-RAN access node) and / or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).

[0210] Other examples of network node 110, 130s include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi- cell / multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes, e.g.,, Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs).

[0211] The network node 110, 130 QQ300 includes a processing circuitry QQ302, a memory QQ304, a communication interface QQ306, and a power source QQ308. The network node 110, 130 QQ300 may be composed of multiple physically separate components, e.g.,, a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node 110, 130 QQ300 comprises multiple separate components, e.g.,, BTS and BSC components), one or more of the separate components may be shared among several network node 110, 130s. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node 110, 130. In some embodiments, the network node 110, 130 QQ300 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated, e.g.,, separate memory QQ304 for different RATs) and some components may be reused, e.g.,, a same antenna QQ310 may be shared by different RATs). The network node 110, 130 QQ300 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 110, 130 QQ300, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 110, 130 QQ300.

[0212] The processing circuitry QQ302 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic operable to provide, either alone or in conjunction with other network node 110, 130 QQ300 components, such as the memory QQ304, to provide network node 110, 130 QQ300 functionality.

[0213] In some embodiments, the processing circuitry QQ302 includes a system on a chip (SOC). In some embodiments, the processing circuitry QQ302 includes one or more of radio frequency (RF) transceiver circuitry QQ312 and baseband processing circuitry QQ314. In some embodiments, the radio frequency (RF) transceiver circuitry QQ312 and the baseband processing circuitry QQ314 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry QQ312 and baseband processing circuitry QQ314 may be on the same chip or set of chips, boards, or units.

[0214] The memory QQ304 may comprise any form of volatile or non-volatile computer- readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non-transitory device- readable and / or computer-executable memory devices that store information, data, and / or instructions that may be used by the processing circuitry QQ302. The memory QQ304 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and / or other instructions capable of being executed by the processing circuitry QQ302 and utilized by the network node 110, 130 QQ300. The memory QQ304 may be used to store any calculations made by the processing circuitry QQ302 and / or any data received via the communication interface QQ306. In some embodiments, the processing circuitry QQ302 and memory QQ304 is integrated.

[0215] The communication interface QQ306 is used in wired or wireless communication of signaling and / or data between a network node 110, 130, access network, and / or UE. As illustrated, the communication interface QQ306 comprises port(s) / terminal(s) QQ316 to send and receive data, for example to and from a network over a wired connection. The communication interface QQ306 also includes radio front-end circuitry QQ318 that may be coupled to, or in certain embodiments a part of, the antenna QQ310. Radio front-end circuitry QQ318 comprises filters QQ320 and amplifiers QQ322. The radio front-end circuitry QQ318 may be connected to an antenna QQ310 and processing circuitry QQ302. The radio front-end circuitry may be configured to condition signals communicated between antenna QQ310 and processing circuitry QQ302. The radio front-end circuitry QQ318 may receive digital data that is to be sent out to other network node 110, 130s or UEs via a wireless connection. The radio front-end circuitry QQ318 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters QQ320 and / or amplifiers QQ322. The radio signal may then be transmitted via the antenna QQ310. Similarly, when receiving data, the antenna QQ310 may collect radio signals which are then converted into digital data by the radio front-end circuitry QQ318. The digital data may be passed to the processing circuitry QQ302. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0216] In certain alternative embodiments, the network node 110, 130 QQ300 does not include separate radio front-end circuitry QQ318, instead, the processing circuitry QQ302 includes radio front-end circuitry and is connected to the antenna QQ310. Similarly, in some embodiments, all or some of the RF transceiver circuitry QQ312 is part of the communication interface QQ306. In still other embodiments, the communication interface QQ306 includes one or more ports or terminals QQ316, the radio front-end circuitry QQ318, and the RF transceiver circuitry QQ312, as part of a radio unit (not shown), and the communication interface QQ306 communicates with the baseband processing circuitry QQ314, which is part of a digital unit (not shown).

[0217] The antenna QQ310 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna QQ310 may be coupled to the radio front-end circuitry QQ318 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna QQ310 is separate from the network node 110, 130 QQ300 and connectable to the network node 110, 130 QQ300 through an interface or port.

[0218] The antenna QQ310, communication interface QQ306, and / or the processing circuitry QQ302 may be configured to perform any receiving operations and / or certain obtaining operations described herein as being performed by the network node 110, 130. Any information, data and / or signals may be received from a UE, another network node 110, 130 and / or any other network equipment. Similarly, the antenna QQ310, the communication interface QQ306, and / or the processing circuitry QQ302 may be configured to perform any transmitting operations described herein as being performed by the network node 110, 130. Any information, data and / or signals may be transmitted to a UE, another network node 110, 130 and / or any other network equipment.

[0219] The power source QQ308 provides power to the various components of network node 110, 130 QQ300 in a form suitable for the respective components, e.g.,, at a voltage and current level needed for each respective component). The power source QQ308 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 110, 130 QQ300 with power for performing the functionality described herein. For example, the network node 110, 130 QQ300 may be connectable to an external power source, e.g.,, the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source QQ308. As a further example, the power source QQ308 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.

[0220] Embodiments of the network node 110, 130 QQ300 may include additional components beyond those shown in Figure 10 for providing certain aspects of the network node 110, 130’s functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node 110, 130 QQ300 may include user interface equipment to allow input of information into the network node 110, 130 QQ300 and to allow output of information from the network node 110, 130 QQ300. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 110, 130 QQ300.

[0221] Figure 11 is a block diagram of a host QQ400, which may be an embodiment of the host QQ116 of Figure 8, in accordance with various aspects described herein. As used herein, the host QQ400 may be or comprise various combinations hardware and / or software, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm. The host QQ400 may provide one or more services to one or more UEs.

[0222] The host QQ400 includes processing circuitry QQ402 that is operatively coupled via a bus QQ404 to an input / output interface QQ406, a network interface QQ408, a power source QQ410, and a memory QQ412. Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as Figures QQ2 and QQ3, such that the descriptions thereof are generally applicable to the corresponding components of host QQ400.

[0223] The memory QQ412 may include one or more computer programs including one or more host application programs QQ414 and data QQ416, which may include user data, e.g., data generated by a UE for the host QQ400 or data generated by the host QQ400 for a UE. Embodiments of the host QQ400 may utilize only a subset or all of the components shown. The host application programs QQ414 may be implemented in a container-based architecture and may provide support for video codecs, e.g.,, Versatile Video Coding (WC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs, e.g.,, FLAC, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs, e.g.,, handsets, desktop computers, wearable display systems, heads-up display systems). The host application programs QQ414 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network. Accordingly, the host QQ400 may select and / or indicate a different host for over-the-top services for a UE. The host application programs QQ414 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time

[0224] Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc.

[0225] Figure 12 is a block diagram illustrating a virtualization environment QQ500 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments QQ500 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node 110, 130, UE, core network node 110, 130, or host. Further, in embodiments in which the virtual node does not require radio connectivity, e.g.,, a core network node 110, 130 or host), then the node may be entirely virtualized. In some embodiments, the virtualization environment QQ500 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an O-2 interface.

[0226] Applications QQ502 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q400 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.

[0227] Hardware QQ504 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, input / output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers QQ506 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs QQ508a and QQ508b (one or more of which may be generally referred to as VMs QQ508), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer QQ506 may present a virtual operating platform that appears like networking hardware to the VMs QQ508.

[0228] The VMs QQ508 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer QQ506. Different embodiments of the instance of a virtual appliance QQ502 may be implemented on one or more of VMs QQ508, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

[0229] In the context of NFV, a VM QQ508 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs QQ508, and that part of hardware QQ504 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs QQ508 on top of the hardware QQ504 and corresponds to the application QQ502.

[0230] Hardware QQ504 may be implemented in a standalone network node 110, 130 with generic or specific components. Hardware QQ504 may implement some functions via virtualization. Alternatively, hardware QQ504 may be part of a larger cluster of hardware, e.g., such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration QQ510, which, among others, oversees lifecycle management of applications QQ502. In some embodiments, hardware QQ504 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system QQ512 which may alternatively be used for communication between hardware nodes and radio units.

[0231] Figure 13 shows a communication diagram of a host QQ602 communicating via a network node 110, 130 QQ604 with a UE QQ606 over a partially wireless connection in accordance with some embodiments. Example implementations, in accordance with various embodiments, of the UE (such as a UE QQ112a of Figure 8 and / or UE QQ200 of Figure 9), network node 110, 130 (such as network node 110, 130 QQ110a of Figure 8 and / or network node 110, 130 QQ300 of Figure 10), and host (such as host QQ116 of Figure 8 and / or host QQ400 of Figure 11) discussed in the preceding paragraphs will now be described with reference to Figure 13.

[0232] Like host QQ400, embodiments of host QQ602 include hardware, such as a communication interface, processing circuitry, and memory. The host QQ602 also includes software, which is stored in or accessible by the host QQ602 and executable by the processing circuitry. The software includes a host application that may be operable to provide a service to a remote user, such as the UE QQ606 connecting via an over-the-top (OTT) connection QQ650 extending between the UE QQ606 and host QQ602. In providing the service to the remote user, a host application may provide user data which is transmitted using the OTT connection QQ650.

[0233] The network node 110, 130 QQ604 includes hardware enabling it to communicate with the host QQ602 and UE QQ606. The connection QQ660 may be direct or pass through a core network (like core network QQ106 of Figure 8) and / or one or more other intermediate networks, such as one or more public, private, or hosted networks. For example, an intermediate network may be a backbone network or the Internet.

[0234] The UE QQ606 includes hardware and software, which is stored in or accessible by UE QQ606 and executable by the UE’s processing circuitry. The software includes a client application, such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE QQ606 with the support of the host QQ602. In the host QQ602, an executing host application may communicate with the executing client application via the OTT connection QQ650 terminating at the UE QQ606 and host QQ602. In providing the service to the user, the UE's client application may receive request data from the host's host application and provide user data in response to the request data. The OTT connection QQ650 may transfer both the request data and the user data. The UE's client application may interact with the user to generate the user data that it provides to the host application through the OTT connection QQ650.

[0235] The OTT connection QQ650 may extend via a connection QQ660 between the host QQ602 and the network node 110, 130 QQ604 and via a wireless connection QQ670 between the network node 110, 130 QQ604 and the UE QQ606 to provide the connection between the host QQ602 and the UE QQ606. The connection QQ660 and wireless connection QQ670, over which the OTT connection QQ650 may be provided, have been drawn abstractly to illustrate the communication between the host QQ602 and the UE QQ606 via the network node 110, 130 QQ604, without explicit reference to any intermediary devices and the precise routing of messages via these devices. As an example of transmitting data via the OTT connection QQ650, in step QQ608, the host QQ602 provides user data, which may be performed by executing a host application. In some embodiments, the user data is associated with a particular human user interacting with the UE QQ606. In other embodiments, the user data is associated with a UE QQ606 that shares data with the host QQ602 without explicit human interaction. In step QQ610, the host QQ602 initiates a transmission carrying the user data towards the UE QQ606. The host QQ602 may initiate the transmission responsive to a request transmitted by the UE QQ606. The request may be caused by human interaction with the UE QQ606 or by operation of the client application executing on the UE QQ606. The transmission may pass via the network node 110, 130 QQ604, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step QQ612, the network node 110, 130 QQ604 transmits to the UE QQ606 the user data that was carried in the transmission that the host QQ602 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step QQ614, the UE QQ606 receives the user data carried in the transmission, which may be performed by a client application executed on the UE QQ606 associated with the host application executed by the host QQ602.

[0236] In some examples, the UE QQ606 executes a client application which provides user data to the host QQ602. The user data may be provided in reaction or response to the data received from the host QQ602. Accordingly, in step QQ616, the UE QQ606 may provide user data, which may be performed by executing the client application. In providing the user data, the client application may further consider user input received from the user via an input / output interface of the UE QQ606. Regardless of the specific manner in which the user data was provided, the UE QQ606 initiates, in step QQ618, transmission of the user data towards the host QQ602 via the network node 110, 130 QQ604. In step QQ620, in accordance with the teachings of the embodiments described throughout this disclosure, the network node 110, 130 QQ604 receives user data from the UE QQ606 and initiates transmission of the received user data towards the host QQ602. In step QQ622, the host QQ602 receives the user data carried in the transmission initiated by the UE QQ606.

[0237] One or more of the various embodiments improve the performance of OTT services provided to the UE QQ606 using the OTT connection QQ650, in which the wireless connection QQ670 forms the last segment. More precisely, the teachings of these embodiments may improve the latency and thereby provide benefits such as reduced user waiting time. In an example scenario, factory status information may be collected and analyzed by the host QQ602. As another example, the host QQ602 may process audio and video data which may have been retrieved from a UE for use in creating maps. As another example, the host QQ602 may collect and analyze real-time data to assist in controlling vehicle congestion, e.g.,, controlling traffic lights). As another example, the host QQ602 may store surveillance video uploaded by a UE. As another example, the host QQ602 may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs. As other examples, the host QQ602 may be used for energy pricing, remote control of non-time critical electrical load to balance power generation needs, location services, presentation services (such as compiling diagrams etc. from data collected from remote devices), or any other function of collecting, retrieving, storing, analyzing and / or transmitting data.

[0238] In some examples, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection QQ650 between the host QQ602 and UE QQ606, in response to variations in the measurement results. The measurement procedure and / or the network functionality for reconfiguring the OTT connection may be implemented in software and hardware of the host QQ602 and / or UE QQ606. In some embodiments, sensors (not shown) may be deployed in or in association with other devices through which the OTT connection QQ650 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software may compute or estimate the monitored quantities. The reconfiguring of the OTT connection QQ650 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node 110, 130 QQ604. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency and the like, by the host QQ602. The measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection QQ650 while monitoring propagation times, errors, etc.

[0239] Although the computing devices described herein, e.g.,, UEs, network node 110, 130s, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and / or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node 110, 130, and / or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non- computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.

[0240] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer-readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and / or by end users and a wireless network generally.

[0241] When using the word "comprise" or “comprising” it shall be interpreted as nonlimiting, i.e. meaning "consist at least of'.

[0242] The embodiments herein are not limited to the preferred embodiments described above. Various alternatives, modifications and equivalents may be used.

Claims

CLAIMS1 . A method performed by a network node (110, 130) for controlling a mobile Base Station, mBS, (110) in a wireless communications network (100), the method comprising: obtaining (201) a User Equipment, UE, Mobility Profile, UMP, of respective one or more UEs (121 , 122, 123) served or expected to be served by the mBS (110) in a first region, R1 , obtaining (202) a UE Operational Status, UOS, of the respective one or more UEs (121 , 122, 123)) wherein the respective UOS comprises one or more of a UE radio access status and a target quality of service, and determining (204) a mBS Operational Profile, MOP, of the mBS (110) based on the obtained UMP and the UOS, wherein the MOP comprises a second region, R2, and a mBS Mobility Profile, MMP, which MMP will be used by the mBS (110) for operating in R2, and which MOP will be used by the mBS (110) for performing one or more operational tasks in R2 for serving the at least one out of the one or more UEs (121 , 122, 123)..

2. The method according to claim 1 , further comprising: determining (203) R2 based on the obtained UMP and the UOS.

3. The method according to any of the claims 1-2, wherein any one out of: the network node (110, 130) is represented by the mBS (110), the network node (110, 130) is represented by a control node (130).

4. The method according to any of the claims 1-3, wherein the network node (110, 130) is represented by a control node (130), the method further comprising: sending (205) to the mBS (110), information related to the MOP, which MOP comprises information about the R2 and the MMP, which MMP will be used by the mBS (110) for operating in R2, and which MOP will be used by the mBS (110) for performing one or more operational tasks in R2 for serving the one or more UEs (121 , 122, 123).

5. The method according to any of the claims 1-3, wherein the network node (110, 130) is represented by the mBS (110), the method further comprising:operating (206) in R2 for serving the one or more UEs (121 , 122, 123) according to the MMP, and performing (207) the one or more operational tasks in R2 according to the determined MOP.

6. The method according to any of the claims 1-5, wherein the respective UMP of the one or more UEs (121 , 122, 123) comprises one or more out of: a UE speed, a UE direction of motion, a UE acceleration, a UE trajectory, and a UE location.

7. The method according to any of the claims 1-6, wherein the respective UE radio access status comprises any one or more out of: a transmit power, a receive antenna status, a transmit antenna status, and a bandwidth.

8. The method according to any of the claims 1-7, wherein the respective target quality of service comprises any one or more out of: UE bit rate, Block Error Rate, BLER, delay sensitivity, and round trip delay and packet transmission delay.

9. The method according to any of the claims 1-8, wherein the determining (204) of the MOP of the mBS (110) is performed when one or more of the following conditions are met: according to a periodicity, after a duration over which the determined MOP is valid, when the UOS of the one or more UEs (121 , 122, 123) is changed, when a number of the one or more UEs (121 , 122, 123) and / or other UEs served by the mBS (110) is changed change by a certain threshold, and upon receiving a message from the mBS (110) requesting to receive its MOP.

10. The method according to any of the claims 1-9, wherein the one or more operational tasks in R2 for serving the one or more UEs (121 , 122, 123) comprises serving the at least one out of the one or more UEs (121 , 122, 123) in R2.11 . A computer program (630) comprising instructions, which when executed by a processor (610), causes the processor (610) to perform actions according to any of the claims 1-10.

12. A carrier (640) comprising the computer program (630) of claim 11 , wherein the carrier (640) is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer-readable storage medium.

13. A method performed by a mobile Base Station, mBS, (110) in a wireless communications network (100), which mBS (110) is serving one or more UEs (121 , 122, 123) in a first region, R1 , the method comprising: receiving (302) from a network node 110, 130 (130), a mBS Operational Profile, MOP, for the mBS (110), which MOP is based on a UE Mobility Profile, UMP, and a UE Operational Status, UOS, of the respective one or more UEs (121 , 122, 123), and which MOP comprises a second region, R2, and a mBS Mobility Profile, MMP, operating (303) in R2 according to the MMP, for serving at least one out of the one or more UEs (121 , 122, 123) and performing (304) the one or more operational tasks in R2 according to the received MOP.

14. The method according to claim 13, wherein the one or more UEs (121 , 122, 123) are assigned a respective UE Mobility Profile, UMP, and a respective UE Operational Status, UOS, wherein the respective UOS comprises one or more of a UE radio access status and a target quality of service.

15. The method according to any of the claims 13-14, wherein the one or more operational tasks in R2 comprises serving the one or more UEs (121 , 122, 123) in R2.

16. The method according to any of the claims 13-15, further comprising: sending (301) a request to the network node 110, 130 (130), requesting to receive the MOP for the mBS (110) for performing the one or more operational tasks in R2.

17. The method according to any of the claims 13-16, wherein the respective UMP of the one or more UEs (121 , 122, 123) comprises one or more out of a UE speed, a UE direction of motion, a UE acceleration, a UE trajectory, and a UE location.

18. The method according to any of the claims 13-17, wherein the respective UE radio access status comprises any one or more out of a transmit power, a receive antenna status, a transmit antenna status, and a bandwidth.

19. The method according to any of the claims 13-18, wherein the respective target quality of service comprises any one or more out of: UE bit rate, Block Error Rate, BLER, delay sensitivity, round trip delay, and packet transmission delay.

20. The method according to any of the claims 13-19, wherein the network node (110, 130) is represented by a control node (130).21 . A computer program (730) comprising instructions, which when executed by a processor (710), causes the processor (710) to perform actions according to any of the claims 13-2022. A carrier (740) comprising the computer program (730) of claim 21 , wherein the carrier (740) is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer-readable storage medium.

23. A network node (110, 130) configured to control a mobile Base Station, mBS, (110) in a wireless communications network (100), the network node (110, 130) further configured to: obtain a User Equipment, UE, Mobility Profile, UMP, of respective one or more UEs (121 , 122, 123) to be served or expected to be served by the mBS (110) in a first region, R1 , obtain a UE Operational Status, UOS, of the respective one or more UEs (121 , 122, 123), wherein the respective UOS is adapted to comprise one or more of a UE radio access status and a target quality of service, and determine an mBS Operational Profile, MOP, of the mBS (110) based on the obtained UMP and the UOS, wherein the MOP is adapted to comprise a second region, R2, and an mBS Mobility Profile, MMP,which MMP is adapted to be used by the mBS (110) for operating in R2, and which MOP is adapted to be used by the mBS (110) for performing one or more operational tasks in R2 for serving the at least one out of the one or more UEs (121 , 122, 123).

24. The network node (110, 130) according to claim 23, further configured to: determine R2 based on the obtained UMP and the UOS.

25. The network node (110, 130) according to any of the claims 23-24, wherein any one out of: the network node (110, 130) is represented by the mBS (110), the network node (110, 130) is represented by a control node (130).

26. The network node (110, 130) according to any of the claims 23-25, wherein the network node (110, 130) is represented by a control node (130), the network node (110, 130) is further configured to: send to the mBS (110), information related to the MOP, which MOP is adapted to comprise information about the R2 and the MMP, which MMP is adapted to be used by the mBS (110) for operating in R2, and which MOP is adapted to be used by the mBS (110) for performing one or more operational tasks in R2 for serving the one or more UEs (121 , 122, 123).

27. The network node (110, 130) according to any of the claims 23-25, wherein the network node (110, 130) is represented by the mBS (110), the network node (110, 130) is further configured to: operate in R2 for serving the one or more UEs (121 , 122, 123) according to the MMP, and perform the one or more operational tasks in R2 according to the determined MOP.

28. The network node (110, 130) according to any of the claims 23-27, wherein the respective UMP of the one or more UEs (121 , 122, 123) is adapted to comprise one or more out of: a UE speed, a UE direction of motion, a UE acceleration, a UE trajectory, and a UE location.

29. The network node (110, 130) according to any of the claims 23-28, wherein the respective UE radio access status is adapted to comprise any one or more out of: a transmit power, a receive antenna status, a transmit antenna status, and a bandwidth.

30. The network node (110, 130) according to any of the claims 23-29, wherein the respective target quality of service is adapted to comprise any one or more out of: UE bit rate, Block Error Rate, BLER, delay sensitivity, and round trip delay and packet transmission delay.

31. The network node (110, 130) according to any of the claims 23-30, further being configured to determine the MOP of the mBS (110) when one or more of the following conditions are met: according to a periodicity, after a duration over which the determined MOP is valid, when the UOS of the one or more UEs (121 , 122, 123) is changed, when a number of the one or more UEs (121 , 122, 123) and / or other UEs served by the mBS (110) is changed by a certain threshold; and upon receiving a message from the mBS (110) requesting to receive its MOP.

32. The network node (110, 130) according to any of the claims 23-31 , wherein the one or more operational tasks in R2 for serving the one or more UEs (121 , 122, 123) is adapted to comprise serving the at least one out of the one or more UEs (121 , 122, 123) in R2.

33. A mobile Base Station, mBS, (110) in a wireless communications network (100), which mBS (110) is configured to serve one or more UEs (121 , 122, 123) in a first region, R1 , the mBS (110) further being configured to: receive from a network node 110, 130 (130), a mBS Operational Profile, MOP, for the mBS (110), which MOP is adapted to be based on a UE Mobility Profile, UMP, and a UE Operational Status, UOS, of the respective one or more UEs (121 , 122, 123), and which MOP is adapted to comprise a second region, R2, and a mBS Mobility Profile, MMP, operate in R2 according to the MMP, for serving at least one out of the one or more UEs (121 , 122, 123) andperform the one or more operational tasks in R2 according to the received MOP.

34. The mBS (110) according to claim 33, wherein the one or more UEs (121 , 122, 123) are adapted to be assigned a respective UE Mobility Profile, UMP, and a respective UE Operational Status, UOS, wherein the respective UOS is adapted to comprise one or more of a UE radio access status and a target quality of service.

35. The mBS (110) according to any of the claims 33-34, wherein the one or more operational tasks in R2 is adapted to comprise: serving the one or more UEs (121 , 122, 123) in R2.

36. The mBS (110) according to any of the claims 33-35, further being configured to: send a request to the network node 110, 130 (130), requesting to receive the MOP for the mBS (110) for performing the one or more operational tasks in R2.

37. The mBS (110) according to any of the claims 33-36, wherein the respective UMP of the one or more UEs (121 , 122, 123) is adapted to comprise one or more out of a UE speed, a UE direction of motion, a UE acceleration, a UE trajectory, and a UE location.

38. The mBS (110) according to any of the claims 33-37, wherein the respective UE radio access status is adapted to comprise any one or more out of a transmit power, a receive antenna status, a transmit antenna status, and a bandwidth.

39. The mBS (110) according to any of the claims 33-38, wherein the respective target quality of service is adapted to comprise any one or more out of: UE bit rate, Block Error Rate, BLER, delay sensitivity, round trip delay, and packet transmission delay.

40. The mBS (110) according to any of the claims 33-39, wherein the network node (110, 130) is represented by a control node (130).

Images