Radio communication device for providing locally defined park network for industrial environment

Abstract

The proposed embodiments relate to a radio communication device for providing a locally defined park network for an industrial environment. The radio communication device may include one or more mobile entities including at least one radio unit for operating a radio front end that maintains the park network.

Description

Technical Field

[0001] The disclosed embodiments generally relate to the field of industrial networks. In particular, the disclosed embodiments relate to a radio communication device for providing a locally defined campus network for an industrial environment. Background Art

[0002] An industrial campus network can operate on one or more geographically restricted sites that participate in one or more private networks of industrial sites such as factory sites, ports, airports, or energy plants.

[0003] Access to the campus network is typically limited to the personnel and devices that are attached to this campus network and operate within one or more sites that define the campus. In other words, for the purpose of mobile communication and / or data exchange, the industrial campus network specifically provides resources to its members, and this exclusivity does not mean that the industrial campus network will be hidden or isolated from third parties and / or public communication networks, which can operate in parallel at the site. The visible coexistence of the industrial campus network (although not automatically accessible) with other communication networks means that the campus network is also subject to the local operating rules of the communication system.

[0004] Today's campus networks are built by integrating infrastructure sites into the industrial sites on-site. Therefore, the campus network largely depends on the static setting of the infrastructure on the campus site. This static infrastructure greatly reduces the flexibility of transferring existing or similar infrastructure concepts to other potentially more dynamic scenarios, which would be particularly beneficial for industrial applications. Summary of the Invention

[0005] According to one aspect of the embodiment, a radio communication device is provided that can provide higher flexibility in applying an already applied or similar infrastructure concept to other more dynamic scenarios.

[0006] According to one aspect of the present invention, a radio communication device for providing a locally defined campus network for an industrial environment is proposed, the radio communication device including one or more mobile entities, the mobile entity including at least one radio unit for operating and maintaining the radio front end of the campus network. Brief Description of the Drawings

[0007] The objects and further advantages of the present invention will become more apparent and easier to understand from the following description of the preferred embodiments in conjunction with the drawings, in which:

[0008] Figure 1 A radio communication system according to a first embodiment is illustrated;

[0009] Figure 2Illustrates a radio communication system according to a second embodiment;

[0010] Figure 3 Illustrates a radio communication system according to a third embodiment;

[0011] Figure 4 Illustrates a radio communication system according to a fourth embodiment;

[0012] Figure 5 Illustrates a radio communication system according to a fifth embodiment;

[0013] Figure 6 Illustrates a radio communication system according to a sixth embodiment; and

[0014] Figure 7 Illustrates a radio communication system according to a seventh embodiment. Detailed Description

[0015] The campus network may be the preferred choice for high-performance 5G mobile networks currently dedicated to industrial applications and will maintain this position for future generations of mobile networks (e.g., 6G). The operation of the campus network can be established by licensing private 5G campus network frequencies to one or more desired locations and integrating its own 5G infrastructure into the on-site industrial network, such that all nodes (e.g., AGVs, production machines, users with mobile devices) have transparent access to the non-public private campus network using wired, wireless, and / or mobile connections.

[0016] The currently dedicated infrastructure (i.e., infrastructure designed for a specific on-site industrial network) has been static so far, as it greatly reduces the flexibility to transfer the dedicated concept to other more dynamic scenarios, which may be more beneficial for industrial applications.

[0017] This embodiment alleviates these and other limitations by extending the concept of mobility from the side of the mobile user equipment (commonly referred to as UE in a mobile network) to parts of the campus network infrastructure itself. This extension of mobility may include infrastructure that is to be movable or mobile during the operation of the network.

[0018] Figure 1 Illustrates a schematic architecture diagram of an example next-generation communication system according to an embodiment of the present invention. A radio communication device RCA for establishing at least one locally defined campus network includes:

[0019] - A mobile entity MBE, which includes one or more radio units for operating and maintaining the radio front end of the campus network, where three radio units RU1, RU2, RUN are shown here;

[0020] - A plurality of network function nodes CNL, TMG, SMO, RIC, UPF, CRE assigned to a shared infrastructure edge cloud EDC, where the mobile entity MBE contributes computing resources to at least one of the plurality of network function nodes CNL, TMG, SMO, RIC, UPF, CRE at least partially;

[0021] - The plurality of network function nodes CNL, TMG, SMO, RIC, UPF, CRE include a trajectory node TMG for collecting and tracking trajectory data of the mobile entity MBE and a positioning node CNL for using the trajectory data to identify locations to be covered by a locally defined campus network.

[0022] For clarity reasons, the radio communication device RCA (part representing the whole) according to various embodiments described herein is sometimes referred to as the mobile entity MBE, because the mobile entity MBE can be the main bearer, or alternatively, constitute the actual device of the radio communication device RCA according to the embodiment.

[0023] As shown in the drawings, a locally defined campus network may include one or more networks or network segments associated with a first industrial site ST1 and a second industrial site ST2 (each network or network segment is represented by an elliptical contour respectively). These networks participating in or associated with the locally defined campus network may be locally separated, or alternatively located together or combined. In the latter case where the networks participating in the locally defined campus network are located together or combined, the network may be organized as a subnet or network segment within the locally defined campus network.

[0024] The first industrial site ST1 and the second industrial site ST2 may be organized in a manner corresponding to the spatial distribution of an industrial complex (such as a distributed factory site) including an office building and a more distant logistics center according to their geographical locations. The increasing flexibility of the spatial distribution of the industrial complex may mean that the ownership of industrial buildings or real estate becomes mandatory, or even represents an obstacle in the case of frequent relocations of operations. Once the current efforts have achieved the result of making the company's operating resources so flexible (making it easy to convert industrial operations), further development will also require that the location of industrial sites may or must be repositioned according to economic or operational needs. Embodiments strive to predict these future developments and provide solutions for such flexibility regarding the campus network used for data exchange for industrial operations, office operations, and / or for communication. According to the nomenclature of the Universal Mobile Telecommunications System (UMTS) and 3GPP Long Term Evolution (LTE), all mobile or wired devices, nodes, servers, or clients that may be involved in this data exchange are hereinafter referred to as user equipment UE1,..., UE5.

[0025] It should be noted that in Figure 1 the example in, only the second user equipment UE2, and the second user equipment UE2 and the fourth user equipment UE4 participate in the campus network, while the first user equipment UE1, the third user equipment UE3, and the fifth user equipment UE5 do not participate in the network currently or permanently. Although the second user equipment UE2 and the fourth user equipment UE4 are located at the first industrial site ST1 and the locally separated second industrial site ST2 respectively, both the user equipment UE2 and the user equipment UE4 participate in the same campus network. As mentioned above, according to the embodiment shown in Figure 1 , two ellipsoidal networks respectively associated with the first industrial site ST1 and the second industrial site ST2 participate in the campus network.

[0026] The network function nodes CNL, TMG, SMO, RIC, UPF, CRE in the mobile entity MBE of the radio communication apparatus RCA may more specifically include a positioning node CNL, a trajectory node TMG, a service management and orchestration node SMO, a radio access network (RAN) intelligent controller RIC, a user plane function node UPF, and a core function node, as further explained below. One or more of the network function nodes CNL, TMG, SMO, RIC, UPF, CRE may be connected through the infrastructure edge cloud EDC for connecting network functions, network function nodes, and / or generally for hosting computing applications.

[0027] The trajectory node TMG may include functions for tracking and / or following the trajectory of the mobile entity MBE, and optionally functions for managing and / or controlling the navigation of the mobile entity MBE. Tracking the trajectory may include monitoring the geographical location, course, acceleration, and / or speed of the mobile entity MBE. The trajectory node TMG may report trajectory data to the positioning node CNL, as further explained below. Managing and / or controlling the navigation of the mobile entity MBE may include obtaining a target location, a destination, or a specified trajectory for reaching the destination. The trajectory node TMG may include means or interfaces for controlling the course and / or speed of the mobile entity MBE to reach the destination.

[0028] The positioning node CNL or the campus network positioning node CNL supports the identification of the campus network to be served by the radio communication device RCA. Based on the trajectory data received from the trajectory node TMG, the positioning node CNL can use a database to retrieve the campus network on the way and match the data of the retrieved campus network with the campus network detected by the positioning node CNL. The database may include an on-board or local database LDBL assigned to the mobile entity MBE and a remote database LDBR, which may be external to the mobile entity MBE, including a location on a third (not shown) mobile entity, or a fixed location that the mobile entity can access on a specifiable occasion or at a specifiable time interval (such as the home base of the mobile entity MBE). The two databases (the on-board database LDBL and the remote database LDBR) can be synchronized with each other as needed or at an adjustable time interval.

[0029] The positioning node CNL can be arranged to consider the system-specific characteristics of the mobile entity MBE. In an exemplary embodiment of the mobile entity MBE being a satellite, the positioning node CNL can be arranged to provide one or more spot beams and / or at least one communication service on at least one fixed-position spot beam. In the case where the mobile entity MBE is embodied as an AGV or an automated guided vehicle equipped with several locally separated antennas, the positioning node CNL can be covered by different antennas for different sectors.

[0030] The positioning node CNL can interact with the service management and orchestration node SMO to exchange configuration data and / or data related to authentication, authorization, or billing (also referred to as AAA data).

[0031] The positioning node CNL may send the required configuration artifacts related to the connectivity with the Radio Access Network (RAN) Intelligent Controller RIC. As used herein, a configuration artifact may refer to a set of configuration parameters that represent the result of an operational process and / or the result caused by the definition of requirements. Alternatively, as described below, the positioning node CNL may directly send the required configuration artifacts related to connectivity to the Distributed Controller Unit DCU and / or to one or more of the Radio Units RU1, RU2, RUN. The Distributed Controller Unit DCU may include one or more (not shown) Distributed Units (also referred to as DUs in the Fifth Generation technology standard or simply 5G for broadband cellular networks) and / or one or more (not shown) Centralized Units (also referred to as CUs in 5G). The Distributed Controller Unit DCU may include any functional diversity of the distributed or central units that provide northbound support (in the upward direction in the figures) to the higher layers of the protocol stack (e.g., handled by the User Plane Function Node UPF), while providing southbound support (i.e., in the downward direction in the figures) to the lower layers of the protocol stack (e.g., handled by the User Plane Function Node UPF).

[0032] The positioning node CNL may assume the responsibility for configuring the connection mode at the corresponding User Plane Function Node UPF. The connection mode may affect virtual network functions, coverage, QoS definition, etc. The positioning node CNL may create a schedule for handover from the current Mobile Entity MBE to one or more other mobile entities via the currently operating campus network. For example, this may be the case when radio-supported industrial sites ST1, ST2 are no longer served by only one Mobile Entity MBE, but rather by several mobile entities. Another use case may require a handover to be scheduled on the infrastructure side, thus handing over from the Mobile Entity MBE that currently provides radio coverage to another mobile entity. In addition, the interconnectivity between campus networks hosted on different mobile entities may be controlled and configured by the positioning node CNL, as will be explained in more detail with respect to the embodiments described further below.

[0033] A set of databases may support the positioning node CNL in its operation, among which the already mentioned authorized campus network location database LDBL provided locally at the Mobile Entity MBE is connected to the master authorized campus network location database LDBR. Both of these databases LDBL, LDBR contribute to the distributed database for storing the campus network identifier along with its location. The distributed database and / or the databases LDBL, LDBR may further include the signature of the regulatory body that has approved or registered the current campus network.

[0034] Although the authorized campus network location database LDBL may typically be located on the mobile entity MBE machine, its master database LDBR may be maintained in a remotely accessible location for periodic synchronization. The distributed database and / or databases LDBL, LDBR may further maintain data regarding allowed frequency ranges and / or permitted transmission powers. Additionally, relevant regulatory parameters may be stored in the distributed database and / or databases LDBL, LDBR and utilized by the mobile entity MBE as described.

[0035] Another pair of databases may support the positioning node CNL in its operation, i.e., the local campus network configuration database CDBL provided locally at the mobile entity MBE is connected to the remote campus network configuration database CDBR, and the latter remote database CDBR is the master database of the local database CDBL. Since each campus network may have a specific set of configuration artifacts required for deployment, commissioning, startup, and operation, these configuration artifacts may be advantageously stored in the master database CDBR, which is capable of providing a local copy of the relevant campus network configuration to the local database CDBL, and the local database makes the configuration available to the positioning node CNL.

[0036] Another pair of databases (or, alternatively, active components that support and exchange data) may support the positioning node CNL in its AAA (authentication, authorization, and / or accounting) operation, i.e., the local database ADBL provided locally at the mobile entity MBE is connected to the remote AAA database ADBR, and the latter remote database ADBR is the master database of the local database ADBL. Since the campus network may be integrated within a wireless and / or wired local area network (e.g., a corporate or enterprise network (also known as an information technology or IT network), or an industrial operations technology network (also known as an OT network)), a combined AAA entity (not shown) may be made available separately in the network or in the campus network such that devices connected via the campus network and delivering the correct credentials are authenticated as participating in the corresponding IT network or OT network. Since mobile entities may require a distributed implementation method to manage their data, this combined AAA entity may be represented by the local database ADBL on the mobile entity machine, which synchronizes with the remote AAA database ADBR that serves as the AAA master component or AAA server.

[0037] In Figure 1 and in the figure below, sites ST1, ST2 represent different locations where a campus network may be deployed.

[0038] A mobile entity can provide an interface to the backbone network BNW. This optional interface BNW can allow the extension of the communication range of the mobile entity MBE by connecting the mobile entity MBE to other mobile entities or to the broadband network INT. An example can be a network of direct point-to-point links between satellites, or it can be Figure 1 the optical transmission link of a ground station of an ellipse near the symbolized broadband network INT depicted in

[0039] In the next section, the mobile radio network components involved in communication are described. Although the names of the components described below may be consistent with the terms of a 5G network as used in 3GPP (Third Generation Partnership Project) terminology to indicate their main functions, such names should not be construed as constituting parts, but as examples. Furthermore, the embodiments are not limited in any way to fifth-generation or 5G radio networks or protocols.

[0040] User equipment UE1, …, UE5 or terminals UE1, …, UE5 generally represent devices that are (or at least can be) connected to the campus network via their (not shown) radio interfaces. Terminals UE1, …, UE5 can also act as routers / bridges to other (not shown) local network segments. Thus, the terminal devices UE1, …, UE5 can be embodied as non-mobile or mobile devices, e.g., handheld devices, mobile robots, AGVs, UAVs. Terminals UE1, …, UE5 can also be used to extend the wireless coverage, e.g., acting as repeaters or gateways located on the roof of an industrial building to provide radio coverage within a factory hall.

[0041] The Service Management and Orchestration Node SMO is the main management component of the campus network and interacts with the Location Node CNL. The Service Management and Orchestration Node SMO can receive the verified and authorized configuration artifacts of the campus network that need to be deployed and operated at the current location of the mobile entity.

[0042] Once the mobile entity MBE leaves the area authorized for a certain campus network operation, it can notify the Service Management and Orchestration Node SMO to stop or shut down the operations related to that specific campus network. For this purpose, the Service Management and Orchestration Node SMO can utilize the application programming interface or the API provided by the Core Function Node CRE for reconfiguration.

[0043] The core function node CRE (which can also be referred to as the 5G core) consists of multiple virtualized network functions. Depending on the deployment, only a subset of the core functions defined by 3GPP needs to run locally on the mobile entity MBE. For example, only the access and mobility management function or AMF (not shown) and the session management function or SMF for managing the user equipment UE1, …, UE5 and the user plane function node UPF can be run by the core function node CRE, while other core functions can be hosted at an alternative location outside the infrastructure edge cloud EDC or even outside the radio communication apparatus RCA.

[0044] As defined by 3GPP, the user plane function node UPF terminates the 3GPP connection with the terminals UE1, …, UE5 and has the ability to forward traffic into the data network or local processing capabilities. In addition to the functions specified by 3GPP, according to an embodiment, the user plane function node UPF can be used as an additional gatekeeper to allow conditional access to a specific data network (e.g., a private network) based on locally available information. This locally available information can include the location of one or more of the terminals UE1, …, UE5 and / or the location of the locally authorized campus network, where the latter location can be queried from the locally authorized campus network location database LDBL.

[0045] The RAN intelligent controller RIC provides mechanisms and interfaces to configure and control the radio-related parts of the radio communication apparatus RCA, e.g., one or more radio units RU1, RU2, RUN and / or one or more of the distributed controller units DCU including one or more distributed units or DUs and / or the centralized unit CU included in one or more of the distributed controller units DCU. The configuration and control of the radio-related parts of the radio communication apparatus RCA includes the management of scheduling policies for the air interface or the configuration of cells / beams on the utilized air interface.

[0046] Although the RIC architecture proposed by the O-RAN Alliance (a community of mobile operators, vendors, research, and academic institutions aiming to design a more intelligent, open, virtualized, and fully interoperable radio access network) can be used for this task, according to an embodiment, the RAN intelligent controller RIC can also be made more integrated and customized for specific needs. Such a specific embodiment of the RAN intelligent controller RIC can, for example, include a dedicated interface with a specific implementation of the distributed unit or DU and / or the centralized unit CU included in one or more of the distributed controller units DCU as shown in Figure 1 Alternatively or additionally, the functions of the RAN intelligent controller RIC can also be directly integrated into the service management and orchestration node SMO.

[0047] A distributed controller unit DCU is a unit that can operate as a central unit or CU, or as a distributed unit or DU, or both in cooperation. A distributed controller unit DCU typically refers to a centralized logical node within a wireless network infrastructure. The central unit or CU and the distributed unit DU defined by 3GPP include a radio protocol stack, which includes a control plane and a user plane. The configuration capabilities of the distributed controller unit DCU are exposed via the RAN intelligent controller RIC directly to the service management and orchestration node SMO by using, for example, the O-RAN interface or by using a customized implementation of a transport alternative.

[0048] One or more radio units RU1, RU2, RUN form a radio front end that implements lower physical layer functions as defined in 3GPP and is based on the split options and integration / decomposition levels of the 5G system at hand.

[0049] The embodiments neither require nor impose a specific split option or architecture. The embodiments only assume that relevant parameters of radio characteristics (e.g., beam characteristics, directivity, etc.) can be configured or at least retrieved (as described above for the distributed controller unit DCU) in order to be used in the decision-making and configuration processes in the RAN intelligent controller RIC or the service management and orchestration node SMO.

[0050] As used herein, the terms 5G and New Radio (NR) refer to, but are not limited to, devices, methods, or systems compliant with Release 15 of 3GPP, as well as any modifications, subsequent releases, revisions, or supplements to the New Radio technology, whether licensed or unlicensed.

[0051] Figure 2 Illustrated is the operation of a radio communication apparatus RCA in an alternative embodiment in a radio communication system that can be referred to as a single-site topology.

[0052] According to the single-site topology or single-site scenario depicted in Figure 2 an industrial site ST1 can be served by a campus network hosted by a mobile entity MBE. The connections between terminals UE1, …, UE5 (optionally, the participation of one or more wireless networks (graphically represented by the ellipse at industrial site ST1)) can be realized through a user plane function node UPF hosted on the mobile entity MBE. Terminals UE1, …, UE3 can be embodied as automated guided vehicles or AGVs or as unmanned aerial vehicles or UAVs. One of the terminals, UE1, can additionally act as the mobile entity MBE, serving other terminals UE2, …, UE5 or other wireless industrial devices not shown in Figure 2 the figure.

[0053] The thick lines in the drawings symbolize the possible communication routes of the communication link between the local wireless network via the industrial site ST1 and the broadband network INT, so as to be guided to the mobile entity MBE via the interface of the backbone network BNW, and the mobile entity MBE is connected to the terminals UE1, …, UE3 via its user plane function node UPF, distributed controller unit DCU and radio unit RU1.

[0054] Figure 3 Illustrates the operation of a radio communication device RCA according to an alternative embodiment in a radio communication system that can be referred to as a multi-site topology. According to the Figure 3 multi-site topology or multi-site scenario depicted in, two or more industrial sites ST11A, ST1B can be served by one campus network hosted by one mobile entity MBE.

[0055] Two or more industrial sites ST11A, ST1B can be locally separated and interconnected by the mobile entity MBE. The two industrial networks assigned to the industrial sites ST11A, ST1B and all user devices or terminals UE1, …, UE6 can be connected, or in other words, can be reached within the same network. It will be understood that the basic embodiment shown in Figure 2 can be modified by a large number of possible alternative embodiments such as using multiple radio units RU1 or interconnecting via one or more user plane function nodes UPF.

[0056] Figure 4 Illustrates the operation of a radio communication device RCA according to an alternative embodiment in a radio communication system that can be referred to as multiple single-site topologies.

[0057] According to the Figure 4 multiple single-site topologies or multiple single-site scenarios depicted in, two or more industrial sites ST11A, ST1B can be served by two or more different campus networks hosted by one mobile entity MBE. According to the Figure 4 multiple single-site configurations, it can be understood that for two or more different sites ST1, ST2, hosting the scenarios according to Figure 2 and Figure 3 , each site ST1, ST2 is supplied by a different campus network.

[0058] According to the multiple single-site topologies of this embodiment depicted in Figure 4 , it can allow different campus networks to operate at different locations or at similar locations on different radio frequencies without interference with each other. Different campus networks can generally be isolated, which may mean that users in one campus network do not interfere with users in other campus networks.

[0059] Multiple multi-site topologies (not shown) then allow different multi-site setups to be operated simultaneously on a single mobile entity MBE. As described for the multiple single-site topologies according to Figure 4 , the campus networks are also isolated in the multiple multi-site topologies and do not interfere with each other. It will be understood that the basic embodiment as shown in Figure 4 can be modified by a large number of possible alternative embodiments, such as using one, more than one, or multiple radio units RU1 or interconnecting via one or more user plane function nodes UPF.

[0060] The exemplary embodiments described above with reference to Figures 1 to 4 can be extended over more than one or multiple mobile entities MBE1, MBE2 to create a multi-hop multi-site scenario, or a multi-hop single-site scenario (as shown in Figure 5 ), or a hybrid of both.

[0061] In Figure 5 , a multi-hop single-site scenario is shown, in which the radio communication device RCA includes at least two connected mobile entities MBE1, MBE2. A connection can be established between the first mobile entity MBE1 and the second mobile entity MBE2 via the backbone network BNW. The campus networks on the industrial sites ST1, ST2 are configured using the configuration data created by one or more positioning nodes CNL.

[0062] In addition to the topology variants shown above, more embodiments of the radio communication device RCA can be advantageously implemented by selecting different architecture implementation options as described below. Specifically, the proposed radio communication device RCA can be implemented by aggregating a large number of mobile entities MBE1, MBE2 instead of using only one mobile entity MBE, which enables at least one locally defined campus network for the industrial environment (e.g., the entire 5G infrastructure).

[0063] According to the embodiments related to Figure 1 described above, the entire 5G infrastructure can be implemented using one mobile entity MBE1, which can serve one or more locally defined campus networks within a certain communication range. In different architecture implementation options as shown in the exemplary embodiments according to Figure 6 , multiple mobile entities MBE1, MBE2, …, MBE5 can cooperate to form an infrastructure edge cloud EDC, where computing applications can be hosted. Accordingly, regarding according to as Figure 1The infrastructure edge cloud EDC of a single mobile entity MBE of the embodiment shown, jointly forms an infrastructure edge cloud EDC that can be connected to one or more of the network function nodes CNL, TMG, SMO, RIC, UPF, CRE, and / or local databases or components as described above, specifically the locally authorized campus network location database LDBL, the local campus network configuration database CDBL, the local AAA database ADBL, and / or one or more distributed controller units DCU.

[0064] The exemplary embodiments according to Figure 6 can be used or further developed to deploy 5G infrastructure components on one or more mobile entities MBE1, MBE2, …, MBE5. Each or at least some of the mobile entities MBE1, MBE2, …, MBE5 can be equipped with one or more radio units RUA, RUB1, RUB2, RUC1, RUC2, RUD, RUE1, RUE2.

[0065] One or more radio units RUA, …, RUE2 can provide radio coverage for one or more campus networks operated by the queues of the mobile entities MBE1, MBE2, …, MBE5 as needed. The queues of the mobile entities MBE1, MBE2, …, MBE5 can be used to deploy 5G infrastructure components on one or many mobile systems. Each of the mobile entities MBE1, MBE2, …, MBE5 can be equipped with one or many radio units RUA, …, RUE2 to provide the required coverage for the campus network operated by the queue of the mobile entity MBE1, MBE2, …, MBE5.

[0066] In Figure 7 multiple mobile entity scenarios are shown, in which a large number of mobile entities MBE1, MBE2, …, MBE5 are organized in a hierarchical manner. In one embodiment, a large number of mobile entities MBE1, MBE2, …, MBE5 can be formed by a large number of satellite MBE1, MBE2, …, MBE5.

[0067] For example, a low Earth orbit or LEO satellite constellation MBE1, MBE2, …, MBE5 can provide an access layer ACC for a terrestrial system. The access layer ACC can host radio units RUA, RUB1, RUB2, RUC1, RUC2, RUD, RUE1, RUE2 and / or distributed controller units DCU.

[0068] The LEO satellite constellations MBE1, MBE2, …, MBE5 can be connected to the high-speed communication backbone HSB. The high-speed communication backbone HSB can be formed by a large number of geostationary orbit or GEO satellites, which provide high-speed links (e.g., optical links) between the satellites MBE1, MBE2, …, MBE5 of the LEO constellation and potentially provide high-speed links to the terrestrial backbone network BNW.

[0069] Two constellations (the LEO satellite constellations MBE1, MBE2, …, MBE5 and the GEO constellation not shown) can implement the infrastructure edge cloud EDC, which provides a computing runtime for the campus network and 5G components. One or both of these infrastructure edge clouds EDC can additionally host application components and / or industrial services close to the communication data sources.

[0070] In summary, the proposed embodiments present a radio communication device for providing a locally defined campus network for an industrial environment. The radio communication device can include one or more mobile entities, which include at least one radio unit for operating and maintaining the radio front-end of the campus network.

[0071] The proposed embodiments can enhance the current concept of mobility from the access point or endpoint side to the infrastructure side. This may even involve the infrastructure itself being mobile while the network is in operation. In a specific embodiment, infrastructure-side mobility can be implemented using satellites. The campus network infrastructure (including radio units, core functions such as 5G core, distributed units or DUs, centralized units or CUs, etc.) may reside in one or more satellites orbiting the Earth. Due to the enhanced mobility provided by the proposed embodiments, the campus network can be dynamically deployed in any area or a combination of areas covered by a transmission system such as a satellite.

[0072] Advantageously, the proposed embodiments can provide the deployment of a geographically distributed campus network on demand without relying on a locally fixed infrastructure.

[0073] Advantageously, the proposed embodiments can provide the implementation of a campus network that is dynamically generated and matches a predefined set of boundaries, which has options for physically restricting signal propagation and the association of endpoints with virtual perimeters, geographical boundaries, and / or geofences, thus adding a layer of physical security. In other words, the proposed embodiments can support geofencing in an industrial environment, for example, by restricting the propagation of signals in certain areas.

[0074] The proposed embodiments can easily utilize the flexibility of the hardware and software components introduced by future fifth-generation or 5G or sixth-generation or 6G systems.

[0075] The proposed embodiments enhance the current mobility concept to involve the infrastructure itself using the architectural setup in the campus network topology. The deployment of the radio communication device according to the embodiments may be on both: global systems (such as 6G non-terrestrial networks or satellite systems) and ground-based factory setups in large-scale neutralized and / or local single sites.

[0076] The proposed embodiments provide design reconfigurability of the campus network while additionally providing improved resilience by seamlessly applying built-in capabilities to use handovers on the infrastructure side.

[0077] It is to be understood that the elements and features recited in the appended claims may be combined in different ways to yield new claims that also fall within the scope of the present invention. Thus, although the dependent claims appended below depend only on a single independent claim or a dependent claim, it is to be understood that these dependent claims may alternatively be made to depend on any preceding or subsequent claim, whether independent or dependent, and such new combinations are to be understood to form part of this specification.

[0078] Although the present invention has been described above by reference to various embodiments, it should be understood that many changes and modifications can be made to the described embodiments. Therefore, the foregoing description is intended to be illustrative rather than restrictive, and it is to be understood that all equivalents and / or combinations of embodiments are intended to be included in this description.

Claims

1. A radio communication device for providing at least one locally defined campus network for an industrial environment, the radio communication device comprising: - a mobile entity comprising at least one radio unit for operating and maintaining a radio front end of the campus network; - a plurality of network function nodes assigned to a shared infrastructure edge cloud, the mobile entity contributing at least partially computing resources to at least one of the plurality of network function nodes; - the plurality of network function nodes comprising a trajectory node for collecting and tracking trajectory data of the mobile entity and a positioning node for using the trajectory data to identify locations to be covered by the locally defined campus network.

2. The radio communication device according to claim 1, wherein, The mobile entity is an autonomous mobile entity.

3. The radio communication device according to one of the preceding claims, comprising a network interface for connecting the mobile entity to at least one other mobile entity or to a backbone network.

4. The radio communication device according to one of the preceding claims, comprising a trajectory node for monitoring at least one of the geographical location, course, acceleration and speed of the mobile entity.

5. The radio communication device according to claim 4, the trajectory node comprising at least one interface for exchanging data for controlling the course and / or speed of the mobile entity.

6. The radio communication device according to one of the preceding claims, the positioning node exchanging data related to authentication, authorization or charging of the campus network.

7. The radio communication device according to claim 6, the positioning node exchanging configuration artifacts or configuration parameters with a local or remote database.

8. A radio communication device according to one of the preceding claims, comprising at least two mobile entities wirelessly connected via a backbone network.

9. The radio communication device according to claim 8, the at least two mobile entities being assigned to at least one of the shared infrastructure edge clouds.

10. The radio communication device according to claim 9, the at least two mobile entities being hierarchically organized.

11. A satellite, which forms a mobile entity of a radio communication device according to one of the preceding claims.

12. An automated guided vehicle, which forms a mobile entity of a radio communication device according to one of the preceding claims.

Images