CN101547430A

CN101547430A - Session method, device and system

Info

Publication number: CN101547430A
Application number: CN200810066198A
Authority: CN
Inventors: 时书锋; 闫学霞; 李明
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2008-03-24
Filing date: 2008-03-24
Publication date: 2009-09-30
Anticipated expiration: 2028-03-24
Also published as: CN101547430B

Abstract

The invention discloses a session method, which comprises that: a second function entity receives a first session request message sent by a first function entity, and sends a second session request message to the first function entity; the second function entity receives a second session request response message sent by the first function entity, wherein the second session request response message is sent after the first function entity determines that the second session request message is associated with a first session request message sent by the first function entity; and the second function entity determines that the second session request response message is associated with the first session request message, and sends a first session request response message to the first function entity. In the method, a terminal expands application layers of the function entities in session, so that the function entities in the session can realize the function of association confirmation of a plurality of pairs of interactively executed session application messages which cannot be realized by a low layer protocol.

Description

A kind of session method, equipment and system

Technical field

The present invention relates to communication technical field, relate in particular to a kind of method, apparatus and system of session.

Background technology

EPS (Evolved Packet System, the packet switching system of evolution) network comprises UMTS (the Universal Mobile Telecommunications System) land radio access web (E-UTRAN of evolution, Evolved UMTS Terrestrial Radio Access Network), Mobility Management Entity (MME, Mobility Management Entity), service gateway entity (Serving GW, ServingGateway), grouped data network gateway entity (PDN GW, Packet Data Network Gateway), external packet data network (PDN, Packet Data Network) interface, "Policy and Charging Rules Function entity (PCRF, Policy and Charging Rule Function), home network server (HSS, HomeSubscriber Server) is used for storing user subscription information, service universal grouping wireless business supporting node functional entitys such as (SGSN, Serving GPRS Supporting Node).

When user's start is linked into the EPS network, perhaps the user leaves original accompanying wireless coverage that MME managed, when moving to the new wireless coverage that MME managed, the attachment flow that is taken place as shown in Figure 1, in the embodiments of the invention, to be called the current MME that adheres to of user for the current EPS of the being linked into network of user provides the MME of service, the MME that will before the MME that service is provided for the user before the current MME that adheres to of user is called the user, adhere to.

In the described flow process of Fig. 1, MME receive from user terminal UE adhere to request after, at first can carry out authentication to this user according to demand, in case the user has passed through authentication, as step S102, MME can initiate the position and upgrade (Update Location) request to the HSS that this user belonged to, to upgrade the current accompanying MME title/address of user of writing down among the HSS; If record user another accompanying MME title/address before among the HSS, then HSS will send canceling position request message (Cancel Location) and give the MME that adheres to before the described user in step S103, and the indication user is linked in the EPS network by other MME; HSS receives that canceling position request response (CancelLocation Ack) that the MME that adheres to before the user among the step S104 sends afterwards, in step S105, can send and insert user contracting data request (InsertSubscriber Data) to the current accompanying MME of user, by this request message user's subscription data is carried the current accompanying MME to the user, after this MME receives user contracting data from HSS, can in step S106, return the response of inserting user contracting data request (Insert Subscriber Data) message and give HSS according to the user contracting data that receives to the inspection that the user roams restriction and access control.HSS after receiving this response message, home position update request response message (UpdateLocation Ack) in step S107; After above-mentioned flow process, the user successfully is linked in the EPS network; In addition, MME and the canceling position flow process between the HSS that above-mentioned steps S103 adheres to the step S104 user also can be carried out the user is attached to new MME after, but current MME that adheres to of user and the position between the HSS upgrade with the insertion subscriber data message then be that the user successfully is linked into the step that the EPS network must be carried out alternately.

At present, the above-mentioned realization between MME and HSS has been defined as Diameter to the underlying protocol that process adopted of subscription authentication and mandate.Diameter is a kind of aaa protocol of supporting based on the AAA framework of IP technology, mainly realizes authentication, mandate, charging (AAA) function, is widely used in the communication network.Diameter is a kind of peer protocol (Peer-To-Peer protocol), and each supports the network function node of Diameter all to be called Peer.In general, the Peer of initial request messages side is called as DiameterClient, and the Peer that receives and handle the requesting party is called as Diameter Server.Each node can the initiation session connection request, also can be the recipient of conversation request, and so-called Client and Server are the notions on the Diameter application-level logic, but not notion physically.At same Peer, in different session interactions, can bear different roles.Diameter itself does not support that the application layer messages in the conversation procedure is nested, just in conversation procedure, after Diameter Server receives the application request of Diameter Client about session 1, can't initiate new application request to Diameter Client before should giving Diameter Client echoing about session 1; If set up new session between Diameter Client and the Diameter Server, be that Diameter Client is under the situation of waiting for Diameter Server response, receive the application request about session 2 that Diameter Server initiates, Diameter Client can't determine related between received application request about session 2 and the session 1.

Therefore, use Diameter, can't realize between MME and the HSS that Update Location's and two pairs of message of Insert Subscriber Data in the above-mentioned flow process shown in Figure 1 is mutual, because the Diameter layer is not supported these two pairs of message are placed in a conversation procedure and is finished, HSS is after receiving Update Location message, to set up a new session connection with MME and send Insert Subscriber Data request, MME receives this request, can't determine that whether it is related with the Update Location request of issuing HSS before, causes the user can not successfully be linked into the EPS network.

Summary of the invention

Main purpose of the present invention is to provide a kind of session method, equipment and system, finishes many sessions that interacting message is carried out in application layer conversation process realize to use Diameter.

In order to realize purpose of the present invention, embodiments of the invention provide following technical scheme:

A kind of session method, the underlying protocol that described session is adopted is a Diameter, comprising:

Second functional entity sends second conversation request message to described first functional entity after receiving first conversation request message of first functional entity transmission;

Described second functional entity receives the second conversation request response message that described first functional entity sends, wherein, the described second conversation request response message is to send after described first functional entity is determined described second conversation request message and first conversation request message that self sends is associated;

Described second functional entity determines that the described second conversation request response message is associated with described first conversation request message, sends the first conversation request response message to described first functional entity.

A kind of conversational system, the underlying protocol that described session is adopted are Diameter, and described system comprises:

First functional entity, be used for sending first conversation request message to second functional entity, and after receiving second conversation request message of described second functional entity transmission, determine that described second conversation request message is associated with first conversation request message that self sends, and sends the second conversation request response message to described second functional entity;

Described second functional entity, be used for after first conversation request message that receives described first functional entity transmission, send second conversation request message to described first functional entity, and behind the second conversation request response message that receives described first functional entity transmission, determine that the described second conversation request response message is associated with described first conversation request message that receives, and sends the first conversation request response message to described first functional entity.

It is Diameter that a kind of conversational device, described conversational device are carried out the underlying protocol that session adopts, and described device comprises:

The first session processing unit is used to send first conversation request message and receives the first conversation request response message;

The second session processing unit is used for after receiving second conversation request message, determines that described second conversation request message is associated with first conversation request message that self sends, and sends the second conversation request response message.

First conversation element is used to receive first conversation request message, and sends the first conversation request response message;

Second conversation element, be used for after described first conversation element receives first conversation request message, send second conversation request message, and receive the second conversation request response message, and after determining the described second conversation request response message and described first conversation request message that receives being associated, notify described first conversation element to send the first conversation request response message.

The embodiments of the invention terminal is expanded by the function to the application layer of the functional entity that carries out session, feasible application layer of carrying out the functional entity of session can realize the irrealizable function of many conversation messages to mutual execution being carried out related affirmation of underlying protocol, and the final functional entity correct execution session command of carrying out session that makes, finish required function.

Description of drawings

Fig. 1 is attached to schematic flow sheet in the network for user in the prior art;

Fig. 2 is the schematic flow sheet of the inventive method embodiment one;

Fig. 3 is the schematic flow sheet of the inventive method embodiment two;

Fig. 4 is the schematic flow sheet of the inventive method embodiment three;

Fig. 5 is the schematic flow sheet of the inventive method embodiment four;

Fig. 6 is the schematic flow sheet of the inventive method embodiment five;

Fig. 7 is the schematic flow sheet of the inventive method embodiment six;

Fig. 8 is the schematic flow sheet of the inventive method embodiment seven;

Fig. 9 is the schematic flow sheet of the inventive method embodiment eight;

Figure 10 is the schematic flow sheet of the inventive method embodiment nine;

Figure 11 is the schematic flow sheet of the inventive method embodiment ten;

Figure 12 is the schematic flow sheet of the inventive method embodiment 11;

Figure 13 is the schematic flow sheet of the inventive method embodiment 12;

Figure 14 is the composition frame chart of system embodiment of the present invention.

Embodiment

In order to make purpose of the present invention, technical scheme and advantage clearer,, embodiments of the invention are further elaborated below in conjunction with drawings and Examples.

The embodiment of the invention one, as Fig. 2, the application scenarios of present embodiment two is: Diameter uses first functional entity and Diameter and uses and need to carry out interacting message between second functional entity and finish certain function, after requiring first functional entity to send conversation request message Req1, second functional entity send give first functional entity about the conversational response of Req1 request before, need send another conversation request message Req2 to first functional entity, after having only second functional entity to receive the response message Rsp2 of first functional entity about Req2, second functional entity just returns conversational response message Rsp1 and gives first functional entity.Present embodiment one comprises:

Step S201: first conversation request message that first functional entity sends to second functional entity;

Step S202: second functional entity sends second conversation request message to described first functional entity;

Step S203: first functional entity sends the second conversation request response message to second functional entity after determining described second conversation request message and first conversation request message that self sends being associated;

Step S204: second functional entity determines that the described second conversation request response message is associated with described first conversation request message, sends the first conversation request response message to first functional entity.

Embodiments of the invention one are expanded by the application level function to the functional entity that carries out session, make the functional entity that carries out session can realize the irrealizable function of many conversation messages to mutual execution being carried out related affirmation of underlying protocol, and the final functional entity correct execution session command of carrying out session that makes, finish required function.

The embodiment of the invention two, as Fig. 3, application scenarios such as embodiment one, the session method of the embodiment of the invention two comprises:

Step S301: first functional entity sends the first conversation request message Req1, session identification parameter in the underlying protocol of described Req1 message extends this as session 1 (Session 1), in addition, also carry the application layer conversation relevant parameter in the described Req1 message, the value of described application layer conversation relevant parameter can be indicated need in the session to be associated many to message, first or second functional entity can carry out association to many in the session to message according to described application layer conversation relevant parameter, the value of described application layer conversation relevant parameter can be generated in this locality or be obtained by alternate manner by first functional entity, in the present embodiment one, described application layer conversation relevant parameter is Para1, and the value of described Para1 is made as application layer conversation association identification 1;

Step S302: after second functional entity is received the first conversation request message Req1, send the second conversation request message Req2 to first functional entity, session identification parameter in its underlying protocol extends this as session 2 (Session 2), also carry application layer conversation relevant parameter Para1 in the described Req2 message, described Para1 value is identical with the value of Para1 in the Req1 message, is application layer conversation association identification 1 also;

Step S303: after first functional entity is received Req2 message, according to wherein be application layer conversation association identification 1 with the value of application layer conversation relevant parameter Para1, judge itself and Req1 message relating, after then handling accordingly, send the second conversation request response message Rsp2 to second functional entity, described Rsp2 carries application layer conversation relevant parameter Para1, and its value also is made as application layer conversation association identification 1;

Step S304: after second functional entity acknowledges receipt of Rsp2 response message about Req2, determine the first conversation request message Req1 of association according to application layer conversation relevant parameter Para1 wherein, return the first conversation request response message Rsp1 to first functional entity, carry parameter Para1, its value is made as application layer conversation association identification 1, and whole application layer conversation is finished dealing with.

The embodiment of the invention two is by carrying out increasing application layer conversation relevant parameter Para1 among related many each message Req1, Req2 to session, Rsp1, the Rsp2 at needs, and the value of described parameter is set to identical value---application layer conversation association identification 1, first functional entity and second functional entity are according to the value of the application layer conversation relevant parameter Para1 that carries in the conversation message, just can judge these message is associated together, realize the association of a plurality of conversation messages, thereby required function is finished in the correct execution order.

The invention process three, to realize that by Diameter the attaching process of user in MME is example between MME and the HSS, as shown in Figure 4, the conversation procedure between MME and the HSS comprises:

Step S401: the current MME that adheres to of user sends the first conversation request Update Location, session identification parameter in its underlying protocol extends this as session 1 (Session 1), except carrying relevant user information, carry application layer conversation relevant parameter Dialog-Id simultaneously, the Dialog 1 of the session that the Dialog-Id value is carried out for the indication that generated in this locality by MME or obtain by alternate manner and HSS;

Step S402:HSS receives Update Location request message, after other of line correlation of going forward side by side handled, send the second conversation request message Insert Subscriber Data to MME, session identification parameter in its underlying protocol extends this as session 2 (Session 2), carry application layer conversation relevant parameter Dialog-Id simultaneously, its value is made as Dialog1;

After step S403:MME receives that carrying Dialog-Id is made as the Insert Subscriber Data request message of Dialog1, judging it is that the Update Location of Dialog1 is related with the Dialog-Id that sends before, after handling accordingly, send the second conversation request response message Insert Subscriber DataAck to HSS, carry parameter Dialog-Id simultaneously, its value is made as Dialog1;

After step S404:HSS receives that carrying Dialog-Id is made as the Insert Subscriber DataAck message of Dialog1, determine the first related conversation request message Update Location according to wherein application layer conversation relevant parameter Dialog-Id, return to MME and carry the first conversation request response message Update Location Ack that Dialog-Id is Dialog1.The user adheres to successfully at MME.

The embodiment of the invention three is by increasing an application layer conversation relevant parameter Dialog-Id in all message that need to carry out two related sessions between MME and HSS, and it is made as identical value---Dialog1, MME and HSS receive carry this parameter and value all identical message the time, just can judge these message is associated together, what realization underlying protocol Diameter can't realize carries out the association affirmation to a plurality of conversation messages of application layer, thereby make MME and the order of HSS correct execution, complete successfully user's adhering in network.

The embodiment of the invention four, the embodiment of the invention not only can be used for needing between two entities a plurality of conversation messages are carried out related scene, need carry out the scene of session association when can be used for the interacting message of a plurality of inter-entity simultaneously, just not only can apply to carry out related to a plurality of conversation messages between first functional entity and second functional entity, can also apply to the more function inter-entity, the embodiment of the invention is enumerated an example that has the 3rd functional entity to participate in session, as Fig. 1, Update Location in the flow process, Cancel Location and three pairs of message of Insert Subscriber Data mutual, this moment, HSS not only needed Insert SubscriberData message and Update Location message relating, and also needing can be with Cancel Location message and Update Location message relating.With first functional entity is the current access of user MME, second functional entity is HSS, the 3rd functional entity is an example for inserting MME before the user, as shown in Figure 5, finish the attaching process schematic diagram of user in the MME of current access by Diameter between MME that provides for the embodiment of the invention four and the HSS, MME that adheres to before the current MME that adheres to of user, the user and the conversation procedure between the HSS comprise:

Step S501: the current accompanying MME of user sends the first conversation request message UpdateLocation, session identification parameter in its underlying protocol extends this as session 1 (Session 1), except carrying relevant user information, carry application layer conversation relevant parameter Dialog-Id simultaneously, its value is for being generated in this locality by the current accompanying MME of user or by identifying of obtaining of alternate manner and a session Dialog1 that HSS carries out;

After step S502:HSS receives Update Location request message from the current accompanying MME of user, accompanying MME sends the 3rd conversation request message Cancel Location before the user, session identification parameter in its underlying protocol extends this as session 3 (Session 3), carry application layer conversation relevant parameter Dialog-Id simultaneously, its value be made as with first session in the identical Dialog1 of Dialog-Id parameter;

Step S503: after accompanying MME receives that carrying Dialog-Id is made as the Cancel Location request message of Dialog1 before the user, handle accordingly, send the 3rd conversation request response message Cancel Location Ack to HSS, carry application layer conversation relevant parameter Dialog-Id simultaneously, its value is made as Dialog1;

Step S504:HSS receives from accompanying MME before the user and carries after Dialog-Id is made as the 3rd conversation request response message Cancel Location Ack of Dialog1, determine that Cancel LocationAck is associated with Update Location request message, send the second conversation request message Insert Subscriber Data to the current accompanying MME of user, session identification parameter in its underlying protocol extends this as session 2 (Session2), carry application layer conversation relevant parameter Dialog-Id simultaneously, its value be made as with the UpdateLocation request message in identical Dialog1;

Step S505: after the current accompanying MME of user receives that carrying Dialog-Id is made as the InsertSubscriber Data request message of Dialog1, judging it is that the Update Location of Dialog1 is related with the Dialog-Id that sends before, after handling accordingly, send the second conversation request response message Insert Subscriber Data Ack to HSS, carry parameter Dialog-Id simultaneously, its value is made as Dialog1;

After step S506:HSS receives that carrying Dialog-Id is made as the Insert Subscriber DataAck response message of Dialog1, determine the first related conversation request message Update Location according to wherein application layer conversation relevant parameter Dialog-Id, return to the current MME that adheres to of user and carry the Update Location Ack response message that Dialog-Id is Dialog1.The user adheres to successfully at the MME of current access.

Embodiment of the invention four-way is crossed and need carry out increasing in each related message the application layer conversation relevant parameter when a plurality of session interaction of a plurality of inter-entity, what realization underlying protocol Diameter can't realize carries out association to a plurality of conversation messages of application layer, thereby make MME and the order of HSS correct execution, complete successfully user's adhering in network.

The embodiment of the invention five, to realize that by Diameter the attaching process of user in MME is example between MME and the HSS, as shown in Figure 6, the conversation procedure between MME and the HSS comprises:

Step S601: the current MME that adheres to of user sends the first conversation request Update Location, and the session identification parameter in its underlying protocol extends this as session 1 (Session 1);

Step S602:HSS receives Update Location request message, after other of line correlation of going forward side by side handled, send the second conversation request message Insert Subscriber Data to MME, session identification parameter in its underlying protocol extends this as session 2 (Session 2), the Diameter layer carries property value to many session identifications Acct-Multi-Session-Id that charges simultaneously, and its value is made as the session identification parameter S ession 1 in first conversation request message;

After step S603:MME receives that carrying property value is made as the Insert Subscriber Data request message of Session1 to Acct-Multi-Session-Id, it is related with the first conversation request message Update Location that sends before to judge it, after handling accordingly, send the second conversation request response message Insert Subscriber Data Ack to HSS, carry the parameter attribute value simultaneously to Acct-Multi-Session-Id, its value is made as Session 1;

After step S604:HSS receives that carrying property value is made as the Insert Subscriber Data Ack message of Session1 to Acct-Multi-Session-Id, determine that it is associated with the first conversation request message Update Location, return to MME that to carry property value be the first conversation request response message Update Location Ack of Session 1 to Acct-Multi-Session-Id.The user adheres to successfully at MME.

Embodiment of the invention five-way is crossed to be needed to carry out carrying property value to Acct-Multi-Session-Id in related a plurality of conversation messages between MME and HSS, and its value is made as session identification parameter (this parameter of portability also can not carried this parameter in first conversation request) in first conversation request message, when MME and HSS receive that carrying this parameter and value all is the message of the session identification parameter in first conversation request message, just can judge these message is associated together, what realization underlying protocol Diameter can't realize carries out association to a plurality of conversation messages of application layer, thereby make MME and the order of HSS correct execution, complete successfully user's adhering in network.In addition, a plurality of message of a plurality of inter-entity that the method for present embodiment five can be applied to embodiment three equally need related scene, and specific embodiment repeats no more.

The embodiment of the invention six, to realize that by Diameter the attaching process of user in MME is example between MME and the HSS, as shown in Figure 7, the conversation procedure between MME and the HSS comprises:

Step S701: the current MME that adheres to of user sends the first conversation request Update Location, and the session identification parameter in its underlying protocol extends this as session 1 (Session 1);

Step S702:HSS receives Update Location request message, after other of being correlated with handled, send the second conversation request message Insert Subscriber Data to MME, the session identification parameter in its underlying protocol extends this as session 2 (Session 2);

The first conversation request message Update Location that step S703:HSS will receive carries out related with the second conversation request message Insert Subscriber Data that sends and writes down incidence relation, the session identification parameter S ession Id of the Diameter layer of the first conversation request message Update Location and the session identification parameter S ession Id among the second conversation request message Insert Subscriber Data can be carried out associated record in the present embodiment, also can be according to IMSI (the International MobileSubscriber Identity of the user in two conversation request message, International Mobile Subscriber Identity) two message is carried out associated record, in other embodiments of the invention, incidence relation between the first conversation request message Update Location and the second conversation request message InsertSubscriber Data also can be recorded in other cellular logic entity, and HSS only need inquire about and determine that its incidence relation gets final product.

After step S704:MME receives the second conversation request message Insert Subscriber Data, related between the second conversation request message Insert SubscriberData that determines the first conversation request message Update Location and receive, MME determines two incidence relations between session, can determine by the IMSI that carries in two conversation messages; Because in the prior art, MME may receive the Insert Subscriber Data conversation request message that HSS sends in the position updating process, also may also can receive the user adheres to when user contracting data changes afterwards, the conversation request message of the Insert Subscriber Data that HSS sends, therefore after HSS sends in the MME Insert Subscriber Data conversation request message position updating process that need determine to receive, could determine incidence relation between first session and second session according to the IMSI that carries in the conversation message, MME need at first read the IMSI that carries among the second received conversation request message Insert SubscriberData, judge whether then to the first conversation request message Update Location of HSS transmission about described IMSI, if, then definite second conversation request message InsertSubscriber Data about described IMSI is the conversation request message in the position updating process, and related with the first conversation request message Update Location about described IMSI that self sends before;

After step S705:MME determines second session and first session association, send the second conversation request response message Insert Subscriber Data Ack to HSS;

After step S706:HSS receives the second conversation request response message Insert Subscriber Data, inquire about associated record between first session and second session according to wherein Session Id or IMSI, definite first conversation request Update Location that is associated with second session, thus the corresponding first conversation request response message Update Location sent.The user adheres to successfully at MME.

Present embodiment six, the HSS side, related by first conversation request message and second conversation request message of sending are carried out, follow-up incidence relation according to record is confirmed the incidence relation between the session; The MME side, determine incidence relation between the session by the IMSI in the conversation request message, what realization underlying protocol Diameter can't realize carries out association to a plurality of conversation messages of application layer, thereby makes MME and the order of HSS correct execution, completes successfully user's adhering in network.

The embodiment of the invention seven, as shown in Figure 8, to realize that by Diameter the attaching process of user in MME is example between MME and the HSS, the conversation procedure between MME and the HSS comprises:

Step S801: the current MME that adheres to of user sends the first conversation request Update Location, and the session identification parameter in its underlying protocol extends this as session 1 (Session 1);

Step S802:HSS receives Update Location request message, after other of being correlated with handled, send the second conversation request message Insert Subscriber Data to MME, the session identification parameter in its underlying protocol extends this as session 2 (Session 2);

The first conversation request message Update Location that step S803:HSS will receive carries out related with the second conversation request message Insert Subscriber Data that sends and writes down incidence relation, the session identification parameter S ession Id of the Diameter layer of the first conversation request message Update Location and the session identification parameter S ession Id among the second conversation request message Insert Subscriber Data can be carried out associated record in the present embodiment, also can carry out associated record to two message according to the IMSI of the user in two conversation request message, in other embodiments of the invention, incidence relation between the first conversation request message Update Location and the second conversation request message Insert Subscriber Data also can be recorded in other cellular logic entity, and HSS only need inquire about and determine that its incidence relation gets final product.

After step S804:MME receives the second conversation request message Insert Subscriber Data, determine that according to the title of second conversation request message described second conversation request message is the conversation request message in the user position update process, and determine the first conversation request message Update Location that described second conversation request message is associated, and send the second conversation request response message InsertSubscriber Data Ack to HSS according to the IMSI that wherein carries; Identical with embodiment six, MME need send HSS in the position updating process when changing about the conversation request message of user data and user contracting data, the conversation request message about user data that HSS sends is distinguished, could determine the incidence relation of second session and first session, and HSS renames to the conversation request message that MME sends when in the present embodiment seven user contracting data being changed, with its called after Update Subscriber Data, making MME can distinguish described conversation request according to the title of conversation message is to take place in the user position update process, thereby carries out corresponding related definite;

After step S805:HSS receives the second conversation request response message Insert Subscriber Data, inquire about associated record between first session and second session according to wherein Session Id or IMSI, determine the first conversation request Update Location that second session is associated, thereby send the corresponding first conversation request response message Update Location; The user adheres to successfully at MME;

Step S806: user contracting data changes, and HSS sends the 3rd conversation request message UpdateSubscriber Data, and the session identification parameter in its underlying protocol extends this as session 3 (Session 3);

Step S807:MME receives the 3rd conversation request message Update Subscriber Data, independent user Data Update request when confirming as user contracting data and change according to message name, upgrade operation according to the user contracting data that wherein carries, send the 3rd conversation request response message UpdateSubscriber Data Ack to HSS.

The invention process profit seven, the HSS side, by carrying out related with second conversation request message of sending first conversation request message and writing down incidence relation, follow-up according to the incidence relation between the incidence relation affirmation session of record; The MME side, by renaming independent user Data Update request message, make it distinguish over insertion user data requests in the position updating process, make MME get final product differentiating sessions according to the message name of session, and the incidence relation between the affirmation session, association is carried out in a plurality of sessions to application layer that realization underlying protocol Diameter can't realize, thereby makes MME and the order of HSS correct execution, completes successfully user's adhering in network.

The embodiment of the invention eight, to realize that by Diameter the attaching process of user in MME is example between MME and the HSS, as shown in Figure 9, the conversation procedure between MME and the HSS comprises:

Step S901: the current MME that adheres to of user sends the first conversation request Update Location, and the session identification parameter in its underlying protocol extends this as session 1 (Session 1);

Step S902:HSS receives Update Location request message, after other of being correlated with handled, send the second conversation request message Insert Subscriber Data to MME, session identification parameter in its underlying protocol extends this as session 2 (Session 2), and carry the action type parameter, this action type parameter value Insert, indicating this second conversation request is insertion user data requests in the user position update process;

The first conversation request message Update Location that step S903:HSS will receive carries out related with the second conversation request message Insert Subscriber Data that sends and writes down incidence relation, the session identification parameter S ession Id of the Diameter layer of the first conversation request message Update Location and the session identification parameter S ession Id among the second conversation request message Insert Subscriber Data can be carried out associated record in the present embodiment, also can carry out associated record to two message according to the IMSI of the user in two conversation request message, in other embodiments of the invention, incidence relation between the first conversation request message Update Location and the second conversation request message Insert Subscriber Data also can be recorded in other cellular logic entity, and HSS only need inquire about and determine that its incidence relation gets final product.

After step S904:MME receives the second conversation request message Insert Subscriber Data, determine that according to the action type parameter of wherein carrying described second conversation request message is the conversation request message in the position updating process, and determine the first conversation request message Update Location that described second conversation request message is associated, and send the second conversation request response message InsertSubscriber Data Ack to HSS according to the IMSI that wherein carries; Identical with embodiment six, seven, MME need send HSS in the position updating process when changing about the conversation request message of user data and user contracting data, the conversation request message about user data that HSS sends is distinguished, could determine the incidence relation of second session and first session, and in the present embodiment eight by carrying the action type parameter, making MME can distinguish described conversation request according to the action type parameter is to take place in the user position update process, thereby carries out corresponding related definite;

After step S905:HSS receives the second conversation request response message Insert Subscriber Data, inquire about associated record between first session and second session according to wherein Session Id or IMSI, determine the first conversation request Update Location that second session is associated, thereby send the corresponding first conversation request response message Update Location; The user adheres to successfully at MME;

Step S906: user contracting data changes, HSS sends the 3rd conversation request message UpdateSubscriber Data, session identification parameter in its underlying protocol extends this as session 3 (Session 3), carry the action type parameter simultaneously, this action type parameter value Update, indicating the 3rd conversation request is the conversation request of user contracting data when changing;

Step S907:MME receives the 3rd conversation request message Update Subscriber Data, independent user Data Update request when confirming as user contracting data and change according to the action type parameter of wherein carrying, upgrade operation according to the user contracting data that wherein carries, send the 3rd conversation request response message Update Subscriber Data Ack to HSS.

The embodiment of the invention eight, in the HSS side, still by carrying out related with second conversation request message of sending first conversation request message as the method among the embodiment five, six and writing down incidence relation, follow-up according to the incidence relation between the incidence relation affirmation session of record; The MME side, then according to the action type of carrying in the conversation request message of receiving with the insertion user data requests in the position updating process and independently the updating user data request message make a distinction, make MME get final product differentiating sessions according to the action type parameter, and the incidence relation between the affirmation session, and realize finally that underlying protocol Diameter can't realize a plurality of conversation messages of application layer are carried out association, thereby make MME and the order of HSS correct execution, complete successfully user's adhering in network.

The embodiment of the invention nine, its realization flow as shown in figure 10, conversation procedure comprises:

Step S1001: first functional entity sends the first conversation request message Req1, and the session identification parameter in the underlying protocol of described Req1 message extends this as session 1 (Session 1);

Step S1002: after second functional entity is received the first conversation request message Req1, send pseudo-response message Pseudo-Rsp1 to this first conversation request to first functional entity, the session identification parameter of protocol layer is filled out and is Session1;

Step S1003: second functional entity sends the second conversation request message Req2 to first functional entity, the session identification parameter of protocol layer is still filled out and is Session1, because second functional entity sends pseudo-response message to first conversation request to first functional entity among the step S1002, session identification parameter S ession 1 discharges at the Diameter layer, therefore second functional entity can be initiated new application request to first functional entity, and its session identification parameter extends this as Session 1;

Step S1004: after first functional entity receives that the session identification parameter of protocol layer is the second conversation request message Req2 of Session 1, judge according to described session identification parameter that it is related with Req1, after then handling accordingly, send response message Rsp2 to the second conversation request message Req2 to first functional entity, the session identification parameter of protocol layer is filled out and is Session 1;

Step S1005: after second functional entity is received response message Rsp2 to the second conversation request message Req2, send the 3rd conversation request message to first functional entity, this message is pseudo-request message Pseudo-Req3, the session identification parameter of protocol layer is also filled out and is that Session 1, this Pseudo-Req3 conversation request message promptly are the real application layer response messages to the Req1 among the step S1001;

Step S1006: after first functional entity is received the 3rd conversation request message Pseudo-Req3, send this request responding message Pseudo-Rsp3 to second functional entity, the session identification parameter of protocol layer is filled out and is Session 1.Whole application layer conversation is finished dealing with.

The embodiment of the invention nine, by fabricate response message (pseudo-response message Pseudo-Rsp1) in underlying protocol to the application layer request message, and the response message that application layer is the original request message (pseudo-request message Pseudo-Req3) that is mapped to protocol layer satisfies the requirement of Diameter, simultaneously in the new conversation request of initiating and session response message, carry the session identification parameter identical with the session identification parameter value of first conversation request, realize the association of a plurality of conversation messages, thereby required function is finished in the correct execution order.

The embodiment of the invention ten, still to realize that by Diameter the attaching process of user in MME is example between MME and the HSS, as shown in figure 11, the conversation procedure between MME and the HSS comprises:

Step S1101:MME sends the first conversation request message Update Location, and the session identification parameter in the underlying protocol is filled out and is Session 1;

After step S1102:HSS receives the first conversation request message Update Location, after other of being correlated with handled, send pseudo-response message Pseudo-Update LocationRsp to this first conversation request to MME, the session identification parameter of protocol layer is filled out and is Session 1;

Step S1103:HSS sends the second conversation request message Insert Subscriber Data to MME, and the session identification parameter of protocol layer is filled out and is Session 1;

After step S1104:MME receives that the session identification parameter of protocol layer is the second conversation request message Insert Subscriber Data of Session 1, it is related to judge its first conversation request message UpdateLocation that sends with self, after handling accordingly, send the second conversation request response message InsertSubscriber Data Ack to HSS, the session identification parameter of protocol layer is filled out and is Session 1;

After step S1105:HSS receives the second conversation request response message Insert Subscriber Data Ack, judge that Insert Subscriber Data Ack is associated with Update Location, send the 3rd conversation request message to MME, this conversation request message is pseudo-request message Pseudo-Update Location Ack, and the session identification parameter of protocol layer is filled out and is Session 1; This conversation request message promptly is the real application layer response message to the first conversation request message Update Location among the step S1101;

After step S1106:MME receives the 3rd conversation request message Pseudo-Update Location Ack, send the Rsp to this request responding message Pseudo-Update Location Ack to HSS, the session identification parameter of protocol layer is filled out and is Session 1.The user adheres to successfully at MME.

The embodiment of the invention ten, by fabricate response message (Pseudo-Update Location Rsp) in underlying protocol to the application layer request message, and the response message that application layer is the original request message (Pseudo-Update Location Ack) that is mapped to protocol layer satisfies the requirement of Diameter, simultaneously in the new conversation request of initiating and session response message, carry the session identification parameter identical with the session identification parameter value of first conversation request, realize the association of a plurality of conversation messages, thereby realize realizing the attaching process of user in MME by Diameter between MME and the HSS.

The embodiment of the invention 11, for realize with EPS network and EPS evolution before packet switching PS network (Packet Switched) carry out intercommunication, HLR in the PS network before MME in the EPS network and the EPS evolution, SGSN (Serving GPRS Supporting Node in the PS network before the EPS evolution, service universal grouping wireless business supporting node) with the EPS network in HSS, need carry out intermediate conveyor by the Signaling System Number 7 net.Because in the EPS network, the Diameter that adopts between MME and the HSS, and in the PS network before the EPS evolution, what HLR and SGSN adopted is MAP, therefore, introduced IWF (Interworking Function, network interworking) function between two networks, this IWF function mainly realizes the protocol conversion between Diameter and the MAP.

As shown in figure 12, IWF is between SGSN/IWF1 and HSS, the Diameter that adopts between IWF and the HSS, adopt MAP between IWF and the SGSN/IWF1, many in conversation procedure of MAP support to using the interacting message execution, IWF need carry out interrelated and message conversion to Diameter message and the MAP message received from two ends, and present embodiment comprises:

Step S1201:SGSN/IWF1 sends Update Location message based on MAP to IWF, and carrying the MAP dialog information is ID1;

After step S1202:IWF will become Update Location request message based on Diameter based on the Update Location message maps of MAP, to send to HSS based on the Update Location request message of Diameter, in the message except carrying relevant user information, carry application layer conversation relevant parameter Dialog-Id simultaneously, its value for generate in this locality by IWF or by alternate manner obtain can unique identification and the Dialog1 of a session carrying out of HSS, also directly value is dialogue identifier ID1 in the MAP message;

Step S1203:HSS receives Update Location request message, after other of line correlation of going forward side by side handled, send Insert Subscriber Data request message to IWF, carry parameter Dialog-Id simultaneously, its value be made as with Update Location request message in identical Dialog1;

After step S1204:IWF receives that from HSS carrying Dialog-Id is made as the Insert SubscriberData request message of Dialog1, judging it is that the UpdateLocation of Dialog1 is related with the Dialog-Id that sends to HSS before, be that the MAP message Update Location of ID1 also is related simultaneously with the MAP dialogue identifier of receiving from SGSN/IWF1, IWF will be somebody's turn to do Insert Subscriber Data based on Diameter and be mapped to Insert Subscriber Data based on MAP, and its MAP dialogue identifier is made as ID1, just with step S1201 in the Update Location message relating received in a MAP dialogue, send to SGSN/IWF1;

Step S1205:SGSN/IWF1 returns MAP response message Insert Subscriber Data Ack to IWF, and the MAP dialogue identifier is ID1;

Step S1206:IWF receives that the MAP dialogue identifier is the response message Insert Subscriber DataAck of ID1, sends Insert Subscriber Data Ack response message to HSS, carries parameter Dialog-Id simultaneously, and its value is made as Dialog1;

After step S1207:HSS receives that carrying Dialog-Id is made as the Insert Subscriber DataAck response message of Dialog1, return to IWF and to carry the Update Location Ack response message that Dialog-Id is Dialog1;

After step S1208:IWF receives that from HSS carrying Dialog-Id is made as the Update LocationAck response message of Dialog1, judging it is that the UpdateLocation of Dialog1 is related with the Dialog-Id that issues HSS before, be that the MAP message Update Location of ID1 is related just with the MAP dialogue identifier of receiving from SGSN/IWF1, IWF will be somebody's turn to do Update Location Ack response message based on Diameter and be mapped to Update Location Ack based on MAP, and its MAP dialogue identifier is made as ID1, just with the first step in the Update Location message relating received in a MAP dialogue, send to SGSN/IWF1.

The embodiment of the invention 11 is applied to the session interaction between IWF and the HSS, can realize IWF correctly with Diameter application message and MAP application message mutual mapping with related, finish the attaching process of EPS user in SGSN or MME.

The embodiment of the invention 12, as Figure 13, MME carries out PS territory intercommunication before interacting message is finished EPS network and evolution by IWF and HLR, realizes that the user among the HLR in the PS territory before the evolution is attached in the EPS network, comprising:

Step S1301:MME sends the Update Location request message based on Diameter, and the session identification parameter of protocol layer is filled out and is Session 1;

Step S1302:IWF will receive that Update Location request message is mapped to the Update Location message based on MAP, create a new MAP dialogue, and dialogue identifier is ID1, sends to HLR;

Step S1303:HLR sends Insert Subscriber Data request message to IWF, and the MAP dialogue identifier is that ID1 and the Update Location message received send in a dialogue;

Step S1304:IWF receives the Insert Subscriber Data message that the MAP dialogue identifier is ID1, judge that the Update Location message that itself and MME in the first step send is related, send Insert Subscriber Data message to MME, the session identification parameter of protocol layer is filled out and is Session 2, and carry the action type parameter, value is Insert, and indicating this message is insertion user data operation in the position updating process;

Step S1305:IWF carries out Insert Subscriber Data message and Update Location message by Session 1 and Session 2 related, and described association is similar with embodiment six, seven, eight, does not repeat them here;

After step S1306:MME receives Insert Subscriber Data message, determine that according to action type parameter wherein this message is the conversation request that takes place in the position updating process, and determine the Update Location message that it is associated according to the IMSI that wherein carries, return Insert Subscriber Data Ack response message to IWF, the session identification parameter of protocol layer is filled out and is Session 2;

Step S1307:IWF will be mapped to MAP message Insert Subscriber Data Ack from the Insert Subscriber Data Ack response message that MME receives and send to HLR, and the MAP dialogue identifier is ID1;

Step S1308:HLR returns Update Location Ack message to IWF, and the MAP dialogue identifier is ID1;

Step S1309:IWF is according to the incidence relation to Diameter session identification Session 1, Session 2, MAP dialogue identifier ID1, to be mapped to Diameter message Update Location Ack from the Update Location Ack that HLR receives, send to MME, session identification is Session 1, and is the same with the session identification of UpdateLocation in the first step;

Step S1310:HLR initiates independently Insert Subscriber Data, and the MAP dialogue identifier is ID2;

Step S1311:IWF will be mapped to Diameter message Insert Subscriber Data from the Insert Subscriber Data that HLR receives and send to MME, the session identification parameter of protocol layer is filled out and is Session 3, and to carry action type Update indication be independently to insert the user data operation.

After step S1312:MME handles the independently Insert Subscriber Data request message of receiving, reply response message Insert Subscriber Data Ack and give IWF, the session identification parameter of protocol layer is filled out and is Session 3;

Step S1313:IWF will be mapped to MAP message Insert Subscriber Data Ack from the Insert Subscriber Data Ack that MME receives, the MAP dialogue identifier is ID2, sends to HLR.

The embodiment of the invention 12 is applied to the session interaction between IWF and the MME, can realize IWF correctly with Diameter application message and MAP application message mutual mapping with related, the user among the HLR in the PS territory before the evolution is attached to the EPS network.

Need to prove that the embodiment of the invention one to embodiment ten described method can apply to perhaps apply to the session interaction between IWF and the MME between IWF and the HSS equally, embodiment it will be apparent to those skilled in the art, does not repeat them here.

One of ordinary skill in the art will appreciate that all or part of step that realizes in the foregoing description method is to instruct relevant hardware to finish by program, described program can be stored in a kind of computer-readable recording medium, read-only memory for example, disk or CD etc.

The embodiment of the invention also provides a kind of conversational system, and as shown in figure 14, this system comprises: first functional entity, 41, the second functional entitys 42;

First functional entity 41, be used for sending first conversation request message to second functional entity 42, and after receiving second conversation request message of described second functional entity 42 transmissions, determine that described second conversation request message is associated with first conversation request message that self sends, send the second conversation request response message to described second functional entity 42;

Described second functional entity 42, be used for after first conversation request message that receives 41 transmissions of described first functional entity, send second conversation request message to described first functional entity 41, and behind the second conversation request response message that receives 41 transmissions of described first functional entity, determine that the described second conversation request response message is associated with described first conversation request message that receives, send the first conversation request response message to described first functional entity 41.

In the specific embodiments of the invention, described first functional entity can be Mobility Management Entity MME, and described second functional entity can be home network server HSS; Perhaps, described first functional entity can be for being arranged at the network interworking function IWF between the PS network and EPS network before the EPS evolution, and described second functional entity can be home network server HSS; Perhaps described first functional entity can be Mobility Management Entity MME, and described second functional entity can be for being arranged at the network interworking function IWF between the PS network and EPS network before the EPS evolution.

When described first functional entity is Mobility Management Entity MME, described second functional entity is home network server HSS, and described MME is during for the current MME that adheres to of user, and described system further comprises the MME that adheres to before the user;

After the location update request message that receives the current MME transmission of adhering to of described user, before the current MME that adheres to of described user sent insertion user data requests message, the MME that described HSS is further used for adhering to before described user sent the canceling position request message;

The MME that adheres to before the described user is used for sending the canceling position request response to described HSS.

Described first functional entity 41 comprises:

The first session processing unit 1411 is used for sending first conversation request message and receiving the first conversation request response message to described second functional entity 42;

The second session processing unit 1412, be used for receiving second conversation request message that described second functional entity 42 sends, after determining described second conversation request message and first conversation request message that self sends being associated, send the second conversation request response message to described second functional entity 42.

Described second functional entity 42 comprises:

First conversation element 1421 is used to receive first conversation request message that described first functional entity 41 sends, and sends the first conversation request response message to described first functional entity 41;

Second conversation element 1422, be used for after first conversation element 1421 receives first conversation request message of described first functional entity 41 transmissions, send second conversation request message to described first functional entity 41, and the second conversation request response message that receives 41 transmissions of described first functional entity, after determining the described second conversation request response message and described first conversation request message that receives being associated, notify described first conversation element 1421 to send the first conversation request response message to described first functional entity 41;

Described second functional entity 42 further comprises:

Session association unit 1423 is used for carrying out related with described first conversation request message described second conversation request message;

Then described second conversation element 1422 after receiving the second conversation request response message, determines that according to the incidence relation that described session association unit 1423 is provided with the described second conversation request response message is associated with described first conversation request message that receives.

Described second functional entity 42 further comprises:

Pseudo-request-response unit 1424, be used for after the described second session transmitting element receives described first conversation request message, and send before second conversation request message, to the pseudo-response message of described first functional entity 41 transmissions to described first conversation request message;

Then described first conversation element 1421 also is used for after described second conversation element 1422 is determined the described second conversation request response message and described first conversation request message that receives is associated, to the pseudo-request message of described first functional entity 41 transmissions about first session, wherein, described pseudo-request message about first session is the response message to described first conversation request message.The embodiments of the invention terminal is expanded by the application level function to the functional entity that carries out session, make the functional entity carry out session can realize that the irrealizable session to a plurality of mutual execution of underlying protocol carries out the related function of confirming, and the final functional entity correct execution session command of carrying out session that makes, finish required function.

The embodiment of the invention is applied to the session between the MME and HSS in the EPS network, can realize that MME and HSS realize the attaching process of user in MME by Diameter.Concrete, the embodiment of the invention is by increasing the application layer conversation relevant parameter in the message that needs to carry out related a plurality of sessions between MME and HSS; Perhaps by carrying AVPAcct-Multi-Session-Id in the message that between MME and HSS, needs to carry out related a plurality of sessions, and it is referred to be made as session identification parameter in first conversation request message; Perhaps related by first conversation request message and second conversation request message of sending are carried out in the HSS side, in the MME side by the IMSI in the conversation request message; Perhaps virtual session request message, the modes such as session identification parameter that the session identification parameter of the new conversation message of initiating still are made as initial associated session have realized the affirmation of functional entity to incidence relation between session, thus the correct execution function is finished session.In like manner, the embodiment of the invention can also be applied in the EPS network between the IWF and HSS, session interaction between IWF and the MME, can realize IWF correctly with Diameter application message and MAP application message mutual mapping with related, finish the attaching process of user in MME or SGSN.

The embodiment of the invention needing between two entities not only can be used for a plurality of conversation messages are carried out related scene, need carry out the scene of session association when can be used for the interacting message of a plurality of inter-entity simultaneously.

The above is the preferred embodiments of the present invention only, is not limited to the present invention, and for a person skilled in the art, the present invention can have various changes and variation.Within the spirit and principles in the present invention all, any modification of being done, be equal to replacement, improvement etc., all should be included within the claim scope of the present invention.

Claims

1, a kind of session method is characterized in that, the underlying protocol that described session is adopted is a Diameter, comprising:

2, session method as claimed in claim 1 is characterized in that, described first functional entity and described second functional entity carry the application layer relevant parameter in each message of described first session and second session; Wherein, the value of the application layer relevant parameter that carries in each message of described first session and second session is identical.

3, session method as claimed in claim 2, it is characterized in that, described first functional entity determines that according to the value of described application layer relevant parameter described second conversation request message is associated with first conversation request message, and described second functional entity is according to determining that according to the value of described application layer relevant parameter the described second conversation request response message is associated with first conversation request message.

4, session method as claimed in claim 1, it is characterized in that, described first functional entity and described second functional entity carry property value to Acct-Multi-Session-Id in each message of described first session and second session, wherein, the property value that carries in each message of described first session and second session is identical to the value of Acct-Multi-Session-Id.

5, session method as claimed in claim 4, it is characterized in that, described first functional entity determines that to the value of Acct-Multi-Session-Id described second conversation request message is associated with first conversation request message according to described property value, and described second functional entity is according to according to described property value the value of Acct-Multi-Session-Id being determined that the described second conversation request response message is associated with first conversation request message.

6, session method as claimed in claim 1 is characterized in that, described second functional entity further comprised before described first functional entity sends second conversation request message:

Send the 3rd conversation request message to the 3rd functional entity, receive the 3rd conversation request response message that described the 3rd functional entity sends after, determine that described the 3rd conversation request response message is associated with described first conversation request message.

7, session method as claimed in claim 1 is characterized in that, further comprises after described second functional entity sends second conversation request message: described second functional entity carries out related with first session that receives second session that self sends.

8, session method as claimed in claim 7 is characterized in that, described second functional entity determines that with the incidence relation of second session second conversation request response message is associated with first conversation request message according to first session that self is provided with.

9, as claim 1 or 7 described session methods, it is characterized in that described first functional entity determines that according to the International Mobile Subscriber Identity that carries in described second conversation request message described second conversation request message is associated with first conversation request message that self sends.

10, session method as claimed in claim 1 is characterized in that, described second functional entity receives after first conversation request message of first functional entity transmission, further comprises before described first functional entity sends second conversation request message:

Described second functional entity is to the pseudo-response message of described first functional entity transmission to described first conversation request.

11, session method as claimed in claim 10, it is characterized in that the session identification parameter of underlying protocol is identical with the session identification parameter of underlying protocol in described first conversation request message in described second conversation request message that described second functional entity sends.

12, session method as claimed in claim 11, it is characterized in that, described first functional entity determines that according to the value of described session identification parameter described second conversation request message is associated with first conversation request message, and described second functional entity is according to determining that according to the value of described session identification parameter the described second conversation request response message is associated with first conversation request message.

13, session method as claimed in claim 12 is characterized in that, described second functional entity sends the first conversation request response message to described first functional entity and specifically comprises:

Described second functional entity is by initiating that to described first functional entity pseudo-request message of first session is sent to described first functional entity with the described first conversation request response message.

14, session method as claimed in claim 1 is characterized in that, described first functional entity is Mobility Management Entity MME, and described second functional entity is home network server HSS, and described method is specially:

After described HSS receives the location update request message of described MME transmission, send insertion user data requests message to described MME;

Described HSS receives the insertion user data requests response message that described MME sends, wherein, described insertion user data requests response message is to send after described MME determines described insertion user data requests message and the location update request message that self sends is associated;

Described HSS determines that described insertion user data requests response message is associated with the described location update request message that receives, and sends the position updating request response message to described MME.

15, session method as claimed in claim 14 is characterized in that, described MME determines that location update request message that described insertion user data requests message and self send is associated and specifically comprises:

Described MME determines that according to the International Mobile Subscriber Identity in the described insertion user data requests message described insertion user data requests message is associated with described location update message.

16, session method as claimed in claim 15, it is characterized in that, described MME determines that according to the International Mobile Subscriber Identity in the described insertion user data requests message described insertion user data requests message further comprises before being associated with described location update message:

Described MME judges whether described insertion user data requests message is the conversation request that takes place in the user position update process, if determine that according to described International Mobile Subscriber Identity described insertion user data requests message is associated with described location update message.

17, session method as claimed in claim 16 is characterized in that, described MME judges whether described insertion user data requests message is that the conversation request that takes place in the user position update process specifically comprises:

Described MME judges whether self initiated location update operations to the pairing user of International Mobile Subscriber Identity in the described insertion user data requests message, if determine that described insertion user data requests message is the conversation request that takes place in the user position update process.

18, session method as claimed in claim 16, it is characterized in that, the message name of the conversation request that takes place in the new message name of conversation request message definition that takes place when changing for user contracting data, described new message name and user position update process is different;

Then described MME judges whether described insertion user data requests message is that the conversation request that takes place in the user position update process specifically comprises:

Described MME receives described insertion user data requests message, judges that according to message name described insertion user data requests message is the conversation request that takes place in the user position update process.

19, session method as claimed in claim 16 is characterized in that, described HSS sends insertion user data requests message to described MME and specifically comprises:

Described HSS sends the insertion user data requests message of carrying the action type parameter to described MME, and wherein, it is the conversation request that takes place in the user position update process that the value of described action type parameter is indicated described insertion user data requests message;

Described MME receives the described insertion user data requests message of carrying the action type parameter, judges that according to described action type parameter described insertion user data requests message is the conversation request that takes place in the user position update process.

20, session method as claimed in claim 1, it is characterized in that, described first functional entity is the network interworking function IWF that is arranged between preceding PS network of EPS evolution and the EPS network, and described second functional entity is home network server HSS, and described method is specially:

Described IWF receives after the location update request message based on MAP of service universal grouping wireless business supporting node SGSN transmission, and the message that described location request message is converted to based on Diameter sends to described HSS;

After described HSS receives the location update request message of described IWF transmission, send insertion user data requests message to described IWF;

After described IWF receives described insertion user data requests message, determine that described insertion user data requests message is associated from the location update request message that described SGSN receives with self, described insertion user data requests message conversion is sent to described SGSN for the message based on MAP, behind the insertion user data requests response message that receives described SGSN transmission, the message that the insertion user data requests response message that described SGSN is sent is converted to based on Diameter sends to described HSS;

Described HSS receives described insertion user data requests response message, determines that described insertion user data requests response message is associated with the described location update request message that receives, and sends the position updating request response message to described IWF;

The message that the position updating request response message based on Diameter that described IWF will receive is converted to based on MAP sends to described SGSN.

21, session method as claimed in claim 20, it is characterized in that, described IWF carries the application layer relevant parameter in the described location update request message of its transmission with inserting in the user data requests response message, described HSS carries the application layer relevant parameter in the insertion user data requests message of its transmission and position updating request response message, wherein, the value of the application layer relevant parameter that carries in described each message is identical.

22, session method as claimed in claim 21 is characterized in that, described IWF determines that according to the value of described application layer relevant parameter described insertion user data requests message is associated with the location update request message that self sends; Described HSS determines that according to the value of described application layer relevant parameter described insertion user data requests response message is associated with the location update request message that receives.

23, session method as claimed in claim 1, it is characterized in that, described first functional entity is Mobility Management Entity MME, and described second functional entity is the network interworking function IWF that is arranged between preceding PS network of EPS evolution and the EPS network, and described method is specially:

Described IWF receives after the location update request message based on Diameter of described MME transmission, and the message that described location request message is converted to based on MAP sends to attaching position register HLR;

After described IWF receives the insertion user data requests message based on MAP of described HLR transmission, described insertion user data requests message conversion based on MAP is sent to described MME for the message based on Diameter;

After described MME receives described insertion user data requests message, determine that described insertion user data requests message is associated with the location update request message that self sends, to the insertion user data requests response message of described IWF transmission based on Diameter;

After described IWF receives described insertion user data requests response message based on Diameter, determine that described insertion user data requests response message is associated with the described location update request message that receives, described insertion user data requests message conversion based on Diameter is sent to described HLR for the message based on MAP;

Described IWF receives the position updating request response message based on MAP that described HLR sends, and the message that described position updating request response message based on MAP is converted to based on Diameter sends to described MME.

24, session method as claimed in claim 23, it is characterized in that, described IWF specifically comprises described insertion user data requests message conversion based on MAP for the message based on Diameter is sent to described MME: described IWF is the message based on Diameter with described insertion user data requests message conversion based on MAP, and in described message, carry the action type parameter, described message is sent to described MME, wherein, to indicate described insertion user data requests message be the conversation request that takes place in the user position update process to the value of described action type parameter.

25, session method as claimed in claim 24 is characterized in that, described MME determines that location update request message that described insertion user data requests message and self send is associated and specifically comprises:

Described MME receives the described insertion user data requests message of carrying the action type parameter, judge that according to described action type parameter described insertion user data requests message is the conversation request that takes place in the user position update process, determine that according to the International Mobile Subscriber Identity in the described insertion user data requests message described insertion user data requests message is associated with described location update message again.

As claim 23 or 24 described session methods, it is characterized in that 26, described IWF further comprises described insertion user data requests message conversion based on MAP for the message based on Diameter is sent to described MME afterwards:

Described IWF carries out related with described location update request message described insertion user data requests message.

27, session method as claimed in claim 26 is characterized in that, described IWF determines that described insertion user data requests response message is associated with the described location update request message that receives and specifically comprises:

After described IWF receives described insertion user data requests response message, according to session identification parameter or the International Mobile Subscriber Identity in the described insertion user data requests response message, determine that described insertion user data requests message is associated with described location update request message.

28, a kind of conversational system is characterized in that, the underlying protocol that described session is adopted is a Diameter, and described system comprises:

29, system as claimed in claim 28 is characterized in that, described first functional entity is Mobility Management Entity MME, and described second functional entity is home network server HSS; Perhaps, described first functional entity is the network interworking function IWF that is arranged between preceding PS network of EPS evolution and the EPS network, and described second functional entity is home network server HSS; Perhaps described first functional entity is Mobility Management Entity MME, and described second functional entity is the network interworking function IWF that is arranged between preceding PS network of EPS evolution and the EPS network.

30, system as claimed in claim 28 is characterized in that, described system further comprises the 3rd functional entity;

After first conversation request message that receives described first functional entity transmission, before described first functional entity sends second conversation request message, described second functional entity is further used for sending the 3rd conversation request message to described the 3rd functional entity, and determines that the 3rd conversation request response message that described the 3rd functional entity sends is associated with first conversation request message;

Described the 3rd functional entity is used for sending the 3rd conversation request response message to described second functional entity.

31, a kind of conversational device is characterized in that, it is Diameter that described conversational device is carried out the underlying protocol that session adopts, and described device comprises:

32, device as claimed in claim 31 is characterized in that, described device comprises: Mobility Management Entity MME perhaps is arranged at the network interworking function IWF between preceding PS network of EPS evolution and the EPS network.

33, a kind of conversational device is characterized in that, it is Diameter that described conversational device is carried out the underlying protocol that session adopts, and described device comprises:

Second conversation element, be used for after described first conversation element receives first conversation request message, send second conversation request message, and receive the second conversation request response message, after determining the described second conversation request response message and described first conversation request message that receives being associated, notify described first conversation element to send the first conversation request response message.

34, device as claimed in claim 33 is characterized in that, described device further comprises:

The session association unit is used for after described second conversation element sends second conversation request message, carries out related with described first conversation request message described second conversation request message;

Then described second conversation element after receiving the second conversation request response message, determines that according to the incidence relation of described session association unit setting the described second conversation request response message is associated with described first conversation request message that receives.

35, device as claimed in claim 33 is characterized in that, described device further comprises:

Pseudo-request-response unit is used for after described first conversation element receives described first conversation request message, and second conversation element sends before second conversation request message, sends the pseudo-response message to described first conversation request message;

Then described first conversation element also is used for after described second conversation element is determined the described second conversation request response message and described first conversation request message that receives is associated, transmission is about the pseudo-request message of first session, wherein, described pseudo-request message about first session is the response message to described first conversation request message.

As the described device of claim 33 to 35, it is characterized in that 36, described device comprises: home network server HSS perhaps is arranged at the network interworking function IWF between preceding PS network of EPS evolution and the EPS network.