Session binding method and system

Abstract

The invention provides a session binding method and system and relates to the field of a smart pipeline. The session binding method provided by the invention comprises the steps that after obtaining an AF (Application Function) session establishment request, a capability opening platform generates an Rx session message according to the AF session establishment request and sends the Rx session message to a DRA (Diameter Routing Agent); and the DRA determines a PCEF (Policy and Charging Enforcement Function) identifier according to a user public network IP address in the Rx session message, determines an attribution PCRF ((Policy and Charging Rules Function) identifier of the user according to a user private network IP address and the PCEF identifier, roams the Rx session message to a user attribution DRA according to the attribution PCRF identifier and forwards the Rx session message to an attribution PCRF, thereby finishing session binding. Through application of the method, the DRA determines the attribution PCEF identifier according to the user public network IP address, determines the attribution PCRF identifier according to the user private network IP address and the PCEF identifier and sends the Rx session message to the attribution PCRF, thereby realizing session binding.

Description

technical field [0001] The invention relates to the field of intelligent pipelines, in particular to a session binding method and system. Background technique [0002] In the LBO (Local Breakout, local breakout) scenario, the intelligent pipeline capability opening needs to solve the following problems: [0003] Question 1: Routing addressing, the request message sent by the OTT (Over The Top) application to the smart pipeline capability opening platform generally only contains the user's private network IP address (allocated by the core network) and public network IP address (NAT (Network Address Translation, network address translation) scenario) information, the core network side can only address the visited province according to the user's public network IP address, and cannot solve the problem that the Rx message should be routed to the user's home province PCRF (Policy and ChargingRules Function, policy and charging rule function unit) problem. [0004] Question 2: S...

AI Technical Summary

Problems solved by technology

[0003] Question 1: Routing addressing, the request message sent by the OTT (Over The Top) application to the smart pipeline capability opening platform generally only contains the user's private network IP address (allocated by the core network) and public network IP address (NAT (Network Address Translation, network address translation) scenario) information, the core network side can only address the visited province according to the user's public network IP address, and cannot solve the problem that the Rx message should be routed to the user's home province PCRF (Policy and ChargingRules Function, policy and charging rule function unit)

[0004] Question 2: Session binding, when LTE (Long Term Evolution) users access multiple APNs (Access Point Name, access point), there is an address pool scenario where different APNs have the same private network IP address segment, and different APNs can On different PCEFs, the PCRF of the user's home province cannot complete the Rx / Gx session binding only based on the user's private network IP address information

Images