CN100563136C - A kind of method based on TCP/IP movable positioning system and location positioning thereof - Google Patents

A kind of method based on TCP/IP movable positioning system and location positioning thereof Download PDF

Info

Publication number
CN100563136C
CN100563136C CNB031539319A CN03153931A CN100563136C CN 100563136 C CN100563136 C CN 100563136C CN B031539319 A CNB031539319 A CN B031539319A CN 03153931 A CN03153931 A CN 03153931A CN 100563136 C CN100563136 C CN 100563136C
Authority
CN
China
Prior art keywords
mpc
location
user
called
district
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Expired - Fee Related
Application number
CNB031539319A
Other languages
Chinese (zh)
Other versions
CN1585319A (en
Inventor
程琦
葛正恺
许国华
阎晓路
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to CNB031539319A priority Critical patent/CN100563136C/en
Publication of CN1585319A publication Critical patent/CN1585319A/en
Application granted granted Critical
Publication of CN100563136C publication Critical patent/CN100563136C/en
Anticipated expiration legal-status Critical
Expired - Fee Related legal-status Critical Current

Links

Images

Abstract

The invention discloses a kind ofly based on the TCP/IP movable positioning system, it comprises a plurality of MPC, connects by ICP/IP protocol between each MPC.The present invention discloses a kind of location positioning method based on TCP/IP, its this method is used above-mentioned movable positioning system and is positioned, and comprises the position fixing process that Client-initiated position fixing process and network side are initiated.The present invention has realized interconnecting and the strange land location positioning between a plurality of MPC, and implementation is simple, does not need MPC is carried out bigger change.

Description

A kind of method based on TCP/IP movable positioning system and location positioning thereof
Technical field
The present invention relates to the shift position business of code division multiple access system, particularly a kind of method based on TCP/IP movable positioning system and location positioning thereof.
Background technology
Location service is a kind of novel value-added service that mobile radio communication provides.This business obtains the positional information of travelling carriage by wireless location technology, comprising: information such as longitude and latitude, translational speed, offer user, mobile communications network or other external entities, and realize the various business relevant with the position.
Fixer network based on TCP/IP is carrying with the grouped data, generally inserts cdma network by packet data serving node (PDSN), realizes the information interaction between position determining entity (PDE) and the travelling carriage (MS), thereby finishes positioning action.
At present, be used to realize location service, referring to Fig. 1, Fig. 1 is the network configuration of prior art based on the movable positioning system of TCP/IP based on the running fix network configuration of TCP/IP.
Wherein, mobile positioning center (MPC) 107 links to each other with service provider/LCS client (can be described as CP) 108 and position determining entity (PDE) 106 by TCP/IP.The ability that MPC107 has the storage, user's access authentication, user management, authorization check of user profile, the normal place service interface is provided and charge information, Operation and Maintenance and database maintenance are provided for content service.
The interface of MPC107 and CP108 can be realized by dual mode: basic demand is the LIF agreement based on XML, and senior requirement is the OSA/Parlay interface.
The interface of MPC107 and PDE106 is: MPC107 is by the interface of TCP/IP network to PDE106 request customer location.
PDE106 carries out with MPC107 and MS104 by the TCP/IP network alternately.
The interface of PDE106 and MPC107 comprises that MPC107 is to PDE106 inquiring user positional information.The interface of PDE106 and MS104 comprises the positioning interaction based on IS801 that carries out between PDE106 and the MS104.
MPC107 and MS104 are exactly interface with PDSN105 based on the interface of TCP/IP, MS104 at first is linked into PDSN105 by radio reception device, carry out the TCP/IP interacting message by PDSN105 and MPC107 again.Also have short message interface between MPC107 and the MS104, short message interface is meant when network side is initiated the location that MPC initiates note location notice to MS, and the message reply of MS.
The major function of PDE106 is determined the MS104 position for finishing location Calculation.
MS104 realizes mobile communication function by base station sub-system/Packet Control Function (BSS/PCF) 102, mobile switching centre (MSC) 102 with CMDA signaling network 101.
Navigation system shown in Figure 1 can realize the location positioning of three kinds of modes.
First kind of positioning service based on WAP that mode: MS initiatively initiates, its basic procedure be referring to Fig. 2, the flow chart based on the positioning service of WAP that Fig. 2 initiatively initiates for prior art MS.This flow process may further comprise the steps:
Step 1, MS insert CP by the WAP mode, send service request.
Step 2, CP send Location Request by the L1 interface to mobile positioning center.Start timer T4.
Step 3, CP return request-reply by WAP
Step 4, mobile positioning center send authentication message to user/CP database, check whether initiation located subscriber and CP are authorized to.User/CP database is the part of mobile positioning center, and this processing process is undertaken by internal interface.
Step 5, user/CP database return authenticating result to mobile positioning center.User/CP database is the part of mobile positioning center, and this processing process is undertaken by internal interface.
Step 6, MS initiate Location Request StartPositioningProcessRequest to mobile positioning center.Termination timing device T4.
If step 7 user refuses the location, or the Authentication Authorization failure, the location finished; If carry out a location to this travelling carriage, must wait for that then this localization is finished after, proceed this location.Otherwise mobile positioning center uses GEOPOSREQ message to send Location Request to position determining entity.Start timer T1.
Step 8, mobile positioning center send location response StartPositioningProcessResponse to MS, activate MS and initiate the IS801 session.MPC must inform travelling carriage with the IP address of PDE, port numbers etc.
IS801 interacting message between step 9, position determining entity and the MS carries out the calculating of MS position.Require position determining entity in the end in IS801 message, directly real position data is not beamed back MS.
Finish step 10, location, and position determining entity uses geoposreq to send positioning result to mobile positioning center, mobile positioning center store M S current location information.Termination timing device T1.
Step 11, mobile positioning center return the MS positional information by the L1 interface and give CP.
Step 12, MS send service request by WAP to CP.
Step 13, CP return information on services by WAP and give MS, for MS provides service.The second way: the positioning service that network side is initiated, its basic procedure are referring to Fig. 3, and Fig. 3 is the flow chart of the positioning service of prior art network side initiation.
Step 1, CP send Location Request by the L1 interface protocol to mobile positioning center.
Step 2, mobile positioning center are carried out authorization check to the authentication of CP and target MS to CP and inquiry promoter.Whether mobile positioning center is signatory to user/CP database auditing CP and target MS, initiates the positional information whether located subscriber has the right to obtain target MS.User/CP database is the part of mobile positioning center, and this processing process is undertaken by internal interface.
Step 3, user/CP database return authenticating result to mobile positioning center.User/CP database is the part of mobile positioning center, and this processing process is undertaken by internal interface.
If step 4 authorization check not by or can not satisfy this Location Request, then finish the location; If carry out a location to this travelling carriage, must wait for that then this localization is finished after, the situation that is authorized to according to location initiator continues this location.Otherwise mobile positioning center uses GEOPOSREQ message to send Location Request to position determining entity.Start timer T1.
Step 5, mobile positioning center send a special MT (Mobile Termination) short message by sms center to target MS, require MS that the inquiry promoter is made authorization check and triggered location process.Start timer T3.
Step 6, target MS send MO (Mobile Origination) short message to mobile positioning center, agree the location.Termination timing device T3.
IS801 interacting message between step 7, position determining entity and the MS carries out the calculating of MS position.Require position determining entity in the end in IS801 message, directly real position data is not beamed back MS.
Step 8, position determining entity use geoposreq to mobile positioning center restoring to normal position result.Termination timing device T1.
Step 9, mobile positioning center store location result, and only reply the MO short message what receive travelling carriage, after information representation user wherein agreed to be positioned, just the message by meeting the L1 interface protocol was to CP restoring to normal position result.If T3 is overtime, perhaps the user disagrees with and is positioned, and then finishes the location.
The positioning service based on JAVA/BREW that the third mode: MS initiatively initiates, its basic procedure be referring to Fig. 4, the flow chart based on the positioning service of JAVA/BREW that Fig. 4 initiatively initiates for prior art MS.
Step 1, MS initiate Location Request StartPositioningProcessRequest to mobile positioning center.Before sending the StartPositioningProcessRequest Location Request, MS should eject a dialog box, requires the user to be confirmed to be and agrees still refusal location.
Step 2, mobile positioning center send authentication message to user/CP database, check whether initiation located subscriber and corresponding mobile station TSR are authorized to.
User/LCS CLIENT database is the part of mobile positioning center, and this processing process is undertaken by internal interface.
Step 3, user/CP database return authenticating result to mobile positioning center.Authenticating result should comprise IMSI and stationkeeping ability that whether following information: CP and MS be contracted user, MS, whether allow to be initiated the CP location of asking etc.This processing process is undertaken by internal interface.
If the failure of step 4 Authentication Authorization finishes the location; If carry out a location to this travelling carriage, must wait for that then this localization is finished after, continue the location.Otherwise mobile positioning center uses GEOPOSREQ message to send Location Request to position determining entity.Start timer T1.
Step 5, mobile positioning center send location response StartPositioningProcessResponse to MS, activate MS and initiate the IS801 session.
IS801 interacting message between step 6, position determining entity and the MS carries out the calculating of MS position.Require position determining entity in the end in IS801 message, directly real position data is beamed back MS.
Step 7, position determining entity use geoposreq to mobile positioning center restoring to normal position result.Termination timing device T1.
Above-mentioned movable positioning system and localization method based on ICP/IP protocol, to the requirement of not upgrading of core network, access network, but the interconnecting between the MPC of being unrealized.
Existing in the world standard criterion realize the scheme that interconnects--PN4747 between the mobile positioning center (MPC) of shift position positioning service in code division multiple access (CDMA) network.But this standard based on agreement be signalling system No.7, and existing CDMA core network is had the upgrading requirement, be not suitable for navigation system based on TCP/IP.
Summary of the invention
In view of this, it is a kind of based on the TCP/IP movable positioning system that main purpose of the present invention is to provide, and realizes interconnecting between a plurality of MPC.
Another main purpose of the present invention is to provide a kind of location positioning method based on TCP/IP, utilizes interconnected MPC, realizes the strange land location positioning.
Be an aspect that achieves the above object, the invention provides a kind of based on the TCP/IP movable positioning system, comprise position determining entity (PDE), packet data serving node (PDSN), mobile positioning center (MPC), MPC links to each other respectively with PDSN with code division multiple access (CDMA) signaling network, PDSN links to each other, it is characterized in that with base station sub-system (the BSS)/Packet Control Function (PCF) of cdma system:
The MPC that this system comprises is a plurality of; Connect by ICP/IP protocol between each MPC; Described PDE links to each other with all MPC by ICP/IP protocol, and MPC links to each other by ICP/IP protocol with location service provider (CP) equipment;
Arbitrary MPC is used for after receiving Location Request, and whether the mobile station MS that judgement need be positioned is the local user, if not, then Location Request is forwarded to the MPC of described MS ownership;
The MPC of described MS ownership is used for sending Location Request to PDE, by interacting message, carries out the MS position calculation between MS and the PDE; PDE returns to the MPC that this MS belongs to positioning result with location response, finishes the user location.
Two kinds of implementation methods can be arranged specifically:
First kind: among described a plurality of MPC, can comprise a Gateway Mobile Location Center (GMPC), PDSN all in the described movable positioning system link to each other with GMPC; Provide provider (CP) equipment of the whole network location service to link to each other with GMPC.GMPC can transmit travelling carriage (MS) or/and the positioning request information that CP sends to other MPC.
First kind: described a plurality of MPC all have the function of CP access, forwards, and local PDSN can link to each other with the MPC of this locality.Can transmit travelling carriage (MS) between described each MPC or/and the positioning request information that CP sends.Can also send the roaming authentication message between described each MPC.
Be another aspect that achieves the above object, the invention provides a kind of location positioning method based on TCP/IP, use above-mentioned movable positioning system and position, this method comprises the position fixing process that Client-initiated position fixing process and network side are initiated;
Described Client-initiated position fixing process may further comprise the steps:
Y1) travelling carriage (MS) sends Location Request by PDSN to the MPC that starts;
Y2) start to judge whether this MS is the local user after MPC receives Location Request, if then carry out the local positioning flow of Client-initiated; Otherwise this Location Request is transmitted to the MPC of this MS ownership;
Y3) after the MPC of this MS ownership receives this Location Request, send Location Request to PDE, and respond to the MS restoring to normal position by start MPC and PDSN;
Y4) pass through interacting message between MS and the PDE, carry out the MS position calculation;
Y5) PDE returns to the MPC that this MS belongs to positioning result with location response, finishes the user location;
The position fixing process that described network side is initiated may further comprise the steps:
W1) network side CP sends Location Request to the MPC that starts that links to each other with this CP;
W2) start to judge whether called MS is the local user after MPC receives Location Request, if then carry out the local positioning flow that network side is initiated; Otherwise this Location Request is transmitted to the MPC of called MS ownership;
W3) after the MPC of called MS ownership receives this Location Request, judge whether called MS is identical with caller MS, if identical then direct execution in step W4), otherwise after caller MS carried out authentication, execution in step W4)
W4) MPC of called MS ownership carries out authentication to CP and the called MS initiated; If authentication is passed through, execution in step W5 then), otherwise finish;
W5) MPC of called MS ownership sends Location Request to PDE, and triggers the called MS localization;
W6) pass through interacting message between called MS and the PDE, carry out the MS position calculation;
W7) PDE returns to positioning result the MPC of called MS ownership with location response;
W8) MPC of called MS ownership by the CP that the MPC that starts returns to initiation, finishes the user location with location response.
Wherein, when the user adopts the WAP mode to position, carrying out described step Y1) precedingly can further carry out following steps:
Y01) MS sends the WAP service request to the CP of its selection, and CP receives that this request back returns the WAP service request to MS and reply, and asks the user to confirm to serve simultaneously; And to the initial MPC transmission Location Request that links to each other with this CP;
Y02) start to judge whether this MS is the local user after MPC receives Location Request, if then directly CP and MS are carried out authentication; Otherwise this Location Request is transmitted to the MPC that this MS belongs to, and the MPC of this MS ownership carries out authentication to CP and MS;
Y03) after the user confirms service, enter step Y1);
Carrying out described step Y5) after can further carry out following steps:
Y51) MPC of this MS ownership returns to CP with location response by the MPC that starts with positioning result;
Y52) this MS sends the WAP service request to the CP of its selection, and CP receives that this request then returns the WAP service request to MS and reply, for MS provides location-based service.
When the user adopts the WAP mode to position, step Y2) identical can may further comprise the steps of the local positioning flow prior art of described Client-initiated:
Y21) start MPC to the response of MS restoring to normal position, and send Location Request to PDE;
Y22) carry out the IS801 interacting message between MS and the PDE, carry out the MS position calculation;
Y23) PDE returns to the MPC that starts with positioning result with location response, finishes the user location.
When the user adopts the JAVA/BREW mode to position, step Y2) identical can may further comprise the steps of the local positioning flow prior art of described Client-initiated:
Y21) MPC that starts carries out authentication to this MS, if authentication is passed through, sends Location Request then to the response of MS restoring to normal position, and to PDE; Otherwise finish;
Y22) carry out the IS801 interacting message between MS and the PDE, carry out the MS position calculation;
Y23) PDE returns to the MPC that starts with positioning result with location response, finishes the user location.
Step W2) same as the prior art can may further comprise the steps of local positioning flow of described network side initiation:
W21) MPC that starts carries out authentication to CP and the called MS initiated; If authentication is passed through then execution in step W22), otherwise finish;
W22) MPC that starts sends Location Request to PDE, and sends the MT short message to called MS and trigger the called MS localization; Called MS is returned the MO short message and is agreed the location;
W23) carry out the IS801 interacting message between called MS and the PDE, carry out the MS position calculation;
W24) PDE returns to the MPC that starts with positioning result with location response;
W25) MPC that starts returns to the CP of initiation with location response, finishes the user location.
When the user adopts the JAVA/BREW mode to position, described step Y3) may further include:
The MPC of this MS ownership carries out authentication to this MS, if authentication is passed through, then sends Location Request to PDE, and responds to the MS restoring to normal position; Otherwise finish.
Described step Y3) may further include: after MS receives location response, initiate the IS801 session to position determining entity;
Step Y4) described information interaction can be the IS801 information interaction.
When the user adopted the JAVA/BREW mode to position, described position determining entity can be in the end in IS801 message, directly real position data returned to MS.
Step W3) describedly caller MS is carried out authentication can may further comprise the steps:
W31) MPC of called MS ownership judges whether caller MS is the local user, if then caller MS is carried out authentication; Otherwise the MPC of called MS ownership sends caller roaming authentication request to the MPC of caller MS ownership;
W32) MPC of caller MS ownership carries out authentication to caller MS;
W33) MPC of caller MS ownership returns caller roaming Authentication Response to the MPC of called MS ownership;
W34) if caller MS roaming authentication is passed through execution in step W4 then), otherwise finish.
Step W3) describedly caller MS is carried out authentication also can may further comprise the steps:
W31) in advance called MS is belonged to the database of MPC and the database of caller MS ownership MPC and carry out data sync;
W32) MPC of called ownership carries out authentication to caller MS;
W33) if the caller authentication is passed through execution in step W4 then), otherwise finish.
Step W5) described triggering called MS localization can may further comprise the steps:
W51) MPC of called MS ownership sends the MT short message to called MS and triggers the called MS localization;
W52) called MS is returned MO short message agreement location.
In addition, this method may further include: a gateway MPC is set in this navigation system, and the Location Request that all MS send all sends to gateway MPC.
By technical scheme of the present invention as seen, this method of the present invention based on TCP/IP movable positioning system and location positioning thereof, it is interconnected to have realized that a plurality of MPC are passed through ICP/IP protocol, and a plurality of MPC carry out traffic carrying capacity and share, reduce single MPC traffic load, improved the efficient of location positioning.In the positioning service of position, position location request is transmitted to ownership MPC, MPC carries out positioning flow by ownership.The present invention has realized interconnecting and the strange land location positioning between a plurality of MPC, and implementation is simple, does not need MPC is carried out bigger change.
Description of drawings
Fig. 1 is the network configuration of prior art based on the movable positioning system of TCP/IP;
The flow chart that Fig. 2 prior art MS initiatively initiates based on the positioning service of WAP;
Fig. 3 is the flow chart of the positioning service of prior art network side initiation;
The flow chart that Fig. 4 initiatively initiates for prior art MS based on the positioning service of JAVA/BREW;
Fig. 5 is the schematic network structure based on the TCP/IP movable positioning system of the present invention's first preferred embodiment;
Fig. 6 uses the WAP mode positioning flow of B district CP2 for B district user;
Fig. 7 uses the WAP mode positioning flow of A district CP for B district user;
Fig. 8 initiates for network side, and B district user uses A district CP location B district user's positioning flow.
Fig. 9 initiates for network side, and B district user uses A district CP location A district user's positioning flow;
The A district user that Figure 10 initiates for network side uses A district CP location B district user's positioning flow;
Figure 11 uses JAVA/BREW mode positioning flow for B district user.
Figure 12 is the schematic network structure based on the TCP/IP movable positioning system of the present invention's second preferred embodiment;
Figure 13 uses the WAP mode positioning flow of B district CP2 for A district user;
Figure 14 roams into the WAP mode positioning flow that the B district uses A district CP1 for A district user;
Figure 15 roams into the WAP mode positioning flow that the B district uses B district CP2 for A district user;
The A district user that Figure 16 initiates for network side uses B district CP2 location A district user's positioning flow;
The A district user that Figure 17 initiates for network side uses A district CP1 location B district user's positioning flow;
The A district user that Figure 18 initiates for network side uses B district CP2 location B district user's positioning flow.
The A district user that Figure 19 initiates for network side uses A district CP1 location B district user's positioning flow;
Figure 20 roams into the JAVA/BREW mode positioning flow in B district for A district user.
Embodiment
For making the purpose, technical solutions and advantages of the present invention clearer, below in conjunction with two embodiment and accompanying drawing, the present invention is described in more detail.
The present invention couples together a plurality of MPC by ICP/IP protocol, utilize wherein have forwarding capability MPC with travelling carriage (MS) or/and the positioning request information that CP sends is transmitted to the MPC of called MS ownership, by the MPC executing location positioning flow of called MS ownership.Between a plurality of MPC in the basic fundamental of interface and the network all computer, connection between the server identical.
Referring to Fig. 5, Fig. 5 is the schematic network structure based on the TCP/IP movable positioning system of the present invention's first preferred embodiment; This system has comprised two MPC: gateway MPC (GMPC) 505 and MPC2 506, and for example, the user of southern Da Qu opens an account on GMPC505, and the user of northern Da Qu opens an account on MPC2506.
Wherein, GMPC 505 finishes the access of CP, the message access function of MS, and realizes forwards, the function of service logic control.Interconnected to realize MPC, the user provides service for the whole network.
Be the CP1 502 and the CP2 504 of Ben Da district user-provided location business, link to each other with GMPC 505, the MPC506 of their place Da Qu respectively; The CP 501 of promising national user-provided location business all link to each other with GMPC 505.
The all PDSN 507 of total system link to each other with GMPC 505, and the virtual address map on the GPSOne mobile phone are become the address of GMPC 505.Promptly the Location Request (StartPositioningProcessRequest) of all mobile phones transmissions all is dealt into GMPC 505 earlier, is distributed by GMPC 505 again.GMPC 505 can also transmit L1 locating request message and roaming authentication message to MPC2.
The major control flow process of the location service service of present embodiment is carried out on the MPC of called ownership; MPC is the segment management user according to number, needs to dispose the CDMA Subscriber Number section and the MPC mapping table in the whole nation on each MPC, and GMPC takes a decision as to whether the local user according to this mapping table, whether needs to transmit Location Request.
GMPC can resolve for the L1 request message of sending from CP, if location oneself then judges whether it is the local user according to number segment, if the local user, then directly local the processing.If not the local user, then L1 is transmitted to MPC2 and handles.
GMPC resolves for the L1 request message of sending from CP, if locate other people, then handles respectively according to calling and called location difference:
If calling and called are all in this locality, then directly handle this locality.
If calling and called, then directly are transmitted to MPC2 all not in this locality and handle.
If caller is called not in this locality in this locality, then the L1 request is transmitted to MPC2, needing on the MPC2 the calling subscriber authentication of ownership place on MPC1.Can adopt the mode that increases caller roaming authorization interface to realize.Also can adopt the data on the synchronous GMPC1 of MPC2, directly use synchrodata to carry out authentication.After the caller authentication is passed through, carry out positioning processing again behind called authentication and the privacy authentication.At last the L1 location response is returned to GMPC.After GMPC receives that the L1 of MPC2 responds, L1 is responded be transmitted to CP again.
If caller is called in this locality not in this locality, then need on MPC2, carry out the caller authentication.Can adopt the mode that increases caller roaming authorization interface to realize.Also can adopt the data on the synchronous MPC2 of GMPC, directly use synchrodata to carry out authentication.After the caller authentication is passed through, carry out the GPSOne location again.At last, the L1 response is returned to CP.
GMPC can also be for receiving that from PDSN the StartPositioningProcessRequest message that MS sends resolve, parse phone number after, judge whether it is the local user according to number segment, if the local user, then directly local the processing.If not the local user, then be transmitted to MPC2 and handle.
To divide into the GMPC location is the A district, and the MPC2 location is the B district, lifts several concrete positioning flows first preferred embodiment is described.
Referring to Fig. 6, Fig. 6 uses the WAP mode positioning flow of B district CP2 for B district user.This flow process may further comprise the steps:
Step 1, MS propose service request by the WAP mode to the CP2 in B district;
Step 2, CP2 send Location Request by the L1 interface to MPC2;
Step 3, CP2 return the WAP request-reply by the WAP mode to MS; And request MS confirms;
Step 4, MPC2 send authentication message to user/CP database, check whether the MS and the CP that initiate the location are awarded; User/CP database is the part of mobile positioning center, and this processing process is carried out (following flow process is identical) by internal interface.
Step 5, user/CP database return authenticating result to MPC2;
After step 6, MS confirm service, send Location Request StartPositioningProcessRequest message to service PDSN;
Step 7, PDSN send to GMPC with Location Request StartPositioningProcessRequest;
Step 8, GMPC resolve message, judge whether it is the local area user, find it is not the local area user; If the local area user then handles at local area, processing procedure is same as the prior art.
Step 9, GMPC then are transmitted to MPC2 with Location Request StartPositioningProcessRequest;
Step 10, MPC2 use GEOPOSREQ message to send Location Request to position determining entity (PDE);
Step 11, MPC2 send location response StartPositioningProcessResponse to MS, activate MS and initiate the IS801 session;
Step 12, GMPC receive the location response StartPositioningProcessResponse that MPC2 sends, and it is transmitted to MS;
Step 13, service PDSN send to MS with location response StartPositioningProcessResponse;
IS801 interacting message between step 14, position determining entity and the MS carries out the calculating of MS position;
Finish step 15, location, and position determining entity uses geoposreq to send positioning result to MPC2, MPC2 storage targeted customer current location information;
Step 16, MPC2 return to CP2 by the L1 interface with the MS positional information;
Step 17, MS send service request by the WAP mode to CP2;
Step 18, CP2 return information on services by the WAP mode and give MS, for MS provides service.
Wherein, B district user uses CP2 to position, select by B district user, this user also can select to use national user-provided location business CP, position as the CP1 of A district user-provided location business.In the present embodiment, because B district MPC2 does not have forwarding capability, B district CP2 links to each other with B district MPC2, so B district CP2 can only be local area user service.
Referring to Fig. 7, Fig. 7 uses the WAP mode positioning flow of A district CP (as the whole network user service) for B district user.This flow process may further comprise the steps:
Step 1, MS propose service request by the WAP mode to CP;
Step 2, CP send Location Request by the L1 interface to GMPC;
Step 3, CP return the WAP request-reply by the WAP mode to MS; And request MS confirms;
Step 4, GMPC resolve message, judge whether it is the local area user, find it is not the local area user; If the local area user then handles at local area, processing procedure is same as the prior art;
Step 5, GMPC are transmitted to MPC2 with the L1 request message
Step 6, MPC2 send authentication message to user/CP database, check whether the MS and the CP that initiate the location are awarded;
Step 7, user/CP database return authenticating result to MPC2;
After step 8, MS confirm service, initiate Location Request StartPositioningProcessRequest to MPC2, StartPositioningProcessRequest message sends to user's service PDSN earlier;
Step 9, PDSN send to GMPC with Location Request StartPositioningProcessRequest;
Step 10, GMPC resolve message, judge whether it is the local area user, find it is not the local area user;
Step 11, GMPC then are transmitted to MPC2 with Location Request StartPositioningProcessRequest;
Step 12, MPC2 use GEOPOSREQ message to send Location Request to position determining entity;
Step 13, MPC2 send location response StartPositioningProcessResponse to MS, activate MS and initiate the IS801 session;
Step 14, GMPC receive the location response StartPositioningProcessResponse that MPC2 sends, and it is transmitted to MS;
Step 15, service PDSN send to MS with location response StartPositioningProcessResponse;
IS801 interacting message between step 16, position determining entity and the MS carries out the calculating of MS position;
Finish step 17, location, and position determining entity uses geoposreq to send positioning result to MPC2, MPC2 storage targeted customer current location information;
Step 18, MPC2 respond to the GMPC restoring to normal position by the L1 interface;
Step 19, GMPC return the MS positional information by the L1 interface to CP;
Step 20, MS send service request by WAP to CP;
Step 21, CP return information on services by WAP and give MS, for MS provides service.
Referring to Fig. 8, Fig. 8 initiates for network side, and B district user uses A district CP (as the whole network user service) location B district user's positioning flow.This flow process may further comprise the steps:
Step 1, CP send Location Request by the L1 interface protocol to GMPC;
Step 2, GMPC resolve the L1 Location Request, and whether judge called is the local area user, find it is not the local area user; If the local area user is then handled by local area, processing procedure is same as the prior art.
Step 3, GMPC are transmitted to MPC2 with the L1 Location Request;
Step 4, MPC2 carry out the calling and called authentication;
Step 5, MPC2 are carried out authorization check to the authentication of CP and called MS to CP and inquiry promoter;
Step 6, user/CP database return authenticating result to MPC2;
Step 7, MPC2 use GEOPOSREQ message to send Location Request to position determining entity.Start timer T1;
Step 8, MPC2 send a special MT (Mobile Termination) short message by sms center to target MS, require step 13, MS that the inquiry promoter is made authorization check and triggered location process;
Step 9, called MS send MO (Mobile Origination) short message to MPC2, agree the location.Termination timing device T3.
IS801 interacting message between step 10, position determining entity and the MS carries out the calculating of MS position.Require position determining entity in the end in IS801 message, directly real position data is not beamed back MS.
Step 11, position determining entity use geoposreq to MPC2 restoring to normal position result.Termination timing device T1.
Step 12, MPC2 store location result, the message by meeting the L1 interface protocol is to GMPC restoring to normal position result;
Step 13, mobile positioning center GMPC store location result, the message by meeting the L1 interface protocol is to LCS CLIENT restoring to normal position result.
Referring to Fig. 9, Fig. 9 initiates for network side, and B district user uses A district CP location A district user's positioning flow.This flow process may further comprise the steps:
Step 1, CP send Location Request by the L1 interface protocol to GMPC;
Step 2, GMPC resolve the L1 interface, find that caller is not in this locality; If caller is in this locality then handle in this locality.
Step 3, GMPC send caller roaming request to MPC2;
Step 4, MPC2 roam Authentication Response with caller and return to GMPC;
Step 5, GMPC are carried out authorization check to the authentication of CP and called MS to CP and inquiry promoter;
Step 6, user/CP database return authenticating result to GMPC;
Step 7, GMPC use GEOPOSREQ message to send Location Request to position determining entity.Start timer T1;
Step 8, GMPC send a special MT (Mobile Termination) short message by sms center to target MS, require MS that the inquiry promoter is made authorization check and triggered location process;
Step 9, called MS send MO (Mobile Origination) short message to GMPC, agree the location.Termination timing device T3.
IS801 interacting message between step 10, position determining entity and the MS carries out the calculating of MS position.Require position determining entity in the end in IS801 message, directly real position data is not beamed back MS.
Step 11, position determining entity use geoposreq to mobile positioning center GMPC restoring to normal position result.Termination timing device T1.
Step 12, mobile positioning center GMPC store location result, the message by meeting the L1 interface protocol is to CP restoring to normal position result.
When the local area user of network side initiation used local area CP location local area user, its realization flow was same as the prior art.
Referring to Figure 10, the A district user that Figure 10 initiates for network side uses A district CP location B district user's positioning flow.This flow process may further comprise the steps:
Step 1, A district CP send Location Request by the L1 interface protocol to GMPC;
Step 2, GMPC resolve the L1 interface, find called not in this locality;
Step 3, GMPC are transmitted to MPC2 with the L1 Location Request;
Step 4, MPC2 send caller roaming authentication request to GMPC;
Step 5, GMPC roam Authentication Response with caller and return to MPC2;
Step 6, MPC2 are carried out authorization check to the authentication of CP and called MS to CP and inquiry promoter;
Step 7, user/CP database return authenticating result to MPC2;
Step 8, MPC2 use GEOPOSREQ message to send Location Request to position determining entity.Start timer T1;
Step 9, MPC2 send a special MT (Mobile Termination) short message, requirement by sms center to called MS
Step 10, called MS are made authorization check and triggered location process to the inquiry promoter;
Step 11, called MS send MO (Mobile Origination) short message to MPC2, agree the location.Termination timing device T3.
IS801 interacting message between step 12, position determining entity and the MS carries out the calculating of MS position.Require position determining entity in the end in IS801 message, directly real position data is not beamed back MS.
Step 13, position determining entity use geoposreq to MPC2 restoring to normal position result.Termination timing device T1.
Step 14, MPC2 store location result, the message by meeting the L1 interface protocol is to GMPC restoring to normal position result;
Step 15, GMPC store location result, the message by meeting the L1 interface protocol is to CP restoring to normal position result.
Referring to Figure 11, Figure 11 uses JAVA/BREW mode positioning flow for B district user.This flow process may further comprise the steps:
Step 1, MS initiate Location Request StartPositioningProcessRequest to GMPC, issue PDSN earlier;
Step 2, PDSN send to GMPC with Location Request StartPositioningProcessRequest;
Step 3, GMPC judge whether it is the local area user, find it is not the local area user, transmit; If the local area user then handles at local area, processing procedure is same as the prior art;
Step 4, GMPC are transmitted to MPC2 with Location Request StartPositioningProcessRequest;
Step 5, MPC2 send authentication message to user/CP database, check whether the MS and the corresponding mobile station TSR of initiating the location are authorized to;
Step 6, user/CP database return authenticating result to MPC2;
Step 7, MPC2 use GEOPOSREQ message to send Location Request to position determining entity;
Step 8, MPC2 send location response StartPositioningProcessResponse to GMPC;
Step 9, GMPC send location response StartPositioningProcessResponse to MS, activate MS and initiate the IS801 session; StartPositioningProcessResponse issues PDSN earlier;
Step 10, service PDSN send to MS with location response StartPositioningProcessResponse;
IS801 interacting message between step 11, position determining entity and the MS carries out the calculating of MS position.Position determining entity in the end in IS801 message, is directly beamed back MS with real position data;
Finish step 12, location, and position determining entity uses geoposreq to send positioning result to MPC2, MPC2 storage targeted customer current location information.
Another preferred embodiment of the present invention is referring to Figure 12, and Figure 12 is the schematic network structure based on the TCP/IP movable positioning system of the present invention's second preferred embodiment.The movable positioning system of present embodiment comprises two, and MPC can be by regional classification, and for example, the user of southern Da Qu opens an account on MPC1 124, and the user of northern Da Qu opens an account on MPC2 125; Local CP1, CP2 only is connected respectively on local MPC1, the MPC2, and each CP can provide service for national user; Various places PDSN126,127 is connected with local MPC, and the virtual address map on the GPSOne mobile phone is become the address of local MPC.Promptly the StartPositioningProcessRequest of all mobile phones transmissions is dealt into earlier on the current on-site MPC of cellphone subscriber; Link to each other based on TCP/IP by the MPC interconnect interface between the MPC.Be peer-to-peer between the MPC of each Da Qu.
The difference of the present embodiment and first preferred embodiment is: all MPC need all to have that CP inserts, MS message inserts, the function of forwards, realize interconnected between MPC jointly, and the user provides service for the whole network.
MPC is the segment management user according to number, needs to dispose the CDMA Subscriber Number section and the MPC mapping table in the whole nation on each MPC.When user mobile phone is initiated StartPositioningProcessRequest, no matter user ascription area wherein, the PDSN of user position is routed to user's request on the MPC (inserting MPC) on visit ground, MPC judges whether it is the local user according to the called number section, if the local user, then directly local the processing.If not, the MPC that then is transmitted to dialed field handles.
Insert MPC for the L1 request of sending, message is resolved from CP, if location oneself then judges whether it is the local user according to number segment, if the local user, then directly local the processing.If not the local user, the MPC that then L1 is transmitted to user attaching handles.
Insert MPC for the L1 request of sending, message resolved,, then handle respectively according to the calling and called location if locate other people from CP:
If calling and called are all in this locality, then directly handle this locality.
If calling and called, then directly are transmitted to the MPC of user attaching all not local and handle.If caller is called not in this locality in this locality, then the L1 request is transmitted to the MPC of called ownership, on called ownership MPC, need to initiate calling subscriber's authentication request to the MPC of caller ownership.After the caller authentication is passed through, carry out positioning processing again behind called authentication and the privacy authentication.At last the L1 location response is returned to the MPC of access.Insert MPC and receive after the L1 response, L1 is responded be transmitted to CP again.
If caller is called in this locality not in this locality, then the MPC to the caller ownership initiates calling subscriber's authentication request.After the caller authentication is passed through, carry out the GPSOne location again.At last, the L1 response is returned to CP.
Present embodiment carries out following processing to whole network data: in the positioning flow, if the whole network user data is arranged on the MPC of various places, CP and calling and called user's Authentication Authorization is all finished on same MPC (called ownership MPC), and calling subscriber's authentication request message can be omitted; Various places MPC only belongs to the user data of oneself else if, and then (calling and called) subscription authentication must be finished on the MPC of (calling and called) user attaching, the Authentication Authorization inspection of CP with MPC that CP links to each other on finish.
To divide into the MPC1 location is the A district, and the MPC2 location is the B district, lifts several concrete positioning flows second preferred embodiment is described.
Referring to Figure 13, Figure 13 uses the WAP mode positioning flow of B district CP2 for A district user.This flow process may further comprise the steps:
Step 1, A district MS initiate service request to B district CP2;
Step 2, B district CP2 send Location Request by the L1 interface to B district MPC2;
The MPC2 in step 3, B district judges by the number segment analysis whether MS is the local user, finds that MS is not the local user,
The MPC2 in step 4, B district is transmitted to Location Request the MPC1 in the A district that MS belongs to;
Step 5, B district CP2 return request-reply by the WAP mode to the user;
Step 6, A district MPC1 send authentication message to A district user/CP database, check whether initiate located subscriber is authorized to;
Step 7, A district user/CP database return authenticating result to A district MPC1;
Step 8, MS initiate Location Request StartPositioningProcessRequest to A district MPC1;
Step 9, A district MPC1 use GEOPOSREQ message to send Location Request to A district position determining entity;
Step 10, A district MPC1 send location response StartPositioningProcessResponse to MS, activate MS and initiate the IS801 session;
IS801 interacting message between step 11, position determining entity and the MS carries out the calculating of MS position;
Finish step 12, location, and position determining entity uses geoposreq to send positioning result to A district MPC1;
Step 13, A district MPC1 are transmitted to B district MPC2 with positioning result;
Step 14, B district MPC2 return the MS positional information to B district MPC2 by the L1 interface;
Step 15, MS send service request by WAP to B district CP2;
Step 16, B district CP2 return information on services by WAP and give MS, for MS provides service.
Referring to Figure 14, Figure 14 roams into the WAP mode positioning flow that the B district uses A district CP1 for A district user.This flow process may further comprise the steps:
Step 1, A district MS roam into the B district, propose service request by the WAP mode to A district CP1;
Step 2, A district CP1 send Location Request by the L1 interface to A district MPC1;
Step 3, A district CP1 return request-reply by the WAP mode to MS;
Step 4, A district MPC1 send authentication message to user/CP database, check whether initiation located subscriber and CP are authorized to;
Step 5, A district user/CP database return authenticating result to MPC1;
Step 6, MS initiate Location Request StartPositioningProcessRequest to B district MPC2;
Step 7, B district MPC2 judge by the number segment analysis whether MS is the local user, find that MS is not the local user, and then execution in step 8
Step 8, StartPositioningProcessRequest is transmitted to A district MPC1;
Step 9, A district MPC1 use GEOPOSREQ message to send Location Request to position determining entity;
Step 10, A district MPC1 send StartPositioningProcessResponse to B district MPC2;
Step 11, B district MPC2 send location response StartPositioningProcessResponse to MS, activate MS and initiate the IS801 session;
IS801 interacting message between step 12, position determining entity and the MS carries out the calculating of MS position;
Finish step 13, location, and position determining entity uses geoposreq to send positioning result to A district MPC1;
Step 14, A district MPC1 return the MS positional information to A district CP1 by the L1 interface;
Step 15, MS send service request by WAP to A district CP1;
Step 16, A district LCS client return information on services by WAP and give MS, for MS provides service.
Referring to Figure 15, Figure 15 roams into the WAP mode positioning flow that the B district uses B district CP2 for A district user.This flow process may further comprise the steps:
Step 1, A district MS roam into the B district, initiate service request to B district CP2;
Step 2, B district CP2 send Location Request by the L1 interface to B district MPC2;
The MPC2 in step 3, B district judges by the number segment analysis whether MS is the local user, finds that MS is not the local user, then execution in step 4,
The MPC2 in step 4, B district is transmitted to Location Request the MPC1 in the A district that MS belongs to;
Step 5, B district CP2 return request-reply by the WAP mode to the user;
Step 6, A district MPC1 send authentication message to A district user/CP database, check whether initiate located subscriber is authorized to;
Step 7, A district user/CP database return authenticating result to A district MPC1;
Step 8, MS initiate Location Request StartPositioningProcessRequest to B district MPC2;
The MPC2 in step 9, B district judges by the number segment analysis whether MS is the local user, finds that MS is not the local user, then execution in step 10,
The MPC2 in step 10, B district is transmitted to StartPositioningProcessRequest the MPC1 in the A district that MS belongs to;
Step 11, A district MPC1 use GEOPOSREQ message to send Location Request to position determining entity;
Step 12, A district MPC1 send StartPositioningProcessResponse to B district MPC2;
Step 13, B district MPC2 send location response StartPositioningProcessResponse to MS, activate MS and initiate the IS801 session;
IS801 interacting message between step 14, position determining entity and the MS carries out the calculating of MS position;
Finish step 15, location, and position determining entity uses geoposreq to send positioning result to A district MPC1;
Step 16, A district MPC1 are transmitted to B district MPC2 with positioning result;
Step 17, B district MPC2 return the MS positional information to B district CP2 by the L1 interface;
Step 18, MS send service request by WAP to B district CP2;
Step 19, B district CP2 return information on services by WAP and give MS, for MS provides service.
Referring to Figure 16, the A district user that Figure 16 initiates for network side uses B district CP2 location A district user's positioning flow.This flow process may further comprise the steps:
Step 1, B district CP2 send Location Request by the L1 interface protocol to B district MPC2;
Step 2, B district MPC2 carry out the CP authentication;
Step 3, B district user/CP database return authenticating result to B district MPC2;
Whether step 4, B district MPC2 judge the called subscriber in this locality by the number segment analysis to called number, find that the called subscriber is not the local user, and then execution in step 5
Step 5, B district MPC2 are transmitted to Location Request the MPC1 in the A district of called subscriber's ownership;
Step 6, A district MPC1 are to the authentication of called MS, and the promoter carries out authorization check to inquiry;
Step 7, A district user/CP database return authenticating result to A district MPC1;
Step 8, A district MPC1 use GEOPOSREQ message to send Location Request to position determining entity;
Step 9, A district MPC1 send a special MT (Mobile Termination) short message by sms center to called MS, require MS that the inquiry promoter is made authorization check and triggered location process;
Step 10, called MS send MO (Mobile Origination) short message to A district MPC1, agree the location;
IS801 interacting message between step 11, position determining entity and the MS carries out the calculating of MS position;
Step 12, position determining entity use geoposreq to A district MPC1 restoring to normal position result;
Step 13, A district MPC1 store location result, and only reply the MO short message what receive MS, after information representation user wherein agreed to be positioned, just the message by meeting the L1 interface protocol was to the MPC2 in B district restoring to normal position result;
Step 14, B district MPC2 pass through the L1 interface to CP2 restoring to normal position result.
Referring to Figure 17, the A district user that Figure 17 initiates for network side uses A district CP1 location B district user's positioning flow.Wherein, the user among the MPC1/CP database is the database of non-whole network data.This flow process may further comprise the steps:
Step 1, A district CP1 send Location Request by the L1 interface protocol to A district MPC1;
Step 2, A district MPC1 carry out the CP authentication;
The user in step 3, A district/CP database returns authenticating result to A district MPC;
Step 4, A district MPC1 are by the number segment analysis to called number, and whether judge called is the local user, find that the called subscriber is not the local user, and then execution in step 5.
Step 5, A district MPC1 are transmitted to Location Request on the MPC2 in B district of called subscriber's ownership
Step 6, B district MPC2 carry out the number segment analysis to the inquiry promoter, judge whether caller is the local user, find that the calling subscriber is not the local user, and then execution in step 7.
Step 7, B district MPC2 initiate the caller authentication request to the MPC1 in the A district of caller ownership;
Step 8, A district MPC1 carry out the caller authentication;
The user in step 9, A district/CP database returns authenticating result to A district MPC1;
Step 10, A district MPC1 return to authenticating result the MPC2 in B district;
Step 11, B district MPC2 carry out called MS authentication and privacy inspection;
Step 12, B district user/CP database return authenticating result to B district MPC2;
Step 13, B district MPC2 use GEOPOSREQ message to send Location Request to position determining entity;
Step 14, B district MPC2 send a special MT (Mobile Termination) short message by sms center to called MS, require MS that the inquiry promoter is made authorization check and triggered location process;
Step 15, called MS send MO (Mobile Origination) short message to B district MPC2, agree the location;
IS801 interacting message between step 16, position determining entity and the MS carries out the calculating of MS position;
Step 17, position determining entity use geoposreq to B district MPC2 restoring to normal position result;
Step 18, B district MPC2 store location result, and only reply the MO short message what receive MS, after information representation user wherein agrees to be positioned, just to the MPC1 in A district restoring to normal position result;
The MPC1 in step 19, A district passes through the L1 interface to the CP1 in A district restoring to normal position result.
Referring to Figure 18, the A district user that Figure 18 initiates for network side uses B district CP2 location B district user's positioning flow.Wherein, the user among the MPC2/CP database is the database of non-whole network data.This flow process may further comprise the steps:
Step 1, B district CP2 send Location Request by the L1 interface protocol to B district MPC2;
Step 2, B district MPC2 carry out the number segment analysis to the inquiry promoter, judge whether caller is the local user, find that the calling subscriber is not the local user, and then execution in step 3.
Step 3, B district MPC2 initiate the caller authentication request to the MPC1 in the A district of caller ownership;
Step 4, A district MPC1 carry out the caller authentication;
The user in step 5, A district/CP database returns authenticating result to A district MPC1;
Step 6, A district MPC1 return to authenticating result the MPC2 in B district;
Step 7, B district MPC1 carry out the CP authentication, called MS authentication and privacy inspection;
Step 8, B district user/CP database return authenticating result to B district MPC2;
Step 9, B district MPC2 use GEOPOSREQ message to send Location Request to position determining entity;
Step 10, B district MPC2 send a special MT (Mobile Termination) short message by sms center to called MS, require MS that the inquiry promoter is made authorization check and triggered location process;
Step 11, called MS send MO (Mobile Origination) short message to B district MPC2, agree the location;
IS801 interacting message between step 12, position determining entity and the MS carries out the calculating of MS position;
Step 13, position determining entity use geoposreq to B district MPC2 restoring to normal position result;
Step 14, B district MPC2 store location result, and only reply the MO short message what receive MS, after information representation user wherein agrees to be positioned, just to the MPC1 in A district restoring to normal position result.
The user of various places/CP database is not a whole network data in the above network side positioning flow.The user of various places/CP database can make the user/CP database of various places become whole network data by the method for data sync.The method of data sync is identical with the method that general database carries out data sync.
Referring to Figure 19, the A district user that Figure 19 initiates for network side uses A district CP1 location B district user's positioning flow.In this flow process A district user/CP database synchronization B district user/CP data of database.This flow process may further comprise the steps:
Step 1, A district CP1 send Location Request by the L1 interface protocol to A district MPC1;
Step 2, A district MPC1 are by the number segment analysis to called number, and whether judge called is the local user, find that the called subscriber is not the local user, and then execution in step 3
Step 3, A district MPC1 are transmitted to Location Request on the MPC2 in B district of called subscriber's ownership
Step 4, B district MPC2 carry out called MS authentication and privacy inspection, and carry out calling subscriber's authentication;
Step 5, B district user/CP database return authenticating result to B district MPC2;
Step 6, B district MPC2 use GEOPOSREQ message to send Location Request to position determining entity;
Step 7, B district MPC2 send a special MT (Mobile Termination) short message by sms center to called MS, require MS that the inquiry promoter is made authorization check and triggered location process;
Step 8, called MS send MO (Mobile Origination) short message to B district MPC2, agree the location;
IS801 interacting message between step 9, position determining entity and the MS carries out the calculating of MS position;
Step 10, position determining entity use geoposreq to B district MPC2 restoring to normal position result;
Step 11, B district MPC2 store location result, and only reply the MO short message what receive MS, after information representation user wherein agrees to be positioned, just to the MPC1 in A district restoring to normal position result;
The MPC1 in step 12, A district passes through the L1 interface to the CP1 in A district restoring to normal position result.
Referring to Figure 20, Figure 20 roams into the JAVA/BREW mode positioning flow in B district for A district user.This flow process may further comprise the steps:
Step 1, A district MS roam into the B district, initiate Location Request StartPositioningProcessRequest to B district MPC2;
Step 2, B district MPC2 judge whether to be the local user by the number segment analysis, find that the user is not the local user, execution in step 3.
Step 3, B district MPC2 are transmitted to StartPositioningProcessRequest the A district MPC1 of MS ownership;
Step 4, A district MPC1 send authentication message to A district user/CP database, check whether initiation located subscriber and corresponding mobile station TSR are authorized to;
Step 5, A district user/CP database return authenticating result to A district MPC1;
Step 6, A district MPC1 use GEOPOSREQ message to send Location Request to position determining entity;
Step 7, A district MPC1 send StartPositioningProcessResponse to B district MPC2;
Step 8, B district MPC2 send location response StartPositioningProcessResponse to MS, activate MS and initiate the IS801 session;
IS801 interacting message between step 9, position determining entity and the MS carries out the calculating of MS position.Require position determining entity in the end in IS801 message, directly real position data is beamed back MS.
Step 10, position determining entity use geoposreq to A district MPC1 restoring to normal position result.
By two above-mentioned embodiment as seen, the present invention has realized interconnecting and the strange land location positioning between a plurality of MPC, and implementation is simple, does not need MPC is carried out bigger change.

Claims (17)

1, a kind of based on the TCP/IP movable positioning system, comprise position determining entity PDE, packet data serving node PDSN, mobile positioning center MPC, MPC links to each other respectively with PDSN with code division multiple access CDMA signaling network, PDSN links to each other with the base station sub-system BSS/ Packet Control Function PCF of cdma system, it is characterized in that:
The MPC that this system comprises is a plurality of; Connect by ICP/IP protocol between each MPC; Described PDE links to each other with all MPC by ICP/IP protocol, and MPC links to each other by ICP/IP protocol with the CP of location service provider equipment;
Arbitrary MPC is used for after receiving Location Request, and whether the mobile station MS that judgement need be positioned is the local user, if not, then Location Request is forwarded to the MPC of described MS ownership;
The MPC of described MS ownership is used for sending Location Request to PDE, by interacting message, carries out the MS position calculation between MS and the PDE; PDE returns to the MPC that this MS belongs to positioning result with location response, finishes the user location.
2, movable positioning system as claimed in claim 1 is characterized in that: among described a plurality of MPC, comprise a Gateway Mobile Location Center (GMPC), PDSN all in the described movable positioning system link to each other with GMPC; Provide the CP of the provider equipment of the whole network location service to link to each other with GMPC.
3, movable positioning system as claimed in claim 1 is characterized in that: local PDSN links to each other with the MPC of this locality.
4, movable positioning system as claimed in claim 1 is characterized in that: transmit mobile station MS between described each MPC or/and the positioning request information that CP sends.
5, movable positioning system as claimed in claim 4 is characterized in that: further send the roaming authentication message between described each MPC.
6, a kind of location positioning method based on TCP/IP is characterized in that: application rights requires 1 described movable positioning system to position, and this method comprises the position fixing process that Client-initiated position fixing process and network side are initiated;
Described Client-initiated position fixing process may further comprise the steps:
Y1, mobile station MS send Location Request by PDSN to the MPC that starts;
Y2, the MPC that starts judge whether this MS is the local user after receiving Location Request, if then carry out the local positioning flow of Client-initiated; Otherwise this Location Request is transmitted to the MPC of this MS ownership;
After the MPC of Y3, this MS ownership receives this Location Request, send Location Request to PDE, and respond to the MS restoring to normal position by start MPC and PDSN;
By interacting message, carry out the MS position calculation between Y4, MS and the PDE;
Y5, PDE return to the MPC that this MS belongs to positioning result with location response, finish the user location;
The position fixing process that described network side is initiated may further comprise the steps:
W1, network side CP send Location Request to the MPC that starts that links to each other with this CP;
W2, the MPC that starts judge whether called MS is the local user after receiving Location Request, if then carry out the local positioning flow that network side is initiated; Otherwise this Location Request is transmitted to the MPC of called MS ownership;
After the MPC of W3, called MS ownership receives this Location Request, judge whether called MS is identical with caller MS, if identical then direct execution in step W4, otherwise after caller MS carried out authentication, execution in step
Figure C031539310003C1
The MPC of W4, called MS ownership carries out authentication to CP and the called MS initiated; If authentication is passed through, execution in step W5 then, otherwise finish;
The MPC of W5, called MS ownership sends Location Request to PDE, and triggers the called MS localization;
By interacting message, carry out the MS position calculation between W6, called MS and the PDE;
W7, PDE return to positioning result the MPC of called MS ownership with location response;
The MPC of W8, called MS ownership by the CP that the MPC that starts returns to initiation, finishes the user location with location response.
7, location positioning method as claimed in claim 6 is characterized in that, when the user adopts the WAP mode to position, is carrying out the described step Y1 execution following steps that take a step forward:
Y01, MS send the WAP service request to the CP of its selection, and CP receives that this request back returns the WAP service request to MS and reply, and asks the user to confirm to serve simultaneously; And to the initial MPC transmission Location Request that links to each other with this CP;
Y02, the MPC that starts judge whether this MS is the local user after receiving Location Request, if then directly CP and MS are carried out authentication; Otherwise this Location Request is transmitted to the MPC that this MS belongs to, and the MPC of this MS ownership carries out authentication to CP and MS;
Y03, user enter step Y1 after confirming service;
After carrying out described step Y5, further carry out following steps:
The MPC of Y51, this MS ownership returns to CP with location response by the MPC that starts with positioning result;
Y52, this MS send the WAP service request to the CP of its selection, and CP receives that this request then returns the WAP service request to MS and reply, for MS provides location-based service.
8, location positioning method as claimed in claim 7 is characterized in that, when the user adopted the WAP mode to position, the local positioning flow of the described Client-initiated of step Y2 may further comprise the steps:
Y21, the MPC that starts respond to the MS restoring to normal position, and send Location Request to PDE;
Carry out the IS801 interacting message between Y22, MS and the PDE, carry out the MS position calculation;
Y23, PDE return to the MPC that starts with positioning result with location response, finish the user location.
9, location positioning method as claimed in claim 6 is characterized in that, when the user adopted the JAVA/BREW mode to position, the local positioning flow of the described Client-initiated of step Y2 may further comprise the steps:
Y21, the MPC that starts carry out authentication to this MS, if authentication is passed through, send Location Request then to the response of MS restoring to normal position, and to PDE; Otherwise finish;
Carry out the IS801 interacting message between y22, MS and the PDE, carry out the MS position calculation;
Y23, PDE return to the MPC that starts with positioning result with location response, finish the user location.
10, location positioning method as claimed in claim 6 is characterized in that, the local positioning flow that the described network side of step W2 is initiated may further comprise the steps:
W21, the MPC that starts carry out authentication to CP and the called MS initiated; If authentication is passed through then execution in step W22, otherwise finish;
W22, the MPC that starts send Location Request to PDE, and send Mobile Termination short message triggering called MS localization to called MS; Called MS is returned mobile originated short message and is agreed the location;
Carry out the IS801 interacting message between W23, called MS and the PDE, carry out the MS position calculation;
W24, PDE return to the MPC that starts with positioning result with location response;
W25, the MPC that starts return to the CP of initiation with location response, finish the user location.
11, location positioning method as claimed in claim 6 is characterized in that, when the user adopted the JAVA/BREW mode to position, described step Y3 further comprised:
The MPC of this MS ownership carries out authentication to this MS, if authentication is passed through, then sends Location Request to PDE, and responds to the MS restoring to normal position; Otherwise finish.
12, as claim 6,7 or 11 described location positioning methods, it is characterized in that described step Y3 further comprises: after MS receives location response, initiate the IS801 session to position determining entity;
The described information interaction of step Y4 is the IS801 information interaction.
13, location positioning method as claimed in claim 12 is characterized in that, when the user adopted the JAVA/BREW mode to position, described position determining entity in the end in IS801 message, directly returned to MS with real position data.
14, location positioning method as claimed in claim 6 is characterized in that, step W3 is described to carry out authentication to caller MS and may further comprise the steps:
The MPC of W31, called MS ownership judges whether caller MS is the local user, if then caller MS is carried out authentication; Otherwise the MPC of called MS ownership sends caller roaming authentication request to the MPC of caller MS ownership;
The MPC of W32, caller MS ownership carries out authentication to caller MS;
The MPC of W33, caller MS ownership returns caller roaming Authentication Response to the MPC of called MS ownership;
If W34 caller MS roaming authentication is passed through, execution in step W4 then, otherwise finish.
15, location positioning method as claimed in claim 6 is characterized in that, step W3 is described to carry out authentication to caller MS and may further comprise the steps:
W31, the database that called MS is belonged to the database of MPC and caller MS ownership MPC in advance carry out data sync;
The MPC of W32, called ownership carries out authentication to caller MS;
If W33 caller authentication is passed through, execution in step W4 then, otherwise finish.
16, location positioning method as claimed in claim 6 is characterized in that, the described triggering called MS of step W5 localization may further comprise the steps:
The MPC of W51, called MS ownership sends the Mobile Termination short message to called MS and triggers the called MS localization;
W52, called MS are returned mobile originated short message and are agreed the location.
17, location positioning method as claimed in claim 6 is characterized in that, this method further comprises: a gateway MPC is set in this navigation system, and the Location Request that all MS send all sends to gateway MPC.
CNB031539319A 2003-08-20 2003-08-20 A kind of method based on TCP/IP movable positioning system and location positioning thereof Expired - Fee Related CN100563136C (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CNB031539319A CN100563136C (en) 2003-08-20 2003-08-20 A kind of method based on TCP/IP movable positioning system and location positioning thereof

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CNB031539319A CN100563136C (en) 2003-08-20 2003-08-20 A kind of method based on TCP/IP movable positioning system and location positioning thereof

Publications (2)

Publication Number Publication Date
CN1585319A CN1585319A (en) 2005-02-23
CN100563136C true CN100563136C (en) 2009-11-25

Family

ID=34597923

Family Applications (1)

Application Number Title Priority Date Filing Date
CNB031539319A Expired - Fee Related CN100563136C (en) 2003-08-20 2003-08-20 A kind of method based on TCP/IP movable positioning system and location positioning thereof

Country Status (1)

Country Link
CN (1) CN100563136C (en)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101714999B (en) * 2008-10-07 2012-08-08 英业达股份有限公司 System for detecting current location of users and providing customized information services and method thereof
CN101640837B (en) * 2009-09-09 2012-02-15 中国电信股份有限公司 Method for increasing position success ratio and mobile position center (MPC) equipment
CN101977334B (en) * 2010-10-13 2013-07-03 镇江和邦通信技术有限公司 Single-soldier backpack emergency communication system
CN105472728A (en) * 2014-09-11 2016-04-06 阿尔卡特朗讯 Positioning method, device and system for wireless network

Non-Patent Citations (6)

* Cited by examiner, † Cited by third party
Title
cdma2000 1x网络中引入新的智能业务——定位业务. 林志宏.电信科学，第4期. 2002
cdma2000 1x网络中引入新的智能业务——定位业务. 林志宏.电信科学，第4期. 2002 *
CDMA位置服务技术的发展. 蒋纯等.电信科学，第10期. 2002
CDMA位置服务技术的发展. 蒋纯等.电信科学，第10期. 2002 *
CDMA无线定位技术与组网方案的研究. 杨宁等.现代电信科技，第7期. 2003
CDMA无线定位技术与组网方案的研究. 杨宁等.现代电信科技，第7期. 2003 *

Also Published As

Publication number Publication date
CN1585319A (en) 2005-02-23

Similar Documents

Publication Publication Date Title
US6922562B2 (en) System and method for providing information services to cellular roamers
EP1650988B1 (en) A disposal method of location information request in the location service
CA2283886C (en) Communicating packet data with a mobile station roaming within an incompatible mobile network
US20080233931A1 (en) Location Service Method and System
CA2785052C (en) Method and system for obtaining location information regarding a device in a wireless network
JP2002503932A (en) Changing the service profile of a mobile subscriber
CA2525485A1 (en) Apparatus and method for providing location information
CN100388830C (en) A position locating system and method
CN101361392A (en) Terminal status discovery in secure user plane location positioning procedure
EP1014619A1 (en) Communication network and method for charging and accounting
CN102027765A (en) System and method for using subscriber role information in a mobile communication system
TW201611539A (en) A server for providing wireless telecommunication services to a wireless transmit/receive unit and the method thereof, and a wireless transmit/receive unit and the method thereof
CN101160986B (en) Method for locating mobile terminal
CN101147363A (en) Optimum selection of a communication network in the location area of a terminal
RU2005129268A (en) SYSTEM AND METHOD FOR ESTABLISHING PACKET DATA CALLS OF TYPE "MOBILE STATION TO MOBILE STATION" BETWEEN MOBILE STATIONS IN VARIOUS WIRELESS NETWORKS
EP1189473A2 (en) Prepaid mobile communcations services using signalling transfer point
US20040198362A1 (en) Procedure and system for setting up a telecommunication connection
CN100563136C (en) A kind of method based on TCP/IP movable positioning system and location positioning thereof
CN103947161A (en) Method and apparatus for configuring service settings for a mobile subscriber
CN100372441C (en) Mobile terminal positioning method
CN100397941C (en) Method for locating roaming target user in location service
EP1076463A2 (en) Supporting network in telecommunications systems
EP2359610A1 (en) Providing access to a gprs network
KR100775538B1 (en) Method and system for providing location based service for roaming subscriber
CN100551136C (en) A kind of method and apparatus of supporting location service access mobile positioning center

Legal Events

Date Code Title Description
C06 Publication
PB01 Publication
C10 Entry into substantive examination
SE01 Entry into force of request for substantive examination
C14 Grant of patent or utility model
GR01 Patent grant
CF01 Termination of patent right due to non-payment of annual fee

Granted publication date: 20091125

Termination date: 20140820

EXPY Termination of patent right or utility model