CN102752331A

CN102752331A - Method and system for realizing policy control in peer-to-peer (P2P) network and resource control proxy

Info

Publication number: CN102752331A
Application number: CN2011101007273A
Authority: CN
Inventors: 吴建华; 陶全军
Original assignee: ZTE Corp
Current assignee: ZTE Corp
Priority date: 2011-04-21
Filing date: 2011-04-21
Publication date: 2012-10-24
Anticipated expiration: 2031-04-21
Also published as: CN102752331B; WO2012142978A1

Abstract

The invention discloses a method for realizing policy control in a peer-to-peer (P2P) network. The method comprises the following steps of: acquiring the address information of a policy control entity (PCE) after an application layer service information message sent by a service control function (SCF) node in the P2P network is received by a resource control proxy (RC-proxy) during the call process, and then, sending an application layer quality of service (QoS) request message to the PCE; and/or, acquiring the address information of a corresponding SCF node after a Diameter message sent by the PCE is received by the RC-proxy, and then, sending a policy control-related message to the SCF node. Meanwhile, the invention discloses a system for realizing the policy control in P2P network and the resource control proxy (RC-proxy). By adopting the method and the system disclosed by the invention, the policy control can be effectively realized in the P2P network.

Description

Method, resource control agent and system for realizing policy control in peer-to-peer network

Technical Field

The present invention relates to Peer-to-Peer (P2P) network technology, and in particular, to a method, a Resource Control Proxy (RC-Proxy) and a system for implementing policy Control in a P2P network.

Background

The P2P network is a distributed network, with participants in the P2P network sharing resources and services owned by the entire network, which can be accessed directly by other nodes in the network without forwarding through special intermediate entities. In a P2P network, each participant is both a provider (server) and an acquirer (client) of resources and services. The P2P network adopts overlay network technology, namely: the nodes are added into a self-organized Overlay network, and quick search and positioning of resources can be realized by using a Distributed Hash Table (DHT) algorithm.

The protocol of the P2P network mainly includes: REsource LOcation and discovery (RELOAD) protocol defined by the Internet Engineering Task Force (IETF), which is described in detail in draft-IETF-p2 psip-base-00. The RELOAD protocol provides basic services of an ad hoc network, including: routing of messages between nodes, and storage and lookup of data. In addition, the RELOAD protocol further defines a node registration Server (endrolmentserver) for allocating a node number, a security certificate, and configuration information of an overlay network to the node, wherein the configuration information includes: what DHT algorithm to use, etc. The RELOAD protocol divides nodes in an overlay network into two categories, namely: peer node and client end. The Peer node has the functions of P2P message routing, storage, searching and the like, the client can send a P2P message to the Peer node, the Peer node performs message routing and data storage, and the client does not have the functions of P2P layer message routing and data storage.

With the development and maturity of P2P network technology and related protocols, P2P network technology is also introduced into a telecommunication network to control and process core network services, fig. 1 is a networking mode of a typical telecommunication network introduced into a P2P network, and as shown in fig. 1, the network device includes: a Service Control Function (SCF) Entity and a User terminal (UE). Wherein, the SCF entity is added into the Overlay network as a Peer node, and all SCF entities form a homogenized P2P core network to jointly complete the control function of the P2P core network service. In the P2P core network, each SCF entity has the same function and is responsible for user access, session control, and service triggering. The UE is accessed to the P2P core network as a client, in other words, the UE in the Overlay network has the functions of the client in the P2P network in addition to the functions of the UE in the conventional network. In the following description, the SCF entity is referred to as SCF node. In the P2P core network, each UE has an SCF node, also referred to as a responsible node, responsible for handling UE traffic. In the networking mode, a traffic model of a basic call is shown in fig. 2, and it is assumed that UE 1 is a calling party, UE 2 is a called party, SCF1 is a responsible node of UE 1, SCF2 is a responsible node of UE 2, and a call process between UE 1 and UE 2 is as follows: the SCF2 processes the received service and sends the processed service to the UE 1 and the SCF 2. In the Session process, the service signaling interaction between the UE and the SCF, and between the SCF and the SCF, adopts a Session Initiation Protocol (SIP), and the interaction between the UE and the SCF, and between the SCF and the P2P layer, such as routing and storage at the P2P layer, adopts a RELOAD Protocol.

In order to ensure the call quality of the user and reasonably utilize network resources, operators need to perform policy control on the network. At present, a policy control system mainly includes: the basic principle of the Policy Control system is similar to that of the Resource Admission Control Subsystem (RACS) of the Telecommunications and Internet convergence Services and Advanced network protocols (TISPAN, Telecommunications and Internet Converged Services and protocols for Advanced Networking), the Resource admission Function (RACF, Resource and admission Control Function) of the International Telecommunications Union (ITU), and the Policy and Charging Control (PCC) of the third generation partnership Project (3 GPP), and the Policy Control system mainly includes, as shown in fig. 3: an Application Function (AF) entity 31, a policy control Function entity 32, and a policy enforcement Function entity 33. The function of the AF entity 31 is: abstracting a Service layer and implementing a first layer mapping of Quality of Service (QoS) mapping, namely: after acquiring service Session Description Protocol (SDP) information, mapping the information in the SDP into service QoS information, and encapsulating the service QoS information in a Diameter message and issuing the Diameter message to a policy control function entity 32; the policy control function entity 32 functions as: and a corresponding resource control strategy is made based on the information such as the operator strategy, the service QoS request, the user appointment and the like, and is issued to the strategy execution functional entity 33 for installation and execution. The policy enforcement function entity 33 functions as: under the guidance of the strategy control functional entity, the operations of QoS strategy implementation, gating, information reporting and the like are carried out.

The existing policy control system is suitable for a conventional IP Multimedia Subsystem (IMS) network. Routing problems would arise if existing policy control systems were applied directly to telecommunications networks incorporating P2P network technology. In particular, when the existing policy control system is applied to a telecommunication network incorporating the P2P network technology, the SCF node is required to have the function of an AF entity and interface with a policy control function entity. Because the SCF node has high dynamic, in a policy control process, when the SCF node fails or data migration occurs, the policy control functional entity needs to route the subsequent related message to a new SCF node, but in the existing system, the policy control functional entity cannot sense the dynamic change of the SCF node, and therefore, the subsequent related message cannot be routed to a correct target node.

Disclosure of Invention

In view of the above, the main objective of the present invention is to provide a method, an RC-proxy and a system for implementing policy control in P2P network, which can effectively implement policy control in P2P network.

In order to achieve the purpose, the technical scheme of the invention is realized as follows:

the invention provides a method for realizing policy control in a P2P network, which comprises the following steps:

in the calling process, after receiving an application layer service information message sent by an SCF node in a P2P network, an RC-proxy acquires address information of a Policy Control Entity (PCE), and then sends an application layer QoS request message to the PCE; and/or after the RC-proxy receives the Diameter message sent by the PCE, the RC-proxy acquires the address information of the corresponding SCF node and then sends a policy control related message to the SCF node.

In the above scheme, the method further comprises:

and when the SCF node sends a message to the RC-proxy for the first time in the calling process, the SCF node acquires the address information of the RC-proxy and then establishes connection with the RC-proxy.

In the above scheme, the acquiring the address information of the RC-proxy includes:

when the SCF node joins in a P2P network, the registration server issues a configuration file containing the RC-proxy address information to the SCF node; or,

the SCF node inquires from a tracking server in a P2P network to acquire the address information of the RC-proxy; or,

and the SCF node acquires the address information of the RC-proxy through a DHT algorithm.

In the above scheme, the address information of the RC-proxy is: IP address, or domain name, or Node number (ID).

In the above scheme, the acquiring address information of the PCE in the P2P network is:

the RC-proxy inquires a Diameter Routing Agent (DRA) to acquire the address information of the PCE; or,

the RC-proxy acquires the address information of the PCE from the policy configuration of a local operator; or,

and the RC-proxy acquires the address information of the PCE from the address information stored in advance locally.

In the foregoing solution, when the protocols adopted for transmitting the application layer QoS request message and the policy control related information between the RC-proxy and the SCF node, and between the RC-proxy and the PCE are different, before sending the application layer QoS request message to the PCE, the method further includes:

the RC-proxy carries out protocol conversion processing on the received application layer QoS request message;

correspondingly, before sending the policy control related message to the SCF node, the method further comprises:

and the RC-proxy performs protocol conversion on the received strategy control related message.

In the above scheme, the method further comprises:

if the function of the AF entity is deployed on the SCF node, the SCF node maps the SDP information of an application layer into QoS information of the application layer, and then sends the service information message of the application layer containing the QoS information of the application layer to the RC-proxy;

and if the function of the AF entity is deployed on the RC-Proxy, the RC-Proxy maps the application layer SDP information in the received application layer service information message into application layer QoS information.

In the above scheme, the acquiring address information of the corresponding SCF node is:

when the RC-proxy locally stores the address information of the corresponding SCF node in advance, directly acquiring the address information of the corresponding SCF node from the local;

and when the RC-proxy does not locally store the address information of the corresponding SCF node, inquiring the address information of the corresponding SCF node from the P2P network according to the DHT algorithm.

In the above scheme, after the address information of the corresponding SCF node is acquired, and when the RC-proxy locally pre-stores the address information of the corresponding SCF node, the RC-proxy learns that the corresponding SCF node is invalid, the method further includes:

inquiring the address information of the backup SCF node of the failed SCF node from the P2P network according to the DHT algorithm, updating the stored address information of the failed SCF node into the address information of the backup SCF node, and then sending a policy control related message to the backup SCF node.

In the above scheme, before sending the policy control related message to the backup SCF node, the method further includes:

and the RC-proxy establishes connection with the backup SCF node.

In the above scheme, when the RC-proxy locally pre-stores the address information of the corresponding SCF node, and the RC-proxy determines that the data corresponding to the received policy control related message has been migrated, the method further includes:

the SCF node returns an error response message to the RC-proxy;

after receiving the error response message, the RC-proxy queries the address of the target SCF node to which the data is migrated from the P2P network according to a DHT algorithm, updates the stored address information of the corresponding SCF node into the address information of the target SCF node to which the data is migrated, and then sends a policy control related message to the target SCF node to which the data is migrated.

In the above scheme, before sending the policy control related message to the target SCF node of the data migration, the method further includes:

and the RC-proxy establishes connection with the target SCF node to which the data is migrated.

The invention also provides a resource control agent for implementing policy control in a P2P network, which comprises: an acquisition module and a sending module; wherein,

the system comprises an acquisition module, a sending module and a sending module, wherein the acquisition module is used for acquiring the address information of the PCE after receiving an application layer service information message sent by the SCF node and sending the acquired address information of the PCE to the sending module; and/or after receiving the Diameter message sent by the PCE, acquiring the address information of the corresponding SCF node, and sending the acquired address information of the SCF node to a sending module;

the sending module is used for sending an application layer QoS request message to the PCE after receiving the address information of the PCE sent by the obtaining module; and/or after receiving the address information of the SCF node sent by the acquisition module, sending a policy control related message to the SCF node.

In the foregoing solution, when acquiring address information of a PCE, the acquiring module is specifically configured to: inquiring DRA to obtain address information of PCE; or acquiring address information of the PCE from the policy configuration of the local operator; or, acquiring the address information of the PCE from the locally pre-stored address information.

In the foregoing solution, when acquiring address information of a corresponding SCF node, the acquiring module is specifically configured to: when the address information of the corresponding SCF node is stored locally in advance, the address information of the corresponding SCF node is directly acquired locally; and when the address information of the corresponding SCF node is not stored locally, inquiring the address information of the corresponding SCF node from the P2P network according to the DHT algorithm.

In the above scheme, when the address information of the corresponding SCF node is acquired, and when the address information of the corresponding SCF node is stored locally in advance, and after the corresponding SCF node is known to be invalid, the acquiring module is further configured to query the address information of a backup SCF node of the invalid SCF node from the P2P network according to the DHT algorithm, update the stored address information of the invalid SCF node to the address information of the backup SCF node, and send the address information of the backup SCF node to the sending module;

the sending module is further configured to send a policy control related message to the backup SCF node after receiving the address information of the backup node sent by the obtaining module.

In the above scheme, when the address information of the corresponding SCF node is locally stored in advance, and it is determined that the data corresponding to the received policy control related message has been migrated, the acquiring module is further configured to query, according to a DHT algorithm, an address of a target SCF node to which the data is migrated from the P2P network, update the stored address information of the corresponding SCF node to the address information of the target SCF node to which the data is migrated, and send the address information of the target SCF node to which the data is migrated to the sending module;

the sending module is further configured to send a policy control related message to the target SCF node to which the data is migrated, after receiving the address information of the target SCF node to which the data is migrated, sent by the obtaining module.

In the above scheme, when the protocols used for transmitting the application layer QoS request message and the policy control related information between the RC-proxy and the SCF node and between the RC-proxy and the PCE are different, the sending module is further configured to perform protocol conversion processing on the received application layer QoS request message and/or the policy control related information, and send the application layer QoS request message and/or the policy control related information after the protocol conversion processing to the PCE and/or the SCF node, respectively.

In the above solution, the resource control agent further includes: and the storage module is used for storing the address information of the PCE and/or the address information of the SCF node.

In the above solution, the resource control agent further includes: and the connection establishing module is used for establishing connection with the SCF node.

The invention also provides a system for realizing policy control in the P2P network, which comprises: a first SCF node, an RC-proxy, and a PCE; wherein,

the first SCF node is used for sending an application layer service information message to the RC-proxy in the calling process; and/or receiving a strategy control related message sent by the RC-proxy;

the RC-proxy is used for acquiring address information of the PCE after receiving the application layer service information message sent by the first SCF node and sending an application layer QoS request message to the PCE; and/or after receiving the Diameter message sent by the PCE, acquiring the address information of the corresponding SCF node, and sending a policy control related message to the first SCF node;

the PCE is used for receiving an application layer QoS request message sent by the RC-proxy; and/or, sending a Diameter message to the RC-proxy.

In the above scheme, the first SCF node is further configured to, when sending a message to the RC-proxy for the first time in a call process, acquire address information of the RC-proxy and establish a connection with the RC-proxy;

the RC-proxy is also used for establishing connection with the first SCF node.

In the above scheme, the system further includes a second SCF node, which is a backup SCF node of the first SCF node, and is configured to receive a policy control related message sent by the RC-proxy;

and after the RC-proxy acquires that the address information of the first SCF node is stored locally in advance, and learns that the first SCF node is invalid, the RC-proxy is further used for inquiring the address information of the second SCF node from the P2P network according to the DHT algorithm, updating the stored address information of the first SCF node into the address information of the second SCF node, and sending a policy control related message to the second SCF node.

In the above scheme, the RC-proxy is further configured to establish a connection with a second SCF node;

and the second SCF node is also used for establishing connection with the RC-proxy.

In the above solution, the system further includes: the third SCF node is used for receiving the strategy control related message sent by the RC-proxy;

when the RC-proxy locally stores the address information of the corresponding SCF node in advance, and the RC-proxy determines that the data corresponding to the received strategy control related message is migrated, the first SCF node is also used for returning an error response message to the RC-proxy;

the RC-proxy is further configured to, after receiving the error response message returned by the first SCF node, query an address of the third SCF node from the P2P network according to the DHT algorithm, update the stored address information of the corresponding first SCF node to the address information of the third SCF node, and send a policy control related message to the third SCF node.

In the above scheme, the RC-proxy is further configured to establish a connection with a third SCF node;

and the third SCF node is also used for establishing connection with the RC-proxy.

In the method, the RC-proxy and the system for realizing the policy control in the P2P network, in the calling process, after the RC-proxy receives an application layer service information message sent by a SCF node in the P2P network, the RC-proxy acquires the address information of a PCE and then sends an application layer QoS request message to the PCE; and/or after receiving the Diameter message sent by the PCE, the RC-proxy acquires the address information of the corresponding SCF node and then sends a policy control related message to the SCF node, so that policy control can be effectively realized in the P2P network. In addition, the RC-proxy sends the policy control related message to the SCF node after acquiring the address information of the corresponding SCF node, so that the policy control related message can be correctly routed to the corresponding SCF node when the SCF node currently processing the service fails or data migration occurs.

Drawings

Fig. 1 is a schematic diagram illustrating a networking manner of a telecommunication network introduced with a P2P network in the prior art;

FIG. 2 is a traffic model diagram of a basic call of a typical telecommunications network incorporating a P2P network;

FIG. 3 is a schematic structural diagram of a conventional strategy control system;

FIG. 4 is a flow chart illustrating a method for implementing policy control in the P2P network according to the present invention;

FIG. 5 is a flowchart illustrating a method for implementing policy control according to an embodiment;

FIG. 6 is a flowchart illustrating a method for implementing policy control according to a second embodiment;

FIG. 7 is a flowchart illustrating a method for implementing policy control according to a third embodiment;

FIG. 8 is a flowchart illustrating a method for implementing policy control according to a fourth embodiment;

FIG. 9 is a schematic diagram of a system for implementing policy control in a P2P network according to the present invention;

FIG. 10 is a schematic diagram of a resource control agent structure for implementing policy control in the P2P network according to the present invention.

Detailed Description

The basic idea of the invention is: in the calling process, after receiving an application layer service information message sent by an SCF node in a P2P network, the RC-proxy acquires address information of a PCE (personal computer equipment), and then sends an application layer QoS (quality of service) request message to the PCE; and/or after the RC-proxy receives the Diameter message sent by the PCE, the RC-proxy acquires the address information of the corresponding SCF node and then sends a policy control related message to the SCF node.

The present invention will be described in further detail with reference to the accompanying drawings and specific embodiments.

The method for implementing policy control in the P2P network, as shown in fig. 4, includes the following steps:

step 401: when a call needs to be made, the SCF node acquires the address information of the RC-proxy and then establishes connection with the RC-proxy;

here, the SCF node is a Peer node in the P2P network, and the SCF node implements the functions of: the system is responsible for user access, session control and service triggering;

step 401 needs to be executed only when the SCF node sends a message to the RC-proxy for the first time in the call process; after the connection is established, when the SCF node subsequently sends a message to the RC-proxy, the step 401 does not need to be executed, and the message can be directly sent to the RC-proxy;

in the practical application process, the RC-proxy accesses to the P2P network by the client of P2P, and the specific access process is completely the same as that in the prior art and is not described herein again; the SCF node and the RC-proxy adopt a RELOAD protocol for routing, so that the SCF node can be completely fused with the existing network; the adopted protocol for transmitting the application layer QoS request message and the policy control related information between the RC-proxy and the SCF node is not limited to be a RELOAD protocol, a Diameter protocol or other suitable application layer protocols;

the acquiring of the address information of the RC-proxy specifically includes:

when the SCF node joins in a P2P network, the enrollent server issues a configuration file containing RC-proxy address information to the SCF node, and the SCF node obtains the RC-proxy address information according to the configuration file; or,

the SCF node queries from a tracking (tracker) server in the P2P network to obtain RC-proxy address information; or,

the SCF node searches the address information of the RC-proxy through a DHT algorithm;

after the RC-proxy is added into the P2P network, registration is initiated to a tracker server, and the tracker server stores address information and other related information of the RC-proxy; after the RC-proxy is added into the P2P network, relevant information such as address information of the RC-proxy and the like is stored on a specific node in the P2P network according to a DHT algorithm, and the SCF node can search the address information of the RC-proxy through the DHT algorithm;

the address information may specifically be: IP address, or domain name, or Node ID, etc.;

if the protocol used for transmitting the application layer QoS request message and the policy control related information between the RC-proxy and the SCF node is not a RELOAD protocol, when the RC-proxy establishes connection, the method further comprises the following steps:

the SCF node establishes application layer connection with the RC-proxy;

in actual application, the RC-Proxy, as a logical unit, may be deployed alone or together with other network element devices, for example, the RC-Proxy may be deployed on the PCE.

Step 402: after receiving the application layer service information message sent by the SCF node, the RC-proxy acquires address information of the PCE and then sends an application layer QoS request message to the PCE; and/or after the RC-proxy receives the Diameter message sent by the PCE, acquiring the address information of the corresponding SCF node, and then sending a policy control related message to the SCF node;

here, the application layer service information message includes: address information of SCF node, user identification, application layer service information, and session identification of session between SCF and RC-proxy (SR, SCF-RC-proxy); wherein, the service message of the application layer is: application layer SDP information or application layer QoS information; specifically, if the function of the AF entity is deployed on the SCF node, the SCF node maps the application layer SDP information into application layer QoS information, which is then carried in an application layer service information message and sent to the RC-Proxy, and if the function of the AF entity is deployed on the RC-Proxy, the application layer service information sent by the SCF node to the RC-Proxy is the application layer SDP information, which is mapped into application layer QoS information after the RC-Proxy receives the application layer SDP information; the specific mapping mode of the SDP information and the QoS information of the application layer is the prior art;

in actual application, the protocol used for transmitting the application layer QoS request message and the policy control related information between the RC-proxy and the PCE is the Diameter protocol. When the protocols adopted for transmitting the application layer QoS request message and the policy control related information between the RC-proxy and the SCF node and between the RC-proxy and the PCE are different, the RC-proxy performs protocol conversion processing on the received application layer QoS request message and the received policy control related information and then sends the processed application layer QoS request message and the received policy control related information to the PCE or SCF node; wherein, the specific processing procedure for protocol conversion can adopt the existing protocol conversion processing flow;

the function of the PCE is completely the same as that of a policy control function entity in the prior art, and the PCE may specifically be: a Policy and Charging Rules Function (PCRF) entity in 3GPP PCC, or a Service-based Policy Decision Function (SPDF) in the RACS of TISPAN, or a generic RACF (x-RACF) of ITU;

the diameter message may specifically be an acknowledgement message, or a time reporting message, or other policy control related messages;

the acquiring of the address information of the PCE specifically includes:

the RC-proxy inquires the DRA to acquire address information of the PCE; or,

the RC-proxy acquires address information of the PCE from the policy configuration of a local operator; or,

the RC-proxy acquires address information of the PCE from the address information stored in advance locally;

the specific processing procedures of the PC-proxy inquiring the DRA to acquire the address information of the PCE and acquiring the address information of the PCE from the local operator policy configuration are the same as those in the prior art, and are not repeated here; in practical application, when the RC-proxy does not store the address information of the PCE in advance, the address information of the PCE may be acquired by querying the DRA, or the address information of the PCE may be acquired from the policy configuration of the local operator, and when the RC-proxy acquires the address information of the PCE through the DRA query or from the policy configuration of the local operator, the address information of the PCE may be stored locally for direct use when a message is sent subsequently; here, the specific implementation manner of locally storing the address information of the PCE may be: establishing a binding relationship between the session identification of the session between the SRs and the address information of the PCE, namely: corresponding relation, after the RC-proxy receives the application layer service information message, according to the session identification of the session between the SRs in the message, the address information of the corresponding PCE can be found;

the acquiring of the address information of the corresponding SCF node specifically includes:

when the RC-proxy does not locally store the address information of the corresponding SCF node, inquiring the address information of the corresponding SCF node from the P2P network according to the DHT algorithm;

the specific implementation that the RC-proxy locally pre-stores the address information of the corresponding SCF node may be: establishing a binding relationship among address information of PCE, session identification of session between SRs, user identification, address information of SCF node and other information, namely: corresponding relation, after the RC-proxy receives the Diameter message, the address information of the corresponding SCF node can be found according to the binding relation; here, when the RC-proxy locally pre-stores the address information of the corresponding SCF node, directly obtaining the address information of the corresponding SCF node from the local, and then sending the policy control related message to the SCF node means: the obtained corresponding SCF node is an SCF node which has not undergone data migration and/or failure;

when the address information of the corresponding SCF node is obtained and the RC-proxy locally pre-stores the address information of the corresponding SCF node, if the RC-proxy knows that the corresponding SCF node is invalid, the method may further include:

inquiring the address information of a backup SCF node of a failed SCF node from a P2P network according to a DHT algorithm, updating the stored address information of the failed SCF node into the address information of the backup SCF node, and then sending a policy control related message to the backup SCF node;

before sending the policy control related message to the backup SCF node, the method may further comprise:

the RC-proxy establishes connection with the backup SCF node;

when the RC-proxy locally pre-stores the address information of the corresponding SCF node, and the RC-proxy determines that the data corresponding to the received policy control related message has been migrated, the method further comprises:

SCF node returns error response message to RC-proxy;

after receiving the error response message, the RC-proxy queries the address of the target SCF node to which the data is migrated from the P2P network according to a DHT algorithm, updates the stored address information of the corresponding SCF node into the address information of the target SCF node to which the data is migrated, and then sends a policy control related message to the target SCF node to which the data is migrated;

after determining that the session identifier of the session between the SRs carried in the policy control related message does not exist locally, the SCF node returns an error response message to the RC-proxy; after the RC-proxy receives the error response message, the migration of the data corresponding to the received strategy control related message can be determined according to the error cause value in the message;

before sending the policy control related message to the target SCF node of the data migration, the method may further comprise:

The present invention will be described in further detail with reference to examples.

The first embodiment is as follows:

the application scenario of this embodiment is as follows: in a P2P core network, an SCF node sends application layer service information to a PCE, and the PCE reports an implementation flow of a policy control related event to the SCF node. The protocols used for transmitting the application layer QoS message and the policy control related information between the RC-proxy and the SCF node, and between the RC-proxy and the PCE are the same, and the method for implementing policy control in this embodiment, as shown in fig. 5, includes the following steps:

step 501: when a call needs to be made, the SCF node acquires the address information of the RC-proxy;

here, the SCF node obtains the address information of the RC-proxy, specifically:

the SCF node queries from a tracker server in the P2P network to obtain RC-proxy address information; or,

the address information may specifically be: IP address, or domain name, or Node number (ID, Identity); in the following description, the address information is a Node ID.

Step 502: after acquiring the Node ID of the RC-proxy, the SCF Node sends a connection request (Attach request) message to the RC-proxy;

specifically, the Attach request message is routed in the P2P network according to the Node ID of the RC-proxy, and finally reaches the RC-proxy.

Step 503: after the RC-proxy receives the Attach request message, a connection request response (Attach ReqAns) message is returned to the SCF node;

here, after the RC-proxy returns the AttachReqAns message to the SCF node, it indicates that the SCF node establishes an IP connection with the RC-proxy.

Step 504: and after receiving the AttachReqAns message, the SCF node sends an application layer connection request (AppleAttach) message to the RC-proxy.

Step 505: after receiving the AppAttach request message, the RC-proxy returns an application layer connection request response (AppAttachAns) message to the SCF node;

here, after the RC-proxy returns the AppTatchAns message to the SCF node, the SCF node is indicated to establish application layer connection with the RC-proxy;

the specific implementation of steps 502-505 is the same as that of the prior art, and is not described herein again;

the steps 504-505 are executed for the purpose of: the SCF node acquires an application layer IP address of the RC-Proxy and establishes application layer connection, and the situation is suitable for the situation that the application layer protocols such as a diameter protocol are adopted between the SCF node and the RC-Proxy, in other words, the situation that steps 504-505 are executed is suitable for the situation that the upper layer protocols such as the diameter protocol need to be used and the application layer IP address of the RC-Proxy is unknown. If the RELOAD protocol is adopted between the SCF node and the RC-Proxy, the steps 504-505 are not executed;

in the calling process, when the SCF node sends a message to the RC-proxy for the first time, the steps 501-505 need to be executed; after the connection is established, when the SCF node subsequently sends a message to the RC-proxy, the steps 501-505 do not need to be executed, and the message can be directly sent to the RC-proxy.

Step 506: after receiving the AppAttachAns message, the SCF node sends an application layer service information message to the RC-proxy;

here, the application layer service information message includes address information of the SCF node, a user identifier, application layer service information, and a session identifier of a session between SRs;

the session identifier of the session between the SRs is a character string generated by the SCF node and used for identifying a certain session between the SCF node and the RC-proxy;

the application layer service information is as follows: application layer SDP information or application layer QoS information; here, whether the application layer service information is application layer SDP information or application layer QoS information is determined by the deployment of the function of the AF entity, specifically, if the function of the AF entity is deployed on the SCF node, the SCF node maps the application layer SDP information into the application layer QoS information, and the application layer QoS information is carried in the application layer service information message and sent to the RC-Proxy, if the function of the AF entity is deployed on the RC-Proxy, the application layer service information sent to the RC-Proxy by the SCF node is the application layer SDP information, and after the RC-Proxy receives the application layer SDP information, the application layer SDP information is mapped into the application layer QoS information; the specific mapping mode of the SDP information and the QoS information of the application layer is the prior art;

the specific protocol used between the SCF node and the RC-proxy is not limited, and the RELOAD protocol may be used, or an upper layer application protocol such as a Diameter protocol may be used.

Step 507-508: after the RC-proxy receives the service information message of the application layer, the address information of the PCE is obtained; then sending an application layer QoS request message to the PCE;

here, the method for acquiring the address information of the PCE by the RC-proxy may be querying the DRA, or directly acquiring the address information from the policy configuration of the local operator; the specific processing process of the PC-proxy for acquiring the address information of the PCE is the same as that in the prior art, and is not described again here;

the PCE sends an application layer QoS request message, specifically:

if the function of the AF entity is deployed on the RC-proxy, the application layer service information received by the RC-proxy is application layer SDP information, the RC-proxy maps the application layer SDP information into application layer QoS information, and then the application layer QoS information is carried in an application layer QoS request message and sent to the PCE;

if the function of the AF entity is deployed on the SCF, the application layer service information received by the RC-proxy is application layer QoS information, and the RC-proxy directly bears the application layer QoS information in an application layer QoS request message and sends the application layer QoS information to the PCE;

here, the application layer QoS request message sent by the RC-proxy to the PCE is carried in a diameter message, which contains application layer QoS information, session-ID of the diameter session, RC-proxy address information, and the like;

after the RC-proxy acquires the address information of the PCE, the RC-proxy stores the binding relationship among the session identifier of the session between the SRs, the address information of the SCF node, the user identifier, the diameter session-ID, and the address information of the PCE, and subsequently can perform routing according to the stored binding relationship, that is: and the subsequent RC-proxy can acquire the PCE address information and the address information of the SCF node according to the binding relationship.

Step 509: after receiving the application layer QoS request message, the PCE stores the service information and returns a Diameter confirmation message to the RC-proxy;

here the Diameter acknowledgement message contains a session-ID.

Step 510-511: after the RC-proxy receives the Diameter confirmation message, acquiring address information of the SCF node; then sending a confirmation message to the SCF node;

here, the acknowledgement message sent to the SCF node carries the session identifier of the session between the SRs;

the RC-proxy acquires the address information of the SCF node, and specifically comprises the following steps:

and inquiring the locally stored binding relationship according to the session-ID in the Diameter confirmation message so as to acquire the address information of the SCF node.

Step 512: when the PCE needs to report an event to the RC-proxy, the PCE sends a Diameter event report message to the RC-proxy;

here, the Diameter event report message carries information such as a report event, a user identifier, and a Diameter-ID.

Step 513-514: after receiving the Diameter event report message, the RC-proxy acquires the address information of the SCF node; then sending an event report message to the SCF node;

here, the event report message sent to the SCF node carries a session identifier of a session between the SRs and a notification event;

the RC-proxy acquires address information of the SCF node, and specifically comprises the following steps:

and inquiring the locally stored binding relationship according to the session-ID in the Diameter event report message so as to acquire the address information of the SCF node.

Step 515: after receiving the event report message, the SCF node sends a confirmation message to the RC-proxy;

here, the acknowledgement message carries a session identifier of a session between the SRs.

Step 516: after receiving the confirmation message, the RC-proxy inquires the locally stored binding relationship according to the session identification of the session between the SRs, acquires the address information of the PCE, and then sends the confirmation message to the PCE.

Example two:

the application scenario of this embodiment is as follows: in the P2P core network, the SCF node that handles the service fails in the policy control process of one session, that is: the SCF node is down or exits from the P2P core network, wherein, the RC-proxy stores the binding relationship of the session identification of the session between the SRs, the address information of the SCF node, the user identification, the diameter session-ID and the address information of the PCE in advance, and the protocols for transmitting the QoS information of the application layer and the policy control related information between the RC-proxy and the SCF node and between the RC-proxy and the PCE are the same. And after the SCF for processing the service fails, the backup SCF node of the failed SCF node takes over the SCF node for processing the service. The method for implementing policy control in this embodiment, as shown in fig. 6, includes the following steps:

step 601: when the PCE needs to report an event to the RC-proxy, the PCE sends a Diameter event report message to the RC-proxy;

Step 602: the RC-proxy receives the Diameter event report message, and after knowing that the SCF node for processing the service is invalid, the RC-proxy queries the address information of the backup SCF node of the invalid SCF node from the P2P network by adopting a DHT algorithm according to the hash (hash) value of the user identifier, and replaces the address information of the invalid SCF node in the prestored binding relationship by adopting the address information of the backup SCF node;

here, the RC-proxy learns the SCF node failure handling service may adopt the existing technology, and is not described herein again.

Step 603: and the RC-proxy sends an Attach request message to the backup SCF node.

Here, after the SCF node processing the service fails, the backup SCF node may learn, by the prior art, that the SCF node processing the service fails, and at this time, the backup SCF node may send an attach request message to the RC-proxy so as to establish an IP connection and an application layer connection with the RC-proxy, thereby taking over the failed SCF node processing the service; the backup SCF node can obtain the address information of the RC-proxy through the backup information of the failed SCF node;

and when the address information of the RC-proxy is the Node ID of the RC-proxy, the Attach request message is routed in the P2P network according to the Node ID of the RC-proxy and finally reaches the RC-proxy.

Step 604: after receiving the Attach request message, the backup SCF node returns an Attach ReqAns message to the RC-proxy;

here, after the backup SCF node returns the AttachReqAns message to the RC-proxy, it indicates that the backup SCF node establishes a connection with the RC-proxy.

Step 605: and after receiving the AttachReqAns message, the RC-proxy sends an AppAttach message to the backup SCF node.

Step 606: after receiving the AppEttach request message, the backup SCF node returns an AppEttachAns message to the RC-proxy;

here, after the backup SCF node returns the AppAttachAns message to the RC-proxy, the backup SCF node indicates that the backup SCF node establishes an application layer connection with the RC-proxy;

the specific implementation of steps 603-606 is the same as that of the prior art, and is not described herein again;

the steps 605 to 606 are executed for the purpose of: the RC-Proxy acquires an application layer IP address of the backup SCF node and establishes application layer connection, and the condition is suitable for the condition that a diameter protocol and other application layer protocols are adopted between the backup SCF node and the RC-Proxy, in other words, the condition that steps 605-606 are executed is suitable for the condition that the diameter protocol and other upper layer protocols are used and the application layer IP address of the backup SCF node is unknown. If the RELOAD protocol is used between the backup SCF node and the RC-Proxy, steps 605-606 may not be performed.

Step 607: and sending an event reporting message to the backup SCF node.

Step 608: after receiving the event report message, the backup SCF node sends a confirmation message to the RC-proxy;

Step 609: after receiving the confirmation message, the RC-proxy inquires the locally stored binding relationship according to the session identification inquiry of the session between the SRs, acquires the address information of the PCE and then sends the confirmation message to the PCE.

Example three:

the application scenario of this embodiment is as follows: in the P2P core network, the SCF node handling the service performs data migration in the policy control process of a session, that is: and migrating part of user data and service information which are responsible for processing by the SCF node for processing the service to another SCF node, wherein the RC-proxy stores the binding relationship of session identification of the session between the SRs, address information of the SCF node, user identification, diameter session-ID and address information of the PCE in advance, and the protocols used for transmitting the application layer QoS information and the policy control related information between the RC-proxy and the SCF node and between the RC-proxy and the PCE are the same. In the following description, the SCF node that handles the service is referred to as SCF1, and the target SCF node for data migration is referred to as SCF 2. The method for implementing policy control in this embodiment, as shown in fig. 7, includes the following steps:

step 701: when the PCE needs to report an event to the RC-proxy, the PCE sends a Diameter event report message to the RC-proxy;

Step 702-703: after receiving the Diameter event report message, the RC-proxy acquires the address information of the SCF 1; then sending an event report message to the SCF 1;

here, the event report message sent to the SCF1 carries the session identifier of the session between the SRs and the notification event;

the RC-proxy acquires the address information of the SCF1, and specifically comprises the following steps:

and inquiring the locally stored binding relationship according to the session-ID in the Diameter event report message, thereby acquiring the address information of the SCF 1.

Step 704: SCF1 receives the event report message, and returns error response message to RC-proxy after determining that there is no session identification of session between SR in the message;

here, after the data migration, the SCF1 will not have any information of the migrated data locally, and accordingly, the SCF1 determines that the session identifier of the session between the SRs carried in the message does not exist locally; the error response message carries an error reason, that is: a session identification of the session between the SRs does not exist.

Step 705: after the RC-proxy receives the error response message, according to the hash value of the user identifier, the address information of a new SCF node is obtained again from the P2P network by adopting a DHT algorithm, and the address information of the SCF1 in the binding relationship is updated to the address information of the new SCF node, namely SCF 2;

here, the RC-proxy can know that the relevant user data and service information in the SCF1 have migrated according to the error cause.

Step 706: the RC-proxy sends an Attach request message to the SCF 2.

Step 707: after receiving the Attach request message, SCF2 returns an Attach ReqAns message to the RC-proxy;

here, the SCF2 returns an AttachReqAns message to the RC-proxy, indicating that the SCF2 has established a connection with the RC-proxy.

Step 708: and after receiving the AttachReqAns message, the RC-proxy sends an AppAttach message to the SCF 2.

Step 709: after receiving the AppEttach request message, the SCF2 returns an AppEttachAns message to the RC-proxy;

here, after the SCF2 returns the AppAttachAns message to the RC-proxy, it indicates that the SCF2 establishes an application layer connection with the RC-proxy;

the specific implementation of steps 706-709 is the same as that of the prior art, and is not described herein again;

the steps 708 to 709 are executed for the following purposes: the RC-Proxy acquires the IP address of the application layer of the SCF2 and establishes application layer connection, and the condition is suitable for the condition that the application layer protocols such as the diameter protocol are adopted between the SCF2 and the RC-Proxy, in other words, the condition that the steps 708-709 are executed is suitable for the condition that the upper layer protocols such as the diameter protocol need to be used and the IP address of the application layer of the SCF2 is unknown. If a RELOAD protocol is employed between SCF2 and RC-Proxy, steps 708-709 may not be performed.

Step 710: and then sends an event report message to the SCF 2.

Step 711: SCF2 sends confirmation message to RC-proxy after receiving event report message;

Step 712: after receiving the confirmation message, the RC-proxy inquires the locally stored binding relationship according to the session identification inquiry of the session between the SRs, acquires the address information of the PCE and then sends the confirmation message to the PCE.

Example four:

the application scenario of this embodiment is as follows: in a P2P core network, an SCF node sends application layer service information to a PCE, and the PCE reports an implementation flow of a policy control related event to the SCF node. Wherein, the RC-proxy does not locally store the binding relationship, that is: the same protocol is used for transmitting the application layer QoS message and the policy control related information between the RC-proxy and the SCF node, and between the RC-proxy and the PCE, without storing the address information of the SCF, and this embodiment implements the policy control method, as shown in fig. 8, including the following steps:

step 801: when a call needs to be made, the SCF node acquires the address information of the RC-proxy;

the address information may specifically be: IP address, or domain name, or Node ID; in the following description, the address information is a Node ID.

Step 802: after acquiring the Node ID of the RC-proxy, the SCF Node sends an Attachrequest message to the RC-proxy;

Step 803: after the RC-proxy receives the Attach request message, returning an Attach ReqAns message to the SCF node;

here, after the RC-proxy returns the AttachReqAns message to the SCF node, it indicates that the SCF node establishes a connection with the RC-proxy.

Step 804: and after receiving the AttachReqAns message, the SCF node sends an AppAttach message to the RC-proxy.

Step 805: after receiving the AppAttach request message, the RC-proxy returns an AppAttachAns message to the SCF node;

the specific implementation of steps 802-805 is the same as that of the prior art, and is not described herein again;

the steps 804 to 805 are executed for the purpose of: the SCF node acquires an application layer IP address of the RC-Proxy and establishes application layer connection, and the situation is suitable for the situation that the application layer protocols such as a diameter protocol are adopted between the SCF node and the RC-Proxy, in other words, the situation that steps 804-805 are executed is suitable for the situation that the upper layer protocols such as the diameter protocol need to be used and the application layer IP address of the RC-Proxy is unknown. If the RELOAD protocol is adopted between the SCF node and the RC-Proxy, the steps 804-805 are not executed;

in the calling process, when the SCF node sends a message to the RC-proxy for the first time, the steps 801-805 need to be executed; after the connection is established, when the SCF node subsequently sends a message to the RC-proxy, the steps 801-805 do not need to be executed, and the message can be directly sent to the RC-proxy.

Step 806: after receiving the AppAttachAns message, the SCF node sends an application layer service information message to the RC-proxy;

the application layer service information is as follows: application layer SDP information or application layer QoS information; here, whether the application layer service information is application layer SDP information or application layer QoS information is determined by deployment of a function of an AF entity, specifically, if the function of the AF entity is deployed on an SCF node, the SCF node maps the application layer SDP information into application layer QoS information and sends the application layer QoS information to an RC-Proxy, if the function of the AF entity is deployed on the RC-Proxy, the application layer service information sent to the RC-Proxy by the SCF node is the application layer SDP information, and after the RC-Proxy receives the application layer SDP information, the application layer SDP information is mapped into application layer QoS information; the specific mapping mode of the SDP information and the QoS information of the application layer is the prior art;

Steps 807 to 808: after the RC-proxy receives the service information message of the application layer, the address information of the PCE is obtained; then sending an application layer QoS request message to the PCE;

the PCE sends an application layer QoS request message, specifically:

if the function of the AF entity is deployed on the RC-proxy, the application layer service information received by the RC-proxy is application layer SDP information, the RC-proxy maps the application layer SDP information into application layer QoS information, and then the application layer QoS information is carried in an application layer QoS request and sent to the PCE;

if the function of the AF entity is deployed on the SCF, the application layer service information received by the RC-proxy is an application layer QoS message, and the RC-proxy directly sends the service information loaded in an application layer QoS request to the PCE;

here, the application layer QoS request sent by the RC-proxy to the PCE is carried in a diameter message, which contains application layer QoS information, session-ID of the diameter session, RC-proxy address information, and the like;

after the RC-proxy queries the address information of the PCE, the binding relationship between the session identifier of the session between the SRs and the address information of the PCE is stored.

Step 809: after receiving the application layer QoS request message, the PCE stores the service information and returns a Diameter confirmation message to the RC-proxy;

here, the Diameter acknowledgement message includes a session-ID and a user identifier.

Step 810-811: after the RC-proxy receives the Diameter confirmation message, according to the hash value of the user identifier, the address information of the corresponding SCF node is inquired from the P2P network by adopting a DHT algorithm, and then the confirmation message is sent to the SCF node;

here, the acknowledgement message sent to the SCF node carries the session identifier of the session between the SRs.

Step 812: when the PCE needs to report an event to the RC-proxy, the PCE sends a Diameter event report message to the RC-proxy;

Step 813-814: after receiving the Diameter event report message, the RC-proxy queries the address information of the corresponding SCF node from the P2P network by adopting a DHT algorithm according to the hash value of the user identifier, and then sends the event report message to the SCF node;

here, the event report message sent to the SCF node carries the session identifier of the session between the SRs and the notification event.

Step 815: after receiving the event report message, the SCF node sends a confirmation message to the RC-proxy;

Step 816-817: after receiving the confirmation message, the RC-proxy inquires the locally stored binding relationship according to the session identification inquiry of the session between the SRs, acquires the address information of the PCE and then sends the confirmation message to the PCE.

In order to implement the above method, the present invention further provides a system for implementing policy control in a P2P network, as shown in fig. 9, the system includes: a first SCF node 91, RC-proxy92, and PCE 93; wherein,

the first SCF node 91, configured to send an application layer service information message to the RC-proxy92 in the call process; and/or receiving a strategy control related message sent by the RC-proxy 92;

the RC-proxy92 is configured to, after receiving the application layer service information message sent by the first SCF node 91, obtain address information of the PCE 93, and send an application layer QoS request message to the PCE 93; and/or, after receiving the Diameter message sent by PCE 93, obtain the address information of the corresponding SCF node, and send a policy control related message to first SCF node 91;

PCE 93, used for receiving application layer QoS request message sent by RC-proxy 92; and/or, send Diameter messages to RC-proxy 92.

The first SCF node 91 is further configured to, when sending a message to the RC-proxy for the first time in a call process, acquire address information of the RC-proxy92, and establish a connection with the RC-proxy 92;

the RC-proxy92 is also used to establish a connection with the first SCF-node 91.

When the protocol used for transmitting the application layer QoS request message and the policy control related information between the RC-proxy92 and the first SCF-node 91 is not a RELOAD protocol, and when establishing a connection with the RC-proxy92, the first SCF-node 91 is further configured to establish an application layer connection with the RC-proxy 92;

the RC-proxy92 is also used to establish an application layer connection with the first SCF-node 91.

The system may further include a second SCF node, which is a backup SCF node of the first SCF node 91, and is configured to receive the policy control related message sent by the RC-proxy 92;

when the address information of the corresponding SCF node is acquired, and when the RC-proxy92 locally and previously stores the address information of the first SCF node 91, if the RC-proxy learns that the first SCF node 91 is invalid, the RC-proxy92 is further configured to query the address information of the second SCF node from the P2P network according to the DHT algorithm, update the stored address information of the first SCF node 91 to the address information of the second SCF node, and send a policy control related message to the second SCF node.

Before sending the policy control related message to the second SCF node, the RC-proxy92 is further configured to establish a connection with the second SCF node;

the second SCF node is also used for establishing connection with the RC-proxy 92.

The system may further comprise: the third SCF node is a target SCF node for data migration and receives the strategy control related message sent by the RC-proxy 92;

when the RC-proxy92 locally stores the address information of the corresponding SCF node in advance, and the RC-proxy92 determines that the data corresponding to the received policy control related message has been migrated, the first SCF node is further configured to return an error response message to the RC-proxy 92;

the RC-proxy92 is further configured to, after receiving the error response message returned by the first SCF node, query an address of the third SCF node from the P2P network according to the DHT algorithm, update the stored address information of the corresponding first SCF node 91 to the address information of the third SCF node, and send a policy control related message to the third SCF node.

The RC-proxy92 is further adapted to establish a connection with a third SCF-node before sending policy control related messages to the third SCF-node.

The third SCF-node is further configured to establish a connection with an RC-proxy 92.

Here, the specific processing procedures of the first SCF node and the RC-proxy in the system of the present invention have been described in detail above, and are not described again.

In order to implement the foregoing method, the present invention further provides an RC-proxy for implementing policy control in a P2P network, as shown in fig. 10, where the RC-proxy includes: an acquisition module 101 and a sending module 102; wherein,

the acquiring module 101 is configured to acquire address information of a PCE after receiving an application layer service information message sent by an SCF node, and send the acquired address information of the PCE to the sending module 102; and/or after receiving the Diameter message sent by the PCE, acquiring address information of the corresponding SCF node, and sending the acquired address information of the SCF node to the sending module 102;

a sending module 102, configured to send an application layer QoS request message to the PCE after receiving the address information of the PCE sent by the obtaining module 101; and/or after receiving the address information of the SCF node sent by the obtaining module 101, sending a policy control related message to the SCF node.

When acquiring the address information of the PCE, the acquiring module 101 is specifically configured to: inquiring DRA to obtain address information of PCE; or acquiring address information of the PCE from the policy configuration of the local operator; or, acquiring the address information of the PCE from the locally pre-stored address information.

When acquiring the address information of the corresponding SCF node, the acquiring module 101 is specifically configured to: when the address information of the corresponding SCF node is stored locally in advance, the address information of the corresponding SCF node is directly acquired locally; and when the address information of the corresponding SCF node is not stored locally, inquiring the address information of the corresponding SCF node from the P2P network according to the DHT algorithm.

The acquiring module 101 is further configured to, when the address information of the corresponding SCF node is acquired, and when the address information of the corresponding SCF node is stored locally in advance, and after it is known that the corresponding SCF node is failed, query the address information of a backup SCF node of the failed SCF node from the P2P network according to the DHT algorithm, update the stored address information of the failed SCF node to the address information of the backup SCF node, and send the address information of the backup SCF node to the sending module 102;

the sending module 102 is further configured to send a policy control related message to the backup SCF node after receiving the address information of the backup node sent by the obtaining module 101.

When the address information of the corresponding SCF node is stored locally in advance, and it is determined that the data corresponding to the received policy control related message has been migrated, the acquiring module 101 is further configured to query, according to the DHT algorithm, an address of a target SCF node to which the data is migrated from the P2P network, update the stored address information of the corresponding SCF node to the address information of the target SCF node to which the data is migrated, and send the address information of the target SCF node to which the data is migrated to the sending module 102;

the sending module 102 is further configured to send a policy control related message to the target SCF node to which the data is migrated, after receiving the address information of the target SCF node to which the data is migrated, sent by the obtaining module 101.

When the protocols adopted for transmitting the application layer QoS request message and the policy control related information between the RC-proxy and the SCF node and between the RC-proxy and the PCE are different, the sending module 102 is further configured to perform protocol conversion processing on the received application layer QoS request message and/or the policy control related information, and send the application layer QoS request message and/or the policy control related information after the protocol conversion processing to the PCE and/or the SCF node, respectively;

the RC-proxy may further include a storage module for storing address information of the PCE, and/or address information of the SCF node.

The RC-proxy may further comprise: and the connection establishing module is used for establishing connection with the SCF node.

The above description is only a preferred embodiment of the present invention, and is not intended to limit the scope of the present invention.

Claims

1. A method for implementing policy control in a peer-to-peer (P2P) network, the method comprising:

in the calling process, after receiving an application layer service information message sent by a Service Control Function (SCF) node in a P2P network, a resource control agent (RC-proxy) acquires address information of a Policy Control Entity (PCE), and then sends an application layer quality of service (QoS) request message to the PCE; and/or after the RC-proxy receives the Diameter message sent by the PCE, the RC-proxy acquires the address information of the corresponding SCF node and then sends a policy control related message to the SCF node.

2. The method of claim 1, further comprising:

3. The method according to claim 2, wherein the obtaining the address information of the RC-proxy is:

and the SCF node acquires the address information of the RC-proxy through a Distributed Hash Table (DHT) algorithm.

4. The method of claim 3, wherein the address information of the RC-proxy is: IP address, or domain name, or Node number (ID).

5. The method of claim 1, wherein the obtaining address information of the PCE in the P2P network is:

6. The method of claim 1, wherein when the protocols used for transferring the application layer QoS request message and the policy control related information between the RC-proxy and the SCF node and between the RC-proxy and the PCE are different, before sending the application layer QoS request message to the PCE, the method further comprises:

7. The method of claim 1, further comprising:

if the function of an Application Function (AF) entity is deployed on the SCF node, the SCF node maps application layer Session Description Protocol (SDP) information into application layer QoS information, and then sends an application layer service information message containing the application layer QoS information to the RC-proxy;

8. The method according to any one of claims 1 to 7, wherein the acquiring address information of the corresponding SCF node is:

9. The method according to claim 8, wherein after acquiring the address information of the corresponding SCF node, and when the RC-proxy locally pre-stores the address information of the corresponding SCF node, the RC-proxy acquires that the corresponding SCF node is invalid, the method further comprises:

10. The method of claim 9, wherein prior to sending the policy control related message to the backup SCF node, the method further comprises:

and the RC-proxy establishes connection with the backup SCF node.

11. The method of claim 8, wherein when the RC-proxy locally pre-stores the address information of the corresponding SCF node, and the RC-proxy determines that the data corresponding to the received policy control related message has been migrated, the method further comprises:

the SCF node returns an error response message to the RC-proxy;

12. The method of claim 11, wherein prior to sending a policy control related message to the target SCF node of the data migration, the method further comprises:

13. A resource control agent for implementing policy control in a P2P network, the resource control agent comprising: an acquisition module and a sending module; wherein,

14. The resource control agent of claim 13, wherein, when acquiring the address information of the PCE, the acquiring module is specifically configured to: inquiring DRA to obtain address information of PCE; or acquiring address information of the PCE from the policy configuration of the local operator; or, acquiring the address information of the PCE from the locally pre-stored address information.

15. The resource control agent of claim 13, wherein, when acquiring the address information of the corresponding SCF node, the acquiring module is specifically configured to: when the address information of the corresponding SCF node is stored locally in advance, the address information of the corresponding SCF node is directly acquired locally; and when the address information of the corresponding SCF node is not stored locally, inquiring the address information of the corresponding SCF node from the P2P network according to the DHT algorithm.

16. The resource control agent of claim 15, wherein the obtaining module, after obtaining the address information of the corresponding SCF node, and when locally pre-storing the address information of the corresponding SCF node, and knowing that the corresponding SCF node is failed, is further configured to query the address information of a backup SCF node of the failed SCF node from the P2P network according to a DHT algorithm, update the stored address information of the failed SCF node to the address information of the backup SCF node, and send the address information of the backup SCF node to the sending module;

17. The resource control agent of claim 15, wherein, when the address information of the corresponding SCF node is locally pre-stored and it is determined that the data corresponding to the received policy control related message has been migrated, the obtaining module is further configured to query, according to a DHT algorithm, an address of a target SCF node to which the data is migrated from the P2P network, update the stored address information of the corresponding SCF node to the address information of the target SCF node to which the data is migrated, and send the address information of the target SCF node to which the data is migrated to the sending module;

18. The resource control agent according to any of claims 13 to 17, wherein when the protocols used for transferring the application layer QoS request message and the policy control related information between the RC-proxy and the SCF node and between the RC-proxy and the PCE are different, the sending module is further configured to perform protocol conversion processing on the received application layer QoS request message and/or the policy control related information, and send the application layer QoS request message and/or the policy control related information after the protocol conversion processing to the PCE and/or the SCF node, respectively.

19. The resource control agent according to any of claims 13 to 17, characterized in that the resource control agent further comprises: and the storage module is used for storing the address information of the PCE and/or the address information of the SCF node.

20. The resource control agent according to any of claims 13 to 17, characterized in that the resource control agent further comprises: and the connection establishing module is used for establishing connection with the SCF node.

21. A system for implementing policy control in a P2P network, the system comprising: a first SCF node, an RC-proxy, and a PCE; wherein,

22. The system of claim 21,

the first SCF node is also used for acquiring the address information of the RC-proxy when a message is sent to the RC-proxy for the first time in the calling process and establishing connection with the RC-proxy;

the RC-proxy is also used for establishing connection with the first SCF node.

23. The system according to claim 21 or 22, characterized in that the system further comprises a second SCF-node, which is a backup SCF-node of the first SCF-node, for receiving the policy control related message sent by the RC-proxy;

24. The system of claim 23,

the RC-proxy is also used for establishing connection with a second SCF node;

25. A system according to claim 21 or 22, characterized in that the system further comprises: the third SCF node is used for receiving the strategy control related message sent by the RC-proxy;

26. The system of claim 25,

the RC-proxy is also used for establishing connection with a third SCF node;