WO2012034390A1

WO2012034390A1 - Method and system for configuring wireless terminal

Info

Publication number: WO2012034390A1
Application number: PCT/CN2011/072115
Authority: WO
Inventors: 吴贤波
Original assignee: 中兴通讯股份有限公司
Priority date: 2010-09-17
Filing date: 2011-03-24
Publication date: 2012-03-22
Also published as: CN101945360A; CN101945360B

Abstract

A method and system for configuring a wireless terminal are disclosed by the present invention, which relates to the field of mobile communications. The method includes: when an over-the-air pre-configuration service server (OTAPS) receives a configuration result message returned by a mobile terminal, the OTAPS extracts the message identifier of the configuration result message; the OTAPS compares the extracted message identifier with that of a stored configuration short message; when there is a message identifier matched with the extracted message identifier, it is determined that the configuration is successful and the configuration result is recorded. The technical solutions provided by the present invention are applied for configuring parameters in a mobile terminal, thus solving the problem that the performing result of configuration can not be acquired.

Description

Wireless terminal configuration method and system

Technical field

The present invention relates to the field of mobile communications, and in particular, to a wireless terminal configuration method and system.

Background technique

With the continuous advancement of technology and the continuous development of information technology, especially with the development of wireless communication and network technology, the intelligence of wireless networks and wireless terminals is becoming higher and higher, and the penetration rate is getting higher and higher. In this case, a service for configuring the parameters of the mobile phone through the air interface comes into being, that is, the OTA Provisioning Service (OTPAS), which can provide necessary settings for the terminal to access the network service, such as connection. Information and application information, facilitating the use of services and applications for the average user.

However, during the current OTAPS process, the specific implementation of the configuration cannot be known, and the configuration failure cannot be discovered in time. Summary of the invention

The present invention provides a method and system for configuring a wireless terminal, which solves the problem that the specific execution cannot be configured.

A wireless terminal configuration method includes:

When receiving the configuration result message returned by the mobile terminal, the OTAPS extracts the message identifier of the configuration result message;

The OTAPS compares the message identifier with the stored message identifier of the configuration short message; when there is a message identifier that matches the message identifier, the configuration is considered successful, and the configuration result is recorded.

Preferably, after the step of comparing, by the OTAPS, the message identifier with the stored message identifier of the configuration short message, the method further includes:

When there is no message identifier matching the message identifier, the configuration is considered to be failed, and the record is recorded. Configuration results.

Preferably, before the step of extracting the message identifier of the configuration result message, when the OTAPS receives the configuration result message returned by the mobile terminal, the method further includes:

The OTAPS sends a configuration short message to a short message center (SMSC) via a short message interface machine (IM);

The IMP receives the confirmation short message returned by the SMSC, and merges the multiple acknowledgement short messages into a configuration confirmation message, and sends the configuration confirmation message to the OTAPS, where the configuration confirmation message carries the message identifier of each configured short message. And the OTAPS extracts and saves the message identifier of the configuration short message from the configuration confirmation message.

Sending, by the SMSC, the configuration short message to the mobile terminal;

After the configuration is completed, the mobile terminal returns a configuration result message to the SMSC; the SMSC sends a configuration result short message to the OTAPS via the IMP.

Preferably, the step of the SMSC sending the configuration result short message to the OTAPS via the IMP includes:

The SMSC extracts a message identifier and a configuration result from the configuration result message; and generates a success status code according to the configuration result;

Sending, by the SMSC, the message identifier and the success status code to the IMP in the form of an IMP message body;

The IMP extracts the message identifier from the received IMP message body, and sends a configuration result short message to the OTAPS, where the message identifier is carried in the configuration result short message.

Preferably, the step of the OTAPS sending a configuration short message to the SMSC via the IMP includes: the OTAPS sending an IMP message body to the IMP, where the IMP message body carries configuration information, where the configuration information is specifically the network management of the OTAPS. The parameter and the network link address, and the wireless access number of the wireless terminal of the user that is itself saved; The IMP converts the IMP message body, and splits the converted IMP message body into a plurality of configuration short messages, and sends the message to the SMSC;

The SMSC sends the configuration short message to a corresponding mobile terminal.

The present invention also provides a wireless terminal configuration system, including OTAPS;

The OTAPS is configured to: when receiving a configuration result message returned by the mobile terminal, extract a message identifier of the configuration result message, compare the message identifier with a stored message identifier of the configuration short message, and presence and the message identifier When the matching message is identified, the configuration is considered successful and the configuration result is recorded.

Preferably, the OTAPS is further configured to: when there is no message identifier matching the message identifier, consider that the configuration fails, and record the configuration result.

Preferably, the wireless terminal configuration system further includes an IMP and an SMSC;

The IMP is configured to: receive the confirmation short message returned by the SMSC, and merge the multiple confirmation short messages into a configuration confirmation message, and send the configuration confirmation message to the OTAPS, where the configuration confirmation message carries each configuration short message. Message identifier

The OTAPS is further configured to: extract and save the message identifier of the configuration short message from the configuration confirmation message.

Preferably, the SMSC is configured to: send the configuration short message to the mobile terminal, receive a configuration result message returned by the mobile terminal after the configuration is completed, and send a configuration result short message to the OTAPS via the IMP.

Preferably, the OTAPS is further configured to: send a configuration short message to the SMSC via the IMP;

The IMP is further configured to: convert the IMP message body, split the converted IMP message into a plurality of configuration messages, and send the message to the SMSC.

The wireless terminal configuration method and system provided by the present invention, when receiving the configuration result message returned by the mobile terminal, the OTAPS extracts the message identifier of the configuration result message, and the OTAPS will cancel the message. The information identifier is compared with the message identifier of the stored configuration message, and when the message identifier matching the message identifier exists, the configuration is considered successful, and the configuration result is recorded, and the operator can learn the configuration result from the OTAPS-side. I am unable to know the specific implementation of the configuration. BRIEF abstract

1 is a flowchart of a method for configuring a wireless terminal according to Embodiment 1 of the present invention; FIG. 2 is a specific flowchart of step 101 in FIG.

3 is a flowchart of a wireless terminal configuration method according to Embodiment 2 of the present invention; FIG. 4 is a schematic structural diagram of a wireless terminal configuration system according to an embodiment of the present invention; FIG. A schematic structural diagram of a wireless terminal configuration system provided by the example. Preferred embodiment of the invention

In order to solve the problem that the configuration specific implementation cannot be known, the present invention provides a wireless terminal configuration method.

First, the first embodiment of the present invention will be described.

As shown in FIG. 1 , an embodiment of the present invention provides a method for configuring a wireless terminal, and the process for completing the configuration by using the method includes:

Step 101: The OTAPS sends a configuration short message to the SMSC via the IMP.

This step is specifically shown in Figure 2, including:

Step 1011: The OTAPS sends an IMP message body to the IMP, where the IMP message body carries configuration information.

In this step, the OTAPS module or the OTAPS of the network management platform generates an IMP-recognizable IMP message body to the IMP according to its own network management parameters and the network link address, and the configuration information of the wireless access number of the wireless terminal of the user.

Step 1012: The IMP converts the IMP message body, and splits the converted IMP message body into a plurality of configuration short messages, and sends the message to the SMSC. In this step, specifically, the IMP performs message conversion according to the message body parameter of the IMP message body (for example, converts the hexadecimal IMP message body into a decimal message body), and converts the converted IMP message according to the length of the short message. Split into multiple configuration SMS messages and send them to the SMS center. For example, if the general length of the short message is 140 bytes or less, the converted IMP message body is divided into a plurality of configuration short messages in units of 140 bytes.

Step 1013: The SMSC sends the configuration short message to the corresponding mobile terminal. In this step, the SMSC sends the configuration short message to the corresponding terminal according to the wireless terminal wireless access number in each of the configured short messages.

Step 102: The IMP receives the confirmation short message returned by the SMSC, and merges the multiple confirmation short messages into a configuration confirmation message, and sends the configuration confirmation message to the OTAPS, where the configuration confirmation message carries each configuration short message. Message identifier

In this step, specifically, after receiving the configuration short message, the SMSC separately generates a confirmation short message corresponding to each configuration short message (where there is a unique identifier messagelD for each configured short message, which is generated by the SMSC and assigned to the configuration short message), The confirmation message is sent to the IMP. The IMP receives multiple confirmation messages and merges them, and returns a reply configuration confirmation message obtained after the combination to the OTAPS module or OTAPS of the network management platform. For example, the message1D of the three configuration short messages is messagelD 1=1111, messageID2=2222, and messageID3=3333, and the configuration confirmation message obtained after the combination carries the messagelD of each configuration short message in the form of 111122223333.

It is to be noted that, as the IMP obtains the configured short message, the unique identifier of each configuration short message is assigned, and the unique identifiers of the multiple configuration short messages belonging to the same IMP message body are divided into a memory and saved, because the SMSC is configured. The messagelD of the SMS confirmation message is associated with the content of the configuration message. Therefore, when the IMP receives the confirmation message, the message identifies that the message identifier matches the corresponding unique identifier, and the unique identifiers belonging to the same IMP message body are matched. In the case of the corresponding messegelD, all the acknowledgement messages corresponding to the IMP message body are combined to obtain a configuration confirmation message.

Step 103: The OTAPS extracts and saves a message identifier of the configuration short message from the configuration confirmation message.

In this step, the OTAPS module or OTAPS in the network management platform extracts all the extracted messagelD is saved to the local database.

Step 104: The SMSC sends the configuration short message to the mobile terminal.

Step 105: After the configuration is completed, the mobile terminal returns a configuration result message to the SMSC.

In this step, the wireless terminal receives the configuration short message, that is, configures the service according to the content of the configured short message, and automatically returns a configuration result message to the SMSC, where the message carries the messageID.

Step 106: The SMSC sends the configuration result message to the OTAPS via the IMP.

In this step, the SMSC processes the received configuration result message, extracts the message identifier message1D and generates a success status code, and sends the messagelD and the success status code to the IMP in the form of an IMP message body. The success status code is generated by the SMSC, indicating the configuration execution result of the terminal, and each IMP message body carries the configuration result of one terminal.

After receiving the IMP message body, the IMP extracts the message1D from it, constructs a short message of the configuration result, carries messagelD in the short message, and returns the configuration result message to the OTAPS module or OTAPS of the network management platform.

Step 107: When receiving the configuration result message returned by the mobile terminal, the OTAPS extracts the message identifier of the configuration result message.

Step 108: The OTAPS compares the message identifier with a message identifier of the stored configuration SMS message;

Step 109: When there is a message identifier that matches the message identifier, the configuration is considered to be successful, and the configuration result is recorded;

Step 110: When there is no message identifier matching the message identifier, the configuration is considered to be failed, and the configuration result is recorded.

Embodiment 2 of the present invention will be described below with reference to the accompanying drawings.

A second embodiment of the present invention provides a method for configuring a wireless terminal. In the embodiment of the present invention, a service configuration is taken as an example for description. The process of completing the configuration using this method is shown in Figure 3, including: Step 301: After the MMS service is triggered, the terminal information (mobile number, imei (mobile phone), imsi (mobile phone card), etc.) is sent to the OTAPS regardless of the trigger condition.

The MMS service needs to be configured first, which can be triggered by the operator interface, which can be triggered by the terminal SMS, or it can be triggered automatically by the system.

Step 302: The OTAPS stores mobile phone information (mobile phone manufacturer, model, supported service, etc.), queries according to the terminal information sent, and extracts the mobile phone information to determine whether the mobile phone supports the MMS.

Step 303: Support MMS, and OTAPS obtains a template from the database and performs content encoding according to the user information. The template is as follows:

<?xml version=" 1.0" encoding="UTF-8" ?>

<!DOCTYPE wap-provisioningdoc (View Source for full doctype...)> - <wap-provisioningdoc>

- CHARACTERISTIC TYPE="BOOTSTRAP">

</CHARACTERISTIC>

- CHARACTERISTIC TYPE="PXLOGICAL">

- CHARACTERISTIC TYPE="PXPHYSICAL">

- CHARACTERISTIC TYPE="PORT">

</CHARACTERISTIC> </CHARACTERISTIC>

</CHARACTERISTIC>

- CHARACTERISTIC TYPE="NAPDEF">

</CHARACTERISTIC>

- CHARACTERISTIC TYPE="APPLICATION">

- CHARACTERISTIC TYPE="RESOURCE">

</CHARACTERISTIC>

- CHARACTERISTIC TYPE="APPLICATION">

</wap-provisioningdoc>

Step 304: Add a multimedia message template to the content of the IMP message body, and the basic parameters are compiled and sent to the IMP;

The message body format is as follows:

Typedef struct

UINT8 sdshead[10];// message SIB header structure

smsImHead T imHead; II interactive header structure

UINT8 SrcTermId[cmppLenTermId_N]; II source number, empty is the configuration source number

UINT8DestTermId[cmppLenTermId_N] ; 11 destination number

UINT8RegDelivery;//Requires a return status report

UINT8MsgFmt; II information format: 0 - ASCII, 8 - Unicode, 15 - GB, 16 - UTF-8

UINT8host[150]; //SMS center host, format: IP + Port, automatic selection when empty (multi-ISMG support)

UINT32 content— len; // message body length

UINT8isFormat; //Do you need to convert the character set: 1 - Convert to Unicode (MsgFmt is 8 after the conversion is successful, UTF8->Unicode when MsgFmt=16)

// 2 - Convert to the specified character set (according to the configuration item CodePage)

UINT81ongMsg; II indicates that the content of the SMS is sent several times: 0 - no specified, 250 - WapPush SMS (starting from url on content[0], loading the content of wappush message from content[500])

UINT8SegMsgLen; //SMS split length (not greater than 134): 0 - not specified

// LBA project support: need to transparently communicate protocol related fields

UINT8MsgID[cmppLenMsgId_N]; //Information ID: Invalid when PkTotal is 0 UINT8PkTotal;〃 Same Msg— Id number of pieces: 0 - Not specified

UINT8PkNumber; // Same Msg - Id serial number: 0 - not specified UINT8MsgLevel; //Information level: 255 - Do not specify

UINT8SerId[10]; //Business Type: Empty means not specified

UINT8Fee_UserType; / / billing user type: 255 - do not specify

UINT8Fee_TermID[cmppLenTermId_N];//Accounting User Number: Empty means not specified

UINT8 Fee— TermiType; //Type of billable user: 255 - Not specified

UINT8TP_pId; // GSM protocol type: 255 - not specified

UINT8TP— udhi; // GSM protocol type: 255 - not specified

UINT8MsgSrc[6]; //Source: Empty means not specified

UINT8FeeType[2]; // Tariff category: Empty means not specified

UINT8FeeCode[6]; // Tariff code: Empty means not specified

UINT8ValidTime[17];//survival validity period: empty means no specified

UINT8AtTime[17]; //Timed send time: Empty means not specified

UINT8DestTermType; The type of the user who receives the SMS: 0 - the real number; 1 - the pseudo code, 255 - does not specify

UINT8 content[smsMaxContent_N]; II message body content

} cmpp SubmitReq_T;

Step 305: The IMP receives the message, and converts the message into multiple configuration short messages according to the length of the message, and sends the message to the SMSC.

Step 306: The SMSC receives the configuration short message sent by the IMP, performs processing, and generates a confirmation short message corresponding to the received configuration short message, and returns the confirmation short message to the IMP.

Step 307: The IMP receives the confirmation short message sent by the SMSC, submits the messagelD (message identifier) of each confirmed short message, performs merging (messageDD splicing together), and generates a configuration confirmation message and sends it to the OTAPS.

Step 308: After receiving the confirmation message, the OTAPS extracts all the messagelDs carried in the configuration confirmation message and stores them in the memory. Step 309: At the same time as step 306, the SMSC also sends the configuration short message to the corresponding MS.

Step 310: The MS receives the message and sends a reply confirmation message to the SMSC. At the same time, the MS receives the first message according to the GSM specification (the mobile phone manufacturer message specification), determines that the short message is configured, merges into a configuration message, and installs the multimedia message service. .

Step 311: After the SMSC sorts the returned results of the MS, the status report request and the configuration result are sent to the IMP.

Step 312: The IMP receives the MS return result of the SMSC, performs the collation, and forwards it to the OTAPS. Step 313: The OTAPS receives the returned result of the MS, performs sorting, extracts the message1D and the saved messagelD for comparison, and determines whether the configuration result is successful or failed.

An embodiment of the present invention further provides a wireless terminal configuration system, the structure of which is shown in FIG. 4, including OTAPS401;

The OTAPS 401 is configured to: when receiving a configuration result message returned by the mobile terminal, extract a message identifier of the configuration result message, compare the message identifier with a stored message identifier of the configuration short message, and presence and the message identifier When the matching message is identified, the configuration is considered successful and the configuration result is recorded.

Preferably, the OTAPS 401 is further configured to: when the message identifier that matches the message identifier does not exist, consider that the configuration fails, and record the configuration result.

Preferably, the wireless terminal configuration system, as shown in FIG. 5, further includes an IMP 402 and an SMSC 403. The IMP 402 is configured to receive an acknowledgement message returned by the SMSC 403, and merge the multiple acknowledgement messages into a configuration confirmation message. The OTAPS 401 sends the configuration confirmation message, where the configuration confirmation message carries the message identifier of each configured short message;

The OTAPS 401 is further configured to extract and save the message identifier of the configuration short message from the configuration confirmation message.

Preferably, the SMSC 403 is configured to send the configuration short message to the mobile terminal, receive a configuration result message returned by the mobile terminal after the configuration is completed, and send the configuration result short message to the OTAPS via the IMP 402. Preferably, the OTAPS 401 is further configured to send a configuration short message to the SMSC 403 via the UI 402.

The ΙΜΡ 402 is further configured to convert the ΙΜΡ 402 message, and split the converted ΙΜΡ 402 message body into a plurality of configuration short messages, and send the message to the SMSC 403.

The above-mentioned wireless terminal configuration system can be combined with a wireless terminal configuration method provided by an embodiment of the present invention. When receiving the configuration result message returned by the mobile terminal, the OTAPS extracts the message identifier of the configuration result message, and the OTAPS will The message identifier is compared with the message identifier of the stored configuration message, and when the message identifier matching the message identifier exists, the configuration is considered successful, and the configuration result is recorded, and the operator can know the configuration result from the OTAPS-side. , solved the problem of not knowing the specific implementation of the configuration. The configuration result is recorded to facilitate the statistics of the service success. This helps determine the stability of the system and locates the time when the configuration service fails.

It will be understood by those skilled in the art that all or part of the steps of the above embodiments may be implemented using a computer program flow, which may be stored in a computer readable storage medium, such as on a corresponding hardware platform (eg, The system, device, device, device, etc. are executed, and when executed, include one or a combination of the steps of the method embodiments.

Optionally, all or part of the steps of the foregoing embodiments may also be implemented by using an integrated circuit. These steps may be separately fabricated into individual integrated circuit modules, or multiple modules or steps may be fabricated into a single integrated circuit module. achieve. Thus, the invention is not limited to any particular combination of hardware and software.

The various devices/function modules/functional units in the above embodiments may be implemented using a general-purpose computing device, which may be centralized on a single computing device or distributed over a network of multiple computing devices.

When each device/function module/functional unit in the above embodiment is implemented in the form of a software function module and sold or used as a stand-alone product, it can be stored in a computer readable storage medium. The above mentioned computer readable storage medium may be a read only memory, a magnetic disk or an optical disk or the like. Any changes or substitutions that are readily conceivable within the scope of the present invention are intended to be included within the scope of the present invention. Therefore, the scope of the invention should be determined by the scope of the claims.

Industrial applicability

The wireless terminal configuration method and system provided by the present invention, when receiving the configuration result message returned by the mobile terminal, the OTAPS extracts the message identifier of the configuration result message, and the OTAPS compares the message identifier with the stored message identifier of the configuration short message. If the message identifier matches the message identifier, the configuration is considered successful, and the configuration result is recorded. The operator can know the configuration result from the OTAPS-side, and solve the problem that the configuration cannot be known.

Claims

Claim

1. A wireless terminal configuration method, comprising:

The air pre-configuration service server (OTAPS) extracts the message identifier of the configuration result message when receiving the configuration result message returned by the mobile terminal;

The OTAPS compares the message identifier with the stored message identifier of the configuration short message; and when there is a message identifier matching the message identifier, the configuration is considered successful, and the configuration result is recorded.

The wireless terminal configuration method according to claim 1, wherein after the step of comparing the message identifier with the stored message identifier of the configured short message, the method further includes:

When there is no message identifier matching the message identifier, the configuration is considered to be failed, and the configuration result is recorded.

The method for configuring a wireless terminal according to claim 1, wherein the method further includes: before the step of extracting the message identifier of the configuration result message, when the OTAPS receives the configuration result message returned by the mobile terminal, the method further includes:

The IMP receives the confirmation short message returned by the SMSC, and merges the multiple acknowledgement short messages into a configuration confirmation message, and sends the configuration confirmation message to the OTAPS, where the configuration confirmation message carries the message identifier of each configured short message. ; as well as

The OTAPS extracts and saves the message identifier of the configuration short message from the configuration confirmation message.

The method for configuring a wireless terminal according to claim 1 or 3, wherein, before the step of extracting the message identifier of the configuration result message, the method further includes the step of the OTAPS receiving the configuration result message returned by the mobile terminal, :

Sending, by the SMSC, the configuration short message to the mobile terminal; After the configuration is completed, the mobile terminal returns a configuration result message to the SMSC; and the SMSC sends a configuration result short message to the OTAPS via the IMP.

The wireless terminal configuration method according to claim 4, wherein the sending, by the SMSC, the configuration result short message to the OTAPS via the IMP comprises:

The SMSC extracts a message identifier and a configuration result from the configuration result message;

According to the configuration result, a success status code is generated;

The wireless terminal configuration method according to claim 3, wherein the step of the OTAPS transmitting the configuration short message to the SMSC via the IMP includes:

The OTAPS sends an IMP message body to the IMP, and the IMP message carries the configuration information, where the configuration information is specifically the network management parameter and the network link address of the OTAPS, and the wireless of the wireless terminal of the user that is saved by itself. Access number

The IMP converts the IMP message body, and splits the converted IMP message body into a plurality of configuration short messages, and sends the message to the SMSC;

A wireless terminal configuration system, comprising an air pre-configuration service server (OTAPS); the OTAPS is configured to: when receiving a configuration result message returned by the mobile terminal, extract a message identifier of the configuration result message, and the message is sent The identifier is compared with the message identifier of the stored configuration SMS. When the message identifier matching the message identifier exists, the configuration is considered successful, and the configuration result is recorded.

8. The wireless terminal configuration system according to claim 7, wherein

The OTAPS is further configured to: when there is no message identifier matching the message identifier, the configuration is considered to be failed, and the configuration result is recorded.

9. The wireless terminal configuration system according to claim 7, wherein the system further comprises an SMS interface machine (IMP) and a short message center (SMSC);

10. The wireless terminal configuration system according to claim 9, wherein

The SMSC is configured to: send the configuration short message to the mobile terminal, receive a configuration result message returned by the mobile terminal after the configuration is completed, and send a configuration result short message to the OTAPS via the IMP.

11. The wireless terminal configuration system according to claim 9, wherein

The OTAPS is further configured to: send a configuration short message to the SMSC via the IMP; the IMP is further configured to: convert the IMP message body, and split the converted IMP message body into multiple configuration short messages. Is sent to the SMSC.