Back to results
US 8,559,309 B2Granted
Tagging VoIP originated traffic
AssigneeVerizon Patent and Licensing Inc.
InventorBrian Edmund Somes
Life of this patent
Estimating the term…
Abstract
A network node receives a Session Initiation Protocol (SIP) or H.323 signaling packet associated with data traffic, and determines if the data traffic originated from a source node or source network as Voice over Internet Protocol (VoIP) traffic. The network node tags a header of the SIP or H.323 signaling packet with a tag that identifies the data traffic as a VoIP originated call based on the determination, and sends the tagged SIP or H.323 signaling packet towards a destination. The network node further sends data identifying the data traffic as a VoIP originated call to an administrative system for at least one of call billing, rating, settlement or taxation purposes.
Claims15
A method, comprising:
- receiving a Session Initiation Protocol (SIP) or H.323 signaling packet associated with data traffic;
- determining if the data traffic originated from a source node or source network as Voice over Internet Protocol (VoIP) traffic;
- tagging a header of the SIP or H.323 signaling packet with a tag that identifies the data traffic as a VoIP originated call based on the determination, wherein tagging the header of the SIP or H.323 signalling packet with a tag comprises one of a) through c):
- a) inserting a code in a “rn-context” tag defined in accordance with Internet Engineering Task Force (IETF) Request for Comments (RFC) 4694 and inserting the “rn-context” tag into the header, wherein the code identifies the data traffic as a VoIP originated call,
- b) appending a code to jurisdiction information in an “rn” tag and inserting the “rn” tag into the header, wherein the code identifies the data traffic as a VoIP originated call, or
- c) inserting a jurisdiction code in a “rn” tag and inserting the “rn” tag into the header, wherein the jurisdiction code identifies the data traffic as originating from a VoIP originated jurisdiction;
- sending the tagged SIP or H.323 signaling packet towards a destination;
- and
- sending data identifying the data traffic as a VoIP originated call to an administrative system for at least one of call billing, rating, settlement or taxation purposes.
6 more elements
A network node, comprising:
- a communication interface;
- and
- a processing unit configured to:
- receive, via the communication interface, a Session Initiation Protocol (SIP) or H.323 signaling packet associated with data traffic,
- determine if the data traffic was sent from a source node or source network as Voice over Internet Protocol (VoIP) traffic,
- modify a header of the SIP or H.323 signaling packet with a tag that identifies the data traffic as a VoIP originated call based on the determination,
- wherein, when modifying the header of the SIP or H.323 signaling packet with a tag, the processing unit is configured to:
- a) insert a code in a “rn-context” tag defined in Internet Engineering Task Force (IETF) Request for Comments (RFC) 4694 and inserting the “rn-context” tag into the header, wherein the code identifies the data traffic as a VoIP originated call,
- b) append a code to jurisdiction information in an “rn” tag and inserting the “rn” tag into the header, wherein the code identifies the data traffic as a VoIP originated call, or
- c) insert a jurisdiction code in a “rn” tag and inserting the “rn” tag into the header, wherein the jurisdiction code identifies the data traffic as originating from a VoIP originated jurisdiction, and
- send, via the communication interface, the tagged SIP or H.323 signaling packet towards a destination.
8 more elements
A method, comprising:
- receiving a Session Initiation Protocol (SIP) or H.323 signaling packet associated with data traffic;
- inspecting a header of the SIP or H.323 signaling packet to identify a tag in the header that indicates whether the data traffic originated from a source node or source network as Voice over Internet Protocol (VoIP) traffic;
- and
- routing the data traffic based on whether the tag in the header indicates that the data traffic originated as VoIP traffic,
- wherein routing the data traffic comprises:
- routing the data traffic to a VoIP-based long distance carrier or Competitive Local Exchange Carrier (CLEC) that supports reduced VoIP rates or taxation if the tag in the header indicates that the data traffic originated as VoIP traffic.
3 more elements
A network node, comprising:
- a communication interface;
- and
- a processing unit configured to:
- receive, via the communication interface, a Session Initiation Protocol (SIP) or H.323 signaling packet associated with data traffic,
- inspect a header of the SIP or H.323 signaling packet to identify a tag in the header that indicates whether the data traffic originated from a source node or source network as Voice over Internet Protocol (VoIP) traffic, and
- route the data traffic based on whether the tag in the header indicates that the data traffic originated as VoIP traffic,
- wherein, when routing the data traffic, the processing unit is configured to:
- route the data traffic to a VoIP-based long distance carrier or Competitive Local Exchange Carrier (CLEC) that supports reduced VoIP rates or taxation if the tag in the header indicates that the data traffic originated as VoIP traffic.
5 more elements
Dependencies are inferred from the claim text.