WO2021204398A1

WO2021204398A1 - Load balancing in musim devices

Info

Publication number: WO2021204398A1
Application number: PCT/EP2020/060238
Authority: WO
Inventors: Nuno Manuel KIILERICH PRATAS; Faranaz SABOURI-SICHANI; Knud Knudsen
Original assignee: Nokia Technologies Oy
Priority date: 2020-04-09
Filing date: 2020-04-09
Publication date: 2021-10-14

Abstract

There is provided a method, comprising the steps of providing for a load balancing between a first access point and a second access point associated with a respective first network and second network, based on establishing a mutual acceptance between the first access point and the second access point to conditionally handle a partitioning of a load to be handled by the first access point.

Description

LOAD BALANCING IN MUSIM DEVICES

DESCRIPTION

FIELD

The present disclosure relates to network load balancing utilizing MUSIM devices.

Examples of embodiments relate to apparatuses, methods and computer program products relating to network load balancing utilizing MUSIM devices.

BACKGROUND

Multi universal subscriber identity module (MUSIM) devices are widely available in the market, especially in enhanced Mobile Broad Band (eMBB) section. These devices can (silently) cause degrade toward the network when they have to share some resources at a user equipment (UE), hence, multiplexing support of services across two networks. However, they have to maintain two subscriptions with best possible user experience despite some performance compromises. In this regard, there has been an ongoing study ([1], [2]) on Service and System Aspects (SA) of support for MUSIM devices mainly in, but not limited to, 5G New Radio (NR) and Long Term Evolution (LTE).

Thus, there is a need to provide a solution to these problems/drawbacks.

Efficiently solving at least part these problems and drawbacks is essential for improving performance and for utilizing the advantages provided by MUSIM devices more efficiently.

REFERENCES

[1 ] SP-190248, “Study on system enablers for multi-USIM devices (FS_MUSIM)",

3GPP Work Item Description approved in TSG SA meeting #SP-83, March 2019.

[2] RP-193263, “ Support for Multi-SIM devices in Rei-1T, 3GPP Work Item

Description presented TSG RAN meeting #86, December 2019. The following meanings for the abbreviations used in this specification apply:

2G Second Generation

3G Third Generation

3GPP 3rd Generation Partnership Project

3GPP2 3rd Generation Partnership Project 2

4G Fourth Generation

5G Fifth Generation

AP Access Point

BS Base Station

C-RNTI Cell Radio Network Temporary Identifier

DAI Downlink Assignment Indicator

DCI Downlink Control Information

DSDA Dual SIM Dual Standby

DSDS Dual SIM Dual Active

DSL Digital Subscriber Line

EDGE Enhanced Data Rates for Global Evolution eNB Evolved Node B

ETSI European Telecommunications Standards Institute

GPRS General Packet Radio System gNB gNodeB

GSM Global System for Mobile communications

HARQ Hybrid Automated Repeat Request

IEEE Institute of Electrical and Electronics Engineers

IETF Internet Engineering Task Force

IMSI International Mobile Subscriber Identity

IMU Inertial Measurement Units

ISDN Integrated Services Digital Network

ITU International Telecommunication Union

LSTM Long Short-Term Memory

LTE Long Term Evolution

LTE-A Long Term Evolution-Advanced

MANETs Mobile Ad-Hoc Networks

MCS Modulation and Coding Scheme

MNO Mobile Network Operator MVNO Mobile Virtual Network Operator

MR-DC Multi-RAT Dual-Connectivity

Multi-RAT Multi-Radio Access Technology

MUMA Multi USIM Multi Active

MUMS Multi USIM Multi Standby

MUSIM Multi Universal Subscriber Identity Module

NR New Radio

NB NodeB

PCS Personal Communications Services

PDCCH Physical Downlink Control Channel

PDSCH Physical Downlink Shared Channel

PLMN Public Land Mobile Network

PRB Physical Resource Block

PUCCH Physical Uplink Control Channel

PUSCH Physical Uplink Shared Channel

RAN Radio Access Network

RANSAC Random Sample Consensus

RRC Radio Resource Control

SIB System Information Block

TB Transport Block

TISPAN Telecoms & Internet converged Services & Protocols for Advanced Networks

TPC Transmit Power Control

UE User Equipment

UL/SUL Uplink/Supplementary Uplink

UMTS Universal Mobile Telecommunications System

UWB Ultra- Wideband

VOLTE Voice-over-LTE

VRB Virtual Resource Block

WCDMA Wdeband Code Division Multiple Access

WMAX Worldwide Interoperability for Microwave Access

WLAN Wreless Local Area Network

SUMMARY Various exemplary embodiments of the present disclosure aim at addressing at least part of the above issues and/or problems and drawbacks.

Various aspects of exemplary embodiments of the present disclosure are set out in the appended claims.

According to an example of an embodiment, there is provided, for example, a method according to claim 1.

In addition, according to an example of an embodiment, there is provided, for example, an apparatus according to claim 26.

According to further refinements, these examples may include one or more of the features according to claims 2 to 10 and 27 to 35..

Furthermore, according to an example of an embodiment, there is provided, for example, a method according to claim 11.

In addition, according to an example of an embodiment, there is provided, for example, an apparatus according to claim 36.

According to further refinements, these examples may include one or more of the features according to claims 12 to 21 and 37 to 46.

Furthermore, according to an example of an embodiment, there is provided, for example, a method according to claim 22.

In addition, according to an example of an embodiment, there is provided, for example, an apparatus according to claim 47.

According to further refinements, these examples may include one or more of the features according to claims 23 to 25 and 48 to 50..

In addition, according to embodiments, there is provided, for example, a computer program product for a computer, including software code portions for performing the steps of the above defined methods, when said product is run on the computer. The computer program product may include a computer-readable medium on which said software code portions are stored. Furthermore, the computer program product may be directly loadable into the internal memory of the computer and/or transmittable via a network by means of at least one of upload, download and push procedures.

Any one of the above aspects enables to solve at least part of the problems and drawbacks present in relation to the prior art regarding the improvement of performance and the utilization of the advantages of MUSIM devices more efficiently.

Thus, improvement is achieved by apparatuses, methods, and computer program products enabling network load balancing by utilizing MUSIM devices.

Specifically, one advantage of the proposed solution is that a network provider can still support its subscribers with their requested services while a provider with less amount of subscriber, hence, free capacity can deliver its extra capacity to another provider (an “indirect subscriber”).

BRIEF DESCRIPTION OF THE DRAWINGS

Some embodiments of the present disclosure are described below, by way of example only, with reference to the accompanying drawings, in which:

Figs. 1a and 1b show MSIM with SIMs belonging to same MNO and different MNOs, respectively;

Fig. 2 shows a flow chart illustrating steps corresponding to a method according to examples of embodiments;

Fig. 3 shows a flow chart illustrating steps corresponding to a method according to examples of embodiments;

Fig. 4 shows a flow chart illustrating steps corresponding to a method according to examples of embodiments; Fig. 5 shows a block diagram illustrating an apparatus according to examples of embodiments;

Fig. 6 shows a block diagram illustrating an apparatus according to examples of embodiments;

Fig. 7 shows a block diagram illustrating an apparatus according to examples of embodiments;

Fig. 8 shows general phases of the proposed inter-operator load balancing operation according to examples of embodiments;

Fig. 9 shows a flexible inter-operator load balancing for UL transmissions according to examples of embodiments; and

Fig. 10 shows a flexible inter-operator load balancing for DL transmissionsaccording to examples of embodiments.

DESCRIPTION OF EMBODIMENTS

In the last years, an increasing extension of communication networks, e.g. of wire based communication networks, such as the Integrated Services Digital Network (ISDN), Digital Subscriber Line (DSL), or wireless communication networks, such as the cdma2000 (code division multiple access) system, cellular 3rd generation (3G) like the Universal Mobile Telecommunications System (UMTS), fourth generation (4G) communication networks or enhanced communication networks based e.g. on Long Term Evolution (LTE) or Long Term Evolution-Advanced (LTE-A), fifth generation (5G) communication networks, cellular 2nd generation (2G) communication networks like the Global System for Mobile communications (GSM), the General Packet Radio System (GPRS), the Enhanced Data Rates for Global Evolution (EDGE), or other wireless communication system, such as the Wireless Local Area Network (WLAN), Bluetooth or Worldwide Interoperability for Microwave Access (WiMAX), took place all over the world. Various organizations, such as the European Telecommunications Standards Institute (ETSI), the 3rd Generation Partnership Project (3GPP), Telecoms & Internet converged Services & Protocols for Advanced Networks (TISPAN), the International Telecommunication Union (ITU), 3rd Generation Partnership Project 2 (3GPP2), Internet Engineering Task Force (IETF), the IEEE (Institute of Electrical and Electronics Engineers), the WiMAX Forum and the like are working on standards or specifications for telecommunication network and access environments.

Basically, for properly establishing and handling a communication between two or more end points (e.g. communication stations or elements or functions, such as terminal devices, user equipments (UEs), or other communication network elements, a database, a server, host etc.), one or more network elements or functions (e.g. virtualized network functions), such as communication network control elements or functions, for example access network elements like access points, radio base stations, relay stations, eNBs, gNBs etc., and core network elements or functions, for example control nodes, support nodes, service nodes, gateways, user plane functions, access and mobility functions etc., may be involved, which may belong to one communication network system or different communication network systems.

In view of different types of communication, the present specification is in the context of support for multi Universal Subscriber Identity Module (multi-USIM) devices mainly in 5G New Radio (NR) and Long Term Evolution (LTE).

A multi-USIM device has two (Dual) or more (Multiple) simultaneous 3GPP/3GPP2 network subscriptions with multiple corresponding International Mobile Subscriber Identities (IMSI) each associated with a particular USIM belonging to the same or different Mobile Network Operator (MNO (/Mobile Virtual Network Operator (MVNO)). A MUSIM device connected to one or more NBs with independent subscriptions is shown in Figures 1a and 1b. In a first case, as illustrated in Figure 1a, the two USIMs belong to the same MNO/MVNO, registered with two independent ID’s (ID_a and ID_b) at the core network and, may be using the same cell or two neighbour cells as serving cell (as indicated by the solid lined arrows RNTI (ID_a) and RNTI (ID_b) between the MUSIM device 100 and the gNB 10 and the solid lined arrow RNTI (ID_b) between the MUSIM device 100 and the gNB 10 and the dashed lined arrow RNTI (ID_a), between the MUSIM device 100 and the gNB 20, respectively). In a second case, as illustrated in Figure 1b, the two USIMs (of the MUSIM device 100) belong to different MNOs (ID_a corresponding to a EPC-2/5GC-2 and ID_b corresponding to EPC-1/5GC-1) and may be using two neighbouring or co-located cells from each MNO as serving cell (e.g. RNTI (ID_a) corresponding to a gNB 50 associated with the shaded cells and RNTI (ID_b) corresponding to a gNB 60 associated with the blank cells). In Figure 1b, the gNBs 30 and 50 and the gNBs 40 and 60 are associated with different MNOs, respectively.

Two main types of MUSIM devices are normally referred to, depending on the supported simultaneous Radio Resource Control-states (RRC-states) on the USIMs. A first type, Dual SIM Dual Standby (DSDS) or Multi USIM Multi Standby (MUMS) are MUSIM devices, which are registered with two or more independent subscriber IDs (USIMs) and can be in RRCJDLE mode on all USIMs. However, it can only be on RRC_CONNECTED mode with a single USIM at a given time. A second type, Dual SIM Dual Active or Multi USIM Multi Active (MUMA), are MUSIM devices, which are registered with two or more independent subscriber IDs (USIMs) and can be in RRCJDLE mode on all USIMs. Further, the device can maintain RRC_CONNECTED mode activities on all USIMs.

Furthermore, the UE’s behaviour with respect to the simultaneous handling of multiple USIMs may depend on the UE’s Hardware and Software capabilities as listed below:

Regarding SingleRx / SingleTx, the UE is only capable of receiving traffic from one network and and/or transmitting traffic to one network at a time. Regarding DualRx / SingleTx, the UE is capable of simultaneously receiving traffic from two networks but is capable of transmitting to only one network at a time. Regarding DualRx /DualTx, the UE is capable of simultaneously receiving and/or transmitting to/from two networks.

During normal network operation, it is expected that at some geographical locations not all operators will be experiencing a high load at the same time. When these high load events occur, it could be beneficial that the operators would be able to share their infrastructure/spectrum resources in order to improve the service experience for their users.

One case of interest is the one where a UE has multiple USIMs, where these USIMs belong each to a different operator. In the case where one operator (associated to at least one of the UE’s USIMs) is experiencing a high load, it would be beneficial for the UE to redirect its traffic to another operator (in case the UE has the associated USIM) that is experiencing a lower load.

The UE does not have information about the network load, but this approach could in principle be performed at the UE side (either via the user direct intervention or via an automatic “smart” radio interface selection at the UE), based on the UE being signaled about the congestion of the network load or based on the UE detecting no/low resource allocation. However, such procedure would involve more latency and be less dynamic as a procedure not being performed at the UE side and incoming Voice-over-LTE (VoLTE) could not be routed by the UE itself. Further, such procedure, in case many UEs are performing this kind of optimization, can cause a transient regime where a large number of UEs transition between networks.

There is therefore the need for a load balancing mechanism that allows for the different networks to control how the UEs’ traffic is offloaded between different networks.

In the following, different exemplifying embodiments will be described using, as an example of a communication network to which examples of embodiments may be applied, a communication network architecture based on 3GPP standards for a communication network, such as a 5G/NR, without restricting the embodiments to such an architecture, however. It is obvious for a person skilled in the art that the embodiments may also be applied to other kinds of communication networks where mobile communication principles are integrated, e.g. Wi-Fi, worldwide interoperability for microwave access (WiMAX), Bluetooth®, personal communications services (PCS), ZigBee®, wideband code division multiple access (WCDMA), systems using ultra- wideband (UWB) technology, mobile ad-hoc networks (MANETs), wired access, etc.. Furthermore, without loss of generality, the description of some examples of embodiments is related to a mobile communication network, but principles of the disclosure can be extended and applied to any other type of communication network, such as a wired communication network.

The following examples and embodiments are to be understood only as illustrative examples. Although the specification may refer to “an”, “one”, or “some” example(s) or embodiment(s) in several locations, this does not necessarily mean that each such reference is related to the same example(s) or embodiment(s), or that the feature only applies to a single example or embodiment. Single features of different embodiments may also be combined to provide other embodiments. Furthermore, terms like “comprising” and “including” should be understood as not limiting the described embodiments to consist of only those features that have been mentioned; such examples and embodiments may also contain features, structures, units, modules etc. that have not been specifically mentioned.

A basic system architecture of a (tele)communication network including a mobile communication system where some examples of embodiments are applicable may include an architecture of one or more communication networks including wireless access network subsystem(s) and core network(s). Such an architecture may include one or more communication network control elements or functions, access network elements, radio access network elements, access service network gateways or base transceiver stations, such as a base station (BS), an access point (AP), a NodeB (NB), an eNB or a gNB, a distributed or a centralized unit, which controls a respective coverage area or cell(s) and with which one or more communication stations such as communication elements or functions, like user devices or terminal devices, like a UE, or another device having a similar function, such as a modem chipset, a chip, a module etc., which can also be part of a station, an element, a function or an application capable of conducting a communication, such as a UE, an element or function usable in a machine-to-machine communication architecture, or attached as a separate element to such an element, function or application capable of conducting a communication, or the like, are capable to communicate via one or more channels via one or more communication beams for transmitting several types of data in a plurality of access domains. Furthermore, core network elements or network functions, such as gateway network elements/functions, mobility management entities, a mobile switching center, servers, databases and the like may be included.

The general functions and interconnections of the described elements and functions, which also depend on the actual network type, are known to those skilled in the art and described in corresponding specifications, so that a detailed description thereof is omitted herein. However, it is to be noted that several additional network elements and signaling links may be employed for a communication to or from an element, function or application, like a communication endpoint, a communication network control element, such as a server, a gateway, a radio network controller, and other elements of the same or other communication networks besides those described in detail herein below.

A communication network architecture as being considered in examples of embodiments may also be able to communicate with other networks, such as a public switched telephone network or the Internet. The communication network may also be able to support the usage of cloud services for virtual network elements or functions thereof, wherein it is to be noted that the virtual network part of the telecommunication network can also be provided by non-cloud resources, e.g. an internal network or the like. It should be appreciated that network elements of an access system, of a core network etc., and/or respective functionalities may be implemented by using any node, host, server, access node or entity etc. being suitable for such a usage. Generally, a network function can be implemented either as a network element on a dedicated hardware, as a software instance running on a dedicated hardware, or as a virtualized function instantiated on an appropriate platform, e.g., a cloud infrastructure.

Furthermore, a network element, such as communication elements, like a UE, a terminal device, control elements or functions, such as access network elements, like a base station (BS), an gNB, a radio network controller, a core network control element or function, such as a gateway element, or other network elements or functions, as described herein, and any other elements, functions or applications may be implemented by software, e.g. by a computer program product for a computer, and/or by hardware. For executing their respective processing, correspondingly used devices, nodes, functions or network elements may include several means, modules, units, components, etc. (not shown) which are required for control, processing and/or communication/signaling functionality. Such means, modules, units and components may include, for example, one or more processors or processor units including one or more processing portions for executing instructions and/or programs and/or for processing data, storage or memory units or means for storing instructions, programs and/or data, for serving as a work area of the processor or processing portion and the like (e.g. ROM, RAM, EEPROM, and the like), input or interface means for inputting data and instructions by software (e.g. floppy disc, CD-ROM, EEPROM, and the like), a user interface for providing monitor and manipulation possibilities to a user (e.g. a screen, a keyboard and the like), other interface or means for establishing links and/or connections under the control of the processor unit or portion (e.g. wired and wireless interface means, radio interface means including e.g. an antenna unit or the like, means for forming a radio communication part etc.) and the like, wherein respective means forming an interface, such as a radio communication part, can be also located on a remote site (e.g. a radio head or a radio station etc.). It is to be noted that in the present specification processing portions should not be only considered to represent physical portions of one or more processors, but may also be considered as a logical division of the referred processing tasks performed by one or more processors.

It should be appreciated that according to some examples, a so-called “liquid” or flexible network concept may be employed where the operations and functionalities of a network element, a network function, or of another entity of the network, may be performed in different entities or functions, such as in a node, host or server, in a flexible manner. In other words, a “division of labor” between involved network elements, functions or entities may vary case by case.

Referring now to Figure 2, there is shown a flow chart illustrating steps corresponding to a method according to examples of embodiments.

In particular, according to Figure 2, in S210, it is provided providing for a load balancing between a first access point and a second access point associated with a respective first network and second network, based on establishing a mutual acceptance between the first access point and the second access point to conditionally handle a partitioning of a load to be handled by the first access point. Further, in S220, a registration request from a terminal endpoint device indicating its capability of communicating via the first network and the second network is received. In addition, in S230, an occurrence of a condition to handle the partitioning of the load to be handled by the first access point is detected. Additionally, in S240, a reconfiguration of the terminal endpoint device is triggered, for instructing the terminal endpoint device to register to the second access point. Moreover, in S250, it is received from the terminal endpoint device, a registration confirmation indicating that the terminal endpoint device is registered to the second access point. Further, in S260, between the first access point and the second access point, load balancing information indicative of information to establish an inter-network load balancing operation between the first access point and the second access point with respect to the terminal endpoint device is exchanged. According to various examples of embodiments, the first point of time may be equal to the second point of time.

Optionally, according to at least some examples of embodiments, the mutual acceptance is provided permanently or temporarily.

Furthermore, according to at least some examples of embodiments, the detecting may further comprise that the condition to handle the partitioning of the load to be handled by the first access point is at least one of exceedance of a load prevailing at the first access point over a predetermined load threshold value, exceedance of a number of terminal endpoint devices including the terminal endpoint device being served by the first access point over a predetermined number threshold value, and occurrence of a predetermined temporal event, lasting from a first point of time to a second point of time.

Moreover, according to various examples of embodiments, the method may further comprise the steps of receiving a service request associated with the terminal endpoint device, determining an insufficient capacity at the first access point to provide the requested service, and initiating transition of the terminal endpoint device to the second access point by triggering an inter-network load balancing operation request to the second access point.

Additionally, according to various examples of embodiments, the method may further comprise the steps of transmitting the inter-network load balancing operation request to the second access point, instructing the second access point to provide the requested service to the terminal endpoint device.

Optionally, according to at least some examples of embodiments, the method further comprises the steps of constructing, based on uplink approval information provided by the second access point, an uplink approval to approve transition of the terminal endpoint device to the second access point, and transmitting the uplink approval to the terminal endpoint device. Alternatively, according to at least some examples of embodiments, the method may further comprise the steps of constructing, based on downlink approval information provided by the second access point, a downlink approval to approve transition of the terminal endpoint device to the second access point for receiving data transmitted from the network communication and control entity, and transmitting the downlink approval to the terminal endpoint device.

Furthermore, according to at least some examples of embodiments, the method may further comprise the steps of providing, based on uplink approval information provided by the second access point, uplink monitoring information to the terminal endpoint device. The uplink monitoring information comprises information about monitoring for an uplink approval provided by the second access point for approving transition of the terminal endpoint device to the second access point. Alternatively, according to at least some examples of embodiments, the method may further comprise the steps of providing, based on downlink approval information provided by the second access point, downlink monitoring information to the terminal endpoint device. The downlink monitoring information comprises information about monitoring for a downlink approval provided by the second access point for approving transition of the terminal endpoint device to the second access point to receive data transmitted from the network communication and control entity.

Further, according to various examples of embodiments, the method may further comprise the steps of receiving, via the second access point, uplink data traffic from the terminal endpoint device, and forwarding the uplink data traffic to a target network communication and control entity.

Moreover, according to various examples of embodiments, the method may further comprise the steps of, if the the terminal endpoint device transitions to the second access point, deciding between redirecting requests associated with the terminal endpoint device to the second access point, or postponing requests associated with the terminal endpoint device until the terminal endpoint device transitions back to the first access point.

The above mentioned features, either alone or in combination, allow for solving at least part of the problems and drawbacks present in relation to the prior art regarding improving the performance of MUSIM devices, as well as regarding utilizing the advantages of MUSIM devices more efficiently. Specifically, the above mentioned features, either alone or in combination, allow for establishing and triggering an inter-network load balancing operation. Therefore, the above mentioned features, either alone or in combination, allow for using capacity available in another network (capacity provided by another provider).

Referring now to Figure 3, there is shown a flow chart illustrating steps corresponding to a method according to examples of embodiments.

In particular, according to Figure 3, in S310, it is provided for a load balancing between a first access point and a second access point associated with a respective first network and second network, based on establishing a mutual acceptance between the first access point and the second access point to conditionally handle a partitioning of a load to be handled by the first access point. Further, in S320, a registration request from a terminal endpoint device indicating its capability of communicating via the first network and the second network is received. Moreover, in S330, between the first access point and the second access point, load balancing information indicative of information for establishing an inter-network load balancing operation between the first access point and the second access point with respect to the terminal endpoint device is exchanged.

According to various examples of embodiments, the first point of time may be equal to the second point of time.

Furthermore, according to at least some examples of embodiments, the registration request may further comprise information indicating that the reason for registration is to enable an inter-network load balancing operation between the first access point and the second access point.

Moreover, according to various examples of embodiments, the method may further comprise the steps of providing a registration confirmation to the terminal endpoint device for usage by the terminal endpoint device to confirm registration at the second access point toward the first access point. Further, according to various examples of embodiments, the method may further comprise the steps of receiving an inter-network load balancing operation request provided by the first access point. The method then further comprises determining a sufficient capacity at the second access point to provide a requested service associated with the terminal endpoint device, the requested service being requested in the inter network load balancing operation request, and conducting transition of the terminal endpoint device to the second access point.

Additionally, according to at least some examples of embodiments, the method may further comprise the steps of receiving the requested service in an uplink request by the terminal endpoint device, or receiving the requested service in a downlink request by a network communication and control entity for transmitting data to the terminal endpoint device.

Moreover, according to various examples of embodiments, the method may further comprise the steps of providing uplink approval information to the first access point to approve transition of the terminal endpoint device to the second access point, or providing an uplink approval to the terminal endpoint device to approve transition of the terminal endpoint device to the second access point.

Further, according to at least some examples of embodiments, the method may further comprise the steps of forwarding uplink data traffic from the terminal endpoint device to the first access point, or forwarding uplink data traffic from the terminal endpoint device to a target network communication and control entity.

Moreover, according to at least some examples of embodiments, the method may further comprise the steps of providing downlink approval information to the first access point to approve transition of the terminal endpoint device to the second access point for receiving data transmitted from the network communication and control entity. Alternatively, according to at least some examples of embodiments, the method may further comprise the steps of providing a downlink approval to the terminal endpoint device to approve transition of the terminal endpoint device to the second access point for receiving data transmitted from the network communication and control entity. Furthermore, according to at least some examples of embodiments, the method may further comprise the steps of providing re-transition information to the terminal endpoint device, the re-transition information comprising information indicating the terminal endpoint device to transit back to the first access point.

The above mentioned features, either alone or in combination, allow for solving at least part of the problems and drawbacks present in relation to the prior art regarding improving the performance of MUSIM devices, as well as regarding utilizing the advantages of MUSIM devices more efficiently.

Specifically, the above mentioned features, either alone or in combination, allow for establishing and conducting an inter-network load balancing operation. Therefore, the above mentioned features, either alone or in combination, allow for providing capacity to another network (capacity provided to another provider).

Referring now to Figure 4, there is shown a flow chart illustrating steps corresponding to a method according to examples of embodiments.

In particular, according to Figure 4, in S410, it is determined whether a terminal endpoint device is a MUSIM device capable of communicating via a first network and via a second network. A first access point and a second access point are associated with the first network and the second network, respectively, and a load balancing is provided between the first access point and the second access point, based on an established mutual acceptance between the first access point and the second access point to conditionally handle a partitioning of a load to be handled by the first access point. If the terminal endpoint device is such MUSIM device (S410: YES), then in S420, it is requested to the first access point for registration of the terminal endpoint device and indicating the capability of the terminal endpoint device to communicate via the first network and the second network. If the terminal endpoint device is not such MUSIM device (S410: NO), processing ends. In addition, in S430, a reconfiguration instruction provided by the first access point is received, the reconfiguration instruction instructing the terminal endpoint device to register to the second access point. Furthermore, in S440, it is requested to the second access point for registration of the terminal endpoint device and indicating the capability of the terminal endpoint device to communicate via the first network and the second network. Further, in S450, it is provided to the first access point, a registration confirmation obtained from the second access point upon registration of the terminal endpoint device to the second access point. The registration confirmation indicating that the terminal endpoint device is registered to the second access point.

According to various examples of embodiments, the method may further comprise the steps of indicating that the reason for registration is to establish an inter-network load balancing operation between the first access point and the second access point.

Furthermore, according to at least some examples of embodiments, the method may further comprise the steps of, after registration to the first access point, transitioning of the terminal endpoint device to radio resource control state, and/or after registration to the second access point, transitioning of the terminal endpoint device to radio resource control state.

Optionally, according to various examples of embodiments, the method may further comprise the steps of processing received from one of the first access point and the second access point instructing the terminal endpoint device in which one of the first network and the second network to connect for receiving a downlink transmission and/or for performing an uplink transmission.

Specifically, the above mentioned features, either alone or in combination, allow for participating in an inter-network load balancing operation. Therefore, the above mentioned features, either alone or in combination, allow for efficiently utilizing a capability of communicating via a first network (provided by a first provider) and via a second network (provided by a second provider).

Referring now to Figure 5, Figure 5 shows a block diagram illustrating an apparatus 500. The apparatus 500 e.g. being configured to be applied in a network communication element, like e.g. in an (first) access point (e.g. NodeB). It is to be noted that the apparatus 500 may include further elements or functions besides those described herein below. Furthermore, even though reference is made to an apparatus, the element or function may be also another device or function having a similar task, such as a chipset, a chip, a module, an application etc., which can also be part of a network element or attached as a separate element to a network element, or the like. It should be understood that each block and any combination thereof may be implemented by various means or their combinations, such as hardware, software, firmware, one or more processors and/or circuitry.

The apparatus 500 shown in Figure 5 may include a processing circuitry, a processing function, a control unit or a processor 510, such as a CPU or the like, which is suitable to perform an inter-network load balancing operation. The processor 510 may include one or more processing portions or functions dedicated to specific processing as described below, or the processing may be run in a single processor or processing function. Portions for executing such specific processing may be also provided as discrete elements or within one or more further processors, processing functions or processing portions, such as in one physical processor like a CPU or in one or more physical or virtual entities, for example. Reference signs 531, 532 denote input/output (I/O) units or functions (interfaces) connected to the processor or processing function 510. The I/O units 531, 532 may be used for communicating with network elements/communication elements and/or devices/apparatuses (which are connectable by wire and/or wirelessly). Reference sign 520 denotes a memory usable, for example, for storing data and programs to be executed by the processor or processing function 510 and/or as a working storage of the processor or processing function 510. It is to be noted that the memory 520 may be implemented by using one or more memory portions of the same or different type of memory. In addition, the memory 520 may refer to a database, e.g. a cloud server based database. Thus the memory 520 may be connected/linked to the apparatus 500, but not comprised by the apparatus 500.

The processor or processing function 510 is configured to execute processing related to the above described method. In particular, the processor or processing circuitry or function 510 includes one or more of the following sub-portions. Sub-portion 511 is a portion for providing for a load balancing between the apparatus 500 and an access point. The portion 511 may be configured to perform processing according to S210 of Figure 2. In addition, the processor or processing circuitry or function 510 may include a sub-portion 512 usable as a portion for receiving a registration request from a terminal endpoint device. The portion 512 may be configured to perform a processing according to S220 of Figure 2. Moreover, the processor or processing circuitry or function 510 may include a sub-portion 513 usable as a portion for detecting an occurrence of a condition to handle the partitioning of the load to be handled by the apparatus 500. The portion 513 may be configured to perform a processing according to S230 of Figure 2. Furthermore, the processor or processing circuitry or function 510 may include a sub-portion 514 usable as a portion for triggering a reconfiguration of the terminal endpoint device. The portion 514 may be configured to perform a processing according to S240 of Figure 2. Further, the processor or processing circuitry or function 510 may include a sub-portion 515 usable as a portion for receiving a registration confirmation. The portion 515 may be configured to perform a processing according to S250 of Figure 2. Moreover, the processor or processing circuitry or function 510 may include a sub-portion 516 usable as a portion for exchanging load balancing information with the access point. The portion 516 may be configured to perform a processing according to S260 of Figure 2.

Referring now to Figure 6, Figure 6 shows a block diagram illustrating an apparatus 600. The apparatus 600 e.g. being configured to be applied in a network communication element, like e.g. in an (second) access point (e.g. NodeB). It is to be noted that the apparatus 600 may include further elements or functions besides those described herein below. Furthermore, even though reference is made to an apparatus, the element or function may be also another device or function having a similar task, such as a chipset, a chip, a module, an application etc., which can also be part of a network element or attached as a separate element to a network element, or the like. It should be understood that each block and any combination thereof may be implemented by various means or their combinations, such as hardware, software, firmware, one or more processors and/or circuitry.

The apparatus 600 shown in Figure 6 may include a processing circuitry, a processing function, a control unit or a processor 610, such as a CPU or the like, which is suitable to perform an inter-network load balancing operation. The processor 610 may include one or more processing portions or functions dedicated to specific processing as described below, or the processing may be run in a single processor or processing function. Portions for executing such specific processing may be also provided as discrete elements or within one or more further processors, processing functions or processing portions, such as in one physical processor like a CPU or in one or more physical or virtual entities, for example. Reference signs 631, 632 denote input/output (I/O) units or functions (interfaces) connected to the processor or processing function 610. The I/O units 631, 632 may be used for communicating with network elements/communication elements and/or devices/apparatuses (which are connectable by wire and/or wirelessly). Reference sign 620 denotes a memory usable, for example, for storing data and programs to be executed by the processor or processing function 610 and/or as a working storage of the processor or processing function 610. It is to be noted that the memory 620 may be implemented by using one or more memory portions of the same or different type of memory. In addition, the memory 620 may refer to a database, e.g. a cloud server based database. Thus the memory 620 may be connected/linked to the apparatus 600, but not comprised by the apparatus 600.

The processor or processing function 610 is configured to execute processing related to the above described method. In particular, the processor or processing circuitry or function 610 includes one or more of the following sub-portions. Sub-portion 611 is a portion for providing for a load balancing between the apparatus 600 and an access point. The portion 611 may be configured to perform processing according to S310 of Figure 3. In addition, the processor or processing circuitry or function 610 may include a sub-portion 612 usable as a portion for receiving a registration request from a terminal endpoint device. The portion 612 may be configured to perform a processing according to S320 of Figure 3. Moreover, the processor or processing circuitry or function 610 may include a sub-portion 613 usable as a portion for exchanging load balancing information with an access point. The portion 613 may be configured to perform a processing according to S330 of Figure 3.

Referring now to Figure 7, Figure 7 shows a block diagram illustrating an apparatus 700. The apparatus 700 e.g. being configured to be applied in a terminal endpoint MUSIM device, like e.g. in a MUSIM user equipment. It is to be noted that the apparatus 700 may include further elements or functions besides those described herein below. Furthermore, even though reference is made to an apparatus, the element or function may be also another device or function having a similar task, such as a chipset, a chip, a module, an application etc., which can also be part of a network element or attached as a separate element to a network element, or the like. It should be understood that each block and any combination thereof may be implemented by various means or their combinations, such as hardware, software, firmware, one or more processors and/or circuitry.

The apparatus 700 shown in Figure 7 may include a processing circuitry, a processing function, a control unit or a processor 710, such as a CPU or the like, which is suitable to communicate via a first network and via a second network different from the first network, as well as to participate in an inter-network load balancing operation. The processor 710 may include one or more processing portions or functions dedicated to specific processing as described below, or the processing may be run in a single processor or processing function. Portions for executing such specific processing may be also provided as discrete elements or within one or more further processors, processing functions or processing portions, such as in one physical processor like a CPU or in one or more physical or virtual entities, for example. Reference signs 731 , 732 denote input/output (I/O) units or functions (interfaces) connected to the processor or processing function 710. The I/O units 731, 732 may be used for communicating with network elements/communication elements and/or devices/apparatuses (which are connectable by wire and/or wirelessly). Reference sign 720 denotes a memory usable, for example, for storing data and programs to be executed by the processor or processing function 710 and/or as a working storage of the processor or processing function 710. It is to be noted that the memory 720 may be implemented by using one or more memory portions of the same or different type of memory. In addition, the memory 720 may refer to a database, e.g. a cloud server based database. Thus the memory 720 may be connected/linked to the apparatus 700, but not comprised by the apparatus 700.

The processor or processing function 710 is configured to execute processing related to the above described method. In particular, the processor or processing circuitry or function 710 includes one or more of the following sub-portions. Sub-portion 711 is a portion for enabling the MUSIM capabilities of the apparatus 700, which are to communicating via a first network and via a second network. The portion 711 may be configured to allow a positive (YES) result in S410 according to Figure 4. In addition, the processor or processing circuitry or function 710 may include a sub-portion 712 usable as a portion for requesting to a first access point for registration and indicating the capability to communicate via a first and a second network. The portion 712 may be configured to perform a processing according to S420 of Figure 4. Moreover, the processor or processing circuitry or function 710 may include a sub-portion 713 usable as a portion for receiving a reconfiguration instruction. The portion 713 may be configured to perform a processing according to S430 of Figure 4. Furthermore, the processor or processing circuitry or function 710 may include a sub-portion 714 usable as a portion for requesting to a second access point for registration and indicating the capability to communicate via a first and a second network. The portion 714 may be configured to perform a processing according to S440 of Figure 4. Further, the processor or processing circuitry or function 710 may include a sub-portion 715 usable as a portion for providing a registration confirmation. The portion 715 may be configured to perform a processing according to S450 of Figure 4.

In the following, further details and implementation examples according to examples of embodiments are described with reference to Figures 8 to 10.

According to at least some examples of embodiments, one idea of the present specification takes advantage of MUSIM devices. Such MUSIM device may e.g. refer to the apparatus 700 according to Figure 7. In this specification, it is proposed that when a network A (e.g. a first network) becomes aware that a UE is MUSIM device (and that the UE’s USIMs are associated to other networks, e.g. B and C (e.g. second and third networks, respectively), operating in the same geographical location), the network A triggers the temporarily transition to either the network B or C, whenever network A is experiencing a high load.

The transition from one network to another can be done at two levels. At higher layers, where a UE is shifted to another gNB belonging to a different network, and which would be applied when the UE has to transition to another network on a larger time scale. At lower layers, where the UE can be shifted to another gNB in a short time frame (e.g. at a scheduling grant granularity). The present specification focuses in at least some examples of embodiments on the second approach, for which the main constituting phases are depicted according to various examples of embodiments in Figure 8.

Referring to Figure 8, there are shown general phases of a proposed inter-operator load balancing operation according to examples of embodiments, wherein the phases are as follows. In S810, an inter-operator scheduling agreement is established. At this step the operators managing a first and second network (the first network being different from the second network), respectively, agree to establish an inter-operator scheduling agreement. A first access point may be associated with the first network. According to Figure 8, such first access point refers to the gNB A (Public Land Mobile Network 1, PLMN1) 500, which may refer to the apparatus 500 according to Figure 5. Further, a second access point may be associated with the second network. According to Figure 8, such second access point refers to the gNB B (Public Land Mobile Network 2, PLMN2) 600, which may refer to the apparatus 600 according to Figure 6. A shown UE 700 refers to a MUSIM device, capable of communication at least via the first network and via the second network (thus, via the gNB A 500 and via the gNB B 600). The UE 700 according to Figure 8 may refer to the apparatus according to 700 according to Figure 7.

The inter-operator scheduling agreement can be on a permanent basis or it can be made on a temporary basis, for example whenever a high load situation is detected, or it is foreseen in the near future. Such situation may e.g. be a large concert or a show.

As part of this agreement, security primitives are exchanged between the gNB a 500 and the gNB B 600, that allow a flexible inter-operator load balancing mode to operate in a secure manner.

In S820, initial access and registration is performed by the UE 700. Specifically, the UE 700 perform its initial access towards the gNB A 500 and becomes registered to the first network, i.e. the UE 700 transitions to RRC Connected state. During this procedure, the UE 700 informs the gNB A 500 that it is a MUSIM UE 700 and that it has a USIM belonging to a second network (PLMN2).

In S830, a high load is detected. Specifically, the gNB A 500 (or the associated first network) detects a high load where either due to the presence of UEs requiring large amounts of resources or due to a large number of UEs being served, the gNB A 500 has difficulties serving all connected UEs.

In S840, reconfiguration of the UE 700 is performed. Particularly, to deal with the high load condition, the gNB A 500 triggers the reconfiguration of the UE 700, so the gNB A 500 instructs the UE 700 to connect to the best gNB associated with the second network (PLMN2), which in the provided example in Figure 8 is the gNB B 600. The reason for this reconfiguration is to ensure that the UE 700 is ready to operate in flexible inter-operator load balancing mode.

In case the UE 700 is already connected to the another PLMN (which in practice can happen as the connection to each PLMN occurs independently from the control of another PLMN), then the UE 700 ignores this command coming from the gNB A 500 and moves to step S860. Note that to reach step S860, the UE 700 might need to perform some signaling exchanges with the second network (PLMN2) in order to obtain the security key for completing step S860.

In S850, initial access and registration of the UE 700 toward the second network is performed. Specifically, the UE 700 performs its initial access towards the gNB B 600 and becomes registered to the second network, i.e. the UE 700 transitions to RRC Connected state. During this procedure, the UE informs the gNB B 600 (the second network, PLMN2) that it is a MUSIM UE and that it has a USIM belonging to the first network (to PLMN1). Furthermore, it informs the second network (PLMN2) that the reason for network establishment is to enable the operation of flexible inter-operator load balancing mode.

During S850, the second network (the PLMN2) provides a security key (e.g. a registration confirmation) to be used by the UE 700 to authenticate towards the first network (towards PLMN1) that it has in fact established the link towards the second network (towards PLMN2).

Further, according to various examples of embodiments, when the UE 700 transitions to PLMN2, then the paging and any voice calls can be redirected from PLMN1 to PLMN2. Alternatively, measurements or System Information Blocks (SIB) readings or any other non-prioritary downlink traffic at PLMN1 can be paused/postponed until the UE 700 returns back to PLMN1;

In S860, confirmation that the UE 700 is now registered towards gNB B 600 is performed. Specifically, the UE 700 confirms the link establishment through the use of the provided security key (see S850). In S870, inter-operator scheduling agreement is established. Specifically, the gNB A 500 (PLMN1) and the gNB B 600 (PLMN2) exchange required information to ensure that the flexible inter-operator load balancing mode is possible.

According to at least some examples of embodiments, the required information may e.g. indicate that the reason for network establishment is to enable the operation of flexible inter-operator load balancing mode. Thus, instead of the UE 700 informing, in S850, the second network (PLMN2) of the reason for network establishment, such information may alternatively or additionally be exchanged between the first network (PLMN1) and the second network (PLMN2) (between gNB A 500 and gNB B 600).

In S880, flexible inter-operator load balancing operation is performed. Specifically, when entering this phase, the gNB A 500 and the gNB B 600 can now trigger the load balancing operation whenever required, i.e. the UE 700 can now be instructed (via a downlink grant or an uplink grant) in which network to connect to either receive a downlink transmission or perform an uplink transmission.

According to at least some examples of embodiments, details of S880 are further outlined in the following with reference to Figures 9 and 10.

Referring now to Figure 9, it is shown a flexible inter-operator load balancing for uplink transmissions according to examples of embodiments. Specifically, in Figure 9, the signalling flow on how to perform load balancing across inter-operator gNBs (500, 600) for uplink transmissions is depicted. It is to be noted that the UE 700 according to Figure 9 refers to the UE 700 according to Figure 8, the gNB A 500 (PLMN1) according to Figure 9 refers to the gNB A 500 (PLMN1) according to Figure 8, and the gNB B 600 (PLMN2) according to Figure 9 refers to the gNB B 600 (PLMN2) according to Figure 8. The steps of the procedure are as follows:

In S910, the higher layers of the UE 700 generate data, wherein in S920, the UE 700 triggers a scheduling request.

In S930, The gNB A 500, which is currently under high load; is not able to satisfy the UE service requirements, so the gNB A 500 triggers an “Inter Operator UL Scheduling Request” in order to request the gNB B 600 if the gNB B 600 can serve the gNB A’s UE request.

In S940, the gNB B 600 replies that it has resources and shares any additional grant info (e.g. which time and frequency resources the UE 700 should use when transmitting to the gNB B 600, as well other physical layer information such as Hybrid Automated Repeat Request (HARQ), process number, power control adjustments, MCS, Uplink/Supplementary Uplink (UL/SUL) indicator, frequency hopping flag).

In S950, the gNB A 500 constructs and transmits an uplink grant Downlink Control Information (DCI) with the contents provided by the gNB B 600. Alternatively, according to various examples of embodiments, the gNB A 500 informs the UE 700 of which Cell Radio Network Temporary Identifier (C-RNTI) it should listen from the gNB B 600 in order to receive the uplink grant. Further, alternatively, according to various examples of embodiments, the gNB B 600 can provide directly an uplink grant to the UE 700 using the already pre-configured C-RNTI. In this case the UE 700 should be already monitoring the Physical Downlink Control Channel (PDCCH) from the gNB B 600. Note that this approach is less complex as the physical layer parameters are not exchanged between PLMNs (500, 600).

In S960, the UE 700 performs the Inter Operator Physical Uplink Shared Channel (PUSCH) Transmission. Note that any eventual HARQ process related to the uplink exchanges with the gNB B 600 will be taken care of by the gNB B 600. In S970, the second network (PLMN2) forwards the uplink traffic either to the first network (PLMN1) or directly to the recipient of the data (e.g. a server in the internet). In S980, the second network (PLMN2) informs that the UE 700 can now transition back to the first network (PLMN1).

Referring now to Figure 10, it is shown a flexible inter-operator load balancing for downlink transmissions according to examples of embodiments. Specifically, in Figure 10, the signalling flow on how to perform load balancing across inter-operator gNBs 500, 600 for downlink transmissions is depicted. It is to be noted that the UE 700 according to Figure 10 refers to the UE 700 according to Figure 8, the gNB A 500 (PLMN1) according to Figure 10 refers to the gNB A 500 (PLMN1) according to Figure 8, and the gNB B 600 (PLMN2) according to Figure 10 refers to the gNB B 600 (PLMN2) according to Figure 8. The steps of the procedure are as follows:

In S1010, the gNB A 500 receives from the core network (not shown) new downlink data to be transmitted to the UE 700. In S1020, the gNB A 500, which is currently under high load, is not able to satisfy the downlink service requirements, so the gNB A 500 triggers an “Inter Operator UL Scheduling Request” in order to request the gNB B 600, if the gNB B 600 can serve the gNB A’s UE downlink transmission.

In S1030, the gNB B 600 replies that it has resources and shares any additional grant info (e.g. which time and frequency resources the UE 700 should use to receive the transmission from the gNB B 600, as well other physical layer information such as HARQ process number, Virtual Resource Block (VRB)-to- Physical Resource Block (PRB) mapping, MCS, Redundancy Version, Downlink Assignment Indicator (DAI), Transmit Power Control (TPC) for the PUCCH, PUCCH resource indicator, Physical Downlink Shared Channel (PDSCH)-to-HARQ feedback timing indicator, Transport Block (TB) scaling). Alternatively, according to at least some examples of embodiments, the UE 700 is informed to listen to the downlink grant to be transmitted by the gNB B 600 over its PDCCH. This approach is less complex as the physical layer parameters are not exchanged between PLMNs (500, 600).

In S1040, the gNB A 500 constructs and transmits a downlink grant DCI with the contents provided by the gNB B 600. In S1050, the UE 700 listens and receives the inter operator PDSCH transmission. Note that any eventual HARQ process related to the downlink exchanged with the gNB B 600 will taken care of by the gNB B 600. In S1060, the second network (PLMN2) informs that the UE 700 can now transition back to the first network (PLMN1).

It should be appreciated that

- an access technology via which traffic is transferred to and from an entity in the communication network may be any suitable present or future technology, such as WLAN (Wireless Local Access Network), WiMAX (Worldwide Interoperability for Microwave Access), LTE, LTE-A, 5G, Bluetooth, Infrared, and the like may be used; additionally, embodiments may also apply wired technologies, e.g. IP based access technologies like cable networks or fixed lines. - embodiments suitable to be implemented as software code or portions of it and being run using a processor or processing function are software code independent and can be specified using any known or future developed programming language, such as a high-level programming language, such as objective-C, C, C++, C#, Java, Python, Javascript, other scripting languages etc., or a low-level programming language, such as a machine language, or an assembler.

- implementation of embodiments is hardware independent and may be implemented using any known or future developed hardware technology or any hybrids of these, such as a microprocessor or CPU (Central Processing Unit), MOS (Metal Oxide Semiconductor), CMOS (Complementary MOS), BiMOS (Bipolar MOS), BiCMOS (Bipolar CMOS), ECL (Emitter Coupled Logic), and/or TTL (Transistor-Transistor Logic).

- embodiments may be implemented as individual devices, apparatuses, units, means or functions, or in a distributed fashion, for example, one or more processors or processing functions may be used or shared in the processing, or one or more processing sections or processing portions may be used and shared in the processing, wherein one physical processor or more than one physical processor may be used for implementing one or more processing portions dedicated to specific processing as described,

- an apparatus may be implemented by a semiconductor chip, a chipset, or a (hardware) module including such chip or chipset;

- embodiments may also be implemented as any combination of hardware and software, such as ASIC (Application Specific 1C (Integrated Circuit)) components,

FPGA (Field-programmable Gate Arrays) or CPLD (Complex Programmable Logic Device) components or DSP (Digital Signal Processor) components.

- embodiments may also be implemented as computer program products, including a computer usable medium having a computer readable program code embodied therein, the computer readable program code adapted to execute a process as described in embodiments, wherein the computer usable medium may be a non-transitory medium.

Although the present disclosure has been described herein before with reference to particular embodiments thereof, the present disclosure is not limited thereto and various modifications can be made thereto.

Claims

CLAIMS:

1. A method, comprising: providing for a load balancing between a first access point and a second access point associated with a respective first network and second network, based on establishing a mutual acceptance between the first access point and the second access point to conditionally handle a partitioning of a load to be handled by the first access point, receiving a registration request from a terminal endpoint device indicating its capability of communicating via the first network and the second network, detecting an occurrence of a condition to handle the partitioning of the load to be handled by the first access point, triggering a reconfiguration of the terminal endpoint device, for instructing the terminal endpoint device to register to the second access point, receiving, from the terminal endpoint device, a registration confirmation indicating that the terminal endpoint device is registered to the second access point, and exchanging, between the first access point and the second access point, load balancing information indicative of information to establish an inter-network load balancing operation between the first access point and the second access point with respect to the terminal endpoint device.

2. The method according to claim 1 , wherein the mutual acceptance is provided permanently or temporarily.

3. The method according to claim 1 or 2, wherein the detecting further comprises that the condition to handle the partitioning of the load to be handled by the first access point is at least one of exceedance of a load prevailing at the first access point over a predetermined load threshold value, exceedance of a number of terminal endpoint devices including the terminal endpoint device being served by the first access point over a predetermined number threshold value, and occurrence of a predetermined temporal event, lasting from a first point of time to a second point of time.

4. The method according to any of claims 1 to 3, further comprising the steps of: receiving a service request associated with the terminal endpoint device, determining an insufficient capacity at the first access point to provide the requested service, and initiating transition of the terminal endpoint device to the second access point by triggering an inter-network load balancing operation request to the second access point.

5. The method according to claim 4, further comprising the steps of: transmitting the inter-network load balancing operation request to the second access point, instructing the second access point to provide the requested service to the terminal endpoint device.

6. The method according to claim 4 or 5, further comprising the steps of: receiving the requested service in an uplink request by the terminal endpoint device, or receiving the requested service in a downlink request by a network communication and control entity for transmitting data to the terminal endpoint device.

7. The method according to any of claims 4 to 6, further comprising the steps of: constructing, based on uplink approval information provided by the second access point, an uplink approval to approve transition of the terminal endpoint device to the second access point, and transmitting the uplink approval to the terminal endpoint device, or constructing, based on downlink approval information provided by the second access point, a downlink approval to approve transition of the terminal endpoint device to the second access point for receiving data transmitted from the network communication and control entity, and transmitting the downlink approval to the terminal endpoint device.

8. The method according to any of claims 4 to 6, further comprising the steps of: providing, based on uplink approval information provided by the second access point, uplink monitoring information to the terminal endpoint device, the uplink monitoring information comprises information about monitoring for an uplink approval provided by the second access point for approving transition of the terminal endpoint device to the second access point, or providing, based on downlink approval information provided by the second access point, downlink monitoring information to the terminal endpoint device, the downlink monitoring information comprises information about monitoring for a downlink approval provided by the second access point for approving transition of the terminal endpoint device to the second access point to receive data transmitted from the network communication and control entity.

9. The method according to any of claims 4 to 8, further comprising the steps of: receiving, via the second access point, uplink data traffic from the terminal endpoint device, and forwarding the uplink data traffic to a target network communication and control entity.

10. The method according to any of claims 4 to 9, further comprising the steps of: if the the terminal endpoint device transitions to the second access point, deciding between redirecting requests associated with the terminal endpoint device to the second access point, or postponing requests associated with the terminal endpoint device until the terminal endpoint device transitions back to the first access point.

11. A method, comprising: providing for a load balancing between a first access point and a second access point associated with a respective first network and second network, based on establishing a mutual acceptance between the first access point and the second access point to conditionally handle a partitioning of a load to be handled by the first access point, receiving a registration request from a terminal endpoint device indicating its capability of communicating via the first network and the second network, and exchanging, between the first access point and the second access point, load balancing information indicative of information for establishing an inter-network load balancing operation between the first access point and the second access point with respect to the terminal endpoint device.

12. The method according to claim 11 , wherein the mutual acceptance is provided permanently or temporarily.

13. The method according to claim 11 or 12, wherein the registration request further comprises information indicating that the reason for registration is to enable an inter-network load balancing operation between the first access point and the second access point.

14. The method according to claim 11 or 12, wherein the exchanging step further comprises to exchange, between the first access point and the second access point, information indicating that the reason for registration of the terminal endpoint device is to enable an inter-network load balancing operation between the first access point and the second access point.

15. The method according to any of claims 11 to 14, further comprising the steps of: providing a registration confirmation to the terminal endpoint device for usage by the terminal endpoint device to confirm registration at the second access point toward the first access point.

16. The method according to any of claims 11 to 15, further comprising the steps of: receiving an inter-network load balancing operation request provided by the first access point, determining a sufficient capacity at the second access point to provide a requested service associated with the terminal endpoint device, the requested service being requested in the inter-network load balancing operation request, and conducting transition of the terminal endpoint device to the second access point.

17. The method according to claim 16, further comprising the steps of: receiving the requested service in an uplink request by the terminal endpoint device, or receiving the requested service in a downlink request by a network communication and control entity for transmitting data to the terminal endpoint device.

18. The method according to claim 17, further comprising the steps of: providing uplink approval information to the first access point to approve transition of the terminal endpoint device to the second access point, or providing an uplink approval to the terminal endpoint device to approve transition of the terminal endpoint device to the second access point.

19. The method according to any of claims 16 to 18, further comprising the steps of: forwarding uplink data traffic from the terminal endpoint device to the first access point, or forwarding uplink data traffic from the terminal endpoint device to a target network communication and control entity.

20. The method according to claim 17, further comprising the steps of: providing downlink approval information to the first access point to approve transition of the terminal endpoint device to the second access point for receiving data transmitted from the network communication and control entity, or providing a downlink approval to the terminal endpoint device to approve transition of the terminal endpoint device to the second access point for receiving data transmitted from the network communication and control entity.

21. The method according to any of claims 16 to 20, further comprising the steps of: providing re-transition information to the terminal endpoint device, the re-transition information comprising information indicating the terminal endpoint device to transit back to the first access point.

22. A method, comprising: comprising, by a terminal endpoint device, a capability of communicating via a first network and a second network, wherein a first access point and a second access point are associated with the first network and the second network, respectively, and a load balancing is provided between the first access point and the second access point, based on an established mutual acceptance between the first access point and the second access point to conditionally handle a partitioning of a load to be handled by the first access point, requesting to the first access point for registration of the terminal endpoint device and indicating the capability of the terminal endpoint device to communicate via the first network and the second network, receiving a reconfiguration instruction provided by the first access point, the reconfiguration instruction instructing the terminal endpoint device to register to the second access point, requesting to the second access point for registration of the terminal endpoint device and indicating the capability of the terminal endpoint device to communicate via the first network and the second network, and providing, to the first access point, a registration confirmation obtained from the second access point upon registration of the terminal endpoint device to the second access point, the registration confirmation indicating that the terminal endpoint device is registered to the second access point.

23. The method according to claim 22, wherein the requesting to the second access point further comprises: indicating that the reason for registration is to establish an inter-network load balancing operation between the first access point and the second access point.

24. The method according to claim 22 or 23, further comprising the steps of: after registration to the first access point, transitioning of the terminal endpoint device to radio resource control state, and/or after registration to the second access point, transitioning of the terminal endpoint device to radio resource control state.

25. The method according to any of claims 22 to 24, further comprising the steps of: processing instructions received from one of the first access point and the second access point instructing the terminal endpoint device in which one of the first network and the second network to connect for receiving a downlink transmission and/or for performing an uplink transmission.

26. An apparatus, comprising: at least one processing circuitry, and at least one memory for storing instructions to be executed by the processing circuitry, wherein the at least one memory and the instructions are configured to, with the at least one processing circuitry, cause the apparatus at least to: provide for a load balancing between the apparatus and an access point associated with a respective first network and second network, based on establishing a mutual acceptance between the apparatus and the access point to conditionally handle a partitioning of a load to be handled by the apparatus, receive a registration request from a terminal endpoint device indicating its capability of communicating via the first network and the second network, detect an occurrence of a condition to handle the partitioning of the load to be handled by the apparatus, trigger a reconfiguration of the terminal endpoint device, for instructing the terminal endpoint device to register to the access point, receive, from the terminal endpoint device, a registration confirmation indicating that the terminal endpoint device is registered to the access point, and exchange, with the access point, load balancing information indicative of information to establish an inter-network load balancing operation with the access point with respect to the terminal endpoint device.

27. The apparatus according to claim 26, wherein the mutual acceptance is provided permanently or temporarily.

28. The apparatus according to claim 26 or 27, wherein the condition to handle the partitioning is at least one of exceedance of a load prevailing at the apparatus over a predetermined load threshold value, exceedance of a number of terminal endpoint devices including the terminal endpoint device being served by the apparatus over a predetermined number threshold value, and occurrence of a predetermined temporal event, lasting from a first point of time to a second point of time.

29. The apparatus according to any of claims 26 to 28, wherein the at least one memory and the instructions are further configured to cause the apparatus at least to: receive a service request associated with the terminal endpoint device, determine an insufficient capacity at the apparatus to provide the requested service, and initiate transition of the terminal endpoint device to the access point by triggering an inter-network load balancing operation request to the access point.

30. The apparatus according to claim 29, wherein the at least one memory and the instructions are further configured to cause the apparatus at least to: transmit the inter-network load balancing operation request to the access point, instructing the access point to provide the requested service to the terminal endpoint device.

31. The apparatus according to claim 29 or 30, wherein the at least one memory and the instructions are further configured to cause the apparatus at least to: receive the requested service in an uplink request by the terminal endpoint device, or receive the requested service in a downlink request by a network communication and control entity for transmitting data to the terminal endpoint device.

32. The apparatus according to any of claims 29 to 31, wherein the at least one memory and the instructions are further configured to cause the apparatus at least to: construct, based on uplink approval information provided by the access point, an uplink approval to approve transition of the terminal endpoint device to the access point, and transmit the uplink approval to the terminal endpoint device, or construct, based on downlink approval information provided by the access point, a downlink approval to approve transition of the terminal endpoint device to the access point for receiving data transmitted from the network communication and control entity, and transmit the downlink approval to the terminal endpoint device.

33. The apparatus according to any of claims 29 to 31, wherein the at least one memory and the instructions are further configured to cause the apparatus at least to: provide, based on uplink approval information provided by the access point, uplink monitoring information to the terminal endpoint device, the uplink monitoring information comprises information about monitoring for an uplink approval provided by the access point for approving transition of the terminal endpoint device to the access point, or provide, based on downlink approval information provided by the access point, downlink monitoring information to the terminal endpoint device, the downlink monitoring information comprises information about monitoring for a downlink approval provided by the access point for approving transition of the terminal endpoint device to the access point to receive data transmitted from the network communication and control entity.

34. The apparatus according to any of claims 29 to 33, wherein the at least one memory and the instructions are further configured to cause the apparatus at least to: receive, via the access point, uplink data traffic from the terminal endpoint device, and forward the uplink data traffic to a target network communication and control entity.

35. The apparatus according to any of claims 29 to 34, wherein the at least one memory and the instructions are further configured to cause the apparatus at least to: if the the terminal endpoint device transitions to the access point, decide to redirect requests associated with the terminal endpoint device to the access point, or postpone requests associated with the terminal endpoint device until the terminal endpoint device transitions back to the apparatus.

36. An apparatus, comprising: at least one processing circuitry, and at least one memory for storing instructions to be executed by the processing circuitry, wherein the at least one memory and the instructions are configured to, with the at least one processing circuitry, cause the apparatus at least to: provide for a load balancing between an access point and the apparatus associated with a respective first network and second network, based on establishing a mutual acceptance between the access point and the apparatus to conditionally handle a partitioning of a load to be handled by the access point, receive a registration request from a terminal endpoint device indicating its capability of communicating via the first network and the second network, and exchange, with the access point, load balancing information indicative of information to establish an inter-network load balancing operation with the access point with respect to the terminal endpoint device.

37. The apparatus according to claim 36, wherein the mutual acceptance is provided permanently or temporarily.

38. The apparatus according to claim 36 or 37, wherein the registration request further comprises information indicating that the reason for registration is to enable an inter-network load balancing operation between the access point and the apparatus.

39. The apparatus according to claim 36 or 37, wherein the at least one memory and the instructions are further configured to cause the apparatus at least to: exchange, with the access point, information indicating that the reason for registration of the terminal endpoint device is to enable an inter-network load balancing operation between the apparatus and the access point

40. The apparatus according to any of claims 36 to 39, wherein the at least one memory and the instructions are further configured to cause the apparatus at least to: provide a registration confirmation to the terminal endpoint device for usage by the terminal endpoint device to confirm registration at the apparatus toward the access point.

41. The apparatus according to any of claims 36 to 40, wherein the at least one memory and the instructions are further configured to cause the apparatus at least to: receive an inter-network load balancing operation request provided by the access point, determine a sufficient capacity at the apparatus to provide a requested service associated with the terminal endpoint device, the requested service being requested in the inter-network load balancing operation request, and conduct transition of the terminal endpoint device to the apparatus.

42. The apparatus according to claim 41, wherein the at least one memory and the instructions are further configured to cause the apparatus at least to: receive the requested service in an uplink request by the terminal endpoint device, or receive the requested service in a downlink request by a network communication and control entity for transmitting data to the terminal endpoint device.

43. The apparatus according to claim 42, wherein the at least one memory and the instructions are further configured to cause the apparatus at least to: provide uplink approval information to the access point to approve transition of the terminal endpoint device to the apparatus, or provide an uplink approval to the terminal endpoint device to approve transition of the terminal endpoint device to the apparatus.

44. The apparatus according to any of claims 41 to 43, wherein the at least one memory and the instructions are further configured to cause the apparatus at least to: forwarding uplink data traffic from the terminal endpoint device to the first access point, or forwarding uplink data traffic from the terminal endpoint device to a target network communication and control entity.

45. The apparatus according to claim 42, wherein the at least one memory and the instructions are further configured to cause the apparatus at least to: provide downlink approval information to the access point to approve transition of the terminal endpoint device to the apparatus for receiving data transmitted from the network communication and control entity, or provide a downlink approval to the terminal endpoint device to approve transition of the terminal endpoint device to the apparatus for receiving data transmitted from the network communication and control entity.

46. The apparatus according to any of claims 42 to 45, wherein the at least one memory and the instructions are further configured to cause the apparatus at least to: provide re-transition information to the terminal endpoint device, the re-transition information comprising information indicating the terminal endpoint device to transit back to the access point.

47. An apparatus, comprising: at least one processing circuitry, and at least one memory for storing instructions to be executed by the processing circuitry, wherein the at least one memory and the instructions are configured to, with the at least one processing circuitry, cause the apparatus at least to: comprise a capability of communicating via a first network and a second network, wherein a first access point and a second access point are associated with the first network and the second network, respectively, and a load balancing is provided between the first access point and the second access point, based on an established mutual acceptance between the first access point and the second access point to conditionally handle a partitioning of a load to be handled by the first access point, request to the first access point for registration and indicate the capability to communicate via the first network and the second network, receive a reconfiguration instruction provided by the first access point, instructing the apparatus to register to the second access point, request to the second access point for registration and indicate the capability to communicate via the first network and the second network, and provide, to the first access point, a registration confirmation obtained from the second access point upon registration to the second access point, the registration confirmation indicating that the apparatus is registered to the second access point.

48. The apparatus according to claim 47, wherein the at least one memory and the instructions are further configured to cause the apparatus at least to: indicate toward the second access point that the reason for registration is to establish an inter-network load balancing operation between the first access point and the second access point.

49. The apparatus according to claim 47 or 48, wherein the at least one memory and the instructions are further configured to cause the apparatus at least to: after registration to the first access point, transition to radio resource control state, and/or after registration to the second access point, transition to radio resource control state.

50. The apparatus according to any of claims 47 to 49, wherein the at least one memory and the instructions are further configured to cause the apparatus at least to: process instructions received from one of the first access point and the second access point instructing the apparatus in which one of the first network and the second network to connect for receiving a downlink transmission and/or for performing an uplink transmission.

51. A computer program product for a computer, including software code portions for performing the steps of any of claims 1 to 10, of any of claims 11 to 21, or of any of claims 22 to 25 when said product is run on the computer.

52. The computer program product according to claim 51 , wherein the computer program product includes a computer-readable medium on which said software code portions are stored, and/or the computer program product is directly loadable into the internal memory of the computer and/or transmittable via a network by means of at least one of upload, download and push procedures.