CN100558110C

CN100558110C - A kind of method and system of in the SIP network, handling public identifier

Info

Publication number: CN100558110C
Application number: CNB2006100868838A
Authority: CN
Inventors: 李辉
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2006-06-26
Filing date: 2006-06-26
Publication date: 2009-11-04
Anticipated expiration: 2026-06-26
Also published as: CN1968268A

Abstract

The invention discloses a kind of method of in the SIP network, handling public identifier, this method by the device that sends sip message with public identifier and relevant information as SIP URI in the sip message header field or Tel URI and send sip message, the content-defined subclass that wherein said public identifier comprises for SIP URI or Tel URI content; The device that receives described sip message is according to the defined content of public identifier, extract this partial content and revert to public identifier according to predetermined format from the SIP URI of sip message header field or Tel URI, described predetermined format is SIP URI form or Tel URI form.The present invention also discloses a kind of SIP network system simultaneously.

Description

A kind of method and system of in the SIP network, handling public identifier

Technical field

The present invention relates to the Session initiation Protocol SIP network technology of the communications field, relate in particular to the method and system of in the SIP network, handling public identifier.

Background technology

IMS is the 3GPP subsystem that superposes on packet network, adopt the bearer path of packet domain for its control signaling and media delivery, introduce Session Initiation Protocol as professional control protocol, utilize simple, the easy expansion of SIP, media combination characteristics easily, by business control is separated with carrying control, provide abundant multimedia service.Main functional entity comprises controlling call entity CSCF, the home subscriber server HSS of centralized management user contracting data of functions such as control user registration, session control among the IMS, and the application server AS of miscellaneous service logic control function is provided.

In IMS uses, in order to finish the UE registering functional, and caller or called business, 3GPP has defined two kinds of public identifiers:

Public user identity (IMPU): the user uses public user identity to communicate.Each IMS user has one or more public user identity, and public user identity adopts the form of SIP URI or TEL URI.For example: sip:tom@example.com.Be stored in when user ID is initial in the ISIM module and HSS of user terminal UE.

Common service mark (PSI): public service identity is used for describing the resource of a specific transactions in the application server.Public service identity adopts the form of SIP URI or TEL URI, for example: sip:conference@examplenetwork.com.

Formal definition for public user identity in 3GPP TS23.228 standard is: public user identity should adopt the SIP URI form of RFC3261 and RFC2396 definition, perhaps " tel: "-URI form of RFC3966 definition.

In 3GPP TS23.003 standard, public user identity is defined as: public user identity will adopt the form of SIP URI (with reference to IETF RFC3261), perhaps the form of tel URI (with reference to IETF RFC3966).The SIP URI of a public user identity will adopt " sip:user@domain " form.The method that relatively will adopt the 19.1.4 joint definition among the RFC3261 of SIP URI).

In 3GPP TS23.003 standard, public service identity is defined as: public service identity will adopt the form of SIP URI (with reference to IETF RFC3261), perhaps the form of tel URI (with reference to IETF RFC3966).On an application server, a public service identity is represented a business, perhaps is the special resource of service creation.The domain name part of public service identity is by IMS operator predefine, and the IMS system provides the flexibility of dynamic creation User Part.

In RFC3261 public user identifier is defined as: service recorder address (Address-of-Record) comes identifying user among the RFC3261, a recording address address-of-record (AOR) be a SIP or SIPS URI it pointed to a main frame with positioning service, this main frame can become URI the URI of user's real physical position.An AOR often is considered to a user's " public address ".

RFC3261 is about the definition of SIP URI and be described below:

SIP URI is used for the resource that communication of mark is used.Just as other all URI, SIP URI can be placed on the webpage, and in the email message, the business card that perhaps prints is first-class.Comprised the conversational communication that this resource was initiated and be maintained to enough information in these URI the insides.

The common form of a SIP URI is such:

sip:user:password@host:port；uri-parameters？headers

These parts (component) have following meaning:

User: in the specific resources address of main frame.

The password:password field is with user-dependent.

Host: main frame provides SIP resource.Host is commonly referred to as a domain name here, and host has partly comprised the address of a complete host name or IPV4/IPV6.

Port: request is with the port that is sent.

The URI parameter: the URI parameter increases after hostport, separates with branch.This extension mechanism has comprised transport, maddr, and ttl, user, method and lr parameter, wherein:

The decision of-transport parameter is at the communication mechanism that sends sip message, and SIP can use any network communication protocol;

-maddr parameter has indicated the address of the server of getting in touch this user, and it can cover the address in the host territory;

-ttl parameter has determined the life cycle of UDP multiple spot message.

From URI, make up SIP and ask needed method territory, can specify by the method parameter.

If specified the lr parameter, be the routing mechanism of realizing according to this standard with regard to the owner who indicates this resource.

Because URI parameter mechanism can be expanded, the SIP element should be skipped those unacquainted uri parameters.

Following table is listed the SIP header field value of SIP URI under different situations, Request-URI and the use usage of quoting thereof.Wherein " m " is the necessary meaning of pressure, and " o " is that optionally "-" is unallowed.

	?Req-URI	To	From	reg./redir. Contact	Dialog?Contact R-R/Route	external
	?Req-URI	To	From	reg./redir. Contact	Dialog?Contact R-R/Route	external	user	?o	o	o	o	o	o
password	?o	o	o	o	o	o	user	?o	o	o	o	o	o
password	?o	o	o	o	o	o	host	?m	m	m	m	m	m
port	?o	-	-	o	o	o	host	?m	m	m	m	m	m
port	?o	-	-	o	o	o	user-param	?o	o	o	o	o	o
method	?-	-	-	-	-	o	user-param	?o	o	o	o	o	o
method	?-	-	-	-	-	o	maddr-param	?o	-	-	o	o	o
ttl-param	?o	-	-	o	-	o	maddr-param	?o	-	-	o	o	o
ttl-param	?o	-	-	o	-	o	transp.-param	?o	-	-	o	o	o
lr-param	?o	-	-	-	o	o	transp.-param	?o	-	-	o	o	o
lr-param	?o	-	-	-	o	o	other-param	?o	o	o	o	o	o
headers	?-	-	-	o	-	o	other-param	?o	o	o	o	o	o

In the prior art, the comparative approach of SIP URI is as follows:

The userinfo of A, SIP URI is a case sensitive.This has comprised and has contained password or according to the comparison of the userinfo of phone descriptor format.For the comparison of other parts of URI, except particularly pointing out, all be that capital and small letter is insensitive.

The order of B, parameter and the order of header field are for relatively SIP URI is inoperative.

C, the character outside the reserved character collection (referring to RFC2396) are equal to their " " % " HEXHEX " form.

D, IP address can be the IP addresses that is equal to the host name correspondence that arrives by dns lookup, and the IP address can not be equal to host name.

If E, two URI are identical, user so, password, host, the port part must be identical.

F, the URI of user part to be arranged and do not have the URI of user part be unequal.It also is different with the URI that does not have the password part that the URI of password part is arranged.

G, one not with the URI of optional part and with these parts but value be that the URI of default value does not wait.For example, if a URI has omitted the port part, and be not equal to a URI who defines the 5060port part.Same application of rules territory transport-parameter, ttl-parameter, user-parameter, method part etc.

H, definition sip:user@host and definition sip:user@host:5060 are unequal.When obtaining the address from URI when, identical URI can obtain identical address.Sip:user@host:5060 can obtain port 5060 all the time.URI:sip:user@host is according to DNS SRV mechanism, and the port that may be able to draw other comes.

I, URI parameter compare according to following rule

-any uri parameter that occurs in two URI all must be the same;

-user, ttl, if perhaps method uri parameter only occurs a side, even and default value equate that it is unequal also to be judged to be two URI;

-comprise the URI of maddr parameter and do not comprise the unequal of maddr parameter;

-other uri parameters if occur a side, are then ignored in relatively;

Relatively can not ignoring of-URI head.Any territory that partly occurs at header all must be mated and compare in both sides URI.

Session Initiation Protocol is as follows according to the method that SIP URI initiates request:

-comprise transport, maddr, ttl or user parameter among the Request-URI of structure request.If URI has comprised the method parameter, its value must be the same with the method for the request of constructing so.And the method parameter can not be placed among the Request-URI.Unacquainted URI parameter must be placed among the Request-URI of message.

-header that occurs among the URI or inclusion partly are incorporated into message itself, and to be used as be oneself part of request.In realization, should not keep those obviously dangerous header field fields: From, Call-ID, Cseq, Via and Record-Route.

The method of the related tel URL of SIP URI:

(RFC 3966) are converted into a SIP URI if-tel is URL, and the whole phone of tel URL is described (telephone-subscriber), parameter so, all needs to be placed on the userinfo part of SIP URI.For example: tel:+358-555-1234567; Postd=pp22 can become: sip:+358-555-1234567; Postd=pp22@foo.com; User=phone

-for fear of the insensitive problem of capital and small letter, when the phone that structure is placed on the userinfo part among the SIP URI is described the territory, should converted magnitude writing insensitive phone, to describe the territory be small letter, and except isdn-subaddress and post-dial, the parameter that phone is described sorts according to parameter name, because they need appear at parameter first in order.

RFC3966 is about the definition of tel URI and be described as: tel URI is a globally unique identifier of describing by telephone number, has described its related methods of use in RFC3261.Tel URI major parameter is described as follows:

-telephone number: overall number or local number, wherein overall number starts with "+"; Local number is the number in a certain zone, must its scope of band phone-context parametric description.

-isub:ISDN network subaddressing.

-ext: be used for the sign of marking terminal, be similar to isdn subaddress.

-phone-context: overall number or domain name.

The comparative approach of-tel URI relatively is that capital and small letter is insensitive:

-must all be overall number or local number, the two numeral of removing behind the separator must be identical.

-URI parameter according to pname is not relatively considered order, if the parameter of a URI does not comprise at another, then the two is unequal.

Public identifier at the use and the acquisition methods of Session Initiation Protocol is:

IMS related entities (comprising the IMS terminal) is according to the relevant header field of public identifier structure sip message (Request-URI for example, From, To, Contact, P-Asserted-Identity) time, directly use public identifier as SIP URI,, can in this SIP URI, add other regulation parts that meet SIP URI definition or expansion part if agreement needs.

The SIPURI of IMS related entities (comprising the IMS terminal) from the relevant header field of the Session Initiation Protocol that receives extracts public identifier.CSCF obtain behind the public identifier, be applied in Cx interface, Rf interface etc. and handle the HSS data query and charge and handle.

At present, the user ID (AOR) and the SIP URI/tel URI that define in public identifier of IMS standard definition (IMPU) and the ietf standard not exclusively are equal to, owing to there is not the two relation of clear description to cause existing following problem:

1, SIP entity (CSCF, AS, Proxy etc.) can't take out user ID according to the SIP URI in the sip message header field that receives.For example: the SIP URI among the Request-URI in the sip message not only comprises CSI called subscriber identification, also may comprise the parameters such as port numbers of reception.

2, CSCF can't carry out matching ratio according to SIP URI in the sip message header field that receives and the public identifier in the iFC initial filter criteria.

If 3 public identifiers adopt tel URI, and tel URI can convert SIP URI to, conversion regime of the two and manner of comparison may cause public identifier correctly to handle.

Summary of the invention

The invention provides a kind of method and system of in the SIP network, handling public identifier, to solve the problem that exists network entity can not correctly handle public identifier in the prior art according to the sip message that receives.

The invention provides following technical scheme:

A kind of method of handling public identifier in the SIP network comprises the steps:

The device that sends sip message with public identifier and relevant information as SIPURI in the sip message header field or Tel URI and send sip message, the content-defined subclass that wherein said public identifier comprises for SIP URI or Tel URI content;

The device that receives described sip message is according to the content that comprises in the described subclass, extract this partial content and revert to public identifier according to predetermined format from the SIP URI of sip message header field or Tel URI, described predetermined format is SIP URI form or Tel URI form.

Wherein: signatory described public identifier adopts SIP URI form; Only comprise the user user parameter in the SIPURI part in the described public identifier.

Signatory described public identifier adopts Tel URI form; When subscriber directory number adopted overall number, described public identifier did not comprise any parameter of Tel URI; Perhaps, when subscriber directory number adopts local number, with the part of the parameter p hone-context in the Tel URI part as public user identity.

A, network entity compare comprising the public identifier that the SIP URI of public identifier or Tel URI and user contract in the sip message, and described network entity comprises home signature user server HSS, service-call session control function S-CSCF, Proxy-Call Session Control Function P-CSCF or application server AS;

B, network entity are handled according to following comparative result:

If the content of the public identifier that the user contracts and the content of described SIP URI or Tel URI are identical, determine that then this public identifier is the public identifier that carries in the described sip message;

If the content of the public identifier that the user contracts is the subclass of described SIP URI or Tel URI, determine that then this public identifier is the public identifier that carries in the described sip message;

Otherwise, determine from described sip message, to obtain described public identifier.

A kind of SIP network equipment comprises:

Comparison means is used for that sip message is comprised the SIP URI of public identifier or the public identifier in Tel URI and the subscription data compares;

Determine device, be used for handling according to comparative result:

The described SIP network equipment also comprises: conversion equipment is used for determining that described SIP URI when converted, is reduced to Tel URI with SIP URI by Tel URI before relatively.

A kind of SIP network system comprises:

Be used for public identifier and relevant information as the SIP URI or the Tel URI of sip message header field and send sip message, the message part that wherein said public identifier comprises is defined as the device of a subclass of SIP URI or Tel URI content;

Be used for according to the defined content of public identifier, extract this message part and revert to the device of public identifier according to predetermined format from the SIP URI of the sip message header field that receives or Tel URI, described predetermined format is SIP URI form or Tel URI form.

Beneficial effect of the present invention is as follows:

1, the message part that public identifier is comprised is defined as the subclass of SIP URI or Tel URI, thereby make message part that network entity can comprise according to subclass from the SIP URI of sip message header field or TelURI, accurately extract public identifier, avoided using in the prior art the unclear problem of IMPU.

2, in registration process, obtain the public identifier that the user contracts and being kept on the network entity, make network entity the SIP URI in the sip message can be comprised matching ratio than accurately extracting public identifier with described public identifier.

Description of drawings

Fig. 1 is the schematic diagram of IMS network system in the embodiment of the invention one;

Fig. 2 is a flow chart of handling public identifier in the embodiment of the invention one in IMS network registry authentication process;

Fig. 3 is the flow chart of IMS network of network entity extraction public identifier in the embodiment of the invention two;

Fig. 4 is a flow chart of handling public identifier in the embodiment of the invention two in the user equipment registration flow process;

In the Calling Side flow process, handle the flow chart of public identifier in Fig. 5 A embodiment of the invention two;

Fig. 5 B is a flow chart of handling public identifier in the embodiment of the invention two in the callee side flow process;

Fig. 6 is the structural representation of the network equipment in the embodiment of the invention.

Embodiment

Present embodiment is that example describes with the IMS network.Be called public identifier with the user ID (AOR) that defines in the public identifier of IMS standard definition and the ietf standard is unified in the present embodiment, wherein the public identifier of IMS standard definition comprises public user identity (IMPU) and public service identity (PSI).

Embodiment one

In the present embodiment public identifier is defined as the subclass of SIP URI/tel URI, the IMS network entity extracts correct public identifier according to the information that this subclass comprises from the SIP URI/tel URI of sip message.Public identifier is that the subclass of SIP URI/tel URI is meant that the part of SIP URI/tel URI comprises all constituents of public identifier, and according to the manner of comparison of SIP URI or tel URI part, the value of corresponding part equates.

Public identifier is signatory can to adopt SIP URI form, also can adopt tel URI form.A kind of preferable SIP URI form is as follows:

SIP-URI ＝″sip:″[userinfo]host?user-param

userinfo ＝(user/telephone-subscriber)″@″

host ＝hostname

user-param?＝″；user＝″(″phone″)

Wherein the definition of user and hostname is with reference to RFC3261.Except userinfo and these two parts of host,, do not carry other any SIP URI part in the signatory public identifier except the SIP URI that is converted to by tel URI need support the user parameter.

A kind of preferable tel URI form is as follows:

telephone-uri ＝″tel:″telephone-subscriber

telephone-subscriber ＝global-number/local-number

global-number ＝global-number-digits

local-number ＝local-number-digits?context

context ＝″；phone-context＝″descriptor

descriptor ＝domainname/global-number-digits

Wherein the definition of global-number-digits, local-number-digits and domainname is with reference to RFC3966.If telephone number is overall number, then can not carry any parameter as public identifier.If telephone number is a local number, then parameter " phone-context " must be as the part of public identifier, and all the other tel URI parameters can not be as the parameter of public identifier.

Consult IMS network system shown in Figure 1, comprise user terminal UE, Proxy-Call Session Control Function P-CSCF entity, interrogation-call session control function I-CSCF entity, service-call session control function S-CSCF entity, home signature user server HSS and application server AS; P-CSCF entity handles user inserts, and forward the request to user's home network, the I-CSCF entity is selected the S-CSCF of home network for the user, the S-CSCF entity provides the user to register and carries out functions such as session control, HSS manages user contracting data concentratedly, and AS provides miscellaneous service logic control function.Each entity in the network is preserved the definition of public identifier, and promptly knowing public identifier is subclass of SIP URI/tel URI.

Consult shown in Figure 2ly, the flow process of handling public identifier in the UE registration process is as follows:

Step 200, UE as the From of SIP registration message and the SIP URI in the To header field, are initiated register requirement according to the relevant information of IMPU in the ISIM module and terminal, and wherein IMPU is the subclass of SIP URI.

After step 210, P-CSCF receive the SIP registration message, be the rule of the subclass of SIP URI, take out the relevant information of subclass and be combined as IMPU, and transmit the home network of register requirement to the user from the SIP URI of To header field according to IMPU.

After step 220, I-CSCF receive the SIP registration message, be the rule of the subclass of SIP URI, take out the relevant information of subclass and be combined as IMPU from the SIP URI of To header field, to HSS inquiring user login state according to IMPU.

Step 230, I-CSCF obtain the address of the S-CSCF that is assigned to the user according to the information that HSS returns.

Step 240, I-CSCF send to S-CSCF with registration message.

After step 250, S-CSCF receive the SIP registration message, according to IMPU is the rule of the subclass of SIP URI, take out the relevant information of subclass and be combined as IMPU from the SIP URI of To header field, get the authentication collection to HSS, and from the response of HSS, obtain authentication information (follow-up authentication process process shown in the figure, the processing of extracting public identifier in this process is same as described above, and authentication process and prior art in like manner repeat no more).

Providing an instantiation below further specifies:

The public identifier of definition is userinfo and host, and this public identifier is the subclass of SIP URI.For example user sip:bob@example.com is initiated a session request, because the needs of acting server route, sip:bob@example.com at the Request-URI of request message header field has added port information, and the SIP URI of this Request-URI header field becomes sip:bob@example.com; Port=6688, S-CSCF (perhaps its acting server) is after receiving this request message, by the definition of above-mentioned public identifier, from Request-URI, extract the public identifier of sip:bob@example.com as the called subscriber, abandon content " port=6688 ".

Embodiment two:

Present embodiment is so that to extract public identifier from sip message be that example describes by comprising matching ratio.

Consult shown in Figure 3ly, the main handling process of IMS network of network entity extraction public identifier is as follows:

Step 300, network entity receive sip message.

Step 301, described network entity compare SIP URI in the sip message or the public identifier in tel URI and the subscription data.

Step 302, judging whether to exist the content of signatory public identifier, identical with the content of SIP URI or tel URI (part and the latter's the part that are the former are identical, and manner of comparison according to SIP URI part, the value of corresponding part equates), if, then carry out step 304, otherwise, carry out step 303.

Step 303, to judge whether to exist the content of a signatory public identifier be that the subclass of described SIP URI or telURI content (is all constituents that the latter's part comprises the former, and manner of comparison according to SIPURI or tel URI part, the value of corresponding part equates), if, then carry out step 304, otherwise, determine and can't from described sip message, obtain public identifier.

Step 304, with a described public identifier as the public identifier that carries in the described sip message.After network entity obtained public identifier, the request message that can judge reception was the request message of registered users, can handle accordingly.

In the present embodiment, at S-CSCF by Cx interface inquiry HSS the time, request message is comprised the SIP URI of IMPU to HSS or the IMPU in tel URI parameter and the user-subscribed database comprises matching ratio by flow process shown in Figure 3, finds out corresponding user totem information and return to CSCF; IMPU in the subscription data that S-CSCF returns according to HSS obtains the public identifier that the user contracts, and is kept at this locality; Then, in the P-Associated-URI header field in the response message of registration, the public identifier that the user is contracted or return to other relevant network entities from the public identifier of the SIP URI of tel URI conversion.For follow-up session request or standalone transaction request, S-CSCF takes out the public identifier in the sip message by SIP URI in the sip message and the local public identifier of preserving are comprised matching ratio.Accordingly, P-CSCF obtains the user ID that the user contracts by the P-Associated-URI header field in the response message of registration, and is kept at this locality.Follow-up session request or standalone transaction request, P-CSCF takes out public identifier by SIP URI in the sip message and the local public identifier of preserving are comprised matching ratio by flow process shown in Figure 3.Same, the local public identifier of contracting of preserving of AS receives session request or standalone transaction request at AS, by SIP URI in the sip message and the local public identifier of preserving are comprised matching ratio, takes out public identifier.

During signatory the or service contracting of IMS user, operator is according to the form of the signatory public identifier of needs decision of oneself, can be according to the sign format of 3GPP TS23.228 and TS23.003 definition, perhaps SIP URI and the RFC3966 that defines according to RFC 3261 fully defines tel URI format assignment.Signatory public identifier is kept in the subscription data on database, IMS terminal ISIM module and the AS of HSS, and the signatory public identifier that public identifier (IMPU) in the IMS terminal ISIM module and HSS preserve is consistent, and the signatory public identifier that public identifier on the AS (PSI sign) and HSS preserve is consistent.

In the present embodiment, before SIP URI/tel URI is not judged as public identifier, need to be treated differently during with itself and the comparison of SIP public identifier, its comparative approach is as follows:

When the signatory public identifier of-two SIP URI forms compares, relatively according to the SIPURI comparative approach of stipulating among the RFC3261;

When the signatory public identifier of-two tel URI forms compares, compare according to the tel URI comparative approach of stipulating among the RFC3966;

When if there is the user parameter in the public identifier of-SIP URI form, must earlier SIP URI be reduced into tel URI public identifier, compare according to tel URI manner of comparison and another one tel URI again.

Because in the sip message transport process, some network entities may convert tel URI to SIPURI, in order correctly to handle public identifier, change by following mode in the present embodiment:

Mode one:

Signatory mark at tel URI form belongs to certain implicitly registered set, and this implicit registration concentrates when comprising other SIP URI public identifiers, and this tel URI public identifier is directly changed into corresponding SIP URI.Wherein:

1, the whole phone of tel URL public identifier is described (telephone-subscriber) and parameter, is placed on the user part of SIP URI public identifier.

2, implicit registration is concentrated the domain part of the domain part of other signatory SIP URI public identifiers that comprise as the SIP URI public identifier after changing.There are a plurality of signatory SIPURI public identifiers if implicit registration is concentrated, can select the domain of default signatory SIP URI public identifier partly or according to configuration information to obtain.

3, increase the parameter of following parameter, come from tel URI conversion to show this SIP URI public identifier as the SIP URI public identifier after changing.

user-param＝″；user＝″(″phone″)

4, for fear of the insensitive problem of capital and small letter, when the phone that structure is placed on the userinfo part among the SIP URI was described the territory, converted magnitude is write insensitive phone, and to describe the territory be small letter.

Mode two:

When the SIP network entity does not have the information of domain part of public identifier of tel URI form, from the public identifier change server (for example: inquiry SIP URI public identifier E.164 Number server) by the SIP network entity.

If the Query Result that the public identifier change server returns comprises SIP URI, the public identifier after then this SIP URI changes as tel URI.If but the SIP URI in the Query Result comprises regular expression, then need URI, the public identifier after then transformation result being changed as tel URI according to regular expression conversion SIP.If the Query Result that E.164 Number server returns does not comprise SIP URI, then the SIP network entity is thought inquiry failure, and the public identifier of this tel URI form can not be converted to SIP URI form.

The process that each network entity of IMS obtains public identifier is as follows:

In the present embodiment IMS network architecture as shown in Figure 1, the process of handling public identifier in the user equipment registration flow process as shown in Figure 4:

Step 400, UE as the From of SIP registration message and the SIP URI in the To header field, are initiated register requirement according to the relevant information of IMPU in the ISIM module and terminal.

Step 410, UE carry out authentication process (comprising a plurality of interactive step).

Step 420, S-CSCF determine the authentication success, upgrade the log-on message of HSS, take out SIP URI as IMPU in the SAR request message from To header field, the subscription data of request download user.

Step 430, request message is comprised the SIP URI of IMPU to HSS or the IMPU in tel URI parameter and the user-subscribed database comprises matching ratio, finds out corresponding public identifier information, and return response to S-CSCF.

Step 440, S-CSCF receive user contracting data, and the IMPU in the subscription data that HSS is returned is kept at this locality, and in the P-Associated-URI header field in the response message of registration, the IMPU that carries in the subscription data returns to the user.

Step 450, I-CSCF transmit 401 message to P-CSCF.

Step 460, the P-Associated-URI header field of P-CSCF from the response message of registration obtain the IMPU in the user contracting data, are kept at this locality, and P-CSCF gives UE with forwards then.The P-Associated-URI header field of UE from the response message of registration obtains the IMPU in the user contracting data, is kept at this locality.

Consult shown in Fig. 5 A, the process of handling public identifier in the Calling Side handling process is as follows:

Step 500, IMS terminal UE 1 use the user ID of user's registration to initiate a session request.

Step 501, P-CSCF1 from sip message (P-Prefered-Identity or From header field) take out SIP URI, and the signatory IMPU of the user who preserves when registering with the user then comprises matching ratio, obtains user's information.After finishing dealing with, be transmitted to S-CSCF1.

Step 502, S-CSCF1 from sip message (P-Asserted-Identity or From header field) take out SIP URI, and the signatory IMPU of the user who preserves when registering with the user then comprises matching ratio, obtains user's information.

Consult shown in Fig. 5 B, the process of handling public identifier in the callee side handling process is as follows:

After step 550, I-CSCF received conversation request message, (Request-URI) took out SIP URI from sip message.

Step 551, I-CSCF use this SIP URI as the IMPU in the LIR request message, send to HSS.

Step 552, HSS comprise matching ratio according to SIP URI in the request message IMPU parameter and the IMPU in the user-subscribed database after receiving the LIR request, find out corresponding user totem information and return to I-CSCF.

Step 553, I-CSCF transmit conversation request message to S-CSCF.

Step 554, S-CSCF from sip message (Request-URI) take out SIP URI, and the signatory IMPU of the user who preserves when registering with the user then comprises matching ratio, obtains user's information.

For example the signatory public identifier of user Bob is sip:bob@example.com.When Bob is initiated a session request, because the needs of acting server route, sip:bob@example.com at the Request-URI of request message header field has added port information, and the SIP URI of this Request-URI header field becomes sip:bob@example.com; Port=6688, acting server is after receiving this request message, compare by SIP URI and the signatory public identifier of Bob the Request-URI header field, find that the signatory public identifier of Bob is the subclass of the SIP URI of Request-URI header field, therefore think that the public identifier that obtains is sip:bob@example.com from Request-URI.

Accordingly, present embodiment provides the network equipment as shown in Figure 6, comprising: conversion equipment 60, comparison means 61 and definite device 62; Conversion equipment 60 is used for determining that described SIP URI when converted, is reduced to tel URI with SIP URI by tel URI before relatively; Comparison means 61 is used for that sip message is comprised the SIP URI of public identifier or the public identifier in tel URI and the subscription data compares; Determine that device 62 is used for handling according to comparative result:, determine that then this public identifier is the public identifier that carries in the described sip message if a public identifier content of the content of described SIP URI or tel URI and subscription data is identical; If the content of described SIP URI or tel URI comprises all the elements of a public identifier in the subscription data, determine that then this public identifier is the public identifier that carries in the described sip message; Otherwise, determine and can't from described sip message, obtain public identifier.

For the other system that uses Session Initiation Protocol, the method for processing public identifier and in like manner above-mentioned repeats no more.

From the above, the message part that the present invention comprises public identifier is defined as the subclass of SIP URI or Tel URI, thereby make message part that network entity can comprise according to subclass from the SIP URI of sip message header field or Tel URI, accurately extract public identifier, avoided using in the prior art the unclear problem of IMPU.In addition, the public identifier that the acquisition user contracts in registration process also is kept on the network entity, makes network entity SIP URI in the sip message and described public identifier can be comprised matching ratio than accurately extracting public identifier.

Obviously, those skilled in the art can carry out various changes and modification to the present invention and not break away from the spirit and scope of the present invention.Like this, if of the present invention these are revised and modification belongs within the scope of claim of the present invention and equivalent technologies thereof, then the present invention also is intended to comprise these changes and modification interior.

Claims

1, a kind of method of handling public identifier in the SIP network is characterized in that, comprises the steps:

The device that receives described sip message is according to the defined content of public identifier, extract this partial content and revert to public identifier according to predetermined format from the SIP URI of sip message header field or Tel URI, described predetermined format is SIP URI form or Tel URI form.

2, the method for claim 1 is characterized in that, described public identifier adopts SIP URI form.

3, method as claimed in claim 2 is characterized in that, only comprises the user user parameter in the SIP URI part in the described public identifier.

4, the method for claim 1 is characterized in that, signatory described public identifier adopts the TelURI form.

5, method as claimed in claim 4 is characterized in that, when subscriber directory number adopted overall number, described public identifier did not comprise any parameter of Tel URI; Perhaps, when subscriber directory number adopts local number, with the part of the parameter p hone-context in the Tel URI part as public user identity.

6, a kind of method of handling public identifier in the SIP network is characterized in that, comprises the steps:

B, network entity are handled according to following comparative result:

7, method as claimed in claim 6 is characterized in that, when described relevant network entity determines that described SIP URI converts to for Tel URI, earlier SIP URI is reduced to Tel URI, carries out matching ratio then.

8, method as claimed in claim 7, it is characterized in that, when converting Tel URI to SIP URI, in SIP URI public identifier, increase the user user parameter that is used to show this conversion, and the whole phone of TelURL public identifier is described by telephone-subscriber and the reference record user part to SIP URI public identifier, the main frame or the domain name part of the SIP URI public identifier after concentrating the main frame of other signatory SIP URI public identifiers that comprise or domain name part as conversion the implicit registration under the Tel URL public identifier.

9, method as claimed in claim 8, it is characterized in that, if described implicit registration is concentrated and to be had a plurality of signatory SIP URI public identifiers, selects the main frame of default signatory SIP URI public identifier or domain name part or according to configuration information acquisition main frame or domain name part.

10, method as claimed in claim 7 is characterized in that, when converting Tel URI to SIP URI, inquires about and obtain SIP URI public identifier according to Tel URI from the public identifier change server.

11, method as claimed in claim 10 is characterized in that, if the SIP URI that returns of public identifier change server comprises regular expression, and then according to regular expression conversion SIP URI, and with the public identifier of transformation result after as Tel URI conversion.

12, a kind of SIP network equipment is characterized in that, comprising:

Comparison means is used for that sip message is comprised the public identifier that the SIP URI of public identifier or Tel URI and user contract and compares;

Determine device, be used for handling according to comparative result:

13, the SIP network equipment as claimed in claim 12 is characterized in that, also comprises:

Conversion equipment is used for determining that described SIP URI when converted, is reduced to Tel URI with SIPURI by Tel URI before relatively.

14, a kind of SIP network system is characterized in that, comprising:

Be used for public identifier and relevant information as the SIP URI or the Tel URI of sip message header field and send sip message the device of a content-defined subclass for SIP URI or Tel URI content that wherein said public identifier comprises;

Be used for according to the defined content of public identifier, extract this partial content and revert to the device of public identifier according to predetermined format from the SIP URI of the sip message header field that receives or Tel URI, described predetermined format is SIP URI form or Tel URI form.