Abstract: A device may include a processor configured to receive an indication from a subscriber management device that a user equipment (UE) device has attached to a second core network, wherein the device is in a core network associated with a Radio Access Network.

Abstract: A geo-fencing system stores a geo-fence associated with a geographic location of a user equipment device (UE). The geo-fencing system receives, from a Network Exposure Function (NEF) or Service Capability Exposure Function (SCEF) in a mobile network, a monitoring event (MONTE) location report associated with a current location of the UE within the mobile network, and extracts a Radio Access Network (RAN) location from the MONTE location report, where the RAN location identifies a cell, cell sector, eNodeB (eNB), gNodeB (gNB), or tracking area (TA) associated with the current location of the UE. The geo-fencing system determines, based on a comparison of the identified cell, cell sector, eNB, gNB, or TA with the stored geo-fence, whether the UE has entered or exited the geo-fence, and sends, based on the determination, a geo-fence alert to the NEF or SCEF for forwarding to a geo-fencing enabled application.

Abstract: A quality of service traffic steering approach for multi-access edge computing (MEC) environments is disclosed. In an embodiment, a network exposure function (NEF) or similar device (e.g., MEC controller or orchestrator) monitors a quality of service (QoS) of a data session between a user equipment (UE) and an application. The NEF then can determine when the QoS of the data session does not meet a requested service level agreement (SLA). When the SLA is not met, the NEF identifies a MEC host that meets the SLA using a database of MEC applications. Based on the identified MEC host, the NEF re-routes the data session to the MEC host.

Abstract: A system described herein may receive a request for Quality of Service (“QoS”) parameter information associated with a particular User Equipment (“UE”). The system may include an exposure element of a core of a wireless network, such as a Network Exposure Function (“NEF”) or a Service Capability Exposure Function (“SCEF”). The system may indicate, to a user information repository of the wireless network, such as a Unified Data Management function (“UDM”) or a Unified Data Repository (“UDR”), that QoS parameter information associated with the particular UE should be provided. The system may receive, based on the indicating, particular QoS parameter information associated with the particular UE, and may output the received particular QoS parameter information associated with the particular UE in response to the request or may push such information as the QoS parameter information is updated.

Abstract: A system described herein may receive monitoring information associated with a plurality of User Equipment (“UEs”) that receive service via a wireless network. The system may identify, based on the received monitoring information, a particular set of network configuration parameters to implement with respect to service provided to a particular UE, of the plurality of UEs, via the wireless network. The system may provide, to the wireless network, the identified set of network configuration parameters. Providing the identified set of network configuration parameters may include providing an identifier of the particular UE. One or more elements of the wireless network may implement the provided set of network configuration parameters, which may include modifying parameters of the service provided to the particular UE.

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 User Equipment (“UE”) described herein may connect or request connection to a base station of a wireless network. The base station may implement multiple frequency bands, and connecting or requesting connection to the base station may include connecting or requesting connection via a particular frequency band of the multiple frequency bands. The UE may provide an indication of the particular frequency band to a core of the wireless network. The core may select a set of parameters for communications between the UE and the wireless network based on the indication of the particular frequency band. Additionally, or alternatively, the core may provide an indication of the particular frequency band to a device that provides a service to the UE via the wireless network, and the device may select parameters for the service based on the indication of the particular frequency band.

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 quality of service traffic steering approach for multi-access edge computing (MEC) environments is disclosed. In an embodiment, a network exposure function (NEF) or similar device (e.g., MEC controller or orchestrator) monitors a quality of service (QoS) of a data session between a user equipment (UE) and an application. The NEF then can determine when the QoS of the data session does not meet a requested service level agreement (SLA). When the SLA is not met, the NEF identifies a MEC host that meets the SLA using a database of MEC applications. Based on the identified MEC host, the NEF re-routes the data session to the MEC host.

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 system comprises a Network Exposure Function (NEF) and a Session Management Function (SMF). The MF may be configured to: receive, from the NEF, a first request to subscribe to a notification service offered by the SMF; send a create session request to a User Plane Function (UPF); receive a first response from the UPF to the create session request, wherein the first response includes binding information that pertains to an association between a User Equipment device (UE) identifier (ID) and Internet Protocol (IP) addresses; and send, as part of the notification service, a message that includes the binding information to the NEF.

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: Systems and methods provide a Multi-access Edge Computing (MEC) traffic breakout service to access an edge network. A network device receives reachability information for a user equipment (UE) device and sends, in response to receiving the reachability information, a reachability notification to a MEC orchestrator for the edge network. The network device receives, from the MEC orchestrator, a local breakout request that identifies a traffic flow authorized to receive local service from the edge network. The network device generates instructions for a gateway device to apply local breakout service, for the traffic flow, to a local MEC application in the edge network and sends the instructions to an anchoring gateway device for the traffic flow.

Abstract: Described herein are methods for chemical modification of nitrocellulose to generate lyophobic properties which are useful in propellant compositions. Such methods include the steps of: a) dissolving neat nitrocellulose in an organic solvent; b) adding a silyl based isocyanate and a catalyst to the solution; (d) stirring the solution in a moisture free environment; e) hydrolyzing the solution by exposing said solution to moisture; and (e) adding fluorinated oxysilane. The modified nitrocellulose retains its energetic properties while exhibiting high water and organic solvent phobicity, effectively functioning as a barrier to migration or diffusion of liquid components in propellant compositions.

Abstract: A method includes receiving at a network device, an identifier from a vehicle routing device. The vehicle routing device is configured to identify packet data flows based on an application running on a vehicle client device. The packet data flows are flowing over a communication link between the vehicle routing device and the vehicle client device. The method includes identifying each packet of each flow according to the application that sends or receives packets related to each of the packet data flows, determining an extended header for the one or more packet data flows based on an Internet protocol version 6 (IPv6) extension header and a RADIUS vendor specific attributes (VSA) structure, and transmitting, by the vehicle routing device, to the network device, the extended header and the one or more packet data flows.

Abstract: A method includes receiving at a network device, an identifier from a vehicle routing device. The vehicle routing device is configured to identify packet data flows based on an application running on a vehicle client device. The packet data flows are flowing over a communication link between the vehicle routing device and the vehicle client device. The method includes identifying each packet of each flow according to the application that sends or receives packets related to each of the packet data flows, determining an extended header for the one or more packet data flows based on an Internet protocol version 6 (IPv6) extension header and a RADIUS vendor specific attributes (VSA) structure, and transmitting, by the vehicle routing device, to the network device, the extended header and the one or more packet data flows.