WO2010025627A1 - 会话信息的标识方法及装置 - Google Patents

会话信息的标识方法及装置 Download PDF

Info

Publication number
WO2010025627A1
WO2010025627A1 PCT/CN2009/071212 CN2009071212W WO2010025627A1 WO 2010025627 A1 WO2010025627 A1 WO 2010025627A1 CN 2009071212 W CN2009071212 W CN 2009071212W WO 2010025627 A1 WO2010025627 A1 WO 2010025627A1
Authority
WO
WIPO (PCT)
Prior art keywords
session
information
diameter
hpcrf
vpcrf
Prior art date
Application number
PCT/CN2009/071212
Other languages
English (en)
French (fr)
Inventor
周晓云
宗在峰
芮通
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from CN2008102129011A external-priority patent/CN101583112B/zh
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Priority to EP09811002.6A priority Critical patent/EP2323340B1/en
Priority to US13/061,881 priority patent/US20110161504A1/en
Publication of WO2010025627A1 publication Critical patent/WO2010025627A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
    • H04L63/102—Entity profiles
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H04L12/1403—Architecture for metering, charging or billing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/48—Secure or trusted billing, e.g. trusted elements or encryption
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/62—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP based on trigger specification
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/66—Policy and charging system
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/82—Criteria or parameters used for performing billing operations
    • H04M15/8228—Session based
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/01—Details of billing arrangements
    • H04M2215/0156—Secure and trusted billing, e.g. trusted elements, encryption, digital signature, codes or double check mechanisms to secure billing calculation and information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/78—Metric aspects
    • H04M2215/7833—Session based

Definitions

  • the present invention relates to the field of communications, and in particular to a method and apparatus for identifying session information.
  • Evolved Packet System Evolved Packet System
  • E-UTRAN Evolved Universal Terrestrial Radio Access Network
  • the S-GW is an access gateway device connected to the E-UTRAN, configured to forward data between the E-UTRAN and the P-GW, and is responsible for buffering paging waiting data;
  • the P-GW is an EPS and a PDN.
  • Border gateway responsible for PDN access, forwarding data between EPS and PDN.
  • the PCRF accesses the IP (Internet Protocol) service provided by the operator through the R interface to obtain service information.
  • the PCRF is connected to the gateway device in the network through the Gx/Gxa/Gxc interface, and is responsible for initiating the IP address.
  • the establishment of the bearer ensures the QoS (Quality of Service) of the service data and performs charging control.
  • Non-3GPP networks include trusted non-3GPP networks and untrusted non-3GPP networks.
  • the IP access of the trusted non-3GPP network can be directly connected to the P-GW through the S2a; the IP access of the untrusted non-3GPP network needs to be connected to the P-GW through the EPDG (Evolved Packet Data Gateway), ePDG and The interface between the P-GWs is S2b.
  • the PCEF Policy and Charging Enforcement Function
  • the PCRF can complete the control of all functions by connecting to the P-GW.
  • the GW exchanges information through the Gx interface.
  • PMIP Proxy Mobile IP
  • BBERF Bit Binding and Event Report Function
  • S - The information is exchanged between the GW and the PCRF through the Gxc interface.
  • the trusted non-3GPP access gateway also resides in the BBERF, and the trusted non-3GPP network access gateway exchanges information with the PCRF through the Gxa interface.
  • the interface between the home PCRF and the visited PCRF is the S9 interface, and the AF (Application Function) that provides the service for the UE is sent to the PCRF through the Rx interface to generate the PCC ( Policy and Charging Control, policy information.
  • the EPS system supports Multiple PDN access, and the UE can pass multiple P-GWs or one.
  • the P-GW accesses multiple PDNs at the same time, that is, one UE can have multiple IP-CAN (IP-Connectivity Access Network) sessions at the same time.
  • IP-CAN IP-Connectivity Access Network
  • FIG. 1 is a roaming architecture diagram of EPS for home routing according to the prior art.
  • P-GW operates in the home network and is operated by the home network.
  • the provider provides IP services (ie AF home network); the second provides IP services for local grooming and home network operators, and Figure 2 shows EPS for local IP network services provided by local network operators based on existing technologies.
  • Roaming architecture diagram as shown in Figure 2, the P-GW is visiting the network, and the IP service is provided by the home network operator (that is, the AF home network); the third is to provide IP services for the local channel operator and the visited network operator.
  • FIG. 1 is a roaming architecture diagram of EPS for home routing according to the prior art.
  • P-GW operates in the home network and is operated by the home network.
  • the provider provides IP services (ie AF home network); the second provides IP services for local grooming and home network operators, and
  • Figure 2 shows EPS for local IP network services provided by local network operators based on existing technologies.
  • Roaming architecture diagram as
  • FIG. 3 is a roaming architecture diagram of an EPS for providing IP services by a local network operator according to the prior art.
  • the P-GW is visiting the network, and the IP service is provided by the visited network operator. (ie AF is visiting the network).
  • the PCC process is different, and the PCC network element performs different functions.
  • the protocol adopted in the PCC architecture is a Diameter application developed on the basis of the Diameter Base Protocol.
  • the PCC architecture has defined the Diameter application protocol used in non-roaming scenarios. For example, applications applied to the Gx interface are discussed, applications applied to the Rx interface, and application protocols for the Gx interface (including the Gxa and Gxc interfaces).
  • IP-CAN session an IP connection of a UE to a PDN network
  • IP-CAN session may involve multiple network elements.
  • each network element will establish a Diameter session with the PCRF, respectively. Because jt ⁇ an IP-CAN session will work with multiple Diameter Word association, these Diameter sessions are established, maintained and deleted using Diameter ten.
  • the Diameter session includes a Gx session established on the G interface, a Gxx session established on the Gx interface (including Gxa and Gxc), and an Rx session on the Rx interface.
  • the S9 roaming interface mainly includes the following three schemes for implementing the S9 roaming interface: Solution 1: For each IP-CAN session of the UE, the vPCRF terminates between the Gx session, the Gxx session or the R session existing in the visited network, and the vPCRF and the hPCRF pass DRA ( Diameter Routing Agent, Diameter Routing Agent) establishes a new S9 session. That is, an S9 session is used to convey information on Gx sessions, Gxx sessions, and Rx sessions.
  • DRA Diameter Routing Agent, Diameter Routing Agent
  • Solution 2 For each IP-CAN session of the UE, the vPCRF only terminates the Gx session and the Gxx session existing in the visited network, and uses an S9 session to transmit the information on the Gx session and the Gxx session without terminating the visited network. The Rx session simply forwards the message of the Rx session to the hPCRF and the vPCRF as a Proxy.
  • Solution 3 For each UE, the vPCRF terminates the Gx session, Gxx that exists in the visited network for all IP-CAN sessions.
  • the hPCRF Under the roaming architecture of the home route, during the reselection of the BBERF (ie, the user equipment is switched), the hPCRF needs to control two BBERFs at the same time, one called Primary BBERF (the main BBERF) and the other called Non-Primary. BBERF (non-primary BBERF) perpetrates its QoS rules and status for two BBERFs respectively, and operates differently for these two BBERFs. For example: When hPCRF wants to update QoS rules, hPCRF will update QoS rules simultaneously. It is sent to two BBERFs.
  • the Primary BBERF cannot successfully install the QoS rule, it will send the same QoS rule to the hPCRF, and the hPCRF 4 will delete the corresponding QoS rule in the Non-Primary, and delete the corresponding PCC rule in the PCEF. If Non-Primary BBERF cannot successfully install QoS rules. After it is sent to hPCRF, hPCRF only updates the QoS rules and their status saved in Non-Primary BBERF in an hPCRF, and does not perform other operations. Of course, hPCRF is for Primary BBERF and Non-Primary. There are other different operations performed by BBERF, which are not described here.
  • hPCRF Since hPCRF operates differently for Primary BBERF and Non-Primary BBERF, hPCRF is required. Which BBERF information comes from (ie from which place of visit) Gxx session) prevail When sending policies and information to the hPCRF, it is also necessary to inform the vPCRF which policies and information are sent to which Gxx session. Regardless of the above scenario 1 or scenario 2, there is only one S9 session to transmit the visit. In the case of the Gxx session, the hPCRF cannot determine which Gxx session the information in the S9 session is from. Similarly, when the hPCRF sends the policy control information, the vPCRF cannot determine which Gxx session the policy control information is sent to.
  • the hPCRF For the local roaming and AF roaming architecture, if there are multiple AFs providing service information at the same time, the hPCRF also needs to discriminate which AF session the service information comes from, and save the service information provided by each AF for each AF. If the service information provided by an AF is updated, the hPCRF must determine which service information has been updated. For scenario 1, since there is only one S9 session to transmit all Rx sessions of the visited network, the hPCRF cannot determine which Rx session the service information in the S9 session is from.
  • one S9 session is used to transmit information of Gxx or Gx sessions of multiple IP-CAN sessions. For example, if UE ⁇ P accesses two PDNs simultaneously in the way of home routing, there will be two Gxx sessions at the visited location to transmit policy control related information, and one S9 session will simultaneously transmit information of two Gxx sessions. If the UE accesses two PDNs in a local grooming manner, then there will be two Gxs in the visited place that require an S9 session to transmit information.
  • the Gx session and the Gxx session in the visited location require an S9 session to transmit information. Therefore, when there is an S9 session to transmit a UE with multiple Gxx or Gx sessions related to the visited network, the hPCRF cannot determine which Gxx or Gx session the information in the S9 session originated from.
  • a problem that cannot be determined when there are multiple Diameter session information in an S9 session message in the related art has not been proposed yet.
  • the present invention has been made in view of the problem that it is impossible to determine when there are multiple Diameter session information in an S9 session message.
  • the main object of the present invention is to provide an identification scheme of session information to solve the above problem.
  • a subject of session information is provided. Know the method.
  • the method for identifying the session information according to the present invention is applied to a network system including a sender PCRF, a receiver PCRF, a BBERF, a PCEF, and/or an AF.
  • the method includes: the sender PCRF sends an S9 session message to the receiver PCRF.
  • the Diameter session information is transmitted, where the S9 session message carries the identification information that uniquely identifies the Diameter session; the receiving end PCRF determines the Diameter session corresponding to the Diameter session information carried in the S9 session message according to the identification information.
  • an apparatus for identifying session information is also provided.
  • the device for identifying the session information according to the present invention is provided in a network system including a sender PCRF and a receiver PCRF.
  • the device includes: an identifier module, configured to identify a Diameter session, where the Diameter session and the Diameter session carried in the S9 session message And a sending module, configured to send an S9 session message, where the S9 session message carries the identifier information that uniquely identifies the Diameter session; the receiving module is configured to receive the S9 session message; and the determining module is configured to determine the S9 session according to the identifier information The Diameter session corresponding to the Diameter session information carried in the message.
  • the identifier information for identifying the session information is carried in the S9 session, so that the sender PCRF can know which Gxx, Gx or Rx session the session information is from, and when the sender is under the PCRF
  • the policy control information can be sent to the corresponding Gxx session, the Gx session, or the AF session according to the unique identification information carried in the S9 session, and the determination cannot be determined when there are multiple Diameter session information in the S9 session message.
  • the problem is to improve the application flow of the S9 roaming interface in the policy charging control architecture.
  • FIG. 1 is a roaming architecture diagram of an EPS routed for a hometown according to the prior art
  • FIG. 2 is a roaming architecture diagram of an EPS provided by a local network operator according to the prior art and providing IP services by a home network operator
  • 3 is a roaming architecture diagram of an EPS for providing IP services by a local network operator and a visited network operator according to the prior art
  • FIG. 1 is a roaming architecture diagram of an EPS routed for a hometown according to the prior art
  • FIG. 2 is a roaming architecture diagram of an EPS provided by a local network operator according to the prior art and providing IP services by a home network operator
  • 3 is a roaming architecture diagram of an EPS for providing IP services by a local network operator and a visited network operator according to the prior art
  • FIG. 1 is a roaming architecture diagram of an EPS routed for a hometown according to the prior art
  • FIG. 2 is a roaming architecture diagram of an EPS provided by a local network operator according to the prior art and
  • FIG. 4 is a flowchart of a method for identifying session information according to an embodiment of the present invention
  • FIG. 6 is a flowchart of Embodiment 2 of the present invention
  • FIG. 7 is a flowchart according to Embodiment 3 of the present invention
  • FIG. 8 is a fourth embodiment of the present invention.
  • Figure 9 is a flow chart of a fifth embodiment of the present invention
  • Figure 10 is a block diagram of an apparatus for identifying session information according to an embodiment of the present invention.
  • the function of the present invention provides an identification scheme of session information, that is, establishing an S9 session transmission between the vPCRF and the hPCRF, in consideration of the problem that the plurality of Diameter session information cannot be determined in the S9 session message in the related art.
  • a globally unique identifier is used to identify which Gxx, Gx, or R session the information came from; and, in the hPCRF, the vPCRF is delivered through the S9 session.
  • a globally unique identifier is also used to identify which Gxx, Gx, or R session this information is sent to. In this way, the vPCRF can deliver the information to the corresponding Gxx session, Gx session or AF session.
  • a method for identifying session information is provided.
  • the method may be applied to a network including a PCR end of a transmitting end, a PCRF of a receiving end, a BFFF, and/or an AF.
  • the architecture of the network environment is as shown in FIG. 1 to As shown in FIG. 3, FIG. 4 is a flowchart of a method for identifying session information according to an embodiment of the present invention.
  • the method includes the following steps 402 to 404: Step 402: The sending end PCRF sends an S9 session message to the receiving end PCRF to transmit the Diameter session information, where the S9 session message carries the identification information that uniquely identifies the Diameter session.
  • Step 404 The receiving end PCRF determines the S9 session message according to the identification information.
  • the Diameter session corresponding to the Diameter session information carried in the Diameter session.
  • the sender PCRF may be a vPCRF
  • the receiver PCRF may be an hPCRF
  • the sender PCRF may be an hPCRF
  • the receiver PCRF may be a vPCRF.
  • the identifier information carried in the S9 session message is the session identifier of the Diameter session; or the vPCRF is used to assign the identifier information to the Diameter session, where the identifier information uniquely identifies an IP-CAN session in the vPCRF.
  • the Diameter session in the present invention specifically refers to one of the following: a Gx session, a G session, and an Rx session.
  • a Gx session such as Gxx, G, and Rx using an S9 session
  • the sender PCRF when transmitting the unique identification information for identifying the session information in the S9 session, the sender PCRF can know that the session information is from In which Gxx, Gx, or Rx session, and when the sending PCR policy is sent by the sending end, the policy control information can be sent to the corresponding Gxx session, Gx session, or AF according to the unique identification information carried in the S9 session. Conversation.
  • the embodiments of the present invention are separately described below through different EPS roaming architecture scenarios.
  • Embodiment 1 This embodiment describes a procedure for an IP-CAN session establishment in which an UE accesses an EPS through an E-UTRAN or a trusted non-3GPP access gateway in a roaming scenario in which the UE is in the home route.
  • E-UTRAN the S-GW and the P-GW adopt the PMIPv6 ten-party negotiation.
  • the PMIPv6 When accessing through the trusted non-3GPP access gateway, the PMIPv6 is used between the access gateway and the P-GW.
  • the PCRF of the transmitting end is the vPCRF
  • the PCRF of the receiving end is the hPCRF.
  • the method includes the following steps 502 to 520: Step 502: The BBERF receives the establishment of the IP-CAN session request message, and the BBERF obtains the NAI (Network Access Identity) of the UE, and the PDN (Packet Data Network) identifier.
  • the access information of the policy is defined, and the access information includes the network identifier where the BBERF is located, and the current location information of the UE.
  • the BBERF may be located in the S-GW or the trusted non-3GPP access gateway.
  • the BBERF sends a "Gateway Control Session (Gxx Session) Setup indication to the vPCRF, where the message is carried in the "Gateway Control Session Establishment Indication" message.
  • Gxx Session Gxx Session
  • the session identifier 1 is allocated by the BBERF and is used to identify a Diameter session to be established between the BBERF and the vPCRF.
  • the vPCRF determines that the UE uses the home route and the hPCRF supports the Gxx interface according to the PDN identity and the roaming protocol.
  • the vPCRF terminates the Gxx session and initiates a new establishment between the hPCRF and the hPCRF.
  • the VPCRF sends an S9 session establishment indication message to the hPCRF, where the message includes the session identifier 2 (corresponding to step 402) allocated by the vPCRF, and the NAI and PDN identifiers carried in the message "Gateway Control Session Establishment Indication" in step 504.
  • the access information of the policy is established, the reason for the establishment of the S9 session (that is, the gateway control session is established), and the message is carried in the message.
  • There is a session identifier 1 for identifying that the access information carried in the message for formulating the policy is related to the established Gxx session (gateway control session) in step 504;
  • Step 508 the hPCRF identifies the NAI, PDN identifier Interact with the SPR (Subscribe Profile Repository) to obtain the subscription information of the UE, and formulate PCC rules, QoS rules, and event triggers according to the network policy and the reported access information, etc.
  • the hPCRF sends an S9 session establishment confirmation to the vPCRF.
  • vPCRF finds the Gxx session between the corresponding BBERF and the vPCRF according to the received session identifier 1 (corresponding to step 404), and sends a gateway control session establishment confirmation message to the BBERF, where the message carries the confirmation message from the S9 session establishment.
  • the obtained QoS rules and event triggers, BBERF installs QoS rules and event triggers. Among them, vPCRF can only access the visited network.
  • the policy modifies the QoS rules and event triggers sent by the hPCRF, so that the modified QoS rules and event triggers are sent in step 510, and the BBERF is installed.
  • Step 512 The BBERF sends an IP-CAN session request message to the P-GW, where the message carries the information such as the NAI identifier and the PDN identifier of the UE, and the IP-CAN session request message is established as a proxy binding update message. Executing with step 504, there is no need to wait for the message returned in step 510. Step 514, because it is a home route, P-GW is in the home network.
  • the P-GW allocates an IP address to the UE, and the PCEF residing on the P-GW sends an IP-CAN session establishment indication message to the hPCRF, where the message carries the NAI identifier, the IP address, the PDN identifier, and the access information used to formulate the policy.
  • the PCEF is the session identifier 3 assigned to the Gx session to be established; in step 516, the hPCRF associates the message with the message 506 according to the NAI and PDN identifiers, and passes the related PCC rules and event triggers through the IP-CAN.
  • the session establishment confirmation message is sent to the PCEF, and after receiving the confirmation message, the PCEF installs the delivered PCC rule and event trigger and the session identifier 3; and the hPCRF can also modify the access information according to the PCEF provided for formulating the policy.
  • the PCC rules so that the hPCRF issues the modified PCC rules.
  • Step 518 the PCEF returns to the BBERF to establish an IP-CAN session response.
  • the IP-CAN session response is established as a proxy binding update acknowledgement message. The message does not have to wait for the acknowledgment message of step 516; in step 520, the BBERF returns to establish an IP-CAN session response.
  • the vPCRF may assign an identity to the Gxx session established in step 504 instead of using the session identifier 1 assigned by the BBERF to the Gxx session in step 504.
  • this identifier assigned by the vPCRF must ensure that the IP-CAN session for the UE in the vPCRF is globally unique. Once the vPCRF has assigned this flag to Gxx, this flag can be used in the vPCRF, S9 session, and hPCRF to associate to the Gxx session established in step 504.
  • Embodiment 2 This embodiment describes a UE in a home-routed roaming scenario, and the UE passes the E-UTRAN or may Trusting the non-3GPP access gateway, the IP-CAN session tampering process caused by the reselection of the BBERF (ie, the user equipment is switched) after the process of accessing the EPS to establish an IP-CAN session as shown in the first embodiment.
  • the PM-IPv6 protocol is adopted between the S-GW and the P-GW.
  • the access gateway and the P-GW adopt the ⁇ protocol.
  • the PCRF of the transmitting end is a vPCRF
  • the PCRF of the receiving end is an hPCRF.
  • the method includes the following steps 602 to 632: Step 602: New BBERF (New BBERF) receives a gateway control session.
  • the request message, and the New BBERF obtains the identifier NAI of the UE, the PDN identifier, and the access information used to formulate the policy, and the access information includes the network identifier where the BBERF is located, the current location information of the UE, and the like; Step 604, New BBERF to the vPCRF Sending a "Gateway Control Session Establishment Indication" message, the "Gateway Control Session Establishment Indication” message carries the identifier of the UE, the PDN identifier and the session identifier 4, wherein the session identifier 4 is assigned by New BBERF and is used to identify New A Diameter session to be established between BBERF and vPCRF.
  • the Diamter Foundation 10 ensures that the session identifier 4 is globally unique; in step 606, the vPCRF determines the context (Context), the Gxx session, and the corresponding S9 session before the UE handover according to the identity of the UE and the PDN identity.
  • the vPCRF sends an S9 session modification indication message (corresponding to step 402) to the hPCRF, where the message carries the session identifier 2 assigned to the S9 session in the S9 session establishment indication message, and carries the new access information of the UE and the Gxx newly created by the session identifier.
  • Session ID 4 the message also carries the S9 session modification reason, that is, the gateway controls the session establishment; Step 608, the hPCRF searches for the context corresponding to the UE before the handover according to the session identifier 2 of the S9 session, and then according to the UE new connection Incoming information re-establishes PCC rules and QoS rules. At the same time, hPCRF saves a new QoS rule for the Gxx session corresponding to session ID 4. The hPCRF sends an S9 session modification confirmation message to the vPCRF, and the message carries the new QoS rule and the session identifier 4; the hPCRF can generate a new event trigger and send the confirmation message together with the QoS rule through the S9 session.
  • the S9 session modification reason that is, the gateway controls the session establishment
  • Step 608 the hPCRF searches for the context corresponding to the UE before the handover according to the session identifier 2 of the S9 session, and then according to the UE
  • Step 610 The vPCRF finds the corresponding Gxx session according to the session identifier 4 (corresponding to step 404), and sends a gateway control session establishment confirmation message to the New BBERF, and the message carries a new message.
  • the QoS rule where New BBERF updates the QoS rule; if the hPCRF issues a new event trigger, the vPCRF will also be sent to the New BBERF, New BBERF update event trigger.
  • the vPCRF can modify the QoS rules and/or event triggers according to this policy and send them to New BBERF.
  • Step 612 the New BBERF sends an IP-CAN session signaling message to the PCEF, where the message carries the identifier of the UE and the PDN identifier; the message is implemented as a PMIPv6 binding update message;
  • Step 614 the PCEF is based on The identifier of the UE and the PDN identifier are used to find the context (PCC rule, event trigger, and the like) corresponding to the UE before the handover, and send an IP-CAN session modification indication message to the hPCRF, where the message carries the session identifier 3;
  • Step 616 hPCRF
  • the PCC rule re-established in step 504 is found according to the session identifier 3, and is sent to the PCEF through the IP-CAN session tampering confirmation message.
  • the PCEF updates the PCC rules; Step 618, the PCEF returns IP-CAN session signaling to the BBERF.
  • the message is implemented as a binding update confirmation message; Step 620, New BBERF returns a tampering IP-CAN session response message; Step 622, Old BBERF (Old BBERF) receives a Delete Gateway Control Session Request message, carried in the message
  • the identification of the NAI and the PDN of the UE is performed.
  • the Old BBERF searches for the context and the Gxx session corresponding to the UE before the handover according to the identifiers of the UE and the PDN identifier.
  • the Old BBERF sends a gateway control session termination indication message to the vPCRF, where the message carries the termination indication and the session identifier 1;
  • Step 626 the vPCRF finds the corresponding S9 session according to the session identifier, and sends an S9 session modification indication to the hPCRF, where the message carries There is an S9 session identifier 2, which carries the termination indication and the session identifier 1 and the S9 session modification reason (ie, the gateway controls the session termination);
  • Step 628 the hPCRF determines that the Gxx session corresponding to the identifier is deleted according to the session identifier 2, Therefore, the hPCRF also deletes the information on the Gxx session and returns the S9 session modification confirmation.
  • the message carries the session identifier 1; Step 630, the vPCRF finds the corresponding Gx session according to the session identifier 1, and sends a gateway control session termination confirmation to the BBERF; Step 632, the Old BBERF returns to delete the IP-CAN session response. Message. Referring to FIG. 6, it can be concluded that from step 604 to step 630, there are two Gxx sessions at the same time, and the hPCRF confirms the two Gxx sessions by session identifier 1 and session identifier 4, respectively.
  • Old BBERF is used as Primary BBERF and New BBERF is used as Non-Primary BBERF; from step 616 to step 630, Old BBERF is used as Non-Primary BBERF and New BBERF is used as Primary BBERF.
  • the BBERF will update the QoS rules, and the hPCRF will take different actions on the two BBERFs.
  • the UE establishes an IP-CAN session through the E-UTRAN or the trusted non-3GPP access gateway, and accesses the EPS as shown in the first embodiment.
  • the BBERF receives a trigger requesting a new QoS rule and/or a gateway applying a trigger to control the session modification procedure.
  • the PCRF of the transmitting end is the vPCRF
  • the PCRF of the receiving end is the hPCRF.
  • the method includes the following steps 702 to 716: Step 702: The Old BBERF receives the request message, and requests 4 to report a message. The event or request QoS rule or both are available; Step 704: The Old BBERF sends a gateway control and QoS rule request message to the vPCRF, where the message carries new resource request information and/or event report information and is in the gateway control session establishment indication message.
  • the session identifier 1 is assigned; Step 706: After receiving the gateway control and QoS rule request message, the vPCRF searches for the corresponding S9 session according to the session identifier 1, and sends an S9 session modification indication message to the hPCRF (corresponding to step 402), where S9 The session identifier 2 of the session establishment indication message is allocated to the S9 session, and carries the new resource request information and/or event information and the session identifier 1 carried by the gateway control and QoS rule request message; Step 708: The hPCRF searches the context of the Gxx session saved in the hPCRF according to the session identifier 2 and the session identifier 1, including a QoS rule, an event trigger, and the like, and a PCC rule corresponding to the Gxx session.
  • the Old BBERF is a Primary BBERF
  • the hPCRF re-forms the PCC and the QoS rule according to the new resource request information and/or the event report information, and sends the QoS rule to the vPCRF through the S9 session modification confirmation message.
  • the session identifier 1; the hPCRF is also able to update the event trigger and issue it along with the updated QoS rules.
  • the Old BBERF updates the QoS rule and/or the event trigger.
  • the hPCRF initiates an IP-CAN session tampering process.
  • the Old BBERF returns a tampering response message. If, in step 708, hPCRF finds that Old BBERF has become a Non-Primary BBERF, in the S9 session tampering confirmation message, hPCRF will return a rejection message. Similarly, if New BBERF receives the request message, request 4 to report the event or request a new one.
  • the S9 session modification request message of the vPCRF will carry the session identifier 4 and the resource request information and/or the event 4 report information, and the hPCRF judges that the New BBERF is the Primary BBERF, and a new QoS rule and/or a new QoS rule will be formulated.
  • Event trigger The S9 session modification confirmation message carries the session identification 4 and the QoS rules and/or event triggers back to the New BBERF. If hPCRF determines that New BBERF is Non-Primary BBERF, hPCRF will return a reject message.
  • Embodiment 4 This embodiment describes a UE in a home-routed roaming scenario, after the UE establishes an IP-CAN session through an E-UTRAN or a trusted non-3GPP access gateway, as shown in the first embodiment, In the handover procedure shown in the second embodiment, the hPCRF receives a trigger, and requests a gateway control session modification process caused by updating the QoS rules and/or event triggers.
  • the PCRF of the transmitting end is the hPCRF
  • the PCRF of the receiving end is the vPCRF.
  • the method includes the following steps 802 to 812: Step 802, the hPCRF is requested to update the QoS rule and/or the event trigger. And according to the information provided, the PCC rules are formulated, and the QoS rules are respectively determined according to the access information of the two BBERFs; Step 804, the hPCRF needs to provide the QoS rules and/or event triggers to the Old BBERF and the New BBERF at the same time. This embodiment only describes providing QoS rules and/or event triggers to Old BBERF.
  • the hPCRF sends an S9 session rule providing message to the vPCRF (corresponding to step 402), and the message carries the session identifier 2 assigned to the S9 session, and carries the newly formulated QoS rule and the session identifier 1 of the Gxx session corresponding to the Old BBERF; vPCRF finds the corresponding Gxx session according to session ID 1 (equivalent to steps)
  • Step 808 The Old BBERF installs a QoS rule and/or an event trigger.
  • the Old BBERF returns a gateway control and a QoS rule providing an acknowledgement message to the vPCRF, where the message carries the session identifier 1.
  • step 808 the Old BBERF does not install some or all of the QoS rules successfully, the Old BBERF will not install the successful QoS rule and session identifier 1 in the confirmation message; Step 812, the vPCRF returns an S9 session rule confirmation to the hPCRF. Message. hPCRF will complete the remaining IP-CAN session update process. If the QoS rule that is not successfully installed is carried in step 810, the vPCRF sends the QoS rule that has not been successfully installed to the hPCRF together with the session identifier 1. The hPCRF determines that the QoS rules that are not successfully installed are related to the Gxx session of the Old BBERF according to the session identifier 1.
  • the hPCRF 4 deletes the same QoS rule in the New BBERF, and The corresponding PCC rule in the PCEF is deleted. If the hPCRF determines that the Old BBERF is Non-Primary BBERF, the hPCRF simply sets the state of the QoS rule in the save information to "Inactive" without performing other operations. In other embodiments, the hPCRF issues QoS rules and/or event triggers to the New BBERF, and carries the session identification 4 and QoS rules and/or event triggers in step 804. If New BBERF does not have all installed successful QoS rules, then New BBERF ⁇ !
  • the QoS rule that has not been successfully installed is given to the vPCRF, and the vPCRF sends the QoS rule together with the session identifier 4 to the hPCRF.
  • the judgment process of hPCRF is similar.
  • the flow of the PCRF to update the QoS rule and/or the event trigger is similar, and will not be described in detail herein.
  • Embodiment 5 The UE described in this embodiment is locally groomed and the AF is in the roaming scenario of the visited place.
  • the AF establishes the R session. , the process of providing business information.
  • the vPCRF terminates the BBERF Gxx session, the PCEF Gx session, and establishes an S9 session between the vPCRF and the hPCRF.
  • the S9 session will be used to convey information about the Gx session and the Rx session.
  • the PM-IPv6 protocol is adopted between the S-GW and the P-GW.
  • the PMIPv6 is used between the access gateway and the P-GW.
  • the session identifier assigned by the BBERF for the Gxx session is the session identifier 1
  • the session identifier assigned by the PCEF for the Gx session is the session identifier 3.
  • the session identifier assigned by the vPCRF to the S9 session is session identifier 2.
  • the PCRF of the transmitting end is the vPCRF
  • the PCRF of the receiving end is the hPCRF.
  • the method includes the following steps 902 to 910: Step 902: Since the AF is in the visited network, the AF sends the signal to the vPCRF.
  • the application/service information is used to establish an Rx session (AF session) between the AF and the vPCRF.
  • the message carries the service information, the IP address of the UE, the PDN identifier, and the session identifier 5 assigned by the AF to the session.
  • the AF can also be triggered by the event sending event to subscribe the PCRF to the event report when the IP-CAN session changes; Step 904, the vPCRF associates the Rx session with the established IP-CAN session according to the IP address, including the corresponding Gxx session, Gx session and S9 session, and find the corresponding context, save the content of the information.
  • the vPCRF sends an S9 session modification indication message (corresponding to step 402) to the hPCRF, where the message carries the session identifier 2 of the S9 session, the session identifier of the Rx session, the content of the service information, and/or the event trigger.
  • the reason for the S9 session modification may also be carried, that is, "Rx session establishment"; Step 906, hPCRF ⁇ finds the corresponding context according to the session identifier 2, and judges an Rx session establishment according to the session identifier 5 and "Rx session establishment". , save the message in the Rx session related Business information content and/or event triggering.
  • the hPCRF formulates PCC rules and/or event triggers based on service information, user subscription information, and network policies.
  • the hPCRF returns an S9 session modification confirmation message to the vPCRF, where the message carries the session identifier 2 assigned to the S9 session, carries the session identifier 5 of the Rx session, and simultaneously sends the newly formulated PCC rule and/or event trigger to the vPCRF; 908, vPCRF finds the corresponding Rx session according to session identifier 5 (equivalent to steps)
  • the PCC rules and/or event triggers of the IP-CAN session are obtained from the message.
  • the vPCRF returns a response message to the AF, and the message carries the session identifier 5; Step 910, the vPCRF extracts the QoS rule from the PCC rule obtained in step 908, provides a PCC rule and/or event trigger to the PCEF, and provides the QoS rule to the BBERF. / or event trigger, initiate IP-CAN session modification process. It is possible for the vPCRF to modify PCC rules, QoS rules, and/or event triggers according to this policy. If more than one AF provides services to the UE, the other AFs may adopt the same process.
  • Each AF establishes an Rx session and assigns a globally unique session identifier to the Rx session, which can be uniquely used in the S9 session.
  • the service information and/or event trigger provided by the AF is identified, and the PCRF can determine, according to the session identifier, which AF the service information comes from.
  • the AF may change the service information, then the AF will provide the changed service information to the vPCRF by using the established Rx session, and the vPCRF uses the Rx session when providing the changed service information to the hPCRF in the S9 session.
  • the session identifier is identified, so that the hPCRF can determine which AF service information has changed.
  • the AF When the AF decides to end the service, the AF sends a terminating Rx session message to the vPCRF.
  • the vPCRF When the vPCRF provides the final request to the hPCRF in the S9 session, the vPCRF identifies the session identifier of the Rx session, so that the hPCRF can determine which Rx session is terminated and needs to be deleted. Business information, and thus the corresponding operation.
  • the information that the vPCRF identifies an AF in the S9 session may also be allocated by the vPCRF, and the identification information uniquely identifies the IP-CAN session in the vPCRF.
  • the method of the present invention can also be used to solve the problem of using an S9 session transmission.
  • the problem of Gxx or Gx session information of multiple IP-CAN sessions cannot be identified.
  • the general approach is as follows:
  • the UE initially establishes a first IP-CAN session.
  • the BBERF establishes a first Gxx session with the vPCRF (the session identifier is 1 A)
  • the vPCRF establishes an S9 session with the hPCRF
  • the PCEF establishes a first Gx session with the hPCRF, where Gxx
  • the session transmits information through the S9 session, and the first Gxx session information to be transmitted is identified by 1 A in the S9 session.
  • the BBERF establishes a second Gxx session with the vPCRF (the session identifier is 2 A), the PCEF establishes a second Gx session with the hPCRF, and transmits the second Gxx with the previously established S9 session. Session information is identified by 2A. Thereafter, the BBERF receives the request or the event packet changes from the first IP-CAN session, requests a new QoS rule, the BBERF sends the request information to the vPCRF through the first Gxx session, and the vPCRF sends the request information to the hPCRF through the S9 session, the information It is identified by session ID 1A.
  • the hPCRF determines that the information is from the first Gxx session according to the session identifier 1A, finds the corresponding context, formulates a new QoS rule and updates it, and the QoS rule carried in the vPCRF return message is also identified by 1 A, and the vPCRF is The QoS rule is sent to the BBERF through the first Gxx session according to 1 A. It can be used to proactively deliver QoS rules by the PCRF, and terminate the IP-CAN session initiated by BBERF.
  • the UE initially establishes a first IP-CAN session.
  • the BBERF establishes a first Gxx session with the vPCRF (the session identifier is 1A)
  • the PCEF establishes a first Gx session with the vPCRF (the session identifier is IB)
  • the vPCRF and the hPCRF are established.
  • S9 session where the Gx session transmits information through the S9 session, and the first Gx session information to be transmitted is identified by 1B in the S9 session.
  • the BBERF establishes a second Gxx session with the vPCRF (the session identifier is 2 A), and the PCEF establishes a second Gx session with the vPCRF (the session identifier is 2B), and uses the previously established S9.
  • the session transmits the second Gx session information and is identified by 2B.
  • the BBERF receives the request or the event causes the first IP-CAN session to change, requests the new QoS rule, the BBERF sends the request information to the vPCRF through the first Gxx session, the vPCRF terminates the Gxx session, and sends the request information to the hPCRF through the S9 session.
  • This information is obtained from the information of the first Gxx session and is identified by the first Gx session identifier 1B.
  • the hPCRF determines that the information is from the first Gx session according to the session identifier 1B, finds the corresponding context, formulates a new PCC rule and updates it, and the PCC rule carried in the vPCRF return message is also identified by 1B, and the vPCRF is based on the data.
  • 1B sends the PCC rule to the PCEF through the first Gx session, and then formulates the QoS rule according to the PCC rule, passing the first Gxx.
  • the session is sent to BBERF.
  • it can be used for PCRF to actively issue PCC rules, BBERF, PCEF initiated IP-CAN session termination, and the like.
  • An apparatus provides an apparatus for identifying session information, where the apparatus is configured to implement the method for identifying session information, where the apparatus is configured to include a PCRF at a transmitting end and a PCRF at a receiving end.
  • the network system as shown in FIG.
  • the device includes: an identification module 10, a sending module 20, a receiving module 30, and a determining module 40, wherein the identifying module 10 and the sending module 20 are disposed at a transmitting end PCRF, a receiving module 30, and a determining module. 40 is set at the receiving end PCRF.
  • the above-mentioned transmitting end PCRF may be a vPCRF
  • the receiving end PCRF may be an hPCRF
  • the transmitting end PCRF may be an hPCRF
  • the receiving end PCRF may be a vPCRF.
  • the module 10 is used to specify a Diameter session, wherein the Diameter session is related to the Diameter session information carried in the S9 session message, and the sending module 20 is connected to the identifier module 10 for sending the S9 session message.
  • the S9 session message carries the identification information that uniquely identifies the Diameter session.
  • the receiving module 30 is connected to the sending module 20, and is configured to receive the S9 session message.
  • the determining module 40 is connected to the receiving module 30, and is configured to determine S9 according to the identifier information.
  • the Diameter session corresponding to the Diameter session information carried in the session message.
  • the vPCRF when transmitting a Diameter session such as Gxx, Gx, and Rx by using an S9 session, the vPCRF can notify the hPCRF by carrying the unique identification information for identifying the session information in the S9 session.
  • the session information is from which Gxx, Gx, or Rx session, and when the hPCRF sends the policy control information, the vPCRF can send the policy control information to the corresponding Gxx session, Gx according to the unique identification information carried in the S9 session.
  • the session or AF session improves the application flow of the S9 roaming interface in the policy charging control architecture.
  • modules or steps of the present invention can be implemented by a general-purpose computing device, which can be concentrated on a single computing device or distributed over a network composed of multiple computing devices. Alternatively, they may be executed by a computing device
  • the program code is implemented so that they can be stored in the storage device by the computing device, or they can be separately fabricated into individual integrated circuit modules, or a plurality of modules or steps can be made into a single integrated circuit module.
  • the invention is not limited to any specific combination of hardware and software.
  • the above is only the preferred embodiment of the present invention, and is not intended to limit the present invention, and various modifications and changes can be made to the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the scope of the present invention are intended to be included within the scope of the present invention.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Hardware Design (AREA)
  • Computer Security & Cryptography (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Mobile Radio Communication Systems (AREA)

Description

^舌信息的标识方法及装置
技术领域 本发明涉及通信领域，具体而言，涉及一种会话信息的标识方法及装置。 背景技术 3GPP ( 3rd Generation Partnership Project, 第三 4弋合作伙伴计划）的 EPS
( Evolved Packet System, 演进的分组系统 )由 E-UTRAN ( Evolved Universal Terrestrial Radio Access Network , 演进的通用地面无线接入网 ；)、 MME
( Mobility Management Entity, 移动管理单元 ), S-GW ( Serving Gateway, 月良务网关）、 P-GW ( Packet Data Network Gateway, 分组数据网络网关）、 HSS ( Home Subscriber Server, 归属用户服务器）、 3GPP AAA服务器 （ 3GPP认 证 4受权计费月良务器；)、 PCRF ( Policy and Charging Rules Function, 策略和计 费规则功能） 及其他支撑节点组成。 其中， S-GW是与 E-UTRAN相连的接入网关设备， 用于在 E-UTRAN 和 P-GW之间转发数据，并且负责对寻呼等待数据进行緩存； P-GW则是 EPS 与 PDN ( Packet Data Network , 分组数据网络）的边界网关， 负责 PDN的接 入、 在 EPS与 PDN间转发数据等。 一方面， PCRF通过 R 接口与运营商提供的 IP ( Internet Protocol, 互 联网协议）业务连接， 获取业务信息； 另一方面， PCRF通过 Gx/Gxa/Gxc接 口与网络中的网关设备相连， 负责发起 IP承载的建立， 保证业务数据的 QoS ( Quality of Service, 月良务质量）， 并进行计费控制。
EPS支持与非 3GPP 网络的互通， 并通过 S2a/b/c接口实现与非 3GPP 网络的互通。 非 3GPP网络包括可信任非 3GPP网络和不可信任非 3GPP网 络。 可信任非 3GPP网络的 IP接入可直接通过 S2a与 P-GW接口； 不可信任 非 3GPP网络的 IP接入需要经过 ePDG ( Evolved Packet Data Gateway, 演进 的数据网关） 与 P-GW相连， ePDG与 P-GW间的接口为 S2b。 在 EPS之间的 3GPP网络中， PCEF ( Policy and Charging Enforcement Function, 策略和计费执行功能）存在于 P-GW中， PCRF只要与 P-GW连接 即可完成对所有功能的控制， PCRF与 P-GW间通过 Gx接口交换信息。 当 P-GW与 S-GW间的接口基于 PMIP( Proxy Mobile IP, ^弋理移动 IP )时， S-GW 中存在 BBERF ( Bearer Binding and Event Report Function, 载绑定和事件 报告功能）， 并且 S-GW与 PCRF之间通过 Gxc接口交换信息。 当可信任非 3GPP网 妻入时，可信任非 3GPP接入网关中也驻留 BBERF ,可信任非 3GPP 网络接入网关与 PCRF之间通过 Gxa接口交换信息。 UE ( User Equipment, 用户设备 ) 漫游时， 归属地 PCRF和拜访地 PCRF的接口为 S9接口， 同时， 为 UE提供业务的 AF( Application Function,应用功能）通过 Rx接口向 PCRF 发送用于生成 PCC ( Policy and Charging Control, 策略计费控制） 策略的业 务信息。 EPS系统支持 Multiple PDN接入， UE可以通过多个 P-GW或者一个
P-GW 同时接入到多个 PDN , 即一个 UE 可以同时有多个 IP-CAN ( IP-Connectivity Access Network, IP连接接入网） 会话。
EPS存在三种漫游架构， 第一种为家乡路由， 图 1是根据现有技术的为 家乡路由的 EPS的漫游架构图， 如图 1所示， P-GW在家乡网络， 并由家乡 网络运营商提供 IP业务（即 AF在家乡网络）； 第二种为本地疏导并家乡网 络运营商提供 IP业务，图 2是才艮据现有技术的本地疏导且家乡网络运营商提 供 IP业务的 EPS的漫游架构图， 如图 2所示， P-GW在拜访网络， 并由家乡 网络运营商提供 IP业务（即 AF在家乡网络）； 第三种为本地疏导并拜访地 网络运营商提供 IP业务，图 3是才艮据现有技术的本地疏导且拜访地网络运营 商提供 IP业务的 EPS的漫游架构图， 如图 3所示， P-GW在拜访网络， 并由 拜访网络运营商提供 IP业务（即 AF在拜访网络）。 对于不同的漫游场景， PCC的流程不同， PCC网元的执行的功能也不相同。 在目前的技术中， PCC 架构中采用的协议是在 Diameter 基础协议 ( Diameter Base Protocol )基石出上发展的 Diameter应用十办议， 目前 PCC架构 已经定义了在非漫游场景下使用的 Diameter应用协议， 例如， 应用于 Gx接 口的应用十办议， 应用于 Rx接口的应用十办议以及 Gx 接口 （包括 Gxa和 Gxc 接口）的应用协议等。 在这些应用协议中定义了用于 PCC的消息、 命令以及 AVP ( Attribute Value Pairs, 属性值对） 等。 在现有技术中， UE到一个 PDN网络的 IP连接称为一个 IP-CAN会话， 一个 IP-CAN会话会涉及多个网元。 为了获取对这个 IP-CAN会话进行控制 的策略控制规则或者提供用于制定策略控制规则的信息， 各个网元将与 PCRF分别建立 Diameter会话。 因 jt匕一个 IP-CAN会话将与多个 Diameter会 话关联， 这些 Diameter会话都采用 Diameter十办议建立、 维持和删除。 目前， Diameter会话包括 G 接口上建立的 Gx会话， Gx 接口 （包括 Gxa和 Gxc ) 上建立的 Gxx会话和 Rx接口上的 Rx会话。 目前， 主要包括以下三种实现 S9漫游接口的方案： 方案一： 针对 UE的每一个 IP-CAN会话， vPCRF终结在拜访地网络存 在的 Gx会话、 Gxx会话或 R 会话， vPCRF与 hPCRF之间通过 DRA( Diameter Routing Agent, Diameter路由代理）建立新的 S9会话。 也就是说， 采用一个 S9会话来传送 Gx会话、 Gxx会话和 Rx会话上的信息。 方案二： 针对 UE的每一个 IP-CAN会话， vPCRF只终结在拜访地网络 存在的 Gx会话、 Gxx会话， 用一个 S9会话来传送 Gx会话、 Gxx会话上的 信息， 而不终结拜访地网络中的 Rx 会话， 只是将 Rx 会话的消息转发给 hPCRF, 将 vPCRF作为一个^ ^理 ( Proxy )„ 方案三： 针对每一个 UE , vPCRF终结所有 IP-CAN会话在拜访地网络 存在的 Gx会话、 Gxx会话， 用一个 S9会话来传送所有 IP-CAN会话的 Gx 会话、 Gxx会话上的信息， 而不终结所有 IP-CAN会话在拜访地网络中的 Rx 会话，只是将 R 会话的消息转发给 hPCRF ,将 vPCRF作为一个代理（ Proxy )。 上述三种方案存在如下问题：
( 1 ) 在家乡路由的漫游架构下， 在 BBERF发生重选 （即用户设备发 生切换 )期间， hPCRF需要同时控制两个 BBERF ,一个称为 Primary BBERF (主 BBERF ), 另一个称为 Non-Primary BBERF (非主 BBERF )„ hPCRF分 别同时为两个 BBERF分别保存其 QoS规则以及状态， 对这两个 BBERF的 操作也不同。 例如： 当 hPCRF要更新 QoS规则时， hPCRF会将更新的 QoS 规则同时下发给两个 BBERF , 若 Primary BBERF无法成功安装 QoS规则， 它将上 4艮给 hPCRF , hPCRF 4夺删除 Non-Primary中相同的 QoS规则， 并且 删除 PCEF中对应的 PCC规则。 若 Non-Primary BBERF无法成功安装 QoS 规则， 它上 4艮给 hPCRF后， hPCRF只是更新一个 hPCRF中为 Non-Primary BBERF保存的 QoS规则及其状态， 而不进行其他操作。 当然， hPCRF针对 Primary BBERF和 Non-Primary BBERF进行的还有其他不同操作， 这里不再 赘述。由于 hPCRF针对 Primary BBERF和 Non-Primary BBERF的操作不同， 因此 hPCRF就必须区分上艮的信息来自哪个 BBERF (即来自于哪个拜访地 的 Gxx会话 )„ 同时在 hPCRF下发策略和信息时， 也要通知 vPCRF这些策 略和信息是下发给哪个 Gxx会话的。 不管是上述的方案 1还是方案 2, 都只有一个 S9会话来传送拜访地的 Gxx会话， hPCRF无法判断 S9会话中的信息来自于哪个 Gxx会话； 同样， 当 hPCRF下发策略控制信息时， vPCRF也无法判断策略控制信息是下发给 哪个 Gxx会话的。
( 2 )对于本地疏导且 AF在拜访地的漫游架构， 若同时有多个 AF提供 业务信息， 则 hPCRF同样需要判别业务信息来自于哪个 AF会话， 并分别为 各个 AF保存其提供的业务信息。 若某个 AF提供的业务信息发生了更新， 则 hPCRF必须判别哪些业务信息发生了更新。 对于方案 1 来说， 由于只有一个 S9会话来传送拜访地网络所有的 Rx 会话， 则 hPCRF无法判断 S9会话中的业务信息来自于哪个 Rx会话。
( 3 ) 对于方案 3 , 当 UE同时接入多个 PDN时， 一个 S9会话用来传 送多个 IP-CAN会话的 Gxx或 Gx会话的信息。 例如， 若 UE啫 P以家乡路由 的方式同时接入两个 PDN,那么在拜访地将有两个 Gxx会话来传送策略控制 相关的信息， 一个 S9会话就要同时传送两个 Gxx会话的信息。 若 UE都以 本地疏导的方式接入两个 PDN, 那么在拜访地将有两个 Gx需要一个 S9会 话来传送信息。 若 UE以家乡路由的方式接入一个 PDN, 以本地疏导的方式 接入第二个 PDN, 那么在拜访地有 Gx会话和 Gxx会话需要一个 S9会话传 送信息。 因此， 当有一个 S9会话来传送一个 UE在拜访地网络相关的多个 Gxx或 Gx会话时， hPCRF无法判断 S9会话中的信息来自于哪个 Gxx或 Gx 会话。 针对相关技术中 S9会话消息中存在多个 Diameter会话信息时无法判断 的问题， 目前尚未提出有效的解决方案。 发明内容 针对 S9会话消息中存在多个 Diameter会话信息时无法判断的问题而提 出本发明， 为此， 本发明的主要目的在于提供一种会话信息的标识方案， 以 解决上述问题。 为了实现上述目的， 才艮据本发明的一个方面， 提供了一种会话信息的标 识方法。 才艮据本发明的会话信息的标识方法， 应用于包括发送端 PCRF、 接收端 PCRF、 BBERF、 PCEF和 /或 AF的网络系统， 该方法包括： 发送端 PCRF向 接收端 PCRF发送 S9会话消息以传送 Diameter会话信息， 其中， S9会话消 息中携带有唯一标识 Diameter会话的标识信息；接收端 PCRF才艮据标识信息， 确定 S9会话消息中携带的 Diameter会话信息对应的 Diameter会话。 为了实现上述目的， 才艮据本发明的另一方面， 还提供了一种会话信息的 标识装置。 根据本发明的会话信息的标识装置，设置于包括发送端 PCRF和接收端 PCRF的网络系统， 该装置包括： 标识模块， 用于标识 Diameter会话， 其中， Diameter会话与 S9会话消息中携带的 Diameter会话信息相关； 发送模块， 用于发送 S9会话消息， 其中， S9会话消息中携带有唯一标识 Diameter会话 的标识信息； 接收模块， 用于接收 S9 会话消息； 确定模块， 用于根据标识 信息确定 S9会话消息中携带的 Diameter会话信息对应的 Diameter会话。 通过本发明的上述技术方案， 在使用 S9会话传送关于 Gxx、 Gx 以及
Rx等 Diameter会话时， 通过在 S9会话中携带唯一的用于标识会话信息的标 识信息， 使得发送端 PCRF 能够得知该会话信息是来自于哪个 Gxx、 Gx或 Rx会话， 并且当发送端 PCRF下发策略控制信息时， 能够根据 S9会话中携 带的唯一的标识信息将策略控制信息下发到相应的 Gxx会话、 Gx会话或者 AF会话，解决了 S9会话消息中存在多个 Diameter会话信息时无法判断的问 题， 进而完善了策略计费控制架构中实现 S9漫游接口的应用流程。 附图说明 此处所说明的附图用来提供对本发明的进一步理解，构成本申请的一部 分， 本发明的示意性实施例及其说明用于解释本发明， 并不构成对本发明的 不当限定。 在附图中： 图 1是根据现有技术的为家乡路由的 EPS的漫游架构图； 图 2是才艮据现有技术的本地疏导且家乡网络运营商提供 IP业务的 EPS 的漫游架构图； 图 3 是根据现有技术的本地疏导且拜访地网络运营商提供 IP 业务的 EPS的漫游架构图； 图 4是根据本发明实施例的会话信息的标识方法的流程图； 图 5是才艮据本发明实施例一的流程图； 图 6是才艮据本发明实施例二的流程图； 图 7是才艮据本发明实施例三的流程图； 图 8是才艮据本发明实施例四的流程图； 图 9是才艮据本发明实施例五的流程图； 图 10是才艮据本发明实施例的会话信息的标识装置的框图。 具体实施方式 以下结合附图对本发明的优选实施例进行说明， 应当理解， 此处所描述 的优选实施例仅用于说明和解释本发明， 并不用于限定本发明。 需要说明的 是，在不沖突的情况下，本申请中的实施例及实施例中的特征可以相互组合。 功能相克述 考虑到相关技术中 S9会话消息中存在多个 Diameter会话信息时无法判 断的问题， 本发明实施例提供了一种会话信息的标识方案， 即， 在 vPCRF 与 hPCRF之间建立 S9会话传送 Gxx会话、 Gx会话以及 Rx会话（或仅传送 Gxx 会话、 Gx 会话） 的信息时， 使用全局唯一的标识来标识信息来自哪个 Gxx、 Gx或 R 会话； 并且， 在 hPCRF通过 S9会话向 vPCRF下发信息时， 也使用全局唯一的标识来标识这些信息发送给到哪个 Gxx、 Gx或 R 会话。 这样， vPCRF能够将信息下发到相应的 Gxx会话、 Gx会话或者 AF会话。 方法实施例
^^据本发明实施例， 提供了一种会话信息的标识方法， 该方法可以应用 于包括发送端 PCRF、 接收端 PCRF、 BBERF、 和 /或 AF的网络， 该网络环 境的架构如图 1至图 3所示， 图 4是根据本发明实施例的会话信息的标识方 法的流程图， 如图 4所示， 该方法包括如下的步骤 402至步骤 404: 步骤 402 , 发送端 PCRF 向接收端 PCRF 发送 S9 会话消息以传送 Diameter会话信息， 其中， S9会话消息中携带有唯一标识 Diameter会话的 标识信息； 步骤 404 , 接收端 PCRF 根据标识信息， 确定 S9 会话消息中携带的 Diameter会话信息对应的 Diameter会话。 优选地， 发送端 PCRF可以为 vPCRF、 接收端 PCRF可以为 hPCRF; 或者优选地， 发送端 PCRF可以为 hPCRF、 接收端 PCRF可以为 vPCRF。 其中，上述 S9会话消息携带的标识信息采用 Diameter会话的会话标识； 或者 vPCRF为 Diameter会话分配标识信息， 其中， 该标识信息在 vPCRF中 唯一标识一个 IP-CAN会话。 本发明中的 Diameter会话特指以下之一： Gx 会话、 G 会话、 Rx会 话。 通过上述实施例，在使用 S9会话传送关于 Gxx、 G 以及 Rx等 Diameter 会话时， 通过在 S9会话中携带唯一的用于标识会话信息的标识信息， 使得 发送端 PCRF能够得知该会话信息是来自于哪个 Gxx、 Gx或 Rx会话， 并且 当发送端 PCRF下发策略控制信息时， 能够才艮据 S9会话中携带的唯一的标 识信息将策略控制信息下发到相应的 Gxx会话、 Gx会话或者 AF会话。 下面通过不同的 EPS漫游架构场景分别描述本发明实施例。 需要说明的是，在以下附图的流程图示出的步骤可以在诸如一组计算机 可执行指令的计算机系统中执行， 并且， 虽然在流程图中示出了逻辑顺序， 但是在某些情况下， 可以以不同于此处的顺序执行所示出或描述的步骤。 实施例一 本实施例描述 UE在家乡路由的漫游场景下， UE通过 E-UTRAN或可 信任非 3GPP接入网关， 接入 EPS的 IP-CAN会话建立的流程。 其中， 通过 E-UTRAN接入时， S-GW与 P-GW之间采用 PMIPv6十办议， 通过可信任非 3GPP接入网关接入时， 接入网关与 P-GW之间采用 PMIPv6十办议。 在本实施例中， 发送端 PCRF为 vPCRF、 接收端 PCRF为 hPCRF , 如 图 5所示， 该方法包括如下的步骤 502至步骤 520: 步骤 502 , BBERF接收到建立 IP-CAN会话请求消息， 并且 BBERF获 得了 UE的标 i只 NAI ( Network Access Identity, 网络接入标 i只 ), PDN ( Packet Data Network, 分组数据网） 标识、 用于制定策略的接入信息， 接入信息包 括 BBERF所在的网络标识， UE当前的位置信息等。 其中， BBERF可以位 于 S-GW或可信任非 3GPP接入网关； 步骤 504, BBERF向 vPCRF发送 "网关控制会话 （ Gxx会话 ) 建立指 示，' 消息， 其中， "网关控制会话建立指示" 消息中携带有 UE的标识 NAI、 PDN标识、 用于制定策略的接入信息和会话标识 1 , 其中， 会话标识 1是由 BBERF分配的，用于标识 BBERF与 vPCRF之间的将要建立 Diameter会话。 Diameter基础协议确保该会话标识 1为全局唯一； 步骤 506, vPCRF才艮据 PDN标识以及漫游协议判断 UE采用了家乡路 由并且 hPCRF支持 Gxx接口的功能。 vPCRF终结 Gxx会话， 并发起建立与 hPCRF之间的新的 Diameter会话。 vPCRF向 hPCRF发送 S9会话建立指示 消息， 消息中包括由 vPCRF分配的会话标识 2 (相当于步骤 402 )、 步骤 504 "网关控制会话建立指示" 消息中携带的 NAI、 PDN标识、 用于制定策略的 接入信息、 S9会话建立的原因 （即网关控制会话建立）， 并且， 该消息中还 携带有会话标识 1 , 其用于标识消息中携带的用于制定策略的接入信息是与 步骤 504中的建立的 Gxx会话 (网关控制会话）有关的； 步骤 508 , hPCRF才艮据 NAI、 PDN标识与 SPR ( Subscription Profile Repository, 用户签约文档库） 交互， 获取 UE的签约信息， 并根据网络策略 以及上报的接入信息等制定 PCC规则、 QoS规则和事件触发器。 hPCRF向 vPCRF发送 S9会话建立确认消息，该消息中携带有标识 S9会话的会话标识 2, QoS规则、 事件触发器和会话标识 1 , 其中， 会话标识 1 用于标识 QoS 规则和事件触发器是与 Gxx会话相关的； 步骤 510, vPCRF才艮据收到的会话标识 1查找到对应的 BBERF与 vPCRF 之间的 Gxx会话（相当于步骤 404 ), 向 BBERF发送网关控制会话建立确认 消息， 消息中携带有从 S9会话建立确认消息中得到的 QoS规则和事件触发 器， BBERF安装 QoS规则和事件触发器。 其中， vPCRF能够才艮据拜访地网络的策略对 hPCRF下发的 QoS规则和 事件触发器进行修改， 从而步骤 510下发修改过的 QoS规则和事件触发器， BBERF进行安装。 步骤 512, BBERF向 P-GW发送建立 IP-CAN会话请求消息， 消息中 携带 UE的 NAI标识， PDN标识等信息， 建立 IP-CAN会话请求消息在实现 时为代理绑定更新消息； 步骤 510可以与步骤 504同时执行， 不必等待步骤 510返回的消息。 步骤 514, 由于是家乡路由， P-GW在家乡网络。 P-GW为 UE分配 IP 地址， 驻留于 P-GW的 PCEF向 hPCRF发送 IP-CAN会话建立指示消息， 消 息中携带 UE的 NAI标识、 IP地址、 PDN标识和用于制定策略的接入信息 和 PCEF为要建立的 Gx会话分配的会话标识 3等； 步骤 516, hPCRF才艮据 NAI和 PDN标识将该消息与 506的消息进行关 联， 并将相关的 PCC规则和事件触发器通过 IP-CAN会话建立确认消息发送 给 PCEF , PCEF接收到确认消息后， 安装下发的 PCC规则和事件触发器以 及会话标识 3; 并且， hPCRF还可以根据 PCEF提供的用于制定策略的接入信息修改 前面制定 PCC规则， 从而 hPCRF下发修改过的 PCC规则。 步骤 518 , PCEF向 BBERF返回建立 IP-CAN会话应答。 在实现时， 建 立 IP-CAN会话应答为代理绑定更新确认消息。 该消息不必等待步骤 516的 确认消息； 步骤 520, BBERF返回建立 IP-CAN会话应答。 在其他实施例中， vPCRF可以为步骤 504中建立的 Gxx会话分配一个 标识， 而不是采用步骤 504中 BBERF为 Gxx会话分配的会话标识 1。 当然， vPCRF分配的这个标识，必须保证在 vPCRF中针对 UE的 IP-CAN会话是全 局唯一的。一旦 vPCRF为 Gxx分配了这个标识，在 vPCRF、 S9会话和 hPCRF 中都可以通过这个标识来关联到步骤 504中建立的 Gxx会话。
UE 在家乡路由的漫游场景下， 通过可信任非 3GPP 接入网采用 DSMIPv6接入 EPS的 IP-CAN会话建立流程与上述实施例基本类似，此处不 进行详细描述。 实施例二 本实施例描述 UE在家乡路由的漫游场景下， UE通过 E-UTRAN或可 信任非 3GPP接入网关， 如实施例一所示的流程接入 EPS建立 IP-CAN会话 后， 由于 BBERF发生重选 （即用户设备发生切换） 而引起的 IP-CAN会话 爹改流程。 其中， 通过 E-UTRAN接入时， S-GW与 P-GW之间采用 PMIPv6 协议， 通过可信任非 3GPP 接入网关接入时， 接入网关与 P-GW 之间采用 ΡΜΙΡνό协议。 在本实施例中， 发送端 PCRF为 vPCRF、 接收端 PCRF为 hPCRF , 如 图 6所示， 该方法包括如下的步骤 602至步骤 632: 步骤 602, New BBERF (新 BBERF )接收到建立网关控制会话请求消 息， 并且 New BBERF获得了 UE的标识 NAI , PDN标识以及用于制定策略 的接入信息等， 接入信息包括 BBERF所在的网络标识， UE当前的位置信息 等； 步骤 604, New BBERF向 vPCRF发送 "网关控制会话建立指示"消息， 该 "网关控制会话建立指示" 消息中携带有 UE的标识 NAI、 PDN标识和会 话标识 4,其中，会话标识 4是由 New BBERF分配的，用于标识 New BBERF 与 vPCRF之间将要建立的 Diameter会话。 Diamter基础十办议确保该会话标识 4是全局唯一的； 步骤 606, vPCRF才艮据 UE的标识 NAI和 PDN标识确定 UE切换之前 的上下文（ Context )、 Gxx会话和对应的 S9会话。 vPCRF向 hPCRF发送 S9 会话修改指示消息 （相当于步骤 402 ), 该消息携带有 S9会话建立指示消息 中分配给该 S9会话的会话标识 2 , 同时携带 UE新的接入信息和会话标识新 建的 Gxx会话标识 4 , 该消息还携带有 S9会话修改原因， 即网关控制会话 建立； 步骤 608 , hPCRF才艮据 S9会话的会话标识 2查找到 UE切换前对应的 上下文，并才艮据 UE新的接入信息重新制定 PCC规则和 QoS规则。同时 hPCRF 为会话标识 4对应的 Gxx会话保存一份新的 QoS规则。 hPCRF向 vPCRF发 送 S9会话修改确认消息， 该消息中携带新的 QoS规则和会话标识 4; hPCRF能够制定新的事件触发器， 并通过 S9会话修改确认消息与 QoS 规则一同下发。 步骤 610, vPCRF才艮据会话标识 4查找到对应的 Gxx会话 （相当于步 骤 404 ), 并向 New BBERF发送网关控制会话建立确认消息， 消息中携带新 的 QoS规则， 其中， New BBERF更新 QoS规则； 如果 hPCRF下发新事件触发器， vPCRF也将下发给 New BBERF, New BBERF更新事件触发器。 vPCRF 又能够根据本次策略修改 QoS 规则和 /事件触发器， 并下发给 New BBERF。 步骤 612, New BBERF向 PCEF发送 IP-CAN会话信令消息， 该消息中 携带有 UE的标识 NAI和 PDN标识；该消息实现时为 PMIPv6的«理绑定更 新消息； 步骤 614, PCEF才艮据 UE的标识 NAI和 PDN标识查找到 UE切换前对 应的上下文 ( PCC规则、 事件触发器等信息）， 并向 hPCRF发送 IP-CAN会 话修改指示消息， 消息中携带会话标识 3； 步骤 616, hPCRF才艮据会话标识 3查找到在 504步中重新制定的 PCC 规则， 并通过 IP-CAN会话爹改确认消息发送给 PCEF。 PCEF更新 PCC规 则； 步骤 618 , PCEF向 BBERF返回 IP-CAN会话信令。 该消息实现时为^ ^ 理绑定更新确认消息； 步骤 620 , New BBERF返回爹改 IP-CAN会话应答消息； 步骤 622, Old BBERF (旧 BBERF ) 收到删除网关控制会话请求消息， 消息中携带 UE的标识 NAI和 PDN标识； 步骤 624, Old BBERF才艮据 UE的标识 NAI和 PDN标识查找到 UE切 换前对应的上下文和 Gxx会话。 Old BBERF向 vPCRF发送网关控制会话终 结指示消息， 消息中携带终结指示和会话标识 1 ; 步骤 626, vPCRF ^艮据会话标识查找到对应的 S9会话， 向 hPCRF发送 S9会话修改指示， 该消息中携带有 S9会话标识 2, 同时携带终结指示和会 话标识 1 , 以及 S9会话修改原因 （即， 网关控制会话终结）； 步骤 628 , hPCRF才艮据会话标识 2判断该标识对应的 Gxx会话将被删 除， 因此， hPCRF亦删除其上该 Gxx会话的信息， 并返回 S9会话修改确认 消息， 该消息中携带有会话标识 1； 步骤 630 , vPCRF才艮据会话标识 1查找到对应的 Gx 会话，并向 BBERF 发送网关控制会话终结确认； 步骤 632 , Old BBERF返回删除 IP-CAN会话应答消息。 参考图 6可以得出，从步骤 604到步骤 630 ,同时存在着两个 Gxx会话， hPCRF通过会话标识 1和会话标识 4来分别确认这两个 Gxx会话。 从步骤 602 到步骤 614 , Old BBERF 作为 Primary BBERF , New BBERF 作为 Non-Primary BBERF; 从步骤 616到步骤 630 , Old BBERF作为 Non-Primary BBERF , New BBERF作为 Primary BBERF。 如果存在两个 Gxx会话的情况 下， BBERF发生 QoS规则的更新， hPCRF将对两个 BBERF采取不同的操 作。 实施例三 本实施例描述的 UE在家乡路由的漫游场景下， UE通过 E-UTRAN或 可信任非 3GPP接入网关， 如实施例一所示的流程接入 EPS建立 IP-CAN会 话后， 在如实施例二所示的切换流程中， BBERF 收到触发， 要求请求新的 QoS规则和 /或施加触发器的网关控制会话修改流程。 在本实施例中， 发送端 PCRF为 vPCRF、 接收端 PCRF为 hPCRF , 如 图 Ί所示， 该方法包括如下的步骤 702至步骤 716: 步骤 702 , Old BBERF收到请求消息， 要求 4艮告一个事件或请求 QoS 规则或两者皆有； 步骤 704 , Old BBERF向 vPCRF发送网关控制和 QoS规则请求消息， 消息中携带新的资源请求信息和 /或事件报告信息以及在网关控制会话建立 指示消息中分配的会话标识 1； 步骤 706 , vPCRF收到该网关控制和 QoS规则请求消息后， 根据会话 标识 1查找到对应的 S9会话， 向 hPCRF发送 S9会话修改指示消息 （相当 于步骤 402 ), 其中 S9会话建立指示消息中分配给该 S9会话的会话标识 2 , 同时携带网关控制和 QoS 规则请求消息携带的新的资源请求信息和 /或事件 •t艮告信息以及会话标识 1； 步骤 708 , hPCRF才艮据会话标识 2和会话标识 1查找到 hPCRF中保存 的该 Gxx会话的上下文， 包括 QoS规则、 事件触发器等以及该 Gxx会话对 应的 PCC规则。 同时判断该 Old BBERF为 Primary BBERF , 因此 hPCRF才艮 据新的资源请求信息和 /或事件报告信息等重新制定 PCC和 QoS规则， 并通 过 S9会话修改确认消息发送给 vPCRF ,消息中携带 QoS规则和会话标识 1； hPCRF还能够更新事件触发器， 并随更新的 QoS规则一同下发。 步骤 710, vPCRF才艮据会话标识 1查找到对应的 Gxx会话 （相当于步 骤 404 ),向 Old BBERF发送网关控制和 QoS规则响应消息，消息中携带 QoS 规则和 /或事件触发器和会话标识 1。 步骤 712, Old BBERF更新 QoS规则和 /或事件触发器； 步骤 714, hPCRF发起 IP-CAN会话爹改流程； 步骤 716, Old BBERF返回爹改应答消息。 如果在步骤 708 中， hPCRF 发现 Old BBERF 已成为 Non-Primary BBERF, 在 S9会话爹改确认消息中， hPCRF将返回拒绝信息。 类似地， 如果 New BBERF 收到请求信息， 要求 4艮告事件或请求新的
QoS规则， 在 706步中， vPCRF的 S9会话修改请求消息将携带会话标识 4 和资源请求信息和 /或事件 4艮告信息， hPCRF 判断 New BBERF 为 Primary BBERF, 将制定新的 QoS规则和 /或事件触发器。 S9会话修改确认消息携带 会话标识 4和 QoS规则和 /或事件触发器返回给 New BBERF。 如果 hPCRF 判断 New BBERF为 Non-Primary BBERF , hPCRF将返回拒绝消息。 当 UE通过可信任非 3GPP接入网关并采用 DSMIPv6协议接入 EPS的 建立 IP-CAN会话后， 由于 BBERF请求新的 QoS规则而引起的爹改流程与 此类似， 此处不进行详细描述。 实施例四 本实施例描述 UE在家乡路由的漫游场景下， UE通过 E-UTRAN或可 信任非 3GPP接入网关， 如实施例一所示的流程接入 EPS建立 IP-CAN会话 后， 在如实施例二所示的切换流程中， hPCRF收到触发， 要求更新 QoS规则 和 /或事件触发器而引起的网关控制会话修改流程。 在本实施例中， 发送端 PCRF为 hPCRF、 接收端 PCRF为 vPCRF , 如 图 8所示， 该方法包括如下的步骤 802至步骤 812: 步骤 802, hPCRF被请求更新 QoS规则和 /或事件触发器， 并才艮据提供 的信息，制定 PCC规则，并根据两个 BBERF的接入信息分别制定 QoS规则； 步骤 804, hPCRF需要同时向 Old BBERF和 New BBERF提供 QoS规 则和 /或事件触发器。本实施例仅描述向 Old BBERF提供 QoS规则和 /或事件 触发器。 hPCRF向 vPCRF发送 S9会话规则提供消息（相当于步骤 402 ), 消 息中携带为 S9会话分配的会话标识 2, 同时携带新制定的 QoS规则和 Old BBERF对应的 Gxx会话的会话标识 1 ; 步骤 806, vPCRF才艮据会话标识 1 , 查找到对应 Gxx会话（相当于步骤
404 ), 向 Old BBERF发送网关控制和 QoS规则提供消息， 该消息中携带有 会话标识 1和 QoS规则和 /或事件触发器； vPCRF有可能才艮据本次策略爹改 QoS规则和 /或事件触发器。 步骤 808 , Old BBERF安装 QoS规则和 /或事件触发器； 步骤 810, Old BBERF向 vPCRF返回网关控制和 QoS规则提供确认消 息， 该消息中携带有会话标识 1。 如果在步骤 808中， Old BBERF没有安装 成功部分或全部 QoS规则， Old BBERF将在确认消息中上 4艮没有安装成功的 QoS规则和会话标识 1 ; 步骤 812, vPCRF向 hPCRF返回 S9会话规则提供确认消息。 hPCRF 将完成余下的 IP-CAN会话更新流程。 如果步骤 810中携带了没有安装成功 的 QoS规则， vPCRF将没有安装成功的 QoS规则同会话标识 1一起上 4艮给 hPCRF。 hPCRF才艮据会话标识 1 判断这些没有安装成功的 QoS规则与 Old BBERF的 Gxx会话有关，若 hPCRF判断此时 Old BBERF为 Primary BBERF , 那么 hPCRF 4夺删除在 New BBERF中的相同的 QoS规则， 并且删除 PCEF 中对应的 PCC规则；若 hPCRF判断此时 Old BBERF为 Non-Primary BBERF , 那么 hPCRF只是将它保存信息中该 QoS规则的状态设为 "Inactive" (停止）， 而不进行其他操作。 在其他实施例中， hPCRF向 New BBERF下发 QoS规则和 /或事件触发 器， 在步骤 804 中携带会话标识 4 和 QoS规则和 /或事件触发器。 若 New BBERF没有全部安装成功 QoS规则， 那么 New BBERF ^！夺没有安装成功的 QoS规则上 4艮给 vPCRF , vPCRF将 QoS规则同会话标识 4一起上 4艮给 hPCRF。 hPCRF的判断操作流程类似。 当 UE通过可信任非 3GPP接入网关并采用 DSMIPv6协议接入 EPS的 建立 IP-CAN会话后， PCRF更新 QoS规则和 /或事件触发器的流程与此类似， 此处不进行详细描述。 实施例五 本实施例描述的 UE在本地疏导并且 AF在拜访地的漫游场景下， UE 通过 E-UTRAN或可信任非 3GPP接入网关，接入 EPS的 IP-CAN会话后, AF 建立 R 会话，提供业务信息的流程。其中 vPCRF终结 BBERF的 Gxx会话， PCEF的 Gx会话， 在 vPCRF和 hPCRF之间建立 S9会话。 S9会话将用来传 送 Gx会话和 Rx会话的信息。 通过 E-UTRAN接入时， S-GW与 P-GW之间 采用 PMIPv6协议，通过可信任非 3GPP接入网关接入时，接入网关与 P-GW 之间采用 PMIPv6十办议。 BBERF为 Gxx会话分配的会话标识为会话标识 1 , PCEF为 Gx会话分配的会话标识为会话标识 3。 vPCRF为 S9会话分配的会 话标识为会话标识 2。 在本实施例中， 发送端 PCRF为 vPCRF、 接收端 PCRF为 hPCRF , 如 图 9所示， 该方法包括如下的步骤 902至步骤 910: 步骤 902 , 由于 AF在拜访地网络， 因此 AF向 vPCRF发送应用 /业务信 息， 同时建立 AF和 vPCRF之间的 Rx会话 ( AF会话）， 消息中携带业务信 息、 UE的 IP地址、 PDN标识以及 AF为该会话分配的会话标识 5。 AF还可 以通过该消息下发事件触发， 向 PCRF订阅 IP-CAN会话发生变化时的事件 报告； 步骤 904, vPCRF才艮据 IP地址将 Rx会话与建立的 IP-CAN会话进行关 联， 包括对应的 Gxx会话、 Gx会话和 S9会话， 并查找到对应的上下文， 保 存信息的内容。 vPCRF 向 hPCRF发送 S9会话修改指示消息 （相当于步骤 402 ) , 消息中携带 S9会话的会话标识 2 , Rx会话的会话标识 5、 业务信息的 内容和 /或事件触发。 还可以携带 S9会话修改的原因， 即 "Rx会话建立"； 步骤 906, hPCRF ^艮据会话标识 2查找到对应的上下文， 并才艮据会话标 识 5和 "Rx会话建立" 判断一个 Rx会话建立， 保存消息中 Rx会话有关的 业务信息内容和 /或事件触发。 hPCRF根据业务信息、用户的签约信息和网络 策略等制定 PCC规则和 /或事件触发器。 hPCRF向 vPCRF返回 S9会话修改 确认消息， 消息中携带为 S9会话分配的会话标识 2, 携带 Rx会话的会话标 识 5 , 同时将新制定的 PCC规则和 /或事件触发器也一起发送给 vPCRF; 步骤 908 , vPCRF才艮据会话标识 5查找到对应的 Rx会话 （相当于步骤
404 )。 同时从消息中获取 IP-CAN会话的 PCC规则和 /或事件触发器。 vPCRF 向 AF返回应答消息， 消息中携带会话标识 5; 步骤 910, vPCRF从步骤 908中获取的 PCC规则中抽取出 QoS规则， 向 PCEF提供 PCC规则和 /或事件触发器， 向 BBERF提供 QoS规则和 /或事 件触发器， 发起 IP-CAN会话修改流程。 vPCRF有可能才艮据本次策略修改 PCC规则、 QoS规则和 /或事件触发器。 如果一个以上的 AF向 UE提供业务， 那么其他的 AF可以采用相同的 流程，每个 AF建立 Rx会话时都会为这个 Rx会话分配全局唯一的会话标识， 在 S9会话中可以用这个会话标识来唯一标识该 AF提供的业务信息和 /或事 件触发， PCRF根据这个会话标识能够判断这个业务信息来自哪个 AF。 在提供业务的过程中， AF可能对业务信息进行更改， 那么 AF将采用 已建立的 Rx会话向 vPCRF提供更改的业务信息， vPCRF在 S9会话中向 hPCRF 提供更改的业务信息时用这个 Rx 会话的会话标识进行标识， 从而 hPCRF就可以判断哪个 AF的业务信息发生了改变。 当 AF决定结束业务是， AF向 vPCRF发送终结 Rx会话消息， vPCRF 在 S9会话中向 hPCRF提供终结请求时用这个 Rx会话的会话标识进行标识， 从而 hPCRF就可以判断哪个 Rx会话终结， 需要删除相关的业务信息， 从而 进行相应的操作。 当然 vPCRF在 S9会话中标识某个 AF的信息也可能由 vPCRF分配， 并且， 该标识信息在该 vPCRF中唯一标识这个 IP-CAN会话。 当 UE通过可信任非 3GPP接入网关并采用 DSMIPv6协议接入 EPS的 建立 IP-CAN会话后， AF的建立、 爹改和终结的流程与此类似， 此处不进行 详细描述。 对于方案三， 同样可以采用本发明的方法来解决采用一个 S9会话传送 多个 IP-CAN会话的 Gxx或 Gx会话信息而无法进行标识的问题。 大致方法 如下：
( 1 ) 家乡路由场景：
UE初始附着建立了第一 IP-CAN会话，在这个过程中 BBERF与 vPCRF 建立第一 Gxx会话（会话标识为 1 A ), vPCRF与 hPCRF建立 S9会话， PCEF 与 hPCRF建立第一 Gx会话， 其中 Gxx会话通过 S9会话传送信息， 在 S9 会话中用 1 A标识要传送的第一 Gxx会话信息。在 UE发起建立第二 IP-CAN 会话的过程中， BBERF与 vPCRF建立第二 Gxx会话（会话标识为 2 A ), PCEF 与 hPCRF建立第二 Gx会话， 用之前建立的 S9会话来传送第二 Gxx会话信 息并用 2A标识。 此后， BBERF收到请求或事件弓 1起第一 IP-CAN会话发生 变化， 请求新的 QoS规则， BBERF通过第一 Gxx会话向 vPCRF发送请求信 息， vPCRF通过 S9会话向 hPCRF发送请求信息， 该信息用会话标识 1A来 标识。 hPCRF才艮据会话标识 1A来判断该信息来自第一 Gxx会话， 找到对应 的上下文，制定新的 QoS规则并进行更新，向 vPCRF返回消息中携带的 QoS 规则也用 1 A来标识， vPCRF才艮据 1 A将 QoS规则通过第一 Gxx会话发发送 给 BBERF。 可以用于 PCRF主动下发 QoS规则， BBERF发起的 IP-CAN会 话终结等。
( 2 ) 本地疏导场景：
UE初始附着建立了第一 IP-CAN会话，在这个过程中 BBERF与 vPCRF 建立第一 Gxx会话（会话标识为 1A ), PCEF与 vPCRF建立第一 Gx会话（会 话标识为 IB ), vPCRF与 hPCRF建立 S9会话， 其中 Gx会话通过 S9会话传 送信息， 在 S9会话中用 1B标识要传送的第一 Gx会话信息。 在 UE发起建 立第二 IP-CAN会话的过程中， BBERF与 vPCRF建立第二 Gxx会话 (会话 标识为 2 A ), PCEF与 vPCRF建立第二 Gx会话（会话标识为 2B ), 用之前 建立的 S9会话来传送第二 Gx会话信息并用 2B标识。 此后， BBERF收到 请求或事件引起第一 IP-CAN会话发生变化， 请求新的 QoS规则， BBERF 通过第一 Gxx会话向 vPCRF发送请求信息， vPCRF终结 Gxx会话， 通过 S9 会话向 hPCRF发送请求信息， 该信息是从第一个 Gxx会话的信息中获取并 用第一 Gx会话标识 1B来标识。 hPCRF才艮据会话标识 1B来判断该信息来自 第一 Gx会话，找到对应的上下文，制定新的 PCC规则并进行更新，向 vPCRF 返回消息中携带的 PCC规则也用 1B来标识， vPCRF才艮据 1B将 PCC规则通 过第一 Gx会话发送给 PCEF,并才艮据 PCC规则制定 QoS规则， 通过第一 Gxx 会话发送给 BBERF。 类似的， 可以用于 PCRF主动下发 PCC规则， BBERF、 PCEF发起的 IP-CAN会话终结等。
( 3 ) 家乡路由、 本地疏导混合场景： 该场景可以认为是（ 1 ) 和 （2 ) 的混合， 流程类似。 当然 vPCRF在 S9会话中标识某个 Gxx或 Gx的信息也可能由 vPCRF 分配， 并且， 该标识信息在该 vPCRF中唯一标识这个 IP-CAN会话。 装置实施例 才艮据本发明的实施例， 还提供了一种会话信息的标识装置， 该装置可以 用于实现上述的会话信息的标识方法， 该装置设置于包括发送端 PCRF和接 收端 PCRF的网络系统， 如图 10所示， 该装置包括： 标识模块 10、 发送模 块 20、 接收模块 30、 确定模块 40, 其中， 标识模块 10和发送模块 20设置 于发送端 PCRF, 接收模块 30和确定模块 40设置于接收端 PCRF。 优选地， 上述的发送端 PCRF可以为 vPCRF、接收端 PCRF可以为 hPCRF; 或者优选 地， 发送端 PCRF可以为 hPCRF、 接收端 PCRF可以为 vPCRF。 具体地， 标 i只模块 10 , 用于标 i只 Diameter会话， 其中， Diameter会话 与 S9会话消息中携带的 Diameter会话信息相关； 发送模块 20, 连接于标识 模块 10 ,用于发送 S9会话消息，其中， S9会话消息中携带有唯一标识 Diameter 会话的标识信息； 接收模块 30, 连接于发送模块 20, 用于接收 S9会话消息； 确定模块 40 , 连接于接收模块 30 , 用于根据标识信息确定 S9会话消息中携 带的 Diameter会话信息对应的 Diameter会话。 综上所述， 通过本发明的上述技术方案， 在使用 S9会话传送 Gxx、 Gx 以及 Rx等 Diameter会话时，通过在 S9会话中携带唯一的用于标识会话信息 的标识信息， 使得 vPCRF能够通知 hPCRF会话信息是来自于哪个 Gxx、 Gx 或 Rx会话， 并且当 hPCRF下发策略控制信息时， vPCRF能够才艮据 S9会话 中携带的唯一的标识信息将策略控制信息下发到相应的 Gxx会话、 Gx会话 或者 AF会话， 完善了策略计费控制架构中实现 S9漫游接口的应用流程。 显然， 本领域的技术人员应该明白， 上述的本发明的各模块或各步骤可 以用通用的计算装置来实现， 它们可以集中在单个的计算装置上， 或者分布 在多个计算装置所组成的网络上， 可选地， 它们可以用计算装置可执行的程 序代码来实现， 从而， 可以将它们存储在存储装置中由计算装置来执行， 或 者将它们分别制作成各个集成电路模块， 或者将它们中的多个模块或步骤制 作成单个集成电路模块来实现。 这样， 本发明不限制于任何特定的硬件和软 件结合。 以上所述仅为本发明的优选实施例而已， 并不用于限制本发明， 对于本 领域的技术人员来说， 本发明可以有各种更改和变化。 凡在本发明的^^申和 原则之内， 所作的任何修改、 等同替换、 改进等， 均应包含在本发明的保护 范围之内。

Claims

权 利 要 求 书 一种会话信息的标识方法， 应用于包括发送端策略和计费规则功能实体 即发送端 PCRF、 接收端策略和计费规则功能实体即接收端 PCRF、 承载 绑定和事件 4艮告功能实体 BBERF、 策略和计费执行功能 PCEF、 和 /或应 用功能实体 AF的网络系统， 其特征在于， 所述方法包括：
发送端 PCRF向接收端 PCRF发送 S9会话消息以传送 Diameter会 话信息， 其中， 所述 S9会话消息中携带有唯一标识 Diameter会话的标 识信息；
所述接收端 PCRF根据所述标识信息， 确定所述 S9会话消息中携 带的所述 Diameter会话信息对应的所述 Diameter会话。 根据权利要求 1所述的方法，其特征在于，在所述发送端 PCRF为 vPCRF、 所述接收端 PCRF为 hPCRF的情况下，所述发送端 PCRF向接收端 PCRF 发送 S9会话消息具体包括：
所述 vPCRF向所述 hPCRF发送 S9会话消息以传送接收到的来自 拜访地网络的一个或多个 Diameter会话信息， 其中， 所述 S9会话消息 中携带有唯一标识所述 Diameter会话的标识信息。 才艮据权利要求 2所述的方法，其特征在于，在所述 Diameter会话建立时， 所述 vPCRF向所述 hPCRF发送 S9会话消息具体包括：
所述 vPCRF终结来自拜访地网络的所述 Diameter会话；
所述 vPCRF使用 S9会话消息向所述 hPCRF传送所述 Diameter会 话信息，所述 S9会话消息中携带的所述标识信息是用于标识携带的所述 Diameter会话信息的所述 Diameter会话；
在所述 hPCRF 4艮据所述标识信息确定所述 Diameter会话之后， 所 述方法还包括：
所述 hPCRF才艮据所述标识信息， 为所述 Diameter会话建立上下文 并保存携带的所述 Diameter会话信息。
4. 才艮据权利要求 2所述的方法，其特征在于，在所述 Diameter会话爹改时， 所述 vPCRF向所述 hPCRF发送 S9会话消息具体包括：
所述 vPCRF终结来自拜访地网络的所述 Diameter会话； 所述 vPCRF使用 S9会话消息向所述 hPCRF传送所述 Diameter会 话所携带的请求和 /或修改信息， 所述 S9会话消息中携带的所述标识信 息是用于标识携带的所述请求和 /或修改信息的所述 Diameter会话； 在所述 hPCRF 4艮据所述标识信息确定所述 Diameter会话之后， 所 述方法还包括：
所述 hPCRF才艮据所述标识信息， 对所述 Diameter会话建立的上下 文进行更新。
5. 才艮据权利要求 2所述的方法， 其特征在于， 所述 Diameter会话终结时， 所述 vPCRF向所述 hPCRF发送 S9会话消息具体包括：
所述 vPCRF终结来自拜访地网络的所述 Diameter会话； 所述 vPCRF使用 S9会话消息向所述 hPCRF传送所述 Diameter会 话所携带的终结指示信息，所述 S9会话消息中携带的所述标识信息是用 于标识携带的所述终结指示信息的所述 Diameter会话；
在所述 hPCRF 4艮据所述标识信息确定所述 Diameter会话之后， 所 述方法还包括：
所述 hPCRF才艮据所述标识信息，删除所述 Diameter会话的上下文。
6. 根据权利要求 1所述的方法，其特征在于，在所述发送端 PCRF为 hPCRF、 所述接收端 PCRF为 vPCRF的情况下，所述发送端 PCRF向接收端 PCRF 发送 S9会话消息具体包括：
所述 hPCRF 向所述 vPCRF发送 S9会话消息以传送一个或多个 Diameter会话的信息， 其中， 所述 S9会话消息中携带有唯一标识所述 Diameter会话的标 i只信息；
在所述 hPCRF 4艮据所述标识信息确定所述 Diameter会话之后， 所 述方法还包括：
所述 vPCRF将所述 S9会话消息中携带的所述 Diameter会话的信 息发送到与确定的所述 Diameter会话对应的网元。
7. 才艮据权利要求 6所述的方法， 其特征在于， 所述 hPCRF向所述 vPCRF 发送 S9会话消息进一步包括：
所述 hPCRF 爹改一个或多个 Diameter会话的控制策略并使用 S9 会话消息向所述 vPCRF发送控制策略， 其中， 所述 S9会话消息中携带 的所述标识信息是用于标识接收所述控制策略的 Diameter会话。
8. 根据权利要求 1至 7中任一项所述的方法， 其特征在于， 所述 S9会话消 息携带的所述标识信息采用所述 Diameter 会话的会话标识； 或者所述 vPCRF为所述 Diameter会话分配所述标识信息， 其中， 所述标识信息在 所述 vPCRF中唯一标识一个 IP连接接入网会话。
9. 才艮据权利要求 8所述的方法， 其特征在于， 所述 Diameter会话包括以下 之一： Gxx会话、 Gx会话、 R 会话。
10. 根据权利要求 9所述的方法， 其特征在于， 所述 BBERF位于服务网关 或可信任非 3GPP IP接入网关。
11. 一种会话信息的标识装置， 其特征在于， 设置于包括发送端 PCRF和接 收端 PCRF的网络系统， 所述装置包括：
标 i只模块， 用于标 i只 Diameter会话， 其中， 所述 Diameter会话与 S9会话消息中携带的 Diameter会话信息相关；
发送模块， 用于发送所述 S9会话消息， 其中， 所述 S9会话消息中 携带有唯一标识所述 Diameter会话的标识信息；
接收模块， 用于接收所述 S9会话消息；
确定模块， 用于才艮据所述标识信息确定所述 S9会话消息中携带的 所述 Diameter会话信息对应的所述 Diameter会话。
PCT/CN2009/071212 2008-08-12 2009-04-09 会话信息的标识方法及装置 WO2010025627A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP09811002.6A EP2323340B1 (en) 2008-09-03 2009-04-09 Method and apparatus for identifying session information
US13/061,881 US20110161504A1 (en) 2008-08-12 2009-04-09 Method and apparatus for identifying session information

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200810212901.1 2008-09-03
CN2008102129011A CN101583112B (zh) 2008-08-12 2008-09-03 会话信息的标识方法及装置

Publications (1)

Publication Number Publication Date
WO2010025627A1 true WO2010025627A1 (zh) 2010-03-11

Family

ID=41800402

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2009/071212 WO2010025627A1 (zh) 2008-08-12 2009-04-09 会话信息的标识方法及装置

Country Status (2)

Country Link
EP (1) EP2323340B1 (zh)
WO (1) WO2010025627A1 (zh)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20030035759A (ko) * 2001-10-30 2003-05-09 한국전자통신연구원 다이아미터 기반 이동 인터넷 프로토콜 망에서의 세션제어 방법
CN101237383A (zh) * 2007-01-31 2008-08-06 华为技术有限公司 一种传输组播信息及授权组播业务的方法和系统

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2007026268A1 (en) * 2005-08-31 2007-03-08 Nokia Corporation Inter-access mobility and service control

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20030035759A (ko) * 2001-10-30 2003-05-09 한국전자통신연구원 다이아미터 기반 이동 인터넷 프로토콜 망에서의 세션제어 방법
CN101237383A (zh) * 2007-01-31 2008-08-06 华为技术有限公司 一种传输组播信息及授权组播业务的方法和系统

Also Published As

Publication number Publication date
EP2323340A4 (en) 2012-01-18
EP2323340A1 (en) 2011-05-18
EP2323340B1 (en) 2014-10-01

Similar Documents

Publication Publication Date Title
US9351325B2 (en) Policy control method and system for converged network
US8799440B2 (en) Policy and charging control method and system for multi-PDN connections of single APN
US9137652B2 (en) Method for implementing policy and charging control in a roaming scene
US8621555B2 (en) Access control method and system for packet data network, PCRF entity
US8793396B2 (en) Method for deleting session information in DRA
US8811342B2 (en) Method and system for deleting redundant information of home policy and charging rules function
US20110161504A1 (en) Method and apparatus for identifying session information
WO2009135362A1 (zh) 一种隐藏拜访地网络拓扑结构的策略计费控制的方法
WO2009094837A1 (en) A method for selecting a policy and charging rules function server on a non-roaming scene
US9113436B2 (en) Method and system for information transmission
WO2011011943A1 (zh) 一种承载绑定和事件报告功能的重选方法
WO2008101392A1 (fr) Procédé de transmission de qualité de service lors de transfert entre systèmes et système de réseau et réseau de destination correspondants
WO2012058998A1 (zh) 漫游场景下支持ip流迁移的策略计费控制方法和系统
WO2012006909A1 (zh) 一种上报固网接入信息的方法及系统
WO2009124436A1 (zh) 一种承载绑定和事件报告功能策略控制的方法及系统
WO2010006491A1 (zh) 一种事件触发器的下发和安装方法
WO2010034195A1 (zh) 用户设备ip地址提供方法、diameter 路由代理
WO2011029289A1 (zh) 漫游场景下承载控制模式的发送方法和系统
WO2010078761A1 (zh) 基于多接入技术的策略计费控制方法、装置和系统
CN101841798B (zh) 计费标识的关联方法和装置
WO2011018020A1 (zh) 控制pcrf负载均衡的方法、系统及重定向dra
WO2012155774A1 (zh) S9子会话建立方法、系统及pcrf
WO2013023515A1 (zh) 一种解决服务质量策略控制冲突的方法和系统
WO2011029349A1 (zh) 多承载绑定和事件报告功能的处理方法及系统
WO2011134315A1 (zh) 业务授权方法、装置及系统

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 09811002

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2009811002

Country of ref document: EP