Deterministic network entity for a communication network - Patents.com

Abstract

A method performed by a network node of a communication network to enable Internet Protocol (IP)-based deterministic networking. The method includes receiving a routing request from a software-defined networking (SDN) controller, where, among other things, the SDN controller is associated with a deterministic network (DetNet), determining whether the routing request conflicts with routing of the communication network, and in response to determining whether the routing request conflicts with routing of the communication network, sending a response to the SDN controller indicating an acceptance or rejection of the routing request. The network node may be a deterministic networking application function (DetNet AF).

Description

[Technical field]

[0001] The present invention relates generally to networking in communication or mobile networks, and more particularly, the present invention relates to Internet Protocol (IP)-based deterministic networking in communication or mobile networks. [Background technology]

[0002] FIG. 1 illustrates a 5G core ("5GC") network 130, network nodes 120 (e.g., 5G base stations ("gNBs"), multiple communications Device 110 (also called user equipment ("UE")), Nothing Illustrated is an example of a radio-frequency ("NR") network (e.g., a fifth-generation ("5G") network).

[0003] 2 illustrates an example of a reference architecture for a 5GC network 130 defined by the 3rd Generation Partnership Project ("3GPP"). In this example, the 5GC network includes a Unified Data Repository ("UDR") 232, a Network Publishing Function ("NEF") 234, a Network Data Analysis Function ("NWDAF") 236, an Application Function ("AF") 238, a Policy Charging Function ("PCF") 242, a Charging Function ("CHF") 244, an Access Control Function ("ACF") 246, and a Data Stream ... and Mobility Management The 5GC network includes an AMF 246, a session management function ("SMF") 248, and a user plane function ("UPF") 250, all communicatively coupled to the SMF 248.

[0004] The PCF 242 supports a unified policy framework for managing network behavior. Specifically, the PCF 242 provides Policy and Charging Control ("PCC") rules to a Policy and Charging Enforcement Function ("PCEF") (e.g., an SMF / UPF that enforces policy and charging decisions according to the provisioned PCC rules).

[0005] The AMF 246 manages UE access (eg, when the UE is connected via different access networks) and UE mobility aspects.

[0006] The SMF 248 supports different functions (eg, the SMF 248 receives PCC rules from the PCF 242 and configures the UPF 250 accordingly).

[0007] The UPF250 transmits user plane traffic based on the rules received from the SMF248. Phi The QoS supports packet handling (e.g., packet inspection and various actions to be taken, such as Quality of Service ("QoS") processing).

[0008] 3rd Generation Partnership Project ("3GPP") networks are increasingly being used for mission-critical applications where low latency and high reliability are important. For Ethernet-based use cases, 3GPP Release 16 defines how to integrate 3GPP networks into TSN networks (see 3GPP TS 23.501, sections 5.27 and 5.28). In 3GPP Release 17, the 3GPP mechanisms for time-sensitive communications are extended to IP-based applications as well. solution includes an AF request scenario, where a particular application can request time-sensitive services from the 3GPP network.

[0009] The Internet Engineering Task Force ("IETF") Deterministic Networking ("DetNet") Working Group has specified the DetNet architecture (RFC 8655), which provides the capability to carry specified unicast or multicast data flows for real-time applications with extremely low data loss rates and bounded latency within a network domain. The DetNet architecture may be applied over a Multiprotocol Label Switching ("MPLS") data network or over an Internet Protocol ("IP")-based data network, with the focus from the perspective of 3GPP networks being IP-based data networks. As a typical example, a DetNet data network may be controlled from a central management entity, such as a Software Defined Networking ("SDN") controller. Summary of the Invention

[0010] Currently, one or more challenges exist: For example, the existing 3GPP Release 16 integration into a TSN network is only applicable to Ethernet networks, but many applications may require an IP solution, and the additional cost of adding native Ethernet support may be high or prohibitive.

[0011] Furthermore, the existing 3GPP Release 17 exposure, which can also be used for IP applications, is not aligned with the DetNet framework defined by the IETF. In the 3GPP Release 17 exposure approach, there is no central controller for the IP network domain and applications communicate their requests directly to the 3GPP network. Therefore, the approach is only applicable to smaller deployments where there are no other IP user plane nodes outside the 3GPP network or where the use of other IP user plane nodes outside the 3GPP network is limited. In other deployments, there may be additional IP nodes or links outside the 3GPP network, which may require a central controller to coordinate and manage resources in the network domain. controller Furthermore, the lack of support for DetNet makes the approach difficult to extend and scale, which is a disadvantage for such deployments.

[0012] Certain aspects of the present disclosure and their embodiments may provide solutions to these or other problems. According to some embodiments, the DetNet Application Function ("AF") entity is a mapping between the IETF-based network management interface for DetNet and the 3GPP interface. The DetNet AF interfaces the SDN controller of the DetNet network and represents (part of) the 3GPP network as an IP router. Based on information received from the SDN controller, the DetNet AF can request QoS reservations for DetNet flows in the 3GPP network. The DetNet AF can also request other configuration updates in the 3GPP network. The DetNet AF then has knowledge of relevant 3GPP network configuration parameters (e.g., topology and routing information, etc.) and provides the information to the SDN controller as it can be expected from the IP router. When the DetNet AF receives an explicit flow routing configuration from the SDN controller, it may compare it to the current routing in the 3GPP network that it knows based on that configuration or based on explicit signaling from an SMF or UPF entity.

[0013] According to additional or alternative embodiments, the DetNet AF accepts requests to the SDN controller if the explicit flow routing information is consistent with the current routing in the system. If the explicit flow routing information is not consistent with the current routing in the system, the DetNet AF can reject the request from the SDN controller or update the routing in the 3GPP system, if applicable.

[0014] In some cases, the DetNet AF entity knows the routing applied in the 3GPP system based on configuration or based on explicit signaling information. The DetNet AF can receive a routing request from the SDN controller, which the DetNet AF accepts if it is consistent with existing routing. If the routing request from the SDN controller is not consistent with the current routing in the system, the DetNet AF can reject the routing request or, if applicable, update the routing in the 3GPP system.

[0015] In an additional or alternative example, the DetNet AF may receive topology and routing information from the 3GPP system, including, for example, information about IP addresses reachable on a given PDU session or on the N6 interface, or IP neighbor nodes reachable on the PDU session or on the N6 interface. The DetNet AF sends the topology information to the SDN controller.

[0016] In an additional or alternative example, the SDN controller may send information about DetNet flows and their QoS requirements to the DetNet AF, which maps this information into QoS requests toward the 3GPP system.

[0017] Certain embodiments may provide one or more of the following technical advantages: According to some embodiments, the DetNet AF entity is aware of the applied routing of the 3GPP system, either based on configuration or based on explicit signaling information. The DetNet AF may receive a routing request from the SDN controller, which the DetNet AF accepts if it is consistent with existing routing. If the routing request from the SDN controller is not consistent with the current routing in the system, the DetNet AF may reject the routing request or, if applicable, update the routing in the 3GPP system.

[0018] According to additional or alternative embodiments, the DetNet AF may receive topology and routing information from the 3GPP system, including, for example, information about IP addresses reachable on a given PDU session or on the N6 interface, or IP neighbor nodes reachable on the PDU session or on the N6 interface. The DetNet AF transmits the topology information to the SDN controller.

[0019] According to additional or alternative embodiments, the SDN controller may send information about DetNet flows and their QoS requirements to the DetNet AF, which maps this information into QoS requests toward the 3GPP system. [Brief description of the drawings]

[0020] The accompanying drawings, which are included to provide a further understanding of the disclosure and are incorporated in and constitute a part of this application, illustrate certain non-limiting embodiments of the inventive concepts.

[0021] [Figure 1] is a schematic diagram illustrating an example of a fifth generation ("5G") network.

[0022] [Diagram 2] is a block diagram illustrating an example of a 5G network architecture.

[0023] [Diagram 3] FIG. 1 is a block diagram illustrating an example 5G system being used as a logical DetNet router in accordance with some embodiments of the present invention.

[0024] [Figure 4] 4 is a flowchart illustrating example operations for operating the 5G system of FIG. 3 as a logical router in accordance with some embodiments of the present invention.

[0025] [Diagram 5] 1 is a block diagram illustrating a communication device according to some embodiments of the present invention.

[0026] [Figure 6] FIG. 1 is a block diagram illustrating a radio access network RAN ​​node (e.g., a base station eNB / gNB) in accordance with some embodiments of the present invention.

[0027] [Figure 7] is a block diagram showing a core network CN node (e.g., an AMF node, an SMF node, etc.) according to some embodiments of the present invention.

[0028] [Figure 8] 1 is a flowchart illustrating the operation of a CN node configured to provide a DetNet AF in accordance with some embodiments of the inventive concepts.

[0029] [Figure 9] 1 is a block diagram of a communication system according to some embodiments.

[0030] [Figure 10] 1 is a block diagram of a user device according to some embodiments.

[0031] [Figure 11] 1 is a block diagram of a network node according to some embodiments.

[0032] [Figure 12] 1 is a block diagram of a host computer in communication with a user device according to some embodiments.

[0033] [Figure 13] 1 is a block diagram of a virtualization environment according to some embodiments.

[0034] [Figure 14] 1 is a block diagram of a host computer that communicates with a user device via a base station over a partially wireless connection, according to some embodiments. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0035] An object of the present invention is to enable Internet Protocol (IP) based deterministic networking in communication or mobile networks.

[0036] The first aspect of the present invention is an Internet Protocol (IP) The present invention relates to a method performed by a network node of a communication network for enabling deterministic networking based on a routing protocol, the method comprising: receiving a routing request from a software defined networking (SDN) controller, where, among other things, the SDN controller is associated with a deterministic network (DetNet), determining whether the routing request conflicts with routing of the communication network, and in response to determining whether the routing request conflicts with routing of the communication network, sending a response to the SDN controller indicating an acceptance or rejection of the routing request.

[0037] According to some embodiments, the communications network includes a fifth generation (5G) network.

[0038] In some embodiments, the network node is a DetNet application function.

[0039] According to some embodiments, the network node comprises a Core Network (CN) node configured to provide DetNet application functionality.

[0040] According to some embodiments, the method further comprises determining control and configuration information for the communications network, the control and configuration information comprising information regarding routing of the communications network.

[0041] According to some embodiments, determining the control and configuration information (control setting information) may include a User Plane Function (UPF), a Session Management Function (SMF), an Access and Mobility Management Function (AMF), and a Policy Management Function (PMF). control The method includes receiving control and configuration information from at least one of the PCFs.

[0042] According to some embodiments, the control and configuration information includes topology and routing information including IP addresses assigned over packet data unit (PDU) sessions in the communications network.

[0043] According to some embodiments, determining control and configuration information for the communications network includes determining multicast distribution rules associated with the communications network, including information related to supported multicast addresses, flows for which multicast distribution is configured, and at least one of a set of outgoing interfaces.

[0044] According to some embodiments, determining whether the routing request conflicts with routing of the communication network includes determining whether the routing request complies with multicast delivery rules.

[0045] According to some embodiments, determining whether the routing request conflicts with routing in the communication network includes determining whether the routing request routes a packet having a given destination address to another packet data unit (PDU) session by comparing it with a destination IP address-to-PDU session mapping.

[0046] According to some embodiments, determining whether the routing request conflicts with routing of the communication network includes determining that the routing request conflicts with routing of the communication network, and sending a response to the SDN controller includes sending a rejection of the routing request.

[0047] According to some embodiments, determining whether the routing request conflicts with routing of the communication network includes determining that the routing request does not conflict with routing of the communication network, and sending a response to the SDN controller includes sending an acceptance of the routing request.

[0048] According to some embodiments, determining whether the routing request conflicts with routing of the communications network includes determining that the routing request conflicts with routing of the communications network.

[0049] According to some embodiments, the method further comprises updating the routing of the communication network to avoid the routing request conflicting with the routing of the communication network.

[0050] According to some embodiments, sending a response to the SDN controller includes sending an acceptance of the routing request in response to updating routing of the communication network.

[0051] According to some embodiments, updating the routing of the communication network includes converting configuration information associated with the routing request into configuration information applicable to the communication network, and transmitting the configuration information applicable to the communication network to a User Plane Function (UPF), a Session Initiator (SIP) and a User Plane Function (UPF) of the communication network. management and sending the request to at least one of a Service Management Function (SMF), an Access and Mobility Management Function (AMF), and a Policy Control Function (PCF).

[0052] According to some embodiments, the method further includes receiving a request from an SDN controller to establish a DetNet flow associated with a routing request in a communication network, where the request to establish the DetNet flow includes quality of service (QoS) requirements for the DetNet flow, determining whether the communication network is capable of satisfying the QoS requirements, and establishing the DetNet flow in response to determining that the communication network is capable of satisfying the QoS requirements.

[0053] According to some embodiments, determining whether the communication network can meet the QoS requirements includes translating the QoS requirements of the DetNet flow into 3rd Generation Partnership Project (3GPP)-specific QoS requirements and sending the 3GPP-specific QoS requirements to a Policy Control Function (PCF) of the communication network.

[0054] According to some embodiments, the method further includes receiving a request from a software defined network SDN controller to establish a deterministic network (DetNet) flow in the communication network, where the request to establish the DetNet flow includes quality of service (QoS) requirements for the DetNet flow, determining whether the communication network is capable of meeting the QoS requirements, and establishing the DetNet flow in response to determining that the communication network is capable of meeting the QoS requirements.

[0055] According to some embodiments, the network node is a Deterministic Networking Application Function (DetNet AF).

[0056] A second aspect of the present invention relates to a method performed by a network node of a communication network for enabling Internet Protocol based deterministic networking, the method comprising receiving a request from a Software Defined Network (SDN) controller to establish a Deterministic Network (DetNet) flow in the communication network, where the request to establish the DetNet flow includes Quality of Service (QoS) requirements for the DetNet flow, determining whether the communication network can meet the QoS requirements, and in response to determining that the communication network can meet the QoS requirements, establishing the DetNet flow.

[0057] Further aspects of the invention relate to a mobile network node configured to perform the respective method described herein. Further aspects of the invention relate to a computer program and product Regarding.

[0058] The objects, features, and advantages of the concepts disclosed herein will become apparent from the following description, claims, and drawings, or may be learned by practice of the described techniques and concepts as set forth herein.

[0059] In general, all terms used in the claims should be interpreted according to their ordinary meaning in the art, unless expressly defined otherwise herein. All references to "a / an / element, apparatus, component, means, module, step, etc." should be openly interpreted as referring to at least one instance of an element, apparatus, component, means, module, step, etc., unless expressly stated otherwise. The steps of any method disclosed herein do not have to be performed in the exact order disclosed, unless expressly stated otherwise.

[0060] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. The embodiments are provided as examples to convey the scope of the subject matter to those skilled in the art. Examples of embodiments of the inventive concept are shown. However, the inventive concept can be embodied in many different forms and should not be construed as being limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the inventive concept to those skilled in the art. It should also be noted that these embodiments are not mutually exclusive. Elements of one embodiment may be implicitly assumed to be present / used in another embodiment.

[0061] Deterministic Networking (DetNet) operates at the IP and Multiprotocol Label Switching (MPLS) layers and provides time-sensitive properties that ensure near-zero packet loss rates and bounded latency. DetNet is intended for networks under a single administrative control or within a closed group of administrative controls, and therefore not for large groups of domains such as the Internet.

[0062] DetNet is applicable to many use cases in the industrial automation vertical for industrial machine-to-machine communication, smart grid, etc. DetNet can provide deterministic QoS when UDP / IP is the transport of choice for deterministic field-level communication.

[0063] 5GS is deployed within the DetNet IP data plane network. DetNet support in 3GPP can be achieved by reusing the TSC framework for deterministic QoS and time synchronization services.

[0064] The DetNet AF is defined to provide a mapping between the central DetNet controller entity and the 5G system. The mapping includes translating DetNet traffic profiles and flow specifications to 5GS QoS parameters and TSCAI. The DetNet AF handles the DetNet YANG group, processing and mapping, which reuses the TSC framework.

[0065] Existing 3GPP routing mechanisms can be reused for DetNet, and a typical 3GPP scenario with IP end hosts behind the UE is assumed.

[0066] Figure 3 illustrates an overview of the system. The 3GPP system includes RAN and UPF entities in the user plane, UE (e.g., communication device), AMF, SMF, and PCF as part of the system architecture defined in 3GPP TS23.501. DetNet flows within the DetNet domain are controlled by an SDN controller. The 5G system is represented as a DetNet IP router (which could be a UPF unit per network) that goes to the SDN controller.

[0067] The DetNet AF is a logical entity in the 3GPP system and represents the 5G system as a logical IP router to the SDN controller. The DetNet AF collects the necessary control and configuration information from the 5G system. The DetNet AF receives configuration from the SDN controller, which can be done using YANG modeling, for example, via a Netconf interface between the SDN controller and the DetNet AF. The DetNet AF translates the configuration information to the 3GPP domain and can request the necessary configuration / control updates in the 3GPP network. The DetNet AF responds to requests from the SDN controller and provides the necessary information to the SDN controller so that the SDN controller has a complete view of the DetNet network and can set up DetNet flows that meet the necessary QoS requirements.

[0068] In some instances, especially if the DetNet AF is not considered trustworthy, there may be a NEF entity between the PCF and the DetNet AF. The NEF may relay information.

[0069] According to some embodiments, the DetNet AF can collect information about the topology and routing of the 3GPP network. This can be based on configuration, for example the DetNet AF may be pre-configured with IP addresses assigned over PDU sessions in a given network and neighbors of the UPF over the N6 interface (or other interfaces). There may be one or more IP addresses assigned to a given PDU session. Alternatively, the network topology and routing information may be collected by the DetNet AF using control signaling. This may use the PMIC and BMIC mechanisms and the information elements carried by them, or additional information elements or other signaling mechanisms. The UPF or SMF can provide information about IP addresses assigned to the UE over the individual PDU sessions. There may be a single IP address (single IPv4 and / or single IPv6 address) assigned for a given PDU session, or multiple addresses in case of prefix delegation or framed routing support. This information can be based on existing IP address allocation mechanisms, as IP addresses are assigned by the SMF or UPF. The UPF or SMF may also provide information about neighbors that are reachable via the N6 interface, if available. This information may be based on a neighbor discovery protocol running on that interface or a protocol capable of providing neighbor information, such as an IGP. If there are multiple N6 interfaces, this information may be provided separately for each interface. If other interfaces exist (such as N19), neighbor information may be provided for those interfaces as well. In addition to the neighbor information, the SMF or UPF may also provide information about IP addresses assigned to the interface (such as the N6 interface) or other interface identifiers (e.g., port numbers).The information may be sent from the UPF to the DetNet AF via the SMF, PCF, in the BMIC or PMIC information, or using other signaling mechanisms. Note that the information may be provided from the NW-TT. Alternatively, the IP address information may also be provided from the device side (UE), which may also arrive from the DS-TT. The UPF may also assign port numbers or other interface identifiers corresponding to the PDU sessions and N6 or other interfaces, although such port number assignment is optional and may not be used in all embodiments.

[0070] The SDN controller can provide explicit flow routes to DetNet routers. Therefore, the SDN controller can also provide such explicit flow routes to the DetNet AF. These flow routes can configure flow specifications using filters (6-tuples of header field combinations) that specify, for a given traffic, which outgoing interface the traffic should be routed to. This allows the SDN controller to assign paths to DetNet flows so that QoS requirements can be met.

[0071] However, in the 3GPP domain, routing is typically determined in the UPF and does not need to be changed individually for flows. This is due to typical deployments where there are end hosts behind the UE, not routers. Therefore, in typical deployments, there is no need to update the routing.

[0072] According to some embodiments, the DetNet AF may verify based on topology information (based on configuration or based on explicit signaling from the SMF or UPF via the PCF) that it has, and the existing routing meets the requirement of explicit routing from the SDN controller (based on mapping of UE's IP address to PDU session). If the explicit routing request from the SDN controller is consistent with the routing and topology information in the 3GPP system, i.e., the SDN controller does not request to route traffic that is known to be different from how packets are routed in the 3GPP system, the DetNet AF may accept the SDN controller's explicit routing request without taking further action, i.e., without routing updates in the 3GPP system. The DetNet AF may store the explicit route provided by the SDN controller, including the flow specification and outgoing interface, as information that may be useful in determining the PDU session associated with a given flow. If the SDN controller requests to route traffic that is known to be different from how packets are routed in the 3GPP system, the DetNet AF may reject the SDN controller's request.

[0073] FIG. 4 illustrates an exemplary operation performed by the DetNet AF to represent the 5G system as a logical router to the SDN controller. In block 1, the DetNet AF collects information about the topology and route information of the 3GPP system. In block 2, the DetNet AF obtains an explicit routing request from the SDN controller. In block 3, the DetNet AF verifies whether the explicit routing request from the SDN controller conflicts with the topology and routing information of the 3GPP system. Specifically, the DetNet AF verifies whether the explicit routing request from the SDN controller is a request to route a packet with a given destination address to another PDU session, compared with the destination IP address-to-PDU session mapping known in the 3GPP system. In block 4, if the DetNet AF's explicit routing request conflicts with the 3GPP system's routing, the DetNet AF rejects the SDN controller's routing request; otherwise, the DetNet AF accepts the SDN controller's request without necessarily updating the routing in the 3GPP system. The DetNet AF may store explicit routes provided by the SDN controller, including the flow specification and outgoing interface, as information that may be useful in determining the PDU session associated with a given flow.

[0074] The operation of Figure 4 is based on the assumption that there are only end hosts behind the UE and no routers involved in the connectivity between outside the 3GPP system and the UE. Therefore, there is only a single route towards the UE, and therefore the UPF has no choice and can only select a single PDU session when it needs to select a route towards an IP host behind the UE. In more complex topologies where this assumption is not met, this simple procedure is not sufficient, but in 3GPP deployments the assumption for simple topologies is usually met.

[0075] It is not excluded that in some instances, in block 4, the DetNet AF may update the routing in the 3GPP system when there may be a possibility of such an update. To that end, the explicit routing request may for example be forwarded to an SMF (one of the SMFs for the concerned PDU session or the SMF designated for routing updates in a given network), which may then update the PDR and FAR rules in the UPF to update the routing. Alternatively, the explicit routing request may be forwarded directly to the UPF, which may update its internal routing table accordingly. As yet another alternative, the explicit routing information may be forwarded to a router external to the UPF, which may update the routing accordingly, and the UPF monitors the routing based on the header fields indicated by the external router. However, not all of these options are required for the present invention. The present invention proposes that the DetNet AF may determine by itself whether the explicit routing request complies with the 3GPP routing rules based on the topology and routing information of the 3GPP network, and accept or reject the request of the SDN controller based on that determination.

[0076] The above description focuses on the unicast case, however, the invention can be applied to multicast as follows.

[0077] According to some embodiments, the UPF may be configured to provide support for multicast. For a particular multicast address or for a given set of flows specified by filter criteria, the UPF may replicate traffic destined for a set of outgoing interfaces. This may be set by implicit configuration or by the multicast protocol. The UPF or SMF may provide information about the set of multicast addresses it supports or flows that are configured for multicast delivery and the outgoing interfaces. This information may be provided, for example, on board the BMIC or similar information sent from the UPF to the DetNet AF.

[0078] In some instances where the SDN controller configures explicit routing for multicast, the DetNet AF may similarly check whether the SDN controller's request complies with the multicast distribution rules configured in the UPF. If the request complies with the multicast routing in the UPF, the DetNet AF may accept the request, otherwise it may reject the request. (Alternatively, it is not excluded that the DetNet AF may request the SMF or UPF to update the multicast routing as necessary, if the system capability exists.)

[0079] According to some embodiments, the SDN controller can provide DetNet flow related parameters, which can include an IP flow identifier and standard specification, traffic specification and QoS requirements. The DetNet AF can use these parameters to request QoS for the DetNet flow from the 3GPP system. The DetNet AF can forward some or all of these parameters to a PCF in the 3GPP system to set up the QoS flow in the 3GPP system. Alternatively, the DetNet AF can map some or all of these parameters to other QoS parameters based on a pre-configured mapping table in the DetNet AF or using an algorithmic mapping, and use the other parameters to request QoS from the 3GPP system.

[0080] According to an additional or alternative embodiment, the DetNet AF needs to determine the input and output ports of a given DetNet flow in the DetNet AF. This is required to determine which PDU session carries a given DetNet flow, so that the DetNet AF can request QoS for the given PDU session (or more precisely, for the AF session between the PCF and the DetNet AF corresponding to the given PDU session). Furthermore, the DetNet AF also needs to determine whether a given DetNet flow is downlink or uplink, so that it can provide the flow direction (downlink / uplink) to the 3GPP system. It is also possible to have a UE-to-UE DetNet flow, including uplink and downlink legs with corresponding PDU sessions. (In case of multicast, there are multiple downlink legs).

[0081] According to some embodiments, the outgoing port in the downlink direction and the corresponding PDU session can be identified based on the routing information collected by the DetNet AF, as described above, from the 3GPP system, from explicit flow routing information from the SDN controller, or from the configuration. For this purpose, it is advantageous for the SDN controller to also specify the destination IP address as part of the DetNet IP flow identifier and specification. The destination IP address can be mapped based on the IP address assigned to the given PDU session. Alternatively, if the SDN controller has provided the accepting DetNet AF with explicit flow routing information, that information is also suitable for determining the PDU session in the downlink direction. For this purpose, the DetNet AF stores the explicit routing information, which includes the flow specification and the output port. output Based on the port, the PDU session is granted. controller If the AF controls this information, other flow specification attributes may be mapped to the appropriate port / PDU session using pre-configured tables within the DetNet AF.

[0082] In the upstream direction, the incoming port in the upstream direction and the corresponding PDU session can be identified based on the route information collected by the DetNet AF, from the 3GPP system or from the configuration, as described above. For this purpose, it is advantageous for the SDN controller to also specify the source IP address as part of the DetNet IP flow identifier and specification. The source IP address can be mapped based on the IP address assigned to a given PDU session. If the source IP address is not specified by the SDN controller for a DetNet flow, other flow specification attributes may be mapped to the appropriate port / PDU session using pre-configured tables in the DetNet AF.

[0083] In some examples, for a DetNet flow spanning from one UE to another, if the SDN controller specifies both the source and destination IP addresses, the incoming and outgoing ports / PDU sessions may be determined, otherwise this determination may be based on other attributes and pre-configured mapping tables in the DetNet AF, or the downlink PDU session may be determined based on the outgoing port of an explicit route, as described above.

[0084] According to some embodiments, in cases where a 3GPP network is integrated into the system, it is advantageous for the SDN controller to specify both the source and destination IP addresses for a DetNet flow, which makes it easier to determine the corresponding PDU session.

[0085] According to some embodiments, a PDU session in the DetNet AF may be identified. In some examples, a PDU session in the DetNet AF may be identified by an IP address assigned to the PDU session. If multiple IP addresses are assigned, it is possible to select one of them for identification. The IP address used for identification may be flagged. The IP address may be provided to the DetNet AF from the UPF (or a NW-TT entity residing in the UPF), or from the SMF, or from the UE (or a DS-TT entity residing in the UE side device). In additional or alternative examples, a PDU session in the DetNet AF may be identified by a port number assigned by the UPF. In additional or alternative examples, a PDU session in the DetNet AF may be identified by another identifier, such as an identifier of the N4 session corresponding to the PDU session, or a locally assigned or configured interface identifier, or an identifier assigned by the DetNet AF and communicated to the SMF and UPF.

[0086] According to additional or alternative embodiments, an interface identifier (such as a port number or other interface identifier) ​​may also be provided from the DetNet AF to the SDN controller so that the SDN controller can later reference that interface identifier when specifying an outgoing interface for an explicit route.

[0087] FIG. 5 illustrates a communication device configured to provide wireless communication in accordance with an embodiment of the inventive concept. Device 500 (also referred to as a mobile terminal, mobile communications terminal, wireless device, wireless communication device, wireless terminal, mobile device, wireless communication terminal, user equipment ("UE"), user equipment node / terminal / device, etc.). (The communication device 500 may be, for example, wireless devices UE9012A, UE9012B, as well as wired or wireless devices UE9012C, UE9012D of FIG. 9, UE1000 of FIG. 10, virtualized hardware of FIG. 13, etc.) Eh14, and virtual machines 1308A, 1308B, and UE 1406 of FIG. 14, all of which should be considered interchangeable with the examples and embodiments described herein and are within the intended scope of the present disclosure unless otherwise noted. As shown, the communication device 500 has a transceiver circuit 501 (e.g., corresponding to the interface 1012 of FIG. 10 having a transmitter 1018 and a receiver 1020, also referred to as a transceiver) including a transmitter and a receiver configured to provide uplink and downlink wireless communication with an antenna 507 (e.g., corresponding to the antenna 1022 of FIG. 10) and a base station (e.g., corresponding to the network nodes 9010A, 9010B of FIG. 9, the network node 1100 of FIG. 11, and the network node 1404 of FIG. 14, referred to as a RAN node) of a radio access network. The communication device 500 may further include a processing circuit 503 (e.g., corresponding to the processing circuit 1002 of FIG. 10 or the control system 1312 of FIG. 13, also referred to as a processor) and a memory circuit 505 (e.g., corresponding to the memory 1010 of FIG. 9, also referred to as a memory) coupled to the processing circuit 503, which is coupled to the transceiver circuit. The memory circuit 505 may include computer readable program code that, when executed by the processing circuit 503, causes the processing circuit 503 to perform operations according to embodiments disclosed herein. According to other embodiments, the processing circuit 503 may be defined to include a memory such that a separate memory circuit is not required. The communication device 500 may also include an interface (e.g., a user interface) coupled to the processing circuit 503, and / or the communication device 500 may be incorporated into a vehicle.

[0088] As described herein, the operations of the communication device 500 may be performed by the processing circuitry 503 and / or the transceiver circuitry 501. For example, the processing circuitry 503 may control the transceiver circuitry 501 to transmit communications through the transceiver circuitry 501 over an air interface to a radio access network node (also referred to as a base station) and / or receive communications through the transceiver circuitry 501 over an air interface from a RAN node. Additionally, modules may be stored in the memory circuitry 505 that may provide instructions such that, when instructions of the modules are executed by the processing circuitry 503, the processing circuitry 503 performs respective operations (e.g., operations described below with respect to exemplary embodiments relating to a wireless communication device). According to some embodiments, the communication device 500 and / or elements / functionality thereof may be embodied as virtual nodes / nodes and / or virtual machines / machines.

[0089] 6 is a block diagram illustrating elements of a RAN radio access network ("RAN") node 600 (also referred to as a network node, base station, eNodeB / eNB, gNodeB / gNB, etc.) configured to provide cellular communications, in accordance with an embodiment of the inventive concept. (RAN node 600 may be provided, for example, as described below with respect to network nodes 9010A, 9010B of FIG. 9, network node 1100 of FIG. 11, hardware 1304 or virtual machines 1308A, 1308B of FIG. 13, and / or base station 1404 of FIG. 14, all of which are considered interchangeable in the examples and embodiments described herein and should be within the intended scope of the present disclosure.) As shown, RAN node 600 includes: MobileThe RAN node 600 may include a transceiver circuit 601 (e.g., also referred to as a transceiver, corresponding to a portion of the RF transceiver circuit 1112 and the radio front-end circuit 1118 of FIG. 11) including a transmitter and a receiver configured to provide uplink and downlink wireless communication with terminals. The RAN node 600 may include a network interface circuit 607 (e.g., also referred to as a network interface, corresponding to a portion of the communication interface 1106 of FIG. 11) configured to provide communication with other nodes (e.g., with other base stations) of the RAN and / or core network ("CN"). The network node 600 may also include a processing circuit 603 (e.g., also referred to as a processor, corresponding to the processing circuit 1102 of FIG. 11) coupled to the transceiver circuit 601, and a memory circuit 605 (e.g., also referred to as a memory, corresponding to the memory 1104 of FIG. 11) coupled to the processing circuit. The memory circuit 605 may include computer readable program code that, when executed by the processing circuit 603, causes the processing circuit 603 to perform operations according to embodiments disclosed herein. According to other embodiments, the processing circuit 603 may be defined to include memory such that a separate memory circuit 605 is not required.

[0090] As described herein, the operations of the RAN node 600 may be performed by the processing circuitry 603, the network interface 607, and / or the transceiver 601. For example, the processing circuitry 603 may control the transceiver 601 to transmit downlink communications through the transceiver 601 over the air interface to one or more mobile terminals (UEs) and / or to receive uplink communications through the transceiver 601 over the air interface from one or more mobile terminals (UEs). Similarly, the processing circuitry 603 may control the network interface 607 to transmit communications through the network interface 607 to one or more other network nodes and / or to receive communications through the network interface from one or more other network nodes. Additionally, modules may be stored in the memory 605 that may provide instructions for the processing circuitry 603 to perform respective operations (e.g., operations described below with respect to exemplary embodiments relating to a RAN node) when instructions of the modules are executed by the processing circuitry 603. According to some embodiments, the RAN node 600 and / or elements / functions thereof may be embodied as virtual nodes / nodes and / or virtual machines / machines.

[0091] According to some other embodiments, the network node may be implemented as a Core Network ("CN") node without a transceiver. According to such embodiments, a transmission to the wireless communication device UE may be initiated by the CN node such that the transmission to the wireless communication device UE is provided through a network node that includes a transceiver (e.g., through a base station or a RAN node). According to embodiments in which the network node is a RAN node that includes a transceiver, initiating the transmission may include transmitting through the transceiver.

[0092] FIG. 7 illustrates components of a CN node (e.g., SMF (Session Management Function) node, AMF (Access and Mobility Management Function) node) of a communication network configured to provide cellular communication in accordance with an embodiment of the present invention. node ) etc.) block 7 shows a CN node 700. (The CN node 700 may be provided, for example, as described below with respect to the core network node 9008 of FIG. 9, the hardware 1304 of FIG. 13, or the virtual machines 1308A, 1308B, all of which are considered interchangeable in the examples and embodiments described herein and should be within the intended scope of the present disclosure.) As shown, the CN node 700 may include a network interface circuit 707 configured to provide communication with other nodes of the core network and / or radio access network RAN. The CN node 700 may also include a processing circuit 703 (also referred to as a processor) coupled to the network interface circuit, and a memory circuit 705 (also referred to as a memory) coupled to the processing circuit. The memory circuit 705 may include computer readable program code that, when executed by the processing circuit 703, causes the processing circuit 703 to perform operations according to embodiments disclosed herein. According to other embodiments, the processing circuit 703 may be defined to include a memory such that a separate memory circuit is not required.

[0093] As described herein, the operations of CN node 700 may be performed by processing circuitry 703 and / or network interface circuitry 707. For example, processing circuitry 703 may control network interface circuitry 707 to transmit communications to one or more other network nodes through network interface circuitry 707 and / or receive communications from one or more other network nodes through network interface circuitry. Additionally, modules may be stored in memory 705 that, when their instructions are executed by processing circuitry 703, provide instructions such that processing circuitry 703 performs respective operations (e.g., operations described below with respect to exemplary embodiments related to a core network node). According to some embodiments, CN node 700 and / or elements / functions thereof may be embodied as virtual nodes / nodes and / or virtual machines / machines.

[0094] In the following description, the network node may be either the core network node 700, the core network node 9008, the hardware 1304, or the virtual machines 1308A, 1308B, but the core network node 700 shall be used to describe the functionality of the operation of the network node. The operation of the core network (CN) node 700 (implemented using the structure of FIG. 7) will be described using the flowchart of FIG. 8 according to some embodiments of the inventive concept. For example, modules may be stored in the memory 705 of FIG. 7, and these modules may provide instructions such that when the instructions of the modules are executed by the respective CN node processing circuitry 703, the processing circuitry 703 performs the respective operations of the flowchart.

[0095] 8 is a flow chart illustrating example operations performed by a network node of a communication network to enable Internet Protocol (IP)-based deterministic networking ("DetNet"). According to some embodiments, the communication network includes a fifth generation ("5G") network, and the network node includes a core network ("CN") node configured to provide DetNet application functionality.

[0096] In block 810, the processing circuit 703 determines control and configuration information for the communication network. According to some embodiments, the control and configuration information includes information regarding routing of the communication network. According to some embodiments, determining the control and configuration information for the communication network includes information regarding a User Plane Function (UPF), a Session Management Function (SMF), an Access and Mobility Management Function (AMF), and a Policy Management Function (PMF). control The method includes receiving control and configuration information from at least one of the PCFs.

[0097] According to additional or alternative embodiments, the control and configuration information includes topology and routing information including IP addresses assigned over packet data unit (PDU) sessions within the communications network.

[0098] According to further or alternative embodiments, determining control and configuration information for the communications network includes determining multicast distribution rules associated with the communications network, including information related to supported multicast addresses, flows for which multicast distribution is configured, and at least one of a set of outgoing interfaces.

[0099] At block 820, the processing circuit 703 receives a routing request via the network interface 707 from an SDN controller associated with the DetNet.

[0100] At block 830, the processing circuit 703 determines whether the routing request conflicts with routing of the communication network. According to some embodiments, determining whether the routing request conflicts with routing of the communication network includes determining whether the routing request complies with multicast delivery rules. According to additional or alternative embodiments, determining whether the routing request conflicts with routing of the communication network includes determining whether the routing request complies with multicast delivery rules for a packet data unit (PDU) session. To The method includes comparing the destination IP address with a mapping of the destination IP address to determine whether to route a packet having a given destination address to a different PDU session.

[0101] In block 840, the processing circuit 703 updates the routing of the communication network to avoid the routing request colliding with the routing of the communication network. According to some embodiments, updating the routing of the communication network includes converting configuration information related to the routing request into configuration information applicable to the communication network, and converting the configuration information applicable to the communication network into configuration information applicable to a user plane function (UPF), a session management and sending the request to at least one of a Service Management Function (SMF), an Access and Mobility Management Function (AMF), and a Policy Control Function (PCF) of the communication network.

[0102] At block 850, the processing circuit 703 sends a response indicating acceptance or rejection of the routing request to the SDN controller via the network interface 707. According to some embodiments, determining whether the routing request conflicts with routing of the communication network includes determining that the routing request conflicts with routing of the communication network, and sending the response to the SDN controller includes sending a rejection of the routing request.

[0103] According to another embodiment, determining whether the routing request conflicts with routing of the communication network includes determining that the routing request does not conflict with routing of the communication network, and sending a response to the SDN controller includes sending an acceptance of the routing request.

[0104] According to additional or alternative embodiments, determining whether the routing request conflicts with routing of the communications network includes determining that the routing request conflicts with routing of the communications network, and sending an acceptance of the routing request in response to updating the routing of the communications network.

[0105] At block 860, the processing circuit 703 receives a request to establish a DetNet flow associated with a routing request in the communication network from the SDN controller via the network interface 707. The request to establish a DetNet flow may include QoS requirements for the DetNet flow.

[0106] At block 870, the processing circuit 703 determines whether the communication network can meet the QoS requirements. According to some embodiments, determining whether the communication network can meet the QoS requirements includes translating the QoS requirements of the DetNet flow into Third Generation Partnership Project (3GPP) specific QoS requirements and sending the 3GPP specific QoS requirements to a Policy Control Function (PCF) of the communication network.

[0107] At block 880, the processing circuit 703 establishes a DetNet flow.

[0108] The various operations from the flowchart in FIG. ofFor some embodiments of the code and related methods, for example, the operations of blocks 840, 860, 870, and 880 of FIG. 8 may be optional for the method of example embodiment 1 (described below).

[0109] FIG. 9 illustrates an example communication system 9000 according to some embodiments.

[0110] In the illustrated example, the communications system 9000 includes a telecommunications network 9002 including an access network 9004, such as a radio access network (RAN), and a core network 9006 including one or more core network nodes 9008. The access network 9004 includes one or more access network nodes, such as network nodes 9010a and 9010b (one or more of which may be generally referred to as network nodes 9010), or any other similar Third Generation Partnership Project (3GPP) access nodes or non-3GPP access points. The network nodes 9010 enable direct or indirect connectivity of user equipment (UE), such as by connecting UEs 9012a, 9012b, 9012c, and 9012d (one or more of which may be generally referred to as UEs 9012) to the core network 9006 via one or more wireless connections.

[0111] Exemplary wireless communication over wireless connections includes transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared, and / or other types of signals suitable for conveying information without the use of wires, cables, or other data conductors. Additionally, according to various embodiments, the communication system 9000 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or be involved in the communication of data and / or signals, whether via wired or wireless connections. The communication system 9000 may include and / or interface with any type of communication, telecommunication, data, cellular, wireless networks, and / or other similar types of systems.

[0112] The UE 9012 is adapted to wirelessly communicate with the network node 9010 and other communication devices. arrangement The network node 9010 may be any of a wide variety of communications devices, including a wireless device that is configured, operable, and / or capable of communicating with the UE 9012 and / or other network nodes or devices in the telecommunications network 9002, directly or indirectly, to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as management in the telecommunications network 9002.

[0113] According to the illustrated embodiment, the core network 9006 connects the network nodes 9010 to one or more hosts, such as the host 9016. These connections may be direct or indirect through one or more intermediate networks or devices. In other examples, the network nodes may be directly coupled to the hosts. The core network 9006 may include hardware Eh A and Software EhThe UE may include one or more core network nodes (e.g., core network node 9008) comprised of a plurality of network components. Features of these components may be substantially similar to those described with respect to the UE, the network node, and / or the host, and therefore, those descriptions are generally applicable to the corresponding components of the core network node 9008. Exemplary core network nodes include one or more functions of a Mobile Switching Center (MSC), a Mobility Management Entity (MME), a Home Subscriber Server (HSS), an Access and Mobility Management Function (AMF), a Session Management Function (SMF), an Authentication Server Function (AUSF), a Subscription Identifier Unhiding Function (SIDF), a Unified Data Management (UDM), a Security Edge Protection Proxy (SEPP), a Network Exposure Function (NEF), and / or a User Plane Function (UPF).

[0114] The host 9016 may be under the ownership or control of, or may be operated by or on behalf of, a service provider other than an operator or provider of the access network 9004 and / or the telecommunications network 9002. The host 9016 may host various applications to provide one or more services. Examples of such applications include live and pre-recorded audio / video content, data collection services such as searching and compiling data on various ambient conditions detected by multiple UEs, analytics functions, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and monitoring center, or any other such functions performed by a server.

[0115] 9 enables connectivity between UEs, network nodes, and hosts. In that sense, the communication system may be based on, but is not limited to, Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G), wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard (WiFi), and / or World Wide Interoperability for Microwave Access (WiMax), bluetooth (registered trademark), Z-Wave, Near Field Communication (NFC), any other suitable wireless communication standard, such as ZigBee, LiFi, and / or any Low Power Wide Area Network (LPWAN) standard such as LoRa and Sigfox. Specific standards, including , predefined rules or procedures order may be configured to operate in accordance with

[0116] In some examples, the telecommunications network 9002 is a cellular network implementing 3GPP standardized features. Thus, the telecommunications network 9002 may support network slicing to provide different logical networks to different devices connected to the telecommunications network 9002. For example, the telecommunications network 9002 may provide URLLC (Ultra Reliable Low Latency Communication) services to some UEs, while providing eMBB (Enhanced Mobile Broadband) services to other UEs, and / or mMTC (Massive Machine Type Communication) / Massive IoT services to further UEs.

[0117] In some examples, the UE 9012 is configured to transmit and / or receive information without direct human interaction. For example, the UE may be designed to transmit information to the access network 9004 on a predefined schedule, when triggered by an internal or external event, or in response to a request from the access network 9004. Furthermore, the UE may be configured to operate in a single or multi-RAT or multi-standard mode. For example, the UE may operate in any one or combination of Wi-Fi, NR (New Radio), and LTE, i.e., may be configured for Multi-Radio Dual Connectivity (MR-DC), such as E-UTRAN (Evolved UMTS Terrestrial Radio Access Network) New Radio Dual Connectivity (EN-DC).

[0118] In an illustrative example, the hub 9014 communicates with the access network 9004 to facilitate indirect communication between one or more UEs (e.g., UEs 9012c and / or 9012d) and a network node (e.g., network node 9010b). In some examples, the hub 9014 may be a controller, a router, a content source and analysis, or any of the other communication devices described herein with respect to a UE. For example, the hub 9014 may be a broadband router that enables access to the core network 9006 for the UE. As another example, the hub 9014 may be a controller that sends commands or instructions to one or more actuators in the UE. The commands or instructions may be received from the UE, the network node 9010, or by executable code, scripts, processes, or other instructions in the hub 9014. As another example, the hub 9014 may be a data collector that acts as a temporary storage for UE data and may perform analysis or other processing of the data according to some embodiments. As another example, the hub 9014 may be a content source. For example, in the case of a UE that is a VR headset, display, loudspeaker or other media distribution device, the hub 9014 can retrieve, via a network node, data related to VR assets, video, audio, or other media or sensory information, which the hub 9014 then provides directly to the UE, either after performing local processing and / or adding additional local content. In yet another example, the hub 9014 acts as a proxy server or orchestrator for the UEs, among other things, when one or more of the UEs are low energy IoT devices.

[0119] The hub 9014 may have a constant / persistent or intermittent connection to the network node 9010b. The hub 9014 may also enable other communication schemes and / or schedules between the hub 9014 and the UEs (e.g., UEs 9012c and / or 9012d) and between the hub 9014 and the core network 9006. According to other embodiments, the hub 9014 is connected to the core network 9006 and / or one or more UEs via a wired connection. Additionally, the hub 9014 may be configured to connect to an M2M service provider via the access network 9004 and / or to another UE via a direct connection. In some circumstances, a UE may establish a wireless connection with the network node 9010 while still being connected through the hub 9014 via a wired or wireless connection. According to some embodiments, the hub 9014 is a dedicated hub, i.e., a UE that is connected to the network node 9010b via a wired or wireless connection. To UE / UE from Network node 9010b According to other embodiments, the hub 9014 may be a non-dedicated hub, i.e., a device capable of operating to route communications between the UE and the network node 9010b, but capable of further operating as a start point and / or endpoint for a particular data channel.

[0120] FIG. 10 illustrates a UE 1000 according to some embodiments. As used herein, a UE refers to a device capable of, configured, arranged, and / or operable to wirelessly communicate with network nodes and / or other UEs. Examples of UEs include smartphones, move Telephones, mobile phones, Voice over IP (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, gaming consoles or device, music storage devices, playback devices, wearable terminal devices, wireless endpoints, mobile stations, tablets, laptops, laptop embedded equipment (LEE), laptop mounted equipment (LME), smart devices, wireless customer premises equipment (CPE), vehicle mounted or embedded / integrated wireless devices, etc. Other examples include any UE defined by the 3rd Generation Partnership Project (3GPP), including Narrowband Internet of Things (NB-IoT) UE, Machine Type Communication (MTC) UE, and / or enhanced MTC (eMTC) UE.

[0121] A UE may support device-to-device (D2D) communications, for example, by implementing 3GPP standards for sidelink communications, dedicated short-range communications (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, a UE may not necessarily have a user in the sense of a human user who owns and / or operates an associated device. Instead, a UE may represent a device that is intended for sale to or operation by a human user, but may or may not initially be associated with a particular human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to or operation by an end user, but may be associated with or operated for a user (e.g., a smart power meter).

[0122] The UE 1000 includes a processing circuit 1002 operatively coupled to an input / output interface 1006, a power source 1008, a memory 1010, a communication interface 1012, and / or any other components, or any combination thereof, via a bus 1004. Some UEs may utilize all or a subset of the components shown in FIG. 10. The level of integration between components may vary from one UE to another. Additionally, some UEs may include multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

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

[0124] In this example, the input / output interface 1006 may be configured to provide an interface to an input device, an output device, or one or more input and / or output devices. Examples of output devices include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smart card, another output device, or any combination thereof. An input device may enable a user to capture information to the UE 1000. Examples of input devices include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a webcam, etc.), a microphone, a sensor, a mouse, a trackball, a directional input pad, a trackpad, a scroll wheel, a smart card, etc. A presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. The sensor may be, for example, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, a light sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may have the same type of interface as an input device. - For example, a Universal Serial Bus (USB) port may be used to provide input and output devices.

[0125] According to some embodiments, the power source 1008 is configured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electrical outlet), a photovoltaic device, or a battery, can be used. The power source 1008 may further include a power circuit for delivering power to various parts of the UE 1000 from the power source 1008 itself and / or from an external power source via an interface, such as an input circuit or a power cable. The power transmission may be for charging the power source 1008, for example. The power circuit may perform any formatting, conversion, or other modification of the power from the power source 1008 to make the power suitable for the respective components of the UE 1000 being powered.

[0126] The memory 1010 may be or be configured to include memory such as random access memory (RAM), read only memory (ROM), programmable read only memory (PROM), erasable field programmable gate array read only memory (EPROM), electrically erasable programmable read only memory (EEPROM), magnetic disk, optical disk, hard disk, removable cartridge, flash drive, etc. According to one embodiment, the memory 1010 includes one or more application programs 1014, such as an operating system, a web browser application, a widget, a gadget engine, or other applications, and corresponding data 1016. The memory 1010 may store any of a variety of operating systems or combinations of operating systems for use by the UE 1000.

[0127] The memory 1010 may be configured to include several physical drives, such as a redundant array of independent disks (RAID), flash memory, a USB flash drive, an external hard disk drive, a thumb drive, a pen drive, a key drive, a high density digital versatile disk (HD-DVD) optical disk drive, an internal hard disk drive, a Blu-ray optical disk drive, a holographic digital data storage (HDDS) optical disk drive, an external mini dual in-line memory module (DIMM), a synchronous dynamic random access memory (SDRAM), an external micro-DIMM SDRAM, a smart card memory, such as a tamper-resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), e.g., a USIM and / or an ISIM, other memory, or any combination thereof. The UICC may be, e.g., an embedded UICC (eUICC), an integrated UICC (iUICC), or a removable UICC commonly known as a "SIM card." The memory 1010 may enable the UE 1000 to access, offload data, or upload data, instructions, application programs, and the like stored on a temporary or non-transitory memory medium. An article of manufacture, such as one that utilizes a communications system, may be tangibly embodied as or in memory 1010, which may be or include a device-readable storage medium.

[0128] The processing circuit 1002 may be configured to communicate with an access network or other networks using a communication interface 1012. The communication interface 1012 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 1022. The communication interface 1012 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in the access network). Each transceiver may include a transmitter 1018 and / or a receiver 1020 suitable for providing network communications (e.g., optical, electrical, frequency allocation, etc.). Additionally, the transmitter 1018 and receiver 1020 may be coupled to one or more antennas (e.g., antenna 1022) and may share circuit components, software or firmware or may be implemented separately.

[0129] According to the illustrated embodiment, the communication functions of the communication interface 1012 include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communication such as Bluetooth, contact Communications may include location-based communications, such as using a Global Positioning System (GPS) to determine location, another similar communications function, or any combination thereof. Communications may include IEEE 802.11, Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Nothing The communications protocol may be implemented in accordance with one or more communications protocols and / or standards, such as Universal Mobile Telecommunications (UMTS), WiMax, Ethernet, Transmission Control Protocol / Internet Protocol (TCP / IP), Synchronous Optical Networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), etc.

[0130] Regardless of the type of sensor, the UE can provide data output captured by its sensors to a network node over a wireless connection via its communications interface 1012. Data captured by a sensor in a UE may also be communicated to a network node over a wireless connection via another UE. The output may be periodic (e.g., once every 15 minutes when reporting sensed temperature), random (e.g., over a load from reports from several sensors), in response to a triggering event (e.g., when moisture is detected, an alert is sent), upon request (e.g., a user-initiated request), or in response to a continuous stream (e.g., a live video feed of a patient). to sing ) may also be used.

[0131] As another example, the UE may receive wireless signals from a network node via a wireless connection. input and an actuator, motor, or switch associated with a communications interface configured to receive wireless input. In response to the received wireless input, the actuator, motor, or switch may change state. For example, the UE may include a motor to adjust a control surface or rotor of a drone in flight in accordance with the received input, or a robotic arm to perform a medical procedure in accordance with the received input.

[0132] The UE, when forming an Internet of Things (IoT) device, may be a device for use in one or more application domains, including, but not limited to, urban wearable technology, extended industrial applications, and healthcare. Non-limiting examples of such IoT devices include connected refrigerators or freezers, TVs, connected lighting fixtures, electric meters, robotic vacuum cleaners, voice controlled smartphone speakers, home security cameras, motion detectors, thermostats, smoke detectors, door / window sensors, flood / moisture sensors, electric door locks, connected doorbells, air conditioning systems such as heat exchangers, autonomous vehicles, surveillance systems, weather monitors, vehicle parking monitors, electric vehicle charging stations, smartphone watches, fitness trackers, head mounted displays for augmented reality (AR) or virtual reality (VR), wearables for haptic or sensory augmentation, water sprinklers, motion sensors ... thing or a device mounted on an industrial robot, an unmanned aerial vehicle (UAV), and any type of medical device such as a heart rate monitor or a remote operated surgical robot, etc. A UE in the form of an IoT device comprises circuitry and / or software according to the intended application of the IoT device, in addition to other components as described in connection with the UE 1000 shown in FIG.

[0133] As yet another specific example, in an IoT scenario, a UE may represent a machine or other device that performs monitoring and / or measurements and transmits results of such monitoring and / or measurements to another UE and / or a network node. The UE may be an M2M device, which in this case may be referred to as an MTC device in the 3GPP context. As one particular example, the UE may implement the 3GPP NB-IoT standard. In other scenarios, the UE may represent a vehicle, such as a car, a bus, a truck, a ship, and an aircraft, or other equipment that can monitor and / or report its operating status or other functions related to its operation.

[0134] In fact, any number of UEs may be used together for a single use case. For example, a first UE may be a drone or may be integrated into a drone and may provide drone speed information (obtained via a speed sensor) to a second UE that is a remote controller that operates the drone. When a user makes a change from the remote controller, the first UE may adjust a throttle on the drone (e.g., by controlling an actuator) to increase or decrease the drone's speed. The first and / or second UE may also include two or more of the functions described above. For example, a UE may be equipped with a sensor and an actuator and handle communication of data for both the speed sensor and the actuator.

[0135] 11 illustrates a network node 1100 according to some embodiments. As used herein, a network node refers to a configured, arranged, and / or operative device that can communicate directly or indirectly with UEs and / or other network nodes or devices in a telecommunications network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., wireless access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs), and NR Node Bs (gNBs)).

[0136] Base stations may be classified based on the amount of coverage they provide (or, stated differently, their transmit power levels) and may therefore be referred to as femto, pico, micro, or macro base stations depending on the amount of coverage provided. A base station may be a relay node or a relay donor node that controls a relay. A network node may also include one or more (or all) parts of a distributed radio base station, such as a centralized digital unit and / or a remote radio unit (RRU), sometimes referred to as a remote radio head (RRH). Such remote radio units may or may not be integrated with an antenna as an antenna-integrated radio. Some of the distributed radio base stations may also be referred to as nodes in a distributed antenna system (DAS).

[0137] Other examples of network nodes include a multi-transmission point (multi-TRP) 5G access node, a multi-standard radio (MSR) equipment such as an MSR BS, a network controller such as a radio network controller (RNC) or a base station controller (BSC), a base transceiver station (BTS), a transmission point, a transmitting node, a multi-cell / multicast coordination entity (MCE), an operation and maintenance (O&M) node, an operation support system (OSS) node, a self-organizing network (SON) node, a positioning node (e.g., an evolved serving mobile location center (E-SMLC)), and / or a minimization of drive testing (MDT).

[0138] The network node 1100 includes a processing circuit 1102, a memory 1104, a communication interface 1106, and a power source 1108. The network node 1100 may be comprised of multiple physically separate components (e.g., a Node B component and an RNC component, or a BTS component and a BSC component, etc.), each of which may have its own components. In certain situations where the network node 1100 includes multiple separate components (e.g., a BTS and a BSC component), one or more separate components may be shared among multiple network nodes. For example, a single RNC may control multiple Node Bs. In such a scenario, each unique Node B and RNC pair may possibly be considered as a single individual network node. In some embodiments, the network node 1100 may be configured to support multiple radio access technologies (RATs). According to such an embodiment, some components may be duplicated (e.g., separate memories 1104 for different RATs) and some components may be reused (e.g., the same antenna 1110 may be shared by different RATs). Network node 1100 may also include multiple sets of the various illustrated components for various wireless technologies integrated into network node 1100, e.g., GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, radio frequency identification device (RFID), or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chips or chipsets and other components within network node 1100.

[0139] The processing circuit 1102 may be a microprocessor, a controller, a microcontroller, a central processing unit, a digital signal processor, an application specific integrated circuit, a field programmable gate array, or any other suitable Computing Devices , resource, or a combination of one or more of a combination of hardware, software and / or coded logic, which combination, alone or in conjunction with other network node 1100 components, such as memory 1104, are operable to provide the network node 1100 functionality.

[0140] According to some embodiments, the processing circuit 1102 includes a system on a chip (SOC). According to some embodiments, the processing circuit 1102 includes one or more of a radio frequency (RF) transceiver circuit 1112 and a baseband processing circuit 1114. In some embodiments, the radio frequency (RF) transceiver circuit 1112 and the baseband processing circuit 1114 may be on separate chips (or chipsets), boards, or units, such as a radio unit and a digital unit. In alternative embodiments, some or all of the RF transceiver circuit 1112 and the baseband processing circuit 1114 may be on the same chip or chipset, board, or unit.

[0141] The memory 1104 may comprise any form of volatile or non-volatile computer-readable memory, including, but not limited to, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (e.g., hard disk), removable storage media (e.g., flash drive, compact disk (CD) or digital video disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory device that stores information, data, and / or instructions that may be used by the processing circuit 1102. The memory 1104 may be a P Programs, software EhThe memory 1104 may store any suitable instructions, data, or information, including applications including one or more of the following: code, logic, rules, code, tables, and / or other instructions that may be executed by the processing circuit 1102 and utilized by the network node 1100. The memory 1104 may be used to store any operations performed by the processing circuit 1102 and / or any data received via the communications interface 1106. According to some embodiments, the processing circuit 1102 and the memory 1104 are integrated.

[0142] The communication interface 1106 may be a network node, an access network, and / or UEThe wireless communication interface 1106 may be used for wired or wireless signaling and / or data between the UE and the antenna 1110. As shown, the communication interface 1106 includes a port / terminal 1116 for transmitting and receiving data to and from the network via a wired connection, for example. The communication interface 1106 also includes a wireless front-end circuit 1118 that may be coupled to the antenna 1110, or to a portion thereof according to an embodiment. The wireless front-end circuit 1118 includes a filter 1120 and an amplifier 1122. The wireless front-end circuit 1118 may be connected to the antenna 1110 and the processing circuit 1102. The wireless front-end circuit may be configured to condition signals communicated between the antenna 1110 and the processing circuit 1102. The wireless front-end circuit 1118 may receive digital data that is to be sent to other network nodes or UEs via a wireless connection. The wireless front-end circuit 1118 may convert the digital data into a wireless signal having appropriate channel and bandwidth parameters using a combination of the filter 1120 and / or amplifier 1122. The wireless signal may then be transmitted via the antenna 1110. Similarly, when receiving data, the antenna 1110 may collect wireless signals that are converted to digital data by the wireless front-end circuitry 1118. The digital data may be passed to the processing circuitry 1102. In other embodiments, the communication interface may be between different components and / or Ma Or the components may include different combinations.

[0143] According to certain alternative embodiments, the network node 1100 does not include a separate radio front-end circuit 1118; instead, the processing circuit 1102 includes the radio front-end circuitry and is connected to the antenna 1110. Similarly, according to some embodiments, all or some of the RF transceiver circuitry 1112 is part of the communications interface 1106. According to still other embodiments, the communications interface 1106 may be connected to one or more ports or terminals as part of a radio unit (not shown). child1116, radio front-end circuitry 1118, and RF transceiver circuitry 1112, and the communications interface 1106 communicates with baseband processing circuitry 1114 that is part of a digital unit (not shown).

[0144] The antenna 1110 may include one or more antennas, or an antenna array, configured to transmit and / or receive wireless signals. The antenna 1110 may be coupled to the radio front-end circuitry 1118 and may be any type of antenna capable of wirelessly transmitting and receiving data and / or signals. According to an embodiment, the antenna 1110 is separate from the network node 1100 and connectable to the network node 1100 through an interface or port.

[0145] The antenna 1110, the communication interface 1106, and / or the processing circuit 1102 may be configured to perform any receiving operation and / or any acquisition operation described herein as being performed by a network node. oh The information and / or signals may be received from a UE, another network node, and / or any other network device. Similarly, the antenna 1110, the communication interface 1106, and / or the processing circuit 1102 may be configured to perform any transmission operation described herein as being performed by a network node. oh The and / or the signal may be transmitted to the UE, another network node, and / or any other network device.

[0146] The power source 1108 provides power to the various components of the network node 1100 in a form suitable for each component (e.g., at voltage and current levels required by each component). The power source 1108 may further comprise or be coupled to a power management circuit for supplying the components of the network node 1100 with power to perform the functions described herein. For example, the network node 1100 may be connectable to an external power source (e.g., a power transmission network, an electrical outlet) via an input circuit or interface, such as an electrical cable, whereby the external power source provides power to the power circuit of the power source 1108. As a further example, the power source 1108 may comprise a power source in the form of a battery or battery pack connected to or integrated into the power circuit. In the event of a failure of the external power source, a backup power source may be provided from the battery.

[0147] Embodiments of network node 1100 may include additional components beyond those shown in Figure 11 to provide certain aspects of network node functionality, including any of the functionality described herein and / or any functionality essential to support the subject matter described herein. For example, network node 1100 may include user interface devices that enable input of information into network node 1100 and output of information from network node 1100. This allows a user to perform diagnostics, maintenance, repair, and other management functions of network node 1100.

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

[0149] The host 1200 includes a processing circuit 1202 operably coupled to an input / output interface 1206, a network interface 1208, a power source 1210, and a memory 1212 via a bus 1204. Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as Figures 10 and 11, such that the descriptions are generally applicable to the corresponding components of the host 1200.

[0150] The memory 1212 may include one or more computer programs, including one or more host application programs 1214 and data 1216, which may include user data, e.g., data generated by the UE for the host 1200 or data generated by the host 1200 for the UE. An embodiment of the host 1200 may utilize only a subset or all of the components shown. The host application programs 1214 may be implemented in a container-based architecture, and may be implemented in a number of different classes, types, or implementations of UE (e.g., handsets, desktop computers, web computers, etc.). EhThe host application program 1214 may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for video, audio, and video streaming (VL, MPEG, HDMI ...

[0151] FIG. 13 is a block diagram illustrating a virtualization environment 1300 in which functionality implemented by some embodiments may be virtualized. In this context, virtualization means creating a virtual version of a device or device, including virtualizing a hardware platform, storage, and network resources. As used herein, virtualization may apply to any device described herein, or components thereof, and relates to implementations in which at least a portion of functionality is implemented as one or more virtual components. Some or all of the functionality described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 1300 hosted by one or more of the hardware nodes, such as a network node, a UE, a core network node, or a hardware computing device acting as a host. Furthermore, in embodiments in which the virtual node does not require wireless connectivity (e.g., a core network node or a host), the node may be fully virtualized.

[0152] An application 1302 (which may alternatively be referred to as a software instance, a virtual appliance, a network function, a virtual node, a virtual network function, etc.) executes in the virtualization environment Q400 to implement some of the features, functions, and / or advantages of some of the embodiments disclosed herein.

[0153] The hardware 1304 includes processing circuitry, memory that stores software and / or instructions executable by the hardware processing circuitry, and / or other hardware devices described herein, such as network interfaces, input / output interfaces, etc. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 1306 (also referred to as a hypervisor or virtual machine monitor (VMM)), provide VMs 1308a and 1308b (one or more of which may be generally referred to as VMs 1308), and / or perform any of the functions, features and / or benefits described in connection with some embodiments described herein. The virtualization layer 1306 may present a virtual operating platform to the VMs 1308 that appears to be networking hardware.

[0154] The VMs 1308 may comprise virtual processing, virtual memory, virtual networking or interfaces, and virtual storage, and may be executed by a corresponding virtualization layer 1306. Various embodiments of an instance of a virtual appliance 1302 may be implemented on one or more of the VMs 1308, and such implementations may be done in different ways. Hardware virtualization is done in some contexts called Network Functions Virtualization (NFV). NFV is a technology that allows many network Device It may be used to integrate the types with industry-standard high-volume server hardware, physical switches, and physical storage that can be deployed in a data center, as well as customer premises equipment.

[0155] According to the NFV situation, VM1308 may be a software implementation of a physical machine that executes programs as if they were running on a physical, non-virtualized machine. Each of the VMs 1308, and that portion of the hardware 1304 on which it runs, is hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forming a separate virtual network element. Furthermore, in the context of NFV, a virtual network function runs in one or more VMs 1308 on the hardware 1304 and is responsible for handling a particular network function corresponding to the application 1302.

[0156] The hardware 1304 may be implemented in a standalone network node having generic or concrete components. The hardware 1304 may implement some functions via virtualization. Alternatively, the hardware 1304 may be part of a larger hardware cluster (e.g., in a data center or CPE) where many hardware nodes work together and are managed via a management and orchestration 1310 that oversees, among other things, the lifecycle management of the applications 1302. According to some embodiments, the hardware 1304 is coupled to one or more radio units, each including one or more transmitters and one or more receivers that may be coupled to one or more antennas. The radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with virtual components to provide a virtual node with wireless functionality, such as a wireless access node or base station. According to some embodiments, some signaling may be provided using a control system 1312, which may alternatively be a hardware control system. Eh It can be used for communication between the anode and the radio unit.

[0157] Figure 14 illustrates a communication diagram of a host 1402 communicating via a network node 1404 with a UE 1406 over a partial wireless connection, according to some embodiments. Exemplary embodiments of a UE (such as UE 9012a of Figure 9 and / or UE 1000 of Figure 10), a network node (such as network node 9010a of Figure 9 and / or network node 1100 of Figure 11), and a host (such as host 9016 of Figure 9 and / or host 1200 of Figure 12), according to various embodiments, are described with respect to Figure 14.

[0158] Similar to the host 1200, an embodiment of the host 1402 includes hardware such as communications interfaces, processing circuitry, and memory. The host 1402 also includes software stored on or accessible by the host 1402 and executable by the processing circuitry. This software includes a host application that may be operable to provide services to a remote user, such as a UE 1406 that connects via an over-the-top (OTT) connection 1450 extending between the UE 1406 and the host 1402. In providing services to the remote user, the host application may provide user data that is transmitted using the OTT connection 1450.

[0159] The network node 1404 includes hardware for communicating with the host 1402 and the UE 1406. Eh The connection 1460 may be direct or pass through a core network (such as core network 9006 in FIG. 9) and / or one or more other intermediate networks, such as one or more public, private, or hosted networks. For example, the intermediate network may be a backbone network or the Internet.

[0160] The UE 1406 includes hardware and software that are stored in or accessible by the UE 1406 and executable by the processing circuitry of the UE. The software includes a client application, such as a web browser or an operator-specific "app," that may be operable to provide services to a human or non-human user via the UE 1406 with the support of the host 1402. An executing host application at the host 1402 may communicate with an executing client application via the UE 1406 and an OTT connection 1450 that terminates at the host 1402. In providing services to a user, the client application at the UE may receive request data from the host application at the host and provide user data in response to the request data. The OTT connection 1450 may carry both the request data and the user data. The client application at the UE may interact with the user and generate user data to provide to the host application via the OTT connection 1450.

[0161] The OTT connection 1450 may extend via a connection 1460 between the host 1402 and a network node 1404, and via a wireless connection 1470 between the network node 1404 and the UE 1406 to provide a connection between the host 1402 and the UE 1406. The connections 1460 and wireless connections 1470 over which the OTT connection 1450 may be provided are depicted abstractly to show communication between the host 1402 and the UE 1406 via the network node 1404, and any intermediate devices and the precise routing of messages through these devices are not explicitly mentioned.

[0162] As an example of transmitting data over the OTT connection 1450, in step 1408, the host 1402 provides user data, which may be performed by executing a host application. According to some embodiments, the user data is associated with a particular human user interacting with the UE 1406. According to other embodiments, the user data is associated with a UE 1406 that shares data with the host 1402 without explicit human interaction. In step 1410, the host 1402 initiates a transmission conveying the user data toward the UE 1406. The host 1402 may initiate the transmission in response to a request transmitted by the UE 1406. The request may be triggered by human interaction with the UE 1406 or by the operation of a client application executing on the UE 1406. The transmission may pass through the network node 1404 in accordance with the teachings of the embodiments described throughout this disclosure. Thus, in step 1412, the network node 1404 transmits the user data carried in the transmission initiated by the host 1402 to the UE 1406, in accordance with the teachings of the embodiments described throughout this disclosure. In step 1414, the UE 1406 receives the user data carried in the transmission, which may be executed by a client application executing on the UE 1406 associated with the host application executed by the host 1402.

[0163] In some examples, the UE 1406 executes a client application that provides user data to the host 1402. The user data may be provided in reaction to or in response to data received from the host 1402. Thus, in step 1416, the UE 1406 may provide the user data, which may be executed by executing the client application. In providing the user data, the client application may further take into account user input received from a user via an input / output interface of the UE 1406. Regardless of the specific manner in which the user data was provided, the UE 1406, in step 1418, initiates transmission of the user data to the host 1402 via the network node 1404. In step 1420, in accordance with the teachings of the embodiments described throughout this disclosure, the network node 1404 receives the user data from the UE 1406 and initiates transmission of the received user data to the host 1402. In step 1422, the host 1402 receives the user data carried in a transmission initiated by the UE 1406.

[0164] One or more of the various embodiments improve the performance of the OTT service provided to the UE 1406 using the OTT connection 1450, of which the radio connection 1470 forms the final leg. More precisely, the teachings of these embodiments enable the use of IP-based deterministic networking, where there may be other IP nodes in the system in addition to the 3GPP network, thereby allowing the data loss rate This can provide advantages such as reduced latency, reduced packet delay variation, and bounded latency for real-time applications.

[0165] In an exemplary scenario, factory status information may be collected and analyzed by the host 1402. As another example, the host 1402 may process audio and video data retrieved from UEs for use in creating maps. As another example, the host 1402 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, the host 1402 may store surveillance video uploaded by UEs. As another example, the host 1402 may store or control access to media content, such as video, audio, VR, or AR, that may be broadcast, multicast, or unicast to UEs. As another example, the host 1402 may provide services such as energy pricing, remote control of non-time-critical electrical loads to balance power generation needs, location services, presentation services ( Remote The device may be used to analyze, retrieve, store, analyze, and / or transmit data (e.g., compiling diagrams, etc. from data collected from the device), or for any other function that collects, retrieves, stores, analyzes, and / or transmits data.

[0166] In some examples, measurement procedures may be provided for the purpose of monitoring data rates, latency, and other factors that one or more embodiments improve upon. Additionally, there may be optional network functionality to reconfigure the OTT connection 1450 between the host 1402 and the UE 1406 in response to fluctuations in the measurement results. The measurement procedures and / or network functionality to reconfigure the OTT connection may be implemented in software or hardware in the host 1402 and / or the UE 1406. According to some embodiments, sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 1450 passes, the sensors providing values ​​for the monitored quantities exemplified above, or in response to software updates. Eh by providing values ​​of other physical quantities from which the monitored quantity can be calculated or estimated; Measurement procedureReconfiguration of the OTT connection 1450 may involve message formats, retransmission settings, preferred routing, etc., and the reconfiguration need not directly change the operation of the network node 1404. Such procedures and functionality may be known and practiced in the art. According to certain embodiments, the measurements may involve proprietary UE signaling that facilitates measurements by the host 1402 of throughput, propagation time, latency, etc. The measurements may be software implemented such that messages, particularly empty or "dummy" messages, are sent using the OTT connection 1450 while monitoring propagation times, errors, etc.

[0167] While the computing devices (e.g., UEs, network nodes, hosts) described herein may include the illustrated combination of hardware components, other embodiments may include computing devices having various combinations of components. It should be understood that these computing devices may comprise any suitable combination of hardware and / or software required to perform the tasks, features, functions, and methods disclosed herein. The determining, calculating, obtaining, or similar operations described herein may be performed by a processing circuit that processes information, e.g., by transforming the obtained information to other information, comparing the obtained or transformed information to information stored in the network node, and / or performing one or more operations based on the obtained or transformed information, the processing may make a decision. Furthermore, although components are depicted as a single box located within a larger box or nested within multiple boxes, in reality a computing device may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned among the separate components. For example, a communication interface may be configured to include any of the components described herein, and / or functionality of a component may be partitioned between a processing circuit and a communication interface. In another example, the computationally intensive functions of any of such components may be implemented in software or firmware, and the computationally intensive functions may be implemented in hardware.

[0168] According to certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored in a memory, and according to certain embodiments, a computer program in the form of a non-transitory computer-readable storage medium. productAccording to alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or distinct device-readable storage medium, such as in a hard-wired manner. In any of these particular embodiments, the processing circuitry may be configured to perform the described functionality, regardless of whether or not it executes instructions stored on a non-transitory computer-readable storage medium. Benefits provided by such functionality are not limited to just the processing circuitry, or to other components of the computing device, but are enjoyed by the entire computing device and / or by end users and the wireless network as a whole.

[0169] Routing in a communication network refers to any one of a routing configuration of a communication network, a routing policy of a communication network, and a routing rule of a communication network, and generally refers to any routing information of routing applied to a communication network.

Claims

1. 1. A method performed by a network node of a communication network to enable Internet Protocol (IP) based deterministic networking, comprising: Receiving a configuration request from a deterministic network (DetNet) controller (820); determining (830) whether the configuration request conflicts with routing of the communications network; sending a response to the DetNet Controller indicating an acceptance or rejection of the configuration request in response to determining whether the configuration request conflicts with the routing of the communication network (850); The method according to claim 1,

2. 2. The method of claim 1, wherein the communication network comprises a fifth generation (5G) network; the network node is a DetNet application function; The method, wherein the network node comprises a Core Network (CN) node configured to provide the DetNet application functionality.

3. 10. The method of claim 1 further comprising: determining (810) control and configuration information for the communications network, the control and configuration information including information regarding the routing of the communications network; wherein determining the control and configuration information includes receiving the control and configuration information from at least one of a User Plane Function (UPF), a Session Management Function (SMF), an Access and Mobility Management Function (AMF), and a Policy Control Function (PCF).

4. 4. The method of claim 3, wherein the control and configuration information includes routing information including IP addresses assigned over packet data unit (PDU) sessions in the communications network.

5. 4. The method of claim 3, wherein determining the control and configuration information of the communications network comprises determining multicast distribution rules associated with the communications network, the multicast distribution rules including at least one of information related to supported multicast addresses, flows that are configured for multicast distribution, and a set of outgoing interfaces.

6. 6. The method of claim 5, wherein determining whether the configuration request conflicts with the routing of the communication network comprises determining whether the configuration request complies with the multicast distribution rules.

7. 2. The method of claim 1, wherein determining whether the configuration request conflicts with the routing of the communication network includes comparing an IP address of a DetNet flow with an IP address of a PDU session to determine whether they match.

8. 2. The method of claim 1, wherein determining whether the configuration request conflicts with the routing of the communication network comprises determining that the configuration request conflicts with the routing of the communication network; The method, wherein sending the response to the DetNet controller includes sending a rejection of the configuration request.

9. 2. The method of claim 1, wherein determining whether the configuration request conflicts with the routing of the communications network comprises determining that the configuration request does not conflict with the routing of the communications network; The method, wherein sending the response to the DetNet controller includes sending an acceptance of the configuration request.

10. 2. The method of claim 1, wherein determining whether the configuration request conflicts with the routing of the communications network comprises determining that the configuration request conflicts with the routing of the communications network; The method further comprises: updating (840) the routing of the communication network to avoid the configuration request conflicting with the routing of the communication network; The method, wherein sending the response to the DetNet controller includes sending an acceptance of the configuration request in response to updating the routing of the communication network.

11. 11. The method of claim 10, wherein updating the routing of the communication network comprises: converting configuration information associated with the configuration request into configuration information applicable to the communications network; sending the configuration information applicable to the communication network to at least one of a User Plane Function (UPF), a Session Management Function (SMF), an Access and Mobility Management Function (AMF), and a Policy Control Function (PCF) of the communication network; A method comprising:

12. 10. The method of claim 9 further comprising: receiving, in the communications network, from the DetNet controller, a request to establish a DetNet flow associated with the configuration request (860); the request to establish the DetNet flow including a quality of service (QoS) requirement for the DetNet flow; determining (870) whether the communications network can meet the QoS requirements; responsive to determining that the communications network can meet the QoS requirements, establishing (880) the DetNet flow; The method according to claim 1,

13. 13. The method of claim 12, wherein determining whether the communications network is capable of meeting the QoS requirements comprises: translating the QoS requirements for the DetNet flows into 3rd Generation Partnership Project (3GPP) specific QoS requirements; sending said 3GPP specific QoS requirements to a Policy Control Function (PCF) of said communication network; A method comprising:

14. 10. The method of claim 1 further comprising: receiving (860) a request to establish a Deterministic Network (DetNet) flow in the communication network from a DetNet controller, the request to establish the DetNet flow including a Quality of Service (QoS) requirement for the DetNet flow; determining (870) whether the communications network can meet the QoS requirements; responsive to determining that the communications network can meet the QoS requirements, establishing (880) the DetNet flow; The method according to claim 1,

15. A network node (700) of a communications network for enabling Internet Protocol (IP) based deterministic networking, said network node having a processor (703) and a memory (705), said memory including instructions executable by said processor such that said network node is operable to perform a method according to any one of claims 1 to 14.

16. A computer program comprising program code that is executed by processing circuitry (703) of a network node (700), the execution of said program code causing said network node to perform a method according to any one of claims 1 to 14.

17. A non-transitory storage medium (705) storing a computer program according to claim 16.

18. A non-transitory computer readable medium storing the computer program of claim 16.

Images