WO2005104450A1 - Procede de regulation du flux separe de signalisation et de media dans un reseau telephonique ip - Google Patents
Procede de regulation du flux separe de signalisation et de media dans un reseau telephonique ip Download PDFInfo
- Publication number
- WO2005104450A1 WO2005104450A1 PCT/CN2005/000373 CN2005000373W WO2005104450A1 WO 2005104450 A1 WO2005104450 A1 WO 2005104450A1 CN 2005000373 W CN2005000373 W CN 2005000373W WO 2005104450 A1 WO2005104450 A1 WO 2005104450A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- message
- value
- call
- gatekeeper
- metropolitan area
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/10—Architectures or entities
- H04L65/102—Gateways
- H04L65/1043—Gateway controllers, e.g. media gateway control protocol [MGCP] controllers
-
- 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/24—Traffic characterised by specific attributes, e.g. priority or QoS
- H04L47/2408—Traffic characterised by specific attributes, e.g. priority or QoS for supporting different services, e.g. a differentiated services [DiffServ] type of service
-
- 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/24—Traffic characterised by specific attributes, e.g. priority or QoS
- H04L47/2416—Real-time traffic
-
- 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/24—Traffic characterised by specific attributes, e.g. priority or QoS
- H04L47/2491—Mapping quality of service [QoS] requirements between different networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/1066—Session management
- H04L65/1101—Session protocols
- H04L65/1106—Call signalling protocols; H.323 and related
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M7/00—Arrangements for interconnection between switching centres
- H04M7/006—Networks other than PSTN/ISDN providing telephone service, e.g. Voice over Internet Protocol (VoIP), including next generation networks with a packet-switched transport layer
Definitions
- the present invention relates to a method for signaling and media offload transmission in the field of data communications, and in particular, to a method for offloading signaling and media in an IP telephone network based on the H.323 standard and including IP telephone, fax, and video services. Transmission method. Background technique
- H.323 signaling packets and media packets transmitted on the IP network with different TOS tag values on the IP header, and then using the TOS policy routing function on the border router, you can achieve all existing network conditions.
- H. 323 signaling and offload control of media packets.
- the T0S tag value still faces the following difficulties:
- the H.323 protocol stack uses the calling function provided by the operating system to complete the change of the T0S label, and for most mainstream operating systems today, the source code of these underlying calling functions is unfair, that is, The operation of adding a specific T0S label to an IP packet must conform to the operating system's processing rules for TCP / IP protocol packets, rather than when you want to label the T0S label when you want, you can put the T0S label at any time;
- the technical problem to be solved by the present invention is to provide a control based on the H.323 standard in an IP telephone network. Quasi-signaling and media offloading methods allow customers to conveniently and flexibly customize policies for gatekeepers and gatekeepers, border gateways and border gateways, between gatekeepers and border gateways, and between metropolitan areas within metropolitan area networks.
- H. 323 standard signaling and media packets transmitted between gatekeepers and border gateways outside the network are marked with TOS tags, so that customers can implement H. 323 standard signaling and media packets inside the metropolitan area network through routers. Implement policy routing based on TOS tag value.
- Another object of the present invention is to provide a method for controlling signaling and media distribution based on the H. 323 standard in an IP telephone network. It is pointed out that in the case of maintaining the status quo of the underlying call of the existing operating system, different methods for calling, Specific implementation methods for H. 323 standard-compliant signaling and media packets with TOS tag values.
- the present invention provides a method for controlling signaling and media offloading in an IP telephone network, which is applied to an IP telephone network based on the H.323 protocol.
- the method is characterized by using data on signaling messages and media messages. Discriminate according to the call flow rules of the H. 323 protocol, and set different TOS values for the signaling packets and media packets transmitted between the metropolitan area network of the IP telephone network and the IP phone network. Cooperating with the router, according to the different TOS values, policy routing is performed on signaling packets and media packets inside and outside the metropolitan area network, so as to realize the offloading of signaling and media in the IP telephone network.
- Step 1 Negotiate the T0S value of the local office and the outbound office of the metropolitan area network between the border gateway and the gatekeeper of the metropolitan area network; and configure the T0S policy routing on the router in the IP telephone network;
- Step 2 Establish a mapping table based on the TOS value on the gatekeeper, including the mapping table A between the TOS value and the calling and called number analysis field of the call, the mapping table B between the TOS value and the IP address of the gatekeeper outside the metropolitan area network. , And the mapping table C between the T0S value and the port monitored by the TCP link proxy process;
- Step 3 According to the mapping relationship in the mapping table C, start multiple TCP proxy processes, listen for external TCP link requests on multiple ports, and specify a mapping table C for each TCP proxy process during the port initialization stage. Corresponding T0S value;
- Step 4 By discriminating the data of the signaling message and the media message, according to the call flow rules of the H. 323 protocol, by looking up the corresponding mapping table, B and C are the internal and external locations of the metropolitan area network of the IP telephone network.
- the corresponding T0S values on the signaling packets and media packet tags in different transmission modes are transmitted; and through the cooperation of the gatekeeper and the router, the policy routing based on the TOS value is implemented to realize the offloading of signaling and media.
- the above method for controlling signaling and media distribution in an IP telephone network is characterized in that in step 1, the step of configuring a TOS policy routing on a router includes configuring a TOS on a metropolitan area network border router of the IP telephone network.
- the policy routing and TOS-first policy routing are configured on the backbone router.
- the method for controlling signaling and media distribution in the IP telephone network described above is characterized in that the TOS priority policy routing on the backbone network router is a strategy that uses calling number first analysis, and is first queried based on the calling number. No more query based on the called number, get and set the corresponding TOS value for routing.
- the above method for controlling signaling and media distribution in the IP telephone network is characterized in that, in step 4, for the LRQ message sent from the gatekeeper to the gatekeeper outside the metropolitan area network, according to the mapping in the mapping table A Relationship, the corresponding TOS value is obtained through the calling and called numbers in the message, and the corresponding TOS value is set on the IP header of the LRQ message.
- step 4 the gatekeeper receives an LRQ message from a gatekeeper outside the metropolitan area network according to the mapping in the mapping table B. Relationship, the corresponding T0S value is obtained through the IP address of the neighbor gatekeeper in the backbone network in the IP telephone network in the LRQ message, and the corresponding TOS tag value is set on the IP header of the reply LCF or LRJ message.
- the above method for controlling signaling and media offloading in the IP telephone network is characterized in that if the response is an LCF message, the mapping table G needs to be queried to find the port that the corresponding TCP link proxy process listens to according to the corresponding TOS tag value Fill in the LCF message and reply to the remote gatekeeper in the IP telephone network, indicating that the subsequent setup message of the remote end must be sent to the end monitored by the corresponding TCP link proxy process
- the above-mentioned method for controlling signaling and media distribution in the IP telephone network is characterized in that, in step 4, the Q. 931 message sent from the gatekeeper to the outside of the metropolitan area network is mapped according to the mapping relationship in the mapping table A through The called number in the first setup message in the Q. 931 message gets the corresponding T0S ⁇ The corresponding T0S value is set on the IP headers of all subsequent Q. 931 messages.
- step 4 the TOS value contained in the non-standard field in the ACF message returned by the gatekeeper to the border gateway is determined according to the following criteria:
- the TOS value contained in the non-standard field in the ACF message is the default value;
- the TOS value contained in the non-standard field in the ACF message is determined by querying the mapping table A according to the called number in the calling ARQ message;
- the TOS contained in the non-standard field in the ACF message will still be determined by querying the mapping table A according to the called number in the called ARQ message.
- the caller number in the ARQ message is analyzed, the TOS value corresponding to the caller number is determined by querying the mapping table A, and the priority flag corresponding to the TOS value is detected. If the TOS value is set as the priority selection, the priority will be given priority. Use this TOS value to fill non-standard fields of the ACF message.
- step 4 the border gateway sends a calling ARQ message to request address resolution, and then receives an ACF message returned by the gatekeeper, and the border gateway receives the ACF message from the gatekeeper.
- the TOS value is taken from the non-standard field of the message and stored, and it is checked whether the call signaling address contained in the ACF message is the IP address of the home gatekeeper. If so, it indicates that the call is a route call, and all subsequent Q.
- the TOS value in the IP header of the 931 message will use the default TOS value; if the call signaling address contained in the ACF message is not the IP address of the home gatekeeper, it indicates that the call is a direct call, and all subsequent calls.
- the TOS value on the IP header of the Q.931 message will use the TOS value in the non-standard field returned in the ACF message.
- the method for controlling signaling and media distribution in the IP telephone network described above is characterized in that in step 4, the border gateway sends a calling or called ARQ message to request address resolution, and then receives an ACF message returned by the gatekeeper.
- the gateway takes the TOS value from the non-standard field of the ACF message and saves it.
- the border gateway will use the saved T0S ⁇ in The corresponding T0S value is set on the IP header of all H.245 messages.
- the border gateway will use the default T0S.
- the corresponding TOS value is set on the IP headers of all H.245 messages sent to the upper-level gatekeeper.
- the gatekeeper receives the H.245 message from the border gateway, and queries the T0S value stored in the corresponding call.
- the corresponding T0S value is set on the IP packet header of the H.245 message and the H.245 message is forwarded to the remote end.
- the method for controlling signaling and media distribution in the IP telephone network described above is characterized in that, for a call occurring in the first metropolitan area network and the second metropolitan area network connected through the backbone network communication, the call route based on the TOS value is as follows:
- the border gateway of the second metropolitan area network sends an ARQ message to its home gatekeeper.
- the IP header of the ARQ message is set with the domain default value, and requests access authentication and address resolution.
- the gatekeeper of the second metropolitan area network determines whether the call is an area call or an area call according to the analysis of the called address, and queries the mapping table A according to the called number to obtain the corresponding TOS value. For an intra-area call, the ACF message is returned to the border gateway of the second metropolitan area network through access authentication. If the call is an inter-area call, an LRQ message is sent to the first metropolitan area network corresponding to the called address.
- the gatekeeper of the second metropolitan area network sends an LRQ message to the gatekeeper of the first metropolitan area network, requesting to provide an address translation, and according to the mapping relationship of the mapping table A, the corresponding TOS value is obtained through the calling and called numbers in the message.
- the corresponding TOS value is set for the IP header of the LRQ message, and is routed to the router of the backbone network corresponding to the corresponding TOS value through the TOS policy route, and then transmitted to the gatekeeper of the first metropolitan area network; the first city
- the gatekeeper of the local area network receives the LRQ message, queries the mapping table B according to the source IP field of the LRQ message, obtains the corresponding T0S value, and sets the corresponding T0S value for the IP header of the reply LCF or LRJ message; and if the reply It is an LCF message.
- mapping table C It is also necessary to query the mapping table C, find the port monitored by the corresponding TCP link proxy process according to the corresponding T0S value, fill it in the LCF message and reply to the gatekeeper of the second metropolitan area network, indicating that Subsequent setup messages of the second metropolitan area network must be sent to the port monitored by the corresponding TCP link proxy process;
- the gatekeeper of the second metropolitan area network After receiving the LCF message, the gatekeeper of the second metropolitan area network sends an ACF message to the border gateway of the second metropolitan area network, where the IP header T0S of the ACF message is the domain default value and the non-standard field T0S The value is a TOS value determined according to the criteria;
- the border gateway of the second metropolitan area network extracts the T0S value from the non-standard field of the ACF message returned, and checks whether the call signaling address contained in the ACF message is the IP address of the home gatekeeper. If so, it indicates that the A route call is a route call.
- the T0S value in the IP packet header of all subsequent Q. 931 messages will use the default T0S tag strip. If the call signaling address contained in the ACF message is not the IP address of the home gatekeeper, it indicates that This call is a direct call.
- the border gateway of the second metropolitan area network will use the saved T0S value to set the corresponding T0S value for the IP headers of all subsequent 245 messages.
- a metropolitan area network interacts with H.245 messages using a gatekeeper routing method.
- the border gateway of the second metropolitan area network will use the default T0S value for the IP header settings of all subsequent H.245 messages.
- the corresponding TOS value is determined by the superior of the border gateway Before forwarding the H.245 message, the gatekeeper queries the T0S value stored in the corresponding call and sets the corresponding T0S on all H.245 message IP headers. Value and forward the H.245 message to the far end;
- the border gateway of the second metropolitan area network sends a setup message to the call signaling address contained in the ACF message to initiate a call.
- the present invention introduces a complete set of rules on H.323 gatekeepers and border gateways, it is an H.323 signaling packet by discriminating data such as the calling IP address, calling number, and called number in the call signaling message.
- the media packets are labeled with different TOS values, and cooperate with routers in the IP telephone network to implement strategic routing for H. 323-based signaling packets and media packets within and outside the metropolitan area network based on different TOS values.
- Signaling and media offloading based on the H. 323 standard in the IP telephone network greatly enhances the security and maintainability of the IP telephone network, improves network execution efficiency, and offloads processing of signaling packets and media packets, audio packets, and video packets. It also provides the basis and control means for customers to optimize the allocation of network resources.
- FIG. 1 is a network system diagram according to an embodiment of the present invention
- FIG. 2 is a flowchart of the method of the present invention. Best way to implement the invention
- the present invention is applied to an IP telephone network system based on the H. 323 standard, in which the H. 323 protocol describes a system definition and a general control process for implementing multimedia communication on a packet network. It requires the support of a set of protocols, including call control protocols, media control protocols, and audio and video coding protocols. They combined with H. 323 constitute the technical standard of H. 323 system.
- the voice coding uses the ITU-T G series protocol, of which G. 711 is a mandatory coding method, and other commonly used coding methods are G. 723.1, G. 729A, and so on.
- Video coding uses H. 260 series protocols, such as H. 261, H. 263, etc. Audio and video encoded information are encapsulated in RTP and transmitted via UDP. The data communication adopts T. 120 protocol and is transmitted through reliable TCP.
- H. 225.0 and H. 245 are the two core protocols of the H. 323 system.
- H. 225.0 is mainly used for call control, while H. 245 is used to control the establishment, maintenance, and release of media channels.
- H. 225.0 is one of the core protocols of the H. 323 system. It consists of three parts: call control, RAS, and how to use RTP to encapsulate audio and video signals.
- H. 225.0's call control signaling originates from Q. . 931, its function is on H.323 endpoint (Including the terminal and the gateway) to establish a call connection, including the process of setting up and tearing down the call;
- RAS is an agreement between the endpoint and the gatekeeper, and mainly performs registration, positioning, and call admission management functions. It mainly includes the following protocol processes.
- Gatekeeper search Used for endpoints to automatically search for their home gatekeeper. Message used are GRQ (G a tek eeper Request, gatekeeper request), GRJ (Gateke printing er Reject, gatekeeper rejection), GCF (Gatekeeper Confirm, confirm gatekeeper). The endpoint uses the multicast address to send GRQ to find its own home gatekeeper, and the available home gatekeeper responds with GCF. After receiving the confirmation, the endpoint selects its own gatekeeper to obtain and record the RAS address of the gatekeeper for subsequent RAS messages.
- GRQ G a tek eeper Request, gatekeeper request
- GRJ Gateke printing er Reject, gatekeeper rejection
- GCF Gatekeeper Confirm, confirm gatekeeper
- Endpoint registration Used for the endpoint to register / deregister its own information with the home gatekeeper, including the alias address (E. 16 address or H. 323 identification) and call signaling transport layer address.
- the endpoint must register before it can initiate and accept calls.
- the registration indicates that the endpoint has joined a management area.
- the messages used for registration include RRQ (Registration Request), RCF (Registration Confirm), and RRJ (Registration Reject).
- the messages used for deregistration include URQ (Unregistration Request, registration request), UCF (Unregistration Confirm, registration confirmation), and URJ (Unregistration Reject, registration rejection).
- the endpoint registers with the searched home gatekeeper using RRQ. If the registration is successful, the gatekeeper responds with RCF.
- the endpoint registers with its own registered gatekeeper through URQ. After successful registration, the gatekeeper responds with UCF.
- Call admission Used for call access of gatekeeper control endpoints, including user access authentication and address resolution.
- the messages used are ARQ (Admission Request), ACF (Admission Confirm), and ARJ (Admission Reject X)
- ARQ Admission Request
- ACF Access Confirm
- ARJ Admission Reject X
- an endpoint When an endpoint initiates a call, it first sends an ARQ message to the home gatekeeper, which contains authentication information, the destination address, and the required bandwidth.
- the gatekeeper authenticates the user and resolves the destination address. If the gatekeeper agrees to initiate the call, it will return an ACF to the endpoint, including the allowed bandwidth and the translated call signaling transport layer address or the gatekeeper's Call signaling transport layer address (depending on whether direct routing or gatekeeper routing is used).
- H. 225.0 The call control protocol uses this call signaling transport layer address to initiate a call.
- the endpoint receives an incoming call request It also needs to send an ARQ message to its gatekeeper for authentication
- Positioning function It refers to requesting the gatekeeper to provide the address translation function.
- the messages used are LRQ (Location Request) and LCF (Location Confirm) LRJ (Location Reject).
- LRQ Location Request
- LCF Location Confirm
- LRJ Location Reject
- LRQ messages can be sent unicast or multicast.
- the gatekeeper of the target endpoint receives the LRQ message, the call signaling transport layer address of the endpoint or the call signaling transport layer address of the gatekeeper is returned to the requester through the LCF. Which address is sent back depends on whether the call signaling uses direct routing or gatekeeper routing.
- Bandwidth management It is used for the bandwidth determined by the endpoint or gatekeeper when the call admission is changed in the middle of the call.
- the messages used include BRQ (Bandwidth Request), BCF (Bandwidth Confirm), and BRJ (Bandwidth Reject).
- Status function It is used by the gatekeeper to query the endpoint or endpoint status information.
- the endpoint can also periodically report status information to the gatekeeper according to the settings.
- the messages used include IRQ (Info Request), IRR (Info Request Response), IACK (Info Request Ack)> INAK (Info Request Nak) 0 '
- Resource function Used by the gateway to report to the gatekeeper about its current available resources, including available capacity, supported protocols, and data rates.
- the messages used include RAI (Resource Available Indicatior, RAC (Resource Available Confirm)).
- a call can contain multiple media information (audio, video, etc.) at the same time, and each media information is transmitted on a logical channel.
- a H. 225.0 call control protocol is first used to establish a call connection between the caller and the callee, and at the same time an H. 245 control channel is established. Then use the H.245 control channel to establish different media channels (ie logical channels) according to the characteristics of the call, so that the multimedia information is transmitted on different media channels.
- the method includes the following steps:
- Step 10 Negotiate the local and outbound T0S values of the metropolitan area network between the border gateway and the gatekeeper within the metropolitan area network. For example, negotiate the interior of the metropolitan area network between the border gateway and the gatekeeper within the metropolitan area network.
- the default T0S value of H. 323 signaling packets and media packets is a; and T0S policy routing is configured on the border routers of the metropolitan area network and the routers of the backbone network.
- H. 323 signaling packets with a T0S tag value of a and Media packets are sent outside the metropolitan area network, and only H.323 signaling packets with a tag value of b0, c, d, etc. are allowed, and the corresponding backbone routers on the metropolitan area network outside the metropolitan area network.
- the router in the backbone network uses The TOS priority routing strategy performs routing, and directly finds the next hop address according to the T0S value.
- Step 20 A mapping table based on three T0S values is established on the gatekeeper. One is a mapping table between the T0S value and the calling and called number analysis fields of the call. A sheet is the T0S value and the neighbor gatekeeper outside the metropolitan area network. IP address mapping table B, a mapping table C between the T0S value and the port monitored by the TCP link proxy process.
- Step 30 According to the mapping relationship in the mapping table C, start multiple TCP proxy processes, listen to external TCP link requests on multiple ports, and specify a mapping table C for each TCP proxy process during the listening port initialization stage. The corresponding T0S value in. These TCP proxy processes are responsible for forwarding external TCP packets to the call signaling port actually used by the machine, and forwarding TCP packets returned by the machine to the external remote. In this way, the IP packet headers of the TCP response messages to which different remote TCP link requests are replied are marked with corresponding T0S tag values.
- Step 40 By discriminating the data of the signaling message and the media message, according to the call flow rules of the H.323 protocol, by searching the corresponding mapping table, B and C are the internal and external locations of the metropolitan area network of the IP telephone network. The corresponding T0S values on the signaling packets and media packet tags in different transmission modes are transmitted; and through the cooperation of the gatekeeper and the router, policy routing based on the TOS value is implemented to realize the offloading of signaling and media. .
- step 40 the following processes are mainly included:
- the border gateway of the second metropolitan area network sends an ARQ message to its home gatekeeper.
- the IP header of the ARQ message is set with the domain default value, and requests access authentication and address resolution.
- the gatekeeper of the second metropolitan area network receives the ARQ message, determines whether the call is an area call or an area call according to the analysis of the called address, and queries the mapping table A according to the called number to obtain the corresponding T0S value, and If the call is an intra-area call and passes access authentication, an ACF message is returned to the border gateway of the second metropolitan area network. If the call is an inter-area call, an LRQ message is sent to the first city corresponding to the called address. Gatekeeper of the domain network.
- the gatekeeper of the second metropolitan area network sends an LRQ message to the gatekeeper of the first metropolitan area network, requesting to provide address translation, and according to the mapping relationship of mapping table A, the corresponding callee and called numbers in the message are used to obtain the corresponding
- the T0S value is set to the corresponding T0S value for the IP header of the LRQ message, and is routed to the router of the backbone network corresponding to the corresponding T0S value through the T0S policy route, and then transmitted to the gatekeeper of the first metropolitan area network.
- the gatekeeper of the first metropolitan area network receives the LRQ message, queries the mapping table B according to the source IP field of the LRQ message, obtains the corresponding TOS value, and sets the IP packet header of the reply LCF or LRJ message.
- the gatekeeper of the metropolitan area network instructs that the subsequent setup message of the second metropolitan area network must be sent to the listening port of the corresponding TCP link proxy process.
- the gatekeeper of the second metropolitan area network After receiving the LCF message, the gatekeeper of the second metropolitan area network sends an ACF message to the border gateway of the second metropolitan area network, where the IP header T0S value of the ACF message is the domain default value, which is non-standard
- the TOS value of the field is the TOS value determined according to the criteria.
- the border gateway of the second metropolitan area network extracts the T0S value from the non-standard field of the returned ACF message, and checks whether the call signaling address contained in the ACF message is the IP address of the home gatekeeper. If yes, It indicates that the call is a routing call.
- the T0S value on the IP header of all subsequent Q. 931 messages will use the default T0S tag ⁇ If the call signaling address contained in the ACF message is not the IP of the home gatekeeper The address indicates that the call is a direct call.
- the T0S value on the IP header of all subsequent Q. 931 messages will use the T0S value in the non-standard field returned in the ACF message.
- the border gateway of the second metropolitan area network When the first metropolitan area network interacts with H.245 messages, the border gateway of the second metropolitan area network will use the saved T0S value to set the corresponding T0S value for the IP headers of all subsequent H.245 messages; when the The way in which H.245 messages are exchanged between the road call and the first metropolitan area network adopts the gatekeeper routing method.
- the border gateway of the second metropolitan area network will use the default T0S value for all subsequent H.245 messages. IP header settings
- the corresponding T0S value should be queried by the upper gatekeeper of the border gateway before forwarding the H.245 message, and the corresponding T0S value stored in the corresponding call should be queried.
- the corresponding T0S value should be set on all H.245 message IP headers and sent to The far end forwards the H.245 message.
- the border gateway of the second metropolitan area network sends a setup message to the call signaling address included in the ACF message to initiate a call.
- H. 323GK Gatekeeper in H. 323 protocol
- GW border gateway device
- POP POP router
- IAD Integrated Access Equipment
- the H.323GK in the first metropolitan area network is hereinafter referred to as GK1, and the H.323Gk in the second metropolitan area network is hereinafter referred to as the GK1.
- This embodiment involves the following rules:
- Tel 1 1011 beginning at a first metropolitan area network, a voice call: (0-5) XX 1011; Video phone number: 1011 (6-9) XX; video conferencing, the number: 011 ⁇ ⁇ .
- the IP address of the gateway GW1 (in the first metropolitan area network): 210.51.195.11, assuming a voice terminal, number: 1011111, and a video terminal: 1011999 respectively.
- the next hop address at T0S 2-5 is R2
- the router in the backbone network uses the T0S priority routing policy to route according to the IP address and TOS, and finds the peer address, which greatly improves the communication quality.
- H.323GK enables three ports 1722, 1724 and 1726 (optional non-special ports can be used) to listen to external TCP requests.
- T0S 5
- 1726 corresponds to TOS 2 7. Therefore, when the process initializes, the T0S values bound to the three ports 1722, 1724, and 1726 are 5, 6, and 7, respectively.
- a phone in the second metropolitan area network 1022999 dials the phone in the first metropolitan area network 1011999 (a cross-domain video call), and its T0S route is as follows:
- GW2 sends an ARQ message to GK2, and sets the domain default T0S value to 0.
- GK2 receives the ARQ message and knows that the called number is a cross-domain call. Is 6.
- GK2 sends an LRQ message, and finds that the TOS value is 6 according to the address of the neighbor gatekeeper GK1.
- the IP header of LRQ is marked with T0S equal to 6, and sent to router 6 in backbone network 2.
- GK1 receives the LRQ message and checks the B table according to the source IP field of LRQ:
- GK2 After receiving the LCF, GK2 sends ACF to GW2.
- the ACF header T0S is 0, and the non-standard field T0S value is the TOS value 6 found in step (2).
- the IP headers of H.245 messages sent by GW2 are marked with T0S value 6.
- GW2 sends a setup message with a T0S value of 0 in the IP header.
- GK2 forwards the setu message, and finds that the T0S value is 6 according to the called number, and sends it to router 6 in backbone network 2.
- Router 6 forwards it to GK1 according to the IP address and T0S value policy, and GK1 forwards it to GW1.
- GW1 sends an ARQ message to GK1.
- the IP packet header T0S value is 0. It looks up the calling number list (terminal number in the non-metropolitan area network), there is no matching entry, and then according to the called number in the message, the T0S value is equal to 6. .
- GK1 returns ACF to GW1, the TOS value of the IP header is 0, and the T0S value of the non-standard field is 6 found in step (7). Thereafter, the IP headers of the H.245 messages sent by GW1 are marked with a T0S value of 6 and pass through the backbone network two routes.
- the video terminal 1200222 in the second backbone network dials the voice terminal 1011111 in the first metropolitan area network.
- the T0S value is 5 according to the called number, and subsequent H.245 messages will be marked with a T0S value of 5 through a route of the backbone network, and the call may not be connected. Therefore, it is necessary to use the calling number first analysis strategy, that is, first check the calling number table (terminal numbers in non-metropolitan area networks). If it cannot be found, route based on the T0S value of the called number.
- the present invention introduces a complete set of rules on H.323 gatekeepers and border gateways, it is an H.323 signaling packet by discriminating data such as the calling IP address, calling number, and called number in the call signaling message.
- the media packets are labeled with different TOS values to implement H.323 standard signaling and media offloading in the IP telephone network, which greatly enhances the security and maintainability of the IP telephone network, improves network execution efficiency, and signaling packets.
- Streaming processing with media packets, audio packets, and video packets also provides the basis and control means for customers to optimize network resource allocation.
- the method of the present invention is suitable for the offload transmission of signaling and media in an IP telephone network including services such as IP telephone, fax, and video based on the H.323 standard.
- the method of the present invention is also suitable for other related fields with similar functional requirements.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Multimedia (AREA)
- Business, Economics & Management (AREA)
- General Business, Economics & Management (AREA)
- Quality & Reliability (AREA)
- Telephonic Communication Services (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Description
Claims
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP05730399A EP1755287A1 (en) | 2004-04-21 | 2005-03-24 | A method for controlling the separated flow of signaling and media in ip telephone network |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN200410009033.9A CN1564562B (zh) | 2004-04-21 | 2004-04-21 | 一种控制ip电话网中信令、媒体分流的方法 |
CN200410009033.9 | 2004-04-21 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2005104450A1 true WO2005104450A1 (fr) | 2005-11-03 |
Family
ID=34477777
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2005/000373 WO2005104450A1 (fr) | 2004-04-21 | 2005-03-24 | Procede de regulation du flux separe de signalisation et de media dans un reseau telephonique ip |
Country Status (3)
Country | Link |
---|---|
EP (1) | EP1755287A1 (zh) |
CN (1) | CN1564562B (zh) |
WO (1) | WO2005104450A1 (zh) |
Families Citing this family (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101043441A (zh) * | 2006-03-24 | 2007-09-26 | 华为技术有限公司 | 服务类型值确定方法及其装置、以及分组网络 |
CN101883393B (zh) * | 2009-05-07 | 2013-01-09 | 华为技术有限公司 | 分组业务数据的传输方法、装置和系统 |
CN101854663A (zh) * | 2010-04-30 | 2010-10-06 | 华为技术有限公司 | 数据传输设备、方法以及通信系统 |
CN102984402B (zh) * | 2011-09-06 | 2015-08-12 | 中兴通讯股份有限公司 | 一种VoIP数据包的处理方法及系统 |
EP2780327A1 (en) | 2011-11-14 | 2014-09-24 | Cadila Healthcare Limited | Polymorphic forms of ivabradine hydrochloride |
CN115242760B (zh) * | 2022-07-20 | 2023-12-26 | 深圳市灵镜技术有限公司 | 一种基于WebRTC的SFU系统及方法 |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2001189754A (ja) * | 1999-12-28 | 2001-07-10 | Toshiba Corp | QoS提供方式、ルータ装置、QoSサーバ、ユーザ端末及びQoS提供方法 |
US6650644B1 (en) * | 1998-05-20 | 2003-11-18 | Nortel Networks Limited | Method and apparatus for quality of service translation |
KR20040027175A (ko) * | 2002-09-27 | 2004-04-01 | 주식회사 케이티 | 전송제어프로토콜/인터넷프로토콜 네트워크에서 에지라우터의 트래픽 처리 방법 및 기록매체 |
Family Cites Families (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2001024662A (ja) * | 1999-07-09 | 2001-01-26 | Nec Commun Syst Ltd | 通信制御方式 |
JP3639556B2 (ja) * | 2001-12-12 | 2005-04-20 | 富士通株式会社 | VoIPネットワークの輻輳制御システム |
-
2004
- 2004-04-21 CN CN200410009033.9A patent/CN1564562B/zh not_active Expired - Fee Related
-
2005
- 2005-03-24 WO PCT/CN2005/000373 patent/WO2005104450A1/zh active Application Filing
- 2005-03-24 EP EP05730399A patent/EP1755287A1/en not_active Withdrawn
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6650644B1 (en) * | 1998-05-20 | 2003-11-18 | Nortel Networks Limited | Method and apparatus for quality of service translation |
JP2001189754A (ja) * | 1999-12-28 | 2001-07-10 | Toshiba Corp | QoS提供方式、ルータ装置、QoSサーバ、ユーザ端末及びQoS提供方法 |
KR20040027175A (ko) * | 2002-09-27 | 2004-04-01 | 주식회사 케이티 | 전송제어프로토콜/인터넷프로토콜 네트워크에서 에지라우터의 트래픽 처리 방법 및 기록매체 |
Also Published As
Publication number | Publication date |
---|---|
EP1755287A1 (en) | 2007-02-21 |
CN1564562A (zh) | 2005-01-12 |
CN1564562B (zh) | 2011-04-06 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7920690B2 (en) | Interworking of multimedia and telephony equipment | |
US9185142B2 (en) | System and method for providing alternate routing in a network | |
US7957517B2 (en) | Method and apparatus for providing internet protocol call transfer in communication networks | |
US7460548B2 (en) | Optimally interworking SIP and QSIG call diversion and transfer | |
WO2006026901A1 (fr) | Systeme de traitement de signal de service de domaine de paquet et procede utilisant ce systeme | |
US20070058787A1 (en) | Centralized Feature Platform In A Packetized Network | |
WO2003030463A1 (fr) | Procede et systeme pour la prestation d'un service vocal ip sur un reseau prive | |
WO2005104450A1 (fr) | Procede de regulation du flux separe de signalisation et de media dans un reseau telephonique ip | |
KR100727069B1 (ko) | Sip 기반의 무선 패킷 교환망 시스템에서의 타망 연동방법 및 그 시스템 | |
US6901080B1 (en) | System and method for providing an intermediary layer for VoIP call pipe establishment | |
US6961332B1 (en) | Multiple appearance directory number support across packet- and circuit-switched networks | |
KR101606142B1 (ko) | 음성패킷망에서 네트워크 주소 번역 통과를 지원하기 위한 장치 및 방법 | |
US8711707B2 (en) | Integrating multimedia capabilities with circuit-switched calls | |
US20170318062A1 (en) | Method for setting up a communication link | |
EP1436963B1 (en) | Method, apparatus and computer program for selecting a media gateway control function based on the monitoring of resources of media gateway functions | |
US20070041357A1 (en) | Interworking of hybrid protocol multimedia networks | |
Cisco | H.323 Applications | |
Cisco | Enhancements to the Session Initiation Protocol for VoIP on Cisco Access Platforms | |
US8705518B1 (en) | Apparatus and method for controlling services and operations in converged communications networks | |
Cisco | Session Initiation Protocol (SIP) for VoIP | |
US7899032B1 (en) | Third party service support with a voice over internet protocol (VoIP) network | |
Jones | h. 323 protocol overview | |
JP2006229550A (ja) | VoIP−GW装置 | |
KR100809398B1 (ko) | 멀티프로토콜을 지원하는 VoIP에서의 SMS 전송방법 및 그 시스템 | |
KR20070047593A (ko) | 이기종 망간 연동하는 화상통화 시스템 및 방법 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AK | Designated states |
Kind code of ref document: A1 Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BW BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE EG ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NA NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SM SY TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW |
|
AL | Designated countries for regional patents |
Kind code of ref document: A1 Designated state(s): BW GH GM KE LS MW MZ NA SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LT LU MC NL PL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWW | Wipo information: withdrawn in national office |
Country of ref document: DE |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2005730399 Country of ref document: EP |
|
WWP | Wipo information: published in national office |
Ref document number: 2005730399 Country of ref document: EP |