Abstract: A device described herein may maintain information associating sets of traffic attributes with respective sets of Quality of Service (“QoS”) parameters, and may receive a request to establish a traffic flow. The request may indicate one or more traffic attributes associated with the requested traffic flow. The device may compare the one or more traffic attributes, included in the request, to the information associating the sets of traffic attributes with the respective sets of QoS parameters, identify a particular set of QoS parameters with which the traffic flow is associated, establish a communication session with a network based on the particular set of QoS parameters, communicate traffic, associated with the traffic flow, with the network via the established communication session. The device may include an application programming interface (“API”) via which an application associated with the traffic flow may specify the traffic attributes in the request.

Abstract: A method, a network device, and a non-transitory computer-readable storage medium are described in relation to an agnostic-based end device management service. The agnostic-based end device management service may include a network-side service that hosts persona information associated with a user and end devices. The persona information may include executable end device applications, end device application data, context information pertaining to the user and the end devices, end device application session data, and business logic. The end devices of the user may not store and execute the end device applications yet have access and use of end device functionality across varying types of end devices. The network-side service may also simulate the executable environment of an end device when providing an application service to the end device. An end device-side service of the end device may render application data and provide sensory data and input data to the network-side service.

Abstract: A system may include one or more devices configured to register a camera device with a core network; assign the camera device to a subscription of a user equipment (UE) device registered with the core network; and assign the camera device to an uplink streaming network slice. The one or more devices may be further configured to assign an uplink streaming video Quality of Service (QOS) class to a data flow sent from the camera device to the core network, wherein the uplink streaming video QoS class guarantees at least one video streaming QoS parameter; and establish the data flow from the camera device to a destination device via the uplink streaming network slice based on the uplink streaming video QoS class.

Abstract: A device may comprise a processor. The processor may be configured to determine, based on secure space information associated with the secure space, whether the device has entered the secure space. If the processor determines that the device has entered the secure space, the processor may disable an ability of the device to communicate wirelessly with networks other than a private network; enable an ability of the device to communicate wirelessly with the private network; connect the device wirelessly to the private network; and run an application hosted on the private network.

Abstract: A device, such as a User Equipment (“UE”), may identify that the device is communicatively coupled to a wireless network via a particular network slice. The particular network slice may be associated with a particular set of Quality of Service (“QoS”) parameters, Service Level Agreements (“SLAs”), or the like. The UE may determine the particular network slice based on a slice identifier provided by a network interface of the device, based on attributes of traffic sent or received via the wireless network, and/or based on attributes of a wireless connection between the device and the wireless network. The device may identify a slice indicator associated with the particular network slice, and may present the slice indicator via a user interface of the device. The presented slice indicator may notify a user of the device that the particular network slice is being used for traffic sent or received via the device.

Abstract: A system comprises a User Equipment device (UE) that includes a processor. The processor may be configured to instantiate a bridge application that includes a container application, wherein the bridge application runs on a container platform on the UE. The bridge application may be configured to: receive application information from a map system on a network slice; display the application information as one or more icons that represent web applications on one or more networks; and when an icon is activated, access a web application among the web applications, wherein the web application corresponds to the icon.

Abstract: A system described herein may maintain information associating one or more tokens to one or more network slices associated with a network. The system may receive a request, from an application executing at a User Equipment (“UE”), for communication session information, where the request includes a particular token. The system may identify a particular network slice associated with the particular token based on the information associating the one or more tokens to the one or more network slices. The system may receive communication session information, associated with the particular network slice, from the network, and may provide the communication session information to the application. The application may use the communication session information to communicate with the network via the particular network slice. The application may use such communication session information without providing an application identifier to the network.

Abstract: A network device may receive, from a user equipment, a dataset identifying: applications utilized by the user equipment, network protocol types associated with the applications, and network addresses associated with the applications. The network device may segregate the dataset based on the network protocol types and to generate a segregated dataset. The network device may determine, based on the segregated dataset, a policy that causes particular application traffic associated with a particular network protocol type to be allocated to a particular network slice of the network. The network device may cause the policy to be provided to the user equipment to cause the user equipment to allocate the particular application traffic associated with the particular network protocol type to the particular network slice of the network.

Abstract: In some implementations, a network device may receive, from a cloud computing service, an indication associating a connection identifier with a network slice identifier. The network device may store the indication. The network device may receive, from a network operator, a request including the connection identifier. Accordingly, the network device may transmit, to the network operator, the network slice identifier in response to the request.

Abstract: Systems and methods described herein enable dynamic in-app subscriptions and controls for network slices. A user device receives a command to launch an application and identifies a preferred network slice for the application. The application determines that a network services subscription for the user device does not include the preferred network slice and obtains consent, from a user of the user device, to add the preferred network slice to the network services subscription. The user device receives, from a provider network, authorization for using the preferred network slice by the application and initiates a network session on the preferred network slice.

Abstract: A system and method disclosed provide a subscription management (SM) platform, associated with a mobile network operator (MNO), that may receive from a first user device, over a second network other than the MNO, a discovery message including the device identifier. The first user device may not include a SIM profile activated to provision the MNO. Methods and systems may send, by the SM platform to the first user device over the second network, a confirmation code request message and receive a confirmation code response message indicative of a request to send a stored confirmation code to a second user device. Methods and systems may receive, by the SM platform over the second network, a confirmation code entered by a user, and send the SIM profile associated with the device ID to activate for provisioning the MNO.

Abstract: Systems and methods described herein use group segmentation of applications (referred to herein as “slicing classes”), based on common service requirements, to allow carriers to assign UE traffic to network slices. A UE stores slicing class definitions for use with UE Route Selection Policies (URSP). Each of the slicing class definitions include network quality of service (QoS) characteristics that are applicable to network traffic for multiple software applications. The UE maps the software applications to corresponding slicing class identifiers associated with the slicing class definitions. The UE also stores URSP rules for associating a slicing class identifier with a network slice identifier. A UE operating system sends, to a modem, one of the slicing class identifiers for an application that is requesting attachment to a wireless network. The modem sends a registration request with a selected network slice identifier based on the received slicing class identifier and the URSP rules.

Abstract: A device described herein may maintain information associating sets of traffic attributes with respective sets of Quality of Service (“QoS”) parameters, and may receive a request to establish a traffic flow. The request may indicate one or more traffic attributes associated with the requested traffic flow. The device may compare the one or more traffic attributes, included in the request, to the information associating the sets of traffic attributes with the respective sets of QoS parameters, identify a particular set of QoS parameters with which the traffic flow is associated, establish a communication session with a network based on the particular set of QoS parameters, communicate traffic, associated with the traffic flow, with the network via the established communication session. The device may include an application programming interface (“API”) via which an application associated with the traffic flow may specify the traffic attributes in the request.

Abstract: A user device may receive information indicating that a universal integrated circuit card has been installed in the user device, where the universal integrated circuit card may store a default table that includes network slice selection assistance information used to route data from the user device to correct slices of a network. The user device may execute an application stored in the user device based on receiving a selection of the application, where execution of the application may cause data to be generated. The user device may identify a slice of the network to which to route the data based on the network slice selection assistance information included in the default table. The user device may cause the data to be routed to the slice of the network identified based on the network slice selection assistance information included in the default table.

Abstract: A system described herein may maintain information associating one or more tokens to one or more network slices associated with a network. The system may receive a request, from an application executing at a User Equipment (“UE”), for communication session information, where the request includes a particular token. The system may identify a particular network slice associated with the particular token based on the information associating the one or more tokens to the one or more network slices. The system may receive communication session information, associated with the particular network slice, from the network, and may provide the communication session information to the application. The application may use the communication session information to communicate with the network via the particular network slice. The application may use such communication session information without providing an application identifier to the network.

Abstract: Systems and methods described herein include receiving an indication that an application on a user device has been launched; determining subscription information associated with the user device or a provider of the application, wherein the subscription information includes an indication of one or more recommended network slices to use for traffic associated with the application; and initiating a data session with the user device for sending and receiving the traffic associated with the application via a recommended network slice of the one or more recommended network slices.

Abstract: A system described herein may provide for multiple levels of authentication, such that a User Equipment (“UE”) may receive secure content from an application server, which may include or may be implemented by a multi-access edge computing (“MEC”) system. As described herein, a user associated with a UE may register the UE and/or a particular application with an authentication system and/or the application server. The registration of the UE and/or the application may establish a “trust” relationship between the authentication system and the UE, such that a user-level authentication performed by the UE, such as biometric authentication, may be accepted by the authentication system and/or the application system as an authentication of the user.

Abstract: A system described herein may provide a technique for applying an authorized set of traffic parameters, such as network slicing parameters, Quality of Service (“QoS”) parameters, etc. to traffic associated with a particular application, without exposing an identifier of the traffic to one or more network devices of a network that handles the traffic. An authentication system of some embodiments may generate a tokenized version of the application. A User Equipment (“UE”) may extract a token from the tokenized application and identify a set of traffic parameters based on then token. The UE may apply the traffic parameters to outbound traffic associated with the application, and the network may determine whether such traffic parameters are authorized for a destination associated with the traffic based on an authorization of the destination for the particular traffic parameters.

Abstract: A system described herein may provide a technique for applying an authorized set of traffic parameters, such as network slicing parameters, Quality of Service (“QoS”) parameters, etc. to traffic associated with a particular application, without exposing an identifier of the traffic to one or more network devices of a network that handles the traffic. An authentication system of some embodiments may generate a tokenized version of the application. A User Equipment (“UE”) may extract a token from the tokenized application and identify a set of traffic parameters based on then token. The UE may apply the traffic parameters to outbound traffic associated with the application, and the network may determine whether such traffic parameters are authorized for a destination associated with the traffic based on an authorization of the destination for the particular traffic parameters.

Abstract: A network device may receive, from a user equipment, a dataset identifying: applications utilized by the user equipment, network protocol types associated with the applications, and network addresses associated with the applications. The network device may segregate the dataset based on the network protocol types and to generate a segregated dataset. The network device may determine, based on the segregated dataset, a policy that causes particular application traffic associated with a particular network protocol type to be allocated to a particular network slice of the network. The network device may cause the policy to be provided to the user equipment to cause the user equipment to allocate the particular application traffic associated with the particular network protocol type to the particular network slice of the network.