CN106851763B

CN106851763B - Message routing method, system and gateway in LTE network

Info

Publication number: CN106851763B
Application number: CN201510891363.3A
Authority: CN
Inventors: 仝黎
Original assignee: ZTE Corp
Current assignee: ZTE Corp
Priority date: 2015-12-07
Filing date: 2015-12-07
Publication date: 2020-09-29
Anticipated expiration: 2035-12-07
Also published as: WO2017097060A1; CN106851763A

Abstract

The invention relates to a message routing method in an LTE network, which comprises the following steps: the MME of the LTE network at the roaming place sends an access request to a routing agent node DRA, and the node carries a source user identifier as the request; the routing agent node DRA locates a first HSS according to the source user identifier and sends a request message to the first HSS, wherein the request message carries the source user identifier, whether a request retry identifier is supported and whether a route optimization identifier is supported; when the first HSS finds that the user does not exist after querying a database according to the source user identifier, if the request retry support identifier is request retry support and the route optimization support identifier is route optimization support, the first HSS returns an error code to a routing agent node DRA and carries a request retry support mark and a route optimization support mark; and the routing agent node DRA analyzes the error code, initiates a query request to EMNP, queries a corresponding target user identifier and a target routing address according to the source user identifier, and re-initiates an access request to a second HSS by using the target user identifier and the target routing address. The method can realize flexible routing conversion and automatic number switching. In addition, a message routing system in the LTE network, a message routing method in another LTE network and a gateway for realizing message routing in the LTE network are also provided.

Description

Message routing method, system and gateway in LTE network

Technical Field

The present invention relates to the field of mobile communications, and in particular, to a message routing method, system, and gateway in an LTE network.

Background

LTE (Long Term Evolution) is a Long Term Evolution of The UMTS (Universal mobile telecommunications System) technology standard specified by The 3GPP (The 3rd generation partnership Project) organization. An S6a interface between an MME (Mobility Management Entity, which is a key control node in 3GPP protocol LTE) and an HSS (home subscriber Server) in an LTE core network is based on a Diameter base protocol. The Diameter base protocol provides a secure, reliable, and easily extensible framework for various authentication, authorization, and charging services, and mainly relates to aspects such as capability negotiation, how messages are sent, how peer-to-peer parties finally end communication, and the like. The RFC3588Diameter protocol specifies that Diameter message routing employs a domain-based routing table approach, and all domain-based routing lookups are performed by means of the routing table.

The 3GPP29.272 protocol specifies the way in which the S6a interface locates the HSS. The MME or DRA (routing agent) needs to locate the HSS according to the User-Name AVP (i.e. the IMSI number of the User) in the S6a interface message. However, in current mobile communication networks, there is a common situation where one user uses multiple USIM cards simultaneously. For example, for CDMA operators such as chinese telecommunications, the Sponsor IMSI provided by the roaming operator is commonly used when the original 3G subscriber roams internationally, and the IMSI number owned by chinese telecommunications is used when the 4G service is developed domestically. However, if the user needs to use the 4G service during international roaming, the Sponsor IMSI is still required to access the LTE network during international roaming of the user for a long time due to the negotiation of a roaming agreement involving a new number.

Disclosure of Invention

Based on this, it is necessary to provide a message routing method, system and gateway in an LTE network, which can implement flexible transformation of routing and automatic number switching.

A method of message routing in an LTE network, the method comprising:

an MME of a roaming area LTE network sends an access request to a routing agent node DRA, wherein the access request carries a source user identifier;

the routing agent node DRA locates a first HSS according to the source user identifier and sends a request message to the first HSS, wherein the request message carries the source user identifier, whether a request retry identifier is supported and whether a route optimization identifier is supported;

when the first HSS finds that the user does not exist after querying a database according to the source user identifier, if the request retry support identifier is request retry support and the route optimization support identifier is route optimization support, the first HSS returns an error code to a routing agent node DRA and carries a request retry support mark and a route optimization support mark;

and the routing agent node DRA analyzes the error code, initiates a query request to EMNP, queries a corresponding target user identifier and a target routing address according to the source user identifier, and re-initiates an access request to a second HSS by using the target user identifier and the target routing address.

In one embodiment, if the identifier of whether to support request retry is the identifier of supporting request retry and the identifier of whether to support route optimization is the identifier of not supporting route optimization, the first HSS initiates a query request to the EMNP, queries a corresponding target subscriber identifier and a target routing address according to the source subscriber identifier, and re-initiates an access request to the second HSS by using the target subscriber identifier and the target routing address.

In one embodiment, if the identifier of whether the request retry is supported is that the request retry is not supported, the first HSS returns an error code to the routing agent node DRA and carries a retry flag of the request retry not supported; and the routing agent node DRA forwards a response message to the MME and rejects the access.

In one embodiment, the request message is a user authentication request or a location update request.

A message routing system in an LTE network, the system comprising:

the MME of the LTE network at the roaming place is used for sending an access request to the DRA, wherein the access request carries a source user identifier;

a routing agent node DRA, configured to locate a first HSS according to the source user identifier, and send a request message to the first HSS, where the request message carries the source user identifier, whether a request retry identifier is supported, and whether a route optimization identifier is supported;

the first HSS is used for returning an error code to the routing agent node DRA and carrying a support request retry mark and a support route optimization mark if the support request retry mark is a support request retry mark and the support route optimization mark is a support route optimization mark when the source user mark queries the database and finds that the user does not exist;

the routing agent node DRA is also used for analyzing the error code, initiating a query request to EMNP, querying a corresponding target user identifier and a target routing address according to the source user identifier, and re-initiating an access request to a second HSS by using the target user identifier and the target routing address.

In one embodiment, the first HSS is further configured to initiate a query request to the EMNP if the identifier of whether the request retry is supported is that the request retry is supported and the identifier of whether the route optimization is supported is that the route optimization is not supported, query a corresponding target subscriber identifier and a target routing address according to the source subscriber identifier, and re-initiate an access request to the second HSS by using the target subscriber identifier and the target routing address.

In one embodiment, the first HSS is further configured to return an error code to the routing agent node DRA and carry an unreported request retry flag if the request retry support flag is that request retry is not supported; the routing agent node DRA is also used for forwarding a response message to the MME and rejecting the access.

A method of message routing in an LTE network, the method comprising:

receiving an access request sent by an MME of an LTE network of a roaming place, wherein the access request carries a source user identifier;

positioning a first HSS according to the source user identifier, and sending a request message to the first HSS, wherein the request message carries the source user identifier, whether a request retry identifier is supported and whether a route optimization identifier is supported;

receiving an error code returned by the first HSS and analyzing the error code, if the error code carries a support request retry mark and a support route optimization mark, initiating a query request to the EMNP, querying a corresponding target user identifier and a target route address according to the source user identifier, and using the target user identifier and the target route address to initiate an access request to the second HSS again.

In one embodiment, if the error code carries a retry flag that does not support the request, a response message is forwarded to the MME, and the access is rejected.

A gateway that enables message routing in an LTE network, the gateway comprising:

the message receiving module is used for receiving an access request sent by an MME of the LTE network of a roaming place, wherein the access request carries a source user identifier;

a message sending module, configured to locate a first HSS according to the source user identifier, and send a request message to the first HSS, where the request message carries the source user identifier, whether a request retry identifier is supported, and whether a route optimization identifier is supported;

the analysis module is used for receiving the error code returned by the first HSS and analyzing the error code;

the query module is used for initiating a query request to the EMNP and querying a corresponding target user identifier and a target routing address according to the source user identifier if the error code carries a request retry support mark and a route optimization support mark;

and the re-access module is used for re-initiating an access request to the second HSS by using the target user identification and the target routing address.

In one embodiment, the gateway further includes:

and the response module is used for forwarding a response message to the MME and rejecting the access if the error code carries a retry-support-request mark.

According to the message routing method, the message routing system and the message routing gateway in the LTE network, whether the request retry identification is supported and whether the route optimization identification is supported are expanded in the request message, under the condition that the request retry is supported and the route optimization is supported, the routing agent node DRA resolves the error code to obtain the request retry support mark and the route optimization support mark, the corresponding target user identification and the target routing address can be inquired from the EMNP according to the source user identification, the routing address can be positioned to the second HSS according to the target routing address, the target user identification and the target routing address can be used for initiating the access request to the second HSS again, the flexible conversion of the routing is realized, and the automatic switching of the number can be realized.

Drawings

FIG. 1 is a flow diagram of a method for message routing in an LTE network in one embodiment;

FIG. 2 is a block diagram of a message routing system in an LTE network in one embodiment;

fig. 3 is a flow chart of a message routing method in an LTE network in another embodiment;

FIG. 4 is a block diagram of a gateway that implements message routing in an LTE network in one embodiment;

fig. 5 is a block diagram of a gateway for implementing message routing in an LTE network according to another embodiment;

FIG. 6 is a diagram illustrating the protocol stack configuration of the EMNP in one embodiment;

FIG. 7 is a diagram of a user authenticated access procedure supporting request retries and supporting route optimization in one embodiment;

FIG. 8 is a diagram of a subscriber location update access procedure supporting request retries and supporting route optimization in one embodiment;

FIG. 9 is a diagram of a user authenticated access procedure that supports request retries but does not support route optimization in one embodiment;

figure 10 is a diagram of a subscriber location update access procedure that supports request retries but does not support route optimization in one embodiment.

Detailed Description

The message routing method in the LTE network provided by the embodiment of the invention is suitable for realizing flexible routing and routing retry of a plurality of numbers of a user under the condition that the user uses a plurality of USIM cards, and can realize automatic number switching. The embodiment of the invention expands whether to support the request retry identification and whether to support the route optimization identification in the request message, the gateway can initiate route query to the EMNP through the expanded request retry information, and can query the EMNP to the corresponding target user identification and target route address according to the source user identification under the condition that the expanded request retry information carries the request retry identification and the support route optimization identification, thereby initiating the access request to the second HSS again by using the target user identification and the target route address, and realizing flexible route conversion and automatic number switching.

As shown in fig. 1, in one embodiment, a message routing method in an LTE network is provided, which includes the following steps:

step 102, the MME of the LTE network at the roaming place sends an access request to the DRA, and the access request carries a source user identifier.

In this embodiment, the user accesses the LTE network of the roaming area by using the source user identifier, for example, the source user identifier may be a Sponsor IMSI provided by a roaming operator used when the 3G user roams internationally. And the MME of the LTE network at the roaming place receives an access request of a user, forwards the access request to the routing agent node DRA, and the request message carries the source user identifier.

And 104, the routing agent node DRA locates a first HSS according to the source user identifier and sends a request message to the first HSS, wherein the request message carries the source user identifier, whether the request retry identifier is supported and whether the route optimization identifier is supported.

In this embodiment, the original request message is expanded, and whether the request retry identifier is supported and whether the route optimization identifier is supported are increased. For example, AIR-Flags are extended in the AIR message (authentication request message) of the original S6a interface to identify whether the AIR message supports request retry and whether route optimization is supported. The ULR-Flags are extended in the ULR message (update location request message) for the original S6a interface to identify whether the ULR message supports request retries and whether route optimization is supported.

Specifically, the routing agent node DRA may be located to the HSS, i.e. the first HSS, according to the source user identifier, and send a request message to the first HSS, where the request message carries an extended identifier for identifying whether the request message supports request retry and whether the request message supports route optimization.

And step 106, when the first HSS finds that the user does not exist after inquiring the database according to the source user identifier, if the request retry support identifier is the request retry support and the route optimization support identifier is the route optimization support, the first HSS returns an error code to the routing agent node DRA and carries a request retry support identifier and a route optimization support identifier.

In this embodiment, the original response message of the request message is also expanded, and whether the request retry identifier is supported or not and whether the route optimization identifier is supported or not are increased. Such as extending the AIA-Flags in the AIA message (authentication answer message) for the original S6a interface to identify whether the AIA message supports request retries and whether route optimization is supported. The ULA-Flags are extended in the ULA message (update location response message) for the original S6a interface to identify whether the ULA message supports request retries and whether route optimization is supported.

And the first HSS inquires that the user does not exist in the database according to the source user identifier, and then returns a response message to the routing agent node DRA, wherein the response message comprises an error code, an expanded identifier whether to support request retry or not and an expanded identifier whether to support route optimization or not. In this embodiment, the identifier of whether to support request retry is a request retry support flag, and the identifier of whether to support route optimization is a route optimization support flag.

And step 108, the routing agent node DRA analyzes the error code, initiates a query request to the EMNP, queries a corresponding target user identifier and a target routing address according to the source user identifier, and re-initiates an access request to the second HSS by using the target user identifier and the target routing address.

The EMNP (Evolved mobile number portability) stores a plurality of user identities of a user, for example, a plurality of IMSI numbers of a user are correspondingly stored when the user uses a plurality of USIM cards. In this embodiment, the routing agent node DRA parses the error code, and obtains a supported Request Retry flag and a supported route optimization flag, and then the routing agent node DRA sends an extended User Retry Request URR (User-Retry-Request) message to the EMNP, where the extended URR message is used to perform route query to the EMNP, and the URR message includes information such as a source User identifier, a host name and a domain name of a message initiator, and a host name and a domain name of a message sending destination.

In a specific embodiment, the URR message is defined as follows:

<User-Retry-Request>::＝<Diameter Header:325,REQ,PXY,16777251>

< Session-Id >// Session ID

[ Vendor-Specific-Application-Id ]// device manufacturer ID

{ Auth-Session-State }// defined by Diameter basic protocol

A parameter for indicating whether the server needs to reserve the state information for the session

{ Origin-Host }// Host name of message originator

{ Origin-real }// Domain name of message originator

[ Destination-Host ]// message transmission Destination Host name

{ Destination-Realm }// message sending Destination domain name

{ Origin-User-Name }// source User identification

Further, the EMNP receives the URR message, queries the corresponding target User identifier and target routing address according to the source User identifier, generates a User Retry response message URA (User-Retry-Answer), and returns to the routing agent node DRA. URA messages are also extended messages that contain information such as the source user identification, the destination user identification (i.e., the redirect number), the destination routing address (i.e., the redirect address domain name), the host name and domain name of the message originator.

In a specific embodiment, the URA message is defined as follows:

<User-Retry-Answer>::＝<DiameterHeader:325,PXY,16777251>

< Session-Id >// Session ID

[ Vendor-Specific-Application-Id ]// device manufacturer ID

[ Result-Code ]// Result Code

[ Experimental-Result ]// error code

[ Error-Diagnostic ]// Error code Diagnostic information

{ Auth-Session-State }// defined by Diameter basic protocol

{ Origin-Host }// Host name of message originator

{ Origin-real }// Domain name of message originator

{ Origin-User-Name }// source User identification

[ Redirection-User-Name ]// redirect number

[ Redirection-real ]// redirect address domain name

Further, the routing agent node receives the URA message, and can be directed to the second HSS according to the target user identification and the target routing address, thereby initiating an access request to the second HSS.

In this embodiment, whether the request retry identifier is supported and whether the route optimization identifier is supported are expanded in the request message, and under the condition that the request retry is supported and the route optimization is supported, the routing agent node DRA resolves the error code to obtain the request retry support identifier and the route optimization support identifier, and then the corresponding target user identifier and the target route address can be queried from the EMNP according to the source user identifier, and the location can be performed to the second HSS according to the target route address, so that the access request can be re-initiated to the second HSS by using the target user identifier and the target route address, thereby realizing flexible conversion of the route and automatic switching of the number.

In an embodiment, if the request message supports the request retry identifier as supporting the request retry and the route optimization identifier as not supporting the route optimization, the first HSS directly initiates a query request to the EMNP, queries a corresponding target subscriber identity and a target routing address according to the source subscriber identity, and re-initiates an access request to the second HSS by using the target subscriber identity and the target routing address.

Specifically, the first HSS sends the expanded URR message to the EMNP, and the EMNP receives the URR message, queries the corresponding target user identifier and the target routing address according to the source user identifier, generates the URA message, and returns the URA message to the routing agent node DRA. And the routing agent node DRA receives the URA message and can be directed to the second HSS according to the target user identification and the target routing address, so that an access request is initiated to the second HSS.

In an embodiment, if the request message supports the request retry identifier as not supporting the request retry, the first HSS returns an error code to the routing agent node DRA and carries a not-supporting request retry flag, and the routing agent node DRA forwards the response message to the MME, so as to reject the access.

In this embodiment, after querying the database according to the source user identifier, the first HSS finds that the user does not exist, and obtains the unreported request retry flag in the request message, returns an error code to the routing agent node DRA and carries the unreported request flag, and the routing agent node DRA parses the error code, obtains the unreported request flag, and forwards a response message to the MME to reject this access.

In one embodiment, the request message may be a user authentication request or a location update request. It can be understood that the message routing method in the LTE network provided by the embodiment of the present invention is not limited to these two request messages, and other request messages that need to be flexibly routed according to the user identifier may use the message routing method in the LTE network provided by the embodiment of the present invention.

As shown in fig. 2, in one embodiment, there is provided a message routing system 20 in an LTE network, the system 20 comprising an MME21, a routing agent node DRA22, and a first HSS23 of a roaming LTE network, wherein:

the MME21 of the roaming LTE network is used for sending an access request to the routing agent node DRA22, wherein the access request carries the source user identification.

The routing agent node DRA22 is configured to locate the first HSS23 according to the source subscriber identity, and send a request message to the first HSS23, where the request message carries the source subscriber identity, a retry-for-request flag, and a routing identity.

The first HSS23 is configured to, when the source subscriber identity queries the database and finds that the subscriber does not exist, return an error code to the routing agent node DRA22 if the request retry support identity is a request retry support identity and the route optimization support identity is a route optimization support identity, and carry a request retry support identity and a route optimization support identity.

In this embodiment, the routing agent node DRA22 is further configured to parse the error code, initiate an inquiry request to the EMNP, inquire the corresponding target user identifier and the target routing address according to the source user identifier, use the target user identifier and the target routing address, and initiate an access request to the second HSS again using the target user identifier and the target routing address.

In one embodiment, the first HSS23 is further configured to initiate a query request to the EMNP if the request retry support identifier is that the request retry support is supported and the route optimization support identifier is that the route optimization support is not supported, query a corresponding target subscriber identifier and a target routing address according to the source subscriber identifier, and re-initiate the access request to the second HSS using the target subscriber identifier and the target routing address.

In one embodiment, the first HSS23 is further configured to return an error code to the routing agent node DRA and carry an unsupported request retry flag if the supported request retry flag indicates that the request retry is not supported. In this embodiment, the routing agent node DRA22 is further configured to forward a response message to the MME, and reject the access.

In one embodiment, the request message may be a user authentication request or a location update request. It can be understood that the message routing system in the LTE network provided by the embodiment of the present invention is not limited to these two request messages, and other request messages that need to be flexibly routed according to the user identifier may use the message routing system in the LTE network provided by the embodiment of the present invention.

As shown in fig. 3, in an embodiment, another message routing method in an LTE network is further provided, which is exemplified by being applied to a gateway in the LTE network, and the method includes:

step 302, receiving an access request sent by an MME of the LTE network of the roaming area, where the access request carries a source user identifier.

In this embodiment, after the user roams, the source user identifier is used to access the LTE network of the roaming area, the MME of the LTE network of the roaming area receives the access request of the user, and forwards the access request to the gateway, and the gateway receives the access request sent by the MME, where the access request carries the source user identifier.

Step 304, positioning the first HSS according to the source user identification, and sending a request message to the first HSS, wherein the request message carries the source user identification, whether the request retry identification is supported, and whether the route optimization identification is supported.

In this embodiment, the request message sent to the HSS by the original gateway is expanded, and whether the request retry identifier is supported and whether the route optimization identifier is supported are increased. For example, AIR-Flags are extended in the AIR message (authentication request message) of the original S6a interface to identify whether the AIR message supports request retry and whether route optimization is supported. The ULR-Flags are extended in the ULR message (update location request message) for the original S6a interface to identify whether the ULR message supports request retries and whether route optimization is supported.

Step 306, receiving the error code returned by the first HSS and analyzing the error code, if the error code carries a retry mark for supporting the request and a route optimization mark for supporting, sending a query request to the EMNP, querying a corresponding target user identifier and a target route address according to the source user identifier, and sending an access request to the second HSS again by using the target user identifier and the target route address.

In this embodiment, the first HSS receives the request message, queries the database according to the source user identifier, finds that the user does not exist, and returns an error code to the gateway if the request retry support identifier in the request message is a request retry support identifier and if the route optimization support identifier is a route optimization support identifier, where the error code carries a request retry support identifier and a route optimization support identifier. And the gateway receives and analyzes the error code, acquires a support request Retry mark and a support route optimization mark, and sends an expanded user Retry request URR (user Retry request) message to the EMNP for carrying out route query to the EMNP. And the EMNP receives the URR message, inquires the corresponding target user identification and the target routing address according to the source user identification, generates a user retry corresponding message URA and returns the URA to the gateway. The gateway receives the URA message, and can be directed to the second HSS according to the target user identification and the target routing address, thereby initiating an access request to the second HSS.

In an embodiment, if the error code carries the retry-support-request flag, a response message is forwarded to the MME, and the access is rejected. In this embodiment, whether the request retry is supported in the request message is the request retry that is not supported, if the first HSS finds that the user does not exist after querying the database according to the source user identifier, an error code is returned to the gateway, and if the gateway receives the error code and obtains the request retry support flag, the gateway forwards the response message to the MME, and rejects the access.

As shown in fig. 4, in one embodiment, there is also provided a gateway 40 for implementing message routing in an LTE network, the gateway 40 comprising:

the message receiving module 41 is configured to receive an access request sent by an MME of the roaming LTE network, where the access request carries a user identifier.

And a message sending module 42, configured to locate the first HSS according to the source subscriber identity, and send a request message to the first HSS, where the request message carries the source subscriber identity, whether the request retry identity is supported, and whether the route optimization identity is supported.

And the parsing module 43 is configured to receive the error code returned by the first HSS and parse the error code.

And the query module 44 is configured to initiate a query request to the EMNP if the error code carries a retry support request flag and a route optimization support flag, and query a corresponding target user identifier and a corresponding target route address according to the source user identifier.

And a re-access module 45, configured to re-initiate the access request to the second HSS using the target subscriber identity and the target routing address.

In one embodiment, as shown in fig. 5, the gateway 40 further includes: a response module 46, configured to forward a response message to the MME if the error code carries the retry-unsupported request flag, and reject the access.

In one embodiment, the request message is a user authentication request or a location update request. It can be understood that the gateway for implementing message routing in the LTE network provided in the embodiment of the present invention is not limited to be used for the two request messages, and other request messages that need to be flexibly routed according to the user identifier may use the gateway for implementing message routing in the LTE network provided in the embodiment of the present invention.

The principle of the method for implementing message routing in the LTE network according to the embodiment of the present invention will be described in detail below with reference to a user authentication access procedure and a user location update access procedure. It can be understood that the method for implementing message routing in the LTE network provided in the embodiment of the present invention is not limited to the user authentication access procedure and the user location update access procedure, and other procedures related to the request message that needs to be flexibly routed according to the user number may also use the provided method for implementing message routing in the LTE network.

Fig. 6 shows a protocol stack configuration of EMNP. As shown in fig. 6, EMNP is an LTE evolution of the conventional circuit domain and MNP device, and supports the MAP protocol and the DIAMETER protocol, and further supports the protocols such as TCAP, SCCP, and IP. The EMNP is used for providing number portability query of a circuit transmission domain, supporting Diameter routing query of an EPC domain and supporting a flexible number conversion strategy.

Fig. 7 shows a user authentication access procedure in supporting request retry and route optimization, and referring to fig. 7, the user authentication access procedure comprises:

step 701: a user accesses an LTE network, and a UE (user equipment) initiates an access Request (Attach Request) to a roaming MME, which carries a source user identifier. This embodiment is exemplified by the source subscriber identity being the sponsorpisi.

Step 702: and the MME at the roaming place finds that the user needs to be authenticated, and sends an authentication request AIR message to the DRA of the roaming gateway, wherein the authentication request AIR message carries the SponsorIMSI.

Step 703: the DRA analyzes the Sponsor IMSI and sends an AIR message to the HSS1, wherein the AIR-Flags in the AIR message carry a support request retry mark and a support optimization routing mark.

Step 704: the HSS1 fails to query the local database using the sponsor imsi, and sends an AIA message to the DRA, the AIA message including the error code 5001 and the AIA-Flags carrying the support request retry flag.

Step 705: DRA analyzes AIA message, finds error code 5001, and AIA-Flags carry request retry mark, then uses SponsorIMSI to send URR inquiry request to EMNP.

Step 706: and the EMNP receives the URR message, queries a local database to obtain a redirection IMSI and a redirection address HSS2 corresponding to the SponsorIMSI, and returns a URA message to the DRA, wherein the URA message carries the converted redirection identifier IMSI and the redirection address HSS 2.

Step 707: the DRA, according to the EMNP return result, initiates AIR query to HSS2 using redirect identity imsi (own imsi).

Step 708: the HSS2 queries the local database using the own IMSI, completes the authentication operation, and returns an AIA message to the DRA.

Step 709: the DRA returns an AIA message to the MME, and the AIA message carries the relevant authentication vector.

Step 710: and the MME completes the user authentication process.

Fig. 8 shows a subscriber location update access procedure in support of request retry and in support of route optimization, and referring to fig. 8, the subscriber location update access procedure comprises:

step 801: after the user is roaming internationally, the UE initiates an access Request (Attach Request) to the MME in the roaming area, where the access Request carries a source user identifier, and this embodiment takes the source user identifier as sponsor imsi as an example for explanation.

Step 802: and the MME completes the authentication operation of the user.

Step 803: after the authentication is passed, the MME initiates a location update request ULR to the routing agent node DRA, and the ULR message carries the Sponsor IMSI.

Step 804: the DRA analyzes the Sponsor IMSI and sends an ULR message to the HSS1, wherein the ULR-Flags carry a supported request retry mark and a supported route optimization mark.

Step 805: the HSS1 fails to query the database using the Sponsor IMSI, and returns a ULA message to the DRA, where the ULA message includes the error code 5001 and ULA-Flags, and the ULA-Flags carry a retry flag of the support request.

Step 806: and the DRA analyzes the ULA message, an error code is found to be 5001, and the ULA-Flags carry a retry mark of the support request, and initiates a URR query to the EMNP by using the SponsorIMSI, wherein the URR message carries a source user identifier SponsorIMSI.

Step 807: and the EMNP receives the URR message, queries a local database to obtain a redirection IMSI and a redirection address HSS2 corresponding to the Sponsor IMSI, and returns a URA message to the DRA, wherein the URA message carries the converted redirection identifier IMSI and the redirection address HSS 2.

Step 808: and the DRA sends an ULR query to the HSS2 by using the redirected own IMSI according to the EMNP return result, and carries the Sponsor IMSI and ULR-Flags, wherein the ULR-Flags carries a support request retry mark.

Step 809: the HSS2 detects that the ULR-Flags carries the retry flag of the support Request, and carries the Sponsor IMSI, and the user has been previously registered in other MMEs (the HSS records the MME address of the user previously registered), and first initiates a CLR (Cancel-Location-Request) Request to an old MME (i.e., the registered MME) using the Sponsor IMSI.

Step 810: the Old MME deletes the original bearer of the user and returns a CLA (Cancel-Location-Answer) message to the HSS 2.

Step 811: HSS2 then queries the local database using the own IMSI and returns a ULA message to the DRA.

Step 812: the DRA returns a ULA message to the MME.

Step 813: and the MME starts to establish a bearer for the user and finishes the user access operation.

Fig. 9 shows a user authentication access procedure when request retry is supported but route optimization is not supported, and referring to fig. 9, the user authentication access procedure comprises:

step 901: the user accesses the LTE network, and the UE initiates an access Request (Attach Request) to the MME of the roaming place, wherein the access Request carries the source user identification. This embodiment is exemplified by the source subscriber identity being the Sponsor IMSI.

Step 902: and the MME at the roaming place finds that the user needs to be authenticated, and sends an authentication request AIR message to the DRA of the roaming gateway, wherein the authentication request AIR message carries the Sponsor IMSI.

Step 903: the DRA analyzes the Sponsor IMSI and sends an AIR message to the HSS1, wherein the AIR-Flags in the AIR message carry a support request retry mark and a non-support optimization routing mark.

Step 904: the HSS1 uses the Sponsor IMSI to query the local database failure and the failure reason is unknown user, but the AIR-Flags carry the retry flag of the support request and the no-support route optimization flag, then the HSS1 uses the Sponsor IMSI to initiate a URR query request to the EMNP, and the URR message carries the Sponsor IMSI.

Step 905: the EMNP queries the local database to obtain the redirected IMSI and the redirected address HSS2 corresponding to the Sponsor IMSI, and returns a URA message to the HSS1, where the URA message carries the translated redirected IMSI and the redirected address HSS 2.

Step 906: HSS1 initiates AIR query to HSS2 using redirect identity imsi (own imsi) according to EMNP return result.

Step 907: HSS2 queries the local database using the own IMSI, completes the authentication operation, and returns an AIA message to HSS 1.

Step 908: the HSS1 returns an AIA message to the DRA carrying the relevant authentication vector.

Step 909: the DRA returns an AIM message to the MME, and the AIM message carries the relevant authentication vector.

Step 910: and the MME completes the user authentication process.

Fig. 10 shows a subscriber location update access procedure when request retry is supported but route optimization is not supported, and referring to fig. 10, the subscriber location update access procedure comprises:

step 1001: after the user is roaming internationally, the UE initiates an access Request (Attach Request) to the MME in the roaming area, where the access Request carries a source user identifier, and this embodiment takes the source user identifier as Sponsor IMSI as an example for explanation.

Step 1002: and the MME completes the authentication operation of the user.

Step 1003: after the authentication is passed, the MME initiates a location update request ULR to the routing agent node DRA, and the ULR message carries the Sponsor IMSI.

Step 1004: the DRA analyzes the Sponsor IMSI and sends an ULR message to the HSS1, wherein the ULR-Flags carry a supported request retry flag and a non-supported route optimization flag.

Step 1005: if the HSS1 fails to query the local database using the Sponsor IMSI and the reason of the failure is an unknown user, but ULR-Flags carry a retry flag for supporting the request and a route optimization flag for not supporting, the HSS1 initiates a URR query request to the EMNP using the Sponsor IMSI and the URR message carries the Sponsor IMSI.

Step 1006: the EMNP queries the local database to obtain the redirected IMSI and the redirected address HSS2 corresponding to the Sponsor IMSI, and returns a URA message to the HSS1, where the URA message carries the translated redirected IMSI and the redirected address HSS 2.

Step 1007: and the HSS1 initiates an ULR query to the HSS2 by using a redirection identifier IMSI (own IMSI) according to the EMNP return result, and carries the Sponsor IMSI and ULR-Flags, wherein the ULR-Flags carry a support request retry mark.

Step 1008: HSS2 detects that the ULR-Flags carries the retry flag of support request, and carries the SponsorIMSI, and the user has been registered in other MME before (HSS records the MME address registered before the user), then initiates the CLR request to the old MME (i.e. the registered MME) by using the SponsorIMSI.

Step 1009: the Old MME deletes the original bearer of the user and returns a CLA message to HSS 2.

Step 1010: HSS2 then queries the local database using the own IMSI and returns a ULA message to HSS 1.

Step 1011: the HSS1 returns a ULA message to the DRA.

Step 1012: the DRA returns a ULA message to the MME.

Step 1013: and the MME starts to establish a bearer for the user and finishes the user access operation.

The technical features of the embodiments described above may be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the embodiments described above are not described, but should be considered as being within the scope of the present specification as long as there is no contradiction between the combinations of the technical features.

The above-mentioned embodiments only express several embodiments of the present invention, and the description thereof is more specific and detailed, but not construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the inventive concept, which falls within the scope of the present invention. Therefore, the protection scope of the present patent shall be subject to the appended claims.

Claims

1. A method of message routing in an LTE network, the method comprising:

2. The method of claim 1 wherein if the retry support identification is retry support and the optimize support identification is not optimize support, the first HSS initiates a query request to the EMNP, queries a corresponding target subscriber identification and target routing address according to the source subscriber identification, and re-initiates an access request to the second HSS using the target subscriber identification and target routing address.

3. The method according to claim 1, wherein if the identifier of whether or not to support request retry is that request retry is not supported, the first HSS returns an error code to the routing agent node DRA and carries a flag of not supporting request retry; and the routing agent node DRA forwards a response message to the MME and rejects the access.

4. The method of claim 1, wherein the request message is a user authentication request or a location update request.

5. A message routing system in an LTE network, the system comprising:

6. The system of claim 5 wherein the first HSS is further configured to initiate a query request to the EMNP if the RET ID is RET and the ROC ID is not ROC, query a corresponding target subscriber ID and target routing address according to the source subscriber ID, and re-initiate an access request to the second HSS using the target subscriber ID and target routing address.

7. The system of claim 5, wherein the first HSS is further configured to return an error code to the routing agent node DRA and carry an unreported request retry flag if the request retry supported identifier is that request retry is not supported; the routing agent node DRA is also used for forwarding a response message to the MME and rejecting the access.

8. The system of claim 5, wherein the request message is a user authentication request or a location update request.

9. A method of message routing in an LTE network, the method comprising:

10. The method of claim 9, wherein if the error code carries an unreported request retry flag, a response message is forwarded to the MME to reject the access.

11. The method of claim 9, wherein the request message is a user authentication request or a location update request.

12. A gateway for implementing message routing in an LTE network, the gateway comprising:

13. The gateway of claim 12, further comprising:

14. The gateway of claim 12, wherein the request message is a user authentication request or a location update request.