OCS (Online Charging System) invalid session cleaning method and system

Abstract

The embodiment of the invention discloses an OCS (Online Charging System) invalid session cleaning method and system. The method comprises the following steps: adding extension parameters in a CCR (Credit Control Request) / SLR (Spending-Limit-Request) message reported by a PCRF (Policy and Charing Rule Function) / PCEF (Policy and Charing Enforcement Function) to the OCS, wherein the extension parameters include a session validity checking identifier, or a session validity checking identifier and a valid session identifier; and cleaning invalid sessions according to the extension parameters afterthe OCS receives the CCR / SLR message. Through adoption of the OCS invalid session cleaning method, the service session consistency between the OCS and the PCEF / PCRF is ensured to the maximum extent;the OCS can clean Gy / Sy invalid sessions on an OCS side; the occupation of OCS side system resources by the invalid sessions is reduced; and the problems of denial of service of the OCS or incapability of accessing new sessions due to release delay of the invalid sessions are solved.

Description

technical field [0001] The present application relates to the technical field of communications, and in particular to a method and system for cleaning up invalid OCS sessions. Background technique [0002] In the existing data service bandwidth control technology, the user's online behavior triggers the PCEF (Policy and Charging Enforcement Function) to report the initial Initial CCR (CCR-I) message to the OCS (Online Charging System, online charging system) , where CCR (Credit Control Request, credit control request) is the charging request message defined in the 3GPP Gy interface agreement; after receiving the Initial CCR message, the OCS creates an online charging session; when the user terminates the Internet access, the PCEF reports to the PCS Terminate CCR (CCR-T, terminating credit control request) message. After receiving the Terminate CCR message, OCS deducts the used service volume and ends the session, and returns Terminate CCA (CCA-T, CCA: Credit Control Answer, ...

AI Technical Summary

Problems solved by technology

When PCEF interrupts the online session without notifying OCS due to some reasons (such as system downtime or interruption of service upgrade, etc.), or directly ends the online session on the local side without notifying OCS due to network timeout, etc., OCS can only reach The relevant resources can be cleaned up and released after the Validity Time, which will lead to the following problems: 1) OCS side resources are insufficient and the service is refused; 2) The overload protection mechanism is triggered, so that new sessions cannot be accessed; 3) The balance reserved for invalid sessions cannot If it is released in time, the newly connected session cannot use this part of the balance, which may lead to problems such as the balance cannot be used or the order of deduction is disordered

When the Sy STR message cannot be reported to the OCS due to various reasons such as system downtime causing PCRF interruption, network interruption or overload flow control, etc., the Sy session created on the OCS side will always be unable to be released, resulting in the following problems: 1) Invalid The memory occupied by the session cannot be released, which may cause resource exhaustion on the OCS side and denial of service

For example, the reserved memory for storing session information on the OCS side is 5G. Under normal circumstances, there are 1 million Sy sessions online, which need to consume 3G of memory.

When the system is down and PCRF is restarted, OCS may create a large number of new Sy sessions in a short period of time, and the created session information may reach 2 million, which requires 6G memory consumption, exceeding the upper limit of OCS reserved memory, resulting in OCS denial of service

2) OCS has overload control and new session requests cannot be accessed

Because there are a large number of invalid sessions, and OCS cannot identify these invalid sessions, new session requests will be restricted and cannot be accessed to protect the normal operation of the system

3) OCS may generate an SNR (Spending-Status-Notification-Request, use status notification request) message returned to PCRF based on the invalid session due to the existence of invalid sessions that have not been cleaned up in time, resulting in wrong sending of invalid SNR messages

[0009] It can be seen that if the PCEF's GyTerminate CCR or the PCRF's Sy STR message fails to be reported to the OCS due to system downtime, interrupted upgrade, or network flash, the invalid session between the OCS side and the PCEF or PCRF will be Cannot be released in time, resulting in OCS denial of service, inability to access new sessions, and return error messages to PCEF / PCRF

Images