Abstract: Systems, methods, and devices can be utilized for policy control function (PCF) fallback during the set up of a session utilizing a 5th Generation (5G) core network. An example method includes receiving, from a session management function (SMF), a request for a policy corresponding to a session. The request includes a first policy identifier corresponding to a first policy control function (PCF). The example method further includes determining that the first PCF is unavailable, generating a modified request by replacing the first policy identifier with a second policy identifier in the request. The second policy identifier corresponds to a second PCF. The example method also includes transmitting, to the second PCF, the modified second request.

Abstract: Systems, methods, and devices can be utilized for policy control function (PCF) fallback during the set up of a session utilizing a 5th Generation (5G) core network. An example method includes receiving, from a session management function (SMF), a request for a policy corresponding to a session. The request includes a first policy identifier corresponding to a first policy control function (PCF). The example method further includes determining that the first PCF is unavailable, generating a modified request by replacing the first policy identifier with a second policy identifier in the request. The second policy identifier corresponds to a second PCF. The example method also includes transmitting, to the second PCF, the modified second request.

Abstract: A telecommunication system can include routing devices, a bearer-management device, and a policy-management device. The bearer-management device can receive a request from a terminal to create a specialized bearer (SB) for a non-audio, non-video media type. The bearer-management device can determine that the request is associated with an authorized user, and then send a setup message comprising a Quality of Service (QoS) indicator to the policy-management device. The policy-management device can create the SB permitting data exchange between the terminal and a routing device. The SB can have QoS characteristics associated with the QoS indicator. In some examples, the terminal can receive a network address, determine an associated network port, and send a SIP INVITE message indicating the non-audio, non-video media type. The terminal can then exchange data on the network port with a peer network terminal.

Abstract: Systems, methods, and devices can be utilized for policy control function (PCF) fallback during the set up of a session utilizing a 5th Generation (5G) core network. An example method includes receiving, from a session management function (SMF), a request for a policy corresponding to a session. The request includes a first policy identifier corresponding to a first policy control function (PCF). The example method further includes determining that the first PCF is unavailable, generating a modified request by replacing the first policy identifier with a second policy identifier in the request. The second policy identifier corresponds to a second PCF. The example method also includes transmitting, to the second PCF, the modified second request.

Abstract: A telecommunication system can include routing devices, a bearer-management device, and a policy-management device. The bearer-management device can receive a request from a terminal to create a specialized bearer (SB) for a non-audio, non-video media type. The bearer-management device can determine that the request is associated with an authorized user, and then send a setup message comprising a Quality of Service (QoS) indicator to the policy-management device. The policy-management device can create the SB permitting data exchange between the terminal and a routing device. The SB can have QoS characteristics associated with the QoS indicator. In some examples, the terminal can receive a network address, determine an associated network port, and send a SIP INVITE message indicating the non-audio, non-video media type. The terminal can then exchange data on the network port with a peer network terminal.

Abstract: A telecommunication system can include routing devices, a Quality of Service (QoS) controller, a policy-management device, and a flow-management device. The QoS controller or flow-management device can receive a request from a terminal to create a specialized flow (SF), e.g., for a non-audio, non-video media type. If the request is associated with an authorized user, a setup message can be sent comprising a QoS indicator. The system can create the SF permitting data exchange between the terminal and a routing device. The SF can have QoS characteristics associated with the QoS indicator. In some examples, the terminal can receive network-address information, determine an associated network resource, and send a flow-request message indicating a non-audio, non-video media type. The terminal can then exchange data on the network port with a peer network terminal.

Abstract: A telecommunication system can include routing devices, a bearer-management device, and a policy-management device. The bearer-management device can receive a request from a terminal to create a specialized bearer (SB) for a non-audio, non-video media type. The bearer-management device can determine that the request is associated with an authorized user, and then send a setup message comprising a Quality of Service (QoS) indicator to the policy-management device. The policy-management device can create the SB permitting data exchange between the terminal and a routing device. The SB can have QoS characteristics associated with the QoS indicator. In some examples, the terminal can receive a network address, determine an associated network port, and send a SIP INVITE message indicating the non-audio, non-video media type. The terminal can then exchange data on the network port with a peer network terminal.

Abstract: A proxy in a service-based telecommunication network, such as a fifth generation (5G) network, can receive a request a from a consumer network function (NF) and route the request to a producer NF. The request can be addressed to the proxy at an Internet Protocol (IP) layer, but include a path header, such as a Hypertext Transfer Protocol Two (HTTP/2) path pseudo-header field, that indicates a type of producer NF and a type of service. The proxy can select a particular instance of that type of producer NF based on the path header and can forward the request to an IP address of the selected producer NF that corresponds to the type of service indicated in the path header.

Abstract: A proxy in a service-based telecommunication network, such as a fifth generation (5G) network, can receive a request a from a consumer network function (NF) and route the request to a producer NF. The request can be addressed to the proxy at an Internet Protocol (IP) layer, but include a path header, such as a Hypertext Transfer Protocol Two (HTTP/2) path pseudo-header field, that indicates a type of producer NF and a type of service. The proxy can select a particular instance of that type of producer NF based on the path header and can forward the request to an IP address of the selected producer NF that corresponds to the type of service indicated in the path header.

Abstract: A telecommunication system can include routing devices, a Quality of Service (QoS) controller, a policy-management device, and a flow-management device. The QoS controller or flow-management device can receive a request from a terminal to create a specialized flow (SF), e.g., for a non-audio, non-video media type. If the request is associated with an authorized user, a setup message can be sent comprising a QoS indicator. The system can create the SF permitting data exchange between the terminal and a routing device. The SF can have QoS characteristics associated with the QoS indicator. In some examples, the terminal can receive network-address information, determine an associated network resource, and send a flow-request message indicating a non-audio, non-video media type. The terminal can then exchange data on the network port with a peer network terminal.

Abstract: A telecommunication system can include routing devices, a bearer-management device, and a policy-management device. The bearer-management device can receive a request from a terminal to create a specialized bearer (SB) for a non-audio, non-video media type. The bearer-management device can determine that the request is associated with an authorized user, and then send a setup message comprising a Quality of Service (QoS) indicator to the policy-management device. The policy-management device can create the SB permitting data exchange between the terminal and a routing device. The SB can have QoS characteristics associated with the QoS indicator. In some examples, the terminal can receive a network address, determine an associated network port, and send a SIP INVITE message indicating the non-audio, non-video media type. The terminal can then exchange data on the network port with a peer network terminal.

Abstract: Aspects of the present disclosure are directed to communication between a policy engine and a charging engine of a wireless communication network. In one example, the charging engine maintains a data store that includes counters and corresponding service identifiers of one or more subscribers of the wireless communication network. In operation, the charging engine receives a status request message from the policy engine, where the status request message is a request for information on a counter associated with a service identifier. The charging engine may determine that the service identifier is not included in the data store and in response thereto generate a default response message that includes nominal data. The charging engine then sends the default response message to the policy engine to enable the policy engine to implement a default policy for allowing a data session between a user device and the wireless communication network.