CN100356813C - Mobile terminal roaming method based on configuration technology - Google Patents

Abstract

The invention discloses a mobile terminal roaming method based on a configuration technology to solve the problem in the prior art that the mobile terminal is difficult to configure and access after WAP application roams. The method is as follows: constructing a wireless application protocol WAP service domain on the basis of all routing blocks covered by the service support node SGSN; According to the identification numbers of the first SGSN and the second SGSN, it is judged whether the corresponding WAP service domains are the same, and if they are different, it is determined that the location switching of the mobile terminal needs to change the configuration related to the WAP service, and the trusted configuration server TPS according to The identification number of the second SGSN determines the configuration file that should be used and sends it to the mobile terminal, and the mobile terminal modifies the relevant configuration according to the instruction of the configuration file.

Description

A Roaming Method of Mobile Terminal Based on Configuration Technology

technical field

The invention relates to mobile communication technology, in particular to a roaming method of a mobile terminal based on configuration technology.

Background technique

The framework of the Wireless Application Protocol (WAP) includes the access point at the junction of the wireless network and the wired network, as well as the proxy server for accessing different services. It is necessary to correctly set these information on the WAP mobile phone to access the web server on the Internet. . Due to the complexity of correctly setting various access parameters, these settings are often very difficult for users. With the development of mobile data services, if there is no new technology that can help users complete these boring and complicated settings, users will have greater difficulties in using mobile data services. The Open Mobile Alliance (OMA) forum has proposed a provisioning technology for this problem, and using the provisioning technology can help users easily access the network.

The provisioning consists of two independent parts, one part is the bootstrap process (Bootstrap) related to the bearer network, and the other part is the continuous provisioning process (continuous provisioning) independent of the bearer network. The bootstrapping process is used to create a trusted relationship between the mobile terminal device and a trusted provisioning server (TPSTrusted Provisioning server). Bootstrapping is further enhanced by a common continuous configuration process, whereby one or more methods of accessing common WAP proxies can be loaded or managed.

The bootstrapping process is related to the bearer network. Different bearer networks implement bootstrapping in different ways, but the mainstream wireless mobile network technology, whether it is a GSM network or a CDMA network, can complete the bootstrapping process for mobile phones based on the SMS push process. The schematic diagram of this implementation is shown in Figure 1, and its specific process is as follows:

1. After the user applies for and opens the WAP service, the operator's business personnel log in to the Bootstrap Server (Bootstrap Server) in WEB mode through the service desk to operate, and request the Bootstrap Server to push the Bootstrap document to the push (Push) gateway.

2. After receiving the instructions from the business personnel, the Bootstrap server sends a Push submission message to the push gateway through the PAP interface, and the Bootstrap document is included in the message.

3. After the Push gateway receives the message, it pushes the bootstrapping message to the mobile phone through the WAP1.2.x gateway through the non-connection Push.

4. After Wap1.2.x encodes the message, it sends the Bootstrap document to the mobile phone in a connectionless manner carried on the SMS, and the message is first sent to the SMSC. The SMSC sends the message to the mobile phone as a short message.

At present, operators' WAP services are carried out according to their own plans, and generally have the following characteristics:

(1) The WAP gateway and the main application server are distributed on the operator's own data network, and the WAP gateway configurations of each operator are different.

(2) Many operators have deployed their own data service networks. If users want to use corresponding data services, they need to correctly set corresponding parameters in mobile terminals.

(3) The WAP gateway needs to authenticate the user. If the user is not registered at the local WAP gateway, he cannot access the Internet through the WAP gateway.

(4) Many WAP gateways have specific business control capabilities and the ability to provide different services.

It is precisely because of the above characteristics that the roaming of WAP services currently has the following problems:

As shown in Figure 2: the operator's WAP gateways are not interoperable. The mobile phone uses the internal IP address to access the WAP gateway, and then accesses the application server distributed on the private network or accesses the Internet server through the firewall.

To use the WAP service, the user must be able to correctly set the WAP gateway address of the network where it is located, and these gateway addresses may be different. For example, user A is a user of network 1. When the user accesses through network 1, the WAP gateway address on the mobile phone needs to be set to 10.25.1.1 to use the WAP service. If he roams to network 2, since the WAP service of network 2 must pass through WAP gateway 2, the user must change the address of the WAP gateway on the mobile phone to 10.25.1.2.

But in many cases, users don't know whether and how to change the WAP service configuration of their mobile phones. Although the provisioning technology can help users complete service configuration to a certain extent, it still cannot trigger and manage the configuration of mobile terminals conveniently after users roam, nor can it solve the current situation of WAP application access difficulties after roaming.

Contents of the invention

The invention provides a mobile terminal roaming method based on provisioning technology to solve the problem in the prior art that the mobile terminal is difficult to configure and access after WAP application roams.

In order to solve the above problems, the present invention provides the following technical solutions:

A roaming method of a mobile terminal based on configuration technology, constructing a wireless application protocol WAP service domain on the basis of all routing blocks covered by a service support node SGSN, and the mobile terminal is switched from the coverage area of the first GPRS SGSN to the second SGSN The location information is updated when the coverage area is covered; the method also includes the following steps after updating the location information:

A. Judging whether the corresponding WAP service domains are the same according to the identification numbers of the first SGSN and the second SGSN, if not, then determine that the location switching of the mobile terminal needs to change the configuration related to the WAP service, and continue to step B; If they are the same, end the location update process;

B. The trusted configuration server TPS determines the configuration file that should be used according to the identification number of the second SGSN, and sends the configuration file to the mobile terminal;

C. The mobile terminal changes the relevant configuration according to the instructions in the configuration file, and ends the location update procedure.

According to the method above:

In step A, judge whether the corresponding WAP service domains are the same according to the identification numbers of the first SGSN and the second SGSN by the home location register HLR, and when the judgment result is not the same, determine that the mobile terminal needs to change the configuration relevant to the WAP service, And send the request message of updating mobile terminal configuration to TPS; Or, in step A, send the message that mobile terminal changes SGSN to TPS by the second SGSN, TPS judges according to the first SGSN carried in this message and the identification number of the second SGSN Whether the corresponding WAP service domains are the same.

The present invention manages the roaming of the user's mobile data service based on the WAP service domain. When the location of the mobile terminal is updated, the HLR or TPS is automatically triggered to check whether the WAP service domain of the mobile terminal needs to be updated. If so, the TPS starts the Provisioning process to update the mobile terminal. configuration file. There is no need for users to manually configure new parameters, nor for network maintainers to manually trigger the configuration update process. This method can bring flexibility in networking and avoid the trouble of reconfiguring services for users and network maintainers due to flexible networking.

Description of drawings

Fig. 1 is a mobile terminal configuration (Provisioning) flowchart;

FIG. 2 is a schematic diagram of WAP domain update caused by mobile terminal location update;

FIG. 3 is a flow chart of trigger configuration in Embodiment 1;

FIG. 4 is a flow chart of the trigger configuration in the second embodiment.

Detailed ways

Due to the diversity of data services, with the development of mobile data services, many different mobile data service subnetworks will appear, and these networks may have different access gateway addresses, WAP gateway addresses, application ports, security requirements, etc. ; On the other hand, the user's mobile living space is divided according to the region, and most mobile networks are distributed and managed according to the region accordingly. Therefore, it is reasonable to believe that in the future, all kinds of mobile data subnets will be divided by region as the standard will account for the vast majority. Since the mobile network has already provided a good mechanism for obtaining regional information, in view of this development trend, combined with the existing technology of the mobile network and the existing WAP technology, the present invention proposes a roaming method for mobile terminals based on provisioning technology .

Before explaining this method, define a basic concept used in this article: WAP service domain. A WAP service domain refers to a uniformly deployed WAP service network. Mobile terminals do not need to change configurations related to WAP services when roaming in this domain, such as access network address, WAP gateway address, and application port allocation. Mobile terminals use the same settings. To access related services in this domain. When the mobile terminal roams across different WAP service domains, it is necessary to readjust relevant parameters based on the WAP application.

In the existing wireless technology, when the mobile terminal switches from the coverage area of the first GPRS Service Support Node (SGSN) to the coverage area of the second SGSN, the second SGSN will report the location update information to the Home Location Register (HLR), The information mainly includes information such as the identification number (ID) of the second SGSN, the address of the second SGSN, and the IMSI. After the location information is updated, the present invention judges whether the location switching of the mobile terminal needs to change the configuration related to the WAP service, and if so, starts a configuration update process to update the configuration of the mobile terminal, otherwise it is not necessary to start a configuration update process .

Whether different SGSNs belong to the same WAP service domain is configured and defined by the operator according to the current networking situation, and then the corresponding relationship between the WAP service domain and the identification numbers of all SGSNs in the service domain is established and stored in the database. The way of defining the WAP service domain is based on the premise given above, that is, the mobile data subnet owned by the operator is divided according to the region. Mobility management can be based on cells, routing areas and routing area groups covered by the SGSN. The WAP service domain cannot be too small, and it is not appropriate to use a small area as a benchmark. There are also some problems with a routing area as a benchmark, because on the one hand, the routing area can be large or small, so it is difficult to grasp the size of the WAP service domain. On the other hand, the concept of routing area is relatively Abstraction is difficult for managers to maintain, so it is best to build WAP service domains based on all routing blocks covered by SGSN. Existing mobile networks have established corresponding mobility management procedures based on SGSN, and most operators are more concerned about roaming issues based on SGSN services, so it is reasonable to build WAP service domains based on SGSN.

The present invention can judge whether the location switching of the mobile terminal needs to change the configuration related to the WAP service through the HLR or the TPS, which will be explained separately below.

Embodiment one:

Define the WAP domain in HLR, let HLR judge whether this time position switching of mobile terminal needs to change the configuration relevant with WAP service, if necessary, then HLR sends mobile terminal configuration update request message to trusted configuration server (TPS), this The message contains the IMSI of the mobile terminal and the identifier of the WAP service domain to which the new SGSN of the mobile terminal belongs. The second SGSN and the first SGSN belong to different WAP service domains, and a configuration update process is started through the PPG.

Referring to Fig. 2, according to the network planning, the area covered by SGSN11 and SGSN12 is defined as WAP service domain 1 in the HLR, and the area covered by SGSN21 and SGSN22 is WAP service domain 2. If the user roams between SGSN11 and SGSN12, or between SGSN21 and SGSN22, there is no need to change the relevant configuration of the WAP service, that is, it is not necessary to start a configuration update process.

Referring to Figure 3, the process of triggering configuration when the mobile terminal roams is as follows:

1. The operator has divided the WAP service domain according to the mobile data service network configuration. SGSN11 and SGSG12 belong to WAP service domain 1, and SGSN21 and SGSN22 belong to WAP service domain 2. The information of the WAP service domain to which the SGSN belongs is stored in the database of the HLR.

2. When the mobile terminal roams from the area covered by the first SGSN to the area covered by the second SGSN, it sends a Routing Area update request to the second SGSN, which contains the following parameters: the old routing area identifier RAI, the old packet Mobile Subscriber Temporary Identity Code P-TMSI, Global Cell Identity Code GCID, etc.

3. The second SGSN can know the address of the first SGSN according to the P-TMSI in the received message, so the second SGSN immediately sends a SGSN context request message, requesting the user to save the context in the first SGSN, which will contain the parameter old RAI , the old P-TMSI, the address of the second SGSN.

4. After the first SGSN judges that the user is a legitimate user, it sends an SGSN context Response message to the second SGSN, and the message passes the user's context to the second SGSN.

5. After successfully obtaining the context information and data of the user, the second SGSN sends an Update Location message to the Home Location Register (HLR), notifying the HLR that the mobile terminal has successfully completed the location update. The information contained in this message includes: IMSI, the address of the second SGSN, the identification number of the second SGSN and other parameters.

6. After receiving the information, the HLR sends an Update Location Ack message to the second SGSN for confirmation, and the main parameter in the message is the IMSI of the mobile terminal.

7. After updating the parameters in the HLR, the second SGSN responds to the mobile phone with a Routing Area update accept message, which carries the newly allocated P-TMSI, and the mobile terminal completes the location update.

8. After the HLR sends the Update Location Ack message, it checks whether the WAP domain of the mobile terminal is updated, and if so, sends a MS Configuration Update message to the TPS server, which contains the new WAP domain identifier and the mobile terminal IMSI.

9. After receiving the MS Configuration Update message, the TPS server responds with MS Configuration Update Ack to confirm receipt of the MS Configuration Update message.

10. The TPS server decides which configuration file to use according to the WAP domain identifier and mobile terminal information. The TPS takes out the corresponding configuration file and sends it to the mobile terminal through the PPG and WAP gateway in push mode. The push message carries instructions to update the configuration of the mobile terminal. The message Configuration Update for the file.

11. After receiving the Configuration Update message, the mobile terminal takes out the new configuration file and modifies the corresponding configuration according to the requirements of the configuration file. As shown in Figure 2, if the mobile terminal changes from WAP service domain 1 to WAP service domain 2, the mobile terminal The terminal will change the address of the WAP gateway from 10.25.1.1 to 10.25.1.2 according to the instructions in the configuration document.

12. After the mobile terminal successfully modifies the configuration, it notifies the TPS server with Configuration Success Indication. If the TPS does not receive the ConfigurationSuccess Indication message returned by the mobile terminal within the specified time, it will resend it.

In the above process, a new interface is added between the HLR and the TPS server. When the HLR judges that the location update of the mobile terminal results in an update of the WAP service domain, the HLR sends a MS ConfigurationUpdate message to the TPS server through this interface, and the message contains the new WAP domain identifier. and the mobile terminal IMSI; the TPS determines the corresponding configuration file according to the new WAP service domain identifier and the mobile terminal IMSI, and then sends the configuration file to the mobile terminal through the provisioning mechanism. For the provisioning mechanism, see Figure 1 and the technical background description. Other interfaces are interfaces provided by the prior art.

Embodiment two:

The WAP service domain has been defined in the TPS. When the mobile terminal switches from the coverage area of the first GPRS service support node (SGSN) to the coverage area of the second SGSN, the second SGSN will report the HLR location update information, which mainly includes the first Information such as the identification number (ID) of the second SGSN, the address of the second SGSN, and the IMSI. After the second SGSN sends this message, that is, after the location update is completed, it sends a specific short message to the short message gateway (SMSC) through the interface, and the SMSC uses the existing SMPP interface to transparently transmit this message to the WAP gateway, and the WAP gateway After receiving the specific message, pass the content carried in the message to the trusted configuration server (TPS) through the HTTP protocol, and the trusted configuration server judges whether it needs Start a continuous configuration process, the judgment criteria are as follows: if the second SGSN and the first SGSN belong to the same WAP service domain, it is not necessary to start a configuration update process; if the second SGSN and the first SGSN belong to different WAP service domains, then Initiate a configuration update process through PPG.

Referring to Figure 2, according to the networking plan, the area covered by SGSN11 and SGSN12 is defined as WAP service domain 1 in the TPW, and the area covered by SGSN21 and SGSN22 is WAP service domain 2. If the user roams between SGSN11 and SGSN12, or between SGSN21 and SGSN22, there is no need to change the relevant configuration of the WAP service, that is, it is not necessary to start a configuration update process.

Referring to Figure 4, the process of triggering configuration when the mobile terminal roams is as follows:

1. When the mobile terminal roams from the area covered by the first SGSN to the area covered by the second SGSN, it sends a Routing Area update request to the second SGSN, which contains the following parameters: the old routing area identifier RAI, the old packet Mobile Subscriber Temporary Identity Code P-TMSI, Global Cell Identity Code GCID, etc.

2. The second SGSN can know the address of the first SGSN according to the P-TMSI in the received message, so the second SGSN immediately sends a SGSN context request message, requesting the user to save the context in the first SGSN, which will contain the parameter old RAI , the old P-TMSI, the address of the second SGSN.

3. After the first SGSN judges that the user is a legitimate user, it sends an SGSN context Response message to the second SGSN, and this message transfers the user's context to the second SGSN.

4. After successfully obtaining the context information and data of the user, the second SGSN sends an Update Location message to the Home Location Register (HLR), notifying the HLR that the mobile terminal has successfully completed the location update. The information contained in this message includes: IMSI, the address of the second SGSN, the identification number of the second SGSN and other parameters.

5. After receiving the information, the HLR sends an Update Location Ack message to the second SGSN for confirmation, and the main parameter in the message is the IMSI of the mobile terminal.

6. After updating the parameters in the HLR, the second SGSN responds to the mobile phone with a Routing Area update accept message, which carries the newly allocated P-TMSI, and the mobile terminal completes the location update.

7, the second SGSN, after accepting the location update of the mobile terminal, generates a WAP service configuration update request message and constructs a short message, then sends it to the short message gateway (SMSC) by the ForwardShortMessage MO SMS message of the Gd interface.

The short message at least includes: message code, MSISDN number of the mobile terminal, IP address of the second SGSN, identification number of the second SGSN, IP address of the first SGSN, identification number of the first SGSN.

The message code is a specific message code, indicating that it is a message to inform the mobile terminal to change the SGSN.

The destination address for sending the short message is the WAP gateway. The reason why the message is sent to the WAP gateway is to utilize the existing SMPP protocol, and the TPS server does not need to increase the interface with the short message gateway SMSC.

8. SMSC responds with ForwardShortMessage MO SMS after receiving the short message sent by the second SGSN.

9. The SMSC sends this message to the WAP gateway through the message Data submit in the SMPP protocol.

10. The WAP gateway confirms with the message Data submit Ack in the SMPP protocol.

11. The WAP gateway receives the message, and extracts the content contained in the short message. It can extract the following information from it: message code (indicating that the message is a WAP service configuration update request message), change the mobile terminal MSISDN number of SGSN, the IP address of the second SGSN, the identification number of the second SGSN, the IP of the first SGSN Address, identification number of the first SGSN, etc. The WAP gateway extracts these information, and then carries them in the HTTP get request and sends them to the TPS server.

12. After receiving the request message, the TPS server responds with an http response.

13. The TPS server processes the message. It first analyzes whether the areas covered by the second SGSN and the first SGSN belong to the same WAP service domain, that is, judges whether the location switching of the mobile terminal needs to change the configuration related to the WAP service.

If the areas covered by the second SGSN and the first SGSN belong to the same WAP service domain, the TPS does not start the subsequent configuration update process. For example, the second SGSN is SGSN11, and the first SGSN is SGSN12, both of which belong to the same WAP service domain 1.

If the areas covered by the second SGSN and the first SGSN do not belong to the same WAP service domain, the TPS starts the following configuration update process. TPS finds out its corresponding WAP service domain according to the second SGSN ID number, as shown in Figure 2, assuming that the second SGSN is SGSN21 and the first SGSN is SGSN11, then the TPS server analyzes and knows that the user has switched from WAP service domain 1 to WAP service domain 2, so it calls out the configuration file of WAP service domain 2 stored in the database for encoding, and submits it to the push gateway PPG through the Push Submit message of the PAP interface. The message includes information such as the MSISDN of the mobile terminal, priority and time for PPG scheduling, and configuration files. Since this message carries configuration information, it should be given the highest priority.

14. After receiving the message submitted by the TPS, the PPG responds with the message Push Submit response.

15. The PPG dispatches this message first, and submits it to the WAP gateway through the message Po UnitPush. The message contains the configuration file and the MSISDN of the mobile terminal.

16. After the WAP gateway performs binary encoding on the message, it submits the message Datasubmit to the SMSC through the SMPP protocol.

17. SMSC responds with the message Data submit response after receiving the message.

18. The SMSC sends the SM Delivery attempt (WSP Push) message to the mobile terminal.

19. After successful reception, the mobile terminal responds to SMSC with SM Delivery Ack.

20. The mobile terminal takes out the provisioning configuration file in the SMS, and changes the relevant configuration according to the instruction of the configuration file. As shown in Figure 2, if the mobile terminal changes from WAP service domain 1 to WAP service domain 2, the mobile terminal will change the address of the WAP gateway from 10.25.1.1 to 10.25.1.2 according to the instruction of the configuration document.

The present invention proposes the concept of WAP service domain, and divides the WAP service domain through the coverage area of SGSN to manage the roaming of the user's mobile data service. When the location of the mobile terminal is updated, HLR or TPS is automatically triggered to check whether the WAP service domain of the mobile terminal needs Update, TPS starts the Provisioning process when an update is required, updating the configuration file of the mobile terminal does not require the user to manually configure new parameters, nor does the network maintainer need to manually trigger the configuration update process. This method can not only bring flexibility in networking, but also avoid the trouble of reconfiguring services for users and network maintainers due to flexible networking.

Claims (7)

1. A roaming method of a mobile terminal based on configuration technology, constructing a wireless application protocol WAP service domain based on all routing areas covered by a service support node SGSN, and switching the mobile terminal from the coverage area of the first GPRS SGSN to the first GPRS SGSN Update location information during the coverage area of two SGSN; It is characterized in that, also comprise following steps after updating location information: A. Judging whether the corresponding WAP service domains are the same according to the identification numbers of the first SGSN and the second SGSN, if not, then determine that the location switching of the mobile terminal needs to change the configuration related to the WAP service, and continue to step B; If they are the same, end the location update process; B. The trusted configuration server TPS determines the configuration file that should be used according to the identification number of the second SGSN, and sends the configuration file to the mobile terminal; C. The mobile terminal changes the relevant configuration according to the instructions in the configuration file, and then ends the location update procedure. 2. The method according to claim 1, characterized in that, in step A, the home location register (HLR) judges whether the corresponding WAP service domains are the same according to the identification numbers of the first SGSN and the second SGSN, and if the judgment result is not At the same time, it is determined that the mobile terminal needs to change the configuration related to the WAP service, and sends a request message for updating the configuration of the mobile terminal to the TPS. 3. The method according to claim 1, wherein in step A, the second SGSN sends a message to the TPS that the mobile terminal changes the SGSN, and the TPS uses the identification numbers of the first SGSN and the second SGSN carried in the message to It is judged whether the corresponding WAP service domains are the same. 4. The method according to claim 3, characterized in that, the second SGSN sends the message of changing the SGSN of the mobile terminal to the TPS comprising the steps of: The second SGSN structure indicates that the mobile terminal changes the short message of the SGSN and sends it to the short message gateway; The short message gateway submits the received short message to the WAP gateway; The identification numbers of the first SGSN and the second SGSN are extracted from the short message by the WAP gateway and sent to the TPS. 5. The method according to claim 2, 3 or 4, wherein step B comprises the steps of: (1) The TPS calls out the configuration file corresponding to the WAP service domain where the second SGSN is located according to the identification number of the second SGSN; (2) Encoding the configuration file, packaging it into a short message and sending it to the mobile terminal. 6. The method according to claim 5, characterized in that step (2) comprises the following steps: Encode the configuration file and send it to the push gateway; The push gateway submits the message including the configuration file and the mobile terminal number to the WAP gateway; The received message is encapsulated into a short message by the WAP gateway and sent to the short message gateway, and then delivered to the mobile terminal by the short message gateway. 7. The method according to claim 2, 3 or 4, characterized in that the corresponding relationship between the WAP service domain and all SGSNs in the domain is configured in the HLR or TPS.

Images