Methods and systems for interaction between 5g and multiple tsc / tsn domains

Abstract

A method (1200) performed by a network node (160, 160c) includes determining (1202) that there are multiple time sensitive communication, TSC, or time sensitive network, TSN, domains (12) in a network. The network node instantiates (1204) at least one virtual bridge (14), where each virtual bridge serves at least one TSC and / or TSN domain.

Description

TECHNICAL FIELD

[0001] The present disclosure relates generally to wireless communication, and more particularly to methods and network nodes for system support of multiple Time-Sensitive Network (TSN) domains. BACKGROUND

[0002] The industry automation sector is currently undergoing a digital transformation whereby, for example, multiple machines, devices, clouds, and people are interconnected, making information accessible from anywhere in the factory. The transparency across processes and assets that results from this transforms the production plant into a cyber-physical production system.

[0003] Time-Sensitive Networking on the wired side and 5G on the wireless side are the communication technologies that enable this transformation. Both technologies are suitable for time-sensitive applications that require deterministic, reliable, and low-latency communication. By introducing TSN and 5G wireless communication, significant benefits can be brought to industrial use cases, for example, due to the increased flexibility of deployment of industrial devices and networks.

[0004] Figure 1 A single TSN system (e.g., a single TSN domain) in a wired deployment is illustrated. In Figure 1 the following traffic use cases are described: Controller-to-Controller (C2C), Controller-to-Device (C2D), and Device-to-Compute (D2cmp). As used herein, a controller refers to a Programmable Logic Controller (PLC), which is an application controller.

[0005] There can be three connection segments in an industrial automation network, as Figure 1 illustrated:

[0006] • Central room / edge cloud,

[0007] • Local machines or machine groups representing production cells,

[0008] • TSN backbone, which in this context refers to an industrial TSN backbone used in industrial automation.

[0009] As depicted in Figure 1 all devices belong to one TSN domain and are thus managed by one Central User Configuration (CUC) / Central Network Configuration (CNC). The central room is a centralized management segment where centralized control and management functions (e.g., centralized PLC, CNC, and automation data acquisition) reside. These functions typically interact with other devices across the entire industrial automation network. The central room can be part of an enterprise edge cloud (e.g., a local automation cloud). The local machine connection segment consists of multiple machines, as in Figure 1The local machines are shown in the middle by machine #1 to machine #N. Each machine is equipped with field devices (e.g. sensors, actuators) and a local PLC. The industrial backbone network provides transport services for the central management segment and the local machine segment, e.g. between the edge cloud and the field devices. The connectivity services can be between different local machines or between the central management layer and the local machines.

[0010] TSN networks can be divided into multiple domains. A CUC / CNC pair is responsible for a TSN domain. A production unit typically uses one TSN domain for communication. Thus, there can be multiple CNCs in an industrial automation network. Figure 2 Fig. 1 illustrates multiple TSN domains. Each TSN domain is controlled and represented by a local CUC and CNC. A TSN domain is defined as a large number of industrial automation devices that are commonly managed.

[0011] In Figure 2 In the middle, for example, production unit / line #1 consists of machines #1 and #2, both of which belong to TSN domain #1. In contrast, in production unit / line #2, each machine can belong to an independent TSN domain. There is also a TSN domain #4 for the backbone network, also referred to as TSN backbone domain 61. Figure 2 The CNC 4 in the backbone network has a higher hierarchy than the other CNCs in the local production units. To allow communication between nodes in different TSN domains, TSN flows across the TSN domain boundaries need to be created, which can also be referred to as inter-TSN domain communication. A lower hierarchy CNC can escalate TSN inter-domain flow establishment requests to a higher hierarchy CNC, which in turn can configure the TSN inter-domain flows, also referred to as TSN flow paths, between TSN domains of lower hierarchy.

[0012] 3GPP TS 23.501 v.16.4.0 has defined an architecture for supporting 5thGeneration Time-Sensitive Networking (5G-TSN) integration. In particular, Figure 3 Fig. 1 illustrates the 3GPP 5G-TSN architecture. A TSN system, which can be a TSN network, a TSN bridge, or an end station, interacts with a 5thGeneration System (5GS) via an Application Function (AF) function. The control and management (C&M) of the TSN system can be a CUC / CNC pair, which can be implemented as part of a Software Defined Network (SDN) controller. 3GPP TS 23.501 also specifies a 5GS bridge model for supporting Time-Sensitive Communication (TSC) and / or TSN, also referred to as Rel-16 bridge model. It is specified that a 5G system can integrate as a TSN bridge with external networks, such a TSN bridge is often referred to as a logical or virtual TSN bridge. The virtual TSN bridge includes a TSN translator function for interoperation between a TSN system and a 5G system, for both user plane and control plane.

[0013] For example, Figure 4 A 3GPP bridge model from 3GPP TS 23.501 is illustrated. Network-side TSN translator (NW-TT) ports at the user plane function (UPF) and device-side TSN translator (DS-TT) ports at the user equipment (UE) act as ports of a virtual TSN bridge. Figure 4 SUMMARY

[0014] The previous methods and systems that provide support for multiple TSN domains present certain problems. For example, a first problem can be that there is no solution on how to adapt the 5GS to support and interact with multiple TSC / TSN domains. As another example, a second problem can be that, according to 3GPP TS 23.501 V16.4.0, the 5GS virtual bridge “assumes that all protocol data unit (PDU) sessions connected via a specific UPF to the same TSN network are handled by the same TSN AF.” That is, according to 3GPP TS 23.501, the 5G system virtual bridge can only interact with a single CNC when deployed in a TSN system.

[0015] As discussed above, the current Rel-16 3GPP model defines a one-to-one mapping between the 5GS virtual bridge and the UPF. This results in the need for a larger number of UPFs when the number of TSN domains is equal to the number of industrial machines (i.e., the number of UPFs required is the same as the number of machines). This one-to-one mapping between the 5GS virtual bridge and the UPF thus hinders the scalability and flexibility of the system and also creates network management problems.

[0016] Certain aspects of the present disclosure and their embodiments can provide solutions to these or other challenges. For example, according to certain embodiments, a method is provided that specifies how the 5GS interacts with multiple TSN domains and multiple non-3GPP network controllers.

[0017] According to certain embodiments, a method performed by a network node includes determining how many TSC and / or TSN domains exist in a network. The network node instantiates at least one virtual bridge, where each virtual bridge serves at least one TSC and / or TSN domain.

[0018] ​In some embodiments, a network node instantiates at least one virtual bridge for each TSC and / or TSN domain of a plurality of TSC and / or TSN domains. The network node is typically a node in a wireless communication network system, wherein the network node provides interaction between the wireless communication system and a plurality of TSN domains and a non-3GPP network controller. The network node can be, for example, a core network node such as an Application Function (AF) or an Operation and Maintenance node (OAM), or another node providing network management functionality.

[0019] According to certain embodiments, a network node comprises processing circuitry configured to determine how many TSC and / or TSN domains are present in a network comprising a plurality of TSC and / or TSN domains, and to instantiate at least one virtual bridge for each TSC and / or TSN domain of the plurality of TSC and / or TSN domains.

[0020] According to certain embodiments, a method performed by a network node comprises determining a set of ports in a network system, and dynamically modeling a first virtual bridge for the set of ports. The method decouples the one-to-one mapping between 5G virtual bridges and UPFs (current 3GPP Rel-16 solution), and allows modeling multiple 5GS virtual bridges even if there is one UPF.

[0021] According to certain embodiments, a network node comprises processing circuitry configured to determine a set of ports in a network system, and to dynamically model a first virtual bridge for the set of ports.

[0022] Certain embodiments can provide one or more of the following technical advantages. For example, certain embodiments propose a new solution for 5GS to support multiple TSN domains. For example, certain embodiments propose that a network management function (e.g., a core network node, an AF, or an OAM) in 5GS can detect or identify how many external TSC / TSN domains are present (e.g., how many CNCs are present). In turn, the network management function can instantiate the required number of 5GS bridges to serve different TSC / TSN domains. For example, the network management function in 5GS can interact with non-3GPP network controllers (e.g., CNCs) based on overall network topology information. The network management function in 5GS can also decide how many 5GS bridges and ports are needed for a TSN domain. Thus, one technical advantage can be that 5GS can provide support for inter-TSN domain communication between different TSN domains. Another technical advantage can be that 5GS can provide communication within one TSN domain. Yet another technical advantage can be that certain embodiments support hierarchical network configuration.

[0023] As another example, certain embodiments propose a port-group based 5G virtual bridge model, and the 5GS can dynamically model virtual bridges based on port groups of the 5GS. This dynamic modeling can be formed, for example, by a network management function in the 5GS. According to certain embodiments, the 5GS can associate this port group with a bridge ID, which can be reported at the AF or other 3GPP network node. Thus, the 5GS virtual bridge can be modeled “per port group of the UPF.” As a result, one technical advantage can be that certain embodiments support interaction with multiple CNCs, such that all 5GS ports can be flexibly divided into several groups, and each port group can be managed by a CNC of a TSN domain. Another technical advantage can be that bridges can be dynamically scaled up and down according to the number of ports reported at the AF, and bridges can be reconfigurable. Yet another technical advantage can be that a one-to-one mapping between 5G virtual bridges and UPFs is no longer necessary.

[0024] Other advantages can be readily apparent to one having skill in the art. Some embodiments can have none, some or all of the recited advantages. BRIEF DESCRIPTION OF DRAWINGS

[0025] For a more complete understanding of the disclosed embodiments and their features and advantages, reference is now made to the following description, taken in conjunction with the accompanying drawings, in which:

[0026] Figure 1 FIG. illustrates a single TSN domain using wired communication in a wired deployment;

[0027] Figure 2 FIG. illustrates multiple TSN domains using wired communication in a wired deployment;

[0028] Figure 3 FIG. illustrates a 3GPP 5G-TSN architecture according to 3GPP TS 23.501 v.16.4.0;

[0029] Figure 4 FIG. illustrates a 3GPP bridge model from 3GPP TS 23.501 v.16.4.0;

[0030] Figure 5 FIG. illustrates support of multiple TSN domains by a 5GS according to certain embodiments;

[0031] Figure 6 FIG. illustrates an example 5GS with one UPF but modeled as multiple virtual bridges according to certain embodiments;

[0032] Figure 7 FIG. illustrates a variant of the example of FIG. 8 according to certain embodiments, in which there are multiple UPFs; Figure 6

[0033] Figure 8 ​Figure illustrates a 5GS virtual bridge according to certain embodiments Figure 6 Another example variant of the above, where more than one virtual bridge can be managed by one CNC of a TSN domain;

[0034] Figure 9 Figure illustrates a 5GS virtual bridge according to certain embodiments Figure 6 Another example variant of the above, where only one 5GS virtual bridge is modeled (one bridge ID can be assigned);

[0035] Figure 10 Figure illustrates an example hierarchical CNC architecture, where a 5GS virtual bridge is part of a TSN backbone domain, according to certain embodiments;

[0036] Figure 11 Figure illustrates an example 5GS virtual bridge acting as its own separate TSN domain, according to certain embodiments;

[0037] Figure 12 Figure illustrates a 5GS virtual bridge interacting with multiple TSC / TSN domains, according to certain embodiments;

[0038] Figure 13 Figure illustrates a 5GS virtual bridge interacting with multiple TSC / TSN domains, according to certain embodiments;

[0039] Figure 14 Figure illustrates an example wireless network, according to certain embodiments;

[0040] Figure 15 Figure illustrates an example network node, according to certain embodiments;

[0041] Figure 16 Figure illustrates an example wireless device, according to certain embodiments;

[0042] Figure 17 Figure illustrates an example user equipment, according to certain embodiments;

[0043] Figure 18 Figure illustrates a virtualization environment in which functions implemented by some embodiments can be virtualized, according to certain embodiments;

[0044] Figure 19 Figure illustrates a telecommunication network connected via an intermediate network to a host computer according to certain embodiments;

[0045] Figure 20 Figure illustrates a general block diagram of a host computer communicating via a base station with a user equipment according to certain embodiments;

[0046] Figure 21 Figure illustrates a method implemented in a communication system according to one embodiment;

[0047] Figure 22FIG. illustrates another method implemented in a communication system, in accordance with one embodiment;

[0048] Figure 23 FIG. illustrates another method implemented in a communication system, in accordance with one embodiment;

[0049] Figure 24 FIG. illustrates another method implemented in a communication system, in accordance with one embodiment;

[0050] Figure 25 FIG. illustrates an example method performed by a network node, in accordance with certain embodiments;

[0051] Figure 26 FIG. illustrates an example virtual computing device, in accordance with certain embodiments;

[0052] Figure 27 FIG. illustrates another example method performed by a network node, in accordance with certain embodiments;

[0053] Figure 28 FIG. illustrates another example virtual computing device, in accordance with certain embodiments;

[0054] Figure 29 FIG. illustrates another example method performed by a network node, in accordance with certain embodiments; and

[0055] Figure 30 FIG. illustrates another example virtual computing device, in accordance with certain embodiments. DETAILED DESCRIPTION

[0056] Some embodiments contemplated herein will now be described in greater detail with reference had to the drawings. Other embodiments, however, are included within the scope of the subject matter disclosed herein, which is not to be interpreted as being limited only to the embodiments set forth herein; rather, these embodiments are provided in order to convey the scope of the subject matter to those skilled in the art.

[0057] Generally, all terms used herein are to be interpreted according to their ordinary meaning in the technical field of the disclosure, unless a different meaning is clearly given and / or is implied from the context in which it is used. All references to a / an / the item are to be interpreted openly as referring to one or more items unless otherwise indicated. The steps of any methods disclosed herein do not have to be performed in the exact order disclosed, unless explicitly stated otherwise. Any of the embodiments disclosed herein can be applied to any other embodiments, wherever technically possible. Similarly, any advantages, features, or benefits described in relation to any of the embodiments can be applied to any other embodiments, wherever technically possible. Other objects, features and advantages of the enclosed embodiments will become apparent from the following description.

[0058] In some embodiments, the more generic term "network node" can be used and can correspond to any type of radio network node or any network node that communicates with a user equipment (UE) (directly or via another node) and / or with another network node. Examples of network nodes are NodeB, master eNodeB (MeNB), network nodes belonging to a master cell group (MCG) or a secondary cell group (SCG), base station (BS), multi-standard radio (MSR) radio node such as a MSR BS, eNodeB (eNB), gNodeB (gNB), network controller, radio network controller (RNC), base station controller (BSC), relay, donor node controlled relay, base transceiver station (BTS), access point (AP), transmission points, transmission nodes, remote radio unit (RRU), remote radio head (RRH), nodes in distributed antenna system (DAS), core network nodes (e.g., application function (AF), session management function (SMF), user plane function (UPF), network exposure function (NEF), etc.), operation and maintenance (OAM), operations support system (OSS), self-optimizing networks (SON), positioning nodes (e.g., evolved serving mobile location center (E-SMLC)), minimization of drive testing (MDT), test equipment (physical node or software), etc.

[0059] In some embodiments, the non-limiting term "user equipment (UE)" or "wireless device" can be used and can refer to any type of wireless device communicating with a network node and / or with another UE in a cellular or mobile communication system. Examples of UE are target device, device to device (D2D) UE, machine type UE or UE capable of machine to machine (M2M) communication, personal digital assistant (PDA), tablet computer, mobile terminal, smart phone, laptop-embedded equipped (LEE), laptop-mounted equipment (LME), universal serial bus (USB) dongle, UE category Ml, UE category M2, proximity service (ProSe) UE, vehicle-to-vehicle (V2V) UE, vehicle-to-everything (V2X) UE, etc.

[0060] In addition, terms such as "base station / gNodeB" and "UE" should be considered as non-limiting terms and especially do not imply some hierarchical relationship between the two; generally, "gNodeB" can be considered as device 1, "UE" can be considered as device 2, and these two devices communicate with each other over some radio channel. In the following, the sender or receiver can be gNB or UE.

[0061] According to certain embodiments, a new solution is provided for 5GS supporting multiple TSN domains.

[0062] For example, according to certain embodiments, a network management function in 5GS (a core network node such as e.g. an application function (AF), or operation and maintenance (OAM), or a 5G exposure interface defined by 5G-ACIA) operates to detect or identify or is otherwise configured with how many external TSC / TSN domains exist (e.g. how many CNCs exist). This network management function is also configured for instantiating multiple 5GS bridges (including corresponding network functions (NFs)) to serve different TSC / TSN domains.

[0063] With the 3GPP Rel-16 5GS bridge model, 5GS bridge instantiation corresponds to UPF virtual network function (VNF) instantiation.

[0064] According to certain embodiments, a method for modeling 5G virtual bridges based on 5GS port groups is proposed. This method decouples the one-to-one mapping between 5G virtual bridges and UPFs (current 3GPP Rel-16 solution) and allows modeling multiple 5GS virtual bridges even if there is one UPF.

[0065] According to certain embodiments, for example, the 5GS can interact with a non-3GPP network controller (e.g., CNC), for example, based on the following: overall network topology information, geographical location of 5G system ports (e.g., UE / DS-TT is a 5GS port), virtual local area network (VLAN), data network name (DNN), and single network slice selection assistance information (S-NSSAI). In turn, the 5GS can decide or determine how many 5GS bridges should serve a TSN domain, and which 5G bridge(s) and ports should serve the TSN domain.

[0066] The term“TSC / TSN domain” is used herein to refer to a domain that is either a TSC domain or a TSN domain. As an umbrella term, time sensitive interworking domain can also be used to refer to a domain that is either a TSC or TSN domain.

[0067] The terms“5G virtual bridge,”“5GS virtual bridge,”“5GS bridge,” and“TSN bridge” are used herein to refer to a logical or virtual bridge that is implemented by using a 5GS.

[0068] Embodiments of a 5G virtual bridge include a TSN translator function for interoperation between a TSN network and a 5GS, for both user plane and control plane. In this embodiment, the 5GS TSN translator function includes a DS-TT and a NS-TT, while 5GS specific procedures in the 5GC and radio access network (RAN), wireless communication links, etc. remain hidden from the TSN network. To achieve this transparency to the TSN network so that the 5GS appears like any other TSN bridge, the 5GS provides TSN ingress and egress ports 17 via the DS-TT and the NW-TT. The 5G virtual bridge of this embodiment includes ports on the UPF side, user plane tunnels between the UE and the UPF, and ports on the DS-TT side. For each 5G bridge to the TSN network, the ports on the NW-TT support connectivity to the TSN network, and the ports on the DS-TT side are associated with the PDU session that provides connectivity to the TSN network. In one implementation, the DS-TT and / or NS-TT can be an Ethernet port that operates according to an Ethernet protocol (e.g., IEEE 802.1Q).

[0069] In one embodiment, the 5GS associates the port 17 (e.g., DS-TT and NW-TT) with a bridge ID and reports this bridge ID to its network management function (such as, for example, an AF or other 3GPP network node). This adds flexibility for 5G virtual bridges, for example, when the UE and / or connected device (e.g., mobile robot) is serving in a particular TSN domain. The UE (or DS-TT) and its connected port on the network side (UPF side NW-TT port) can be modeled in the 5G virtual bridge serving that TSN domain. However, when the same UE moves to another TSN domain, the UE acting as a port for the 5G bridge can be modeled to another 5G bridge serving another TSN domain.

[0070] As Figures 5-13 shown in

[0071] Instantiation of the 5GS bridge can be according to either of two alternatives, which will be described in more detail below.

[0072] As mentioned above, certain embodiments extend the 3GPP Rel-16 5GS bridge model to include 5GS bridge instantiation, which can correspond to UPF VNF (virtual network function) instantiation. For example, the bridge model of Rel-16 can be followed such that there is at least one UPF per TSN domain. Figure 5 An example system 10 is illustrated according to certain embodiments, showing 5GS support for multiple TSN domains 12. In Figure 5 the embodiment shown in Figure 5 the embodiment shown in Figure 5 the example illustrated in

[0073] Certain embodiments described herein relate to 5GS bridge instantiation. Specifically, when the 5GS network management function 19 detects multiple TSN domains 12, the 5GS network management function 19 decides how many ports 17 and UPFs 18 are needed and which ports 17 and UPFs 18 are needed for a particular TSN domain 12. The 5GS network function 19 can in turn instantiate UPF functions.

[0074] According to certain other embodiments, a port grouping based bridge model can be used.

[0075] With the proposed port-based 5G virtual bridge model, the 5GS can dynamically model virtual bridges based on port groups of the 5G system. The 5GS ports can be ingress or egress ports. Additionally, the 5GS ports can be UPF (NW-TT) ports or UE (DS-TT) ports. The 5GS can associate these ports with a bridge ID and report this bridge ID to a network management function, such as, for example, an AF or other 3GPP network node. This increases the flexibility for 5G virtual bridges, for example, when a UE 22 and / or connected device (e.g., mobile robot) is serving a particular TSN domain. The UE (or DS-TT) and its connected port on the network side (UPF side NW-TT port) can be modeled in a 5G virtual bridge that serves that TSN domain. However, when the same UE 22 moves to another TSN domain, the UE 22, which acts as a port for the 5G bridge, can be modeled to another 5G bridge that serves the other TSN domain.

[0076] Figure 6 An example system 20 with one UPF 18 is illustrated in accordance with certain embodiments. More specifically, Figure 6 A port-group based 5GS bridge model with one UPF 18 is illustrated, where one UPF 18 is shared between multiple 5G virtual bridges 14. In this embodiment, the ports 17 belonging to the UPF 18 can serve different 5G virtual bridges 14. In Figure 6 In the example, three virtual bridges 14 are modeled based on three groups of ports. As Figure 6 As depicted in the example, all ports 17 belonging to a TSN domain are considered a group of ports. Thus, since Figure 6 The example system 20 includes three domains, the system 20 has three groups of ports. Each group of ports constitutes a virtual bridge 14.

[0077] The ports 17 can be on the UPF side (or at the NW-TT port) or on the UE side (or at the DS-TT port). In accordance with certain embodiments, the 5GS (e.g., 5GS RAN 19) selects a group of ports 17 and assigns a bridge ID associated with these ports. The port and bridge management information can be reported to the AF 21, which can be dedicated to the virtual bridge 14. Each virtual bridge 14 can be managed by a dedicated CNC 16 from a different TSN domain 12.

[0078] Figure 7 Another example system 30 including multiple UPFs 18 is illustrated in accordance with certain embodiments. In one embodiment of the system 30, 5G virtual bridges 14 can be served by ports 17 belonging to different UPFs 18. More specifically, Figure 7 The example system 30 including two UPFs 18 is illustrated, where three virtual bridges 14 are modeled based on three groups of ports. As with the above Figure 6Similarly, port grouping is based on the 5GS bridge model. Thus, the modeling of the 5G virtual bridges 14 can still be based on port groups. For example, in this case, 5G virtual bridge #2 involves two UPFs 18 and the 5G communication in TSN domain #2 12 can involve UPF-to-UPF communication, such as for example on the N19 interface between UPFs (not depicted).

[0079] Figure 8 Fig. illustrates another example system 40 illustrating a port grouping based 5GS bridge model according to certain embodiments, wherein one UPF 18 is shared between multiple 5G virtual bridges 14. In this embodiment, ports 17 belonging to a UPF 18 can serve different 5G virtual bridges 14. More specifically, Figure 8 Fig. illustrates Figure 6 another example variant of Fig., wherein more than one virtual bridge 14 can be managed by one CNC 16 of a TSN domain 12. In other words, in this embodiment, a TSN domain 12 can have one or more 5G virtual bridges 14.

[0080] According to certain embodiments, the port and bridge management information of the virtual bridges 14 of a TSN domain 12 can be reported to different AFs 21 (as in TSN domain #1 12, bridge #1 14 is reported to AF #1 21 and bridge #2 14 is reported to AF #2 21) or to only one AF 21 (as TSN domain #3 12 shows where bridges #4 and #5 14 are reported to a single AF #4 21).

[0081] According to current Rel-16 3GPP definition, each 5GS bridge 14 interacts with the TSN system via one TSN AF 21 only, which is shown in TSN domain #1 12. According to certain embodiments, an option is provided for multiple virtual bridges 14 to share one TSN AF 21, with one AF 21 per TSC / TSN domain 12.

[0082] Figure 9 Fig. illustrates Figure 6 another example system 50 of the variant of Fig., wherein only one 5GS virtual bridge 14 is modeled (one bridge ID can be assigned) to serve more than one TSN domain 12. Multiple UPF ports 17 are divided into groups, which are assigned to TSN domains 12 (e.g. by slicing). Individual groups are configured by separate CNCs 16.

[0083] According to certain embodiments, the port and bridge management information of a single virtual bridge 14 can be reported to different AFs 21. An AF 21 manages a group of ports 17, which is only accessible and configurable by a specific CNC 16.

[0084] In certain embodiments, port and bridge management information can be reported by a single AF 21 Figure 9 However, there is a need to isolate different port groups, e.g., a group of ports 17 is only accessible / configurable by a certain CNC 16.

[0085] Some additional scenarios are now described to further illustrate the solutions, techniques, and embodiments associated with the embodiments described above in relation to Figure 5 the 5G virtual bridge.

[0086] For example, Figure 10 Another example system 60 is illustrated, showing an example hierarchical CNC architecture, where the 5G virtual bridge is part of a TSN backbone domain 61, such as, for example, the TSN backbone domain shown in Figure 2 As shown in Figure 10 The 5G virtual bridge 14 is part of a “higher” TSN domain (backbone domain 61), with the indicated TSN flows 62 (e.g., for C2C, C2D, D2Cmp). The TSN backbone domain 61 provides transport and connectivity services between TSN domains 12, such as TSN domains #1, #2, #3. The interaction between the TSN backbone domain 61 and other TSN domains 12 using 5G will become inter-TSN domain communication.

[0087] In the illustrated example system 60, inter-TSN domain communication between TSN domains 12, such as TSN domains #1, #2, #3, can go through the TSN backbone domain 61. In certain embodiments, CNC #4 16 can have a higher hierarchy than CNCs #1-3 16. When there is a need for communication between a device in TSN domain #1 and a device in TSN domain #2, CNC #1 and CNC #2 can send a request to CNC #4. According to the request, CNC #4 can configure the corresponding ports 17 and connections inside 5G (i.e., configure the 5G bridge and corresponding ports 17) in order to provide 5G connectivity between TSN domain #1 and TSN domain #2. In turn, CNC #1 and #2 can configure their local connections to deliver data to the corresponding devices within their own domains.

[0088] Figure 11 Another example system 70 is illustrated, which includes a 5GS virtual bridge that acts as its own separate 5G TSN domain 71. The system 70 can include a 5G TSN domain 71 made up of one or more 5GS virtual bridges.

[0089] As depicted, TSN domains #1, #2, #3 12 are local production domains. TSN domain #5 can be a TSN backbone (e.g., TSN backbone domain 61) for connecting to an industrial edge cloud network or another wired network.

[0090] In this case, the 5G TSN domain 71 uses 5G to provide two types of services:

[0091] • Connection / transport services between TSN domains #1, #2, #3

[0092] • Connection / transport services between local production domains (TSN domains #1, #2, #3) and TSN domain #5 (e.g., TSN backbone domain 61).

[0093] In one embodiment, CNC #4 16 has a higher hierarchy than CNCs #1, #2, #3, and #5 16. In this embodiment, CNC #4 can configure 5G connections within 5G TSN domain 71 according to requests from other TSN domains.

[0094] Figure 12 and 13 Figures illustrate examples of industrial automation use cases. Figure 12 and Figure 13 The letters A-E in Figures 1-4 indicate interconnections between different entities, e.g., D2D interconnections, controller-to-controller (C2C) interconnections, or device-to-computer (D2comp) interconnections. Figure 12 and 13 Figures 1-4 can be mapped to industrial use cases such as those described in the background. More specifically, Figure 12 Figures illustrate example systems 80 showing how a 5GS virtual bridge interacts with multiple TSC / TSN domains. Certain lines are controller-to-device (C2D) use cases in industrial automation and are shown as solid lines with arrowheads at the end. In the case of local communication (such as, for example, within one TSN domain, more specifically such as machine #3 internally), the 5GS provides interconnection “A” between PLCs and field devices via UE-to-UE communication. This 5GS connection is controlled by local CNC 2.

[0095] Figure 13 Figures illustrate example systems 90 showing how a 5GS virtual bridge interacts with multiple TSC / TSN domains. Certain lines are controller-to-controller (C2C) use cases in industrial automation and are shown as solid lines with arrowheads at the end.

[0096] 5GS is ready to interact with different CNCs. As mentioned above, this can be done, for example, by having different CNCs configure different port pair groups of the 5GS virtual bridge or by splitting the 5GS into multiple virtual bridges managed by different CNCs. A port pair refers to two ports at two different entities, e.g., a DS-TT port and a NW-TT port; two DS-TT ports at different devices; or two NW-TT ports at different UPFs. In case of inter-TSN domain communication, a higher level CNC can configure TSN flow paths between lower level TSN domains (e.g., between machines) or between backbone and local TSN domains. Since the 5GS interacts with all CNCs, all CNC configurations can be done over the 5GS.

[0097] Figure 14 A wireless network is illustrated in accordance with some embodiments. While the subject matter described herein can be implemented in any appropriate type of system, embodiments disclosed herein are described in relation to a wireless network, such as the example wireless network illustrated in FIG. 1. For simplicity, the wireless network of FIG. 1 only depicts networks 106, network nodes 160, 160b, and 160c, and wireless devices 110. In practice, a wireless network can also include any additional elements suitable to support communication between wireless devices or between a wireless device and another communication device (such as a landline telephone, a service provider, or any other network node or end device). Of the illustrated components, network nodes 160 and 160c and wireless devices 110 are depicted with additional detail. The wireless network can provide communication and other types of services to one or more wireless devices to facilitate access and / or use of services provided by or via the wireless network. Figure 14 Figure 14 The wireless network can include and / or can interface with any type of communication, telecommunication, data, cellular, and / or radio network or other similar type of system. The wireless network may, in some embodiments, be configured to operate according to specific standards or other types of predefined rules or procedures. Thus, particular embodiments of the wireless network can implement communication standards, such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term

[0098] The wireless network can include and / or can interface with any type of communication, telecommunication, data, cellular, and / or radio network or other similar type of system. The wireless network may, in some embodiments, be configured to operate according to specific standards or other types of predefined rules or procedures. Thus, particular embodiments of the wireless network can implement communication standards, such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term

[0099] ​Network 106 can comprise one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTNs), packet data networks, optical networks, wide-area networks (WANs), local area networks (LANs), wireless local area networks (WLANs), wired networks, wireless networks, metropolitan area networks, and other networks to enable communication between devices. For example, network 106 can comprise any one or any combination of the networks described above Figure 3 with respect to the 5G core network described above. Any one or Figure 3 more components of the 5G core network described above can supplement or replace any one or more components of Figure 14 the network 106.

[0100] Network nodes 160 and wireless devices 110 include various components described in greater detail below. These components

[0101] Figure 15Figure illustrates example network nodes 160, 160c, according to certain embodiments. As used herein, a network node refers to equipment capable, configured, arranged, and / or operable to communicate directly or indirectly with a wireless device and / or with other network nodes or equipment in the wireless network, to enable and / or provide wireless access to the wireless device and / or to perform other functions (e.g., administration) in the wireless network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs), and NR NodeBs (gNBs)). They can be classified as femto, pico, or macro base stations based on the amount of their coverage area (or in other words, their transmission power level) and can also be referred to as a gNB when being implemented in a 5G network. Base stations can be stand-alone nodes or can be remote radio headers controlled by a base station node. Network nodes can also include one or more (or all) parts of a distributed radio base station such as centralized digital units and / or remote radio units (RRUs), also referred to as remote radio heads (RRHs). Such remote radio units can or can not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station can also be referred to as nodes in a distributed antenna system (DAS). Yet further examples of network nodes include multi-standard radio (MSR) devices, network controllers, base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCEs), core network nodes (e.g., MSCs, MMEs), OAM nodes, OSS nodes, SON nodes, positioning nodes (e.g., E-SMLCs), and / or MDTs, as described in more detail below. As another example, a network node can be a virtual network node as described in more detail below. More generally, however, network nodes can represent any suitable device (or group of devices) capable, configured, arranged, and / or operable to enable and / or provide a wireless device with access to a wireless network and / or to provide some service to a wireless device.

[0102] In Figure 15 The network nodes 160 and 160c include processing circuitry 170, device readable medium 180, interface 190, auxiliary equipment 184, power source 186, power circuitry 187, and antenna 162. While Figure 15The network nodes 160 and 160c shown in the exemplary wireless network can represent devices that include a combination of the illustrated hardware components, but other embodiments can include network nodes with different combinations of components. For example, in certain embodiments, the core network node 160c can not include certain of these features (such as the antenna 162, radio front-end circuitry 192, RF transceiver circuitry 172, and baseband circuitry 174). It will be appreciated that the network nodes include any suitable combination of hardware and / or software needed to perform the tasks, features, functions and methods disclosed herein. Moreover, although the components of the network nodes 160 and 160c are depicted as single boxes located within a larger box or nested within multiple boxes, in practice, the network nodes can comprise multiple different physical components (e.g., the device readable medium 180 can comprise multiple individual disk drives as well as multiple RAM modules) constituting the single illustrated component.

[0103] Similarly, the network nodes 160 and 160c can be composed of multiple physically separate components (e.g., NodeB components and RNC components, or BTS components and BSC components, etc.), which can have their own respective components. In certain scenarios in which the network nodes 160 and 160c include multiple separate components (e.g., BTS and BSC components), one or more separate components can be shared among several network nodes. For example, a single RNC can control multiple NodeB’s. In such scenarios, each unique NodeB and RNC pair, in some instances, can be considered a single network node. In some embodiments, the network nodes 160 and 160c can be configured to support multiple radio access technologies (RATs). In such embodiments, some components can be duplicated (e.g., individual device readable medium 180 for separate RATs) and some components can be reused (e.g., the same antenna 162 can be shared by the RATs). The network nodes 160 and 160c can also include multiple sets of various illustrated components for different wireless technologies integrated into the network nodes 160 and 160c, such as, for example, Global System for Mobile Communications (GSM), Wideband Code Division Multiple Access (WCDMA), Long Term Evolution (LTE), New Radio (NR), WiFi, or Bluetooth wireless technologies. These wireless technologies can be integrated into the network nodes 160 and 160c within the same or different chip or chipset as well as other components.

[0104] In certain embodiments, processing circuitry 170 is configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being provided by a network node. These operations performed by processing circuitry 170 can include processing information obtained by processing circuitry 170 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and / or performing one or more operations based on the obtained information or converted information, as well as determining as an outcome of such processing. In this way, the processing circuitry 170 can be considered to be at least one

[0105] Processing circuitry 170 can comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other processing circuit, or any combination thereof, and working memory located either on the same chip as the processing circuitry 170 or on a separate chip. As examples, processing circuitry 170 can include a processor, a microprocessor, an application-specific circuit, a field programmable gate array, or some combination thereof. Processing circuitry 170 can be implemented as a single device (e.g., a single chip) or multiple devices (e.g., multiple chips), and / or can be implemented using one or more integrated circuits (ICs) and / or one or more other components of network node 160.

[0106] In some embodiments, processing circuitry 170 can include one or more of radio frequency (RF) transceiver circuitry 172 and baseband processing circuitry 174. In some embodiments, radio frequency (RF) transceiver circuitry 172 and baseband processing circuitry 174 can be on separate chips (or chipsets), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 172 and baseband processing circuitry 174 can be on the same chip or chipset, board, or unit.

[0107] In certain embodiments, some or all of the functionality described herein as being provided by a network node, base station, eNB, or other such network device can be performed by processing circuitry 170 executing instructions stored on device readable medium 180 or memory within processing circuitry 170. In alternative embodiments, some or all of the functionality can be provided by processing circuitry 170 without executing instructions stored on a separate or discrete device readable medium, such as in a hard-wired device or an application- specific integrated circuit. In any of those embodiments, whether executing instructions stored on a device readable storage medium or not, processing circuitry 170 can be configured to perform the described functionality. The benefits provided by the functionality are not limited to processing circuitry 170 or other components of network nodes 160 and 160c but are enjoyed by network nodes 160 and 160c as a whole, and / or by end users and the wireless network generally.

[0108] Device readable medium 180 can include any form of volatile or non-volatile computer readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media, removable storage media, and / or any other volatile or non-volatile, non-transitory device readable and / or computer-executable memory devices that store information, data, and / or instructions that can be used with processing circuitry 170. Device readable medium 180 can be used to store any suitable instructions, data or information, including a computer program, software, an application including one or more of logic, rules, codes, tables, etc. and / or other instructions capable of being executed by processing circuitry 170 and used by network node 160 and 160c. Device readable medium 180 can be used to store any calculations made by processing circuitry 170 and / or any data received via interface 190. In some embodiments, processing circuitry 170 and device readable medium 180 can be considered to be integrated.

[0109] Interface 190 is used in the wired or wireless communication of signaling and / or data between network node 160, network 106, and / or wireless devices 110. As illustrated, interface 190 includes a port / terminal 194 to send and receive data, such as to and from network 106 over a wired connection. Interface 190 also includes radio front end circuitry 192 that can be coupled to, or in certain embodiments a part of, antenna 162. Radio front end circuitry 192 comprises filters 198 and amplifiers 196. Radio front end circuitry 192 can be connected to antenna 162 and processing circuitry 170. Radio front end circuitry 192 can be configured to condition signals communicated between antenna 162 and processing circuitry 170. Radio front end circuitry 192 can receive digital data that is to be sent out to other network nodes or wireless devices via a wireless connection. Radio front end circuitry 192 can convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 198 and / or amplifiers 196. The radio signal can then be transmitted via antenna 162. Similarly, when

[0110] In certain alternative embodiments, network node 160 can not include separate radio front-end circuitry 192, but rather processing circuitry 170 can comprise radio front-end circuitry and can be connected to antenna 162 without separate radio front-end circuitry 192. Similarly, in some embodiments, all or some of RF transceiver circuitry 172 can be considered a part of interface 190. In some other embodiments, interface 190 can include one or more ports or terminals 194, radio front-end circuitry 192, and RF transceiver circuitry 172 as part of a radio unit (not shown) and interface 190 can communicate with baseband processing circuitry 174, which is part of a digital unit (not shown).

[0111] Antenna 162 can comprise one or more antennas or antenna arrays configured to send and / or receive wireless signals. Antenna 162 can be coupled to radio front-end circuitry 192 and can be any type of antenna and / or antennas in

[0112] Antenna 162, interface 190, and / or processing circuitry 170 can be configured to perform any receiving operations and / or certain obtaining operations described herein as being performed by a network node. Any information, data and / or signals can be received from a wireless device, another network node and / or any other network equipment. Similarly, antenna 162, interface 190, and / or processing circuitry 170 can be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and / or signals can be transmitted to a wireless device, another network node and / or any other network equipment.

[0113] Power circuitry 187 can comprise, or be coupled to, power management circuitry and be configured to supply the components of network node 160 with power for performing the functionality described herein. Power circuitry 187 can receive power from power source 186. Power source 186 and / or power circuitry 187 can be configured to provide power to the various components of network node 160 in a form suitable for use by each respective component (e.g., at a voltage and current level that each respective component needs to function). Power source 186 can be included in, or external to, power circuitry 187 and / or network node 160. For example, network node 160 can be connected to an external power source (e.g., an electricity outlet) via an input circuitry or interface, and the external power source can provide power to power circuitry 187 to power the components of network node 160. As another example, power source 186 can comprise a battery or battery pack coupled to, or integrated in, power circuitry 187. The battery can provide backup power should the external power source fail, allowing network node 160 to perform a controlled shutdown if the external power source fails. Other types of power sources, such as photovoltaic devices, can also be used.

[0114] Alternative embodiments of network nodes 160 and 160c can include additional components Figure 15 that are not shown in FIG. 1 6, which can be responsible for providing certain aspects of the network node’s functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, network node 160 can include user interface equipment to allow input of information into network node 160 and to allow output of information from network node 160. This can allow a user to perform diagnostic, maintenance, repair, and other administrative functions for network node 160.

[0115] Figure 16A wireless device 110 according to certain embodiments is illustrated. As used herein, a wireless device refers to a device that is capable of, configured for, designed for, and / or operable for wireless communication with a network node and / or another wireless device. The term wireless device can be used interchangeably with user equipment (UE) throughout this document unless otherwise indicated. A wireless communication can involve sending and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information over a network. In some embodiments, a wireless device can be configured to transmit and / or receive information without direct human interaction. For instance, a wireless device can be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the network. Examples of a wireless device include, but are not limited to, a smart phone, a mobile phone, a cell phone, a voice over IP (VoIP) phone, a wireless local loop phone, a desktop computer, a personal digital assistant (PDA), a wireless cameras, a gaming console or device, a music storage device, a playback appliance, a wearable terminal device, a wireless endpoint, a mobile station, a tablet, a laptop, a laptop mounted embedded equipment (LEE), a laptop mounted installation equipment (LME), a smart device, a Customer Premises Equipment (CPE), a vehicle-mounted wireless terminal device, etc. A wireless device can support device-to-device (D2D) communication, e.g., by implementing a 3GPP standard for sidelink communication, vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to- everything (V2X), and in this case can be referred to as a D2D communication device. As yet another specific example, in a loT scenario a wireless device can represent a machine or other device that performs monitoring and / or measurements and transmits the results of such monitoring and / or measurements to another wireless device and / or a network node. In this case the wireless device can be a machine-to-machine (M2M) device, which can be referred to as an MTC device in a 3GPP context. As one particular example, a wireless device can be a UE implementing the 3GPP narrow band loT (NB-loT) standard. Particular examples of such machines or devices are sensors, metering devices such as power meters, industrial machinery, or home or personal appliances, e.g. refrigerators, televisions, etc., or personal wearables such as watches, fitness trackers, etc. In other scenarios, a wireless device can represent a vehicle or other equipment that is capable of monitoring and / or reporting its operational status or other functions associated with its operation. A wireless device as described above can represent the endpoint of a wireless connection, in which case the device can be referred to as a wireless terminal. Furthermore, a wireless device as described above can be mobile, in which case it can also be referred to as a mobile device or mobile terminal.

[0116] As illustrated, wireless device 110 includes antenna 111, interface 114, processing circuitry 120, device readable medium 130, user interface equipment 132, auxiliary equipment 134, power source 136, and power circuitry 137. Wireless device 110 can include multiple sets of one or more of the various illustrated components for different wireless technologies supported by wireless device 110, such as, for example, GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wireless technologies, just to mention a few. These wireless technologies can be integrated into wireless device 110 within the same or different chip sets and / or other components.

[0117] Antenna 111 can include one or more antennas or antenna arrays configured to send and / or receive wireless signals, and is connected to interface 114. In certain alternative embodiments, antenna 111 can be separate from wireless device 110 and can be connectable to wireless device 110 through an interface or port. Antenna 111, interface 114, and / or processing circuitry 120 can be configured to perform any of the receiving or transmitting operations described herein as being performed by a wireless device. Any information, data and / or signals can be received from a network node and / or another wireless device. In some embodiments, radio front end circuitry and / or antenna 111 can be considered an interface.

[0118] As illustrated, interface 114 includes radio front end circuitry 112 and antenna 111. Radio front end circuitry 112 includes one or more filters 118 and amplifiers 116. Radio front end circuitry 114 is connected to antenna 111 and processing circuitry 120, and is configured to condition signals communicated between antenna 111 and processing circuitry 120. Radio front end circuitry 112 can be coupled to or a part of antenna 111. In some embodiments, wireless device 110 can not include separate radio front end circuitry 112; rather, processing circuitry 120 can comprise radio front end circuitry and can be connected to antenna 111. Similarly, in some embodiments, some or all of RF transceiver circuitry 122 can be considered a part of interface 114. Radio front end circuitry 112 can receive digital data that is to be sent out to other network nodes or wireless devices via a wireless connection. Radio front end circuitry 112 can convert the digital data into a wireless signal having the appropriate channel and bandwidth parameters using a combination of filters 118 and / or amplifiers 116. The wireless signal can then be transmitted via antenna. Similarly, when receiving data, antenna 111 can collect wireless signals, which are then converted into digital data by radio front end circuitry 112. The digital data can be passed on to processing circuitry 120. In other embodiments, the interface can comprise different components and / or different combinations of components.

[0119] The processing circuit 120 can include a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field-programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic operable to provide functionality of the wireless device 110 alone or in conjunction with other wireless device 110 components such as the device readable medium 130. Such functionality can include providing any of the various wireless features or benefits discussed herein. For example, processing circuit 120 can execute instructions stored in the device readable medium 130 or in memory within processing circuit 120 to provide the functionality disclosed herein.

[0120] As illustrated, processing circuit 120 includes one or more of RF transceiver circuitry 122, baseband processing circuitry 124, and application processing circuitry 126. In other embodiments, the processing circuit can include different components and / or different combinations of components. In certain embodiments, the processing circuit 120 of the wireless device 110 can include a SOC. In some embodiments, the RF transceiver circuitry 122, the baseband processing circuitry 124, and the application processing circuitry 126 can be on separate chips or chipsets. In alternative embodiments, portions of or all of the baseband processing circuitry 124 and the application processing circuitry 126 can be combined into one chip or chipset, and the RF transceiver circuitry 122 can be on a separate chip or chipset. In another alternative embodiment, portions of or all of the RF transceiver circuitry 122 and the baseband processing circuitry 124 can be on the same chip or chipset, and the application processing circuitry 126 can be on a separate chip or chipset. In another alternative embodiment, portions of or all of the RF transceiver circuitry 122, the baseband processing circuitry 124, and the application processing circuitry 126 can be combined into the same chip or chipset. In some embodiments, the RF transceiver circuitry 122 can be part of the interface 114. The RF transceiver circuitry 122 can condition RF signals for the processing circuit 120.

[0121] In certain embodiments, some or all of the functionality described herein as being performed by a wireless device can be provided by processing circuitry 120 executing instructions stored on device readable medium 130, which in some embodiments can be a computer-readable storage medium. In alternative embodiments, some or all of the functionality can be provided by processing circuitry 120 without executing instructions stored on a separate or discrete device readable medium, such as in a hard-wired device. In any of those embodiments, whether executing instructions stored on a device readable storage medium or not, processing circuitry 120 can be configured to perform the described functionality. The benefits provided by this functionality are not limited to processing circuitry 120 or other components of wireless device 110 but are enjoyed by wireless device 110 as a whole, and / or by end users and the wireless network generally.

[0122] Processing circuitry 120 can be configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being performed by a WD. These operations, as performed by processing circuitry 120, can include processing information obtained by processing circuitry 120 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by wireless device 110, and / or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.

[0123] Device readable medium 130 can be operable to store a computer program; software; applications including one or more of logic, rules, codes, tables, etc.; and / or other instructions capable of being executed by processing circuitry 120. Device readable medium 130 can include computer memory (e.g., Random Access Memory (RAM) or Read Only Memory (ROM)), mass storage media (e.g., a hard disk), removable storage media (e.g., a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non- transitory device readable and / or computer executable storage medium that can be coupled with processing circuitry 120 and that can be accessed by processing circuitry 120. Processing circuitry 120 and device readable medium 130 can be considered to be integrated.

[0124] User interface equipment 132 can provide components that allow for a human user to interact with wireless device 110. Such interaction can be of many forms, such as visual, auditory, tactile, etc. User interface equipment 132 can be operable to generate output to the user and to allow the user to provide input to wireless device 110. The type of interaction can vary depending on the type of user interface equipment 132 installed in wireless device 110. For example, if wireless device 110 is a smart phone, the interaction can be via a touch screen; if wireless device 110 is a smart meter, the interaction can be through a screen that provides usage (for example, the amount of gallons used) or a speaker that provides audible alerts (for example, if smoke is detected). User interface equipment 132 can include input interfaces, devices, and circuits, and output interfaces, devices, and circuits. User interface equipment 132 is configured to allow input of information into wireless device 110 and is connected to processing circuitry 120 to allow processing circuitry 120 to process input information. User interface equipment 132, for example, can include a microphone, a proximity sensor or other sensor, keys / buttons, a touch display, one or more cameras, a USB port, or other input circuitry. User interface equipment 132 is also configured to allow output of information from wireless device 110, and to allow processing circuitry 120 to output information from wireless device 110. User interface equipment 132, for example, can include a speaker, a display, vibrating circuitry, a USB port, a headphone interface, or other output circuitry. Using one or more input and output interfaces, devices, and circuits of user interface equipment 132, wireless device 110 can communicate with end users and / or the wireless network, and allow them to benefit from the functionality described herein.

[0125] Auxiliary equipment 134 is operable to provide more specific functionality that can not be relevant in all types of wireless devices. This can include specialized sensors for making measurements for various purposes, interfaces for additional types of communication, such as wired communication, etc. The inclusion and type of components of auxiliary equipment 134 can vary depending on the embodiment and / or scenario.

[0126] In some embodiments, power source 136 can be in the form of a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic devices, or power cells, can also be used. Wireless device 110 can further comprise power circuitry 137 for delivering power from power source 136 to the various parts of wireless device 110 which need power from power source 136 to perform any of the functions described or indicated herein. In some embodiments, power circuitry 137 can include power management circuitry. Additionally or alternatively, power circuitry 137 can be operable to receive power from an external power source; in which case wireless device 110 can be connectable to the external power source (such as an electricity outlet) via input circuitry, or an interface such as an electrical power cable. In some embodiments, power circuitry 137 can also be operable to deliver power from an external power source to power source 136. This could be used, for example, to charge power source 136. Power circuitry 137 can perform any formatting, converting, or other modification to the power from power source 136 in order to make the power suitable for use by the respective components of wireless device 110 which are powered by power source 136.

[0127] Figure 17 One embodiment of a UE is illustrated in accordance with aspects described herein. As used herein, a user equipment or UE can not necessarily have a user in the sense of a human user that owns and / or operates the relevant device. Instead, a UE can represent a device that is intended for sale to, or operation by, a human user but that can not have, and / or that can not initially have, an association with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE can represent a device that is not intended for sale to, or operation by, an end user but that can be associated with or operated for the benefit of a user (e.g., a smart power meter). UE 200 can be any UE identified by the 3rd Generation Partnership Project (3GPP) including a NB-loT UE, a machine Figure 15 As shown in FIG. 1, UE 200 is one example of a wireless device configured for communication in accordance with one or more communication standards promulgated by the 3rd Generation Partnership Project (3GPP), such as 3GPP's GSM, UMTS, LTE, and / or 5G standards. As previously described, the term wireless device and UE can be used interchangeably. Thus, although Figure 17 As shown in FIG. 1, UE 200 is one example of a wireless device configured for communication in accordance with one or more communication standards promulgated by the 3rd Generation Partnership Project (3GPP), such as 3GPP's GSM, UMTS, LTE, and / or 5G standards. As previously described, the term wireless device and UE can be used interchangeably. Thus, although

[0128] In Figure 17In some embodiments, the UE 200 includes processing circuitry 201 that is operatively coupled to the input / output interface 205, the radio frequency (RF) interface 209, the network connection interface 211, the memory 215 including the random access memory (RAM) 217, the read-only memory (ROM) 219, and the storage medium 221, the communication subsystem 231, the power source 213, and / or any other component or any combination thereof. The storage medium 221 includes an operating system 223, application program 225, and data 227. In other embodiments, the storage medium 221 can include other similar types of information. Some of the components in the Figure 17 may be used in the embodiments shown in FIG. 2, or only a subset of the components. Levels of integration can vary from one embodiment to another. Further, a certain implementation of a UE can

[0129] In Figure 17 , the processing circuitry 201 can be configured to process computer instructions and data. The processing circuitry 201 can be configured as any sequential state machine operative to

[0130] In the depicted embodiment, input / output interface 205 can be configured to provide a communication interface to input and output devices. UE 200 can be configured to use output device via input / output interface 205. An output device can use the same type of interface port as an input device. For example, a USB port can be used to provide input to and output from UE 200. The output device can be a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. UE 200 can be configured to use an input device via input / output interface 205 to allow a user to capture information into UE 200. The input device can include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital still or video camera), a microphone, a sensor, a mouse, a track ball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display can include a capacitive or resistive touch sensor for sensing input from a user. The sensor, for example, can be an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, another like sensor, or any combination thereof. For example, the input device can be an accelerometer, a magnetometer, a digital camera, a microphone, and an optical sensor.

[0131] In Figure 17 RF interface 209 can be configured to provide a communication interface to RF components such as a transmitter, a receiver, and an antenna. Network connection interface 211 can be configured to provide a communication interface to network 243a. Network 243a can encompass

[0132] The RAM 217 can be configured to interface via the bus 202 to the processing circuitry 201 to provide storage or caching of data or computer instructions during the execution of software programs such as the operating system, application programs, and device drivers. The ROM 219 can be configured to provide computer instructions or data to the processing circuitry 201. For example, the ROM 219 can be configured to store invariant low-level system code or data for basic system functions such as basic input and output (I / O) operations, startup, or reception of keystrokes from a keyboard that are stored in non-volatile memory. The storage medium 221 can be configured to include memory such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, floppy disks, hard disks, removable cartridges, or flash memories. In one example, the storage medium 221 can be configured to include operating system 223, application program 225 such as a web browser application, a widget or gadget engine or another application, and data file 227. The storage medium 221 can store, among other things, various operating systems, one or a combination of various applications, or a combination of operating system and applications.

[0133] The storage medium 221 can be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), soft disk drive, flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, High-Density Digital Versatile Disc (DVD) optical disc drive, built-in hard disk drive, Blu-Ray optical disc drive, holographic data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smart card memory such as a user identity module or a removable user identity (SIM / RUIM) module, other memory, or any combination thereof. The storage medium 221 can allow the UE 200 to access computer-executable instructions, application programs or the like stored on transitory or non-transitory memory media to off-load data or to store data in excess of internal memory. An article of manufacture such as one utilizing a communication system can have tangibly embodied therein

[0134] In Figure 17In particular embodiments, processing circuitry 201 can be configured to communicate with a network 243b using communication subsystem 231. Network 243a and network 243b can be the same network or different networks. Communication subsystem 231 can be configured to include one or more transceivers used to communicate with network 243b. For example, communication subsystem 231 can be configured to include one or more transceivers used to communicate with one or more remote transceivers of another device capable of wireless communication such as another wireless device, UE, or base station of a RAN, according to one or more communication protocols such as IEEE 802.2, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, or the like. Each transceiver can include transmitter 233 and / or receiver 235 to implement transmitter or receiver functionality, respectively, as appropriate for the RAN link (e.g., frequency allocations, etc.). Further, transmitter 233 and receiver 235 of each transceiver can share circuit components, software, or firmware, or alternatively can be implemented separately.

[0135] In the illustrated embodiment, communication functions of communication subsystem 231 can include data communication, voice communication, multimedia communication, short-range communications, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like function, or any combination thereof. For example, communication subsystem 231 can include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. Network 243b can encompass wired and / or wireless networks, such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network, or any combination thereof. For example, network 243b can be a cellular network, a Wi-Fi network, and / or a near-field network. Power source 213 can be configured to provide alternating current (AC) or direct current (DC) power to components of UE 200.

[0136] The features, benefits and / or functions described herein can be implemented in one of the components of UE 200, or can be partitioned among multiple components of UE 200. Further, the features, benefits and / or functions described herein can be implemented in any combination of hardware, software or firmware. In one example, communication subsystem 231 can be configured to include any of the components described herein. Further, processing circuitry 201 can be configured to communicate with any of such components over bus 202. In another example, any of such components can be represented by program instructions stored in memory that, when executed by processing circuitry 201, perform the corresponding functions described herein. In another example, the functionality of any of such components can be partitioned between processing circuitry 201 and communication subsystem 231. In another example, non-computationally intensive functions of any of such components can be implemented in software or firmware and computationally intensive functions can be implemented in hardware.

[0137] Figure 18 is a schematic block diagram illustrating a virtualization environment 300 in which functions implemented by some embodiments can be virtualized. In the present context, virtualization means the creation of virtual versions of apparatuses or devices that can include virtualized hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to a node (e.g., a virtualized base station or a virtualized radio access node) or to an apparatus (e.g., a UE, a wireless device, or any other type of communication device or component thereof), and relates to an implementation in which at least a part of the functionality is implemented as one or more virtual components (e.g., via one or more applications, components, functions, virtual machines or containers executing on one or more physical processing nodes in one or more networks). According to certain embodiments, virtualization environment 300 can be applied to a node such as a core network node.

[0138] In some embodiments, some or all of the functionality described herein can be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments 300 hosted by one or more of hardware nodes 330. Further, in embodiments where a virtual node is not a radio access node or does not require radio connectivity (e.g., a core network node), the node can be entirely virtualized.

[0139] These functions can be implemented by one or more applications 320 (alternatively referred to as software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) operative to implement some of the functionality, features, and / or benefits of some of the embodiments disclosed herein. The applications 320 are run in virtualization environment 300 which provides hardware 330 comprising processing circuitry 360 and memory 390. The memory 390 contains instructions 395 executable by the processing circuitry 360 such that the application 320 is operative to provide one or more of the features, benefits, and / or functions disclosed herein.

[0140] Virtualization environment 300 comprises general-purpose or special-purpose network hardware devices 330 comprising a set of one or more processors or processing circuitry 360, which can be commercial off-the-shelf (COTS) processors, dedicated Application-Specific Integrated Circuits (ASICs), or any other type of processing circuitry including digital or analog hardware components or special purpose processors. Each hardware device can comprise memory 390-1 which can be non-persistent memory for temporarily storing instructions 395 or software executed by processing circuitry 360. Each hardware device can comprise one or more network interface controllers (NICs) 370, also known as network interface cards, which include physical network interfaces 380. Each hardware device can also include non-transitory, persistent, machine-readable storage media 390-2 having stored therein software 395 and / or instructions executable by processing circuitry 360. Software 395 can include any type of software including software to instantiate one or more virtualization layers 350 (also referred to as hypervisors), software to execute virtual machines 340, and software allowing it to execute the functions, features and / or benefits of some embodiments described herein.

[0141] Virtual machines 340 comprise virtual processing, virtual memory, virtual networking or interface, and virtual storage, and can be run by a corresponding virtualization layer 350 or hypervisor. Different embodiments of the instance of virtual appliance 320 can be implemented on one or more virtual machines 340, and the embodiments can be implemented by different ways.

[0142] During operation, processing circuitry 360 executes software 395 to instantiate the hypervisor or virtualization layer 350, which can sometimes be referred to as a virtual machine monitor (VMM). Virtualization layer 350 can present a virtual operating platform that appears like networking hardware to virtual machine 340.

[0143] As Figure 18As shown in Figure 3C, hardware 330 can be a standalone network node with generic or specific components. Hardware 330 can comprise antenna 3225 and can implement some functions via virtualization. Alternatively, hardware 330 can be part of a larger cluster of hardware (e.g., such as in a data center or customer premises equipment (CPE)) where multiple hardware nodes work together and are managed via management and orchestration (MANO) 3100 which oversees lifecycle management of applications 320, among other things.

[0144] Virtualization of the hardware is in some contexts referred to as Network Function Virtualization (NFV). NFV can be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches and physical storage, which can be located in

[0145] In the context of NFV, virtual machine 340 can be a software implementation of a physical machine that executes programs like they are running on a physical, non-virtual machine. Each virtual machine 340, and that part of hardware 330 that executes that virtual machine, i.e. the hardware dedicated to that virtual machine and / or the hardware shared by that virtual machine with the other virtual machines 340, comprise a separate virtual network element (VNE).

[0146] Still in the context of NFV, Virtual Network Function (VNF) is responsible for handling specific network functions that are run in one or more virtual machines 340 on top of hardware networking infrastructure 330 and corresponds to Figure 18 application 320 in Figure 3A.

[0147] In some embodiments, one or more radio units 3200 that each include one or more transmitters 3220 and one or more receivers 3210 can be coupled to one or more antennas 3225. Radio units 3200 can communicate directly with hardware nodes 330 via one or more suitable networks, and can be used in combination with virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station.

[0148] In some embodiments, some signaling can be effected with the use of control system 3230, which can alternatively be used for communication between hardware nodes 330 and radio units 3200.

[0149] Figure 19 Figure 3D illustrates a telecommunications network connected via an intermediate network to a host computer according to some embodiments.

[0150] Reference is made to Figure 19According to an embodiment, the communication system includes a telecommunication network 410, such as a 3GPP-type cellular network, which comprises an access network 411, such as a RAN, and a core network 414. The access network 411 comprises a plurality of base stations 412a, 412b, 412c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 413a, 413b, 413c. Each base station 412a, 412b, 412c is connectable to the core network 414 over a wired or wireless connection 415. A first UE 491 located in coverage area 413c is configured to wirelessly connect to, or be paged by, the corresponding base station 412c. A second UE 492 located in coverage area 413a is wirelessly connectable to the corresponding base station 412a. While a plurality of UEs 491, 492 are illustrated in this example, the

[0151] The telecommunication network 410 is itself connected to a host computer 430, which can be embodied in hardware and / or software and can be embodied as a standalone server, a cloud-implemented server, or a distributed server. The host computer 430 can be controlled by a service provider or be operated by a service provider. Connections 421 and 422 between the telecommunication network 410 and the host computer 430 can be implemented via wired or wireless connections. The intermediate network 420 can be a public, private, or hosted network; the intermediate network 420 can be a bulk network, an Internet, or a combination of two or more of them; and the intermediate network 420 can include one or more wired, wireless, and / or optical links. The connections 421 and 422 can be implemented through the intermediate network 420, or they can be operatively discrete from the intermediate network 420.

[0152] Figure 19The communication system as a whole enables connectivity between the connected UEs 491, 492 and the host computer 430. The connectivity can be described as an over-the-top (OTT) connection 450. The host computer 430 and the connected UEs 491, 492 are configured to communicate data and / or signaling over the OTT connection 450 using the access network 411, the core network 414, any intermediate network 420 and possible further infrastructure (not shown) as intermediaries. The OTT connection 450 can be transparent in the sense that the

[0153] Figure 20 Figure illustrates a host computer communicating via a base station with a user equipment in accordance with some embodiments of the present disclosure.

[0154] Example implementations, in accordance with an embodiment, of the UE, base station and host computer discussed in the preceding paragraphs will now be described with reference to the Figure 20 communications system 500, the host computer 510 comprises hardware 515 enabling it to establish and maintain a connection 520 with a base station 410, such as the base station 412 of Figure 4. The connection 520 can be a logical connection 520, such as an over-the-air connection. The hardware 515 of the host computer 510 can comprise one or more transmitters 515 and receivers 517. The transmitter 515 and receiver 517 can be used to establish a wireless connection 520 between the host computer 510 and the base station 410. The transmitter 515 and receiver 517 can be used to exchange data and / or signaling with the base station 410. The hardware 515 of the host computer 510 can also include a processing circuitry 518, which can include a processor 522 and memory 524. The processor 522 and the memory 524 can be adapted to provide some or all of the functionality described herein as that of the host computer 510. In particular, the processor 522 and the memory 524 can be adapted to establish and maintain a connection 520 with a base station 410, and to transmit and receive data and / or signaling to and from the base station 410 over the connection 520.

[0155] The communication system 500 also includes a base station 520, which is provided in the telecommunications system and includes hardware 525 enabling it to communicate with the host computer 510 and the UE 530. Hardware 525 may include a communication interface 526 for establishing and maintaining wired or wireless connections with different communication devices in the communication system 500, and for establishing and maintaining connections with at least the coverage area served by the base station 520 (not in...). Figure 20 The radio interface 527 of the UE 530's wireless connection 570 (shown in the diagram) is used. The communication interface 526 can be configured to facilitate a connection 560 to the host computer 510. The connection 560 can be direct, or it can be via the core network of the telecommunications system (not shown in the diagram). Figure 20 (as shown in the diagram) and / or via one or more intermediate networks outside the telecommunications system. In the illustrated embodiment, the hardware 525 of base station 520 also includes processing circuitry 528, which may include one or more programmable processors, application-specific integrated circuits, field-programmable gate arrays, or combinations of these components (not shown) adapted to execute instructions. Base station 520 also has software 521 that is internally stored or accessible via an external connection.

[0156] The communication system 500 also includes the previously mentioned UE 530. Its hardware 535 may include a radio interface 537 configured to establish and maintain a wireless connection 570 with a base station serving the coverage area where the UE 530 is currently located. The hardware 535 of the UE 530 also includes processing circuitry 538, which may include one or more programmable processors, application-specific integrated circuits, field-programmable gate arrays, or combinations of these components (not shown) suitable for executing instructions. The UE 530 also includes software 531, which is stored in or accessible to the UE 530 and can be executed by the processing circuitry 538. The software 531 includes a client application 532. The client application 532 can be operated with the support of a host computer 510 to provide services to human or non-human users via the UE 530. In the host computer 510, a executing host application 512 can communicate with the executing client application 532 via an OTT connection 550 terminated between the UE 530 and the host computer 510. When providing services to a user, client application 532 can receive request data from host application 512 and, in response to that request data, provide user data. OTT connection 550 can transmit both request data and user data. Client application 532 can interact with the user to generate the user data it provides.

[0157] Notice, Figure 20 The host computer 510, base station 520, and UE 530 shown can be respectively connected to... Figure 19The host computer 430, base stations 412a, 412b, and 412c, and UEs 491 and 492 are similar to or identical to each other. That is to say, the internal workings of these entities can be as follows: Figure 20 As shown, and independently, the surrounding network topology can be Figure 19 Those in it.

[0158] exist Figure 20 The OTT connection 550 has been abstractly depicted to illustrate communication between the host computer 510 and the UE 530 via base station 520, without explicitly mentioning any intermediate devices or the precise message routing via these devices. The network infrastructure can determine the routing, which can be configured to be hidden from the UE 530 or the service provider operating the host computer 510, or both. When the OTT connection 550 is active, the network infrastructure can further make decisions by dynamically changing the routing (e.g., based on load balancing considerations or network reconfiguration).

[0159] The wireless connection 570 between UE 530 and base station 520 is based on the teachings of the embodiments described in this disclosure. One or more embodiments in the various embodiments can improve the performance of OTT services provided to UE 530 using OTT connection 550, wherein wireless connection 570 constitutes the final segment. More precisely, the teachings of these embodiments can improve / enhance data rates, latency, and / or power consumption, thereby providing benefits such as reduced user wait time, relaxed file size limits, better responsiveness, and / or extended battery life.

[0160] A measurement procedure can be provided for the purpose of monitoring data rate, latency, and other factors on which the one or more embodiments have an impact. There can further be an optional network functionality to reconfigure the OTT connection 550 between the host computer 510 and the UE 530, in response to variations in the measurement results. The measurement procedure and / or the network functionality to reconfigure the OTT connection 550 can be implemented in the software 511 and the hardware 515 of the host computer 510 or in the software 531 and the hardware 535 of the UE 530, or both. In embodiments, sensors (not shown) can be deployed in or in association with the communication devices through which the OTT connection 550 passes; the sensors can participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which the software 511, 531 can compute or estimate the monitored quantities. The reconfiguring of the OTT connection 550 can include message format, retransmission settings, preferred routing, etc. ; the reconfiguring need not affect the base station 520, and it can be unknown or invisible to the base station 520. Such procedures and functionalities can be known and practiced in the art. In certain embodiments, the measurements can involve proprietary UE signaling facilitating the host computer's 510 measurements of throughput, propagation times, error rates, etc. The measurements can be implemented at least in part by the software 511, 531 causing messages to be sent along the OTT connection 550 and

[0161] Figure 21 is a flowchart illustrating a method implemented in a communication system in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which can be those described with reference to Figure 19 and 20 for simplicity of the present disclosure, only diagram references to Figure 21 will be included in this section. In step 610, the host computer provides user data. In sub-step 611 (which can be optional) of step 610, the host computer provides the user data by executing a host application. In step 620, the host computer initiates a transmission carrying the user data to the UE. In step 630 (which can be optional), the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described in the present disclosure. In step 640 (which can also be optional), the UE executes a client application associated with the host application executed by the host computer.

[0162] Figure 22 is a flowchart illustrating a method implemented in a communication system in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which can be those described with reference to Figure 19 and 20those described with reference to the Figure 22 In step 710 of the method, the host computer provides user data. In an optional substep (not shown) the host computer provides the user data by executing a host application. In step 720, the host computer initiates a transmission of the user data to the UE. The transmission can pass via the base station, in accordance with the teachings of the embodiments described in this disclosure. In step 730 (which can be optional), the UE receives the user data carried in the transmission.

[0163] Figure 23 is a flow chart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which can be those described with reference to Figure 19 and 20 those described with reference to the Figure 23 For simplicity of the present disclosure, only drawing references to In step 810 (which can be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step 820, the UE provides user data. In substep 821 of step 820 (which can be optional), the UE provides the user data by executing a client application. In substep 811 of step 810 (which can be optional), the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer. In providing the user data, the executed client application can further take into account user input received from the user. Regardless of the specific manner in which the user data is provided, the UE initiates, in substep 830 (which can be optional), transmission of the user data to the host computer. In step 840 of the method, the host computer receives the user data transmitted from the UE, in accordance with the teachings of the embodiments described in this disclosure.

[0164] Figure 24 is a flow chart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which can be those described with reference to Figure 19 and 20 those described with reference to the Figure 24 For simplicity of the present disclosure, only drawing references to In step 910 (which can be optional), the base station receives user data from the UE, in accordance with the teachings of the embodiments described in this disclosure. In step 920 (which can be optional), the base station initiates a transmission of the received user data to the host computer. In step 930 (which can be optional), the host computer receives the user data carried in the transmission initiated by the base station.

[0165] Figure 25 A method 1000 performed by a network node 160 according to certain embodiments is depicted. At step 1002, the network node determines a number of Time-Sensitive Communication (TSC) and / or Time-Sensitive Network (TSN) domains 12 present in the network. At step 1004, the network node 160 instantiates a plurality of virtual bridges 14. Each virtual bridge 14 serves a particular TSC and / or TSN domain of the plurality of TSC and / or TSN domains 12.

[0166] In certain embodiments, the network node is a core network node 160c.

[0167] In certain embodiments, the core network node 160c includes one or more of an Application Function (AF), an Operations and Maintenance (OAM), and a Fifth Generation (5G) Open Interface defined by 5G-ACIA.

[0168] In certain embodiments, determining the number of TSC and / or TSN domains 12 includes determining a number of Core Network Controllers (CNCs) 16 in the network.

[0169] In certain embodiments, instantiating the plurality of virtual bridges 12 includes instantiating a plurality of network functions 21. Each network function is associated with a TSC and / or TSN domain 12 and / or a virtual bridge 14.

[0170] In certain embodiments, determining the number of TSC and / or TSN domains includes receiving information from a non-3GPP network controller, such as, for example, a CNC 16.

[0171] In certain embodiments, the information includes network topology information, geographic locations of 5G System (5GS) ports 17, VLAN information, DNNs, and S-NSSAIs.

[0172] In certain embodiments, for each TSC and / or TSN domain 12, a different core network controller 16 manages one or more of the plurality of virtual bridges 14.

[0173] In certain embodiments, the number of TSC and / or TSN domains 12 includes a plurality of TSC and / or TSN domains, and instantiating the plurality of virtual bridges 14 includes: determining how many ports 17 and user plane functions 18 are needed for a particular TSC and / or TSN domain of the plurality of TSC and / or TSN domains 12; and instantiating the user plane functions 18.

[0174] In certain embodiments, at least one virtual bridge 14 is part of a higher TSC and / or TSN domain 12.

[0175] In particular embodiments, a first CNC 16 higher up in the hierarchy provides communication between at least two other CNCs 16 lower in the hierarchy than the first CNC 16.

[0176] In particular embodiments, at least one virtual bridge 61, 71 acts as its own TSC and / or TSN domain.

[0177] In particular embodiments, at least one TSC and / or TSN domain 71 provides connectivity and / or transport services for other TSC and / or TSN domains 12.

[0178] In particular embodiments, at least one TSC and / or TSN domain 71 provides connectivity and / or transport services between at least two local production domains 12.

[0179] In particular embodiments, different CNCs 16 configure each port pair group of a virtual bridge 14.

[0180] In particular embodiments, each virtual bridge 14 is managed by a different CNC 16.

[0181] In particular embodiments, a first CNC 16 higher up in the hierarchy configures at least one TSC and / or TSN flow path 62 between multiple TSC and / or TSN domains 12 lower in the hierarchy.

[0182] Figure 26 A schematic block diagram of a virtual apparatus 1100 in a wireless network (e.g., the wireless network shown in Figure 14 The apparatus can be implemented in a wireless device or network node (e.g., the wireless device 110 or network node 160 shown in Figure 14 The apparatus 1100 is operable to carry out the example method described with reference to Figure 25 and possibly any other procedures or methods disclosed herein. It is also contemplated that the methods Figure 25 described with reference to FIG. 13 need not be carried out by the apparatus 1100 alone. At least some operations of the method can be performed by one or more other entities.

[0183] Virtual apparatus 1100 can include processing circuitry, which can comprise one or more microprocessor or microcontrollers, as well as other digital hardware, which can include digital signal processors (DSPs), special-purpose computer chips, or the like. The processing circuitry can be configured to execute program code stored in memory, which can include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc. In several embodiments, the program code stored in the memory includes program instructions for implementing one or more telecommunication and / or data

[0184] According to certain embodiments, determining module 1110 can perform certain determining functions of apparatus 1100. For example, determining module 1110 can determine a number of Time-Sensitive Communication (TSC) and / or Time-Sensitive Network (TSN) domains 12 that exist in a network.

[0185] According to certain embodiments, instantiation module 1120 can perform certain instantiation functions of apparatus 1100. For example, instantiation module 1120 can instantiate a plurality of virtual bridges 14. Each virtual bridge 14 serves a particular TSC and / or TSN domain of the plurality of TSC and / or TSN domains 12.

[0186] As used herein, the term “unit” can have conventional meaning in the field of electronics, electrical devices, and / or electronic devices, and can include, for example, electrical and / or electronic circuitry, devices, modules, processors, memories, logic solid state and / or discrete devices, computer programs or instructions, and / or the like, for performing various tasks, processes, computations, outputs, and / or displays, as described, for example, in the various embodiments.

[0187] Figure 27 A method 1200 performed by a network node 160 is depicted, according to certain embodiments. At step 1202, network node 160c determines how many TSC and / or TSN domains exist in a network, where the network includes a plurality of TSC and / or TSN domains. At step 1204, network node 160c instantiates at least one virtual bridge 14, where each virtual bridge serves at least one TSC and / or TSN domain 12. In some embodiments, network node 160c instantiates at least one virtual bridge 14 for each TSC and / or TSN domain of the plurality of TSC domains 12.

[0188] In a particular embodiment, the network node is a core network node 160c.

[0189] In another particular embodiment, the core network node 160c comprises at least one of an AF 21, an OAM, and a network exposure interface.

[0190] In a particular embodiment, determining how many TSC and / or TSN domains exist comprises determining how many CNC controllers exist in the network.

[0191] In a particular embodiment, instantiating the at least one virtual bridge 14 comprises instantiating at least one network function 21, and each network function is associated with at least one TSC and / or TSN domain, or with at least one virtual bridge.

[0192] In a particular embodiment, determining how many TSC and / or TSN domains exist comprises receiving information from a non-3GPP network controller. In another particular embodiment, the non-3GPP network controller comprises a CNC controller 16. In yet another particular embodiment, the non-3GPP network controller comprises an SDN controller.

[0193] In another particular embodiment, the received information comprises: network topology information; geographical location of 5G system, 5GS, ports; VLAN information; DNN; and / or S-NSSAI.

[0194] In a particular embodiment, the instantiating of the at least one virtual bridge is performed in dependence on how many TSC and / or TSN domains exist in the network.

[0195] In a particular embodiment, for each TSC domain, a different CNC controller manages at least one bridge, which is virtual or fixed.

[0196] In a particular embodiment, instantiating the at least one virtual bridge comprises determining how many ports 17 and user plane functions 18 are needed for a particular TSC and / or TSN domain of the plurality of TSC and / or TSN domains, and instantiating a plurality of user plane functions in dependence on how many user plane functions are needed.

[0197] In a particular embodiment, the at least one virtual bridge is part of a higher TSC and / or TSN domain, and the network node 160c provides communication between at least two other central network configuration controllers that are lower in the hierarchy than a first CNC controller using the first central network configuration controller that is higher in the hierarchy.

[0198] In particular embodiments, the at least one virtual bridge acts as a TSC and / or TSN domain 71. In another particular embodiment, the at least one virtual bridge acting as a TSC / TSN domain provides connectivity and / or transport services for at least one other TSC / TSN domain; and / or the at least one virtual bridge acting as a TSC / TSN domain provides connectivity and / or transport services between at least two local production domains.

[0199] Figure 28 FIGURE 1 illustrates a schematic block diagram of a virtual apparatus 1300 in a wireless network (e.g., the wireless network illustrated in FIGURE 1). The apparatus can be implemented in a wireless device or network node (e.g., the wireless device 110 or network node 160 illustrated in FIGURE 1). The apparatus 1300 is operable to carry out the example method described with reference to FIGURE 1 and possibly any other processes or methods disclosed herein. It is also contemplated that the method of FIGURE 1 is not necessarily carried out by the apparatus 1300 alone. At least some operations of the method can be carried out by one or more other entities. Figure 14 Figure 14 Figure 27 The apparatus 1300 can include processing circuitry, which can include one or more microprocessors, one or more microcontrollers, one or more CPUs, one or more GPUs, one or more Figure 27

[0200] The virtual apparatus 1300 can include processing circuitry, which can include one or more microprocessors or microcontrollers, and other digital hardware, which can include digital signal processors (DSPs), special-purpose computer chips, etc. The processing circuitry can be configured to execute program code stored in memory, which can include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc. In several embodiments, the program code stored in memory includes program instructions for executing one or more telecommunication and / or data communication protocols and program instructions for carrying out one or more of the techniques described herein. In some implementations, the processing circuitry can be used to cause the determining module 1310, the instantiating module 1320, and any other suitable units of the apparatus 1300 to perform their corresponding functions in accordance with one or more embodiments of the present disclosure.

[0201] According to certain embodiments, the determining module 1310 can perform certain determining functions of the apparatus 1300. For example, the determining module 1310 can determine how many TSC and / or TSN domains 12 are present in a network.

[0202] According to certain embodiments, the instantiating module 1320 can perform certain instantiating functions of the apparatus 1300. For example, the instantiating module 1320 can instantiate at least one virtual bridge 14, where each virtual bridge 14 serves at least one TSC and / or TSN domain 12.

[0203] Figure 29 ​​​A method 1400 performed by a network node 160 according to certain embodiments is depicted. In certain embodiments, the network node 160 can comprise a core network node 160c. At step 1402, the network node 160, 160c determines a set of ports 17 in a network system. At step 1404, the network node dynamically models a first virtual bridge 14 for the set of ports 17. In particular embodiments, the set of ports is associated with a first TSC / TSN domain.

[0204] In particular embodiments, the first virtual bridge is managed by a CNC controller associated with the first TSC domain.

[0205] In particular embodiments, the first virtual bridge is associated with a first TSC domain and the first TSC domain is serving a UE. When the UE moves to a second TSC domain, the network node dynamically models a second virtual bridge associated with the second TSC domain.

[0206] In particular embodiments, the set of ports 17 includes at least one ingress port.

[0207] In particular embodiments, the set of ports 17 includes at least one egress port.

[0208] In particular embodiments, the set of ports 17 includes at least one UPF port.

[0209] In particular embodiments, the set of ports 17 includes at least one user equipment (UE) port.

[0210] In particular embodiments, the method further comprises associating the set of ports 17 with a bridge identifier.

[0211] In particular embodiments, the method further comprises reporting the bridge identifier to a network function, such as an application function 21 specific to the virtual bridge 14 or a 3GPP network node.

[0212] In particular embodiments, the network comprises a plurality of virtual bridges 14 and each virtual bridge 14 is managed by a dedicated CNC 16 from a different TSC and / or TSN domain 12.

[0213] In particular embodiments, the virtual bridge 14 is associated with a first TSC and / or TSN domain 12 serving a user equipment (UE) 110 and wherein when the UE 110 moves to a second TSC and / or TSN domain 12, the UE 110 is modeled to another virtual bridge 14 associated with the second TSC and / or TSN domain 12.

[0214] Figure 30 A wireless network (e.g., Figure 14Fig. 16 is a schematic block diagram of a virtual apparatus 1500 that can include processing circuitry configured to implement techniques described herein, according to certain example embodiments. The apparatus can be implemented in a wireless device or network node (e.g., a network node such as the network node 160 or 160c, or a wireless device such as the wireless device 110 or 110c shown in Fig. 1). Figure 14 Fig. 16 is a schematic block diagram of a virtual apparatus 1500 that can include processing circuitry configured to implement techniques described herein, according to certain example embodiments. The apparatus can be implemented in a wireless device or network node (e.g., a network node such as the network node 160 or 160c, or a wireless device such as the wireless device 110 or 110c shown in Fig. 1). Figure 29 the example methods described, as well as any other processes or methods disclosed herein. It should also be understood that, although the terms “first,” “second,” etc. can be used herein to describe various steps or Figure 29 The method of Fig. 16 need not necessarily be performed solely by the apparatus 1500. At least some operations of the method can be performed by one or more other entities.

[0215] The virtual apparatus 1500 can include processing circuitry, which can include one or more microprocessors or microcontrollers, as well as other digital hardware, which can include digital signal processors (DSPs), special-purpose computer chips, etc. The processing circuitry can be configured to execute program code stored in memory, which can include one or more types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc. In several embodiments, the program code stored in memory includes instructions for executing one or more telecommunication and / or data communications protocols and instructions for carrying out one or more of the techniques described herein. In some implementations, the processing circuitry can be used to cause the determining module 1510, the dynamic modeling module 1520, and any other suitable units of the apparatus 1500 to perform their corresponding functions in accordance with one or more embodiments of the present disclosure.

[0216] According to certain embodiments, the determining module 1510 can perform certain determining functions of the apparatus 1500. For example, the determining module 1510 can determine a set of ports 17 in a network system.

[0217] According to certain embodiments, the dynamic modeling module 1520 can perform certain instantiation functions of the apparatus 1500. For example, the instantiation module 1520 can dynamically model a virtual bridge 14 for the set of ports 17.

[0218] Example Embodiments

[0219] Example Embodiment 1. A method performed by a network node, the method comprising: determining a number of time sensitive communication (TSC) and / or time sensitive network (TSN) domains present in a network; and instantiating a plurality of virtual bridges, wherein each virtual bridge serves a particular TSC and / or TSN domain of the plurality of TSC and / or TSN domains.

[0220] Example Embodiment 2. The method of example embodiment 1, wherein the network node is a core network node.

[0221] Example Embodiment 3. The method of any of Example Embodiments 1-2, wherein the core network node comprises one or more of: an Application Function (AF), an Operations and Maintenance (OAM), and a 5thGeneration (5G) Open Interface defined by 5G-ACIA.

[0222] Example Embodiment 4. The method of any of Example Embodiments 1-3, wherein determining the number of TSC and / or TSN domains comprises determining a number of CNCs in the network.

[0223] Example Embodiment 5. The method of any of Example Embodiments 1-4, wherein instantiating the plurality of virtual bridges comprises instantiating a plurality of network functions, each network function associated with a TSC and / or TSN domain and / or virtual bridge.

[0224] Example Embodiment 6. The method of any of Example Embodiments 1-5, wherein determining the number of TSC and / or TSN domains comprises receiving information from a non-3GPP network controller, such as, for example, a CNC.

[0225] Example Embodiment 7. The method of Example Embodiment 6, wherein the information comprises network topology information, geographic location of 5G System (5GS) ports, Virtual Local Area Network (VLAN) information, Data Network Name (DNN), Single Network Slice Selection Assistance Information (S-NSSAI).

[0226] Example Embodiment 8. The method of any of Example Embodiments 1-7, wherein, for each TSC and / or TSN domain, a different CNC controller manages one or more of the plurality of virtual bridges.

[0227] Example Embodiment 9. The method of any of Example Embodiments 1-8, wherein: the number of TSC and / or TSN domains comprises a plurality of TSC and / or TSN domains, and instantiating the plurality of virtual bridges comprises determining how many ports and user plane functions are needed for a particular TSC and / or TSN domain of the plurality of TSC and / or TSN domains; and instantiating the user plane functions.

[0228] Example Embodiment 10. The method of any of Example Embodiments 1-9, wherein at least one virtual bridge is part of a higher TSC and / or TSN domain.

[0229] Example Embodiment 11. The method of Example Embodiment 10, further comprising using a first CNC higher in a hierarchy to provide communication between at least two other CNCs lower in the hierarchy than the first CNC.

[0230] Example embodiment 11. The method of any one of example embodiments 1 to 9, wherein at least one virtual bridge acts as its own TSC and / or TSN domain, wherein the virtual bridge may, for example, be a 5G virtual bridge.

[0231] Example embodiment 12. The method of example embodiment 11, wherein at least one TSC and / or TSN domain provides connectivity and / or transport services for other TSC and / or TSN domains.

[0232] Example embodiment 13. The method of example embodiment 11, wherein at least one TSC and / or TSN domain provides connectivity and / or transport services between at least two local production domains.

[0233] Example embodiment 14. The method of any one of example embodiments 1 to 13, wherein different CNCs configure each port pair group of a virtual bridge.

[0234] Example embodiment 15. The method of any one of example embodiments 1 to 13, wherein each virtual bridge is managed by a different CNC.

[0235] Example embodiment 16. The method of any one of example embodiments 1 to 15, wherein a first CNC higher in a hierarchy configures at least one TSC and / or TSN flow path between a plurality of TSC and / or TSN domains lower in the hierarchy.

[0236] Example embodiment 17. A network node comprising processing circuitry configured to perform any of the methods of example embodiments 1 to 16.

[0237] Example embodiment 18. A computer program comprising instructions which, when executed on a computer, perform any of the methods of example embodiments 1 to 16.

[0238] Example embodiment 19. A computer program product comprising a computer program comprising instructions which, when executed on a computer, perform any of the methods of example embodiments 1 to 16.

[0239] Example embodiment 20. A non-transitory computer readable medium storing instructions which, when executed by a computer, perform any of the methods of example embodiments 1 to 16.

[0240] Example embodiment 21. A method performed by a network node, the method comprising: determining a set of ports in a network system; and dynamically modelling a virtual bridge for the set of ports.

[0241] Example embodiment 22. The method of example embodiment 21, wherein the set of ports comprises at least one ingress port.

[0242] Example embodiment 23. The method of any of example embodiments 21 to 22, wherein the set of ports comprises at least one egress port.

[0243] Example embodiment 24. The method of any of example embodiments 21 to 23, wherein the set of ports comprises at least one UPF port.

[0244] Example embodiment 25. The method of any of example embodiments 21 to 24, wherein the set of ports comprises at least one user equipment (UE) port.

[0245] Example embodiment 26. The method of any of example embodiments 21 to 25, further comprising associating the set of ports with a bridge identifier.

[0246] Example embodiment 27. The method of example embodiment 26, further comprising reporting the bridge identifier to a network function, such as an application function dedicated to virtual bridges or a 3GPP network node.

[0247] Example embodiment 28. The method of any of example embodiments 21 to 27, wherein the network comprises a plurality of virtual bridges, and each virtual bridge is managed by a dedicated CNC from a different TSC and / or TSN domain.

[0248] Example embodiment 29. The method of any of example embodiments 21 to 28, wherein a virtual bridge is associated with a first TSC and / or TSN domain serving a user equipment (UE), and wherein when the UE moves to a second TSC and / or TSN domain, the UE is modelled to another virtual bridge associated with the second TSC and / or TSN domain.

[0249] Example embodiment 30. A network node comprising processing circuitry configured to perform any of the methods of example embodiments 21 to 29.

[0250] Example embodiment 31. A computer program comprising instructions which, when executed on a computer, perform any of the methods of example embodiments 21 to 29.

[0251] Example embodiment 32. A computer program product comprising a computer program comprising instructions which, when executed on a computer, perform any of the methods of example embodiments 21 to 29.

[0252] Example embodiment 33. A non-transitory computer-readable medium storing instructions that, when executed by a computer, perform any of the methods of example embodiments 21 to 29.

[0253] Example embodiment 34. A network node comprising: processing circuitry configured to perform any of the steps of any of the example embodiments 1 to 33; and power supply circuitry configured to supply power to the wireless device.

[0254] Example embodiment 35. A communication system including a host computer comprising: processing circuitry configured to provide user data; and communication interface configured to forward the user data to a cellular network for transmission to a wireless device, wherein the cellular network comprises a network node having radio interface and processing circuitry configured to perform any of the steps of any of the example embodiments 1 to 33.

[0255] Example embodiment 36. The communication system of the preceding embodiment, further including the network node.

[0256] Example embodiment 37. The communication system of the preceding 2 embodiments, further including the wireless device, wherein the wireless device is configured to communicate with the network node.

[0257] Example embodiment 38. The communication system of the preceding 3 embodiments, wherein: the processing circuitry of the host is configured to execute a host application, thereby providing the user data; and the wireless device includes processing circuitry configured to execute a client application associated with the host application.

[0258] Example embodiment 39. A method implemented in a communication system including a host computer, a network node and a wireless device, the method comprising: at the host computer, providing user data; and at the host computer, initiating a transmission carrying the user data to the wireless device via a cellular network comprising the network node, wherein the network node performs any of the steps of any of the example embodiments 1 to 33.

[0259] Example embodiment 40. The method of the preceding example embodiment, further comprising: at the network node, sending the user data.

[0260] Example embodiment 41. The method of the preceding 2 example embodiments, wherein the user data is provided at the host computer by execution of a host application, the method further comprising, at the wireless device, execution of a client application associated with the host application.

[0261] Example embodiment 42. A wireless device configured to communicate with a network node, the wireless device comprising a radio interface and processing circuitry configured to perform the steps of any of the preceding 3 example embodiments.

[0262] Example embodiment 43. A communication system including a host computer comprising a communication interface configured to receive user data originating from a transmission from a wireless device to a network node, wherein the network node comprises a radio interface and processing circuitry configured to perform any of the steps of any of the example embodiments 1 to 33.

[0263] Example embodiment 44. The communication system of the preceding example embodiment, further including the network node.

[0264] Example embodiment 45. The communication system of the preceding 2 example embodiments, further including the wireless device, wherein the wireless device is configured to communicate with the network node.

[0265] Example embodiment 46. The communication system of the preceding 3 example embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application; and the wireless device is configured to execute a client application associated with the host application, thereby providing user data to be received by the host computer.

[0266] Example embodiment 47. The method of any of the preceding example embodiments, wherein the network node comprises a base station.

[0267] Example embodiment 48. The method of any of the preceding example embodiments, wherein the wireless device comprises a user equipment (UE).

[0268] Modifications, additions, or omissions can be made to the systems and apparatuses described herein without departing from the scope of the disclosure. The components of the systems and apparatuses can be integrated or separated. Moreover, the operations of the systems and apparatuses can be performed by more, fewer, or other components. Additionally, operations of the systems and apparatuses can be performed using any suitable logic comprising software, hardware, and / or other logic. As used in this document, "each" refers to each member of a set or each member of a subset of a set.

[0269] Modifications, additions, or omissions can be made to the methods described herein without departing from the scope of the disclosure. The methods can include more, fewer, or other steps. Additionally, steps can be performed in any suitable order.

[0270] While the present disclosure has been described in connection with certain embodiments, modifications and substitutions by one of ordinary skill in the art are feasible without departing from the spirit and scope of the disclosure. For example, the disclosure has been made in terms of a virtual bridge modeled using a 5GS. However, a virtual bridge according to the present disclosure can be implemented by using other wireless systems, such as a 6G system currently under development. Accordingly, the above description of embodiments does not limit the present disclosure. Other changes, modifications and alterations are possible without departing from the spirit and scope of the present disclosure.

Claims

1. A method (1200) performed by network nodes (160, 160c), the method comprising: Determine (1202) how many TSC and / or TSN domains exist in a network system (10; 20; 30; 40; 50; 60; 70; 80) that includes multiple Time-Sensitive Communication (TSC) and / or Time-Sensitive Network (TSN) domains (12); and Instantiate (1204) at least one virtual bridge (14), wherein each virtual bridge serves at least one TSC and / or TSN domain, and wherein instantiating at least one virtual bridge includes: Determine how many ports (17) and user plane functions (18) are required for a specific TSC and / or TSN domain among the plurality of TSC and / or TSN domains; and Instantiate one or more user-face functions as needed.

2. The method according to claim 1, wherein, The network node is the core network node (160c).

3. The method according to claim 2, wherein, The core network node includes at least one of the following: Application function AF(21), Operation and maintenance of OAM, and Network open interfaces.

4. The method according to any one of claims 1 to 3, wherein, Determining how many TSC and / or TSN domains exist includes: determining how many central network configuration CNC controllers (16) exist in the network.

5. The method according to any one of claims 1 to 3, wherein, Instantiating at least one virtual bridge includes: instantiating at least one network function (21), each network function being associated with at least one TSC and / or TSN domain or at least one virtual bridge.

6. The method according to any one of claims 1 to 3, wherein, Determining the number of TSC and / or TSN domains present includes receiving information from non-3GPP network controllers.

7. The method according to any one of claims 1 to 3, wherein, Instantiate at least one virtual bridge based on the number of TSC and / or TSN domains present in the network.

8. The method according to any one of claims 1 to 3, wherein, Each TSC and / or TSN domain includes a CNC controller that manages at least one virtual bridge.

9. The method according to any one of claims 1 to 3, wherein, At least one virtual bridge is part of a higher TSC and / or TSN domain, and the method further includes: using a first CNC controller that is higher in the hierarchy to provide communication between at least two other CNC controllers that are lower in the hierarchy than the first CNC controller.

10. The method according to any one of claims 1 to 3, wherein, At least one virtual bridge acts as a TSC and / or TSN domain (71).

11. A computer program product comprising a computer program, the computer program including instructions that, when executed on a computer, perform a method, the method comprising: Determine how many TSC and / or TSN domains exist in a network system that includes multiple Time-Sensitive Communication (TSC) and / or Time-Sensitive Network (TSN) domains; as well as Instantiate at least one virtual bridge, wherein each virtual bridge serves at least one TSC and / or TSN domain, and wherein instantiating at least one virtual bridge includes: Determine how many ports and user plane functions are required for a specific TSC and / or TSN domain among the plurality of TSC and / or TSN domains; and Instantiate one or more user-face functions as needed.

12. A network node (160, 160c), comprising: The processing circuit (170) is configured as follows: Determine (1202) how many TSC and / or TSN domains exist in a network system (10; 20; 30; 40; 50; 60; 70; 80) that includes multiple Time-Sensitive Communication (TSC) and / or Time-Sensitive Network (TSN) domains (12); and Instantiate (1204) at least one virtual bridge (14), wherein each virtual bridge serves at least one TSC and / or TSN domain, and wherein, when at least one virtual bridge is instantiated, the processing circuitry is configured to: Determine how many ports (17) and user plane functions (18) are required for a specific TSC and / or TSN domain among the plurality of TSC and / or TSN domains; and Instantiate one or more user-face functions as needed.

13. The network node according to claim 12, wherein, The network node is the core network node (160c).

14. The network node according to claim 13, wherein, The core network node includes at least one of the following: Application function AF(21), Operation and maintenance of OAM, and Network open interfaces.

15. The network node according to any one of claims 12 to 14, wherein, When determining how many TSC and / or TSN domains exist, the processing circuitry is configured to determine how many central network configuration CNC controllers (16) exist in the network.

16. The network node according to any one of claims 12 to 14, wherein, When at least one virtual bridge is instantiated, the processing circuitry is configured to instantiate at least one network function (21), each network function being associated with at least one TSC and / or TSN domain or at least one virtual bridge.

17. The network node according to any one of claims 12 to 14, wherein, The processing circuitry is configured to receive information from a non-3GPP network controller.

18. The network node according to any one of claims 12 to 14, wherein, When at least one virtual bridge is instantiated, the processing circuitry is configured to instantiate at least one virtual bridge based on the number of TSC and / or TSN domains present in the network.

19. The network node according to any one of claims 12 to 14, wherein, The processing circuitry is configured to interact with a different CNC controller for each TSC and / or TSN domain, wherein the CNC controller manages at least one virtual bridge.

20. The network node according to any one of claims 12 to 14, wherein, At least one virtual bridge is part of a higher TSC and / or TSN domain, and wherein the processing circuitry is configured to provide communication between at least two other CNC controllers that are lower in the hierarchy than the first CNC controller, using a first CNC controller that is higher in the hierarchy.

21. The network node according to any one of claims 12 to 14, wherein, At least one virtual bridge is configured to act as a TSC and / or TSN domain (71).

22. A method (1400) performed by a network node (160, 160c), the method comprising: Determine (1402) network system (10; 20; 30; 40; 50; 60； A set of ports (17) in 70; 80); Dynamically model (1404) a first virtual bridge (14) for the set of ports, wherein the set of ports is associated with a first Time-Sensitive Communication (TSC) or Time-Sensitive Network (TSN) domain (12), wherein the first virtual bridge is associated with the first TSC or TSN domain, and the first TSC or TSN domain is serving a User Equipment (UE) (22; 200); and When the UE moves to the second TSC or TSN domain, a second virtual bridge associated with the second TSC or TSN domain is dynamically modeled.

23. The method according to claim 22, wherein, The first virtual bridge is managed by a central network configuration CNC (16) controller associated with the first TSC or TSN domain.

24. The method according to any one of claims 22 or 23, wherein, The set of ports includes inbound ports and / or outbound ports.

25. The method according to any one of claims 22 or 23, wherein, The set of ports includes at least one UPF port and / or at least one user equipment (UE) port.

26. The method according to any one of claims 22 or 23, further comprising: Associate the set of ports with a bridge identifier.

27. The method according to any one of claims 22 or 23, wherein, The network comprises multiple virtual bridges, and each virtual bridge is managed by a dedicated CNC controller from a different TSC and / or TSN domain.

28. A computer program product comprising a computer program, the computer program including instructions that, when executed on a computer, perform a method, the method comprising: Identify a set of ports in a network system; A first virtual bridge is dynamically modeled for the set of ports, wherein the set of ports is associated with a first Time-Sensitive Communication (TSC) or Time-Sensitive Network (TSN) domain, wherein the first virtual bridge is associated with the first TSC or TSN domain, and the first TSC or TSN domain is serving a User Equipment (UE); and When the UE moves to the second TSC or TSN domain, a second virtual bridge associated with the second TSC or TSN domain is dynamically modeled.

29. A network node (160), comprising: The processing circuit (170) is configured as follows: Determine the network system (10; 20; 30; 40; 50; 60； A set of ports (17) in 70; 80); A first virtual bridge (14) is dynamically modeled for the set of ports, wherein the set of ports is associated with a first Time-Sensitive Communication (TSC) or Time-Sensitive Network (TSN) domain (12), wherein the first virtual bridge is associated with the first TSC or TSN domain, and the first TSC or TSN domain is serving a User Equipment (UE); and When the UE moves to the second TSC or TSN domain, a second virtual bridge associated with the second TSC or TSN domain is dynamically modeled.

30. The network node according to claim 29, wherein, The first virtual bridge is managed by a central configuration controller (CNC) (16) associated with the first TSC or TSN domain.

31. The network node according to any one of claims 29 or 30, wherein, The set of ports includes at least one of an inbound port and an outbound port.

32. The network node according to any one of claims 29 or 30, wherein, The set of ports includes at least one UPF port.

33. The network node according to any one of claims 29 or 30, wherein, The set of ports includes at least one user equipment (UE) port.

34. The network node according to any one of claims 29 or 30, wherein, The processing circuitry is configured to associate the set of ports with a bridge identifier.

35. The network node according to any one of claims 29 or 30, wherein, The network comprises multiple virtual bridges, and each virtual bridge is managed by a dedicated CNC controller from a different TSC and / or TSN domain.

Images