Abstract:
A device establishes a quality of service (QoS) framework with a network connected to the device. The device includes a push-to-talk (PTT) application, and the QoS framework assigns priorities to different types of traffic associated with the device. The device utilizes the PTT application to establish a PTT session with another device via the network, and prioritizes, based on the QoS framework, PTT traffic, provided in the PTT session, over best effort traffic during the PTT session with the other device.
Abstract:
In some implementations, an authentication system may receive a user authentication request identifying a primary device. The authentication system may generate a challenge associated with a user profile mapped to the primary device. The authentication system may transmit a challenge message including the challenge. The authentication system may receive a challenge response including a response to the challenge, wherein the response to the challenge includes identification information regarding the user profile. The authentication system may determine a set of primary services associated with the user profile mapped to the primary device and a set of secondary services associated with a set of secondary devices. The authentication system may generate a set of security keys mapped to the set of primary services and the set of secondary services. The authentication system may provision the primary device and the set of secondary devices with the set of security keys.
Abstract:
A device may receive, from a user equipment, a token request associated with an application, wherein the token request is associated with a device identifier. The device may generate a device token for the application and the user equipment. The device may provide, using the device identifier, the device token to the user equipment to enable a user to access the application via an application platform. The device may receive, from the application platform, a slice request for a network slice of a network that is to be used for an application session. The device may determine that the user equipment is associated with the application session based on the device token and the device identifier. The device may configure a network slice instance of the network slice. The device may determine a user equipment route selection policy for the application session according to the network slice instance.
Abstract:
A first device may dynamically switch a proximity detection point from a second device, conducting an on-going call via a device identifier, to the first device. The first device may receive a proximity detection signal or an indication of a loss of a proximity detection signal from the second device, wherein the first device and the second device are associated with the device identifier. The first device may receive, from a network, another indication of the on-going call being conducted by the second device and may provide, to the network, a call origination request to pull the on-going call based on the proximity detection signal or the indication and based on the other indication of the on-going call. The first device may connect with the on-going call based on the call origination request and may conduct the on-going call via the first device rather than the second device.
Abstract:
A network device receives an indication to establish a session for an internet protocol (IP) service between a first device and a second device, wherein the network device is part of a local network with the first device and another network device. The network device identifies a service tag to include in a service tag field of a session request. The other network device causes the session request that includes an updated service tag to be provided to the second device. The second device provides a session response with the service tag to the other network device, the other network device updates the session response to include the original service tag and provides an updated session response to the network device. The network device causes the session to be established.
Abstract:
A device determines whether a PTT application is authenticated to access a first API and a second API, and prevents the PTT application from accessing the first and second APIs when the PTT application is not authenticated. The device permits the PTT application to access the first and second APIs when the PTT application is authenticated, and modifies, via the first API, a timer that dictates when the device checks for traffic received from a network. The device establishes, via the second API, a data connection with the network, and determines, based on the data connection, a QoS framework for the network. The device utilizes the PTT application and the timer to establish a PTT session with another device via the network, and prioritizes, based on the QoS framework, PTT traffic provided in the PTT session with the other device.