×

Method and system for transporting service flow securely in an IP network

  • US 8,542,580 B2
  • Filed: 10/06/2006
  • Issued: 09/24/2013
  • Est. Priority Date: 06/18/2004
  • Status: Active Grant
First Claim
Patent Images

1. A method for transporting a service flow securely in an Internet Protocol, IP, network, comprising the following steps:

  • upon receiving a service call request sent by a calling user, a service server determining bandwidth that the service call needs through negotiation with the calling user and a called user, and analyzing the service call to determine a quality of service (QoS) level and a security level;

    the service server sending a first request to a resource manager, requesting to build a service flow path for a call between the calling user and the called user, wherein the first request comprises bandwidth that the service call needs, location information of the calling user and the called user, information of level of QoS and security level;

    the resource manager receiving the first request, determining whether the network has enough resources for the service flow path by comparing a current resource status of the network with the information in the first request, if the network has not enough resources for the service flow path, rejecting the first request, and if the network has enough resources for the service flow path, establishing a Label Switching Path (LSP) between a first Provider Edge Router (PE) that serves the calling user and a second PE that serves the called user;

    the resource manager sending a configuration request message to the first PE and the second PE respectively according to the LSP;

    each of the first PE and the second PE building an item in respective flow classification tables according to the configuration request message, wherein the item comprises correspondence between information of a service flow of the call and an identity of the LSP, the information of the service flow of the call comprises protocol, source address, local port number, remote address, and remote port number; and

    each of the first PE and the second PE receiving a service flow, determining whether the service flow matches information contained in one of the items listed in the flow classification tables, forwarding the service flow to an LSP corresponding to the service flow when the service flow matches information contained in one of the items listed in the flow classification tables, and forwarding the service flow in a connectionless manner when the service flow does not match information contained in any one of the items listed in the flow classification tables.

View all claims
  • 1 Assignment
Timeline View
Assignment View
    ×
    ×