WO2010020102A1 - 一种策略安装失败时的反馈方法和处理系统 - Google Patents

一种策略安装失败时的反馈方法和处理系统 Download PDF

Info

Publication number
WO2010020102A1
WO2010020102A1 PCT/CN2008/073578 CN2008073578W WO2010020102A1 WO 2010020102 A1 WO2010020102 A1 WO 2010020102A1 CN 2008073578 W CN2008073578 W CN 2008073578W WO 2010020102 A1 WO2010020102 A1 WO 2010020102A1
Authority
WO
WIPO (PCT)
Prior art keywords
policy
installation
racf
rcef
error
Prior art date
Application number
PCT/CN2008/073578
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 中兴通讯股份有限公司
Priority to EP08876779.3A priority Critical patent/EP2299635B1/en
Priority to US13/056,776 priority patent/US8713164B2/en
Publication of WO2010020102A1 publication Critical patent/WO2010020102A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/069—Management of faults, events, alarms or notifications using logs of notifications; Post-processing of notifications
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F15/00—Digital computers in general; Data processing equipment in general
    • G06F15/16—Combinations of two or more digital computers each having at least an arithmetic unit, a program unit and a register, e.g. for a simultaneous processing of several programs
    • G06F15/163—Interprocessor communication
    • G06F15/173—Interprocessor communication using an interconnection network, e.g. matrix, shuffle, pyramid, star, snowflake
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0806—Configuration setting for initial configuration or provisioning, e.g. plug-and-play
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/20—Traffic policing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/04—Registration at HLR or HSS [Home Subscriber Server]
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0866—Checking the configuration
    • H04L41/0869—Validating the configuration within one network element

Definitions

  • the present invention relates to the field of communications, and more particularly to a method and system for processing when a policy installation fails.
  • NGN Network Generation Network
  • NGN because the bearer network uses packet technology, especially IP technology, the problem of NGN in terms of quality of service (QoS) is particularly prominent. Therefore, how to provide end-to-end QoS will be one of the core issues of NGN.
  • QoS quality of service
  • TISPAN Telecommunication and Internet converged Services and Protocols for Advanced Networking, services and protocols for advanced network communication and Internet convergence
  • TISPAN divides the NGN architecture into a service layer and a transport layer.
  • NASS Network Attachment Subsystem
  • RACS Resource and Admission Control Subsystem
  • NASS is responsible for the upper layer services.
  • the layer provides independent user access management, while the RACS solves the QoS problem of the NGN bearer network.
  • FIG. 1 is a schematic diagram of a RACS function architecture of TISPAN in the prior art.
  • RACS is one of the components of the NGN. It associates the resource requirements of the service layer (such as IMS) with the resource allocation of the network bearer layer. It mainly implements policy control, resource reservation, admission control, and NAT (Network Address Translation). ) Crossing and other functions.
  • the RACS provides the transport layer control service for the application function (AF) through a series of QoS policies, so that the user equipment (User Equipment, UE) can obtain the service with the required QoS guarantee.
  • AF application function
  • UE User Equipment
  • the RACS consists of two entities: the SPDF module (Service-based Policy Decision Function) and the A-RACF module (Access-Resource and Admission Control Function, access resource admission control function), where:
  • the SPDF module provides a unified interface to application functions, shields the underlying network topology and specific access types, and provides business-based policy control.
  • the SPDF module selects a local policy according to the request of the application function module, and maps the request into a QoS parameter, and sends it to the A-RACF module and the BGF module (Border Gateway Function) to control the corresponding resources.
  • the A-RACF module controls the access network and has the functions of admission control and network policy aggregation.
  • the request is received from the SPDF module, and then the admission control is implemented based on the access network policy, accepting or rejecting the request for the transmission resource.
  • the A-RACF module obtains network attachment information and user QoS list information from the Network Attachment Subsystem (NASS) through the e4 interface, so that available network resources can be determined according to network location information (eg, the address of the physical node of the access user), and When processing the resource allocation request, check if the requested bandwidth information is consistent with that described in the user access list.
  • NSS Network Attachment Subsystem
  • the transport layer contains two functional entities: a BGF module (Border Gateway Function) and a RCEF module (Resource Control Enforcement Function), where:
  • the BGF module is a packet-to-packet gateway that can be located between the access network and the core network (implementing the core border gateway function) or between the two core networks (implementing the interconnection border gateway function). ).
  • the BGF module performs NAT traversal, gating, QoS marking, bandwidth limitation, usage measurement, and resource synchronization functions under the control of the SPDF module.
  • the RCEF module implements the Layer 2/Layer 3 (L2/L3) media stream policy transmitted by the A-RACF module through the Re reference point to complete functions such as gating, QoS marking, and bandwidth limitation.
  • L2/L3 Layer 2/Layer 3
  • the flow chart includes the following steps:
  • the AF receives the service request from the user, and triggers the AF to generate a session initialization message
  • the AF sends a service request message to the SPDF to request the resource to meet the user requirement; (203) the SPDF performs an authorization check on the service request according to the local operator policy, that is, determines whether the requested resource is consistent with the local operator policy rule;
  • the SPDF sends a resource request message to the A-RACF to request the corresponding resource; (205) A-RACF performs authorization and admission control according to the access network policy; A-RACF simultaneously determines whether the transmission policy needs to be loaded into the RCEF;
  • A-RACF interacts with RCEF to perform transmission policy installation (also called policy loading);
  • the RCEF sends a policy installation response message to the A-RACF to confirm the installation;
  • A-RACF sends a resource request response to notify the SPDF
  • the SPDF issuing policy is installed to the BGF and the BGF, and the result is notified to the SPDF; the execution of the step (209) and the steps (204) - (208) are not sequential, and may be performed simultaneously.
  • the SPDF sends a service request response to notify the AF.
  • the policy installation message sent by the A-RACF to the RCEF may include multiple policies. If some of the policies are installed incorrectly, the policy installation response message in step 207 carries the policy name and policy status of the error, but does not give an error reason for each of the installation errors. That is, if there are some policy installation errors, the policy installation response message only gives a message level error reason, which is usually expressed by the [Experimental-Result] parameter.
  • policy installation response message PIA Policy Install Answer
  • A-RACF accurately grasps the details of the policy installation failure on the RCEF, and improves the efficiency of the next release policy installation.
  • the present invention provides a feedback method when a policy installation fails, including: RCEF construction when the policy installation of the resource control execution function entity RCEF is failed when the access resource admission control function entity A-RACF fails to be installed.
  • RCEF construction when the policy installation of the resource control execution function entity RCEF is failed when the access resource admission control function entity A-RACF fails to be installed.
  • the feedback message is a policy installation response message PIA or an event notification message CCR.
  • the foregoing method may also have the following features: In the resource request process in the push mode or during the modification process, the RCEF installation policy, if the policy installation fails, add a policy to the PIA message sent by the A-RACF on the Re interface. Error reason parameter, otherwise it will not be added.
  • the foregoing method may also have the following features: In the resource release process, after the policy installation error on the RCEF, the parameter of the policy error reason is added to the CCR message sent by the A-RACF on the Re interface, otherwise it is not added.
  • the above method may also have the following characteristics: The reason of the policy error is added in the policy rule report parameter.
  • the policy rule report parameter further carries the following parameters: a policy name, a policy state.
  • the policy rule includes a policy error cause and one or more policy names.
  • the above method may also have the following features: Establish an error cause table on the A-RACF and the RCEF, and each cause of the error corresponds to a cause value; when the policy installation of the A-RACF to the RCEF fails, the RCEF is in feedback. The cause value of the installation failure is added to the message; A-RACF receives the error reason table to know the cause of the failure of each policy that failed to install.
  • the present invention also provides a processing system when a policy installation fails, including an access resource admission control function entity A-RACF and a resource control execution function entity.
  • A-RACF access resource admission control function entity
  • RCEF resource control execution function entity
  • the A-RACF is configured to send a policy to the RCEF
  • the RCEF is configured to send a feedback message to the A-RACF to confirm the installation, and when the policy installation fails, the feedback message carries the error reason of the installation failure policy.
  • the feedback message is a policy installation response message PIA or an event notification message CCR.
  • A-RACF cannot handle each policy in a targeted manner, and using the method of the present invention, a policy for each installation error is given.
  • the cause of the error that is, the more granular policy-level error causes, helps A-RACF to accurately grasp the cause of the error in each installation failure policy on the RCEF, so that the next time the policy is installed, it can be targeted. Handle, avoid further errors, ensure the effectiveness of the next policy installation, and improve the efficiency of the next release policy installation. This is especially true when there are multiple policy installation errors.
  • FIG. 1 is a schematic diagram of a RACS function architecture of TISPAN in the prior art
  • Figure 3 is a flow chart of resource request in a push mode of the method of the present invention.
  • the main idea of the present invention is that when the policy installation of the A-RACF to the RCEF fails, the RCEF will return the error reason for each A-RACF policy that failed to install.
  • the [Policy-Rule-Report] parameter in the PIA message feeds back the policy installation on the RCEF, [Policy-Rule-Name] and [Policy-Rule-Base-Name] indicate the policy name, and [Policy-Rule-Status] indicates Policy status, if a policy fails to be installed, it also feeds back the reason why this policy is installed incorrectly, namely: [Rule-Failure-Code].
  • Each [Policy-Rule-Report] carries a policy error reason and multiple policy names. If the reason for the failure of each of the installations is different, the policy may be reported in multiple [Policy-Rule-Report]. Each [Policy-Rule-Report] carries a policy error reason and one or several corresponding policy names.
  • each [Policy-Rule-Report] carries a policy error reason and multiple policy names. If the reason for the failure of each installation policy is different, the policy may be reported by multiple [Policy-Rule-Report], and each [Policy-Rule-Report] carries a policy error reason and one or several corresponding policy names.
  • a processing system when a policy installation fails based on the present invention including A-RACF and RCEF, wherein:
  • the A-RACF is configured to send a policy to the RCEF
  • the RCEF is configured to send a feedback message to the A-RACF to confirm the installation, and when the policy installation fails, the feedback message carries the error reason of the installation failure policy.
  • the feedback message is a policy installation response message PIA or an event notification message CCR.
  • the resource request process in the push mode based on the method of the present invention is as shown in FIG. 3, and the process includes the following steps:
  • the AF receives the service request from the user, and triggers the AF to generate a session initialization message
  • the AF sends a service request message to the SPDF to request resources to meet user requirements;
  • the SPDF performs an authorization check on the service request according to the local operator policy, that is, determines whether the requested resource is consistent with the local operator policy rule;
  • the SPDF sends a resource request message to the A-RACF to request the corresponding resource
  • A-RACF performs authorization and admission control according to the access network policy, and A-RACF also determines whether the transmission policy needs to be loaded into the RCEF;
  • A-RACF interacts with RCEF to perform transmission policy installation
  • RCEF sends a policy installation response message to A-RACF to confirm the installation
  • A-RACF can issue multiple policies to RCEF at one time. If there is a policy installation failure, the reason for the installation failure is returned for each failed installation policy.
  • the reason for the installation failure can be represented by the [Rule-Failure-Code] parameter, and the The parameters are included in the [Policy-Rule-Report] parameter. as follows:
  • the [Policy-Rule-Report] parameter in the Policy Installation Response Message (PIA) is used to feed back the policy installation on the RCEF. After adding the [Rule-Failure-Code] parameter to this parameter, you can return the reason for the installation failure for each failed installation policy.
  • an error cause table may be established on the A-RACF and the RCEF in advance, including the possible cause of the error, and each cause of the error corresponds to a cause value, when the policy installation issued by the A-RACF to the RCEF fails.
  • RCEF reports the installation failure reason value in the PIA, and the A-RACF can know the error reason of each policy of the installation failure according to the error reason table.
  • A-RACF sends a resource request response to notify SPDF
  • the SPDF issuing policy is installed to the BGF and the BGF, and the result is notified to the SPDF; the execution of the step (309) and the steps (304) - (308) are not sequential, and may be performed simultaneously.
  • SPDF sends a service request response to notify AF.
  • the resource release process based on the method of the present invention is shown in FIG. 4, and the process includes the following steps:
  • the RCEF sends an event notification message to the A-RACF, that is, a CCR message;
  • the RCEF returns detailed information to the A-RACF, that is, for each failed installation policy, the reason for the installation failure is returned.
  • the reason for the installation failure can be represented by the [Rule-Failure-Code] parameter, and the parameter is included in the [Policy-Rule-Report] parameter. as follows: [Policy-Rule-Name]
  • the [Policy-Rule-Report] parameter in the Event Notification Message (CCR) is used to feedback the installation of the policy on the RCEF. After adding the [Rule-Failure-Code] parameter to this parameter, the RCEF can return the reason for the failure of each installation for each failed installation policy.
  • A-RACF responds to the RCEF with an event notification response
  • A-RACF sends an interrupt session request message to the SPDF
  • the process of installing the other policy can also report the failure reason by using the method of the present invention, for example, modifying the process, and modifying the process is similar to the request process, and using the policy installation request PIR (Policy-Install- in the process)
  • PIR Policy-Install- in the process
  • the Request command sends an updated policy, and then the PIA command reports the reason for the failure.
  • the cause of the error is given to each of the installation error strategies, that is, the finer-grained policy-level error causes, which helps A-RACF accurately grasp each installation failure on the RCEF.
  • the cause of the error in the strategy.
  • the A-RACF can be processed in a targeted manner to avoid further errors, ensure the validity of the next policy installation, and improve the efficiency of the next release policy installation. This is especially true when there are multiple policy installation errors.

Description

一种策略安装失败时的反馈方法和处理系统
技术领域
本发明涉及通信领域， 更具体地涉及一种策略安装失败时的处理方法和 系统。
背景技术
NGN ( Network Generation Network , 下一代网络）是当前通信标准领域 的一个热点研究课题， 它釆用 IP等分组技术作为承载网技术融合固定通信和 移动通信。
NGN中， 由于承载网釆用了分组技术， 特别是 IP技术， 使 NGN在服务 质量（Quality of Service, QoS )方面的问题尤其突出。 因此， 如何提供端到 端的 QoS将是 NGN的核心问题之一。
TISPAN ( Telecommunication and Internet converged Services and Protocols for Advanced Networking, 用于高级网络的通信和互联网融合的业务和协议 ) 成立了专门的研究组， 致力于 NGN技术标准的制定工作。
TISPAN将 NGN架构分为业务层和传输层， 在传输控制层引入了 NASS ( Network Attachment Subsystem, 网络附着子系统）与 RACS ( Resource and Admission Control Subsystem, 资源接纳控制子系统） ， NASS负责为上层业 务层提供独立的用户接入管理， 而 RACS则解决 NGN承载网的 QoS问题。
图 1是现有技术中 TISPAN的 RACS功能架构图。 RACS是 NGN组成部 分之一， 它将业务层（如 IMS )的资源需求与网络承载层的资源分配相关联， 主要完成策略控制、资源预留、接纳控制、 NAT ( Network Address Translation, 网络地址转换） 穿越等功能。 RACS 通过一系列 QoS 策略为应用功能 ( Application Function, AF )提供传输层的控制服务， 使得用户终端 （User Equipment, UE )可以获得所需 QoS保证的业务。
RACS 由两个实体组成： SPDF 模块 （ Service-based Policy Decision Function, 基于业务的策略决策功能）和 A-RACF模块（ Access-Resource and Admission Control Function, 接入资源接纳控制功能） ， 其中：
SPDF模块， 向应用功能提供统一的接口，屏蔽底层网络拓朴和具体的接 入类型，提供基于业务的策略控制。 SPDF模块根据应用功能模块的请求选择 本地策略， 并将请求映射成 QoS 参数， 发送给 A-RACF模块和 BGF模块 ( Border Gateway Function, 边界网关功能） ， 以控制相应的资源。
A-RACF模块， 控制接入网， 具有接纳控制和网络策略汇聚的功能。 从 SPDF模块接收请求， 然后基于接入网策略实现接纳控制，接受或拒绝对传输 资源的请求。 A-RACF模块通过 e4接口从网络附着子系统（NASS )获得网 络附着信息和用户 QoS清单信息， 从而可以根据网络位置信息（例如接入用 户的物理节点的地址 )确定可用的网络资源， 同时在处理资源分配请求时检 查所请求的带宽信息是否与用户接入清单中描述的一致。
传输层中包含二种功能实体： BGF模块（ Border Gateway Function, 边界 网关功能）和 RCEF模块（ Resource Control Enforcement Function, 资源控制 执行功能） ， 其中：
BGF模块， 是一个包到包（Packet-to-packet ) 网关， 可位于接入网和核 心网之间 （实现核心边界网关功能） ， 也可以位于两个核心网之间 （实现互 联边界网关功能） 。 BGF模块在 SPDF模块的控制下完成 NAT穿越、 门控、 QoS标记、 带宽限制、 使用测量以及资源同步功能。
RCEF模块， 实施 A-RACF模块通过 Re 参考点传送过来的二层 /三层 ( L2/L3 )媒体流策略， 完成门控、 QoS标记、 带宽限制等功能。
图 2是现有技术中推模式下的资源请求过程。 该流程图包括以下步骤：
( 201 ) AF收到来自用户的业务请求， 并触发 AF生成会话初始化消息；
( 202 ) AF发送业务请求消息给 SPDF以请求资源来满足用户需求； ( 203 ) SPDF根据本地运营商策略对该业务请求进行授权检查， 即判断 所请求的资源是否与本地运营商策略规则一致；
( 204 )若通过授权检查， 则 SPDF给 A-RACF发送资源请求消息以请求 相应的资源； ( 205 ) A-RACF根据接入网策略执行授权和接纳控制； A-RACF同时决 定传输策略是否需要加载到 RCEF;
( 206 )若需要加载， 则 A-RACF与 RCEF交互， 进行传输策略安装（又 称为策略加载） ；
( 207 ) RCEF发送策略安装应答消息给 A-RACF以确认安装；
( 208 ) A-RACF发送资源请求应答以通知 SPDF;
( 209 ) SPDF下发策略给 BGF, BGF进行安装， 并将结果通知 SPDF; 步骤（209 )与步骤（204 ) - ( 208 ) 的执行无先后顺序， 也可同时进行。
( 210 ) SPDF发送业务请求应答以通知 AF。
在步骤 206中， A-RACF下发给 RCEF的策略安装消息中可以包含多条 策略。 若某些策略安装出错， 则在步骤 207中的策略安装应答消息中会携带 出错的那些策略名及策略状态， 但不会针对每条安装出错的策略给出出错原 因。 即， 若存在某些策略安装出错， 策略安装应答消息只给出一个消息级的 出错原因， 通常用 [Experimental-Result]这个参数来表达。
现有技术中， 策略安装情况在策略安装应答消息 PIA ( Policy Install Answer ) 中表示为如下几个参数： 策略名 策略状态 出错原因
Figure imgf000005_0001
注： "*"表示多个 在这种情况下，返回的是粗粒度（消息级）的出错原因。这不利于 A-RACF 掌握 RCEF的策略安装情况。 发明内容 本发明提出了一种策略安装失败时的反馈方法和处理系统， 有助于
A-RACF准确地掌握 RCEF上策略安装失败的详细信息， 提高下次下发策略 安装的效率。
为了解决上述技术问题，本发明提供了一种策略安装失败时的反馈方法， 包括： 当接入资源接纳控制功能实体 A-RACF下发给资源控制执行功能实体 RCEF的策略安装失败时， RCEF构造向 A-RACF的反馈消息时， 在所述反馈 消息中携带安装失败的策略的出错原因。
进一步地， 上述方法还可具有以下特点： 反馈消息为策略安装应答消息 PIA或事件通知消息 CCR。
进一步地， 上述方法还可具有以下特点： 在推模式下的资源请求过程中 或修改过程中， RCEF安装策略，若策略安装失败，则在 Re接口上向 A-RACF 发送的 PIA消息中添加策略出错原因参数， 否则不添加。
进一步地， 上述方法还可具有以下特点： 在资源释放过程中， RCEF上 策略安装出错后， 在 Re接口上向 A-RACF发送的 CCR消息中添加策略出错 原因的参数， 否则不添加。
进一步地， 上述方法还可具有以下特点： 策略出错原因添加在策略规则 报告参数中。
进一步地， 上述方法还可具有以下特点： 策略规则报告参数中还携带有 以下参数： 策略名、 策略状态。
进一步地， 上述方法还可具有以下特点： 策略规则^艮告参数中携带有一 个策略出错原因和一个或多个策略名。
进一步地， 上述方法还可具有以下特点： 在 A-RACF和 RCEF上建立一 个错误原因表， 每种出错原因对应一个原因值； 当 A-RACF下发给 RCEF的 策略安装失败时， RCEF在反馈消息中添加安装失败的原因值； A-RACF收到 后对照错误原因表获知安装失败的各个策略的出错原因。
为了解决上述技术问题， 本发明还提供了一种策略安装失败时的处理系 统， 包括接入资源接纳控制功能实体 A-RACF 和资源控制执行功能实体 RCEF, 其中：
所述 A-RACF , 用于向所述 RCEF下发策略；
所述 RCEF, 用于发送反馈消息给 A-RACF以确认安装， 以及在策略安 装失败时， 在所述反馈消息中携带安装失败的策略的出错原因。
进一步地， 上述系统还可具有以下特点： 所述反馈消息为策略安装应答 消息 PIA或事件通知消息 CCR。
若多条策略出错， 只返回一个笼统的出错原因给 A-RACF, A-RACF无 法针对每条策略进行针对性地处理， 而釆用本发明所述方法， 对每条安装出 错的策略给出出错原因， 即更细粒度的策略级的出错原因， 有助于 A-RACF 准确地掌握 RCEF上每条安装失败的策略的出错原因， 这样在下次下发策略 安装时， 就能针对性地进行处理， 避免再出错， 保证下次策略安装的有效性， 提高下次下发策略安装的效率。对于有多条策略安装出错时的情况尤其有效。 附图概述
图 1是现有技术中 TISPAN的 RACS功能架构图；
图 2是现有技术中推模式下的资源请求流程图；
图 3 于本发明方法的推模式下的资源请求流程图；
图 4是基于本发明方法的资源释放流程图。 本发明的较佳实施方式
下面结合附图对本发明的技术方案进行详细说明。
本发明的主要思想是：当 A-RACF下发给 RCEF的策略安装失败时， RCEF 将返回给 A-RACF每条安装失败的策略的出错原因。
具体包括：
( 1 )修改 Re接口上策略安装应答消息 （ PIA ) 中的 [Policy-Rule-Report] (策略规则报告）参数， 在此参数中添加 [Rule-Failure-Code]参数。 即， 策略名
策略状态 策略出错原因 出错原因
Figure imgf000008_0001
注: 表示多个
PIA 消息中的 [Policy-Rule-Report]这个参数反馈 RCEF 上策略的安装情 况 ， [Policy-Rule-Name] 和 [Policy-Rule-Base-Name] 表 示 策 略 名 ， [Policy-Rule-Status]表示策略状态， 若某条策略安装失败， 则还反馈这条策略 安装出错的原因， 即： [Rule-Failure-Code]。
如果多个策略安装失败的原因相同， 则可通过一条 [Policy-Rule-Report] 上报， 每条 [Policy-Rule-Report]中携带一个策略出错原因和多个策略名。 如果 各个安装失败的策略的原因不相同， 则可通过多条 [Policy-Rule-Report]上报， 每条 [Policy-Rule-Report]中携带一个策略出错原因和对应的一个或几个策略 名。
( 2 )修改 Re接口上事件通知消息（ CCR )中的 [Policy-Rule-Report]参数， 在此参数中添加 [Rule-Failure-Code]参数。 即，
[Policy-Rule-Name]
[Policy-Rule-Base-Name] 策略名
Policy-Rule-Status] 策略状态
Rule-Failure-Code] 策略出错原因 事件触发
Figure imgf000008_0002
注： 表示多个 如果多个策略安装失败的原因相同， 则可通过一条 [Policy-Rule-Report] 上报， 每条 [Policy-Rule-Report]中携带一个策略出错原因和多个策略名。 如果 各个安装失败的策略的原因不相同， 则可通过多条 [Policy-Rule-Report]上报， 每条 [Policy-Rule-Report]中携带一个策略出错原因和对应的一个或几个策略 名。
基于本发明的一种策略安装失败时的处理系统， 包括 A-RACF和 RCEF, 其中：
所述 A-RACF , 用于向所述 RCEF下发策略；
所述 RCEF, 用于发送反馈消息给 A-RACF以确认安装， 以及在策略安 装失败时， 在所述反馈消息中携带安装失败的策略的出错原因。
所述反馈消息为策略安装应答消息 PIA或事件通知消息 CCR。
基于本发明方法的推模式下的资源请求过程如图 3所示， 该流程包括以 下步骤：
( 301 ) AF收到来自用户的业务请求， 并触发 AF生成会话初始化消息；
( 302 ) AF发送业务请求消息给 SPDF以请求资源来满足用户需求；
( 303 ) SPDF根据本地运营商策略对该业务请求进行授权检查， 即判断 所请求的资源是否与本地运营商策略规则一致；
( 304 )若通过授权检查， 则 SPDF给 A-RACF发送资源请求消息以请求 相应的资源；
( 305 ) A-RACF根据接入网策略执行授权和接纳控制， A-RACF同时决 定传输策略是否需要加载到 RCEF;
( 306 )若需要加载， 则 A-RACF与 RCEF交互， 进行传输策略安装；
( 307 ) RCEF发送策略安装应答消息给 A-RACF以确认安装；
A-RACF可以一次下发多条策略给 RCEF,若存在策略安装失败， 则针对 每条安装失败的策略， 返回安装失败的原因。
具体地， 安装失败的原因可以用 [Rule-Failure-Code]参数来表示， 并且该 参数包含在 [Policy-Rule-Report]参数中。 如下:
[Policy-Rule-Name]
[Policy-Rule-Base-Name]
Figure imgf000010_0001
策略名
[Policy-Rule-Report]
[Policy -Rule- Status] 策略状态
[Rule-Failure-Code] 策略出错原因 其中 "*" 表示多个。
策略安装应答消息 （PIA ) 中的 [Policy-Rule-Report]参数用来反馈 RCEF 上策略的安装情况。 在此参数中添加了 [Rule-Failure-Code]参数后， 可以针对 每条安装失败的策略， 返回其安装失败原因。
具体实现时，例如可以事先在 A-RACF和 RCEF上建立一个错误原因表， 其中包括可能出现的出错原因， 每种出错原因对应一个原因值， 当 A-RACF 下发给 RCEF 的策略安装失败时， RCEF在 PIA 中上报安装失败原因值， A-RACF即可对照错误原因表知道安装失败的各个策略的出错原因。
( 308 ) A-RACF发送资源请求应答以通知 SPDF;
( 309 ) SPDF下发策略给 BGF, BGF进行安装， 并将结果通知 SPDF; 步骤（309 )与步骤（304 ) - ( 308 ) 的执行无先后顺序， 也可同时进行。
( 310 ) SPDF发送业务请求应答以通知 AF。
基于本发明方法的资源释放过程如图 4所示， 该流程包括以下步骤：
( 401 ) RCEF上发生事件触发， 有可能是由于某些策略安装出错；
( 402 ) RCEF给 A-RACF发送事件通知消息， 即 CCR消息；
若存在某些策略安装失败， 则 RCEF给 A-RACF返回详细信息， 即针对 每条安装失败的策略， 返回安装失败的原因。
具体地， 安装失败的原因可以用 [Rule-Failure-Code]参数来表示， 并且该 参数包含在 [Policy-Rule-Report]参数中。 如下： [Policy-Rule-Name]
[Policy-Rule-Base-Name] 策略名
[Policy-Rule-Report]
[Policy -Rule- Status] 策略状态
[Rule-Failure-Code] 策略出错原因 其中 "*" 表示多个。
事件通知消息（CCR )中的 [Policy-Rule-Report]参数用来反馈 RCEF上策 略的安装情况。 在此参数中添加了 [Rule-Failure-Code]参数后， RCEF可以针 对每条安装失败的策略， 返回其安装失败原因。
( 402a ) A-RACF给 RCEF回复事件通知应答；
( 403 ) A-RACF给 SPDF发送中断会话请求消息；
( 403a ) SPDF给 A-RACF回复中断会话请求应答；
( 404 ) SPDF给 AF发送中断会话请求消息；
( 404a ) AF给 SPDF回复中断会话请求应答；
( 405 ) SPDF释放 BGF上的资源。
404和 405的执行无先后顺序。
除上述流程外， 对于其他下发策略安装的流程也可釆用本发明的方法上 报失败原因， 例如修改流程， 修改流程与请求流程类似， 在该流程中使用策 略安装请求 PIR ( Policy-Install-Request )命令下发更新的策略， 然后由 PIA 命令上报失败原因。
当然， 本发明还可有其他多种实施例， 在不背离本发明精神及其实质的 但这些相应的改变和变形都应属于本发明所附的权利要求的保护范围。
工业实用性 釆用本发明所述方法， 对每条安装出错的策略给出出错原因， 即更细粒 度的策略级的出错原因， 有助于 A-RACF准确地掌握 RCEF上每条安装失败 的策略的出错原因。 在下次下发策略安装时， A-RACF可以有针对性地进行 处理， 避免再出错， 保证下次策略安装的有效性， 提高下次下发策略安装的 效率。 对于有多条策略安装出错时的情况尤其有效。

Claims

权 利 要 求 书
1、 一种策略安装失败时的反馈方法， 其特征在于，
当接入资源接纳控制功能实体 A-RACF 下发给资源控制执行功能实体 RCEF的策略安装失败时， 所述 RCEF构造向 A-RACF的反馈消息时， 在所 述反馈消息中携带安装失败的策略的出错原因。
2、 如权利要求 1所述的方法，其特征在于， 所述反馈消息为策略安装应 答消息 PIA或事件通知消息 CCR。
3、 如权利要求 2所述的方法，其特征在于，在推模式下的资源请求过程 中或修改过程中， 所述 RCEF安装策略， 若策略安装失败， 则在 Re接口上向 所述 A-RACF发送的 PIA消息中添加策略出错原因参数， 否则不添加。
4、 如权利要求 2 所述的方法， 其特征在于， 在资源释放过程中， 所述 RCEF上策略安装出错后， 在 Re接口上向所述 A-RACF发送的 CCR消息中 添加策略出错原因的参数， 否则不添加。
5、 如权利要求 1-4中任一权利要求所述的方法， 其特征在于， 所述策略 出错原因添加在策略规则报告参数中。
6、 如权利要求 5所述的方法，其特征在于， 所述策略规则报告参数中还 携带有以下参数： 策略名、 策略状态。
7、 如权利要求 6所述的方法，其特征在于， 所述策略规则报告参数中携 带有一个策略出错原因和一个或多个策略名。
8、 如权利要求 1-4中任一权利要求所述的方法， 其特征在于， 在 A-RACF和 RCEF上建立一个错误原因表， 每种出错原因对应一个原 因值；
当 A-RACF下发给 RCEF的策略安装失败时， RCEF在反馈消息中添加 安装失败的原因值；
所述 A-RACF收到后对照错误原因表获知安装失败的各个策略的出错原 因。
9、 一种策略安装失败时的处理系统，其特征在于， 包括接入资源接纳控 制功能实体 A-RACF和资源控制执行功能实体 RCEF, 其中： 所述 A-RACF , 用于向所述 RCEF下发策略；
所述 RCEF, 用于发送反馈消息给 A-RACF以确认安装， 以及在策略安 装失败时， 在所述反馈消息中携带安装失败的策略的出错原因。
10、 如权利要求 9所述的系统， 其特征在于，
所述反馈消息为策略安装应答消息 PIA或事件通知消息 CCR。
PCT/CN2008/073578 2008-08-20 2008-12-18 一种策略安装失败时的反馈方法和处理系统 WO2010020102A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP08876779.3A EP2299635B1 (en) 2008-08-20 2008-12-18 Feedback method and processing system when policy installation being failed
US13/056,776 US8713164B2 (en) 2008-08-20 2008-12-18 Feedback method and processing system for policy installation failures

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200810147531.8A CN101355807B (zh) 2008-08-20 2008-08-20 一种策略安装失败时的反馈方法
CN200810147531.8 2008-08-20

Publications (1)

Publication Number Publication Date
WO2010020102A1 true WO2010020102A1 (zh) 2010-02-25

Family

ID=40308330

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2008/073578 WO2010020102A1 (zh) 2008-08-20 2008-12-18 一种策略安装失败时的反馈方法和处理系统

Country Status (4)

Country Link
US (1) US8713164B2 (zh)
EP (1) EP2299635B1 (zh)
CN (1) CN101355807B (zh)
WO (1) WO2010020102A1 (zh)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
MX2018001875A (es) * 2015-08-14 2018-06-20 Ericsson Telefon Ab L M Sistema y metodo para proporcionar informacion de control para el control de congestion especifico de la aplicacion para la comunicacion de datos.
CN106155746B (zh) * 2016-07-13 2019-12-03 珠海豹趣科技有限公司 一种安装文件处理方法及装置、服务器
CN107800550B (zh) * 2016-08-31 2021-04-30 中国电信股份有限公司 策略执行方法和编排器
CN114095367B (zh) * 2020-07-30 2023-05-09 大唐移动通信设备有限公司 一种状态反馈方式的配置方法、状态反馈方法及装置

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040225749A1 (en) * 2003-05-08 2004-11-11 Gregory Pavlik Transformation of web site summary via taglibs
CN101198165A (zh) * 2007-10-19 2008-06-11 中兴通讯股份有限公司 资源接纳控制方法

Family Cites Families (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6983317B1 (en) * 2000-02-28 2006-01-03 Microsoft Corporation Enterprise management system
US20040034794A1 (en) * 2000-05-28 2004-02-19 Yaron Mayer System and method for comprehensive general generic protection for computers against malicious programs that may steal information and/or cause damages
US7496652B2 (en) * 2000-07-17 2009-02-24 Teleservices Solutions, Inc. Intelligent network providing network access services (INP-NAS)
US20040015579A1 (en) * 2001-06-14 2004-01-22 Geoffrey Cooper Method and apparatus for enterprise management
US7225367B2 (en) * 2001-08-22 2007-05-29 Genworth Financial, Inc. Method and system for tracking errors
US8914492B2 (en) * 2002-05-07 2014-12-16 British Telecommunication Plc Method and apparatus for selecting user policies
US7209963B2 (en) * 2002-07-11 2007-04-24 International Business Machines Corporation Apparatus and method for distributed monitoring of endpoints in a management region
US7155514B1 (en) * 2002-09-12 2006-12-26 Dorian Software Creations, Inc. Apparatus for event log management
US20080177994A1 (en) * 2003-01-12 2008-07-24 Yaron Mayer System and method for improving the efficiency, comfort, and/or reliability in Operating Systems, such as for example Windows
US7647398B1 (en) * 2005-07-18 2010-01-12 Trend Micro, Inc. Event query in the context of delegated administration
CN100373976C (zh) 2005-10-14 2008-03-05 华为技术有限公司 在设备管理中处理失败任务的方法及装置
CN1863201B (zh) * 2005-10-17 2010-12-08 华为技术有限公司 查询客户端对策略条件执行结果的方法
US8108677B2 (en) 2006-10-19 2012-01-31 Alcatel Lucent Method and apparatus for authentication of session packets for resource and admission control functions (RACF)
CN101072180B (zh) * 2007-04-03 2011-04-06 中兴通讯股份有限公司 一种下一代通讯网络中加强传送控制层控制的方法及系统
US8059533B2 (en) * 2007-10-24 2011-11-15 Cisco Technology, Inc. Packet flow optimization (PFO) policy management in a communications network by rule name
CN101355808B (zh) 2008-08-20 2013-01-16 中兴通讯股份有限公司 一种上报策略安装失败的方法

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040225749A1 (en) * 2003-05-08 2004-11-11 Gregory Pavlik Transformation of web site summary via taglibs
CN101198165A (zh) * 2007-10-19 2008-06-11 中兴通讯股份有限公司 资源接纳控制方法

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP2299635A4 *

Also Published As

Publication number Publication date
CN101355807B (zh) 2016-08-03
EP2299635A1 (en) 2011-03-23
US8713164B2 (en) 2014-04-29
CN101355807A (zh) 2009-01-28
EP2299635B1 (en) 2018-08-08
US20110138237A1 (en) 2011-06-09
EP2299635A4 (en) 2012-05-02

Similar Documents

Publication Publication Date Title
EP2148466B1 (en) A multicast/unicast admission control method, device and system
US9009333B2 (en) Method and device for transmitting network resource information data
US8811236B2 (en) Interaction method and device between resource and admission control systems
WO2009114976A1 (zh) 资源接纳控制方法和系统
US20090274163A1 (en) Method, system, and apparatus for controlling multicast bearer resources
WO2009003421A1 (fr) Procédé de contrôle d'admission des ressources, système et système d'application de service
US20090086744A1 (en) Method, system and device for selecting edge connection link across different management domain networks
WO2011120257A1 (zh) 一种家庭网络的资源接纳控制方法及系统
US20100226379A1 (en) Policy control method and system for layer two devices
WO2010020102A1 (zh) 一种策略安装失败时的反馈方法和处理系统
WO2010081314A1 (zh) 一种ngn家庭网络资源接纳控制方法及系统
EP2224660A1 (en) A system and a method for the resource access control
WO2011022961A1 (zh) 资源接纳控制系统间的交互方法及资源接纳控制系统
WO2009026802A1 (fr) Procédé, dispositif et système pour obtenir un rapport de qos
WO2010020083A1 (zh) 一种上报策略安装失败的方法和系统
WO2012149833A1 (zh) 一种资源接纳控制方法及系统
WO2011032374A1 (zh) 批发场景下的拉模式资源接纳控制方法和系统
WO2011044811A1 (zh) 一种接纳控制系统及方法
EP2068508A1 (en) Method, device and system for synchronizing user data in next generation network
WO2009105942A1 (zh) 资源接纳控制子系统及发送资源决策请求消息的方法
WO2011035666A1 (zh) 资源管理系统中实现资源状况上报的方法及系统
WO2008154847A1 (fr) Procédé d'indication d'opération, dispositif et système
WO2011069390A1 (zh) 用量签订方法及系统、基于用量的接纳控制方法及系统
WO2011035662A1 (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: 08876779

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2008876779

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 13056776

Country of ref document: US

NENP Non-entry into the national phase

Ref country code: DE