# US 2010/0074110 A1 · Control Method, System and Function Entity for Reporting Bearer Event of Signaling IP Flow

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2010/0074110 A1
- Document ID: US20100074110A1
- Status: Published application
- Kind: A1
- Application number: 12/634,147
- Filed: 2009-12-09
- Published: 2010-03-25
- Earliest claimed: 2007-03-23
- Assignees: Huawei Technologies Co., Ltd.
- Inventors: Shibi HUANG; Peng ZHAO; Yuxin MAO; Shiyong TAN; Weihua WEI; Yan LI
- Web page: https://patentgrep.com/patent/US20100074110A1

## CPC

- H04W 4/20: Services signaling; Auxiliary data signalling, i.e. transmitting data via a non-traffic channel
- H04L 12/14: Charging, metering or billing arrangements specially adapted for data communications, e.g. authentication, authorisation and accounting [AAA] framework
- H04L 12/1428: {Invoice generation, e.g. customization, lay-out, database processing, algorithms for calculating the bill or formatting invoices as WWW pages (invoicing in general G06Q30/04)}
- H04L 12/1457: {using an account}
- H04L 12/56: {Packet switching systems}
- H04L 65/80: Responding to QoS
- H04L 65/1016: IP multimedia subsystem [IMS]
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A control method, system and function entity for reporting a bearer event of a signaling IP flow are provided. Flow identifier information such as a 5-tuple is generated for a signaling IP flow and a media IP flow so as to unify a mechanism for reporting a signaling path status and a mechanism for reporting a bearer event of a media IP flow, so that the mechanism for reporting a signaling path status is not limited by the parameter of Flow Usage, the PDP context with a signaling tag, thereby establishing corresponding PCC rules for signaling and the association between a signaling IP flow and a bearer. A method for reporting a signaling path status is further provided in the invention. In the method, for a default PDP context or a PDP context of a signaling IP flow, the predefined PCC rules are activated or signaling PCC rules generated in accordance with an Application Function address are installed, thereby an IP signaling path status is reported in accordance with rule names of the predefine PCC rules or the signaling PCC rules.

## Claims

### Claim 1

A method for reporting a bearer event of a signaling IP flow, comprising:
generating, by an Application Function, flow identifier information of a signaling IP flow;
sending, by the Application Function, a subscription request for subscribing to a bearer event of the signaling IP flow to a Policy Control and Charging Rules Function, wherein the subscription request carries the flow identifier information of the signaling IP flow; and
receiving, by the Application Function, a bearer event report of the signaling IP flow from the Policy Control and Charging Rules Function, wherein the bearer event report carries the flow identifier information of the signaling IP flow.

### Claim 2 (depends on 1)

The method according to claim 1, further comprising:
establishing, by the Policy Control and Charging Rules Function, Policy Control and Charging rules and Policy Control and Charging rule names corresponding to the signaling IP flow in accordance with the flow identifier information of the signaling IP flow, and sending the Policy Control and Charging rules and the Policy Control and Charging rule names to a Policy and Charging Enforcement Function;
reporting, by the Policy and Charging Enforcement Function, upon detection of the bearer event subscribed to by the Policy Control and Charging Rules Function, the Policy Control and Charging rule names associated with the bearer event and the detected bearer event to the Policy Control and Charging Rules Function; and
generating and sending, by the Policy Control and Charging Rules Function, the bearer event report carrying information including the flow identifier information of the signaling IP flow corresponding to the Policy Control and Charging rule names associated with the bearer event.

### Claim 3 (depends on 2)

The method according to claim 2, further comprising:
establishing, by the Policy Control and Charging Rules Function, upon receiving the subscription request, the Policy Control and Charging rules and the Policy Control and Charging rule names corresponding to the signaling IP flow in accordance with the flow identifier information of the signaling IP flow, after determining that no Policy Control and Charging rule or Policy Control and Charging rule name is available for the signaling IP flow.

### Claim 4 (depends on 1)

The method according to claim 1, further comprising:
sending, by the Policy Control and Charging Rules Function, if the Policy Control and Charging Rules Function determines that the Policy Control and Charging rules and Policy Control and Charging rule names are available for the signaling IP flow in accordance with the flow identifier information of the signaling IP flow, the Policy Control and Charging rules and the Policy Control and Charging rule names to a Policy and Charging Enforcement Function;
reporting, by the Policy and Charging Enforcement Function, upon detection of the bearer event subscribed to by the Policy Control and Charging Rules Function, the Policy Control and Charging rule names associated with the bearer event and the detected bearer event to the Policy Control and Charging Rules Function; and
generating and sending, by the Policy Control and Charging Rules Function, the bearer event report carrying information including the flow identifier information of the signaling IP flow corresponding to the Policy Control and Charging rule names associated with the bearer event.

### Claim 5 (depends on 1)

The method according to claim 1, wherein the step of generating flow identifier information of a signaling IP flow comprises:
providing the signaling IP flow with a default media component number 0.

### Claim 6 (depends on 3)

The method according to claim 3, wherein the generating a flow identifier information of a signaling IP flow comprises:
providing the signaling IP flow with a default media component number 0.

### Claim 7 (depends on 4)

The method according to claim 4, wherein the generating a flow identifier information of a signaling IP flow comprises:
providing the signaling IP flow with a default media component number 0.

### Claim 8

An Application Function, comprising:
a first subscription request sending unit adapted to send a subscription request for subscribing to a bearer event of a signaling IP flow to a Policy Control and Charging Rules Function, wherein the subscription request carries a generated flow identifier information of the signaling IP flow; and
a first bearer event report receiving unit adapted to receive a bearer event report of the signaling IP flow from the Policy Control and Charging Rules Function, where the bearer event report carries the flow identifier information of the signaling IP flow.

### Claim 9 (depends on 8)

The Application Function according to claim 8, wherein the signaling IP flow is provided with a default media component number 0.
