A method for managing at least two subnetworks

Abstract

The invention relates to a method (100) for managing at least two subnetworks (30, 40), comprising the following steps carried out by a central subnetwork managing entity (10): - Collecting (101) user information and / or network information from the at least two subnetworks (30,40), - Deriving (102) a suitable pre-configuration for each of the at least two subnetworks (30,40) based on the collected information, - Initializing (103) the derived pre-configuration for each of the at least two subnetworks (30, 40), - Managing (104) a coordination of the at least two pre-configured subnetworks (30, 40), wherein the coordination is specified as a traffic and / or a resource management. Further the invention relates to a central subnetwork managing entity (10) and a computer program (90).

Description

[0001] A method for managing at least two subnetworks

[0002] The invention relates to a method for managing at least two subnetworks. Further, the invention relates to a computer program, an entity, and a storage medium for this purpose.

[0003] State of the art

[0004] Future telecommunications technology such as 6G will have to cope with demanding radio performance requirements. Services such as holographic telepresence or virtual reality may require data rates above 100 Gbps, while industrial services such as fast motion control in robotic machines could require fraction of millisecond latencies and seven to nine nines reliability. These requirements are beyond what is currently supported by current communications technology such as 5G or WiFi6 and can only be achieved by moving the network infrastructure to the very edge, together with the intelligence and decision-making capabilities.

[0005] Efficient supporting of these challenging technical requirements will be crucial. As an example, 6G technology is expected to bridge the gap between digital, physical, and biological worlds by supporting services such as holographic telepresence, extreme virtual reality with tactile feedback, remote surgery, and high accuracy sensing. So called in-X networks will be utilized in locations where high-performance requirements are demanded, such as production modules, vehicles, or human bodies for critical functions like heartbeat control. Further, such subnetworks can find application in vehicles where sensors and compute entities can be seamlessly interconnected via 6G subnetworks.

[0006] In an ecosystem, where several 6G subnetworks operate concurrently, the potential for interference, resource contention, and miscoordination is significant. Each subnetwork is designed to support a specific set of applications with distinct requirements in terms of bandwidth, latency, and reliability. These diverse demands can lead to complex traffic management challenges. Coordinating these needs in a harmonious and efficient manner, which maintains the requirements of each individual subnetwork, particularly real-time constraints, therefore will be necessary.

[0007] Further, this also relates to the challenge of mitigating signal interference between the subnetworks. While 6G subnetworks are expected to use low power communication to reduce interference, the close proximity of multiple subnetworks can still lead to overlapping subnetworks that degrade network performance if not mitigated.

[0008] Furthermore, in a multi-subnetwork environment, the allocation and management of resources like spectrum and energy will become more complicated. Each subnetwork has its own requirements and peak usage times, and balancing these needs to optimize the overall network performance can be a complex task. Especially dynamic behaviour, e.g. changing application traffic, mobility of subnetworks, or changing propagation environments require fast adaptation to meet application requirements without service interruption.

[0009] Disclosure of the invention

[0010] According to aspects of the invention a method with the features of claim 1 , a computer program with the features of claim 9, a central subnetwork management entity with the features of claim 10 as well as a computer-readable storage medium with the features of claim 12 are provided. Further features and details of the invention are disclosed in the respective dependent claims, the description, and the drawings. Features and details described in the context to the method also correspond to the computer program according to the invention, the central, subnetwork management entity according to the invention as well as the computer-readable storage medium according to the invention, and vice versa in each case.

[0011] According to an aspect of the invention a method for managing at least two subnetworks is provided, the method comprising the following steps, wherein the steps may be carried out by a central subnetwork managing entity, in particular repeatedly and / or successively. Preferably, the subnetworks are part of a radio or wireless communication network. Specially, the subnetworks may be radio or wireless communication networks, e.g., according to one of the IEEE 802.11 or 3GPP standards.

[0012] In a first step, user information and / or network information, preferably a channel information, is collected from the at least two subnetworks.

[0013] A subnetwork can be referred to a segregated portion of a network infrastructure delineated for specific operational purposes. It can be characterized by distinct configurations, management policies, and functional responsibilities, aimed at optimizing network performance, enhancing security measures, or facilitating administrative tasks. User information can be understood as information related to user related aspects regarding a user management or application requirements such as for example criticality of service or mobility of user devices in a subnetwork or the like.

[0014] Network information, in particular channel information or channel state information, may be specified as information regarding network related aspects of network management such as for example power allocation, time and resource scheduling, interference monitoring or management for a subnetwork.

[0015] In a next step, a suitable pre-configuration for each of the at least two subnetworks is derived based on the collected information.

[0016] This allows to specify a configuration depending on the respective network and / or user conditions for each subnetwork individually.

[0017] In a next step, the derived pre-configuration is initialized for each of the at least two subnetworks. Pre-configuring may enable a more efficient central management of the at least subnetworks and allows a faster deployment. The pre-configuration is received before the at least two subnetworks become active. The configuration can have temporary validity and should be updated regularly.

[0018] In a next step, coordination of the at least two pre-configured subnetworks is managed, wherein the coordination is specified as a traffic and / or a resource management. The at least two subnetworks are actively managed or coordinated by the CSNM entity. This allows for better coordination and allocation of network resources in the at least two subnetworks. Further, this has the advantage of prioritizing critical applications and services, ensuring they receive sufficient resources to meet performance requirements. This advantageously improves for a better Quality of Service for end-users and enhances their overall experience.

[0019] In a further example, during the initializing, the method comprises at least one of the following steps:

[0020] Configuring at least one setting for a subnetwork operation, wherein the at least one setting comprise a frequency re-use factor, bandwidth, frequency bands, transmission power, time slot allocation or the like,

[0021] Specifying at least one parameter for a subnetwork operation such as a requirement for quality of service, a security setting and / or a traffic priority level.

[0022] Configuring settings or specifying parameters for subnetwork operations may offer advantages such as improved network performance, efficient resource allocation, customized QoS, enhanced security, traffic prioritization, flexible network management, or adaptability to dynamic environments. This allows to achieve a more robust and reliable network infrastructure capable of meeting the diverse needs of users and applications.

[0023] In an alternative example, the method comprises the further following steps: Monitoring a user condition of each of the at least two subnetworks, wherein the user condition is based on a behavior of utilized applications in the respective subnetwork of the at least two subnetworks, Monitoring a network condition of the respective subnetwork of the at least two subnetworks,

[0024] Evaluating a need for adapting a configuration of the respective subnetwork of the at least two subnetworks based on an analysis of the monitored conditions,

[0025] Adapting the configuration of the respective subnetwork of the at least two subnetworks if the result of the analysis results in a deviation with respect to one of the monitored conditions.

[0026] Monitoring user conditions allows to better understand user needs and preferences. By adapting configurations based on this monitoring, a subnetwork can be optimized to deliver a more tailored and satisfactory user experience. Further, monitoring network conditions has the advantage to enabling a real-time visibility into factors such as traffic load, congestion, and latency. By evaluating these conditions and adapting a respective configuration accordingly, network performance can be optimized to ensure smooth and reliable operation. Furthermore, Monitoring network conditions allows for the detection of security threats or anomalies that may indicate unauthorized access or malicious activity. By adapting configurations in response to these conditions, networks can strengthen security measures and mitigate potential risks, safeguarding sensitive data and infrastructure. By continually evaluating and adapting configurations based on analysis of monitored conditions, networks can undergo continuous improvement and optimization over time. This iterative process enables networks to adapt to changing requirements, and usage patterns, ensuring ongoing performance enhancements and operational efficiency.

[0027] In an alternative example, during the managing, the method comprises the following step:

[0028] Coordinating a radio access for a subnetwork device for each of the at least two subnetworks.

[0029] By coordinating radio access, the central management entity can ensure and improve efficient utilization of the available spectrum across multiple subnetworks with the goal to minimize interference and maximize throughput. By coordinating radio access parameters such as transmission power and frequency allocation, the central management entity can mitigate interference between neighboring subnetworks. This advantageously reduces signal degradation and improves the reliability of wireless communication within each subnetwork.

[0030] In an alternative example, during the managing, the method comprises the following step:

[0031] Establishing a scheduling framework for each subnetwork controller of the at least two subnetworks, wherein the scheduling framework specifies a coordination with respect to each subnetwork controller.

[0032] The framework allows to centrally allocate resources within each subnetwork, ensuring that resources are utilized effectively based on the specific requirements and demands of the subnetwork. Further, this has the advantage to coordinate and control resource usage more effectively.

[0033] According to another example, during the collecting the method comprises the further following step:

[0034] Collecting the user and / or network information via a respective subnetwork controller of the at least two subnetworks, wherein each subnetwork controller aggregates the user information and / or a sensing information received from at least one subnetwork device in the respective subnetwork, wherein the sensing information is collected to enable each subnetwork controller to send the sensing information as network information to the central subnetwork managing entity.

[0035] The collecting of respective user and network information at subnetwork level allows to manage the current state and dynamics of each subnetwork more efficiently. Further, collecting network information, particularly sensing information, from a subnetwork the entity can advantageously monitor changes in network or channel conditions, network congestion, and user behavior. This allows to proactively adjust network parameters and configurations to maintain optimal performance in response to varying conditions.

[0036] In an alternative example, the central subnetwork managing entity comprises a user management function and / or a network management function, wherein the user management function manages the user and application related activities in a respective subnetwork, and, wherein the network management function manages the network related conditions and / or activities.

[0037] This has the advantage to manage and / or optimize subnetwork configurations more effectively by considering user, application and network aspects related to a respective subnetwork. This split functionality of the central subnetwork management entity further allows to efficiently manage and coordinate firstly the user applications that require a communication service with a certain QoS guarantee, for example a deterministic communication of the subnetwork devices, secondly the subnetwork providing communication services and thus enabling an application, and thirdly the interfaces, for example software APIs that enable intelligent management among different sub-networks while maintaining user requirements.

[0038] According to another example, during the collecting the method comprises at least one of the following steps:

[0039] Collecting the user and / or network information, preferably a channel state information, directly from a subnetwork device in a respective subnetwork of the at least two subnetworks.

[0040] This allows to faster collect information about user and / or network conditions, including signal strength, interference levels, and channel quality. Further, this allows to respond quickly to changing conditions, such as addressing congestion or optimizing resource allocation to improve overall network performance of the subnetwork.

[0041] In another aspect of the invention a computer program may be provided, in particular a computer program product, comprising instructions which, when the computer program is executed by a central subnetwork management entity, cause the central subnetwork management entity to carry out the method according to the invention. Thus, the central subnetwork management entity brings the same advantages as have been described in detail with reference to the method according to the invention.

[0042] In another aspect of the invention a central subnetwork management entity may be provided, comprising means for carrying out the method according to the invention. Thus, central subnetwork management entity brings the same advantages as have been described in detail with reference to the method according to the invention.

[0043] According to another example, the central subnetwork management entity comprises an interface for interacting with at least one further central subnetwork management entity. This allows for a better and more efficient interaction between central subnetwork management entities.

[0044] According to another aspect of the invention a computer-readable storage medium may be provided which comprises the computer program according to the invention and / or instructions which, when executed by a central subnetwork management entity, cause the central subnetwork management entity to carry out the steps of the method according to the invention. The storage medium may be formed as a data storage device such as a hard disk and / or a non-volatile memory and / or a memory card and / or a solid state drive. The storage medium may, for example, be integrated into the central subnetwork management entity.

[0045] Furthermore, the method according to the invention may be implemented as a computer-implemented method. Alternatively, or additionally, at least one of the disclosed method steps may be computer-implemented and / or automated.

[0046] Further advantages, features and details of the invention will be apparent from the following description, in which embodiments of the invention are described in detail with reference to the drawings. In this context, the features mentioned in the claims and in the description may each be essential to the invention individually or in any combination. Showing:

[0047] Fig. 1 : A method, computer program, a storage medium and apparatus according to embodiments of the invention,

[0048] Fig. 2: a schematic diagram according to embodiments of the invention,

[0049] Fig. 3: a further schematic diagram according to embodiments of the invention, Fig. 4: a schematic overview according to embodiments of the invention, and Fig. 5: a schematic flow diagram according to embodiments of the invention.

[0050] In the following figures, the identical reference signs are used for the same technical features even of different embodiment examples.

[0051] The main idea of the invention relates to a Central Sub-Network Management and

[0052] Coordination (CSNM) Entity 10, which is a central orchestrator of multiple subnetworks 30, 40, 50, 60 as shown in Fig. 2 and Fig. 3.

[0053] The core tasks of the CSNM entity 10 can be split into two categories, firstly a user management function 11 and network management function 12 as depicted in Fig. 2.

[0054] The CSNM entity 10 may enable and / or coordinate a centralized optimization regarding traffic management and resource coordination among subnetworks 30, 40 as shown in Fig. 2. Each subnetwork 30, 40 has additionally a local Subnetwork Controller 31 , 41 , which is responsible to manage tasks that can be handled locally and may not require coordination among the subnetworks 30, 40.

[0055] The user management function 11 may consider various application requirements and other user-related aspects such as a criticality of service, mobility of subnetwork devices 35, 45 or similar. Exemplary, three different components to be controlled are shown as subnetwork devices 35, 45 such as for example sensors 35a, 45a (as a data source), controllers 35b, 45b (as a data sink and source), and actuators 35c, 45c (as a data sink). However, the range of applications and / or devices 35, 45 may not limited to any specific application, a sensor 35a, 45a for example could be a sensor feeding a real-time controller, a high-bandwidth video camera, or a low-power loT sensor without timing constraints. There are various options how the subnetwork devices 35, 45 may transmit their information to the User Management function 11 . Subnetwork devices 35, 45 may communicate directly with the User management function 11 of the CSNM entity 10. Alternatively, each Subnetwork Controller 31 , 41 can aggregate the user information in a first step and then transmit them jointly to the CSNM entity 10. Further, it may be possible that the Subnetwork Controller 31 , 41 derives a local pre-configuration for the respective subnetwork 30, 40 and transfers user information in a compressed way to reduce configuration and transmission load between the CSNM entity 10 and each subnetwork 30, 40. The CSNM entity 10 further comprises a network management function 12. This function 12 may act as a central coordination function and as a control function for network-related aspects. This includes for example function such as power allocation, time and resource scheduling, interference monitoring and / or management for the subnetwork 30, 40. The Subnetwork Controller 31 , 41 per subnetwork 30, 40 may manage resources within each respective subnetwork as granted by the CSNM entity 10. The Subnetwork Controller 31 , 41 may function as a proxy towards the Network Management function 12 and may manage resource requests, negotiations, and can grant these related to the subnetwork 30, 40.

[0056] It should be understood that the network management is carried out as a local network optimization control loop in the subnetwork 30, 40, and is performed as a coordinated optimization control loop in the CSNM entity 10. While the local loop requires a fast adaptation, for example on a per transmission time-slot level, the CSNM entity may tolerate slower adaptation.

[0057] The key task of the CSNM entity 10 is deriving continuously optimized subnetwork configurations by taking user and network aspects into account. It acts hence as a proxy for three important aspects:

[0058] 1) user applications that require, in the most demanding case, deterministic communication (sensor, control, actuators),

[0059] 2) the subnetwork providing communication services and thus enabling this application, and

[0060] 3) the software APIs that enable intelligent management among different sub-networks 30, 40, while maintaining user requirements.

[0061] Further, the coordination and management tasks of the CSNM entity 10 can be split into two main parts. Firstly, a static pre-configuration provided by the CSNM entity 10 before a subnetwork 30, 40 may become operational. This may include aspects which remain static or remain valid for longer periods of time. For example, stream configurations, instantaneous traffic load from an application, etc., as well as an initial radio configuration. Then, there may be an active management during operation that addresses aspects requiring dynamic adaptation such as interference management.

[0062] Fig. 3 depicts a further schematic diagram according to embodiments of the invention. In particular Fig. 3 shows an example for an inter-CSNM coordination between two CSNM entities 10, 20 and several subnetworks 30, 40, 50, 60 with their respective subnetwork controllers 31 , 41 , 51 , 61 . The CSNM entities 10, 20 can communicate between each other via an interface 70, for example to coordinate resource usage between them, as depicted in Fig. 3.

[0063] Fig. 4 shows a schematic overview according to embodiments of the invention. Fig. 4 particularly depicts different states or stages of a subnetwork 30, 40 with respect to a CSNM configuration.

[0064] In the initial state, called subnetwork idle 401 , the subnetwork 30, 40 has not yet received any configuration from a CSNM entity 10. In this state, operation may be either prohibited, or only possible with a known global default setting to avoid any interference.

[0065] In a further state, called subnetwork pre-configured 402, the subnetwork 30, 40 may have received an initial pre-configuration from the CSNM entity 10 based on its requirements and network state. The pre-configuration can be received before the subnetwork 30, 40 becomes active. The configuration may only have a temporary validity 410 and should be updated regularly.

[0066] In the next state, called actively managed 403, the subnetwork 30, 40 may be actively managed by the CSNM entity 10. This should be the normal operation mode of the subnetwork 30, 40. In case, the connection between the CSNM entity 10 and the subnetwork 30, 40 is lost 420 or unavailable 420, for example, due to a poor signal reception, interruption during handover, or any other form of communication error between the Subnetwork Controller 31 , 41 and CSNM entity 10, the state of the subnetwork 30, 40 may change to a temporary autonomous operation 404.

[0067] In such a mode, called temporary autonomous operation 404, the subnetwork 30, 40 may be required to continue operation, either fully, or with some limitations. User requirements for subnetwork applications should be met without interruption in this mode. However, the subnetwork 30, 40 may only last for a certain duration in this mode with its pre-configuration. Certain conditions can cause the subnetwork 30, 40 to return to idle mode 401 , usually associated with a deviation from the system state during which the subnetwork pre-configuration was received.

[0068] For example, if the mobility of the subnetwork 30, 40 may exceed a certain preconsidered area, the switch to idle mode 401 may be triggered to prevent unobservable interference. In another example, a timeout can be used for this task.

[0069] Fig. 5 shows a schematic flow diagram according to embodiments of the invention, in particular an overview on ta exemplary step-by-step configuration procedure. The tasks of the CSNM entity 10 and the exchanged information over the interfaces between CSNM entity 10 and a Subnetwork Controller 31 , 41 may be as follows:

[0070] In step 501 user information from the subnetwork devices 35, 45 may be collected and transmitted to the User Management function 11 of the CSNM entity 10. This information can comprise, for example, stream information such as the stream source and sink of each data stream, the timing behaviour of frame generation and processing between sensor, controller, and actuator. Further, it may comprise a traffic characterization such as cycle time or inter-arrival time, packet size, latency bound, a measure for the criticality of the frame, e.g. tolerance to packet losses.

[0071] Furthermore, the information could include non-network related aspects that might be useful as assistance information in the network management process, such as the location of subnetwork devices, mobility models, known mobility routes, inter-device mobility, i.e. relative location changes of subnetwork device to each other, etc.

[0072] In step 502, a subnetwork controller 31 , 41 in each subnetwork 30, 40 may collect network information such as for example a sensing information via reporting mechanisms from each subnetwork device 35, 45 to create and provide network information, particularly channel state information, of the subnetwork 30, 40 to the Network Managing function 12 of the CSNM entity 10. The CSNM entity 10 does not necessarily require all network information like for example commonly used in 3GPP values such as RSRP, RSRQ, SINR, or the like. As shown in Fig. 2, some network optimization remains local in the subnetwork 30, 40, only information relevant to the CSNM entity 10 may be conveyed there. This may include for example information on the required transmit power within the subnetwork 30, 40 to reach individual devices, especially on the edge of the subnetwork 30, 40. Further, it can be of interest to the CSNM entity 10 how much of the bandwidth is required for the subnetwork 30, 40. This value may be influenced by the SINR, which impacts for example the modulation and coding scheme and hence the spectral efficiency. The overall subnetwork channel report as a type of network information should give the CSNM entity 10 an indication how much communication resources are required. In step 503, the CSNM entity may derive suitable pre-configuration for each subnetwork 30, 40 based on the user and network information collected in Step 501 and 502. It can initialize the configuration for the Subnetwork Controller 31 , 41 . It may also set parameters such as the frequency re-use factor, time slot allocation, total bandwidth, frequency bands, and maximum power. Further, it may also define parameters like quality of service (QoS) requirements, traffic priority levels, and security settings to allow more personalized and applicationspecific configurations.

[0073] In step 504, the CSNM entity 10 continuously monitors the application behaviour if the application provides the necessary APIs to access this information. It can provide valuable information for network optimization, such as mobility trajectories of the subnetwork or its users, the application condition, varying criticality of the current service, or imminent changes to the traffic characteristics.

[0074] In step 505, the CSNM entity may continuously monitor the network conditions of the subnetwork 30, 40 to detect necessary changes, e.g., due to mobility, worsening channel conditions which require higher bandwidth or power allocation or increasing interference levels due to proximity of other subnetworks. This may comprise for example, a tracking of metrics like end-to-end latency, jitter, packet loss, interference, and resource utilization. This information may be used in Step 506 to adapt the subnetwork 30, 40, as well as information from Step 504.

[0075] In step 506, the CSNM entity 10 may manage the resource usage of each subnetwork 30, 40. The entity 10 can influence the radio access decisions of the subnetworks 30, 40, with two possible modes:

[0076] In Mode 1 the CSNM entity can assume a full radio access, with the subnetwork 30, 40 functioning as central scheduler. This closely aligns with traditional cellular communication, where the base station needs to actively grant resources every other time interval to the users.

[0077] In Mode 2 the CSNM entity 10 can establish a broader scheduling framework with defined boundary constraints, within which the subnetworks 30, 40 operate freely. The constraints are modified in larger timescales compared to the Mode 1 , whenever, for example, interference might be imminent. For instance, it might dictate that a subnetwork 30, 40 should use Time Division Multiple Access (TDMA), where only a predefined sequence of time slot might be allocated to this subnetwork. Alternatively, a subnetwork might be configured to use Frequency Division Multiple Access (FDMA) within certain frequency bands, where the subnetworks manage their own detailed scheduling within these constraints. Alternatively, a combination of allocation methods might be used with certain constraints. In either operation mode, the CSNM entity may consistently receive performance data from an application and / or a subnetwork 30, 40, which it uses to decide if a configuration change might be necessary. For instance, if performance data indicates recurring network congestion at certain times, it might adjust bandwidth allocation or traffic scheduling parameters.

[0078] Further, the CSNM entity 10 might utilize advanced machine learning techniques, to proactively adapt its resource coordination and allocation policies based on these performance metrics, optimizing network performance over time. This iterative approach ensures that the subnetwork 30, 40 is continually optimized to meet changing conditions and requirements. Each change is data-driven, based on real-time performance metrics, and the system is able to adapt proactively to enhance network performance and reliability.

[0079] In another embodiment, the CSNM entity 10 can be implemented as part of a 3GPP base station, e.g. a gNB. At least the network management function 12 may be implemented in the RAN, for example in the Radio Resource Control (RRC). The coordination among multiple CSNM entities 10, 20 could then be implemented over the X2 or Xn interface 70 between the base stations.

[0080] In another embodiment, the CSNM entity 10 might be, at least partially, part of a so called xApp inside the RAN Intelligent Controller (RIC). Exploiting the E2 interface as standardized in open RAN the entity 10 can be used to manage and monitor a network state of subnetworks. Further the entity 10 can apply policies tailored to individual subnetworks 30, 40. This has the advantage that user information can be easily fed into the system via the xApp as form of enrichment information.

[0081] In another embodiment, the CSNM entity 10 may be implemented for example in a gNB. The entity 10 may manage a 3GPP sidelink-based subnetwork. Using for example sidelink mode 1 , the gNB can control resource assignment to subnetwork devices via a Downlink Control Information (DCI) over the Uu interface to the UE. The CSNM would at least partially be then part of the (RRC).

[0082] In another embodiment, the radio technology could be non-3GPP, like for example Bluetooth. Network management could then be centrally coordinated by introducing a centralized instance 10 that assigns bands or frequency hopping configuration to individual subnetworks to mitigate interference among those.

[0083] In another embodiment, the radio technology could be WiFi, where a central WiFi coordination device 10 could take the role of the CSNM entity 10. This may be possible in larger WiFi Multi-AP deployments. The CSNM entity 10 could manage interference among subnetworks within a multi-access point WiFi network, for example, by assigning WiFi bands intelligently to subnetworks between neighbouring WiFi access points to avoid interference.

[0084] The above explanation of the embodiments describes the present invention in the context of examples. Of course, individual features of the embodiments can be freely combined with each other, provided that this is technically reasonable, without leaving the scope of the present invention.

Claims

Claims1 . A method (100) for managing at least two subnetworks (30, 40), comprising the following steps carried out by a central subnetwork managing entity (10):Collecting (101) user information and / or network information from the at least two subnetworks (30,40),Deriving (102) a suitable pre-configuration for each of the at least two subnetworks (30,40) based on the collected information, Initializing (103) the derived pre-configuration for each of the at least two subnetworks (30, 40),Managing (104) a coordination of the at least two pre-configured subnetworks (30, 40), wherein the coordination is specified as a traffic and / or a resource management.

2. The method (100) of claim 1 , characterized in that during the initializing (103), the method comprises at least one of the following steps:Configuring at least one setting for a subnetwork operation, wherein the at least one setting comprise a frequency re-use factor, bandwidth, frequency bands, transmission power, time slot allocation or the like,Specifying at least one parameter for a subnetwork operation such as a requirement for quality of service, a security setting and / or a traffic priority level.

3. The method (100) of any one of the preceding claims, characterized in that the method (100) comprises the further following steps:Monitoring a user condition of each of the at least two subnetworks (30,40), wherein the user condition is based on a behaviour of utilized applications in the respective subnetwork of the at least two subnetworks (30, 40),Monitoring a network condition of the respective subnetwork of the at least two subnetworks (30, 40),Evaluating a need for adapting a configuration of the respective subnetwork of the at least two subnetworks (30, 40) based on an analysis of the monitored conditions, Adapting the configuration of the respective subnetwork of the at least two subnetworks (30, 40) if the result of the analysis results in a deviation with respect to one of the monitored conditions.

4. The method (100) of any one of the preceding claims, characterized in that during the managing (104), the method (100) comprises the following step:Coordinating a radio access for a subnetwork device (35, 45) for each of the at least two subnetworks (30, 40).

5. The method (100) of any one of the preceding claims, characterized in that during the managing (104), the method (100) comprises the following step:Establishing a scheduling framework for each subnetwork controller (31 , 41) of the at least two subnetworks (30, 40), wherein the scheduling framework specifies a coordination with respect to each subnetwork controller (31 , 41).

6. The method (100) of any one of the preceding claims, characterized in that, during the collecting (101) the method (100) comprises the further following step:Collecting the user and / or network information via a respective subnetwork controller (31 , 41) of the at least two subnetworks (30, 40), wherein each subnetwork controller (31 , 41) aggregates the user information and / or a sensing information received from at least one subnetwork device (35, 45) in the respective subnetwork (30, 40), wherein the sensing information is collected to enable each subnetwork controller (31 , 41) to send the sensing information as the network information to the central subnetwork managing entity (10).

7. The method (100) of any one of the preceding claims,characterized in that, the central subnetwork managing entity (10) comprises a user management function (11) and / or a network management function (12), wherein the user management function (11 ) manages the user and application related activities in a respective subnetwork (30, 40), and, wherein the network management function (12) manages the network related conditions and / or activities.

8. The method (100) of any one of the preceding claims, characterized in that, during the collecting (101) the method (100) comprises at least one of the following steps:Collecting the user and / or network information directly from a subnetwork device (35, 45) in a respective subnetwork of the at least two subnetworks (30, 40).

9. A computer program (90), comprising instructions which, when the computer program (90) is executed by a central subnetwork management entity (10), cause the central subnetwork management entity (10) to carry out the method (100) of any one of claims 1 to 8.

10. Central subnetwork management entity (10), comprising means for carrying out the method (100) of any one of claims 1 to 8.11 . Central subnetwork management entity (10) of claim 10, characterized in that, the entity (10) comprises an interface (70) for interacting with at least one further central subnetwork management entity (20).

12. A computer-readable storage medium (15) comprising instructions which, when executed by a central subnetwork management entity (10), cause the central subnetwork management entity (10) to carry out the steps of the method (100) of any one of claims 1 to 8.

Images