Patent classifications
H04M15/74
SESSION RECOVERY FROM DEDICATED BEARER FAILURE
Techniques and systems for recovering a communication session from a dedicated bearer failure are disclosed. For example, a P-CSCF node can determine that a dedicated bearer associated with a communication session has failed, and, in response, send a SIP message to a UE associated with the communication session, the SIP message causing the UE to refrain from sending SIP requests using a SIP INVITE method. The process may further include identifying a first network node associated with an identifier of the UE, the first network node comprising one of a PGW or a SMF, and sending an instruction to the first network node to dissociate the dedicated bearer from the communication session. This causes a new attach procedure to be performed by the UE to recover the session without session failure.
CHARGING FUNCTION FALLBACK
Systems, methods, and devices can be utilized to provide charging function (CHF) fallback in a 5.sup.th Generation Core (5GC). An example method is performed by a fail-open function (FOF), and includes receiving, from the CHF, information corresponding to a subscriber of a network. The information is stored in a database. Further, the example method includes receiving, from the CHF or a connected function, a request corresponding to the subscriber. The connected function is a session management function (SMF) and/or a policy control function (PCF). Based on the request, the information stored in the database is at least one of accessed or modified. Based on performing at least one of accessing or modifying the information stored in the database, a response is generated and transmitted to the CHF or the connected function.
Communications method and apparatus
A communications method and apparatus, the method including receiving, by a policy control network element, from a first session management network element, a policy request message, sending, by the policy control network element, to the first session management network element, according to the policy request message, policy information, where the policy information comprises a data network access identifier (DNAI), and establishing, by the first session management network element, according to the DNAI, a first user plane network element for a first protocol data unit (PDU) session for a terminal device.
MULTI-SERVICES APPLICATION GATEWAY AND SYSTEM EMPLOYING THE SAME
An intelligent gateway device provided at a premise (home or business) for providing and managing application services associated with use and support of a plurality of digital endpoint devices associated with the premises. The device includes a communications and processing infrastructure integrated with a peer and presence messaging based communications protocol for enabling communications between the device and an external support network and between the device and connected digital endpoint devices. A services framework at the gateway device implements the communications and processing infrastructure for enabling service management, service configuration, and authentication of user of services at the intelligent gateway. The framework provides a storage and execution environment for supporting and executing received service logic modules relating to use, management, and support of the digital endpoint devices. Thus, the gateway device provides a network-based services point of presence for a plurality of digital endpoint devices at the premises.
ACR buffering in the cloud
A network element of an Internet Protocol multimedia subsystem buffers network resource usage information in the cloud. After generating network resource usage information based on an observation of network resource usage, the network element transmits the network resource usage information to a cloud-based storage service for buffering. Once a network resource usage collection function is available, the network element retrieves the network resource usage information from the cloud-based storage service and transmits it to a charging collection function for generation of call detail records.
Telecommunication network analytics platform
Methods, computer-readable media and devices are disclosed for selecting a plurality of network devices to perform a plurality of tasks in accordance with a set of functional network analytics instructions. For example, a processor deployed in a telecommunication network may receive a set of functional network analytics instructions compiled from a set of instructions in accordance with a functional network analytics platform application programming interface. The processor may further, in accordance with the set of functional network analytics instructions, select a plurality of network devices to perform a plurality of tasks, send the plurality of tasks to the plurality of network devices, receive control plane data from the plurality of network devices, correlate the control plane data in accordance with operations defined in the set of functional network analytics instructions to create resulting data, and forward the resulting data to at least one recipient device.
Session recovery from dedicated bearer failure
Techniques and systems for recovering a communication session from a dedicated bearer failure are disclosed. For example, a P-CSCF node can determine that a dedicated bearer associated with a communication session has failed, and, in response, send a SIP message to a UE associated with the communication session, the SIP message causing the UE to refrain from sending SIP requests using a SIP INVITE method. The process may further include identifying a first network node associated with an identifier of the UE, the first network node comprising one of a PGW or a SMF, and sending an instruction to the first network node to dissociate the dedicated bearer from the communication session. This causes a new attach procedure to be performed by the UE to recover the session without session failure.
METHOD FOR PREHEATING A RESOURCE FILE AND CENTRAL MANAGEMENT SYSTEM
The present disclosure discloses a method for preheating a resource file, and a central management system, and relates to the field of network communication technology. The method includes: according to historical bandwidth data of a target intermediate node, determining a bandwidth off-peak period of the target intermediate node; during the bandwidth off-peak period of the target intermediate node, pre-caching the resource file on an edge node corresponding to the target intermediate node.
REPLAY AGENT FOR DELIVERING CHARGING EVENT MESSAGES FROM A MESSAGE BROKER IN A MOBILE TELECOMMUNICATIONS NETWORK
A system for preserving charging event messages in a mobile telecommunications network when a charging server is unavailable includes a message broker comprising persistent storage. The system also includes a network element that generates a charging event message, attempts to send the charging event message to a charging server, and writes the charging event message to the message broker in response to determining that the attempt to send the charging event message to the charging server has failed. The system also includes a replay agent that subscribes to the message broker for notifications associated with the charging server, receives a notification from the message broker about the charging event message, reads the charging event message from the message broker, and causes the charging event message to be sent to the charging server when the charging server is available.
Distributed backup of unshipped charging data records
A first charging data record (CDR) generating node can receive charging server information and available CDR storage information from a second CDR generating node. The first CDR generating node can detect that the charging server is unavailable to receive CDRs from the first CDR generating node. The first CDR generating node can also determine that a CDR storage area corresponding to the first CDR generating node should not be used to store additional CDRs. The first CDR generating node can also select the second CDR generating node for storing the additional CDRs that are generated by the first CDR generating node. The second CDR generating node can be selected based at least in part on the charging server information and the available CDR storage information. The first CDR generating node can cause at least one CDR to be sent to the second CDR generating node.