WO2016070556A1 - 一种获取用户标识的方法及网络侧设备 - Google Patents

一种获取用户标识的方法及网络侧设备 Download PDF

Info

Publication number
WO2016070556A1
WO2016070556A1 PCT/CN2015/075406 CN2015075406W WO2016070556A1 WO 2016070556 A1 WO2016070556 A1 WO 2016070556A1 CN 2015075406 W CN2015075406 W CN 2015075406W WO 2016070556 A1 WO2016070556 A1 WO 2016070556A1
Authority
WO
WIPO (PCT)
Prior art keywords
request
user identifier
pcrf
message
request message
Prior art date
Application number
PCT/CN2015/075406
Other languages
English (en)
French (fr)
Inventor
王长春
陈刚
姜志诚
赵莉
严晓飞
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2016070556A1 publication Critical patent/WO2016070556A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40—Network security protocols

Definitions

  • This document relates to the technology of the application function (AF). It is an implementation scheme for the AF to obtain the user ID in the scenario where the user identification is not available in the PCC (Policy and Charging Control) architecture.
  • PCC Policy and Charging Control
  • PCRF Policy and Charging Rule Function
  • PCEF Policy and Charging Enforcement Function
  • BBERF Bit Binding and Event Reporting Function
  • AF Application Function
  • TDF Traffic Detection Function
  • SPR Subscription Profile Repository
  • OFCS Offline charging system
  • OCS Online charging system
  • the PCRF is responsible for the formulation of the policy and accounting rules.
  • the PCC policy and the accounting rules are sent to the PCEF through the Gx interface.
  • the PCEF installs and executes the PCC policy, reports related events, and exchanges accounting information with the charging system.
  • the PCRF sends the QoS (Quality of Service) rules to the BBERF through the Gxx interface.
  • the BBERF does not exchange accounting information with the accounting system. It is only responsible for reporting bearer bindings and related events.
  • the PCRF sends the service information to be monitored to the TDF through the Sd interface.
  • 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 saves the service information that the user subscribes to.
  • the PCRF can query the SPR for the service information subscribed 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.
  • the TDF sends the service-based online charging information to the OCS through the Gyn interface, and sends the service-based offline charging information to the OFCS through the Gz n interface.
  • IP-CAN IP Connectivity Access Network, IP connection
  • the access network maintains the connection state with each other, and the AF and the PCRF maintain the connection state with each other through the AF session.
  • the PCEF sends an indication of establishing, updating, and releasing an IP-CAN session to the PCRF through a CCR (Credit-Control-Request) message; the AF sends an establishment and update of the AF session to the PCRF through an AAR (Authentication-Authorization-Request) message.
  • the indication of the release of the AF session is sent to the PCRF by the STR (Session-Termination-Request).
  • the PCRF formulates a dynamic PCC policy based on the service-related information provided by the AF, the bearer-related information reported by the PCEF, and the service information subscribed by the user in the SPR, and sends the policy to the PCEF.
  • the policy information includes QoS and charging information.
  • the AF can provide dynamic policy and charging control for services.
  • the AF may be a P-CSCF (Proxy-Call Session Control Function) in an IMS (IP Multimedia System) network, or may be a third-party application platform.
  • the third-party application platform is used as the AF network element, which is limited by the network deployment and cannot obtain the user identifier. Therefore, the service control based on the user identifier cannot be performed, for example, the charging purpose based on the user identifier.
  • a method for obtaining a user identifier including the following operations:
  • the policy and charging control entity PCRF parses the request message when receiving the request message sent by the application function entity AF;
  • the response message that constructs the request message carries the user identifier acquired by the AF request;
  • the PCRF feeds back the constructed response message to the AF.
  • the request message includes at least an authentication authorization request AAR or a session termination request STR message.
  • the foregoing method further includes:
  • the PCRF determines, according to the AF neighboring office configuration, whether the AF network element needs to acquire the user identifier from the PCRF;
  • the PCRF determines that the AF network element needs to obtain the user identifier from the PCRF, the PCRF carries the user identifier acquired by the AF request in the response message that constructs the request message.
  • the PCRF parses, from the request message, an indication that the AF request acquires the user identifier, including:
  • the PCRF parses the value of the acquisition setting field from the request message to a set value, and determines that the AF request acquires a user identifier from the PCRF.
  • a network side device including:
  • a parsing unit configured to parse the request message when receiving the request message sent by the application function entity AF;
  • a response message construction unit configured to: when the parsing unit parses the AF request to obtain an indication of the user identifier from the request message, in the response message constructing the request message, carrying the user identifier acquired by the AF request;
  • a sending unit configured to feed back a response message constructed by the response message construction unit to the AF.
  • the request message includes at least an authentication authorization request AAR or a session termination request STR message.
  • the response message constructing unit is further configured to determine, according to the AF neighboring office configuration, whether the AF network element needs to be obtained from the request message if the AF request is obtained from the request message.
  • the PCRF obtains the user identifier
  • the response message constructing unit determines that the AF network element needs to obtain the user identifier from the PCRF, the response message that constructs the request message carries the user identifier acquired by the AF request.
  • the parsing unit parses the indication that the AF request for obtaining the user identifier is obtained from the request message, and includes:
  • the parsing unit parses the value of the acquisition setting field from the request message to a set value, and determines that the AF request acquires the user identifier from the local device.
  • the network side device is a policy and charging control PCRF device.
  • the embodiment of the invention further provides a computer readable storage medium storing program instructions, which can be implemented when the program instructions are executed.
  • the technical solution of the embodiment of the present invention uses the existing interface to transmit the user identifier, thereby solving the problem that the AF network element cannot obtain the user identifier in some scenarios and cannot perform service control based on the user identifier, and the implementation manner is simple and efficient.
  • FIG. 1 is a schematic diagram of a related art PCC system architecture
  • FIG. 2 is a schematic flowchart of obtaining a user identifier according to an embodiment of the present invention
  • FIG. 3 is a schematic flowchart of obtaining a user identifier when an AF session is established according to an embodiment of the present invention
  • FIG. 4 is another schematic flowchart of obtaining a user identifier when an AF session is established according to an embodiment of the present invention
  • FIG. 5 is a schematic flowchart of obtaining a user identifier when an AF session is updated according to an embodiment of the present invention
  • FIG. 6 is a schematic flowchart of obtaining a user identifier when an AF session ends according to an embodiment of the present invention
  • FIG. 7 is a schematic structural diagram of a network side device according to an embodiment of the present invention.
  • the PCRF holds the user identity associated with the session.
  • the AF will be bound to the IP-CAN session when the session is created. After the session is bound, the AF can obtain the user ID associated with the session. How the PCRF sends the associated user identifier to the AF through the Rx interface can be implemented by the following embodiments.
  • This embodiment provides a method for obtaining a user identifier, as shown in FIG. 2, which mainly includes the following operations:
  • Step 201 The PCRF receives the request message sent by the AF, and parses the request message.
  • Step 202 If the PCRF parses the request from the request message to obtain the AF request for obtaining the user identifier, the response message that constructs the request message carries the user identifier acquired by the AF request.
  • step 203 the PCRF feeds back the constructed response message to the AF.
  • the request message related to this embodiment includes at least but not limited to an AAR or STR message.
  • Figure 3 is a schematic diagram of the process of obtaining a user identifier when a session is established.
  • the process includes the following operations:
  • Step 301 The PCEF sends an IP-CAN (IP Connection Access Network) session establishment indication message to the PCRF, where the user identifier is carried, and the PCRF obtains the subscription information of the user from the SPR, and performs a rule decision, and sends a session establishment response message to the PCEF.
  • IP-CAN IP Connection Access Network
  • the PCRF and the PCEF complete the creation of the IP-CAN session, and save the IP-CAN session information and user information on the PCRF;
  • Step 302 When the AF network element receives an external or internal event, a new AF session needs to be created.
  • the AF network element detects that there is no user identifier associated with the session.
  • the request message includes an indication (AVP) requesting to obtain a user identifier;
  • an AVP is added to carry an AF request to obtain an indication of the user identifier. That is, when the value of the setting field AVP is the set value, it is considered that the request message includes an indication that the AF request acquires the user identifier.
  • Step 303 The AF network element sends an AAR request message to the PCRF, requesting to establish an AF session, where the AVP is requested to obtain the user identifier.
  • Step 304 After receiving the establishment session request message of the AF, the PCRF decodes the AAR message, and takes out the AVP requesting to obtain the user identifier, and then performs a subsequent process;
  • Step 305 The PCRF performs session binding and PCC rule authorization according to the session information and the media information carried in the AAR message. After the session is bound, the PCRF is an IP-CAN session bound from the AF session. Get the associated user ID in the middle;
  • Step 306 The PCRF obtains the user identifier AVP according to the request carried in the AAR request message, and includes the user identifier when constructing the session establishment response message.
  • Step 307 The PCRF sends a session establishment response message to the AF, where the user identifier is carried, and after receiving the response message, the AF decodes and obtains the user identifier.
  • Step 308 The PCRF performs a re-decision according to the AF session information and other information, and modifies the IP-CAN session.
  • the PCRF can determine whether the AF network element needs to obtain the user identifier from the PCRF according to the configuration of the AF neighboring office if the AFF does not obtain the indication of the AF request to obtain the user identifier.
  • the PCRF carries the user identifier acquired by the AF request in the response message of the configuration request message only when the AF network element needs to obtain the user identifier from the PCRF. See the description of scenario 2 below.
  • FIG. 4 is another schematic flowchart of obtaining a user identifier when a session is established. The process includes the following operations:
  • Step 401 The PCEF sends an IP-CAN session establishment indication message to the PCRF, where the user identifier is carried, the PCRF obtains the subscription information of the user from the SPR, and performs a rule decision, and sends a session establishment response message to the PCEF, and the PCRF and the PCEF complete the creation of the IP- CAN session and save IP-CAN session information and user information on the PCRF;
  • Step 402 The AF network element receives an external or internal event trigger, and needs to create a new AF session.
  • the AVP that requests the acquisition of the user identifier is not included in the configuration request message (ie, the indication that the AF request is not included to obtain the user identifier);
  • Step 403 The AF network element sends an AAR request message to the PCRF to request to establish an AF session.
  • Step 404 After receiving the establishment session request message of the AF, the PCRF decodes the AAR message, does not parse the AVP requesting to obtain the user identifier, and then performs a subsequent process;
  • Step 405 The PCRF performs session binding and PCC rule authorization according to the session information and the media information carried in the AAR message. After the session is bound, the PCRF is an IP-CAN session bound from the AF session. Get the associated user ID in the middle;
  • Step 406 The PCRF reads the AF neighboring office configuration, and determines that the AF network element needs to obtain the user identifier from the PCRF.
  • the premise of the step is that the PCRF network element configures the AF neighboring office to obtain the user identifier from the PCRF.
  • Step 407 According to the configuration, the AF network element needs to obtain the user identifier, so when constructing the response message, the user identifier of the AF binding session is included;
  • Step 408 The PCRF sends a session establishment response message to the AF, where the user identifier is carried. After receiving the response message, the AF decodes and obtains the user identifier.
  • Step 409 The PCRF performs a re-decision according to the AF session information and other information, and modifies the IP-CAN session.
  • FIG. 5 is a schematic flowchart of obtaining a user identifier when a session is modified. The process includes the following operations:
  • Step 501 The AF network element is triggered by an external or internal event, and the existing AF session needs to be modified.
  • the AF network element detects that there is no user identifier associated with the session, and needs to obtain the user identifier for service control.
  • the AVP requesting the user identifier is included in the construction request message;
  • Step 502 The AF network element sends an AAR request message to the PCRF, requesting to modify the AF session, where the AVP is requested to obtain the user identifier (that is, the AF request to obtain the user identifier).
  • Step 503 After receiving the modification session request message of the AF, the PCRF decodes the AAR message, and takes out the AVP requesting to obtain the user identifier, and then performs a 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 identifier AVP according to the request carried in the AAR request message, and includes the user identifier when constructing the session modification response message.
  • Step 506 The PCRF sends a session modification response message to the AF, where the user identifier is carried. After receiving the response message, the AF decodes and obtains the user identifier.
  • Step 507 The PCRF performs a re-decision according to the new AF session information and other information, and modifies the IP-CAN session.
  • Figure 6 is a schematic diagram of the process of obtaining a user identifier when the session is released. The process includes the following operations:
  • Step 601 The AF network element receives an external or internal event, and needs to release the existing AF session.
  • the AF network element detects that there is no user identifier associated with the session, and needs to obtain the user identifier for service control.
  • the AVP that requests the acquisition of the user identifier is included in the construction request message (the AF request to obtain the indication of the user identifier);
  • Step 602 The AF network element sends an STR request message to the PCRF, requesting to release the AF session, where the AVP is requested to obtain the user identifier.
  • Step 603 After receiving the release session request message of the AF, the PCRF decodes the STR message, and takes out the AVP requesting to obtain the user identifier, and then performs a subsequent process;
  • Step 604 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 request message, and deletes the saved AF session.
  • Step 605 The PCRF obtains the user identifier AVP according to the request carried in the request message, and includes the user identifier when constructing the session termination response message.
  • Step 606 The PCRF sends a session termination response message to the AF, where the user identifier is carried. After receiving the response message, the AF decodes and obtains the user identifier.
  • Step 607 The PCRF performs a re-decision and modifies the IP-CAN session.
  • the AAR message may be extended, and an AVP is added to the message layer for the AF request to obtain the user identifier, and the PCRF is configured to carry the user identifier and its type in the AAA (Authentication-Authorization-Answer) response message.
  • the definition is: Subscription-Id-Request, the type is an enumeration, and the specific values are as follows:
  • this value is used to indicate the acquisition of the user ID (that is, the set value).
  • the AVP may also be not carried in the message, indicating that the user identifier is not explicitly indicated, and the PCRF determines whether the user identifier is carried in the response message.
  • the AAR message format is described in 3GPP TS 29.214.
  • the AAA message may also be extended, and a subscription-Id is added at the message layer to carry the user identifier and type.
  • a subscription-Id is added at the message layer to carry the user identifier and type.
  • For the AAA message format refer to 3GPP TS 29.214.
  • the STR message may also be extended, and a subscription-Id-Request is added to the message layer for the AF request to obtain the user identifier, and the PCRF is configured to carry the user identifier and its type in the STA (Session-Termination-Answer) response message.
  • STA Session-Termination-Answer
  • the definition is consistent with the Subscription-Id-Request in the AAR message in this article.
  • the STR message format is described in 3GPP TS 29.214.
  • the STA message may also be extended, and a subscription-Id is added at the message layer to carry the user identifier and type.
  • a subscription-Id is added at the message layer to carry the user identifier and type.
  • STA message format refer to 3GPP TS 29.214.
  • Subscription-Id refer to RFC 4006.
  • the embodiment provides a network side device, which may be a PCRF device. As shown in FIG. 7, it includes at least a parsing unit 701, a response message constructing unit 702, and a sending unit 703, where:
  • the parsing unit 701 is configured to parse the request message when receiving the request message sent by the AF;
  • the parsing unit 701 parses the AF request to obtain an indication of the user identifier from the request message, and may determine that the value of the setting field is a set value from the request message.
  • the request message for AF transmission includes at least but not limited to an AAR or STR message.
  • the response message construction unit 702 is configured to: when the parsing unit 701 parses the AF request to obtain the user identifier from the request message, the response message of the configuration request message carries the user identifier acquired by the AF request;
  • the response message constructing unit 702 may not determine whether the AF network element needs to obtain the user identifier from the PCRF according to the AF neighboring office configuration, if the AF network element needs to be obtained from the request message.
  • the response message constructing unit 702 carries the user identifier acquired by the AF request in the response message constructing the request message.
  • the sending unit 703 is configured to feed back a response message constructed by the response message constructing unit 702 to the AF.
  • the device provided in this embodiment can implement the method in the foregoing Embodiment 1, and other detailed operations may be referred to the corresponding content in Embodiment 1, and details are not described herein again.
  • the technical solution of the present application sends a request message to the PCRF through the AF, and the PCRF sends the user identifier to the AF according to the content of the request message and/or the local configuration, so as to solve the part existing in the related technology.
  • the AF network element in the scenario cannot obtain the problem and defect of the user ID.
  • the AF can perform the service control based on the user ID in the scenario.
  • the solution of the embodiment of the present invention uses the existing interface to transmit the user identifier, thereby solving the problem that the AF network element cannot obtain the user identifier in some scenarios and cannot perform service control based on the user identifier, and the implementation manner is simple and efficient.

Abstract

一种获取用户标识的方法及网络侧设备，所述方法包括：PCRF收到AF发送的请求消息时，解析请求消息；若PCRF从请求消息中解析得到AF请求获取用户标识的指示，则在构造请求消息的响应消息中，携带AF请求获取的用户标识；PCRF将所构造的响应消息反馈给AF。所述设备包括：解析单元、响应消息构造单元和发送单元。

Description

一种获取用户标识的方法及网络侧设备 技术领域
本文涉及AF(Application Function，应用功能)的技术，是一种PCC(Policy and Charging Control，策略和计费控制)架构中在无法获取用户标识场景下AF获取用户标识的实现方案。
背景技术
在PCC架构网络中，如图1所示，存在几个主要的功能实体：PCRF(Policy and Charging Rule Function，策略和计费规则功能)、PCEF(Policy and Charging Enforcement Function，策略和计费执行功能)、BBERF(Bearer Binding and Event Reporting Function，承载绑定和事件上报功能)、AF(Application Function，应用功能)、TDF(Traffic Detection Function，业务检测功能)、SPR(Subscription Profile Repository，用户签约数据库)、OFCS(Offline charging system，离线计费系统)、OCS(Online charging system，在线计费系统)。
PCRF主要负责策略和计费规则的制定，通过Gx接口将制定的PCC策略和计费规则下发给PCEF，PCEF安装、执行PCC策略，并上报相关事件，与计费系统交互计费信息。PCRF通过Gxx接口将QoS(Quality of Service，业务服务质量)规则下发给BBERF，BBERF不和计费系统交互计费信息，只负责承载绑定和相关事件的上报。PCRF通过Sd接口把需要监控的业务信息下发给TDF，TDF执行业务监控，并上报给PCRF。AF通过Rx接口向PCRF提供业务信息。SPR保存了用户签约的业务信息，PCRF可以通过Sp接口向SPR查询用户签约的业务信息。OCS通过Sy接口向PCRF报告与用户消费相关的策略计数器状态信息。PCEF通过Gy接口将在线计费信息发送给OCS进行在线计费的统计，通过Gz接口将离线计费信息发送给OFCS。TDF通过Gyn接口将基于业务的在线计费信息发送给OCS，通过Gz n接口将基于业务的离线计费信息发送给OFCS。
PCEF和PCRF之间通过IP-CAN(IP Connectivity Access Network，IP连 接接入网)会话互相维持连接状态，AF和PCRF之间通过AF会话互相维持连接状态。PCEF通过CCR(Credit-Control-Request)消息向PCRF发送建立、更新、释放IP-CAN会话的指示；AF则通过AAR(Authentication-Authorization-Request，认证授权请求)消息向PCRF发送建立、更新AF会话的指示，通过STR(Session-Termination-Request，会话终止请求)向PCRF发送释放AF会话的指示。
PCRF根据AF提供的业务相关信息、PCEF上报的承载相关信息以及SPR中用户签约的业务信息，制定动态PCC策略，并下发给PCEF，策略信息中包含QoS和计费的信息。
AF可以提供业务的动态策略和计费控制。AF可以是IMS(IP Multimedia System，IP多媒体子系统)网络中的P-CSCF(Proxy-Call Session Control Function，代理呼叫会话控制功能)，也可以是一个第三方应用平台。在某些场景时，第三方应用平台作为AF网元，受限于网络部署而无法获取到用户标识，从而不能执行基于用户标识的业务控制，比如基于用户标识的计费目的。
发明内容
一种获取用户标识的方法及网络侧设备，以解决第三方应用平台作为AF时，AF网元无法获取到用户标识的问题和缺陷。
一种获取用户标识的方法，包括以下操作：
策略和计费控制实体PCRF收到应用功能实体AF发送的请求消息时，解析所述请求消息；
若所述PCRF从所述请求消息中解析得到AF请求获取用户标识的指示，则在构造所述请求消息的响应消息中，携带AF请求获取的用户标识；
所述PCRF将所构造的响应消息反馈给所述AF。
可选地，上述方法中，所述请求消息至少包括认证授权请求AAR或会话终止请求STR消息。
可选地，上述方法还包括：
当所述PCRF从所述请求消息中没有解析得到AF请求获取用户标识的指示时，所述PCRF则根据AF邻接局配置判断所述AF网元是否需要从PCRF获取用户标识；
当所述PCRF判断所述AF网元需要从PCRF获取用户标识时，所述PCRF在构造所述请求消息的响应消息中，携带AF请求获取的用户标识。
可选地，上述方法中，所述PCRF从所述请求消息中解析得到AF请求获取用户标识的指示，包括：
所述PCRF从所述请求消息中解析获取设定字段的值为设定值，判定所述AF请求从本PCRF中获取用户标识。
一种网络侧设备，包括：
解析单元，设置为在收到应用功能实体AF发送的请求消息时，解析所述请求消息；
响应消息构造单元，设置为在所述解析单元从所述请求消息中解析得到AF请求获取用户标识的指示时，在构造所述请求消息的响应消息中，携带AF请求获取的用户标识；以及
发送单元，设置为将所述响应消息构造单元构造的响应消息反馈给所述AF。
可选地，上述设备中，所述请求消息至少包括认证授权请求AAR或会话终止请求STR消息。
可选地，上述设备中，所述响应消息构造单元还设置为从所述请求消息中如果没有解析得到AF请求获取用户标识的指示，则根据AF邻接局配置判断所述AF网元是否需要从PCRF获取用户标识；
当所述响应消息构造单元判断所述AF网元需要从PCRF获取用户标识时，在构造所述请求消息的响应消息中，携带AF请求获取的用户标识。
可选地，上述设备中，所述解析单元从所述请求消息中解析得到AF请求获取用户标识的指示，包括：
所述解析单元从所述请求消息中解析获取设定字段的值为设定值，则判定所述AF请求从本设备中获取用户标识。
可选地，上述设备中，所述网络侧设备为策略和计费控制PCRF设备。
本发明实施例还提供一种计算机可读存储介质，存储有程序指令，当该程序指令被执行时可实现上述方法。
本发明实施例技术方案利用现有接口传输用户标识，从而解决了部分场景下AF网元无法获取到用户标识造成无法基于用户标识进行业务控制的问题，且实现方式简单高效。
附图概述
图1是相关技术PCC系统架构示意图；
图2是本发明实施例的获取用户标识的流程示意图；
图3是本发明实施例AF会话建立时获取用户标识的流程示意图；
图4是本发明实施例AF会话建立时获取用户标识的另一流程示意图；
图5是本发明实施例AF会话更新时获取用户标识的流程示意图；
图6是本发明实施例AF会话结束时获取用户标识的流程示意图；
图7是本发明实施例网络侧设备的结构示意图。
本发明的实施方式
需要说明的是，在不冲突的情况下，本申请的实施例和实施例中的特征可以任意相互组合。
考虑到PCRF和PCEF之间创建IP-CAN会话，PCRF持有会话关联的用户标识。AF在会话创建时将和IP-CAN会话进行绑定，会话绑定后，AF则可以获取会话关联的用户标识。PCRF如何通过Rx接口，发送关联的用户标识给AF，可以通过以下实施例实现。
实施例1
本实施例提供一种获取用户标识的方法，如图2所示，主要包括以下操作：
步骤201，PCRF收到AF发送的请求消息，解析该请求消息；
步骤202，若PCRF从该请求消息中解析得到AF请求获取用户标识的指示，则在构造该请求消息的响应消息中，携带AF请求获取的用户标识；
步骤203，PCRF将所构造的响应消息反馈给AF。
其中，本实施例所涉及的请求消息至少包括但不限于AAR或STR消息。
下面结合应用场景及附图对上述方法作详细介绍：
场景一
图3所示为会话建立时获取用户标识的流程示意图。该过程包括如下操作：
步骤301、PCEF向PCRF发送IP-CAN(IP连接接入网)会话建立指示消息，其中携带用户标识，PCRF从SPR获取该用户的签约信息，并进行规则决策，发送会话建立响应消息给PCEF，PCRF和PCEF完成创建IP-CAN会话，并在PCRF上保存IP-CAN会话信息和用户信息；
步骤302、当AF网元收到外部或者内部事件触发，需要创建新的AF会话，在创建AF会话时，AF网元检测到没有与该会话关联的用户标识，为了获取到用户标识，在构造请求消息时包含请求获取用户标识的指示(AVP)；
其中，本实施例中，在构造请求消息时采用新增AVP以携带AF请求获取用户标识的指示。即设定字段AVP的取值为设定值时，即认为请求消息中包含了AF请求获取用户标识的指示。
步骤303、AF网元发送AAR请求消息给PCRF，请求建立AF会话，其中携带请求获取用户标识的AVP；
步骤304、PCRF收到AF的建立会话请求消息后，解码AAR消息，并取出请求获取用户标识的AVP，然后执行后续流程；
步骤305、PCRF根据AAR消息携带的会话信息和媒体信息，执行会话绑定和PCC规则授权，会话绑定后，PCRF即从AF会话绑定的IP-CAN会话 中获取到关联的用户标识；
步骤306、PCRF根据AAR请求消息携带的请求获取用户标识AVP，在构造会话建立响应消息时，包含用户标识；
步骤307、PCRF发送会话建立响应消息给AF，其中携带用户标识，AF收到该响应消息后，解码并获取到用户标识；
步骤308、PCRF根据AF会话信息和其他信息执行重决策，修改IP-CAN会话。
还有一些可选方案提出，PCRF如果没有从请求消息中解析得到AF请求获取用户标识的指示，则还可以根据AF邻接局配置判断AF网元是否需要从PCRF获取用户标识。仅当AF网元需要从PCRF获取用户标识时，PCRF在构造请求消息的响应消息中，才携带AF请求获取的用户标识。参见下述场景二的描述。
场景二
图4为会话建立时获取用户标识的另一流程示意图。该过程包括如下操作：
步骤401、PCEF向PCRF发送IP-CAN会话建立指示消息，其中携带用户标识，PCRF从SPR获取该用户的签约信息，并进行规则决策，发送会话建立响应消息给PCEF，PCRF和PCEF完成创建IP-CAN会话，并在PCRF上保存IP-CAN会话信息和用户信息；
步骤402、AF网元收到外部或者内部事件触发，需要创建新的AF会话。在构造请求消息时不包含请求获取用户标识的AVP(即不包含AF请求获取用户标识的指示)；
步骤403、AF网元发送AAR请求消息给PCRF，请求建立AF会话；
步骤404、PCRF收到AF的建立会话请求消息后，解码AAR消息，没有解析出请求获取用户标识的AVP，然后执行后续流程；
步骤405、PCRF根据AAR消息携带的会话信息和媒体信息，执行会话绑定和PCC规则授权，会话绑定后，PCRF即从AF会话绑定的IP-CAN会话 中获取到关联的用户标识；
步骤406、PCRF读取AF邻接局配置，判断AF网元需要从PCRF获取用户标识，该步骤的前提是PCRF网元配置AF邻接局为需要从PCRF获取用户标识；
步骤407、根据配置，AF网元需要获取用户标识，因此在构造响应消息时，包含AF绑定会话的用户标识；
步骤408、PCRF发送会话建立响应消息给AF，其中携带用户标识。AF收到该响应消息后，解码并获取到用户标识；
步骤409、PCRF根据AF会话信息和其他信息执行重决策，修改IP-CAN会话。
场景三
图5为会话修改时获取用户标识的流程示意图。该过程包括如下操作：
步骤501、AF网元收到外部或者内部事件触发，需要修改存在的AF会话；在修改AF会话时，AF网元检测到没有与该会话关联的用户标识，并且需要获取用户标识用于业务控制；为了获取到用户标识，在构造请求消息时包含请求获取用户标识的AVP；
步骤502、AF网元发送AAR请求消息给PCRF，请求修改AF会话，其中携带请求获取用户标识的AVP(即AF请求获取用户标识的指示)；
步骤503、PCRF收到AF的修改会话请求消息后，解码AAR消息，并取出请求获取用户标识的AVP，然后执行后续流程；
步骤504、PCRF根据AAR消息携带的会话信息，从AF会话绑定的IP-CAN会话中获取到关联的用户标识，并更新保存的AF会话；
步骤505、PCRF根据AAR请求消息携带的请求获取用户标识AVP，在构造会话修改响应消息时，包含用户标识；
步骤506、PCRF发送会话修改响应消息给AF，其中携带用户标识。AF收到该响应消息后，解码并获取到用户标识；
步骤507、PCRF根据新的AF会话信息和其他信息执行重决策，修改IP-CAN会话。
场景四
图6所示为会话释放时获取用户标识的流程示意图。该过程包括如下操作：
步骤601、AF网元收到外部或者内部事件触发，需要释放存在的AF会话；在释放AF会话时，AF网元检测到没有与该会话关联的用户标识，并且需要获取用户标识用于业务控制；为了获取到用户标识，在构造请求消息时包含请求获取用户标识的AVP(AF请求获取用户标识的指示)；
步骤602、AF网元发送STR请求消息给PCRF，请求释放AF会话，其中携带请求获取用户标识的AVP；
步骤603、PCRF收到AF的释放会话请求消息后，解码STR消息，并取出请求获取用户标识的AVP，然后执行后续流程；
步骤604、PCRF根据请求消息携带的会话信息，从AF会话绑定的IP-CAN会话中获取到关联的用户标识，并删除保存的AF会话；
步骤605、PCRF根据请求消息携带的请求获取用户标识AVP，在构造会话终止响应消息时，包含用户标识；
步骤606、PCRF发送会话终止响应消息给AF，其中携带用户标识。AF收到该响应消息后，解码并获取到用户标识；
步骤607、PCRF执行重决策，修改IP-CAN会话。
本实施例可以对AAR消息进行扩展，在消息层增加一个AVP，用于AF请求获取用户标识，指示PCRF在AAA(Authentication-Authorization-Answer，认证授权响应)响应消息中携带用户标识及其类型，定义为，Subscription-Id-Request，类型为枚举，具体取值如下：
DISABLE(0)，该值用于指示不获取用户标识。为默认取值。
ENABLE(1)，该值用于指示获取用户标识(即为设定值)。
该AVP也可以不在消息中携带，表示不明确指示获取用户标识，由PCRF决定是否在响应消息中携带用户标识。
AAR消息格式参见3GPP TS 29.214。
<AA-Request>::＝<Diameter Header:265,REQ,PXY>
<Session-Id>
……
[Subscription-Id-Request]
*[AVP]
也可以对AAA消息进行扩展，在消息层增加Subscription-Id，用于携带用户标识及类型，AAA消息格式参见3GPP TS 29.214，Subscription-Id的定义参见RFC 4006。
<AA-Answer>::＝<Diameter Header:265,PXY>
<Session-Id>
……
*[Subscription-Id]
*[AVP]
还可以对STR消息进行扩展，在消息层增加Subscription-Id-Request，用于AF请求获取用户标识，指示PCRF在STA(Session-Termination-Answer，会话终止响应)响应消息中携带用户标识及其类型，定义与本文中AAR消息中的Subscription-Id-Request一致。STR消息格式参见3GPP TS 29.214。
<ST-Request>::＝<Diameter Header:275,REQ,PXY>
<Session-Id>
……
[Subscription-Id-Request]
*[AVP]
还可以对STA消息进行扩展，在消息层增加Subscription-Id，用于携带用户标识及类型，STA消息格式参见3GPP TS 29.214，Subscription-Id的定义参见RFC 4006。
<ST-Answer>::＝<Diameter Header:275,PXY>
<Session-Id>
……
*[Subscription-Id]
*[AVP]
实施例2
本实施例提供一种网络侧设备，可以是PCRF设备，如图7所示，其至少包括解析单元701、响应消息构造单元702和发送单元703，其中：
所述解析单元701，设置为在收到AF发送的请求消息时，解析该请求消息；
解析单元701从请求消息中解析得到AF请求获取用户标识的指示，可以是从请求消息中解析得到设定字段的值为设定值。
其中，本实施例所涉及的AF发送的请求消息至少包括但不限于AAR或STR消息。
所述响应消息构造单元702，设置为在解析单元701从请求消息中解析得到AF请求获取用户标识的指示时，在构造请求消息的响应消息中，携带AF请求获取的用户标识；
可选地，响应消息构造单元702没有从请求消息中解析得到AF请求获取用户标识的信息时，还可以根据AF邻接局配置判断AF网元是否需要从PCRF获取用户标识；仅当AF网元需要从PCRF获取用户标识时，响应消息构造单元702在构造所述请求消息的响应消息中，才携带AF请求获取的用户标识。
所述发送单元703，设置为将响应消息构造单元702构造的响应消息反馈给AF。
要说明的是，由于本实施例提供的设备可以实现上述实施例1的方法，故其他详细操作可以参见实施例1的相应内容，在此不再赘述。
从上述实施例可以看出，本申请技术方案，通过AF发送请求消息给PCRF，PCRF根据请求消息内容和/或本地配置，将用户标识通过相应消息发送给AF，从而解决相关技术中存在的部分场景下AF网元无法获取到用户标识的问题和缺陷，实现所述场景下AF可以正常执行基于用户标识的业务控制。
本领域普通技术人员可以理解上述方法中的全部或部分步骤可通过程序来指令相关硬件完成，所述程序可以存储于计算机可读存储介质中，如只读存储器、磁盘或光盘等。可选地，上述实施例的全部或部分步骤也可以使用一个或多个集成电路来实现。相应地，上述实施例中的各模块/单元可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。
工业实用性
本发明实施例方案利用现有接口传输用户标识，从而解决了部分场景下AF网元无法获取到用户标识造成无法基于用户标识进行业务控制的问题，且实现方式简单高效。

Claims (10)

  1. 一种获取用户标识的方法，包括：
    策略和计费控制实体PCRF收到应用功能实体AF发送的请求消息时，解析所述请求消息；
    若所述PCRF从所述请求消息中解析得到AF请求获取用户标识的指示，则在构造所述请求消息的响应消息中，携带AF请求获取的用户标识；
    所述PCRF将所构造的响应消息反馈给所述AF。
  2. 如权利要求1所述的方法，其中，所述请求消息包括认证授权请求AAR或会话终止请求STR消息。
  3. 如权利要求1所述的方法，该方法还包括：
    当所述PCRF从所述请求消息中没有解析得到AF请求获取用户标识的指示时，所述PCRF则根据AF邻接局配置判断所述AF网元是否需要从PCRF获取用户标识；
    当所述PCRF判断所述AF网元需要从PCRF获取用户标识时，所述PCRF在构造所述请求消息的响应消息中，携带AF请求获取的用户标识。
  4. 如权利要求1至3任一项所述的方法，其中，所述PCRF从所述请求消息中解析得到AF请求获取用户标识的指示，包括：
    所述PCRF从所述请求消息中解析获取设定字段的值为设定值，判定所述AF请求从本PCRF中获取用户标识。
  5. 一种网络侧设备，包括：
    解析单元，设置为在收到应用功能实体AF发送的请求消息时，解析所述请求消息；
    响应消息构造单元，设置为在所述解析单元从所述请求消息中解析得到AF请求获取用户标识的指示时，在构造所述请求消息的响应消息中，携带AF请求获取的用户标识；以及
    发送单元，设置为将所述响应消息构造单元构造的响应消息反馈给所述AF。
  6. 如权利要求5所述的设备，其中，所述请求消息包括认证授权请求AAR或会话终止请求STR消息。
  7. 如权利要求5所述的设备，其中，
    所述响应消息构造单元还设置为从所述请求消息中如果没有解析得到AF请求获取用户标识的指示，则根据AF邻接局配置判断所述AF网元是否需要从PCRF获取用户标识；
    当所述响应消息构造单元判断所述AF网元需要从PCRF获取用户标识时，在构造所述请求消息的响应消息中，携带AF请求获取的用户标识。
  8. 如权利要求5至7任一项所述的设备，其中，所述解析单元从所述请求消息中解析得到AF请求获取用户标识的指示，包括：
    所述解析单元从所述请求消息中解析获取设定字段的值为设定值，则判定所述AF请求从本设备中获取用户标识。
  9. 如权利要求8所述的设备，其中，所述网络侧设备为策略和计费控制PCRF设备。
  10. 一种计算机可读存储介质，存储有程序指令，当该程序指令被执行时可实现权利要求1-4任一项所述的方法。
PCT/CN2015/075406 2014-11-04 2015-03-30 一种获取用户标识的方法及网络侧设备 WO2016070556A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410613953.5 2014-11-04
CN201410613953.5A CN105553923A (zh) 2014-11-04 2014-11-04 一种获取用户标识的方法及网络侧设备

Publications (1)

Publication Number Publication Date
WO2016070556A1 true WO2016070556A1 (zh) 2016-05-12

Family

ID=55832859

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/075406 WO2016070556A1 (zh) 2014-11-04 2015-03-30 一种获取用户标识的方法及网络侧设备

Country Status (2)

Country Link
CN (1) CN105553923A (zh)
WO (1) WO2016070556A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021168829A1 (zh) * 2020-02-28 2021-09-02 华为技术有限公司 一种用户标识的验证方法及相关设备
US11651060B2 (en) 2020-11-18 2023-05-16 International Business Machines Corporation Multi-factor fingerprint authenticator

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101420338A (zh) * 2007-10-26 2009-04-29 华为技术有限公司 Pcc架构中的信息查询方法、装置及系统
CN101459904A (zh) * 2008-06-17 2009-06-17 中兴通讯股份有限公司 Aaa服务器、p-gw、pcrf、用户设备标识的获取方法和系统
CN102045717A (zh) * 2009-10-26 2011-05-04 中国移动通信集团公司 数据业务中获取用户标识的系统、方法及相关设备
CN102695171A (zh) * 2012-05-18 2012-09-26 中国联合网络通信集团有限公司 用户标识获取方法、系统及设备

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101039311B (zh) * 2006-03-16 2010-05-12 华为技术有限公司 一种身份标识网页业务网系统及其鉴权方法
CN101188504A (zh) * 2006-11-20 2008-05-28 华为技术有限公司 一种网络融合策略计费控制架构的系统及处理方法
CN101068148A (zh) * 2007-04-19 2007-11-07 华为技术有限公司 策略和计费控制的方法及装置
CN101867909B (zh) * 2009-04-20 2013-10-16 中兴通讯股份有限公司 一种实现有限策略计费控制的方法及系统
CN101540980B (zh) * 2009-04-24 2012-03-21 华为技术有限公司 业务优先级更新指示方法、业务优先级更新方法及装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101420338A (zh) * 2007-10-26 2009-04-29 华为技术有限公司 Pcc架构中的信息查询方法、装置及系统
CN101459904A (zh) * 2008-06-17 2009-06-17 中兴通讯股份有限公司 Aaa服务器、p-gw、pcrf、用户设备标识的获取方法和系统
CN102045717A (zh) * 2009-10-26 2011-05-04 中国移动通信集团公司 数据业务中获取用户标识的系统、方法及相关设备
CN102695171A (zh) * 2012-05-18 2012-09-26 中国联合网络通信集团有限公司 用户标识获取方法、系统及设备

Also Published As

Publication number Publication date
CN105553923A (zh) 2016-05-04

Similar Documents

Publication Publication Date Title
KR102546956B1 (ko) 3gpp 네트워크들에서의 소량 데이터 사용 가능
US9848090B2 (en) Offline charging per service data flow
US8825874B2 (en) Extending revalidation-time of diameter sessions
US8885568B2 (en) Policy application method for machine type communication, and policy and charging enforcement function
US8949447B2 (en) Optimized interface between two network elements operating under an authentication, authorization and accounting protocol
JP5461743B2 (ja) Ｄｉａｍｅｔｅｒセッション監査
US9319867B2 (en) Method and apparatuses for policy and charging control of machine-to-machine type communications
US20150236914A1 (en) Method and node for controlling resources for a media service as well as a corresponding system and computer program
EP3125591B1 (en) Policy control and processing method and device
WO2009124441A1 (zh) 会话终结触发方法、实现方法及系统
WO2016201999A1 (zh) 一种第三方应用的计费方法、装置及应用功能设备
WO2011063688A1 (zh) 策略和计费规则功能实体的选择方法及系统
WO2011085621A1 (zh) 业务处理方法及系统
EP2795946B1 (en) Methods and apparatuses for determining a user identity token for identifying user of a communication network
JP5727052B2 (ja) 一時サブスクリプションレコード
WO2016062025A1 (zh) 一种策略和计费规则功能的选择方法及装置
WO2009056046A1 (fr) Procédé de fin de session
WO2012116600A1 (zh) 策略和计费控制功能实体功能协商的方法和系统
WO2016070556A1 (zh) 一种获取用户标识的方法及网络侧设备
EP3507952B1 (en) Method and apparatus for policy management for temporary products in a telecommunications network
EP2807796B1 (en) Session termination in a mobile packet core network
WO2017107563A1 (zh) 进出区域监控的处理方法及装置
WO2018228215A1 (zh) 无线通信的方法和设备
CN103139798A (zh) 一种保障端到端会话业务质量的方法、pcrf及af
WO2016062061A1 (zh) 一种网元间同步策略规则的方法及设备

Legal Events

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

Ref document number: 15856696

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 15856696

Country of ref document: EP

Kind code of ref document: A1