CN102413147A - Agent server - Google Patents
Agent server Download PDFInfo
- Publication number
- CN102413147A CN102413147A CN201110440378XA CN201110440378A CN102413147A CN 102413147 A CN102413147 A CN 102413147A CN 201110440378X A CN201110440378X A CN 201110440378XA CN 201110440378 A CN201110440378 A CN 201110440378A CN 102413147 A CN102413147 A CN 102413147A
- Authority
- CN
- China
- Prior art keywords
- user agent
- type
- ipv6
- address
- message
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000004891 communication Methods 0.000 claims description 14
- 230000005540 biological transmission Effects 0.000 claims description 13
- 238000000034 method Methods 0.000 abstract description 18
- 238000004590 computer program Methods 0.000 abstract description 7
- 230000000977 initiatory effect Effects 0.000 abstract description 2
- 239000003795 chemical substances by application Substances 0.000 description 173
- 239000008186 active pharmaceutical agent Substances 0.000 description 19
- 238000012545 processing Methods 0.000 description 10
- 238000005516 engineering process Methods 0.000 description 4
- 238000012546 transfer Methods 0.000 description 4
- 238000006243 chemical reaction Methods 0.000 description 3
- 238000011160 research Methods 0.000 description 3
- 230000011664 signaling Effects 0.000 description 3
- 230000006978 adaptation Effects 0.000 description 2
- 230000002349 favourable effect Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 108091023037 Aptamer Proteins 0.000 description 1
- 230000003213 activating effect Effects 0.000 description 1
- 238000013459 approach Methods 0.000 description 1
- 230000000903 blocking effect Effects 0.000 description 1
- 230000003247 decreasing effect Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000009977 dual effect Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000005538 encapsulation Methods 0.000 description 1
- 239000000284 extract Substances 0.000 description 1
- 230000002452 interceptive effect Effects 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000005457 optimization Methods 0.000 description 1
- 238000000926 separation method Methods 0.000 description 1
- 230000005641 tunneling Effects 0.000 description 1
Images
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/1066—Session management
- H04L65/1069—Session establishment or de-establishment
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/09—Mapping addresses
- H04L61/25—Mapping addresses of the same type
- H04L61/2503—Translation of Internet protocol [IP] addresses
- H04L61/251—Translation of Internet protocol [IP] addresses between different IP versions
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/09—Mapping addresses
- H04L61/25—Mapping addresses of the same type
- H04L61/2503—Translation of Internet protocol [IP] addresses
- H04L61/2542—Translation of Internet protocol [IP] addresses involving dual-stack hosts
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/09—Mapping addresses
- H04L61/25—Mapping addresses of the same type
- H04L61/2503—Translation of Internet protocol [IP] addresses
- H04L61/256—NAT traversal
- H04L61/2564—NAT traversal for a higher-layer protocol, e.g. for session initiation protocol [SIP]
-
- 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
-
- 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/1104—Session initiation protocol [SIP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
- H04L69/167—Adaptation for transition between two IP versions, e.g. between IPv4 and IPv6
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Business, Economics & Management (AREA)
- General Business, Economics & Management (AREA)
- Multimedia (AREA)
- Computer Security & Cryptography (AREA)
- Telephonic Communication Services (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Small-Scale Networks (AREA)
Abstract
The method involves inserting an indicator, representative of type of address associated to a user agent included in one of two heterogeneous nodes, in a contact field of a session initiation protocol (SIP) request message transmitted by the user agent. The indicator is a coded digital value representative of internet protocol version 4 (IPv4), internet protocol version 6 (IPv6) or IPv4 and IPv6 protocols designated as double stack. Independent claims are also included for the following:a carrier signal of a request message comprising an indicator; a system for transmitting data between heterogeneous nodes; and a computer program comprising program code instructions for implementing data transmitting method.
Description
This case be that February 15, application number in 2007 are 200780007096.2 the applying date, denomination of invention divides an application for the application for a patent for invention of " method and system of characterising heterogeneous communication nodes ".
Technical field
The field of the invention is a field of telecommunications, more specifically, is the IP phone field.
Background technology
How People more and more uses Internet Protocol (IP) network as the unified support means for a large amount of services and application.For many operators of selecting this agreement, IP has born associating person's role, is used for making the service of previous separation to lean on each other for support.
The IPv4 version of Internet Protocol used several years.
In order to satisfy the restriction that this type of communication service applies; More specifically; In order to adapt to the demand growth of aspect, address, operator and network equipment manufacturer join together, and have formulated communication protocol of new generation; Be called IPv6, it is by being in the ripe specification and the analytical documentation definition that must be enough to make it it is contemplated that the development phase that the operation in carrier network is disposed now.
But introducing should a new generation's agreement cause significant problem, and these problems relate to needs and guarantee the IPv6 agreement and be deployed in interoperability and the interconnection (interwork) between the IPv4 agreement in the IP network.In the current generation of prior art, people have proposed the solution to these problems, but these solutions have following shortcoming, and its operation is on " service " level (specifically on application layer) not only, and on " transmission " level (on the IP layer).In transport layer, internet engineering ad hoc working group (IEFT) proposed and standardization some mechanism, for example NAP-PT technology, and various tunneling technique, its with the IPv6 data encapsulation in the IPv4 datagram or opposite.
In addition, must upgrade and aptamers architecture and service platform, transparent as much as possible for the end user with the interconnection that enables between the client that is arranged in dissimilar (IPv4 and IPv6) IP world.
In other multimedia activities, IEFT standardization SIP (SIP), its major function is for initiating, revise and the termination Multimedia session.The interesting example that SIP uses for the present invention.It is used for producing the description to the parameter relevant with associated session based on service describing agreement (SDP).In case the success of the negotiation between the calling both sides, then both sides can come switched-media stream through activating real-time transport protocol (rtp).The RTP session parameter is decided through consultation through SIP signaling message (mainly in the SDP part) in advance.They mainly are end address and the port numbers of using at the arbitrary end of the communication link that will be provided with place.
Since in request comment (RFC) 2543, having described first version of SIP, it is just compatible with IPv6.In theory, the realization meeting of SIP is decoded ip v4 and IPv6 address easily, and it be directed in the head such as specific fields such as " CONTACT " (contact) head or SDP part.But,, that is,, then exist this type of address to stop SIP is set and call out if one has the IPv4 address and another has the IPv6 address if two terminals all can't be got in touch under identical IP world.Thus; When the IPv4 user agent initiates the IP session with IPv6 user agent A (it locates to register at IPv4 location-server (being also referred to as " registration side " R)); Result's sip message exchange is shown in Fig. 1 a, and its peculiar IPv4 address of first user agent A use of wherein seeking to get in touch the second user agent B is to acting server PS transmission " INVITE " (invitation) message.Here, acting server PS is attached to the environment that has only IPv4.In case acting server PS receives this message, then acting server is submitted inquiry to location-server (being also referred to as registrar), to obtain the address of the second user agent B.Under current hypothesis, this address is the IPv6 address, and has only the IPv4 type owing to acting server PS belongs to, so acting server PS does not know the route of this destination.Then, send error message, can not between the first user agent A and the second user agent B, the SIP session be set to indicate to user agent A.This error message is " (2) 404 No Route " (no route) message shown in Fig. 1 a.
Can get in touch the positioning address of the first user agent A and the positioning address of the second user agent B if suppose acting server PS now, another sip message exchange then can take place, wherein the second user agent B attempts the first user agent A, shown in Fig. 1 b.
In this case, acting server PS will send the positioning address of the first user agent A from " INVITE " message route that the second user agent B receives to.Should " INVITE " message comprise SDP and propose, it has also described RTP port numbers and address that the second user agent B can be used for sending and receiving rtp streaming outside the codec (encoder/decoder) that the second user agent B proposes.In Fig. 1 b, this address is the IPv6 address.Thus, when the first user agent A received this " INVITE " message, it can only refuse open session, because it is the IPv4 client.Depend on it and how to realize, it can connect with the network of indicating its IP address of not supporting the second user agent B to the back error message at most.Thus, in above any one example, all the SIP session can't be set with reference to Fig. 1 a and Fig. 1 b description.
Dissimilar IP address coexistences may influence and above those calling different call with graphical display and description.Thus, also may terminate in the Media Stream exchange to the calling of two stack (DS) clients, wherein the DS user agent can process IP v4 and IPv6 address style.This is to be used for sending perhaps only IP address of receiving media stream because basic SIP is suitable for indicating.In order to overcome this problem, RFC 4092 introduces new semantic feature, comprises " sdp-anat " sign, so that the user agent can announce and/or find one or more address style.Thus, the DS user agent can indicate its IPv4 address and IPv6 address in its STP proposes.Through this technology, from or whereabouts DS user agent and whereabouts or from the single version client (promptly only with the IPv4 protocol-compliant, or only with the client of IPv6 protocol-compliant) the all-calls SIP session that can successfully terminate.
Two nodes that send the communication link end of deciding calling in intention to are under the situation of single version node; Relevant SIP phone service provider can use ALG (ALG) to use; Revise SDP and propose, to guarantee address style of being supported and the consistency between the type that in the sip message of receiving, comprises.For this purpose, sip server use about transport layer and be not the peculiar information of SIP, come route to transmit and call out, perhaps decision uses ALG should be used for changing the content that SDP proposes.This class behavior of sip server is not covered by standard.
Generally speaking, also not research at length and the relevant problem of interconnection two isomery user agents (being the user agent of different IP type) of telecommunications industry.Particularly, except that the ANAT that in RFC 4091 and RFC 4092, describes proposes (it has solved subproblem), there is not the behavior of IETF document description sip server to come route to transmit the calling that is connected two user agents under two different IP environment.
In addition, prior art has following shortcoming:
-use ALG application and additional function not by documenting; Acting server PS does not have the means of RFC 3261 appointments to promote this task;
-acting server PS must use from the information of network layer (in this document, being also referred to as transport layer) and carry out the judgement about service layer; Therefore, it must consider address outside the source address of message, that be used for the contact agent server, perhaps checks the SDP part; This can cause the risk that makes agency's (it is by the pre-configured seeervice level information of only handling) decreased performance;
-use these addresses not optimised: a kind of method of the session of achieving success is to make two user agents that participate in calling out can both have two types address; Thereby SDP negotiation is success always, but this can cause the problem (especially among IPv4s) of optimization to the utilization of operator's available address space.
-solution is not general: call out the route transmission by acting server PS and depend on the interconnection solution in the transport layer deploy with the idea of interfering.
-acting server PS can't confirm that the user agent belongs to IPv4, IPv6, still is the DS type.
The inventor obtains to draw a conclusion through practice: although from above research, demand occurred; But under the current state of prior art; There is not simple method to make the communication component in the IP communication network can discern the address style related with given user agent; This most of technology of just having explained the calling between the management heterogeneous nodes of people's current research why all has a weak point, and does not have to handle and enable the demand for services that isomery is called out.
When proposing to enable easily to discern the transfer approach of the address style that given user agent supports, the invention provides a kind of solution that does not have above shortcoming.
Summary of the invention
The method feature that is used between heterogeneous nodes transmitting data of the present invention is; The method includes the steps of: before the communication session that is provided with between the said node; In a said node; Type indicator is inserted in the message of being sent by the user agent, and said type indicator is represented the type of the address related with said user agent.
The invention provides a kind of immediate mode and discern incompatible risk between two types the user agent that must intercom mutually, and consider and if necessary then overcome this type of incompatibility.
Particularly; The present invention makes such as above-mentioned acting server can discern two types the user agent that must intercom mutually rapidly; Thereby said server can be discerned and dispose the required resource of communication session that is provided with effectively between those agencies in suitable place, and no matter whether these agencies belong to same type.
" type " of claiming the user agent here refers to one or more version (for example IPv4, IPv6) of the Internet Protocol that (a plurality of) network interface of the SIP node that the user agent can be through holding it uses.If user agent's type that node A is held is different with user agent's type that Node B is held, claim that then two node A and B are isomeries.
Thus, agreement of the present invention can further comprise following steps: according to three kinds of IP types: pure IPv4, pure IPv6, or two stack, sort out the user agent of transmission types designator.
In one particular embodiment of the present invention, propose to carry out said inserting step by said user agent.
This makes the user agent can its calling of sending or receiving be limited to corresponding network interface and Internet Protocol type.
Advantageously, type indicator can adopt the form of coded numeric value, its expression IPv4 agreement, IPv6 agreement, perhaps two stack (IPv4+IPv6) agreement.
Therefore this type of digital value can realize that the present invention can not cause any remarkable increase of the size of message that exchanges from call intent easily with several bits of encoded.
In the of the present invention first favourable variant, said method further comprises following steps: the identifier with the associated user agency is stored said type indicator.
In many situation, this storing step is created in database and is being upgraded reference table, be used for easily Direct Recognition with stored each user agent's IP address associated type of type indicator for it.This database can spontaneously be presented when initialization connects by each user agent; Perhaps present through being updated periodically; And by the positioning service management, the user agent registers at this location-server when the initialize communications session or when registration period is expired.
In the second favourable variant that can replace or be used in combination of the present invention with first variant; Said method further can comprise: at the type indicator that is associated with the user agent who has sent said invitation message and be associated with under the situation incompatible between destination user agent's the type indicator of said invitation message, and the step of the address that conversion comprises in inviting the message of communicating by letter that gets into the user agent.
According to this variant of the present invention, make it just can compensate therebetween any incompatible before attempting to set up connection between caller and the callee even relatively act on behalf of related type indicator simply with caller and called subscriber.
For example, advantageously, the present invention is used to be called the IP phone application of VoIP (the last voice of IP), perhaps usually is grouped under the item of talk service.
Like this, the invention solves general considerations RFC 3162 definition and that dispose with IPv6 client both for the IPv4 client, that serve based on the signaling of SIP.These services can be voice, video, scene (presence) or the like services.
As stated, the present invention proposes a kind of simple mechanism, help being attached to the IPv4 territory, another is attached between the isomery client in IPv6 territory the SIP session is set at one.
The application of the invention; Sip proxy server can route transmit the SIP calling; And can intervene the content of proposing, thereby enable between heterogeneous nodes, to be provided with session with SID that transmit, RFC 2327 definition in modification (or making it to revise) sip message.On the contrary; If do not realize the present invention; Then the information outside the necessary access application layer of sip proxy server is specially the information that relates to network layer, to instruct its selective call route and to optimize the use of ALG being used (it is responsible for revising the SIP session of sip message to succeed).If do not use the isomorphism protocol stack, then to use under the situation of nonintervention at sip server and ALG, some SIP session can't take place.
The present invention allows interconnecting heterogeneous SIP node, and simplifies and therefore promoted the calling route in the SIP telecommunication system.
Particularly, the present invention has optimized the use to the IP address, and do not require sip proxy server to the processing of sip message to depend on the desired processing of the sip message that comes determining server to receive from the information of transport layer.
Among the distinctive a kind of embodiment of the example application of institute's reference, can type indicator be inserted in " CONTACT " field that comprises in the SIP query messages herein.
Type indicator is introduced the type that query messages can be notified the IP address that network interface available among location-server and the acting server user agent supports.In addition, acting server can use the type designator to handle query messages then, thereby its route is sent to its destination, and without the information in the accesses network layer.
The invention described above first variant transposing is applied to this example can be obtained the user agent its type indicator is inserted in " REGISTER " message.
Thus, when receiving " REGISTER " message, location-server advances to storage registered address, registration obsolete address and type indicator.It also can store other data.
The invention described above second variant transposing is applied to this example can obtains under situation incompatible between the type indicator that is associated with the user agent who has sent said " INVITE " message and the destination user agent's who is associated with said " INVITE " message the type indicator address that acting server conversion comprises in " INVITE " message.
Particularly, belong to dissimilar, then can produce this type of incompatibility if send and receive the user agent of " INVITE " message.
In of the present invention this type of used, between two dissimilar user agents, must use the gateway on the application layer to call out the route processing to carry out this type of processing below the acting server execution basis of revising message related to calls:
-or according to the classification of in the registration database of and character that comprise caller and called subscriber Agent Type that upgrade by location-server, storing;
-perhaps act on behalf of the type indicator that comprises in " INVITE " message of transmission according to the classification of in the registration database of the character that comprises called subscriber's Agent Type, storing and the calling subscriber.
Can find out from above description; As through its in above-mentioned application realization and directly the acquisition product; The invention still further relates to and carry any signal comprise expression and the query messages of the type indicator of the character of user agent's IP address associated of sending this message, this message for example can be " REGISTER ", " INVITE ", perhaps " 200OK " message.Particularly, can type indicator be inserted in " CONTACT " field.
Hardware aspect of the present invention relates to a kind of system that between heterogeneous nodes, transmits data; Being characterised in that this system comprises is used for following parts: before the communication session that is provided with between the said node; In a said node; Type indicator is inserted in the message of being sent by the user agent, and said type indicator is represented the type of the address related with this user agent.Hardware aspect of the present invention also relates to the terminal that forms such data communication system; Comprise and be used for following parts: at said node; Type indicator is inserted in the message of being sent by the user agent, and said type indicator is represented the type of the address related with this user agent.
A kind of variant of hardware aspect of the present invention relates to above-mentioned transfer system; Further comprise and be used for following parts: according to the agency's who sends query messages type indicator and the database that is used for storing said classification, classification and the said user agent of classification.
The another kind of variant of hardware aspect of the present invention relates to above-mentioned transfer system, further comprises to be used for following parts: relatively the calling subscriber agency acts on behalf of peculiar type indicator with the called subscriber.
Be configured to realize that another aspect of the present invention of parts of the present invention relates to a kind of computer program, comprise a series of code instructions, when said program is carried out, be used for carrying out the particular step of said method in computer.
Particularly, the present invention provides a kind of acting server, has to be used for the device that route SIP calls out between calling subscriber agency and called subscriber agency, it is characterized in that it also comprises with lower device:
-be used to discern the device of said two user agents' IP address class type (IPv4, IPv6, or comprise two stacks of IPv4 and IPv6), said identification based on:
For current or former calling, act on behalf of the IP address class type designator that comprises in " CONTACT " field that comprises in the SIP query messages of transmission by the calling subscriber;
The classification of in the registration database that comprises called subscriber's Agent Type, storing,
-be used to discern and when suitable, be deployed in the device of effectively setting up the necessary resource of communication session between those two user agents.
Acting server also comprises with lower device: type that the said caller of Classification and Identification that is used for storing based on the registration database that is upgraded by location server and called subscriber act on behalf of and the device that comprises said two user agents' type.
Acting server also comprises with lower device: be used for device that the content that the SDP that transmits at the sip message that has each other between two user agents of different types proposes is made amendment or it is modified.
Description of drawings
From the description that provides as the indefiniteness example below in conjunction with accompanying drawing, can understand the present invention better, wherein:
Fig. 1 a and 1b relate to prior art;
Fig. 2 shows the flow chart of the basic step of the inventive method as explanation;
Fig. 3 shows first example of registration IPv4 and IPv6 user agent as explanation;
Fig. 4 shows second example of the two stack user agents of registration as explanation; And
Fig. 5 shows system of the present invention, is used for interconnecting heterogeneous SIP node, and it moves under following situation: the user agent sends " REGISTER " (registration) message and gives and locate server, and acting server is passed through in the transfer of " INVITE " (invitation) message.
Embodiment
Following with reference to Fig. 2 and accompanying drawing subsequently, method of the present invention is described in more detail.
In general; Each heterogeneous nodes that is for example formed by IPv4, IPv6, perhaps two stack (DS) hybrid IP terminal all comprises the user agent UA of particular type, the version of the IP that (a plurality of) network interface that the type can be used through associated terminal corresponding to the user agent can use.
As shown in Figure 2, method of the present invention in step 10, is inserted type indicator " atypes " in the query messages M that user agent UA sends.After this inserted, query messages was expressed as M (" atypes ").This type of query messages for example comprises to the registration message of location-server (being also referred to as " registration side ") R.Also the message that sends to acting server PS can be arranged, for example point out the message of communicating by letter that gets into another user agent.
After the message of type indicator had wherein been inserted in transmission (13), the time designator " atypes " that method of the present invention comprises according to query messages M (" atypes ") was handled (11) query messages M (" atypes ").This processing is carried out in unit 12, and unit 12 can perhaps be used to point out the acting server of entering with another user agent's the message of communicating by letter for the location-server that is used for registration message.
Processing 11 routes of in acting server 12, carrying out transmit this message, the information of acting server 12 in needn't the access transport layer.
Particularly, type indicator " atypes " obviously comprises coding digital data, the network interface that the user agent that this message is sent in its expression can use and the character of Internet Protocol, thus this information is offered location-server and acting server 12:
-so that location-server 12 can advance to registration 11 type indicators relevant with user agent's identifier, thus maintenance provides the database of information about the various user agents' that possibly attempt to communicate by letter type;
-so that can carrying out route under the situation of any information in can't visiting the transport layer that is used for sending M (" atypes ") message, acting server 12 transmits 11.
The example of the realization of the following step 10 of describing method of the present invention shown in Figure 2 with reference to Fig. 3 and Fig. 4.
In a kind of embodiment of particular type, type indicator " atypes " is inserted in " CONTACT " (contact) field of SIP inquiry (" REGISTER " and " INVITE " inquiry is specifically arranged).For the definition of this designator is described, below indicated the description ABNF of " CONTACT " field of RFC 3162 definition.
In following description ABNF, commonly known in the art and element that in RFC 3162, describe is a normal font, and additional descriptive elements is a runic.
Following table T1 has listed all new ABNF of description.
Table T1
The user agent possibly exist call blocking incoming call or that breathe out:
On-its IPv4 interface;
On-its IPv6 interface;
-or two types interface on, if it is equipped with two stack (DS) interfaces (promptly with two kinds of protocol version IPv4 and IPv6 all the interface of compatibility).
This operation is notified through type indicator " atypes ".
Can configure user act on behalf of, thereby, do not announce effective availability through type indicator " atypes " is set to suitable value.Please note: have only when one of institute's configured address belongs to global scope (the IPv6 agreement is distinguished " link is local " and " overall situation " type address), just the IPv6 interface is regarded as as available.The address of subrange can't be routed and be sent to outside the local area network (LAN), and this address with four corner is different, and it can be routed to be sent to outside the local area network (LAN) and (promptly be connected to outside the local area network (LAN)).At period of registration, sip user agent sends " REGISTER " message with the expansion that comprises additional header " atypes " " CONTACT " field of in table T1, listing, and " atypes " can get following value:
-4, if the user only supports IPv4;
-6, if the user only supports IPv6;
-0, if the user has two stack functions.
Send in " REGISTER " message of registrar R the user agent; The user agent can (for example be set to 4 through " atypes " type indicator; Even the user agent belongs to two stack (DS) types); It only supports the IPv4 agreement to acting server PS indication, perhaps is set to 6 through " atypes " type indicator, and it only supports the IPv6 agreement to acting server PS indication; Perhaps be set to 0 through " atypes " type indicator, it supports dual stack to acting server PS indication.
In Fig. 3, R indicates the location-server relevant with B with user agent A respectively with R6.
IPv4 user agent's example
Suppose that user agent A is the IPv4 user agent, has address 192.165.25.2." (1) REGISTER " message as shown in Figure 3, that user agent A lists in location-server R transmission table T2:
Table T2
Registrar R responds user agent A with " (2) 200OK " message of listing among the table T3:
Table T3
IPv6 user agent's example
Suppose that user agent B is the IPv6 user agent, has address 2001:688:1ffb:ff80::2." (1) REGISTER " message as shown in Figure 3, that user agent B lists in location-server R6 transmission table T4:
Table T4
Registrar R responds to confirm registration with " (2) 200OK " message of listing among the table T5:
Table T5
IP address in " CONTACT " field can be the unique address of the type different with the type of indication in the type indicator field " atypes ".Type indicator " atypes " is set to 6 user agent and can in " CONTACT " field, uses the IPv4 address; Perhaps type indicator " atypes " is set to 0 user agent and can only announces an address; But not two addresses are described below.The address that in " CONTACT " field, comprises uses route to transmit signaling message by sip proxy server.Media information sends the user agent to through the IPv6 interface; Because the user agent is declared as IPv6 user agent (according to the type indicator that is inserted in its message that sends to acting server, perhaps according to the type indicator of location-server for this user agent's storage) to its acting server PS.
The example that in " CONTACT " field, has only the DS user agent of an address:
With reference to Fig. 4, suppose that the user agent is two stack (DS) user agents, has address 2001:688:1ffb:ff80::2/192.168.25.5.As shown in Figure 4:
-during registration phase, " (1) REGISTER " message that the DS user agent lists in its location-server R transmission table T6:
Table T6
Location-server R6 responds with " (2) 200OK " message of listing among the table T7, to confirm registration:
Table T7
The processing of designator " atypes ":
When receiving " REGISTER " message, location-server R is the address of stored record (AOR), registration expired time and type indicator " atypes " also.These data (also having other data) are stored in the registration database of positioning service management.They maybe be by other " REGISTER " information updatings from same user agent.This processing has substituted the processing of initial appointment in RFC 3261.
Use is from the information of type indicator " atypes ", and location-server is divided three classes its user agent:
-pure IPv4;
-pure IPv6;
-two stacks (DS).
Acting server should be classified with regard to addressable through inquiring the registration database of positioning service management simply.Acting server can also be inserted into to the type indicator in the message of acting server through reading the user agent simply, carries out this classification, is described below.
The user agent is provided with type indicator " atypes " in the time of can also sending " INVITE " message at it.
Under following situation (situation-1), acting server PS must send sip message under the prerequisite of the content of not revising sip message:
-IPv4 to IPv4;
-IPv6 to IPv6;
-IPv4 to DS and DS to IPv4;
-IPv6 to DS and DS to IPv6;
-DS to DS
Under the situation of above-mentioned situation-1; Claim that the user agent is compatible, this is because it belongs to same type (perhaps more generally, for the DS user agent; Because it has a type at least is identical), and therefore can use identical IP version to engage in the dialogue.
Only under following situation (situation-2), just revise sip message, this sip message makes the called and calling subscriber agency's of same type IP address use after revising:
-IPv6 to IPv4;
-IPv4 to IPv6.
Under the situation of above-mentioned situation-2, claim that the user agent is incompatible, this is because it does not belong to same type, and therefore can not communicate by letter.
Transmit and confirm to use ALG to use or revise sip message obtaining the session of the success between two dissimilar user agents for calling out route, acting server (PS) can:
-or check the registration database that location-server is safeguarded:
In this case, acting server PS inquiry location-server R is with inquiry caller and called subscriber's Agent Type.Under the situation of a part that is situation-2, acting server PS can confirm to revise the SDP content of sip message then, so that consistent with the address style of callee's support.Example shown in Fig. 5 has shown this operator scheme through the calling between IPv4 user agent A and the IPv6 user agent B.The function of interconnection IPv4 and IPv6 network represented by node IN, and node IN is as relay station, and carries out the protocol conversion between IPv4 datagram and the IPv6 datagram particularly.
Suppose that user agent B is the IPv6 user agent.When the service beginning, user agent B registers on location-server R through type indicator " atypes " is set to 6, and user agent A registers on location-server R through type indicator " atypes " is set to 4.For simplicity, in Fig. 5, do not show this initial registration stage.
In under the IPv6 environment, know user agent B through the IPv6 address, this IPv6 address is converted into the IPv4 address by IPv6-IPv4 interconnection mechanism (for example NAT-PT mechanism).Then, identification user agent B is the IPv6 user agent, and identification user agent A is the IPv4 user agent.If user agent A attempts to be provided with the session with user agent B, the following sip message of exchange then:
-RE (1): user agent A sends " INVITE " message to acting server PS;
-RE (2): acting server PS inquiry location-server R, with the positioning address that obtains user agent B and at the user agent A of registration phase indication and the type indicator " atypes " of B;
-RE (3): the address of location-server R loopback user agent B, the type indicator " atypes " of user agent B and the type indicator " atypes " of user agent A;
-RE (4): acting server PS compares two type indicators " atypes " of user agent A and B.Go up available classification of type according to location-server R, acting server PS checking A is the IPv4 user agent, and B is the IPv6 user agent.Then, acting server PS starts adaptation mechanism, propose with the initial SDP that revises user agent A, thereby it comprises the IPv6 address.Then, " INVITE " message that will revise of acting server PS sends to the address of the indicated user agent B of location-server R.
If this program not, then acting server PS can't send user agent B to calling out route, also can't start with message correctly route send the necessary adaption function of user agent B to.Acting server PS can give user agent B the inquiry loopback and not revise it, and in this case, with the SIP session that can not take place between user agent A and the B.(referring to Fig. 1 b)
-or the type indicator " atypes " checking registration database and in " INVITE " message, transmit
In this case, acting server PS inquiry location-server R is to obtain the type that the called subscriber acts on behalf of B.The calling subscriber acts on behalf of the type of A " INVITE " message determining from its transmission.Then, acting server PS confirm to revise the content of sip message, and to act on behalf of the address style that B supports consistent with the called subscriber to make it; This situation is the part of situation-2 situation.For this option, the user agent can limit the type of the address of using for each session.The example of describing with reference to Fig. 5 has shown this other operator schemes through the calling between IPv4 user agent and the IPv6 user agent.
Suppose that user agent B is the IPv6 user agent.When the service beginning, user agent B registers on location-server R through type indicator " atypes " is set to 6, and user agent A registers on location-server R through type indicator " atypes " is set to 4.Here, identification user agent B is the IPv6 user agent, and identification user agent A is the IPv4 user agent.If user agent A attempts to be provided with the session with user agent B, the following sip message of exchange then:
-I (1): user agent A sends " INVITE " message to acting server PS;
-I (2): acting server PS inquiry location-server R, with the positioning address that obtains user agent B and at the type indicator " atypes " of the user agent B of registration phase indication;
-I (3): the address of location-server R loopback user agent B and the type indicator " atypes " of user agent B;
-I (4): acting server PS extracts the type indicator " atypes " of user agent A from " I (1) INVITE " inquiry, and the type indicator " atypes " of itself and user agent B is compared.Go up available classification of type according to location-server R, acting server PS checking user agent A is the IPv4 user agent, and user agent B is the IPv6 user agent.Then, acting server PS starts adaptation mechanism, propose with the initial SDP that revises user agent A, thereby it comprises the IPv6 address.Then, " INVITE " message that will revise of acting server PS sends to the address of the indicated user agent B of location-server R.
In order to use the agreement shown in Fig. 5, advantageously, acting server PS comprises module M
1, be used for comparison and calling subscriber agency and called subscriber to act on behalf of relevant type indicator.If module M1 confirms that the calling subscriber acts on behalf of with called subscriber agency and belongs to dissimilar, acting server PS active module M then
2, revise calling subscriber agency's IP address to call resource.The outside modification resource of acting server PS does not show in Fig. 5.Can the computer program form realize module M
1With M
2For simplicity, in Fig. 5, indicate them with identical digital alphabet mark.
The present invention also comprises computer program M
0, carry out by computer or special equipment (the for example IPv4 at IP terminal, IPv6, perhaps two stack user agent).As computer program M
0The time, its code command inserts the type indicator " atypes " of the type of one or more IP address that available network interface is supported among this user agent US of expression in the query messages that user agent UA sends, as stated and Fig. 2,3, shown in 4.
As stated, the present invention also comprises computer program M
1, M
2, it comprises a series of instructions, is carried out by computer or special equipment (for example acting server PS).As executive program M
1, M
2The time, these instruction process user agent is to the query messages of the type indicator " atypes " of the acting server transmission and type that comprise one or more IP address that available network interface is supported among this user agent of expression.Under the situation of not visiting the information that in transport layer, comprises, this processing is sent to its destination with the query messages route, as stated and shown in Fig. 2 to 5.
As stated, the present invention also comprises computer program M
3, it comprises code command, is carried out by computer or special equipment (for example location-server R).As executive program M
3The time, these instructions are extracted type indicator from the registration message that the user agent sends, and in registration database, store the type designator relatively with user agent's identifier.These instructions also are categorized as one of three IP classifications (IPv4, IPv6, two stack) with the user agent, as stated and shown in Fig. 2 to 5.
Claims (3)
1. an acting server has the device that is used for route SIP calling between calling subscriber agency and called subscriber agency, it is characterized in that it also comprises with lower device:
-be used to discern the device of said two user agents' IP address class type (IPv4, IPv6, or comprise two stacks of IPv4 and IPv6), said identification based on:
For current or former calling, act on behalf of the IP address class type designator that comprises in " CONTACT " field that comprises in the SIP query messages of transmission by the calling subscriber;
The classification of in the registration database that comprises called subscriber's Agent Type, storing,
-be used to discern and when suitable, be deployed in the device of effectively setting up the necessary resource of communication session between those two user agents.
2. acting server as claimed in claim 1 is characterized in that it also comprises with lower device: type that the said caller of Classification and Identification that is used for storing based on the registration database that is upgraded by location server and called subscriber act on behalf of and the device that comprises said two user agents' type.
3. acting server as claimed in claim 1 is characterized in that it also comprises with lower device: be used for device that the content that the SDP that transmits at the sip message that has each other between two user agents of different types proposes is made amendment or it is modified.
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| FR0650681 | 2006-02-28 | ||
| FR0650681A FR2898003A1 (en) | 2006-02-28 | 2006-02-28 | Data transmitting method for telephony over internet protocol network, involves inserting indicator, representative of type of address associated to user agent, in contact field of session initiation protocol request message |
Related Parent Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNA2007800070962A Division CN101395891A (en) | 2006-02-28 | 2007-02-15 | Method and system for characterising heterogeneous communication nodes |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN102413147A true CN102413147A (en) | 2012-04-11 |
| CN102413147B CN102413147B (en) | 2015-04-08 |
Family
ID=36952572
Family Applications (2)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNA2007800070962A Pending CN101395891A (en) | 2006-02-28 | 2007-02-15 | Method and system for characterising heterogeneous communication nodes |
| CN201110440378.XA Expired - Fee Related CN102413147B (en) | 2006-02-28 | 2007-02-15 | Agent server |
Family Applications Before (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNA2007800070962A Pending CN101395891A (en) | 2006-02-28 | 2007-02-15 | Method and system for characterising heterogeneous communication nodes |
Country Status (6)
| Country | Link |
|---|---|
| US (1) | US20090041034A1 (en) |
| EP (1) | EP1994724B1 (en) |
| JP (2) | JP4927101B2 (en) |
| CN (2) | CN101395891A (en) |
| FR (1) | FR2898003A1 (en) |
| WO (1) | WO2007099248A2 (en) |
Families Citing this family (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8683077B2 (en) | 2008-06-24 | 2014-03-25 | Blackberry Limited | Method for indicating supported IP versions and reaching a device that supports compatible IP versions with SIP |
| US8331355B2 (en) | 2008-06-24 | 2012-12-11 | Research In Motion Limited | Method for a network component to route a communication session |
| FR2933259A1 (en) * | 2008-06-30 | 2010-01-01 | France Telecom | METHOD FOR RECEIVING A DATA PACKET FROM AN IPV4 DOMAIN IN AN IPV6 DOMAIN, ASSOCIATED DEVICE AND ACCESS EQUIPMENT |
| EP2297928B1 (en) | 2008-06-30 | 2012-05-09 | France Telecom | Method for receiving a data packet in an ipv6 domain, and associated device and residential gateway |
| JP4920052B2 (en) * | 2009-03-11 | 2012-04-18 | 株式会社日立製作所 | Communication system and server |
| NO330630B1 (en) * | 2009-07-01 | 2011-05-30 | Tandberg Telecom As | System and procedure for making a call using a global register |
| CN102158926B (en) * | 2010-02-12 | 2015-04-01 | 中兴通讯股份有限公司 | Method and device for processing SDP (Session Description Protocol) request in media path optimizing process |
| US20130007291A1 (en) * | 2011-06-28 | 2013-01-03 | Verrizon Patent and Licensing Inc. | MEDIA INTERWORKING IN IPv4 AND IPv6 SYSTEMS |
| US9578180B2 (en) * | 2011-12-08 | 2017-02-21 | Institute For Information Industry | Communication network system, calling terminal and voice call establishing method thereof |
| FR3094590A1 (en) * | 2019-03-28 | 2020-10-02 | Orange | Gateway and method for differentiating traffic emitted by the gateway, device and method for managing traffic. |
| EP3761587B1 (en) * | 2019-07-04 | 2022-11-09 | Deutsche Telekom AG | Method for infinity registration using a session initiation protocol based communication in a session initiation protocol based network, and network |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20030110292A1 (en) * | 2001-12-07 | 2003-06-12 | Yukiko Takeda | Address translator, message processing method and euipment |
Family Cites Families (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2000270024A (en) * | 1999-03-19 | 2000-09-29 | Nippon Telegr & Teleph Corp <Ntt> | Method for exchanging capability of frame packet processing size in internet phone, terminal utilizing internet phone and medium recording program of internet phone |
| WO2003021911A1 (en) * | 2001-09-04 | 2003-03-13 | Ntt Docomo, Inc. | Encoding method selection method and terminal apparatus |
| US6920396B1 (en) * | 2001-09-20 | 2005-07-19 | Phenogenomics Corporation | System and method for providing flexible access and retrieval of sequence data from a plurality of biological data repositories |
| US7231452B2 (en) * | 2002-11-29 | 2007-06-12 | National University Of Singapore | Method and apparatus for communicating on a communication network |
| KR100560737B1 (en) * | 2003-02-18 | 2006-03-13 | 삼성전자주식회사 | appatus for converting IPv4-to-IPv6 using dual stack and method thereof |
| JP2004364141A (en) * | 2003-06-06 | 2004-12-24 | Hitachi Communication Technologies Ltd | Ip address conversion device and packet transfer device |
| US7467214B2 (en) * | 2003-06-20 | 2008-12-16 | Motorola, Inc. | Invoking protocol translation in a multicast network |
| JP2005086467A (en) * | 2003-09-09 | 2005-03-31 | Hitachi Ltd | Session controller, information communication terminal, server, and terminal |
-
2006
- 2006-02-28 FR FR0650681A patent/FR2898003A1/en not_active Withdrawn
-
2007
- 2007-02-15 US US12/224,571 patent/US20090041034A1/en not_active Abandoned
- 2007-02-15 CN CNA2007800070962A patent/CN101395891A/en active Pending
- 2007-02-15 EP EP07731633.9A patent/EP1994724B1/en not_active Not-in-force
- 2007-02-15 JP JP2008556827A patent/JP4927101B2/en not_active Expired - Fee Related
- 2007-02-15 WO PCT/FR2007/050808 patent/WO2007099248A2/en active Application Filing
- 2007-02-15 CN CN201110440378.XA patent/CN102413147B/en not_active Expired - Fee Related
-
2011
- 2011-12-09 JP JP2011270289A patent/JP5085781B2/en not_active Expired - Fee Related
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20030110292A1 (en) * | 2001-12-07 | 2003-06-12 | Yukiko Takeda | Address translator, message processing method and euipment |
Non-Patent Citations (2)
| Title |
|---|
| J. ROSENBERG等: ""SIP: Session Initiation Protocol"", 《NETWORK WORKING GROUP REQUEST FOR COMMENTS: 3261》 * |
| YASURO KAWARASAKI等: ""IPv4/IPv6 SIP interworking methods in dual-stack network"", 《IEEE》 * |
Also Published As
| Publication number | Publication date |
|---|---|
| FR2898003A1 (en) | 2007-08-31 |
| EP1994724A2 (en) | 2008-11-26 |
| JP5085781B2 (en) | 2012-11-28 |
| US20090041034A1 (en) | 2009-02-12 |
| CN102413147B (en) | 2015-04-08 |
| WO2007099248A2 (en) | 2007-09-07 |
| EP1994724B1 (en) | 2016-08-17 |
| CN101395891A (en) | 2009-03-25 |
| JP2009528742A (en) | 2009-08-06 |
| WO2007099248A3 (en) | 2007-10-25 |
| JP4927101B2 (en) | 2012-05-09 |
| JP2012100293A (en) | 2012-05-24 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102413147B (en) | Agent server | |
| US6678735B1 (en) | Method and apparatus for a sip client manager | |
| CN101589638B (en) | Providing interaction management for communication networks | |
| CN103634490B (en) | The gateway that a kind of enterprise network being provided for use SIP can be survived | |
| JP5051728B2 (en) | Method and system for transmitting data between nodes connected to different IP environments by assigning a fake address | |
| US20050050211A1 (en) | Method and apparatus to manage network addresses | |
| US20050117605A1 (en) | Network address and port translation gateway with real-time media channel management | |
| US8423652B2 (en) | Service templates for an IP multimedia subsystem | |
| CN101305560B (en) | Method and communication system for selecting a transmission mode for transmitting useful data | |
| JP2007049415A (en) | Voice data conversion apparatus, network system, and control method and program | |
| CN101335759A (en) | Session initiation protocol adaptor | |
| JP2005236824A (en) | IPv6/IPv4 TRANSLATOR | |
| US20050047423A1 (en) | Protocol interworking framework | |
| CN101257435B (en) | Implementing method of SIP application-level gateways based on NAT-PT | |
| US20080165947A1 (en) | Methods, systems, and computer program products for providing a dynamic and flexible media gateway termination identifier | |
| CN101268661A (en) | Method and system for SIP-based mobility management | |
| KR100544195B1 (en) | Method and system of initiating session using session initiation protocol under mobile IPv6 | |
| CN101197808B (en) | Method for sustaining NAT address in SIP network system and device thereof | |
| US20090187664A1 (en) | Method for addressing call transmission and service elements between heterogenous nodes | |
| EP1202521B1 (en) | A method for processing in a gatekeeper of an internet protocol network | |
| KR100673175B1 (en) | System and method for interworking videotelephony in different networks | |
| CN101316263B (en) | Resource reservation method and apparatus | |
| Kellerer | Intelligence on top of the networks: SIP based service control layer signaling | |
| JP2006014144A (en) | Protocol conversion server | |
| Ribeiro et al. | A SIP/H. 323 Signaling Gateway Implementation for IP Telephony. |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20150408 Termination date: 20180215 |
|
| CF01 | Termination of patent right due to non-payment of annual fee |