CN105553923A - Method for obtaining user identifier and network side equipment - Google Patents

Abstract

The invention discloses a method for acquiring user identification and network side equipment, and relates to AF (Application? Function, application function) technology. The method disclosed in the present invention includes: when the policy and charging control entity PCRF receives the request message sent by the application function entity AF, it parses the request message; The response message of the request message carries the user identifier requested by the AF; the PCRF feeds back the constructed response message to the AF. The invention also discloses a network side device. The technical solution of the present application utilizes the existing interface to transmit the user ID, thereby solving the problem that the AF network element cannot obtain the user ID in some scenarios, resulting in the inability to perform service control based on the user ID, and the implementation method is simple and efficient.

Description

A method for obtaining user identification and network side equipment

technical field

The present invention relates to AF (Application Function, application function) technology, and is an implementation scheme for AF to obtain a user ID in a scenario where the user ID cannot be obtained in a PCC (Policy and Charging Control, policy and charging control) framework.

Background technique

In the PCC architecture network, as shown in Figure 1, there are several main functional entities: PCRF (PolicyandChargingRuleFunction, policy and charging rule function), PCEF (PolicyandChargingEnforcementFunction, policy and charging enforcement function), BBERF (BearerBindingandEventReportingFunction, bearer binding Fixed and event reporting function), AF (Application Function, application function), TDF (TrafficDetectionFunction, business detection function), SPR (SubscriptionProfileRepository, user subscription database), OFCS (Offline charging system, offline charging system), OCS (Online charging system, online charging system).

The PCRF is mainly responsible for the formulation of policies and charging rules, and sends the formulated PCC policies and charging rules to the PCEF through the Gx interface. The PCEF installs and executes the PCC policies, reports related events, and exchanges charging information with the charging system. PCRF sends QoS (Quality of Service) rules to BBERF through the Gxx interface. BBERF does not exchange charging information with the charging system, but is only responsible for bearer binding and reporting of related events. The PCRF sends the service information to be monitored to the TDF through the Sd interface, and the TDF performs service monitoring and reports it to the PCRF. The AF provides service information to the PCRF through the Rx interface. The SPR stores the service information signed by the user, and the PCRF can query the SPR for the service information signed by the user through the Sp interface. The OCS reports policy counter status information related to user consumption to the PCRF through the Sy interface. The PCEF sends the online charging information to the OCS through the Gy interface for online charging statistics, and sends the offline charging information to the OFCS through the Gz interface. TDF sends service-based online charging information to OCS through the Gyn interface, and sends service-based offline charging information to OFCS through the Gzn interface.

The PCEF and the PCRF maintain the connection state with each other through the IP-CAN (IP Connectivity Access Network, IP connection access network) session, and the AF and the PCRF maintain the connection state with each other through the AF session. PCEF sends instructions to PCRF to establish, update, and release IP-CAN sessions through CCR (Credit-Control-Request) messages; AF sends instructions to PCRF to establish and update AF sessions through AAR (Authentication-Authorization-Request) messages. An instruction to send an instruction to release the AF session to the PCRF through a STR (Session-Termination-Request, session termination request).

Based on the service-related information provided by the AF, the bearer-related information reported by the PCEF, and the service information signed by users in the SPR, the PCRF formulates a dynamic PCC policy and sends it to the PCEF. The policy information includes QoS and charging information.

AF can provide dynamic policy and charging control for services. The AF may be a P-CSCF (Proxy-CallSessionControlFunction, proxy call session control function) in an IMS (IP Multimedia System, IP Multimedia Subsystem) network, or a third-party application platform. In some scenarios, the third-party application platform, as an AF network element, is limited by network deployment and cannot obtain user IDs, so it cannot perform user ID-based service control, such as user ID-based charging purposes. The IP-CAN session created between PCRF and PCEF holds the user ID associated with the session. When the AF session is created, it will be bound with the IP-CAN session. After the session is bound, the user ID associated with the AF session can be obtained. However, how the PCRF sends the associated user ID to the AF through the Rx interface is an urgent problem to be solved.

Contents of the invention

The technical problem to be solved by the present invention is to provide a method for obtaining user IDs and network side equipment to solve the problem and defect that AF network elements cannot obtain user IDs when a third-party application platform is used as AF.

In order to solve the above technical problems, the present invention discloses a method for obtaining a user ID, which includes the following operations:

When the policy and charging control entity PCRF receives the request message sent by the application function entity AF, it parses the request message;

If the PCRF parses from the request message to obtain an indication that the AF requests to obtain the user ID, then constructing the response message of the request message carries the user ID obtained by the AF request;

The PCRF feeds back the constructed response message to the AF.

Optionally, in the above method, the request message includes at least Authentication Authorization Request AAR and Session Termination Request STR messages.

Optionally, the above method also includes:

When the PCRF does not obtain an indication that the AF requests to obtain the user ID from the request message, the PCRF judges whether the AF network element needs to obtain the user ID from the PCRF according to the configuration of the AF adjacent office;

When the AF network element needs to obtain the user ID from the PCRF, the PCRF constructs the response message of the request message to carry the user ID requested by the AF.

Optionally, in the above method, the PCRF parses from the request message to obtain an indication that the AF requests to obtain the user ID:

The PCRF parses and obtains the value of the setting field from the request message, and judges that the AF requests to obtain the user identifier from the PCRF.

The invention also discloses a network side device, including:

The parsing unit, when receiving the request message sent by the application function entity AF, parses the request message;

A response message construction unit, when the parsing unit parses from the request message to obtain an indication that the AF requests to obtain the user ID, constructing the response message of the request message, carrying the user ID obtained by the AF request;

The sending unit feeds back the response message constructed by the response message construction unit to the AF.

Optionally, in the above device, it is characterized in that the request message includes at least an Authentication Authorization Request AAR and a Session Termination Request STR message.

Optionally, in the above-mentioned device, if the response message construction unit does not obtain an indication that the AF requests to obtain the user ID from the request message, it judges whether the AF network element needs to obtain the user ID from the PCRF according to the configuration of the AF adjacent office. logo;

When the AF network element needs to obtain the user ID from the PCRF, the response message for constructing the request message carries the user ID requested by the AF.

Optionally, in the above device, the parsing unit parses the request message to obtain an indication that the AF requests to obtain the user ID:

The parsing unit parses and obtains the value of the setting field from the request message to be a set value, and then judges that the AF requests to obtain the user ID from the device.

Optionally, in the above device, the network side device is a policy and charging control PCRF device.

The technical solution of the present application utilizes the existing interface to transmit the user ID, thereby solving the problem that the AF network element cannot obtain the user ID in some scenarios, resulting in the inability to perform service control based on the user ID, and the implementation method is simple and efficient.

Description of drawings

FIG. 1 is a schematic diagram of an existing PCC system architecture;

Fig. 2 is a schematic flow chart of acquiring a user ID provided by the present invention;

Fig. 3 is a schematic flow diagram of obtaining a user ID when an AF session is established according to the present invention;

Fig. 4 is another schematic flow diagram of obtaining a user ID when an AF session is established according to the present invention;

Fig. 5 is a schematic flow diagram of obtaining a user ID when an AF session is updated provided by the present invention;

Fig. 6 is a schematic flow chart of obtaining a user ID when an AF session ends according to the present invention.

detailed description

In order to make the purpose, technical solution and advantages of the present invention clearer, the technical solution of the present invention will be further described in detail below in conjunction with the accompanying drawings. It should be noted that, in the case of no conflict, the embodiments of the present application and the features in the embodiments can be combined with each other arbitrarily.

Example 1

This embodiment provides a method for obtaining a user ID, as shown in Figure 2, which mainly includes the following operations:

Step 201, when the PCRF receives the request message sent by the AF, it parses the request message;

Step 202, if the PCRF obtains an indication that the AF requests to obtain the user ID from the request message, then construct the response message of the request message to carry the user ID obtained by the AF request;

In step 203, the PCRF feeds back the constructed response message to the AF.

Wherein, the request messages involved in this embodiment at least include but not limited to AAR and STR messages.

The following is a detailed introduction to the specific implementation of the above method in combination with specific application scenarios and accompanying drawings:

scene one

FIG. 3 is a schematic flow diagram of obtaining a user ID when a session is established. The process includes the following operations:

Step 301, PCEF sends an IP-CAN session establishment instruction message to PCRF, which carries the user identifier, and PCRF obtains the user's subscription information from SPR, makes a rule decision, and sends a session establishment response message to PCEF, and PCRF and PCEF complete the establishment of IP-CAN CAN session, and save IP-CAN session information and user information on PCRF.

In step 302, the AF network element needs to create a new AF session upon receiving an external or internal event trigger. When creating an AF session, the AF network element detects that there is no user ID associated with the session. In order to obtain the user ID, the AVP requesting to obtain the user ID is included when constructing the request message.

Wherein, in this embodiment, when constructing the request message, a newly added AVP is used to carry an indication that the AF requests to obtain the user ID. That is, when the value of the setting field AVP is a set value, it is considered that the request message includes an indication that the AF requests to obtain the user ID.

In step 303, the AF network element sends an AAR request message to the PCRF, requesting to establish an AF session, which carries an AVP requesting to obtain a user ID.

Step 304: After receiving the session establishment request message from the AF, the PCRF decodes the AAR message, and takes out the AVP requesting to obtain the user ID, and then executes subsequent procedures.

In step 305, the PCRF performs session binding and PCC rule authorization according to the session information and media information carried in the AAR message. After the session is bound, the PCRF obtains the associated user ID from the IP-CAN session bound to the AF session.

Step 306 , PCRF obtains the user identity AVP according to the request carried in the AAR request message, and includes the user identity when constructing the session establishment response message.

In step 307, the PCRF sends a session establishment response message to the AF, which carries the user identifier. After receiving the response message, the AF decodes and obtains the user identifier.

Step 308, the PCRF performs re-decision according to the AF session information and other information, and modifies the IP-CAN session.

In some preferred solutions, if the PCRF does not obtain the indication that the AF requests to obtain the user ID from the request message, it can also judge whether the AF network element needs to obtain the user ID from the PCRF according to the configuration of the AF adjacent office. Only when the AF network element needs to obtain the user ID from the PCRF, the PCRF carries the user ID requested by the AF in the response message of the construction request message. For the specific implementation of this preferred solution, refer to the description of the second scenario below.

scene two

Fig. 4 is a schematic flow diagram of another process for obtaining a user ID when a session is established. The process includes the following operations:

Step 401, PCEF sends an IP-CAN session establishment indication message to PCRF, which carries the user identifier, and PCRF obtains the user's subscription information from SPR, makes a rule decision, and sends a session establishment response message to PCEF, and PCRF and PCEF complete the establishment of IP-CAN CAN session, and save IP-CAN session information and user information on PCRF.

In step 402, the AF network element needs to create a new AF session upon receiving an external or internal event trigger. When constructing the request message, the AVP requesting to obtain the user ID is not included (that is, the indication that the AF requests to obtain the user ID is not included).

Step 403, the AF network element sends an AAR request message to the PCRF, requesting to establish an AF session.

Step 404 , after receiving the session establishment request message from the AF, the PCRF decodes the AAR message, and finds out no AVP requesting to acquire the user ID, and then executes subsequent procedures.

In step 405, the PCRF performs session binding and PCC rule authorization according to the session information and media information carried in the AAR message. After the session is bound, the PCRF obtains the associated user ID from the IP-CAN session bound to the AF session.

Step 406, the PCRF reads the configuration of the AF adjacent office, and judges that the AF network element needs to obtain the user ID from the PCRF. The premise of this step is that the PCRF network element configures the AF adjacent office to need to obtain the user ID from the PCRF.

Step 407, according to the configuration, the AF network element needs to obtain the user ID, so when constructing the response message, the user ID of the AF binding session is included.

In step 408, the PCRF sends a session establishment response message to the AF, which carries the user identifier. After receiving the response message, the AF decodes and obtains the user identifier.

Step 409, the PCRF performs re-decision according to the AF session information and other information, and modifies the IP-CAN session.

scene three

Fig. 5 is a schematic flow chart of obtaining a user ID when a session is modified. The process includes the following operations:

Step 501, the AF network element receives an external or internal event trigger, and needs to modify an existing AF session. When modifying an AF session, the AF network element detects that there is no user ID associated with the session, and needs to obtain the user ID for service control. In order to obtain the user ID, the AVP requesting to obtain the user ID is included when constructing the request message.

In step 502, the AF network element sends an AAR request message to the PCRF, requesting to modify the AF session, which carries an AVP requesting to obtain the user ID (ie, an indication that the AF requests to obtain the user ID).

Step 503: After receiving the session modification request message from the AF, the PCRF decodes the AAR message, and takes out the AVP requesting to obtain the user ID, and then executes the subsequent process.

Step 504 , the PCRF obtains the associated user identifier from the IP-CAN session bound to the AF session according to the session information carried in the AAR message, and updates the saved AF session.

Step 505 , the PCRF obtains the user identity AVP according to the request carried in the AAR request message, and includes the user identity when constructing the session modification response message.

In step 506, the PCRF sends a session modification response message to the AF, which carries the user identifier. After receiving the response message, the AF decodes and obtains the user identifier.

Step 507, the PCRF performs re-decision according to the new AF session information and other information, and modifies the IP-CAN session.

scene four

FIG. 6 is a schematic flow diagram of obtaining a user ID when a session is released. The process includes the following operations:

In step 601, the AF network element needs to release the existing AF session upon receiving an external or internal event trigger. When releasing the AF session, the AF network element detects that there is no user ID associated with the session, and needs to acquire the user ID for service control. In order to obtain the user ID, an AVP requesting to obtain the user ID (an indication that the AF requests to obtain the user ID) is included when constructing the request message.

In step 602, the AF network element sends a STR request message to the PCRF, requesting to release the AF session, which carries an AVP requesting to obtain the user ID.

Step 603: After receiving the session release request message from the AF, the PCRF decodes the STR message, and takes out the AVP requesting to obtain the user ID, and then executes subsequent procedures.

Step 604: According to the session information carried in the request message, the PCRF obtains the associated user ID from the IP-CAN session bound to the AF session, and deletes the saved AF session.

Step 605, PCRF obtains the user identity AVP according to the request carried in the request message, and includes the user identity when constructing the session termination response message.

In step 606, the PCRF sends a session termination response message to the AF, which carries the user identifier. After receiving the response message, the AF decodes and obtains the user identifier.

Step 607, the PCRF executes a re-decision to modify the IP-CAN session.

Specifically, this embodiment can extend the AAR message, add an AVP at the message layer, and use it for the AF request to obtain the user ID, and instruct the PCRF to carry the user ID and Its type is defined as Subscription-Id-Request, and its type is an enumeration. The specific values are as follows:

DISABLE(0), the value used to indicate that the user ID is not obtained. is the default value.

ENABLE (1), the value is used to indicate to obtain the user ID (that is, the set value).

The AVP may also not be carried in the message, indicating that it does not explicitly indicate to obtain the user ID, and the PCRF decides whether to carry the user ID in the response message.

For the AAR message format, refer to 3GPPTS29.214.

<AA-Request>::=<DiameterHeader:265,REQ,PXY>

<Session-Id>

...

[Subscription-Id-Request]

*[AVP]

It is also possible to extend the AAA message by adding Subscription-Id at the message layer to carry the user ID and type. For the format of the AAA message, refer to 3GPPTS29.214, and for the definition of Subscription-Id, refer to RFC4006.

<AA-Answer>::=<DiameterHeader:265,PXY>

<Session-Id>

...

*[Subscription-Id]

*[AVP]

It is also possible to extend the STR message, add Subscription-Id-Request at the message layer, and use it for AF to request to obtain the user ID, and instruct PCRF to carry the user ID and its type in the STA (Session-Termination-Answer, session termination response) response message , the definition is consistent with the Subscription-Id-Request in the AAR message of the present invention. For the STR message format, refer to 3GPPTS29.214.

<ST-Request>::=<DiameterHeader:275,REQ,PXY>

<Session-Id>

...

[Subscription-Id-Request]

*[AVP]

It is also possible to extend the STA message and add Subscription-Id at the message layer to carry the user identifier and type. For the format of the STA message, refer to 3GPPTS29.214, and for the definition of Subscription-Id, refer to RFC4006.

<ST-Answer>::=<DiameterHeader:275,PXY>

<Session-Id>

...

*[Subscription-Id]

*[AVP]

Example 2

This embodiment provides a network side device, which may be a PCRF device, which at least includes the following units.

The parsing unit parses the request message when receiving the request message sent by the AF;

Specifically, the parsing unit parses the request message to obtain the indication that the AF requests to obtain the user ID, and may parse the request message to obtain the value of the set field as a set value.

Wherein, the request message sent by the AF involved in this embodiment at least includes but not limited to AAR and STR messages.

The response message construction unit, when the parsing unit parses from the request message to obtain the indication of the AF request to obtain the user ID, carries the user ID obtained by the AF request in the response message of the construction request message;

Preferably, when the response message construction unit does not obtain the information that the AF requests to obtain the user identification from the request message, it can also judge whether the AF network element needs to obtain the user identification from the PCRF according to the configuration of the AF adjacent office; only when the AF network element needs to obtain the user identification from the PCRF When acquiring the user ID, the response message constructing unit only carries the user ID acquired by the AF request in the response message to construct the request message.

The sending unit feeds back the response message constructed by the response message construction unit to the AF.

It should be noted that since the device provided in this embodiment can implement the method in Embodiment 1 above, other detailed operations can refer to the corresponding content in Embodiment 1, which will not be repeated here.

It can be seen from the above embodiments that in the technical solution of the present application, the AF sends a request message to the PCRF, and the PCRF sends the user identification to the AF through a corresponding message according to the content of the request message and/or local configuration, thereby solving the problem existing in the prior art In some scenarios, the AF network element cannot obtain the problem and defect of the user ID, and the AF can normally perform the service control based on the user ID in the above-mentioned scenarios.

Those skilled in the art can understand that all or part of the steps in the above method can be completed by instructing relevant hardware through a program, and the program can be stored in a computer-readable storage medium, such as a read-only memory, a magnetic disk or an optical disk, and the like. Optionally, all or part of the steps in the foregoing embodiments may also be implemented using one or more integrated circuits. Correspondingly, each module/unit in the foregoing embodiments may be implemented in the form of hardware, or may be implemented in the form of software function modules. This application is not limited to any specific form of combination of hardware and software.

The above descriptions are only preferred examples of the present invention, and are not intended to limit the protection scope of the present invention. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present invention shall be included within the protection scope of the present invention.

Claims (9)

1. obtain a method for user ID, it is characterized in that, comprise following operation:

When strategy and charging controlled entity PCRF receive the request message of Application Function AF transmission, resolve described request message;

If described PCRF resolves the instruction obtaining AF acquisition request user ID from described request message, then, in the response message of structure described request message, carry the user ID of AF acquisition request;

Constructed response message is fed back to described AF by described PCRF.

2. the method for claim 1, is characterized in that, described request message at least comprises authentication authorization request AAR and session termination request STR message.

3. the method for claim 1, is characterized in that, the method also comprises:

When described PCRF does not have parsing to obtain the instruction of AF acquisition request user ID from described request message, described PCRF then adjoins AF network element described in office's configuration determination according to AF and obtains user ID the need of from PCRF;

When AF network element needs to obtain user ID from PCRF, described PCRF, in the response message of structure described request message, carries the user ID of AF acquisition request.

4. the method as described in any one of claims 1 to 3, is characterized in that, described PCRF resolves the instruction obtaining AF acquisition request user ID and refers to from described request message:

It is set point that described PCRF resolves the value obtaining setting field from described request message, judges that described AF request obtains user ID from this PCRF.

5. a network equipment, is characterized in that, comprising:

Resolution unit, when receiving the request message that Application Function AF sends, resolves described request message;

Response message structural unit, when described resolution unit resolves the instruction obtaining AF acquisition request user ID from described request message, in the response message of structure described request message, carries the user ID of AF acquisition request;

Transmitting element, feeds back to described AF by the response message of described response message structural unit structure.

6. equipment as claimed in claim 5, it is characterized in that, described request message at least comprises authentication authorization request AAR and session termination request STR message.

7. equipment as claimed in claim 5, is characterized in that,

If described response message structural unit does not have to resolve the instruction obtaining AF acquisition request user ID from described request message, then adjoin AF network element described in office's configuration determination according to AF and obtain user ID the need of from PCRF;

When AF network element needs to obtain user ID from PCRF, in the response message of structure described request message, carry the user ID of AF acquisition request.

8. the equipment as described in any one of claim 5 to 7, is characterized in that, described resolution unit is resolved the instruction obtaining AF acquisition request user ID and referred to from described request message:

It is set point that described resolution unit resolves the value obtaining setting field from described request message, then judge that described AF request obtains user ID from this equipment.

9. equipment as claimed in claim 8, is characterized in that, described network equipment is strategy and charging control PCRF equipment.