CN100421521C - A Security-Based User Plane Mobile Location Method - Google Patents

Abstract

The present invention discloses a security-based user plane mobile positioning method. The method provided by the present invention can support two or more requesting parties by extending the requesting party identification in the positioning request message, and the H-SLP After receiving the positioning request message sent by the SUPL agent, the requester ID that needs to be confirmed or notified to the target SET is carried in the SUPL initialization message and sent to the target SET, and the requester ID authorized by the target SET will be obtained after the positioning is completed. Sending to the SUPL agent achieves the purpose of improving the positioning efficiency when multiple requesters need to obtain the location information of the target SET at the same time, and saves network resources at the same time.

Description

A Security-Based User Plane Mobile Location Method

technical field

The invention relates to the field of user plane mobile location services, in particular to a security-based user plane mobile positioning method initiated by a network.

Background technique

At present, the International Open Mobile Alliance (OMA, Open Mobile Alliance) has formulated a positioning process for SUPL Terminals (SET, SUPL Enabled Terminal) in its Secure User Plane Location (SUPL, Secure User Plane Location) protocol. Among them, in the location process initiated by the network, the mobile location service (MLS, Mobile LocationService) application on the network side sends a location request to the target SET by a requesting party to the SUPL location platform (SLP, SUPL LocationPlatform) through the SUPL agent, and then The SLP performs relevant authentication on the requester according to the privacy setting of the target SET, and sends the location information of the target SET obtained during the positioning process to the requester after passing the authentication.

A typical network-originated positioning process is shown in Figure 1, which mainly includes the following steps:

Step 101: the MLS application on the network side sends a Mobile Location Protocol (MLP, Mobile Location Protocol) Immediate Location Request (SLIR, Standard Location Immediate Request) message to the SLP (H-SLP, Home SLP) to which the target SET belongs through the SUPL agent, the The MLPSLIR message carries the requester ID (Requestor-ID) and the initiator client ID (Client-ID).

Here, the requester ID can only represent one requester, and the requester refers to the Mobile Station Integrated Services Digital Network (MSISDN, Mobile Station Integrated Service Digital Network) number, Uniform Resource Locator (URL, Uniform ResourceLocator) that needs to obtain the location information of the target SET wait.

Step 102: After receiving the MLP SLIR message, the H-SLP judges according to the privacy setting information of the target SET whether the requester corresponding to the requester ID can directly obtain the authorization of the target SET, or needs to confirm or notify the target SET, or directly If it is rejected by the target SET, if the authorization of the target SET can be directly obtained, go to step 104; if it needs to be confirmed or notified to the target SET, go to step 103; if it is directly rejected by the target SET, go to step 112.

The privacy setting information of the target SET is stored in the privacy checking entity. After receiving the MLPSLIR message, the H-SLP queries the privacy checking entity for the privacy setting information of the target SET.

Step 103: The H-SLP carries the information that needs to be confirmed or notified to the target SET in the Notification parameter of the SUPL initialization (INIT) message.

Specifically, the indication information that needs to be confirmed or notified to the target SET is carried in the type identifier of the notification parameter, and at the same time, the identifier of the requester that needs to be confirmed or notified to the target SET is also carried in the notification parameter.

Step 104: The H-SLP sends a SUPL initialization message to the target SET.

If in step 102, the H-SLP determines that it needs to confirm or notify the target SET, the SUPL initialization message carries notification parameters; otherwise, it does not carry notification parameters.

Before sending the SUPL initialization message, the H-SLP needs to perform routing judgment on the target SET to determine whether the target SET has roamed.

Step 105: After receiving the SUPL initialization message, the target SET establishes a data connection with the H-SLP, and judges whether the SUPL initialization message carries notification parameters, and if so, executes step 106; otherwise, executes step 109.

Step 106: The target SET judges whether the type identifier of the notification parameter carries indication information that needs to be confirmed by itself, and if so, executes step 107; otherwise, executes step 109.

Step 107: The target SET judges whether to authorize the requester corresponding to the requester ID included in the notification parameter of the SUPL initialization message, if yes, execute step 109; otherwise, execute step 108.

Step 108: The target SET directly sends a SUPL end message to the H-SLP, and then goes to step 112.

Step 109: The target SET sends a SUPL positioning initialization (POS INIT) message to the H-SLP, and starts a positioning session with the H-SLP.

Step 110: After receiving the SUPL positioning initialization message, the H-SLP exchanges positioning process messages with the target SET.

Step 111: After the positioning process is completed, the location information of the target SET is obtained, and the H-SLP sends a SUPL end message to the target SET to notify the target SET that the current positioning session is over.

Step 112: The H-SLP sends an MLP Immediate Location Response (SLIA, Standard Location Immediate Answer) message to the SUPL agent.

If the H-SLP has not performed the positioning process, the MLP SLIA message carries the positioning failure information; if the H-SLP has performed the positioning process, the MLP SLIA message carries the location information of the target SET.

As mentioned above, in the current SUPL protocol, the requester is the only one, but in practical applications, there are often situations where multiple requesters need to obtain the location information of the same target SET at the same time. At this time, the multiple requesters There are two ways to obtain the authorization of the same target SET: one is that the multiple requesters initiate a positioning request in the name of one of the requesters and require the authentication of the target SET. After obtaining the authorization of the target SET and receiving the SLP send After receiving the location information of the target SET, the requester that initiates the positioning request forwards the location information of the target SET to other requesters. It can be seen that there must be a prerequisite for this situation: the authentication results of the target SET for all requesters must be The same, but in practical applications, the target SET usually has different authentication results for the requester that needs to obtain its own location information; the other is that the multiple requesters initiate location requests separately and require the authentication of the target SET one by one, In this case, each requesting party needs to initiate a positioning request, which reduces positioning efficiency and wastes network resources.

Contents of the invention

In view of this, the main purpose of the present invention is to provide a SUPL positioning method to improve SUPL positioning efficiency when multiple requesters need to obtain the location information of the same target SET at the same time.

In order to achieve the above object, technical solution of the present invention is achieved in that way:

A security-based SUPL method for user plane mobile positioning, which extends the requester identification and requester type identification in the positioning request message to support two or more requesters, the method comprising:

A. After receiving the location request message sent by the SUPL agent, the SUPL positioning platform H-SLP to which the target SUPL terminal belongs, queries the information carried in the location request message to indicate two or more requesting parties according to the privacy setting information of the target SET. Whether the requester corresponding to the requester ID has a requester that can directly obtain the authorization of the target SET, and save the query result information, and at the same time judge whether there is a requester that needs to confirm or notify the target SET. The indication information of the authorized requester, the indication information that needs to be confirmed or notified to the target SET, and the requester ID are carried in the SUPL initialization message, and then step B is performed; otherwise, step B is performed;

B. H-SLP sends a SUPL initialization message to the target SET. After the target SET receives the SUPL initialization message, it judges whether the SUPL initialization message carries indication information that needs to be confirmed to itself. If it carries it, continue to judge the requester identification carried by the SUPL initialization message Whether there is a requesting party that can obtain its own authorization among the corresponding requesting parties, if so, carry the authorized requesting party identification in the SUPL positioning initialization message and send it to the H-SLP, and then perform step D, if not, perform step C; If not carried, send a SUPL positioning initialization message to the H-SLP, and then perform step D;

C. The target SET judges whether the SUPL initialization message carries the indication information of a directly authorized requesting party, and if so, sends the SUPL location initialization message to the H-SLP, and then performs step D; otherwise, notifies the H-SLP to end this location, this process Finish;

D. The H-SLP starts positioning after receiving the SUPL positioning initialization message, and sends the obtained location information of the target SET and the requester ID authorized by the target SET to the SUPL agent.

The requester ID carried in the positioning request message in step A is: requester member ID and/or requester group ID;

The requester ID carried in the SUPL initialization message in steps A and B is the requester member ID and/or the requester group ID;

The requester ID carried in the SUPL positioning initialization message in steps B and D is the requester member ID and/or the requester group ID.

The requester ID carried in the positioning request message in step A includes the requester group ID,

The requester corresponding to the requester identifier carried in the H-SLP query positioning request message has a requester that can directly obtain the authorization of the target SET, specifically:

H-SLP judges whether the requester group corresponding to the requester group identifier can obtain the information authorized by the target SET in the privacy setting information of the target SET, if found, save the query result information, if not found, then First find the requester member IDs corresponding to the requester group ID in itself, and then find out whether the requester corresponding to the requester member IDs can obtain the information authorized by the target SET according to the privacy setting information of the target SET.

The requester ID carried in the positioning request message in step A includes the requester group ID,

The requester corresponding to the requester identifier carried in the H-SLP query positioning request message has a requester that can directly obtain the authorization of the target SET, specifically:

The H-SLP first finds the requester member ID corresponding to the requester group ID in itself, and then searches the privacy setting information of the target SET to find out whether the requester corresponding to each requester member ID can obtain authorization from the target SET.

The requester ID carried in the positioning request message in step A includes the requester group ID,

After the H-SLP receives the positioning request message, before judging whether there is a requesting party that needs to confirm or notify the target SET, it further includes:

H-SLP searches the privacy setting information of the target SET to see if the requestor group corresponding to the requestor group identifier has information that needs to be confirmed or notified to the target SET, and if found, carries the requestor group identifier in the SUPL initialization message If it is not found, first find the requester member ID corresponding to the requester group ID in itself, and then check in the privacy setting information of the target SET whether the requester corresponding to each requester member ID needs to send Information to be confirmed or notified by the target SET.

The requester ID carried in the positioning request message in step A includes the requester group ID,

After the H-SLP receives the positioning request message, before judging whether there is a requesting party that needs to confirm or notify the target SET, it further includes:

H-SLP first finds the requester member ID corresponding to the requester group ID in itself, and then checks in the privacy setting information of the target SET whether the requester corresponding to each requester member ID needs to confirm or notify the target SET Information.

When the requester ID carried in the positioning request message includes a requester group ID, the requester group ID is one or more than one.

In step A, the H-SLP determines that the requestors corresponding to the requestor IDs carried in the positioning request message indicate two or more requesters have no requestors that can directly obtain the authorization of the target SET, and do not need to confirm with the target SET or after the notified requesting party, before performing step B, further include:

The H-SLP judges whether the privacy setting information of the target SET contains the information of denying all requesters corresponding to the requester ID carried in the positioning request message to obtain their own location information. If yes, this process ends; otherwise, execute step B.

In step A, the H-SLP carries the indication information that needs to be confirmed or notified to the target SET in the SUPL initialization message: the H-SLP carries the indication information that needs to be confirmed or notified to the target SET in the notification parameter of the SUPL initialization message In the type identifier of the

And after the target SET described in step B receives the SUPL initialization message, before judging whether the SUPL initialization message carries indication information that needs to be confirmed to itself, it further includes:

The target SET judges whether the SUPL initialization message carries notification parameters, if so, judges whether the type identifier of the notification parameter of the SUPL initialization message carries indication information that needs to be confirmed to itself; otherwise, sends the SUPL positioning initialization message to the H-SLP, and then performs step D .

Compared with the prior art, the method provided by the present invention adopts the requester identification that supports multiple requesters, and after the H-SLP receives the location request message sent by the SUPL agent, it will need to confirm or notify the target SET The requester ID carried in the SUPL initialization message is sent to the target SET, and then the target SET will return the requester ID authorized by itself to the H-SLP through the SUPL positioning initialization message, and then the H-SLP will be authorized by the target SET after the positioning is completed. The ID of the requesting party is sent to the SUPL agent, which improves the positioning efficiency when multiple requesting parties need to obtain the location information of the target SET at the same time, and saves network resources at the same time.

Description of drawings

FIG. 1 is a flowchart of SUPL positioning initiated by a network in the prior art;

Fig. 2 is a flow chart of network-initiated SUPL positioning provided by the present invention.

Detailed ways

The present invention will be further described in detail below in conjunction with the accompanying drawings and specific embodiments.

Fig. 2 is the flow chart of the SUPL location that the network initiates provided by the present invention, as shown in Fig. 2, its specific steps are as follows:

Step 201: The MLS application on the network side sends an MLP SLIR message to the H-SLP to which the target SET belongs through the SUPL agent, and the MLP SLIR message carries the initiator client ID and requester IDs representing two or more requesters .

Specifically, in the present invention, requester IDs representing two or more requesters are divided into two categories: requester group IDs and two or more requester member IDs. That is to say, when there are two or more requesters, the MLP SLIR message can carry only two or more requestor member IDs, or only requester group IDs, or requester member IDs and requester group IDs. Logos are carried. There may be one or more than one requester group identifiers.

Here, the optional parameter in the MLP SLIR message - the requester parameter can be extended in the following two ways, so that the requester ID can represent two or more requesters:

Method 1: Extend the requester ID and requester type ID in the requester parameter to support two or more requesters;

For the convenience of distinction, in the present invention, each requester ID representing only one requester is called a requester member ID.

Method 2: Extend the requester type identifier in the requester parameter to support the requester group type.

For the convenience of distinction, in the present invention, each requester ID that can represent two or more requesters is called a requester group ID.

The corresponding relationship between each requester group ID and the requester member IDs corresponding to the requesters included in the requester group is stored in the H-SLP in advance.

Specifically, it can be seen from the requester type identifier of the requester parameter whether the requester identifier represents a requester or a requester group.

Step 202: H-SLP receives the MLP SLIR message, and according to the requester ID carried in the MLP SLIR message, searches for the authentication information of the requester in the privacy setting information of the target SET, and then inquires whether there is a request directly authorized by the target SET side, and save the query result information.

Step 203: H-SLP simultaneously judges whether there is a requesting party that needs to confirm or notify the target SET according to the privacy setting information of the target SET. If so, execute step 204; otherwise, execute step 205.

If the requester ID is the requester member ID, the H-SLP will directly search for the authentication information of each requester in the privacy setting information of the target SET; if the requester ID is the requester group ID, then the H-SLP can first search Find the authentication information of the requester group in the privacy setting information of the SET, that is, whether there is information that the requester group can directly obtain the authorization of the target SET and whether there is information that the requester group needs to confirm or notify the target SET, if necessary The requester group that confirms or notifies the target SET, carries the requester group ID in the SUPL initialization message and sends it to the target SET, if not found, then finds the requester member corresponding to the requester group ID in itself ID, and then look up the authentication information of the requester corresponding to each requester member ID in the privacy setting information of the target SET. If there is a requester that needs to confirm or notify the target SET, carry the corresponding requester member ID in the Send to the target SET in the SUPL initialization message, or directly find the requester member ID corresponding to the requester group ID in itself, and then find the authentication of the requester corresponding to each requester member ID in the privacy setting information of the target SET information, if there is a requester that needs to confirm or notify the target SET, the corresponding requester member identifier is carried in the SUPL initialization message and sent to the target SET. That is to say, the SUPL initialization message may carry the requester member ID and/or the requester group ID.

The privacy setting information of the target SET may include authentication information corresponding to the member ID of the requesting party, and may also include authentication information corresponding to the group ID of the requesting party.

Further, if the H-SLP judges according to the privacy setting information of the target SET that the requester corresponding to the requester ID carried in the positioning request message is neither directly authorized by the target SET nor needs to be confirmed or notified to the target SET, The H-SLP can continue to judge whether the privacy setting information of the target SET contains the information denying all requesters to obtain their own location information, if so, execute step 214 ; otherwise, execute step 205 .

Step 204: The H-SLP carries the indication information and requester ID that need to be confirmed or notified to the target SET in the SUPL initialization message, and at the same time, the SUPL initialization message carries the indication information of whether there is a directly authorized requester, and then executes step 205 .

Specifically, the indication information that needs to be confirmed or notified to the target SET is carried in the notification type identifier of the notification parameter of the SUPL initialization message, and the requester identifier that needs to be confirmed or notified to the target SET is carried in the notification parameter. Here, the optional parameter-notification parameter of the SUPL initialization message needs to be extended so that it can include multiple requester member IDs and/or requester group IDs.

Step 205: The H-SLP sends a SUPL initialization message to the target SET.

The SUPL initialization message contains indication information whether there is a directly authorized requester. At the same time, if in step 203, the H-SLP determines that there is a requester that needs to confirm or notify the target SET, it will need to confirm or notify the target SET. The information is carried in the notification type identifier of the notification parameter of the SUPL initialization message, and the requester identifier that needs to be confirmed or notified to the target SET is carried in the notification parameter at the same time; If the SET confirms or notifies, the SUPL initialization message does not carry notification parameters.

Step 206: After receiving the SUPL initialization message, the target SET judges whether the SUPL initialization message carries indication information that needs to be confirmed to itself, and if so, executes step 207; otherwise, executes step 211.

Here, after the target SET receives the initialization message, it can first judge whether the SUPL initialization message carries a notification parameter, if so, continue to judge whether the notification type identifier of the notification parameter carries the indication information that needs to be confirmed to itself; otherwise, execute step 211 .

Step 207: The target SET judges whether the requester corresponding to the requester ID carried in the SUPL initialization message can be authorized by itself, and if so, executes step 210; otherwise, executes step 208.

Step 208 : The target SET judges whether the SUPL initialization message carries indication information of a directly authorized requester, and if so, executes step 211 ; otherwise, executes step 209 .

Step 209: The target SET directly sends a SUPL end message to the H-SLP, and then goes to step 214.

Step 210: The target SET carries the requester ID authorized by itself in the SUPL location initialization message.

Here, the existing SUPL positioning initialization message needs to be extended, and an optional parameter—requester confirmation parameter can be added to the message, which can include the requester ID, namely: requester member ID and/or requester group ID.

Step 211: The target SET sends a SUPL location initialization message to the H-SLP.

Step 212: After receiving the SUPL positioning initialization message, the H-SLP starts to exchange positioning process messages with the target SET, and obtains the position information of the target SET after positioning is completed.

Step 213: The H-SLP sends a SUPL end message to the target SET to notify the target SET that the positioning session is over.

Step 214: H-SLP sends MLP SLIA message to SUPL proxy.

If the positioning process is not performed, the MLP SLIA message carries the positioning failure information; if the positioning process is performed, the MLP SLIA message carries the location information of the target SET, and if there is a requester authorized by the target SET, the MLP SLIA message carries the target SET Requester ID for SET authorization.

An example of practical application is given below to further illustrate the present invention:

Let mobile terminal A set up a friend group X including mobile terminals B, C, and D on the game service platform, and set that when he enters the game, B can directly obtain his own location information without his own confirmation, C and D needs to obtain its own location information after its own confirmation. Then when A enters the game, the game service platform will initiate a positioning of A, and then the positioning server sends a positioning notification message to A to notify the game service platform of A to locate it, and at the same time send the identification of C and D to A , after A receives the positioning notification message, according to the needs of this application, it determines that the location information of this positioning can be sent to D but not to C, then returns the identification of D to the positioning server, and the positioning server receives the identification of D , perform positioning, and send the obtained location information of A to the game service platform, and at the same time notify the game service platform that A’s location information can be sent to B and D, and then the game service platform sends A’s location information to B and D.

After mobile terminal A receives the identities of C and D, it can display the identities of C and D to the user, and the user decides whether to send the location information of this positioning to C and D, and after the user selects D, send D The ID of the returned to the location server.

The above descriptions are only process and method embodiments of the present invention, and are not intended to limit the present invention. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present invention shall be included in the scope of the present invention. within the scope of protection.

Claims (9)

1. one kind based on safe user plane running fix SUPL method, it is characterized in that, the sign of the requesting party in the locating request message and/or requesting party's type identification is expanded to can support two or more requesting parties, and this method comprises:

A, after the SUPL locating platform H-SLP of target SUPL terminal attaching receives that SUPL acts on behalf of the locating request message of sending, privacy configuration information according to target SUPL terminal, two or more requesting parties' of expression that carry in the inquiry locating request message requesting party identifies corresponding requesting party and whether has the requesting party that can directly obtain target SUPL authorization terminal, and preserve this Query Result information, judged whether that simultaneously the requesting party need confirm or notifies to target SUPL terminal, if, whether H-SLP will exist the requesting party's of direct mandate indication information, with need confirm or the indication information notified and requesting party's sign are carried in the SUPL initial message execution in step B then to target SUPL terminal; Otherwise, execution in step B;

B, H-SLP send the SUPL initial message to target SUPL terminal, after target SUPL terminal is received the SUPL initial message, judging whether the SUPL initial message carries need be to the indication information of self confirming, if carry, continue to judge requesting party that the SUPL initial message carries identifies whether the requesting party that can obtain self mandate is arranged among the corresponding requesting party, if have, authorized requesting party sign is carried in the initial message of SUPL location sends to H-SLP, execution in step D then, if there is not execution in step C; If do not carry, send SUPL location initial message, execution in step D then to H-SLP;

Whether C, target SUPL terminal judges SUPL initial message carry the indication information that has the requesting party who directly authorizes, if send SUPL location initial message, execution in step D then to H-SLP; Otherwise notice H-SLP finishes this location, and this flow process finishes;

D, H-SLP begin the location after receiving SUPL location initial message, and target SUPL location information of terminals that obtains and the requesting party's sign that obtains the target SET mandate are sent to the SUPL agency.

2. the method for claim 1 is characterized in that, the requesting party that the described locating request message of steps A is carried is designated: requesting party member's sign and/or requesting party's group id;

The requesting party that the described SUPL initial message of steps A and B carries is designated requesting party member's sign and/or requesting party's group id;

The requesting party that the described SUPL of step B and D location initial message carries is designated requesting party member's sign and/or requesting party's group id.

3. method as claimed in claim 2 is characterized in that, requesting party's sign that the described locating request message of steps A is carried comprises requesting party's group id,

Whether the requesting party who carries in the described H-SLP inquiry locating request message identifies corresponding requesting party and exists the requesting party that can directly obtain target SUPL authorization terminal to be specially:

H-SLP judges whether the requesting party's group that whether finds this requesting party's group id correspondence in the privacy configuration information of target SUPL terminal can obtain the information of target SUPL authorization terminal, if find, preserve this Query Result information, if do not find, then, identify the information whether corresponding requesting party can obtain target SUPL authorization terminal according in the privacy configuration information of target SUPL terminal, searching described each requesting party member then at first self finding each requesting party member's sign of this requesting party's group id correspondence.

4. method as claimed in claim 2 is characterized in that, requesting party's sign that the described locating request message of steps A is carried comprises requesting party's group id,

Whether the requesting party who carries in the described H-SLP inquiry locating request message identifies corresponding requesting party and exists the requesting party that can directly obtain target SUPL authorization terminal to be specially:

H-SLP at first self finding requesting party member's sign of this requesting party's group id correspondence, searches described each requesting party member then and identifies the information whether corresponding requesting party can obtain target SUPL authorization terminal in the privacy configuration information of target SUPL terminal.

5. method as claimed in claim 2 is characterized in that, requesting party's sign that the described locating request message of steps A is carried comprises requesting party's group id,

Described H-SLP receives after the locating request message, has judged whether that the requesting party need further comprise before target SUPL terminal is confirmed or notified:

Whether H-SLP searches this requesting party's group id correspondence in the privacy configuration information of target SUPL terminal requesting party group has the information that need confirm or notify to target SUPL terminal, if find, this requesting party's group id is carried in the SUPL initial message, if do not find, then at first self finding the requesting party member sign of this requesting party's group id correspondence, in the privacy configuration information of target SUPL terminal, searching described each requesting party member then and identify corresponding requesting party whether the information that need confirm or notify to target SUPL terminal is arranged.

6. method as claimed in claim 2 is characterized in that, requesting party's sign that the described locating request message of steps A is carried comprises requesting party's group id,

Described H-SLP receives after the locating request message, has judged whether that the requesting party need further comprise before target SUPL terminal is confirmed or notified:

H-SLP at first self is finding the requesting party member sign of this requesting party's group id correspondence, searches described each requesting party member then and identify corresponding requesting party and whether need the information confirming or notify to target SUPL terminal in the privacy configuration information of target SUPL terminal.

7. as any described method in the claim 2 to 6, it is characterized in that when requesting party's sign of carrying when described locating request message comprised requesting party's group id, described request side's group id was one or more.

8. the method for claim 1, it is characterized in that, the described H-SLP of steps A judges that two or more requesting parties' of expression that locating request message is carried requesting party identifies the requesting party that corresponding requesting party does not have directly to obtain the mandate of target SUPL terminal, do not need yet to target SUPL terminal confirm or the requesting party that notify after, execution in step B further comprises before:

H-SLP judges that whether having comprised the requesting party who carries in the refusal locating request message in the privacy configuration information of target SUPL terminal identifies the information that all corresponding requesting parties obtain self positional information, if comprise, this flow process finishes; Otherwise, execution in step B.

9. the method for claim 1, it is characterized in that, the described H-SLP of steps A will need to confirm or the indication information notified is carried in the SUPL initial message and is to target SUPL terminal: H-SLP will need to confirm or the indication information notified is carried in the type identification of notifying parameters of SUPL initial message to target SUPL terminal

And the described target SUPL terminal of step B receives after the SUPL initial message, judges whether the SUPL initial message carries need further comprise before the indication information of self confirming:

Whether target SUPL terminal judges SUPL initial message carries notifying parameters, if whether the type identification of judging the notifying parameters of SUPL initial message carries need be to the indication information of self confirming; Otherwise, send SUPL location initial message, execution in step D then to H-SLP.

Images