CN1968269A

CN1968269A - Method and system for implementing IPTN service

Info

Publication number: CN1968269A
Application number: CNA2006100885388A
Authority: CN
Inventors: 徐锐
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2006-06-02
Filing date: 2006-06-02
Publication date: 2007-05-23
Also published as: WO2007140694A1

Abstract

The invention relates to a method for realizing IPTN service and relative system, wherein said method comprises that: building IPTN LSP tunnel between edge routers; presetting IPTN mark of mark stack relative to the IPTN LSP tunnel in edge router of user domain, and pointing the target address or network section of said IPTN LSP tunnel; for the service requested by source terminal of user domain, edge router based on the IPTN mark or mark stack transfers service to target terminal, to realize the IPTN service between two access points, without RM server, to reduce network complexity, confirm the bandwidth and QoS of service.

Description

Method and system for realizing IPTN service

Technical Field

The invention relates to an IPTN technology, in particular to a method and a system for realizing an IPTN service through an IPTN tunnel statically configured under a user domain.

Background

Current network technology advances have made it possible to carry voice over packet networks, and the rich traffic demands that require rapid push-out have prompted the emergence of a soft switch (SoftSwitch) architecture. Meanwhile, Next Generation Networks (NGNs), which mark the arrival of the new generation telecommunication network age, are open, IP-based networks in which the functions of conventional telecommunication switching equipment are separated to form individual components that are developed independently and are coordinated with each other through standard protocols. After the IP network is commercialized, the basic platform for telecommunication service has the following problems:

1. QoS (quality of service) issues: ISP (internet service provider)/ICP (internet content provider) does not have the ability to guarantee quality of service to users, and cannot charge users a sufficient fee; and the IP network can not meet the needs of the private line users temporarily, it is difficult to deploy real-time services, and the convergence of the three networks (cable television network, mobile communication network and internet) is also difficult to implement.

2. Safety problems are as follows: the ubiquitous hacker makes the business under attack from time to time, etc., which will result in the inability to enhance the user experience, especially making enterprise users seriously worried about.

3. Management problems: the traditional IP network does not define and design a management and maintenance system for the public environment, so that when a network fails, the failure cannot be located or is not located quickly enough.

4. Value chain problems: the "free" model of traditional IP networks has led to "network foam economies" that have a critical need to establish benign operational models that form a benign value chain for users, ISPs, ICPs, etc.

On the basis, in order to solve the problems of QoS, security, management and the like of the IP network, a concept and a framework of an IP telecommunication network (IPTN) are proposed, and the existing IP network is modified. The IP telecommunications network can carry both traditional PSTN (public switched telephone network) traffic and data private line traffic while supporting new IP services at the carrier level quality of service (QoS).

Figure 1 shows an overall block diagram of an IPTN.

As shown in fig. 1, the IPTN mainly comprises: service control layer, bearing control layer, logic bearing network and basic physical network. Wherein,

the CA, which is a call agent, is located at the traffic control layer, which performs various traffic controls, and may be a softswitch, a video on demand Server (VOD Server), a virtual private network manager (vpn manager), etc.

The load control layer is provided with an RM (resource management server) which has the functions of: managing resources of the logical bearer network; the method comprises the steps of receiving a resource request from a service control layer, determining whether to accept a call, designating a service flow path, and controlling an Edge Router (ER) to finish service sensing, thereby achieving the effects of applying for resources before use, ensuring resources in use and releasing resources after use of the carrier-class service.

The logic bearing network is provided with an Edge Router (ER) and a convergence router (BR), wherein the ER receives a QoS control command issued by an RM in a bearing control layer to complete the works such as flow classification, label stack push-in and the like. The BR and the ER form an MPLS (multiprotocol label switching) network together, and a plurality of LSPs (label switching paths) are connected into an IPTN path through a label stack, so that various service flows can reach a destination under the condition of ensuring certain QoS.

The physical circuit in the basic physical network corresponds to the logical bearer network to complete the service.

Among them, a plurality of MA management areas (domains) correspond to a plurality of resource managers RM, respectively (for example, MA1 corresponds to RM1, MA2 corresponds to RM2, and the like).

According to the general framework of IPTN shown in fig. 1, a user may issue a service request through a call, establish a service (e.g. call, internet access, etc.) with a target user via CA, RM, ER.

Figure 2 shows a typical application of existing IPTN technology implemented in accordance with the general framework of IPTN shown in figure 1.

As shown in fig. 2, the conventional IPTN service flow includes:

1) the user terminal a initiates a call, triggering a service request.

2) The NGN service system (CA) completes service request analysis, acquires IP addresses and TCP/UDP port numbers of both parties (user terminals A and B) of the call, and applies resources to RM1 according to QoS indexes required by audio and video data streams;

RM1 collects link topology and resource information, determines whether to admit or reject the call of user terminal A according to the resource usage, if finding that the resource is not enough to establish connection, RM1 returns call failure to NGN service system; if the call of the user terminal a is admitted, the service system continues to establish a call connection.

3) After admitting the call of the user terminal A, the RM1 performs routing according to the IP addresses of the two parties of the call and a preset routing strategy, sends out a resource request to the RM (RM2, RM3 and the like) of the next domain according to the routing result, and determines whether to admit or reject the user call according to the resource use condition after receiving the request.

4) If RM2 accepts the request, a resource request is again issued to RM3 of the next domain according to the routing result.

5) RM3 issues a stream install command to ER (ER in MA3 domain) corresponding to the IP address through COPS (common open policy service) protocol, respectively, mapping to traffic policy of audio or video, if the destination IP address in the resource request message received by RM3 belongs to the local domain.

6) After the ER receives the stream installation command, the strategy switch is executed to classify the message stream, and the stream matched with the rule is guaranteed to have high-grade QoS of the telecommunication service, so that the user service can be developed. And reporting a QoS resource response message to RM3 after the policy is successfully installed.

7) RM3 forwards the flow QoS resource response message to RM2 of the previous domain according to the source IP (user terminal a) after receiving the response message.

8) After receiving the QoS resource response message, RM2 forwards the source IP in the message to RM1 of the previous domain until the RM that originally initiated the resource request (RM1) if the source IP does not belong to the local domain.

9) Since the LSP is a unidirectional path, and an LSP path must be established in both directions to establish a call, RM1 needs to issue a flow installation command containing traffic policies with the same content and in opposite directions to the ER corresponding to the source IP address.

10) After receiving the stream installation command, the ER (ER in MA 1) also locally executes the policy switch, establishes mapping of the streams in the opposite direction, and reports a response message of successful stream installation to the RM.

11) After RM1 receives the response message of stream installation success, the bidirectional path of call is ready at this time, and reports the QoS resource response message to NGN service system (CA).

12) After receiving successful QoS resource response message, NGN service system completes the connection establishment process, the target terminal rings, and user terminals A and B can use telecommunication service.

As can be seen from the above-mentioned process, in the existing IPTN application, the service is dynamically delivered by the RM, which collects the link topology and resource information, responds and proxies the call request and bandwidth application of the NGN service layer, and then delivers the IPTN stream to the ER through the COPS (general open policy service) protocol, thereby implementing the call establishment and bandwidth occupation.

Although this method of managing resources and topology of the entire network using the RM and proxying the service establishment of the ER can flexibly plan and utilize the relatively complex network topology and resources, in the system architecture, a device of the bearer control layer, i.e. the RM server, is added, which is redundant for a service or application that only needs to use the relatively simple network topology.

If the operator wants to provide point-to-point based IPTN LSP tunnel service with NGN service and QoS guarantee, then the RM server manages the IPTN LSP tunnel and bandwidth and issues the stream, which complicates networking and increases unnecessary cost.

Therefore, there is a need to design a method and a system for implementing an IPTN service through an IPTN LSP tunnel statically configured in a user domain, so as to greatly reduce the complexity of a network and simultaneously ensure the bandwidth and QoS required by the service.

Disclosure of Invention

The invention aims to provide a method for realizing IPTN service, which greatly reduces the complexity of a network and ensures the bandwidth and QoS required by the service.

According to the object of the present invention, a method for implementing an IPTN service is provided, the method comprising: establishing IPTN LSP tunnel between edge routers in advance; an IPTN label or a label stack corresponding to the IPTN LSP tunnel is pre-configured in an edge router serving as a user domain, and a destination address or a network segment of the IPTN LSP tunnel is specified; and for the service requested by the source terminal user on line from the user domain, the edge router forwards the service to the destination terminal according to the IPTN label or label stack of the IPTN tunnel corresponding to the requested service.

Another object of the present invention is to provide a system for implementing IPTN services, which greatly reduces the complexity of the network, while ensuring the bandwidth and QoS required by the services.

According to another object of the present invention, a system for implementing IPTN services is provided, which includes an edge router, which uses a single LSP or a plurality of LSPs to connect with a convergence router and other edge routers, so as to establish an IPTN LSP tunnel between the edge routers; and the terminal requests the IPTN service from the user domain corresponding to the edge router, wherein the edge router forwards the service to the destination terminal according to the IPTN label or label stack of the IPTN tunnel corresponding to the requested IPTN service.

The invention has the advantages that IPTN service between two access points is realized through the statically configured IPTN LSP tunnel without participation of an RM server, thereby greatly reducing the complexity of the network and simultaneously ensuring the bandwidth and QoS required by the service.

Drawings

Figure 1 shows an overall framework diagram of an IPTN;

figure 2 shows a typical application of existing IPTN technology implemented in accordance with the general framework of IPTN shown in figure 1; and

figure 3 shows a system architecture of the IPTN architecture of the present invention.

Detailed Description

The invention provides service for each user of access domain by using Edge Router (ER) as access device.

As shown in fig. 3, compared with the existing IPTN, the IPTN architecture according to the present invention omits a bearer control layer, and in the prior art, the content (implemented function) issued by the RM in the bearer control layer is statically configured by the user, and the static configuration is implemented by a command line or a network management MIB.

The following describes in detail a process of statically configuring an IPTN LSP tunnel under a domain to provide a simple IPTN service according to the IPTN architecture of the present invention. The IPTN traffic described therein is a data stream with the same purpose IP, the same protocol, and the same TCP port number, that is, in the present invention, traffic is distinguished by domain, e.g., loginwww.hotmail.comIs an IPTN service, and different users log inwww.hotmail.comAll joining the same domain.

The configuration options for the IPTN service in the invention comprise: the source and destination IP addresses and masks, TCP or UDP port numbers for the source and destination IP addresses and protocols, all of which are user selectable and arbitrarily collocated.

According to the invention, the process of configuring the IPTN LSP tunnel under the domain specifically comprises the following steps:

1): an aggregation router and an edge router are deployed in advance in a logical bearer network by using connection of a single LSP or multiple LSPs, so as to establish an IPTN LSP tunnel between any two edge routers, that is, a BR and an ER are deployed in advance in the logical bearer network, and a single LSP (label switched path) or multiple LSP connections are used to establish an IPTN LSP tunnel between any two access points (e.g., ER1 and ER2) to form an LSP network, and certain resources and specified QoS parameters are reserved on the tunnel.

In the prior art, an RM dynamically establishes an IPTN LSP tunnel between two access points according to resources, and simultaneously reserves certain resources and specified QoS parameters on the tunnel.

2): configuring IPTN label or label stack, and appointing destination address or network segment, in which each label represents an LSP, and each LSP has been configured with a certain total bandwidth.

As shown in fig. 3, a complete IPTN LSP tunnel is formed by the label switching paths L1, L2, L3, and L4 between the two access points ER1 and ER2, and the L1, L2, L3, and L4 are a set of label stacks, which specify the destination address of the above-mentioned pre-established IPTN LSP tunnel as ER 2.

Of course, it is possible to configure the IPTN tag or tag stack for all any two access points and store the IPTN tag or tag stack information in the ER.

In addition, other matching rules, such as protocol number, source and destination port number, etc., may also be configured and stored in the ER along with the IPTN tag or tag stack information described above.

With the simple configuration described above, traffic can be completed between two access points (e.g., ER1 and ER2) using an IPTN LSP tunnel.

Still referring to fig. 3, how to complete the service through the above-mentioned IPTN LSP tunnel statically configured under the user domain is illustrated.

a) The user terminal A initiates a call, requests a service request of a terminal B, the terminal A corresponds to the access equipment ER1, the terminal B corresponds to the access equipment ER2, the user domain 1 of the ER1 is (10.0.0.1/24), and the user domain 2 of the ER2 is (11.0.0.1/24).

b) The NGN service system (CA) analyzes the service request, and obtains the IP addresses of both parties (user domains 1 and 2) and the TCP/UDP port numbers.

c) The NGN service system (CA) notifies the access device ER1 corresponding to the terminal a and the terminal a of the destination network segment address (address of the user domain 2), and the terminal a gets on line from the ER1, which is the user domain 1.

d) Since the ER1 pre-stores label stacks (L1/L2/L3/L4) corresponding to the preconfigured IPTN LSP tunnels (tunnels between the ER1 and the ER2), the ER1 matches the destination address (or matches other rules such as protocol number, source and destination port number) of the message (message sent from the online terminal a in the user domain 1) added to the user domain 1, and inserts the label stacks (L1/L2/L3/L4) into the message, thereby forwarding the LSP on the statically configured IPTN LSP tunnels and reaching the terminal B corresponding to the user domain 2.

Since the ER1 may have a plurality of label stacks (corresponding to the IPTN LSP tunnels between the ER1 and the plurality of ERs), the matching of the destination address is to find the label stack corresponding to the destination address (user domain 2).

Meanwhile, a label stack (L1/L2/L3/L4) corresponding to a preconfigured IPTN LSP tunnel (a tunnel between the ER1 and the ER2) is also prestored in the ER2 corresponding to the target user terminal B.

Therefore, by statically configuring the IPTN LSP tunnel under the domain and storing the relevant information of the IPTN LSP tunnel in the Edge Router (ER), when the source and destination terminal users are connected to the LSP network through the access device (ER), the static IPTN LSP tunnel can be used for forwarding the service according to the label stack corresponding to the IPTN LSP tunnel, and each LSP corresponding to the label stack reserves certain resources and QoS indexes, thereby ensuring the bandwidth and QoS required by the forwarded service.

In addition, the invention can also be directly applied to the existing IPTN architecture system shown in FIG. 1, wherein the statically configured IPTN LSP tunnel does not affect the connection between the ER and the RM.

That is, if the RM issues the IPTN stream to the ER through COPS, the IPTN stream dynamically issued through COPS protocol will be preferentially checked and forwarded in the ER; if there is no IPTN flow dynamically issued to ER by COPS protocol, the IP telecommunication network service is realized by label stack corresponding to IPTN LSP tunnel statically configured in user domain, so as to simplify service flow. Therefore, the IPTN service is realized more flexibly.

In summary, according to the method and system for implementing the IPTN service through the IPTN LSP tunnel statically configured in the user domain provided by the present invention, the IPTN service between two access points is implemented through the IPTN LSP tunnel statically configured without participation of the RM server, thereby greatly reducing the complexity of the network and simultaneously ensuring the bandwidth and QoS required by the service. In addition, if the RM issues the IPTN flow to the ER through the COPS, the IPTN flow dynamically issued through the COPS protocol is preferentially checked and forwarded in the ER, and the IPTN service is more flexibly realized.

Other advantages and modifications will readily occur to those skilled in the art, based upon the foregoing description. Therefore, the present invention is not limited to the above-described embodiments, and one aspect of the present invention is described in detail and exemplarily by way of example only. Those skilled in the art can substitute various equivalents for the above-described embodiments without departing from the spirit of the present invention, but such embodiments are to be construed as being included in the scope of the claims and their equivalents.

Claims

1. A method for realizing IPTN service includes:

establishing IPTN LSP tunnel between edge routers in advance;

an IPTN label or a label stack corresponding to the IPTN LSP tunnel is pre-configured in an edge router serving as a user domain, and a destination address or a network segment of the IPTN LSP tunnel is specified; and

for the service requested by the source terminal user on line from the user domain, the edge router forwards the service to the destination terminal according to the IPTN label or label stack of the IPTN tunnel corresponding to the requested service.

2. A method of implementing an IPTN service as claimed in claim 1,

reserving certain resources and specifying QoS parameters on the IPTN LSP tunnel.

3. A method of implementing an IPTN service as claimed in claim 2,

the edge router selects a tunnel matched with the destination IP address from the preset IPTN LSP tunnels according to the destination IP address, the protocol number or the source and destination port numbers of the service requested by the source terminal user.

4. A method of implementing an IPTN service as claimed in claim 3,

the edge router inserts a label or a label stack into a message header corresponding to the service requested by the source terminal user, and performs LSP forwarding.

5. A method of implementing an IPTN service according to any one of claims 1-4, wherein,

the IPTN system further includes a bearer control layer, and under the condition that the resource management server in the bearer control layer issues the IPTN flow to the edge router through the COPS protocol, the edge router preferentially checks and forwards the IPTN flow.

6. A system for realizing IPTN service includes,

the edge router is connected with the aggregation router and other edge routers by using a single LSP or a plurality of LSPs so as to establish an IPTN (IPTN-path) LSP tunnel between the edge routers; and

a terminal which requests IPTN service from the user domain corresponding to the edge router,

and the edge router forwards the service to the destination terminal according to the IPTN label or label stack of the IPTN tunnel corresponding to the requested IPTN service.

7. The system for implementing an IPTN service of claim 6, wherein,

and an IPTN label or a label stack corresponding to the IPTN LSP tunnel is pre-configured in an edge router corresponding to a user domain, a destination address or a network segment of the IPTN LSP tunnel is appointed, and certain resources and QoS parameters are reserved on the IPTN LSP tunnel.

8. The system for implementing an IPTN service of claim 7, wherein,

9. The system for implementing an IPTN service of claim 8, wherein,

10. A system implementing an IPTN service according to any one of claims 6-9, wherein,

the IPTN system further includes a resource management server, which issues the IPTN flow to the edge router through the COPS protocol, and the edge router preferentially checks and forwards the IPTN flow.