Abstract: A first network device may receive, from an application server, a first request for a dedicated bearer session for an application with a quality of service (QoS) and for a notification of an idle session for the application. The first network device may generate, based on the first request, a second request to be notified regarding expiration of an idle session timer for the application, and may provide the second request to a second network device. The first network device may receive, from the second network device and based on the second request, a notification of expiration of the idle session timer for the application, and may provide, to the application server, the notification of expiration of the idle session timer for the application.

Abstract: In some implementations, a network device may receive an identifier associated with an application server. The network device may associate the identifier with a service profile associated with a network slice based on a quality of service associated with the network slice. The network device may provide, to a device associated with the application server, information indicating that the identifier is associated with the service profile. The network device may receive address information associated with the application server. The network device may associate the address information with the service profile. The network device may provide service profile information to a security device included in a core network to cause the security device to forward traffic transmitted by the application server toward a destination via the network slice. The service profile information may include an identifier associated with the service profile, the identifier, and the address information.

Abstract: A device may receive a request from a User Equipment (UE) device to enlist termination information for an application hosted on the UE device when either a Protocol Data Unit (PDU) session or a Packet Data Network (PDN) session is established between the application and a network. In addition, the device may insert the termination information into a routing table on the device in response to receiving the request; receive data originating from the application on the UE device or from an application function (AF) node; translate the received data using the routing table; and forward the translated data to the application on the UE device or to the AF node.

Abstract: A system may receive a request from the UE device to establish a session over a user plane of a network; establish a session over the user plane in response to the request from the UE device; receive, at a first node, uplink IP data from the UE device over the session; redirect the received IP data at the first node to a second node for translating IP data to a T8 message; translate, at the second node, the redirected IP data to a first T8 message; and forward the first T8 message to an application server or an application function (AF) node.

Abstract: Disclosed are systems and methods for an electronic security framework that is configured to detect anomalies, determine (or capture) forensics for those events, and enable mediation to not only address the activity causing the anomaly, but also perform processing steps to prevent the same or similar type of anomaly from occurring again at a later time. In some embodiments, as network requests are received, the disclosed framework can determine the type of activity triggered, whereby the request (e.g., packets) can be subject to a deep inspection, which can trigger the request and/or its associated device being quarantined and/or prevented from operating on the network entirely should a suspect activity that can predicate an anomaly or set of anomalies be detected. The disclosed systems and methods, therefore, provide an advanced, adaptive security backstop for existing networks in order to maintain the integrity of the operations being performed thereon.

Abstract: In some implementations, a network device may receive an identifier associated with an application server. The network device may associate the identifier with a service profile associated with a network slice based on a quality of service associated with the network slice. The network device may provide, to a device associated with the application server, information indicating that the identifier is associated with the service profile. The network device may receive address information associated with the application server. The network device may associate the address information with the service profile. The network device may provide service profile information to a security device included in a core network to cause the security device to forward traffic transmitted by the application server toward a destination via the network slice. The service profile information may include an identifier associated with the service profile, the identifier, and the address information.

Abstract: In some implementations, a network device may receive an identifier associated with an application server. The network device may associate the identifier with a service profile associated with a network slice based on a quality of service associated with the network slice. The network device may provide, to a device associated with the application server, information indicating that the identifier is associated with the service profile. The network device may receive address information associated with the application server. The network device may associate the address information with the service profile. The network device may provide service profile information to a security device included in a core network to cause the security device to forward traffic transmitted by the application server toward a destination via the network slice. The service profile information may include an identifier associated with the service profile, the identifier, and the address information.

Abstract: In some implementations, a network device may receive an identifier associated with an application server. The network device may associate the identifier with a service profile associated with a network slice based on a quality of service associated with the network slice. The network device may provide, to a device associated with the application server, information indicating that the identifier is associated with the service profile. The network device may receive address information associated with the application server. The network device may associate the address information with the service profile. The network device may provide service profile information to a security device included in a core network to cause the security device to forward traffic transmitted by the application server toward a destination via the network slice. The service profile information may include an identifier associated with the service profile, the identifier, and the address information.

Abstract: A user device may be provisioned with a list of paths for connecting to a network. A method may include determining that the user device has attached to a visited network and sending the visited network an indication of connectivity capabilities associated with the network. The method may include receiving an indication of one or more paths established from the visited network to the network based on capabilities of the visited network. The one or more paths may be included in the list of paths. The method may include transmitting data to or from the user device via a first path of the one or more paths.

Abstract: A device, located in a core network associated with a radio access network (RAN), may include a processor configured to expose services or capabilities to application servers outside the core network, wherein the device is located in a core network associated with a radio access network (RAN). The processor may be further configured to receive a subscriber identifier message from a gateway device that established a connection to a user equipment (UE) device via the RAN, wherein the subscriber identifier message includes information identifying the UE device; receive a request from an application server associated with the connection for the information identifying the UE device; and provide the requested information identifying the UE device to the application server, in response to receiving the request from the application server.

Abstract: A device may determine that an application server requires an IPv6 address of a user equipment, and may provide, to another network device, a request for the IPv6 address of the user equipment, wherein the request includes data identifying an IP address of the network device and a port of the network device, and wherein the request is to cause the other network device to provide the request for the IPv6 address to the user equipment via a SMS request message, and receive, from the user equipment, data identifying the IPv6 address and a port of the user equipment via a SMS response message. The network device may receive, from the other network device, a response that includes the data identifying the IPv6 address and the port of the user equipment, and may store the data identifying the IPv6 address and the port of the user equipment.

Abstract: A device may determine that an application server requires an IPv6 address of a user equipment, and may provide, to another network device, a request for the IPv6 address of the user equipment, wherein the request includes data identifying an IP address of the network device and a port of the network device, and wherein the request is to cause the other network device to provide the request for the IPv6 address to the user equipment via a SMS request message, and receive, from the user equipment, data identifying the IPv6 address and a port of the user equipment via a SMS response message. The network device may receive, from the other network device, a response that includes the data identifying the IPv6 address and the port of the user equipment, and may store the data identifying the IPv6 address and the port of the user equipment.

Abstract: A user device may be provisioned with a list of paths for connecting to a network. A method may include determining that the user device has attached to a visited network and sending the visited network an indication of connectivity capabilities associated with the network. The method may include receiving an indication of one or more paths established from the visited network to the network based on capabilities of the visited network. The one or more paths may be included in the list of paths. The method may include transmitting data to or from the user device via a first path of the one or more paths.

Abstract: A user device may be provisioned with a list of paths for connecting to a network. A method may include determining that the user device has attached to a visited network and sending the visited network an indication of connectivity capabilities associated with the network. The method may include receiving an indication of one or more paths established from the visited network to the network based on capabilities of the visited network. The one or more paths may be included in the list of paths. The method may include transmitting data to or from the user device via a first path of the one or more paths.

Abstract: A network device may receive, a flow control request for a first device that is registered for an internet protocol (IP) pinhole service. The flow control request may include a device identifier associated with the first device and a private IP address. The network device may identify at least one of IP address information, port information, and pinhole rules. The network device may provide, to another network device, a flow control response that includes at least one of the IP address information, the port information, and the pinhole rules. The flow control response may cause the other network device to allow traffic flow through the firewall using at least one of the IP address information and the port information. The network device may provide a public IP address and a port identifier to a second device, allowing the second device to provide traffic to the first device.

Abstract: A system may receive a request from the UE device to establish a session overser plane of a network; establish a session over the user plane in response to the request from the UE device; receive, at a first node, uplink IP data from the UE device over the session; redirect the received IP data at the first node to a second node for translating IP data to a T8 message; translate, at the second node, the redirected IP data to a first T8 message; and forward the first T8 message to an application server or an application function (AF) node.

Abstract: A network device may receive, a flow control request for a first device that is registered for an internet protocol (IP) pinhole service. The flow control request may include a device identifier associated with the first device and a private IP address. The network device may identify at least one of IP address information, port information, and pinhole rules. The network device may provide, to another network device, a flow control response that includes at least one of the IP address information, the port information, and the pinhole rules. The flow control response may cause the other network device to allow traffic flow through the firewall using at least one of the IP address information and the port information. The network device may provide a public IP address and a port identifier to a second device, allowing the second device to provide traffic to the first device.

Abstract: A network device may receive, a flow control request for a first device that is registered for an internet protocol (IP) pinhole service. The flow control request may include a device identifier associated with the first device and a private IP address. The network device may identify at least one of IP address information, port information, and pinhole rules. The network device may provide, to another network device, a flow control response that includes at least one of the IP address information, the port information, and the pinhole rules. The flow control response may cause the other network device to allow traffic flow through the firewall using at least one of the IP address information and the port information. The network device may provide a public IP address and a port identifier to a second device, allowing the second device to provide traffic to the first device.

Abstract: A network device may receive, a flow control request for a first device that is registered for an internet protocol (IP) pinhole service. The flow control request may include a device identifier associated with the first device and a private IP address. The network device may identify at least one of IP address information, port information, and pinhole rules. The network device may provide, to another network device, a flow control response that includes at least one of the IP address information, the port information, and the pinhole rules. The flow control response may cause the other network device to allow traffic flow through the firewall using at least one of the IP address information and the port information. The network device may provide a public IP address and a port identifier to a second device, allowing the second device to provide traffic to the first device.

Abstract: A method and apparatus for attenuating jitter in digital signals. A recovered clock is derived from the digital signal and the digital signal is stored in a buffer. The derived clock is input to an input counter which counts a predetermined number of degrees out of phase with an output counter. When the input counter is at a maximum counter value, the output counter value is latched to the address inputs of a ROM look-up table, which outputs a coefficient to a numerically controlled oscillator (NCO). The NCO includes a low frequency portion that adds the coefficient successively to itself and outputs a carry out (CO) signal. A high frequency portion of the NCO receives a high frequency clock and preferably divides down the high frequency clock to a clock frequency which is centered at the desired output frequency. The high frequency portion preferably includes an edge detect circuit that receives the CO signal and adjusts the frequency of the output clock to produce a compensation clock.