WO2017097060A1

WO2017097060A1 - Message routing method and system in lte network, and gateway

Info

Publication number: WO2017097060A1
Application number: PCT/CN2016/103973
Authority: WO
Inventors: 仝黎
Original assignee: 中兴通讯股份有限公司
Priority date: 2015-12-07
Filing date: 2016-10-31
Publication date: 2017-06-15
Also published as: CN106851763A; CN106851763B

Abstract

A message routing method and system in an LTE network, and a gateway. The method comprises: an MME at a roaming site LTE network sends an access request to an international roaming gateway DRA, the access request carrying a source subscriber identifier; the international roaming gateway DRA positions a first HSS according to the source subscriber identifier, and sends a request message to the first HSS, the request message carrying the source subscriber identifier, an identifier indicating whether a request retry is supported and an identifier indicating whether routing optimization is supported; when the first HSS finds that a subscriber does not exist after the first HSS queries in a database according to the source subscriber identifier, the first HSS returns an error code to the international roaming gateway DRA and carries the identifier indicating whether a request retry is supported and the identifier indicating whether routing optimization is supported if the identifier indicating whether a request retry is supported indicates that a retry is supported and the identifier indicating whether routing optimization is supported indicates that routing optimization is supported; and the international roaming gateway DRA parses the error code, initiates a query request to an EMNP, and fining a corresponding target subscriber identifier and a target routing address according to the source subscriber identifier, and again initiates an access request to a second HSS by using the target subscriber identifier and the target routing address.

Description

Message routing method, system and gateway in LTE network

Technical field

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

Background technique

Long Term Evolution (LTE) is a long-term evolution of the Universal Mobile Telecommunications System (UMTS) technology standard specified by the 3rd Generation Partnership Project (3GPP). The S6a interface between the Mobility Management Entity (MME) and the Home Subscriber Server (HSS) in the LTE core network is based on the Diameter basic protocol. The MME is a key control node in the 3GPP protocol LTE. The Diameter basic protocol provides a secure, reliable, and easily scalable framework for multiple authentication, authorization, and accounting services. The protocol may involve performance negotiation, how messages are sent, and Waiting for the parties to finally end the communication and other aspects. In the RFC3588Diameter protocol, the Diameter message routing is defined by a domain-based routing table. All domain-based routing lookups can be performed by means of a routing table.

The 3GPP 29.272 protocol specifies the manner in which the S6a interface locates the HSS. The MME or the Diameter Routing Agent (DRA) needs to locate the HSS according to the User-Name AVP in the S6a interface message, that is, the International Mobile Subscriber Identification Number (IMSI) of the user according to the S6a interface message. Locate the HSS.

However, in the related art mobile communication network, there is a case where one user simultaneously uses a plurality of Universal Subscriber Identity Modules (USIMs). For example, for operators such as China Telecom that use Code Division Multiple Access (CDMA) technology, 3G users generally use the sponsor IMSI provided by roaming operators during international roaming, and carry out 4G services in China. When using China Telecom's self-operated IMSI. However, if such users need to use 4G services for international roaming, due to the negotiation of roaming agreements involving new numbers, for a long period of time, these users still need to use the Sponsor IMSI to access the LTE network during international roaming.

Summary of the invention

The present disclosure provides a message routing method, system and gateway in an LTE network capable of implementing flexible transformation of routes and automatic number switching.

A message routing method in an LTE network, the method includes:

The MME of the roaming LTE network sends an access request to the international roaming gateway DRA, where the access request carries the source user identifier;

The international roaming gateway DRA locates the first HSS according to the source user identifier, and sends a request message to the first HSS, where the request message carries the source user identifier, whether the request retry identifier is supported, and whether the route optimization identifier is supported;

If the first HSS queries the database according to the source user identifier and finds that the user does not exist, if the request retry identifier is supported to support the request retry, and whether the route optimization identifier is supported to support route optimization, The first HSS returns an error code to the international roaming gateway DRA, and carries a support request retry flag and a support route optimization flag;

The international roaming gateway DRA parses the error code, initiates a query request to the EMNP, queries the corresponding target user identifier and the target routing address according to the source user identifier, and uses the target user identifier and the target routing address to re-route The second HSS initiates an access request.

Optionally, if the request retry identifier is supported to support request retry, and whether the route optimization identifier is supported to not support route optimization, the first HSS initiates a query request to the EMNP according to the source. The user identifier queries the corresponding target user identifier and the target routing address, and uses the target user identifier and the target routing address to re-initiate an access request to the second HSS.

Optionally, if the request retry identifier is not supported for request retry, the first HSS returns an error code to the international roaming gateway DRA and carries a non-support request retry flag; the international roaming gateway DRA forwards the response message. To the MME, the access is denied.

Optionally, 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 roaming LTE network is configured to send an access request to the international roaming gateway DRA, where the access request carries the source user identifier;

The international roaming gateway DRA is configured to locate the 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 the request retry identifier is supported, and whether the route optimization identifier is supported. ;

If the first HSS is configured to query the database according to the source user identifier and find that the user does not exist, if the request retry identifier is supported to support the request retry, and the route optimization identifier is supported to support route optimization, Return an error code to the international roaming gateway DRA, and carry the support request retry flag and Support for route optimization flags;

The international roaming gateway DRA is further configured to parse the error code, initiate a query request to the EMNP, query the corresponding target user identifier and the target routing address according to the source user identifier, and use the target user identifier and the target routing address. The access request is re-initiated to the second HSS.

Optionally, the first HSS is further configured to: if the support retry identifier is supported to support request retry, and whether the route optimization identifier is supported to not support route optimization, initiate a query request to the EMNP, according to the The source user identifier queries the corresponding target user identifier and the target routing address, and uses the target user identifier and the target routing address to re-initiate an access request to the second HSS.

Optionally, the first HSS is further configured to: if the request retry identifier is not supported for request retry, return an error code to the international roaming gateway DRA and carry a non-support request retry flag; the international roaming The gateway DRA is also used to forward the response message to the MME, rejecting the current access.

A message routing method in an LTE network is applied to a gateway side, and the method includes:

Receiving an access request sent by the MME of the roaming LTE network, where the access request carries the source user identifier;

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

Receiving an error code returned by the first HSS and parsing the error code, if the error code carries a support request retry flag and a support route optimization flag, initiating a query request to the EMNP, and querying the corresponding according to the source user identifier The target user identifier and the target routing address, and re-initiating an access request to the second HSS using the target user identifier and the target routing address.

Optionally, if the error code carries the unsupported request retry flag, the response message is forwarded to the MME, and the current access is rejected.

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

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

The message sending module is configured to: locate the 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 the request retry identifier is supported, and whether the route optimization identifier is supported;

a parsing module configured to receive an error code returned by the first HSS and parse the error code;

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

Re-accessing the module, configured to re-initiate an access request to the second HSS using the target user identity and the target routing address.

Optionally, the gateway further includes:

The response module is configured to: if the error code carries the unsupported request retry flag, forward the response message to the MME, rejecting the current access.

A non-transitory computer readable storage medium storing computer executable instructions for performing a message routing method in an LTE network as described above.

A non-transitory computer readable storage medium storing computer executable instructions for performing the above-described message routing method applied to an LTE network on a gateway side.

An electronic device comprising one or more processors, a memory, and one or more programs, the one or more programs being stored in a memory, when executed by one or more processors, performing the Message routing method in LTE networks.

An electronic device comprising one or more processors, a memory, and one or more programs, the one or more programs being stored in a memory, when executed by one or more processors, executing the application A message routing method in an LTE network on the gateway side.

The message routing method, system and gateway in the foregoing LTE network extend the support request retry identifier and whether to support the route optimization identifier in the request message, and support the request retry and support route optimization, the international roaming gateway DRA The error code is parsed to obtain the support request retry flag and the support route optimization flag, and then the corresponding target user identifier and the target route address can be queried according to the source user identifier to the EMNP, and the second HSS can be located according to the target route address, thereby being usable. The target user identifier and the target routing address re-initiate an access request to the second HSS, so that flexible routing can be implemented, and automatic number switching can be implemented.

DRAWINGS

1 is a flowchart of a message routing method in an LTE network according to an embodiment of the present disclosure;

2 is a framework diagram of a message routing system in an LTE network according to an embodiment of the present disclosure;

FIG. 3 is a flowchart of a message routing method applied to an LTE network on a gateway side according to an embodiment of the present disclosure Figure

4 is a structural block diagram of a gateway for implementing message routing in an LTE network according to an embodiment of the present disclosure;

FIG. 5 is a structural block diagram of a gateway for implementing message routing in an LTE network according to an embodiment of the present disclosure;

6 is a schematic diagram of a protocol stack configuration of an EMNP according to an embodiment of the present disclosure;

FIG. 7 is a schematic diagram of a user authentication access procedure supporting request retry and supporting route optimization according to an embodiment of the present disclosure;

FIG. 8 is a schematic diagram of a user location update access procedure supporting request retry and supporting route optimization according to an embodiment of the present disclosure;

FIG. 9 is a schematic diagram of a user authentication access procedure supporting request retry but not supporting route optimization according to an embodiment of the present disclosure;

10 is a schematic diagram of a user location update access procedure supporting request retry but not supporting route optimization according to an embodiment of the present disclosure;

FIG. 11 is a schematic structural diagram of hardware of an electronic device according to an embodiment of the present disclosure;

FIG. 12 is a schematic structural diagram of hardware of another electronic device according to an embodiment of the present disclosure.

detailed description

The message routing method in the LTE network provided by the embodiment of the present disclosure can be applied to a flexible routing and route retry of multiple numbers of users when a user uses multiple USIM cards, and can automatically switch numbers. In the embodiment of the present disclosure, by extending whether the request retry identifier is supported in the request message and whether the route optimization identifier is supported, the gateway may initiate a route query to the EMNP through the extended request retry message, and carry the request in the extended request retry message. In the case of the test flag and the support route optimization flag, the corresponding target user identifier and the target route address may be queried to the EMNP according to the source user identifier, thereby re-initiating the access request to the second HSS by using the target user identifier and the target route address, thereby Flexible routing of routes and automatic switching of numbers can be achieved.

As shown in FIG. 1, in an embodiment, a message routing method in an LTE network is provided, including step 102, step 104, step 106, and step 108.

In step 102, the MME of the roaming LTE network sends an access request to the international roaming gateway DRA, where the access request carries the source user identifier.

In this embodiment, the user may use the source user identifier to access the roaming LTE network. For example, the source user identifier may be the Sponsor IMSI provided by the roaming operator used by the 3G user during international roaming. The MME of the roaming LTE network receives the access request of the user, and forwards the access request to the international roaming gateway DRA, where the request message carries the source user identifier.

In step 104, the international roaming gateway DRA locates the first HSS according to the source user identifier, and sends a request message to the first HSS, where 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 request message is extended, and whether the request retry identifier and the route optimization identifier are supported may be added. For example, for the AIR-Flags in the Authentication Response (AIR) message of the S6a interface, it is set to identify whether the AIR message supports request retry and whether to support route optimization. The extended ULR-Flags in the Update Location Request (ULR) message of the S6a interface is set to identify whether the ULR message supports request retry and whether route optimization is supported.

Optionally, the international roaming gateway DRA can locate the HSS, that is, the first HSS, according to the source user identifier, and send a request message to the first HSS, where the request message carries the extended identifier, and is set to identify whether the request message supports the request retry. And whether to support route optimization.

In step 106, when the first HSS queries the database according to the source user identifier and finds that the user does not exist, if the request retry identifier is supported to support the request retry, and whether the route optimization identifier is supported to support route optimization, the first HSS may An error code is returned to the international roaming gateway DRA, and the support request retry flag and the support route optimization flag can be carried.

In this embodiment, the response message to the request message is also extended, and whether the request retry identifier and the route optimization identifier are supported may be added. For example, for the AIA message (authentication response message) of the S6a interface, the AIA-Flags is extended, and it is set to identify whether the AIA message supports the request retry and whether the route optimization is supported. The extended ULA-Flags in the Update Location Answer (ULA) message of the S6a interface is set to identify whether the ULA message supports request retry and whether route optimization is supported.

The first HSS, according to the source user identifier, queries that the user does not exist in the database, and may return a response message to the international roaming gateway DRA, including whether the error code and the extended support request retry identifier and whether the route optimization identifier is supported. In this embodiment, whether the request retry identifier is supported may be a support request retry flag, and whether the route optimization identifier is supported may be a support route optimization flag.

In step 108, the international roaming gateway DRA parses the error code, and may initiate a query request to the EMNP, query the corresponding target user identifier and the target routing address according to the source user identifier, and re-route to the second HSS using the target user identifier and the target routing address. Initiate an access request.

The Evolved Mobile Number Portability (EMNP) stores a plurality of user identifiers of the user. For example, if the user uses multiple USIM cards, the user stores multiple IMSI numbers of the user. In this embodiment, the international roaming gateway DRA parses the error code and obtains a support request retry. The flag and the support route optimization flag, the international roaming gateway DRA sends an extended User-Retry-Request (URR) message to the EMNP, and the extended URR message is set to perform routing query to the EMNP, in the extended URR message. It can contain information such as the source user ID, the host name and domain name of the message originator, the destination address of the message, and the domain name.

In an alternative embodiment, the URR message is defined as follows:

Optionally, the EMNP receives the URR message, and may query the corresponding target user identifier and the target routing address according to the source user identifier, and generate a User-Retry-Answer (URA) message, and return to the international roaming gateway DRA. . The URA message is also an extended message, which may include information such as the source user ID, the target user ID (ie, the redirected number), the destination routing address (ie, the redirected address domain name), and the host name and domain name of the message originator.

In an alternative embodiment, the URA message is defined as follows:

Optionally, the international roaming gateway receives the URA message, and can be directed to the second HSS according to the target user identifier and the target routing address, thereby initiating an access request to the second HSS.

In this embodiment, by extending whether the request retry identifier is supported and whether the route optimization identifier is supported in the request message, when the request retry is supported and the route optimization is supported, the international roaming gateway DRA parses the error code to obtain the support request weight. The test flag and the support route optimization flag can further query the corresponding target user identifier and the target route address to the EMNP according to the source user identifier, and can be located to the second HSS according to the target route address, so that the target user identifier and the target route address can be used again. An access request is initiated to the second HSS, so that flexible routing can be implemented, and automatic number switching can be implemented.

In an embodiment, if the request retry identifier in the request message supports the request retry, and the route optimization identifier is supported to not support the route optimization, the first HSS may directly initiate a query request to the EMNP, according to the source. The user identifier queries the corresponding target user identifier and the target routing address, and can re-initiate the access request to the second HSS by using the target user identifier and the target routing address.

Optionally, the first HSS sends an extended 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, and generates a URA message, and returns to the international roaming gateway DRA. The international roaming gateway DRA receives the URA message, and can be directed to the second HSS according to the target user identifier and the target routing address, thereby initiating an access request to the second HSS.

In an embodiment, if the request retry identifier in the request message does not support the request retry, the first HSS returns an error code to the international roaming gateway DRA and carries the unsupported request retry flag, and the international roaming gateway DRA can The response message is forwarded to the MME, and the current access is denied.

In this embodiment, after the first HSS queries the database according to the source user identifier and finds that the user does not exist, and obtains the unrequested request retry flag in the request message, the first HSS returns an error code to the international roaming gateway DRA and carries the unsupported request flag. The international roaming gateway DRA parses the error code, and can obtain the unsupported request flag, and then forwards the response message to the MME, rejecting the current access.

In one embodiment, the request message can 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 disclosure is not limited to the two types of request messages, and other request messages that need to be flexibly routed according to the user identifier may be provided by using the embodiments of the present disclosure. A message routing method in an LTE network.

As shown in FIG. 2, in one embodiment, a message routing system 20 in an LTE network is provided. The system 20 includes an MME 21 of an LTE network roaming, an international roaming gateway DRA 22, and a first HSS 23, where:

The MME 21 of the roaming LTE network is configured to send an access request to the international roaming gateway DRA 22, where the access request carries the source user identity.

The international roaming gateway DRA 22 is configured to locate the first HSS 23 according to the source user identifier, and send a request message to the first HSS 23, where the request message carries the source user identifier, whether the request retry flag is supported, and whether the route identifier is supported.

When the first HSS 23 is configured to query the database according to the source user identifier and find that the user does not exist, if the request retry identifier is supported to support the request retry, and whether the route optimization identifier is supported to support route optimization, then the international roaming gateway DRA 22 is provided. The error code is returned, and the support request retry flag and the support route optimization flag are carried.

In this embodiment, the international roaming gateway DRA 22 is further configured to parse the error code, initiate a query request to the EMNP, query the corresponding target user identifier and the target routing address according to the source user identifier, and use the target user identifier and the target routing address, and The access request is re-initiated to the second HSS using the target user identity and the target routing address.

Optionally, the first HSS 23 is further configured to: if the request retry identifier is supported to support the request retry, and whether the route optimization identifier is supported to not support route optimization, initiate a query request to the EMNP, and query the corresponding according to the source user identifier. The target user identifier and the target routing address, and use the target user identifier and the target routing address to re-initiate an access request to the second HSS.

Optionally, the first HSS 23 is further configured to: if the request retry identifier is supported to not support the request retry, return an error code to the international roaming gateway DRA and carry the unsupported request retry flag. In this embodiment, the international roaming gateway DRA 22 is further configured to forward the response message to the MME, and reject the current access.

Optionally, 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 disclosure is not limited to the two types of request messages, and other request messages that need to be flexibly routed according to the user identifier may be provided by using the embodiments of the present invention. A message routing system in an LTE network.

As shown in FIG. 3, in an embodiment, a message routing method in another LTE network is also provided. The method is applied to a gateway in an LTE network, where the method includes step 302, step 304, and Step 306.

In step 302, receiving an access request sent by an MME of a roaming LTE network, the access request The source user ID is carried in the middle.

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

In step 304, the first HSS is located according to the source user identifier, and a request message is sent to the first HSS, where 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 request message sent by the gateway to the HSS is extended, and whether the request retry identifier and the route optimization identifier are supported may be added. For example, for AIR-Flags in the AIR message (authentication request message) of the S6a interface, it is set to identify whether the AIR message supports request retry and whether route optimization is supported. For ULR-Flags in the ULR message of the S6a interface, it is set to identify whether the ULR message supports request retry and whether route optimization is supported.

In step 306, the error code returned by the first HSS is received and the error code is parsed. If the error code carries the support request retry flag and the support route optimization flag, the query request is sent to the EMNP, and the corresponding target is queried according to the source user identifier. The user identity and the target routing address, and re-initiating an access request to the second HSS using the target user identity and the target routing address.

In this embodiment, the first HSS receives the request message, and after the database is queried according to the source user identifier, the user does not exist, and the request message supports the request retry identifier to support the request retry, and whether the route optimization identifier is supported as the support route. The identifier returns an error code to the gateway and carries the support request retry flag and the support route optimization flag. When the gateway receives the error code and parses the error code, obtains the support request retry flag, and supports the route optimization flag, it sends an extended URR message to the EMNP, which can be set to perform route query to the EMNP. The EMNP receives the URR message, queries the corresponding target user identifier and the target routing address according to the source user identifier, generates a user retry corresponding message URA, and returns to the gateway. The gateway receives the URA message and can be directed to the second HSS according to the target user identity and the target routing address, so that an access request can be initiated to the second HSS.

Optionally, if the error code carries the unsupported request retry flag, the response message is forwarded to the MME, and the current access is denied. In this embodiment, whether the request retry is supported in the request message does not support the request retry. After the first HSS queries the database according to the source user identifier and finds that the user does not exist, the error code is returned to the gateway, and the gateway receives the error code and obtains the error code. If the request retry flag is not supported, the response message is forwarded to the MME, and the current access is denied.

Optionally, 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 disclosure is not limited to the two request messages. 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 embodiments of the present disclosure.

As shown in FIG. 4, in an embodiment, a gateway 40 for implementing message routing in an LTE network is provided. The gateway 40 includes a message receiving module 41, a message sending module 42, a parsing module 43, a query module 44, and Re-access module 45.

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

The message sending module 42 is configured to locate the 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 the request retry identifier is supported, and whether the route optimization identifier is supported.

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

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

The re-access module 45 is configured to re-initiate an access request to the second HSS using the target user identity and the target routing address.

Optionally, as shown in FIG. 5, the gateway 40 may further include: a response module 46, configured to: if the error code carries the unsupported request retry flag, forward the response message to the MME, rejecting the current access.

Optionally, 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 by the embodiment of the present disclosure is not limited to being applicable to the two types of request messages, and other request messages that need to be flexibly routed according to the user identifier may use the present message. A gateway implementing message routing in an LTE network as provided by the disclosed embodiments.

The method for implementing message routing in the LTE network provided by the embodiment of the present disclosure is described in detail below in conjunction with the user authentication access procedure and the user location update access procedure. It can be understood that the method for implementing message routing in the LTE network provided by the embodiment of the present disclosure is not limited to the user authentication access procedure and the user location update access procedure, and other request messages that need to be flexibly routed according to the user number. The process involved can also use the method of implementing message routing in the provided LTE network.

Figure 6 shows the protocol stack configuration of the EMNP. It can be seen from FIG. 6 that EMNP is an LTE evolution of the circuit domain and the MNP device in the related art, and can support both the MAP protocol and the DIAMETER protocol, and can also support protocols such as TCAP, SCCP, or IP. The EMNP can be set to provide a number portability query for the transmission domain. It also supports Diameter route query in EPC domain and supports flexible number change strategy.

FIG. 7 shows a user authentication access procedure for supporting request retry and supporting route optimization. Referring to FIG. 7, the user authentication access procedure may include steps 701-710.

In step 701, the user accesses the LTE network, and the user equipment (User Equipment, UE) initiates an access request (Attach Request) to the roaming MME, and carries the source user identifier. This embodiment uses the source user identifier as the Sponsor IMSI for illustration.

In step 702, the roaming MME finds that the user needs to be authenticated, and sends an AIR message to the roaming gateway DRA, carrying the Sponsor IMSI.

In step 703, the DRA analyzes the Sponsor IMSI and sends an AIR message to the HSS 1. The AIR-Flags in the AIR message carries the support request retry flag and the support optimized route flag.

In step 704, the HSS1 fails to query the local database by using the Sponsor IMSI, and sends an AIA message to the DRA. The AIA message includes an error code 5001, and the AIA-Flags carries the support request retry flag.

In step 705, the DRA parses the AIA message, finds the error code 5001, and the AIA-Flags carries the request retry flag, and then uses the Sponsor IMSI to initiate a URR query request to the EMNP.

In step 706, the EMNP receives the URR message, queries the local database, obtains the redirected IMSI and the redirected address HSS2 corresponding to the Sponsor IMSI, and returns a URA message to the DRA, which carries the translated redirected IMSI and the redirected address HSS2.

In step 707, the DRA initiates an AIR query to HSS 2 using the redirected IMSI (ie, own IMSI) based on the EMNP return result.

In step 708, HSS 2 queries the local database using own IMSI, completes the authentication operation, and returns an AIA message to the DRA.

In step 709, the DRA returns an AIA message to the MME, carrying the associated authentication vector.

In step 710, the MME completes the user authentication process.

FIG. 8 shows a user location update access procedure for supporting request retry and supporting route optimization. Referring to FIG. 8, the user location update access procedure may include steps 801-813.

In step 801, after the user roams internationally, the UE initiates an access request (Attach Request) to the roaming MME to carry the source user identifier. In this embodiment, the source user identifier is the Sponsor IMSI as an example.

In step 802, the MME completes the authentication operation of the user.

In step 803, after the authentication is passed, the MME initiates a location update request ULR to the international roaming gateway DRA, and the ULR message carries the Sponsor IMSI.

In step 804, the DRA analyzes the Sponsor IMSI and sends a ULR message to the HSS1, where the ULR-Flags carries the support request retry flag and the support route optimization flag.

In step 805, the HSS 1 fails to query the database using the Sponsor IMSI, and returns a ULA message to the DRA, which includes an error code 5001 and ULA-Flags, and the ULA-Flags carries a support request retry flag.

In step 806, the DRA parses the ULA message, finds that the error code is 5001, and carries the support request retry flag in the ULA-Flags, and then uses the Sponsor IMSI to initiate a URR query to the EMNP, where the URR message carries the source user identifier Sponsor IMSI.

In step 807, the EMNP receives the URR message, queries the local database, obtains the redirected IMSI and the redirected address HSS2 corresponding to the Sponsor IMSI, and returns a URA message to the DRA, which carries the translated redirected IMSI and the redirected address HSS2.

In step 808, the DRA initiates a ULR query to the HSS2 using the redirected own IMSI according to the EMNP return result, and carries the Sponsor IMSI and the ULR-Flags, and the ULR-Flags carries the support request retry flag.

In step 809, the HSS 2 detects that the support request retry flag is carried in the ULR-Flags, and carries the Sponsor IMSI, and the user has previously registered with other MMEs (the HSS records the MME address previously registered by the user), and then uses the Sponsor first. The IMSI initiates a Cancel-Location-Request (CLR) request to the registered MME (ie, the old MME).

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

In step 811, HSS 2 uses the own IMSI to query the local database and returns a ULA message to the DRA.

In step 812, the DRA returns a ULA message to the MME.

In step 813, the MME starts to establish a bearer for the user, and completes the user access operation.

FIG. 9 shows a user authentication access procedure when the request retry is supported but the route optimization is not supported. Referring to FIG. 9, the user authentication access procedure may include steps 901 to 910.

In step 901, the user accesses the LTE network, and the UE initiates an access request (Attach Request) to the roaming MME, carrying the source user identifier. This embodiment uses the source user identifier as the Sponsor IMSI for illustration.

In step 902, the roaming MME finds that the user needs to be authenticated, and sends an authentication request AIR message to the roaming gateway DRA, carrying the Sponsor IMSI.

In step 903, the DRA analyzes the Sponsor IMSI and sends an AIR message to the HSS 1. The AIR-Flags in the AIR message carries the support request retry flag and does not support the optimized route flag.

In step 904, HSS 1 fails to query the local database using Sponsor IMSI and the reason for the failure is unknown user, but AIR-Flags carries the support request retry flag and does not support the route optimization flag, then HSS1 uses the Sponsor IMSI to initiate a URR query request to the EMNP. The URR message carries the Sponsor IMSI.

In step 905, the EMNP queries the local database, obtains the redirected IMSI and the redirected address HSS2 corresponding to the Sponsor IMSI, and returns a URA message to the HSS1, which carries the translated redirected IMSI and the redirected address HSS2.

In step 906, HSS 1 initiates an AIR query to HSS 2 using the redirected IMSI (ie, own IMSI) based on the EMNP return result.

In step 907, HSS 2 queries the local database using own IMSI, completes the authentication operation, and returns an AIA message to HSS1.

In step 908, HSS 1 returns an AIA message to the DRA carrying the associated authentication vector.

In step 909, the DRA returns an AIM message to the MME, carrying the associated authentication vector.

In step 910, the MME completes the user authentication process.

FIG. 10 shows a user location update access procedure when the request retry is supported but the route optimization is not supported. Referring to FIG. 10, the user location update access procedure may include step 1001 - step 1013.

In step 1001, after the user roams internationally, the UE initiates an access request (Attach Request) to the roaming MME to carry the source user identifier. In this embodiment, the source user identifier is the Sponsor IMSI as an example.

In step 1002, the MME completes the authentication operation of the user.

In step 1003, after the authentication is passed, the MME initiates a location update request ULR to the international roaming gateway DRA, and the ULR message carries the Sponsor IMSI.

In step 1004, the DRA analyzes the Sponsor IMSI and sends a ULR message to the HSS 1, wherein the ULR-Flags carries the support request retry flag and does not support the route optimization flag.

In step 1005, HSS 1 fails to use the Sponsor IMSI to query the local database and the reason for the failure is an unknown user, but the ULR-Flags carries the support request retry flag and does not support the route optimization flag, and the HSS 1 uses the Sponsor IMSI to initiate a URR query to the EMNP. Request, carry the Sponsor in the URR message IMSI.

In step 1006, the EMNP queries the local database, obtains the redirected IMSI and the redirected address HSS 2 corresponding to the Sponsor IMSI, and returns a URA message to the HSS 1, carrying the translated redirected IMSI and the redirected address HSS2.

In step 1007, the HSS 1 initiates a ULR query to the HSS 2 using the redirected IMSI (ie, the own IMSI) according to the EMNP return result, and carries the Sponsor IMSI and the ULR-Flags, and the ULR-Flags carries the support request retry flag.

In step 1008, the HSS 2 detects that the support request retry flag is carried in the ULR-Flags, and carries the Sponsor IMSI, and the user has previously registered with other MMEs (the HSS records the MME address previously registered by the user), and then uses the Sponsor first. The IMSI initiates a CLR request to the old MME (ie, the registered MME).

In step 1009, the Old MME deletes the original bearer of the user and returns a CLA message to the HSS 2.

In step 1010, HSS 2 queries the local database using own IMSI and returns a ULA message to HSS1.

In step 1011, HSS1 returns a ULA message to the DRA.

In step 1012, the DRA returns a ULA message to the MME.

In step 1013, the MME starts to establish a bearer for the user, and completes the user access operation.

In one embodiment, a non-transitory computer readable storage medium is also provided, stored with computer executable instructions for performing a message routing method in the LTE network described above.

In one embodiment, there is also provided a non-transitory computer readable storage medium storing computer executable instructions for performing the above described message routing method in an LTE network applied to a gateway side.

As shown in FIG. 11 , it is a schematic diagram of a hardware structure of an electronic device according to an embodiment of the present disclosure. As shown in FIG. 11 , the electronic device includes:

A processor 1101 and a memory 1102; may further include a communication interface 1103 and a bus 1104.

The processor 1101, the memory 1102, and the communication interface 1103 can complete communication with each other through the bus 1104. Communication interface 1103 can be used for information transmission. The processor 1101 can invoke logic instructions in the memory 1102 to perform the message routing method in the LTE network of the above embodiments.

In addition, the logic instructions in the memory 1102 described above may be implemented in the form of a software functional unit and sold or used as a stand-alone product, and may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present disclosure may be embodied in the form of a software product stored in a storage medium, including a plurality of instructions for causing a computer device (which may be a personal computer, a server, or a network) The device or the like) performs all or part of the steps of the method described in the embodiments of the present disclosure. The foregoing storage medium may be a non-transitory storage medium, including: a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk. A medium that can store program code, or a transitory storage medium.

As shown in FIG. 12, it is a schematic diagram of a hardware structure of an electronic device according to an embodiment of the present disclosure. As shown in FIG. 11, the electronic device includes:

A processor 1201 and a memory 1202; and may further include a communication interface 1203 and a bus 1204.

The processor 1201, the memory 1202, and the communication interface 1203 can complete communication with each other through the bus 1204. Communication interface 1203 can be used for information transmission. The processor 1201 can call the logic instructions in the memory 1202 to perform the message routing method applied to the LTE network on the gateway side of the above embodiment.

Moreover, the logic instructions in the memory 1202 described above may be implemented in the form of software functional units and sold or used as separate products, and may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present disclosure may be embodied in the form of a software product stored in a storage medium, including a plurality of instructions for causing a computer device (which may be a personal computer, a server, or a network) The device or the like) performs all or part of the steps of the method described in the embodiments of the present disclosure. The foregoing storage medium may be a non-transitory storage medium, including: a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk. A medium that can store program code, or a transitory storage medium.

Finally, it should be understood that those skilled in the art can understand that all or part of the process of implementing the above embodiment method can be completed by executing related hardware by a computer program, and the program can be stored in a non-transitory computer. In reading a storage medium, the program, when executed, may include a flow of an embodiment of the method described above, wherein the computer readable storage medium may be a magnetic disk, an optical disk, a read only memory (ROM), or a random access memory. (RAM), etc.

In the case of no conflict, the technical features of the above-described embodiments may be arbitrarily combined. For the sake of brevity of description, all possible combinations of the technical features in the above embodiments are not described, however, as long as these technical features are There is no contradiction in the combination and should be considered as the scope of this manual.

The above-described embodiments are merely illustrative of alternative embodiments of the present disclosure, but are not to be construed as limiting the scope of the disclosure.

Industrial applicability

The embodiments of the present disclosure provide a message routing method, system, and gateway in an LTE network, which can implement flexible routing and automatic number switching.

Claims

A message routing method in an LTE network, comprising:

The mobile management entity MME of the roaming LTE network sends an access request to the routing proxy node DRA of the international roaming gateway, where the access request carries the source user identifier;

The international roaming gateway DRA locates the first home subscriber server HSS according to the source subscriber identity, and sends a request message to the first HSS, where the request message carries the source subscriber identity, whether the request retry identifier is supported, and whether the support is supported. Route optimization identifier;

If the first HSS finds that the user does not exist after querying the database according to the source user identifier, if the request retry identifier is supported to support the request retry, and the route optimization identifier is supported to support route optimization, The first HSS returns an error code to the international roaming gateway DRA, and carries a support request retry flag and a support route optimization flag;

The international roaming gateway DRA parses the error code, initiates a query request to the EMNP, queries the corresponding target user identifier and the target routing address according to the source user identifier, and uses the target user identifier and the target routing address to re-route The second HSS initiates an access request.
The method according to claim 1, wherein the first HSS initiates a query request to the EMNP if the support request retry identifier is a support request retry, and the support route optimization identifier does not support route optimization, Querying the corresponding target user identifier and the target routing address according to the source user identifier, and re-initiating an access request to the second HSS by using the target user identifier and the target routing address.
The method according to claim 1, wherein if the support request retry identifier does not support request retry, the first HSS returns an error code to the international roaming gateway DRA and carries a non-support request retry flag; The international roaming gateway DRA forwards the response message to the MME, rejecting the current access.
The method of claim 1, wherein the request message is a user authentication request or a location update request.
A message routing system in an LTE network, comprising:

The MME of the roaming LTE network is configured to send an access request to the international roaming gateway DRA, where the access request carries the source user identifier;

The international roaming gateway DRA is configured to locate the 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 the request retry identifier is supported, and whether the route optimization identifier is supported. ;

If the first HSS is configured to query the database according to the source user identifier and find that the user does not exist, if the request retry identifier is supported to support the request retry, and the route optimization identifier is supported to support route optimization, Return an error code to the international roaming gateway DRA, and carry a support request retry flag And support route optimization flags;

The international roaming gateway DRA is further configured to parse the error code, initiate a query request to the EMNP, query the corresponding target user identifier and the target routing address according to the source user identifier, and use the target user identifier and the target routing address. The access request is re-initiated to the second HSS.
The system according to claim 5, wherein the first HSS is further configured to: if the support retry identifier is supported to support request retry, and whether the route optimization identifier is supported to not support route optimization, The EMNP initiates a query request, queries the corresponding target user identifier and the target routing address according to the source user identifier, and uses the target user identifier and the target routing address to re-initiate an access request to the second HSS.
The system according to claim 5, wherein the first HSS is further configured to return an error code to the international roaming gateway DRA and carry the unsupported request if the support retry identifier is not supported for request retry. The international roaming gateway DRA is further configured to forward the response message to the MME, rejecting the current access.
The system of claim 5 wherein the request message is a user authentication request or a location update request.
A message routing method in an LTE network, applied to the network management side, includes:

Receiving an access request sent by the MME of the roaming LTE network, where the access request carries the source user identifier;

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

Receiving an error code returned by the first HSS and parsing the error code, if the error code carries a support request retry flag and a support route optimization flag, initiating a query request to the EMNP, and querying the corresponding according to the source user identifier The target user identifier and the target routing address, and re-initiating an access request to the second HSS using the target user identifier and the target routing address.
The method according to claim 9, wherein if the error code carries the unsupported request retry flag, the response message is forwarded to the MME, and the current access is rejected.
The method of claim 9, wherein the request message is a user authentication request or a location update request.
A gateway for implementing message routing in an LTE network, comprising:

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

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

a parsing module configured to receive an error code returned by the first HSS and parse the error code;

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

Re-accessing the module, configured to re-initiate an access request to the second HSS using the target user identity and the target routing address.
The gateway of claim 12, further comprising:

The response module is configured to: if the error code carries the unsupported request retry flag, forward the response message to the MME, rejecting the current access.
The gateway of claim 12, wherein the request message is a user authentication request or a location update request.
A non-transitory computer readable storage medium storing computer executable instructions for performing a message routing method in an LTE network of any of claims 1-4, 9-11.