Abstract:
In some implementations, a network device (e.g., an Internet protocol multimedia subsystem (IMS) application server (IMS-AS) may receive, via a first communication interface, from a call session control function (CSCF) device, a request to register for an Internet protocol multimedia subsystem (IMS) service. The network device may provide via a second communication interface between the network device and a unified data management (UDM) device, and to the UDM device, a request for IMS service information associated with the IMS service. The network device may receive based on providing the request for IMS service information, via the second communication interface, and from the UDM device, IMS service information. The network device may cause, based on the IMS service information, the IMS service to be provided to a user device associated with the request to register for the IMS service.
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.
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.
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, a network device (e.g., an Internet protocol multimedia subsystem (IMS) application server (IMS-AS) may receive, via a first communication interface, from a call session control function (CSCF) device, a request to register for an Internet protocol multimedia subsystem (IMS) service. The network device may provide via a second communication interface between the network device and a unified data management (UDM) device, and to the UDM device, a request for IMS service information associated with the IMS service. The network device may receive based on providing the request for IMS service information, via the second communication interface, and from the UDM device, IMS service information. The network device may cause, based on the IMS service information, the IMS service to be provided to a user device associated with the request to register for the IMS service.
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.