H04L41/5019

Technique for Dynamically Classifying and Re-Classifying a Data Packet Flow

A technique for dynamically classifying and re-classifying a data packet flow on a user plane of a core network domain is described. According to an apparatus aspect, a device is provided for dynamically classifying and re-classifying a data packet flow, wherein the device is configured to classify and re-classify the data packet flow using packet detection rules (PDRs) and wherein each PDR is associated with at least one action to be applied to data packets matching the PDR. The device is configured to receive one or more first data packets of a data packet flow, to determine that the received one or more first data packets match a first PDR to classify the data packet flow according to the first PDR, and to trigger application of at least one first action associated with the first PDR to the one or more first packets. The device is further configured to receive one or more second data packets of the data packet flow, wherein the one or more second data packets are received after the one or more first data packets, to determine that the received one or more second data packets match a second PDR to re-classify the data packet flow according to the second PDR, wherein the second PDR is different from the first PDR, and to trigger application of at least one second action associated with the second PDR to the one or more second data packets.

Technique for Dynamically Classifying and Re-Classifying a Data Packet Flow

A technique for dynamically classifying and re-classifying a data packet flow on a user plane of a core network domain is described. According to an apparatus aspect, a device is provided for dynamically classifying and re-classifying a data packet flow, wherein the device is configured to classify and re-classify the data packet flow using packet detection rules (PDRs) and wherein each PDR is associated with at least one action to be applied to data packets matching the PDR. The device is configured to receive one or more first data packets of a data packet flow, to determine that the received one or more first data packets match a first PDR to classify the data packet flow according to the first PDR, and to trigger application of at least one first action associated with the first PDR to the one or more first packets. The device is further configured to receive one or more second data packets of the data packet flow, wherein the one or more second data packets are received after the one or more first data packets, to determine that the received one or more second data packets match a second PDR to re-classify the data packet flow according to the second PDR, wherein the second PDR is different from the first PDR, and to trigger application of at least one second action associated with the second PDR to the one or more second data packets.

SERVICE CHAIN BASED NETWORK SLICING

A processor may identify one or more sources. The processor may identify a respective requirement of each of the one or more sources. The processor may determine if a respective requirement is different than another respective requirement. The processor may locate each of the one or more sources in a respective slice on a different container available in a server of a network.

MULTI-DOMAIN AND MULTI-TENANT NETWORK TOPOLOGY MODEL GENERATION AND DEPLOYMENT
20220385538 · 2022-12-01 · ·

Techniques are described herein for generating network topologies based on models, and deploying the network topologies across hybrid clouds and other computing environments that include multiple workload resource domains. A topology deployment system may receive data representing a logical topology model, and may generate a network topology for deployment based on the logical model. The network topology may include various services and/or other resources provided by different tenants in the computing environment, and tenant may be associated with different set of resources and deployment constraints. The topology deployment system may determine and generate the network topology to use the various resources and comply with various deployment constraints of the different tenants providing the services, and the tenants consuming the network topology.

Determining network flow direction

A computer-implemented system and method identifies a network flow direction. The method includes observing, by a network flow monitor, a plurality of data packets as each data packet travels past a connection point. The method further includes identifying, from the plurality of data packets, a flow session, wherein the flow session comprises a source port, a source device, a destination device, a destination port, and a communication protocol. The method also includes, gathering, from the plurality of data packets, directional metadata. The method includes, comparing the source port and the destination port against a list of common destination ports. The method further includes determining, based on the plurality of data packets, a flow direction of the flow session. The method includes storing the flow session in a database.

METHOD AND APPARATUS FOR ABSTRACTING NETWORK RESOURCES IN A MOBILE COMMUNICATIONS NETWORK
20220376995 · 2022-11-24 ·

A method of abstracting network resources in a mobile communications network includes: determining a service coverage area for a class of service, the class of service defined by service parameters; determining a set of tracking areas that fall at least partly within the service coverage area; selecting available network resources for tracking areas of the set of tracking areas, for providing the class of service in the tracking areas; defining an abstraction view of the selected network resources for the class of service in the service coverage area, the abstraction view having deliverable values of the service parameters within the set of tracking areas; and outputting a communication signal having an indication of the abstraction view.

METHOD AND APPARATUS FOR ABSTRACTING NETWORK RESOURCES IN A MOBILE COMMUNICATIONS NETWORK
20220376995 · 2022-11-24 ·

A method of abstracting network resources in a mobile communications network includes: determining a service coverage area for a class of service, the class of service defined by service parameters; determining a set of tracking areas that fall at least partly within the service coverage area; selecting available network resources for tracking areas of the set of tracking areas, for providing the class of service in the tracking areas; defining an abstraction view of the selected network resources for the class of service in the service coverage area, the abstraction view having deliverable values of the service parameters within the set of tracking areas; and outputting a communication signal having an indication of the abstraction view.

AUTONOMOUS SYSTEM BOTTLENECK DETECTION

In one embodiment, a supervisory service for a network obtains quality of experience metrics for application sessions of an online application. The supervisory service maps the application sessions to paths that traverse a plurality of autonomous systems. The supervisory service identifies, based in part on the quality of experience metrics, a particular autonomous system from the plurality of autonomous systems associated with a decreased quality of experience for the online application. The supervisory service causes application traffic for the online application to avoid the particular autonomous system.

HYPERSCALE CLOUD PROVIDER (HCP) EDGE INTERWORKING WITH MULTIPLE PROTOCOL DATA UNIT (PDU) SESSIONS

A method performed by one or more network devices of a cloud platform for providing interworking between the cloud platform and a communication service platform. The method includes receiving, from a user of the cloud platform, input regarding desired characteristics for an edge cloud, providing, via an application programming interface, an indication of the desired characteristics for the edge cloud to the communication service platform, receiving, from the communication service platform via the application programing interface, an indication of a set of edge locations that is capable of supporting the desired characteristics for the edge cloud, provisioning an edge subnet at each edge location in the set of edge locations, and making the edge subnets visible to the user of the cloud platform.

Technologies for switching network traffic in a data center

Technologies for switching network traffic include a network switch. The network switch includes one or more processors and communication circuitry coupled to the one or more processors. The communication circuitry is capable of switching network traffic of multiple link layer protocols. Additionally, the network switch includes one or more memory devices storing instructions that, when executed, cause the network switch to receive, with the communication circuitry through an optical connection, network traffic to be forwarded, and determine a link layer protocol of the received network traffic. The instructions additionally cause the network switch to forward the network traffic as a function of the determined link layer protocol. Other embodiments are also described and claimed.