WO2008006311A1

WO2008006311A1 - A method and corresponding device for using of user terminal identifier

Info

Publication number: WO2008006311A1
Application number: PCT/CN2007/070215
Authority: WO
Inventors: Youzhu Shi
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2006-07-05
Filing date: 2007-07-02
Publication date: 2008-01-17
Also published as: CN101102583A

Abstract

A method and corresponding device for using of user terminal identifier are provided. The method includes the following steps. The terminal identifier information sender sends a message carrying the user terminal identifier allocated by user's home network. Said user terminal identifier can be a GRUU, a contact address, a sub-address of the user terminal, or a network resource identifier in common service identifier. The terminal identifier information receiver receives said message, and uses said user terminal identifier to respond to the terminal indicated by the identifier information.

Description

User manual and method for using terminal identification

[1] Technical field

[2] The present invention relates to the field of communications, and in particular, to a method and apparatus for using a user terminal identifier.

[3] Background of the invention

[4] Session initiation protocol (SIP)

) is an application layer control protocol for establishing, changing, and terminating multimedia sessions or calls, including multimedia conferencing, distance learning, Internet telephony, and the like.

[5] In the SIP protocol, SIP

Messages are addressed by the user ID. Generally, user identities are classified into public identities (health identities).

Two types, the common identifier is the identifier issued by the user to the public, for other users or the network to initiate a communication request, such as a phone number. In the SIP protocol, the format of the common identifier is generally in the URI format. The private identity is assigned by the user's home network operator and is generally used for registration, authentication, authentication, management, accounting, etc., such as the Subscriber Identity Module (SIM) card number.

[6] in SIP

In the protocol, one user can have multiple registered terminals, that is, multiple user terminals can share a common identifier. Obviously, when another user or network initiates a communication request to the multi-terminal user, the communication request is initiated with its shared identity, so it is impossible to determine which terminal to establish communication with. For example, User A has two registered terminals, one is a mobile terminal and the other is a fixed terminal. User B wants to establish communication with user A's mobile terminal, user B to user A

The common identity initiates a call, User A

The two terminals may ring at the same time. If the fixed terminal is answered by the off-hook, user B

Establish a call contact with the fixed terminal.

[7] In order to solve the above problem, the most direct method is that the user specifies the terminal identifier of user A in advance after initiating a call request. Currently, a method for addressing a user terminal is as follows: The globally routable user agent uniform resource identifier (GRUU), the user B can directly use the GRUU of the mobile terminal of the user A to initiate a call request to establish a call connection with the mobile terminal of the user A.

[8] In carrying out the process of the present invention, the inventors have found that the above prior art has the following problems:

[9] Unlike the common identity of the user, the GRUU is generally obtained after the user terminal is registered, and the GRU

The U naming convention is undefined. It is difficult for GRUU to be distributed by means of a directory or a verbal method like a shared logo, and it is difficult for a user to memorize other users' GRUUs. Therefore, the calling user needs to obtain the GRUU of the called user in other ways before using the GRUU to initiate a session request.

[10] Although the calling user terminal can obtain the GRUU of the called user terminal in the process of establishing a communication connection with the called user terminal, for example, the user B initiates a call request to the user A, and a registered terminal of the user A answers and the user The B terminal establishes a call contact, and the user B terminal can obtain the GRUU of the answering terminal of the user A, and the answering terminal of the user A also obtains the GRUU of the user B terminal. However, the foregoing method can obtain the GRUU of the called user terminal only after the calling user terminal initiates the session request.

And only the GRUU of the called user terminal that is answered can be obtained. The calling user terminal still does not know the GRUU of the called user terminal before the first session request is initiated.

In addition, the subaddress of the user terminal also has the above problem.

[11] Summary of the invention

[12] An embodiment of the present invention provides a method and apparatus for using a user terminal identifier, and provides a complete method for notifying a GRUU to other users or networks outside the establishment of a communication connection, and using the GRUU, including the GRU U in charging and location. Use of business and other aspects.

[13] According to an aspect of an embodiment of the present invention, a method for using a user terminal identifier is provided, including the steps of:

[14] The user terminal identifies that the sender sends a message, where the message carries the user terminal identifier allocated by the user home network;

[15] The user terminal identifier receiver receives the message, and obtains the user terminal identifier, and the user terminal identifies the receiver to use the user terminal identifier to respond to the user terminal identifier corresponding party.

According to another aspect of an embodiment of the present invention, an apparatus for using a user terminal identifier is provided. The method includes: [17] a user terminal identifier sending unit, configured to send a message, where the message carries a user home network allocation User terminal identification;

[18] The user terminal identifier receiving unit is configured to obtain the user terminal identifier from the received message, and then use the user terminal identifier to respond to the user terminal identifier corresponding party.

[19] BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings are intended to provide a further understanding of the invention, and are not intended to limit the invention. In the drawing:

1 is a flowchart of a method for using a user terminal identifier according to an embodiment of the present invention;

2 is a block diagram of an apparatus for using a user terminal identifier according to an embodiment of the present invention;

FIG. 3 is a flowchart showing a signaling according to a first embodiment of the present invention; FIG.

4 is a flow chart showing a first embodiment of the present invention;

Figure 5 is a flow chart showing a second embodiment of the present invention;

Figure 6 is a flow chart showing a third embodiment of the present invention;

Figure 7 is a flow chart showing a fourth embodiment of the present invention;

8 is a flow chart showing a fifth embodiment of the present invention;

9 is a flow chart showing a sixth embodiment of the present invention.

[30] Mode for carrying out the invention

[31] Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings.

An embodiment of the present invention provides a method for using a user terminal identifier, including the following steps: Step S102

The user terminal identifier information sender sends a message, where the message carries the user terminal identifier; Step S104, the user terminal identifier information receiver receives the message, obtains the user terminal identifier; and step S106, the user terminal identifier information receiver uses the user terminal identifier to the user The terminal identification information corresponding party responds.

[33] Preferably, the above message includes an identifier notification message or a service message.

[34] When the message is an identification notification message, step S106

The response may be a communication request to the user terminal identification information corresponding party, or a communication hold, or a communication release, etc., wherein the identification notification message includes a SIP NOTIFY message, or SIP PUBLISH ( release the news. The user terminal identification information is carried in the information application body of the event package in the message, where the event package may be a dialog event package, or a presence (presentation)

An event package, or an event package that represents a callback.

[35] When the message is a service message, step S106

The response may be a service information storage, or a service information query service, etc., where the service information may be location information or communication record information, etc., and the communication record information may be communication charging information, or Communication tracking information, or communication log information, etc.

[36] Preferably, the user terminal identifier may be GRUU

Or the sub-address of the user terminal, or the contact address of the user terminal, or the sub-address of the user terminal, or a certain network resource identifier under the public service identifier. The network resource identifier can distinguish multiple network resources under one public service identifier. The user terminal identifier may be a user terminal identifier of the sender of the user terminal identifier information, or a terminal identifier of another user terminal saved by the sender of the user terminal identifier information, or a terminal identifier of the peer end of the session where the sender of the terminal identifier information is located.

An embodiment of the present invention provides a device 200 for using a user terminal identifier. Includes:

[38] terminal identification information transmitting unit 202

And sending a message, where the message carries the user terminal identifier; and the terminal identifier information receiving unit 204 is configured to receive the message, obtain the user terminal identifier, and then respond to the terminal identifier information corresponding party by using the user terminal identifier.

[39] Preferably, the message comprises an identification notification message or a service message.

[40] When the message is an identification notification message, the response may be to initiate a communication request, or a communication hold, or a communication release to the user terminal identification information corresponding party, wherein the identification notification message includes a SIP NOTIFY message, or SIP PUBLISH

Message. The user terminal identification information is carried in the information application body of the event package in the message, wherein the event package may be a dialog event package, or a presence event package, or an event package indicating a callback.

[41] When the message is a service message, the response may be to provide a service information storage, or a service information query service, etc. to the terminal identification information corresponding party, where the service information may include location information or communication record information, etc., The record information may be communication billing information, or communication trace information, or communication log information, and the like. [42] Preferably, the user terminal identifier may be a GRUU, or a sub-address of the user terminal, a contact address of the user terminal, or a certain network resource identifier under the public service identifier.

[43] and so on. The user terminal identifier may be a terminal identifier of the sender of the terminal identifier information, or a terminal identifier of another user terminal saved by the sender of the terminal identifier information, or a terminal identifier of the peer end of the session where the sender of the terminal identifier information is located.

[44] First Embodiment

Figure 3 shows a signaling flow diagram in accordance with a first embodiment of the present invention, Figure 4

Is a flow chart in accordance with a first embodiment of the present invention.

[46] In step S402, user A terminal and user B

The terminal is already in the session, such as a call. In step S404, the user C terminal initiates a session state subscription to the user B, and sends a SIP SUBSCRIBE subscription message. In the subscription message, the Event event header field is set to the dialog dialog event package, which means to user B.

To subscribe to its current session state, an example is: Event: dialog. In step S406, the user B terminal receives the SIP SUBSCRIBE message and returns a 200 OK response code. If User B has multiple registered terminals, each registered terminal can receive the SIP SUBSCRIBE message.

[47] Next,

[48] In step S408, the user B terminal sends a SIP to the user C.

NOTIFY notification message, the message body carries the GRUU information of the user B terminal, and the user A terminal

GRUU information, examples are as follows:

[49] Event: dialog

[50] Content- Type: application/dialog-info+xml

[51]

[52] <local>

[53] <targeturi='sip:alice@pc33.example.com'gruu='f81d4fae-7dec-l ld0-a765'>

[54] </local>

[55] <remote>

[56] <target uri='sip :confid @ host3.example.net' gruu='hdg7777ad7aflzig8sf7'>

[57] </remote> [58] The Content-Type header field is set to "application/dialog-info+xml", which means that this part of the message body is in Extended Markup (Extended Markup).

Language, referred to as XML) describes the dialog information application. The content of the dialog information application is only an example, and the call identifier (call-id), local-tag (local-tag), remote tag (remote-tag), state (state), etc. are omitted. "local" means local information, "uri" means that this is the local resource identifier, that is, the shared user ID of the user B terminal ("sip:alice@pc33.example.com"), "gr uu" means this is this The GRUU information of the terminal, that is, the GRUU of the user B terminal ("f81d4fae-7dec-l ld0-a7 65"); "remote" indicates the peer information, and "uri" indicates that this is the unified resource identifier of the peer end, that is, the shared by the user A terminal. The user ID ("sip:confid@host3.example.net"), "gruu" indicates that this is the GRUU information of the peer, that is, the GRUU of the user A terminal ("hdg7777ad7aflzig8sf7").

[59] Next, in step S410, the user C terminal receives the NOTIFY message to obtain the user B.

GRUU information of the terminal and user A terminal, return 200 OK response code. Finally, in step S412, user C initiates a communication request to the GRUU counterpart.

[60] It can be seen from the above embodiment that the GRUU notification message (SIP NOTIFY message) sent by the user B terminal to the third party (user C) does not belong to the established SIP session contact, and the GRUU notification message can be transmitted. In addition to the sender's own GRUU information, the peer GRUU information of the SIP session in which the sender is located may be transmitted, that is, the GRUU information of the user A terminal.

[61] In the above embodiment, the notification message is a SIP NOTIFY message. In addition, the notification message can also be

SIP PUBLISH publishes messages and so on. The GRUU of the terminal can be carried in the header field of the message or in the message body.

Ι π Λ∑! ,.

[62] In the first embodiment, the GRUU information is used in conjunction with the dialog event package, via dislog

The information application body passes the relevant GRUU. GRUU

Information can also be used in conjunction with other event packages to convey relevant GRUU information through the application body of these event packages, such as event packages that describe session state or call status.

[63] Second Embodiment

[64] Next, a second embodiment in which the GRUU information and the presence event packet are used together will be described with reference to the drawings.

Figure 5 is a flow chart showing a second embodiment in accordance with the present invention.

[66] In step S502, user A adds user B to his own 'buddy list'. Assume User B There are two registered terminals, then the user A's buddy list can distinguish the two registered terminals. User A initiates a subscription to the presence status to User B, and subscribes to the event package as a presence.

[67] In step S504, the user B or the network notifies the user A of the current presentation status of the user B (ie, whether it is online), and the presence status notification message includes the GRUU information of each registered terminal of the user B and the current The presentation status corresponding to the terminal.

[68] Next, in step S506, user A records user B in the 'buddy list'

Registered terminal and its corresponding presentation status. It should be noted that what is recorded is not User B and its corresponding rendering status. Then, in step S508, user A

A communication request is initiated to a registered terminal of user B by clicking in the 'buddy list'.

[69] Third Embodiment

[70] Below, the GRUU is described in conjunction with the drawings.

The third embodiment in which the information is used in conjunction with the event package representing the callback.

Figure 6 is a flow chart in accordance with a third embodiment of the present invention.

[72] In step S602, user A calls user B, and user B is currently busy or long called. In step S604, user A activates a busy call completion service or a no answer call completion service. In step S606, the network goes to user B.

Subscribe to an event package that identifies a busy call completion or a no answer call completion.

[73] If User B has more than one registered terminal, if User A still wants to be called by the original user B

The terminal calls back, then in step S608, user B

The event packet application body that informs the network that the busy call is completed or the non-answered call is completed, and carries the GRUU information corresponding to the user B terminal and its corresponding state. In step S610, user A initiates a callback to the designated user B terminal.

[74] In the above three embodiments, GRUU

Information is used to initiate a call to its corresponding user terminal. In addition, GRUU

Information can also be used for call hold, call release, and the like.

[75] In the above three embodiments, the user is actively obtained to acquire other user terminals GRUU.

Information, and then initiate a communication request to the acquired GRUU information, and the GRUU

The user terminal corresponding to the information establishes a communication link. In addition, GRUU Not only limited to terminal addressing in communications, but also other broader uses, including billing, location services, tracking, and the like.

[76] In addition, it should be noted that, in addition to the above user terminal, GRUU can be sent.

In addition to the notification message, the network element that stores the GRUU information of the user terminal in the network may also send the GRUU that carries the GRUU information of the terminal.

The notification message, for example, the network element may be an access point, a registration point, or the like of the user terminal in the network. That is, the GRUU information sender may be a user terminal or a network element. Similarly, the GRUU information receiver may be a user terminal or a network element.

[77] Fourth Embodiment

Figure 7 is a flow chart showing a fourth embodiment of the present invention.

[79] The GRUU sender is a session processing NE, GRUU

The information receiver is a billing processing network element.

[80] In step S702, during the user communication establishment process, during communication, or after the communication ends, the GRUU information transmission direction sends the communication-related charging information to the GRUU information receiving party, where the GRU of the communication party is included.

U information.

[81] In step S704, the GRUU information receiver receives the information, and acquires the GRUU of the communication party.

. In step S706, the GRUU information receiver is based on the received GRUU.

The information clearly indicates the cost of the communication, and which terminal of the communication party is associated with the fee, for example, the GRUU information of the communicating party is displayed in the generated communication bill.

[82] Generally, the GRUU information sending direction can be transmitted by the GRUU information receiving party.

The Diameter protocol, that is, the GRUU information of the communicating party needs to be extended in the Diameter protocol.

Fifth Embodiment

8 is a flow chart showing a fifth embodiment of the present invention.

[85] The GRUU sender is a location service client, GRUU

The information receiver is a location business client.

[86] In step S802, the GRUU information transmission direction GRUU

The information receiver sends a message describing the location information of the client or a message of the location query of the client, where the client GRUU information is carried. In step S804, GRUU The information receiver receives the message and obtains the GRUU information. In step S806, the GRUU information receiver saves the client location information or returns the client location information.

[87] In general, XML carried in SIP messages or HTTP messages

Content to describe client location information, ie, need to extend client GRUU information in client location information; and XML content or Diameter carried through HTTP messages

The message describes the client location query parameters, ie, the client GRUU information needs to be extended in the client location query parameters.

[88] Sixth Embodiment

9 is a flow chart showing a sixth embodiment of the present invention.

[90] The GRUU sender is a tracking maintenance network element, GRUU

The information receiver is a session processing network element.

[91] In step S902, the GRUU information transmission direction GRUU

The information receiver sends a tracking command, which carries the GRUU information of the tracked party. In the steps

In S904, the GRUU information receiver receives the instruction. In step S906, GRUU

Information receiving direction GRUU information sender returns GRUU

The communication status of the tracked party corresponding to the information to accurately track the communication status of the specific terminal.

[92] As can be seen from the third to sixth embodiments described above, the GRUU information transmission direction GRUU

The information receiver sends the GRUU of the terminal

The information is not used to address the terminal in the communication, but to provide a service such as information preservation and inquiry in addition to the communication service, that is, the GRUU information receiver uses the GRUU.

The information positioning terminal provides related service information storage and service information inquiry operations for the terminal, wherein the service information refers to location information, communication record information, etc., and communication record information such as communication charging information, communication tracking information, and communication log Information, etc.

[93] In addition, it should be noted that the GRUU is only a way of identifying the user terminal, and the GRUU enables the user to establish a communication relationship directly with the terminal that he wants to establish a communication connection with. Obviously, using the above-mentioned embodiments of the present invention, other user terminal identification methods (for example, the contact address of the user terminal, the sub-address of the user terminal, etc.) can also be used for the purpose, that is, the embodiment of the present invention is equally applicable to other users. Terminal identification method. The subaddress of the GRUU and the user terminal are provided by the user home network. The user terminal identifier, where the GRUU may be generated by the user after registration, and the sub-address of the user terminal may be pre-allocated as the subscription data in the user home network by signing the contract; the contact address of the user terminal is generally It is the user terminal identifier provided by the user accessing the network. Generally, since the home network is determined by the subscriber in the contracting carrier, unless the subscriber subscription changes, the user home network generally remains unchanged. Thus, when the user roams, the user terminal identifier assigned by the access network changes. The user terminal identifier assigned by the home network may remain unchanged. Therefore, the user terminal identifier provided by the home network is more suitable for providing various services to the user. The user terminal identifier provided by the access network may also be used to provide various services for the user, but need to be at the user terminal. Update notification after the identity has changed.

[94] For the application scenario of a network resource identifier in the public service identifier, the method for using the network resource identifier in the embodiment of the present invention is further described by taking the network resource identifier as the conference resource identifier as an example.

[95] The conference initiates a message to the conference server to request a conference resource. For example, the conference initiator sends a SIP INVITE message to the conference server. The SIP INVITE message example is as follows:

[96] INVITE sip onference-factoryl @ mrfcl.homel.net SIP/2.0

[97] Among them, ' sip:conference-factoryl @ mrfcl.homel.net ' is the public service identifier of the conference business.

[98] The conference server is receiving a SIP INVITE

After the message, the conference resource is allocated for the public service identity of the conference service. After other conference participants are invited to join the above conference, other conference participants obtain the network resource identifier of the conference resource through the invited process. After the network resource identifier of the conference resource is obtained, the other conference participants send a SIP INVITE message to the conference server. The message example is as follows:

[99] INVITE sip onference-factory 1 @ mrfc 1.home 1.net;grid=conference 1 SIP/2.0 [100] where ' conferencel

'For the network resource identifier of the conference resource allocated above, the corresponding parameter name is named 'grid' in the example.

[101] SIP INVITE sent by other conference participants

The message is routed to the corresponding conference server according to the public service identifier of the conference service in the message, and according to

' conferencel in the SIP INVITE message

'Locate to the above allocated conference resources. That is, using the user terminal identification class under the common user ID Similarly, the network resource identifier corresponding to the public service identifier may be located, and the network resource may be allocated by Linyi, such as a conference resource, or may be fixed, such as a network resource specified by the user in the voice mailbox, the user. Initiate a call to its own voice mailbox, examples of which are as follows:

[102] INVITE sip:vmail@homel.net;grid=alice SIP/2.0

[103] Among them, 'sip:vmail@homel.net' is the public service identifier of the voice mailbox, and 'alice' is the voice mailbox resource fixedly allocated for the user. It can be assigned by the user in the subscription voice mailbox.

[104] Obviously, those skilled in the art will appreciate that the various modules or steps of the present invention described above can be implemented with a general purpose computing device, which can be centralized on a single computing device or distributed across multiple computing devices. Optionally, they may be implemented by program code executable by the computing device, such that they may be stored in the storage device by the computing device, or they may be separately fabricated into individual integrated circuit modules, or Implementing multiple modules or steps in them as a single integrated circuit module. Thus, the invention is not limited to any specific combination of hardware and software. It is to be understood that changes in these specific embodiments will be apparent to those skilled in the art without departing from the scope of the invention.

The above description is only the preferred embodiment of the present invention, and is not intended to limit the present invention, and various modifications and changes can be made by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and scope of the present invention are intended to be included within the scope of the present invention.

Claims

Claim

[1] 1. A method for using a user terminal identifier, characterized in that the method of using the method comprises the following steps:

The user terminal identifies that the sender sends a message, where the message carries the user terminal identifier allocated by the user home network;

The user terminal identifier receiving the message receives the user terminal identifier, and the user terminal identifier receiving party responds to the user terminal identifier corresponding party by using the user terminal identifier.

[2] The method according to claim 1, wherein the message comprises one or more of the following: an identifier notification message, a service message.

[3] The method of using according to claim 2, wherein the identification notification message

Includes one or more of the following: Session Initiation Protocol Notification SIP NOTIFY

The message, session initiation protocol issues a SIP PUBLISH message.

[4] The method of using the user terminal according to claim 2, wherein the user terminal identification information is included in an information application body of the event package in the identification notification message.

[5] The use method according to claim 4, wherein the event package comprises one or more of the following: a session dialog event package, a presence event package, and an event package indicating a callback.

[6] The method of using the method according to claim 2, wherein the service message comprises one or more of the following: an HTTP message, a SIP message, and a Diameter message.

[7] The method of claim 1, wherein the response comprises one or more of the following: identifying, by the user terminal, a corresponding party to initiate a communication request, a communication hold, a communication release, and a service Information storage service, service information inquiry service, and joining the conference.

[8] The method of using the method according to claim 7, wherein the service information comprises one or more of the following: location information, communication record information.

[9] The method of using the method according to claim 8, wherein the communication record information comprises one or more of the following: communication charging information, communication tracking information, and communication log information.

[10] The method of using the user terminal according to any one of claims 1 to 9, wherein the user terminal identifier comprises one or more of the following:

Globally routable user agent uniform resource identifier, subaddress of user terminal, The network resource identifier under the public service identifier and the contact address of the user terminal.

[11] The method of using the user terminal according to any one of claims 1 to 9, wherein the user terminal identifier comprises one or more of the following: the user terminal identifies a terminal identifier of the sender, The user terminal identifies the terminal identifier of the user terminal saved by the sender, and the terminal identifier of the peer end of the session where the user terminal identifies the sender.

[12] 12. The device for using the user terminal identifier, wherein the device for use includes: a user terminal identifier sending unit, configured to send a message, where the message carries a user terminal identifier allocated by the user home network;

The user terminal identifier receiving unit is configured to obtain the user terminal identifier from the received message, and then use the user terminal identifier to respond to the user terminal identifier corresponding party.