Charging system and method for positioning service

[0034] In order to enable those skilled in the art to better understand the solutions of the embodiments of the present invention, the embodiments of the present invention will be further described in detail below with reference to the accompanying drawings and implementation manners.

[0035] The embodiment of the present invention adopts an event-based charging method to realize charging in different positioning scenarios according to the characteristics of positioning services that are different from general services (such as voice services and video services).

[0036] First of all, refer to image 3 The structure diagram of the charging system according to the embodiment of the present invention is shown as follows:

[0037]The system includes: a location server (Location Server, LS) 31, a location controller (Location Controller, LC) 32, and a charging server. The charging server can be the AAA server 33 in the figure, or it can be the AAA server 33 in the figure. The online charging (pre-paid) server (Pre-Paid Server, PPS) 34 in, of course, can also include an AAA server 33 and PPS 34 at the same time. LS31 includes a positioning server charging function unit (LS Charging Function, LS CF) 311, and LC32 includes a positioning controller charging function unit (LC Charging Function, LC CF) 321.

[0038] Each entity in the system will be described separately below.

[0039] LS, which can be located in the CSN, is the external interface of the network and is responsible for receiving and processing positioning requests (the positioning request can include the identification of the LCS client (LCS Client), the identification of the target terminal and the QoS (Quality of Service) of the positioning result. ) Request and other parameters), and forward the legal positioning request to the appropriate LC to locate the target. LS31 can exist alone in the CSN.

[0040] LC, which can be located in the ASN, is the processing and control center of the positioning function in the ASN. It is mainly responsible for receiving the positioning request of the LS31, positioning the target terminal, calculating the positioning result and returning it. LC can be a functional unit, and can be located in the ASN GW at this time, or it can exist alone.

[0041] LS CF: Execute the LS positioning and charging function, collect charging information related to the positioning service for the client that initiates the positioning request and the target terminal to be positioned, create a Usage DataRecord (UDR), and send the UDR data record To the AAA server. If it is an online charging user, before the LS initiates a positioning request to the access network, the LS CF is responsible for applying for a quota from the PPS. After the positioning is completed, if the QoS level of the actual positioning result is lower than the QoS level requested by the user, so that the allocated quota is left, the LS CF shall request the PPS to return the remaining balance.

[0042] LC CF: Detect positioning messages in the ASN part, collect positioning and charging information, create UDR data records, and send the data records to the AAA server of the network to which the ASN belongs. The UDR data record serves as the basis for charging the LS when providing positioning data measurement services to the LS.

[0043] AAA server, authentication, authorization, and accounting server, including offline accounting system of WiMAX network.

[0044] PPS, online charging server, as the online charging system of WiMAX network, for general session services, PPS is responsible for allocating and managing user session quotas. For positioning services, PPS needs to respond to positioning quota requests and allocate positioning quotas. The quota indicates whether the positioning service requested by the user this time is allowed.

[0045] In the system of the embodiment of the present invention, independent charging is performed between the LS and the access network, and the UDR data generated by the LS CF on the LS and the UDR data generated by the LC CF on the LC can be transmitted to the same charging The server can also be transmitted to a different accounting server.

[0046] The charging records generated on the LC CF of the ASN need to be sent to the AAA server corresponding to the ASN, and the charging records generated by the LS CF on the LS can be sent to the AAA server or other charging systems.

[0047] Using the system of the foregoing embodiment, charging for positioning services in the WiMAX network can be implemented. The charging may include charging for the terminal requesting positioning information, and may also include charging for the target terminal to be located. Of course, according to the operation The charging strategy of the provider may not charge the target terminal to be located. Moreover, by using the system of this embodiment, two modes of offline charging and online charging can be realized: if the terminal requesting positioning information and the target terminal to be located are not the same entity, and both require to be charged, the calculation of both The charging modes can be inconsistent, that is, one adopts offline charging mode and the other adopts online charging mode.

[0048] If the user requesting positioning information is an online charging user, before the LS initiates a positioning request to the access network, the LS CF needs to apply for a quota from the PPS. When PPS receives a quota request from LS CF, PPS needs to allocate a certain quota to the user based on the QoS requirements of the service requested by the user, the user's positioning service subscription information, and the user's account balance. The quota indicates the location of the user's request. Whether the business is allowed. After the LS CF obtains the quota, the LS performs further positioning operations. After the positioning is over, if the allocated quota is left, LS CF requests the PPS to return the user's remaining quota.

[0049] The system of the embodiment of the present invention can correlate the charging of the positioning service with the position accuracy and time response of the positioning result. For example, the positioning result can be distinguished according to the positioning accuracy, time response and other parameters of different QoS levels, so that the positioning meter The amount of the fee is related to the QoS level of the positioning result. The higher the QoS level, the greater the charging amount. During the positioning process, LS CF and LC CF respectively record the QoS level requested by the user and the QoS level of the positioning result measured by the final network. If the actual QoS level of the positioning result is lower than the QoS level requested by the user, it will be based on the actual positioning result. The QoS level charges users or not, depending on whether the positioning request indicates that the QoS level of the positioning result is allowed to be degraded when the QoS level of the positioning result of the positioning request cannot be reached. For online charging users, this is required at this time Return the remaining quota of the user; otherwise, the user is charged according to the QoS level requested by the user.

[0050] Generally, the positioning process can generally be divided into the following three types according to the initiation of the positioning request:

[0051] 1. MO-LR (Mobile Originated Location Request), the positioning scenario where the terminal initiates a positioning request, refers to the positioning method in which the terminal obtains its own geographic location information or sends its own location information to another LCS Client;

[0052] 2. MT-LR (Mobile Terminated Location Request), the location request is initiated by an LCSClient to request the location information of a target MS;

[0053] 3. NI-LR (Network Induced Location Request), the scenario where the network initiates a location request, is generally suitable for emergency location of the terminal in the emergency location service.

[0054] The embodiment of the present invention provides a method for charging a positioning service, which not only can realize offline charging for the positioning service, but also can realize online charging. For the above three different positioning procedures, the offline charging and online charging procedures for the positioning service in the method of the embodiment of the present invention will be described below.

[0055] 1. Offline billing

[0056] In the non-roaming scenario, during the positioning process in the MO-LR mode, the LS collects the charging information for the positioning service initiated by the MS through its charging function unit (LS CF), and generates usage data records; the LC on the ASNGW detects in the ASN The locating service is used to collect charging information through the charging function unit (LC CF) to generate usage data records; LS and LC send the generated usage data records to the AAA server, or to other charging servers to realize LS (Or its provider) and ASN (or its operator) independent offline charging for positioning services.

[0057] Reference Figure 4 The charging process for offline positioning in MO-LR mode in a non-roaming scenario in the method of the embodiment of the present invention includes the following steps:

[0058] 1. The MS initiates its own location request to the LC (Location Controller) through the LCS request message (LCS Invoke);

[0059] 2a. The charging function unit (LC CF) located on the LC initiates the creation of UDR (Usage Data Record). LC CF begins to collect billing information and create UDR data; this UDR data record should include but is not limited to the following: the identification of the originator of the positioning request, the identification of the LCS Client or other entity to which the positioning result is to be sent, the positioning type, and the positioning request Initiation time, UDR record creation time (optional), requested positioning service QoS parameters (such as positioning accuracy, response time, etc., requested positioning QoS level, etc.), periodic positioning information (optional, periodic frequency and number of times or Total time) and other content;

[0060] 3. LC forwards the LCS request message to the selected LS (Location Server);

[0061] 4a. LS processes the positioning request message, such as checking the user's subscription information. The charging function unit (LS CF) located in LS begins to collect charging information and create UDR data; this UDR data record should include but not limited to the following: the identification of the originator of the positioning request, the LCS Client to which the positioning result is to be sent, or other The identity of the entity, the type of positioning, the time when the positioning request was initiated, the time when the UDR record was created (optional), the requested positioning service QoS parameters (such as positioning accuracy, response time, etc., requested positioning QoS level, etc.), periodic positioning information ( Optionally, the cycle frequency and number of times or total time), etc.;

[0062] 5. LS sends a location request (Location Request) to LC according to the QoS information of the location request;

[0063] 6. The LC determines the positioning method and the data required for positioning according to the QoS of the positioning request, the positioning capability of the network and other information, and interacts with the MS to complete the data measurement required for positioning;

[0064] 7. LC calculates the positioning result according to the positioning measurement data, and sends a location report (LocationReport) to the LS, and reports the positioning calculation result to the LS;

[0065] 8. LS sends the positioning result information to LCS Client;

[0066] 9. After receiving the positioning result information, the LCS Client will reply with an acknowledgement message (Location InformationAck), indicating that it has successfully received the positioning result;

[0067] 10. LS sends the location result to LC by returning location result message (Location Result Return);

[0068] 11. After LC receives the location result message sent by LS, it sends a location result confirmation message (Location ResultAck) to LS, indicating that it has successfully received the location result; this step can be omitted;

[0069] 4b. Corresponding to 4a, LS CF completes the collection of charging information in LS. LS CF can regenerate a new UDR record but associated with the UDR in 4a, or add a new one to the UDR generated in 4a. Record item. The UDR record should include but is not limited to: the final positioning result data, the positioning method used in the actual positioning process, the QoS parameters of the positioning result, etc.;

[0070]4c. LS CF reports the generated UDR data to the AAA server;

[0071] 12. LC sends the final location result to MS by returning location result message (Location Result Return);

[0072] 13. The MS replies to the positioning result confirmation message, indicating that the positioning result has been successfully received; in order to avoid the user from refusing to send the confirmation message after receiving the positioning result to achieve the purpose of evading charging, this step can be omitted;

[0073] 2b. Corresponding to 2a, the LC CF completes the collection of positioning and charging information in the LC. The LC CF can regenerate a new UDR record but associated with the UDR in 2a, or add a new UDR record to the UDR generated in 2a. Of records. The UDR record should include but is not limited to: the final positioning result data, the positioning method used in the actual positioning process, the QoS level of the positioning result, etc.;

[0074] 2c. The LC CF reports the generated UDR data to the AAA server.

[0075] If the MS indicates periodic positioning requirements and information in the positioning request, steps 5-13 need to be repeated according to the number of periodic positioning indicated in the periodic positioning information or the total duration. UDR data generated in LS and LC can be performed in all requirements After the periodic positioning is completed, it will be sent to the charging server uniformly, or sent to the charging server after a set number of intervals.

[0076] In the roaming scenario, during the positioning process in MO-LR mode, H-LS (Home-LS, home location server), CF on V-LS and CF on V-LC (Visited-LC, visited location controller) It is necessary to collect charging information separately and establish independent charging records.

[0077] Reference Figure 5 In the method shown in the embodiment of the present invention, the offline positioning and charging process in the MO-LR mode in the roaming scenario is similar to the charging process in the non-roaming scenario, and each step is briefly described as follows:

[0078] 1. MS initiates its own location request to LC;

[0079] 2a. LC CF initiates UDR creation, collects charging information and establishes UDR data records;

[0080] 3. LC forwards the location request message to V-LS;

[0081] 4a. V-LS processes positioning request messages, such as checking user subscription information. This process may require interaction between V-LS and H-LS; LS CF located in V-LS starts to collect charging information and create UDR data;

[0082] 5. V-LS sends a location request (Location Request) to LC;

[0083] 6. The LC determines the positioning method and the data required for positioning according to the QoS of the positioning request and the positioning capability of the network, and interacts with the MS to complete the data measurement required for positioning;

[0084] 7. LC calculates the positioning result according to the positioning measurement data, and sends a location report (LocationReport) to V-LS, and reports the positioning calculation result to V-LS;

[0085] 8. V-LS sends the positioning result information to H-LS;

[0086] 9a. H-LS processes positioning request messages, such as checking user subscription information, etc.; CF located in H-LS starts to collect billing information and create UDR data;

[0087] 10. H-LS sends the location result information to the LCS Client through the Location Information Report;

[0088] 11. After receiving the location result information, the LCS Client will reply with a location information confirmation message (LocationInformation Ack), indicating that it has successfully received the location result;

[0089] 12. After the H-LS receives the positioning information from the LCS Client and confirms the success, it sends the positioning result to the V-LS by returning a location result message (Location Result Return);

[0090] 13. After V-LS receives the location result message sent by H-LS, it sends a location result confirmation message (Location ResultAck) to H-LS, indicating that it has successfully received the location result, this step can be omitted;

[0091] 9b. Corresponding to 9a, the CF located in the H-LS completes the collection of charging information in the LS. The CF can regenerate a new UDR record but associated with the UDR in 9a, or in the UDR generated in 9a Add new record items. The UDR record should include but is not limited to: the final positioning result data, the positioning method used in the actual positioning process, and the QoS parameters of the positioning result;

[0092] 9c. The CF located in the H-LS reports the generated UDR data to the AAA server;

[0093] 14. The V-LS sends the location result to the LC through the location result message (Location Result Return);

[0094] 15. After LC receives the location result message sent by V-LS, it sends an acknowledgement message (Location ResultAck) to V-LS, indicating that it has successfully received the location result. This step can be omitted;

[0095] 4b. Corresponding to 4a, the CF located in the V-LS completes the collection of charging information in the V-LS. The CF can regenerate a new UDR record but associated with the UDR in 4a, or it can be generated in 4a New record items are added in UDR. The UDR record should include but is not limited to: the final positioning result data, the positioning method used in the actual positioning process, and the QoS parameters of the positioning result;

[0096] 4c. The CF located in the V-LS reports the generated UDR data to the AAA server;

[0097] 16. LC sends the final location result to MS by returning location result message (Location Result Return);

[0098] 17. The MS replies with a positioning result confirmation message, indicating that the positioning result has been successfully received; in order to prevent the user from refusing to send the confirmation message after receiving the positioning result to achieve the purpose of evading charging, this step can be omitted;

[0099] 2b. Corresponding to 2a, the LC CF located in the LC completes the collection of positioning and charging information in the LC. The LC CF can regenerate a new UDR record but associated with the UDR in 2a, or the UDR generated in 2a Add new record items in. The UDR record should include but is not limited to: the final positioning result data, the positioning method used in the actual positioning process, and the QoS parameters of the positioning result;

[0100] 2c. The LC CF reports the generated UDR data to the AAA server.

[0101] In the non-roaming scenario, during the positioning process in the MT-LR mode, the LS collects the charging information for the positioning service initiated by the LCS Client through its charging function unit (LSCF), and generates usage data records; the LC on the ASN GW detects the ASN The locating service within the charging function unit (LC CF) collects charging information to generate usage data records; LS and LC send the generated usage data records to the AAA server, which can be different charging servers to realize LS( (Or its provider) and ASN (or its operator) independent offline charging for positioning services.

[0102] Reference Figure 6 The offline positioning and charging process in MT-LR mode in a non-roaming scenario in the method of the embodiment of the present invention includes the following steps:

[0103] 1. The LCS Client initiates a positioning service request to the LS. The request contains information such as the identification of the target MS being located, the accuracy of the positioning result, and response time requirements;

[0104] 2a. LS processes the positioning request message, such as checking the user's subscription information and verifying the privacy of the request. The LS CF located in the LS begins to collect billing information and create UDR data; this UDR data record should include but not limited to the following: the identification of the location request initiator, the identification of the MS being located, the location type, the time when the location request was initiated, UDR Record creation time (optional), requested positioning service QoS parameters (such as positioning accuracy, response time, etc., requested positioning QoS level, etc.), periodic positioning information (optional, periodic frequency and number of times or total time), etc. ;

[0105] 3. The LS sends a location request to the LC located in the ASN GW;

[0106] 4a. The LC CF located in the LC initiates the creation of the UDR. LC CF begins to collect billing information and create UDR data; this UDR data record should include but is not limited to the following: the identification of the location request initiator, the identification of the located MS, the location type, the time when the location request was initiated, the creation of the UDR record Time (optional), requested positioning service QoS parameters (such as positioning accuracy, response time, etc., requested positioning QoS level, etc.), periodic positioning information (optional, periodic frequency and number of times or total time), etc.;

[0107] 5. LC and MS interact to complete the data measurement required for positioning;

[0108] 6. LC calculates the positioning result according to the positioning measurement data, and reports the positioning calculation result to LS;

[0109] 7. After the LS receives the location result information, it responds with a location confirmation message (Location Ack), indicating that it has successfully received the location result. This step can be omitted;

[0110] 4b. Corresponding to 4a, the LC CF located in the LC completes the collection of positioning and charging information within the LC. The LC CF can regenerate a new UDR record but associated with the UDR in 4a, or the UDR generated in 4a Add new record items in. The UDR record should include but is not limited to: the final positioning result data, the positioning method used in the actual positioning process, and the QoS parameters of the positioning result;

[0111] 4c. LC CF reports the generated UDR data to the AAA server;

[0112] 8. LS sends a positioning report message to the LCS Client, which carries the positioning result;

[0113] 9. LCS Client replies to the positioning report confirmation message, indicating that the positioning result has been successfully received; in order to prevent the user from refusing to send the confirmation message after receiving the positioning result to achieve the purpose of evading charging, this step can be omitted;

[0114] 2b. Corresponding to 2a, the CF located in the LS completes the collection of charging information in the LS. The CF can regenerate a new UDR record but associated with the UDR in 2a, or add a new UDR record to the UDR generated in 2a. Of records. The UDR record should include but is not limited to: the final positioning result data, the positioning method used in the actual positioning process, and the QoS parameters of the positioning result;

[0115]2c. LS CF reports the generated UDR data to the AAA server.

[0116] If the LCS Client indicates the periodic positioning requirements and information in the positioning request, steps 5-9 need to be repeated according to the periodic positioning times or the total duration indicated in the periodic positioning information. The UDR data generated in LS and LC can be used in all requirements. After the periodic positioning is completed, it will be sent to the charging server uniformly, or sent to the charging server after a set number of intervals.

[0117] In the roaming scenario, in the MT-LR mode positioning process, H-LS (Home-LS, home location server), V-LS (Visited-LS, visited location server) on the LS CF and V-LC (Visited- LC, visit location controller) LC CF needs to collect charging information separately and establish independent charging records. The detailed process is similar to the above and will not be repeated here.

[0118] The positioning process initiated by the network (NI-LR mode) is generally suitable for emergency positioning services. In the positioning process, LS collects charging information through its charging function unit (LS CF) and generates usage data records; LC uses its records The charge function unit (LC CF) collects charging information and generates usage data records; LS and LC send the generated usage data records to the AAA server to realize offline charging for positioning services.

[0119] Figure 7 The offline positioning and charging process in NI-LR mode in the method of the embodiment of the present invention is described.

[0120] The NI-LR mode positioning process is generally applied to emergency positioning services. The first is the establishment process of emergency services. In this process, the network determines the positioning server and client according to the location of the located terminal. After the emergency service is established, the emergency service Generally, there is no process of privacy checking, authentication, etc. The positioning request is directly initiated by the LS or the network, and the LC responds to the positioning request to initiate the positioning process. After the positioning is completed, the emergency service release process needs to be executed.

[0121] 2. Online billing

[0122] Different from the offline charging positioning and charging process, after the MS or LCSClient that uses online charging to charge sends a positioning request to the LS, before the LS initiates a positioning request to the access service network, the LS CF needs to apply for a quota from the PPS. When PPS receives a quota request from LS CF, PPS needs to allocate a certain quota to the user based on the QoS requirements of the service requested by the user, the user's positioning service subscription information, and the user's account balance. The quota indicates the location of the user's request. Whether the business is allowed. Only after LS CF obtains the quota, LS will perform further positioning operations. After the positioning is over, if the allocated quota is left, PPS needs to return the user's remaining quota. Similarly, if the user being located is also an online charging user, before being located, the LS related to the user being located must also query the user's balance. It is not required that both the user who initiates the positioning and the user to be positioned use online charging at the same time. One party may be an offline charging user. In this case, the offline charging user does not need to perform balance inquiry operations.

[0123] Reference Figure 8 The MO-LR mode online positioning charging process in the non-roaming scenario in the method of the embodiment of the present invention is shown:

[0124] The charging process is basically similar to the online positioning process of the MO-LR mode in the non-roaming scenario, but before the LS initiates a positioning request to the LC on the ASN GW, the LS CF must apply for a quota from the PPS. Only after obtaining the quota, the LS will further initiate a positioning request, which is reflected in steps 5 and 6 in the figure. If the final positioning result QoS level is lower than the positioning QoS level requested by the user, the LS CF needs to request the PPS to return the remaining quota, corresponding to steps 14 and 15 in the figure.

[0125] Reference Picture 9 The online positioning and charging process in the MT-LR mode in the roaming scenario in the method of the embodiment of the present invention includes the following steps:

[0126] 1. The LCS Client sends an LCS service request to R-LS (Requesting Location Server);

[0127] 2a. After the R-LS receives the location request from the LCS Client, the CF on the R-LS starts to collect charging information and create a UDR data record; this UDR data record should include but is not limited to the following content: the identification of the originator of the location request , The identification of the located MS, the location type, the time when the location request was initiated, the time when the UDR record was created (optional), the requested location service QoS parameters (such as location accuracy, response time, etc., requested location QoS level, etc.), cycle Positioning information (optional, periodic frequency and number of times or total time) and other content;

[0128] In addition, R-LS needs to query the LS and PPS corresponding to the LCS Client. The LS will also generate corresponding charging records. The LS CF on the LS is responsible for initiating a quota request message to the PPS to apply for the quota required for this positioning. To make the illustration clear, Picture 9 The LS entity is omitted in the section, only showing that the LS CF on the R-LS (actually should be on the LS corresponding to the LCS Client) to the PPS related to the LCS Client applies for positioning quota; there may be many PPS and AAA in the figure One, corresponding to different charging information collection entities or functions;

[0129] 3. The LS CF sends a Quota Request message (Quota Request) to the PPS related to the LCS Client to request a positioning quota;

[0130] 4. PPS allocates a certain quota to the user according to the QoS requirements of the service requested by the user, the user's positioning service subscription information, the user's account balance and other information. The quota indicates whether the positioning service requested by the user is allowed, and PPS sends the R-LS Return Quota Response;

[0131] 5. If the LS CF obtains the quota for this positioning, the R-LS sends an LCS routing information request message (Routing Info Request for LCS) to the AAA server to query the H-LS corresponding to the located MS;

[0132] 6. The AAA server returns an LCS routing information response message (Routing Info Response forLCS), which carries the address information of the H-LS;

[0133] 7. R-LS sends LCS service request to H-LS;

[0134] 8. H-LS checks the privacy of this positioning request to determine whether the positioned MS allows the originator of the positioning request to locate it;

[0135] 9. If the located entity is also an online charging user, the LS CF on the H-LS initiates a quota request (Quota Request) to the corresponding PPS;

[0136] 10. PPS returns a Quota Response message (Quota Response) to the LS CF on the H-LS. If the positioned user is an offline charging user or does not require charging for the positioned user, the process (9th, 10th) Step can be omitted);

[0137] 11a. The CF on the H-LS collects charging information and creates a UDR data record; this UDR data record should include but is not limited to the following: the identity of the location request initiator, the identity of the MS being located, the location type, and the location request initiated Time, UDR record creation time (optional), requested positioning service QoS parameters (such as positioning accuracy, response time, etc., requested positioning QoS level, etc.), periodic positioning information (optional, cycle frequency and number of times or total time ) And other content;

[0138] 12. If the LS CF on the H-LS obtains the quota for this positioning, the H-LS sends an LCS routing information request message (Routing Info Request for LCS) to the AAA server to query the V-LS where the MS is located ;

[0139] 13. The AAA server returns an LCS routing information response message (Routing Info Response forLCS), which carries the address information of the target terminal's visited LS (Visited-LS, V-LS);

[0140] 14. H-LS sends LCS service request to V-LS;

[0141] 15a. The CF on the V-LS collects charging information and creates UDR data; this UDR data record should include but is not limited to the following: the identification of the location request initiator, the identification of the located MS, the location type, and the time when the location request was initiated , UDR record creation time (optional), requested positioning service QoS parameters (such as positioning accuracy, response time, etc., requested positioning QoS level, etc.), periodic positioning information (optional, cycle frequency and number of times or total time) And other content;

[0142] 16. The V-LS sends a location request to the LC located in the V-ASN GW;

[0143] 17a. LC CF initiates the creation of UDR, LC CF begins to collect billing information and create UDR data; this UDR data record should include but not limited to the following: the identification of the originator of the positioning request, the identification of the located MS, the positioning type, and the positioning Request initiation time (or UDR record creation time), positioning service QoS parameters (such as positioning accuracy, response time, requested positioning QoS level, etc.), periodic positioning information (optional, periodic frequency and number of times or total time), etc. content;

[0144] 18. The LC located in the V-ASN GW determines the positioning method and the data required for positioning according to the QoS of the positioning request and the positioning capability of the network, and interacts with the MS to complete the data measurement required for positioning;

[0145] 19. The LC located in the V-ASN GW returns a positioning report to the V-LS;

[0146] 20. The V-LS sends a location report confirmation message (Location ReportAck) to the LC located in the V-ASN GW, indicating that the location result has been successfully received, and this step can also be omitted;

[0147] 17b. Corresponding to 17a, the CF located on the V-LC completes the collection of positioning and charging information within the LC. The V-LC CF can regenerate a new UDR record but associated with the UDR in 17a, or in 17a Add new record items to the UDR generated in. In addition to the content contained in the UDR in 17a, the record should also contain the final positioning result data, the positioning method used in the actual positioning process, and the QoS parameters of the positioning result;

[0148] 17c. The V-LC CF reports the generated UDR data to the AAA server;

[0149] 21. V-LS returns LCS service response message to H-LS;

[0150] 22. H-LS replies to the LCS service response confirmation, indicating that the positioning result has been successfully received; this step can also be omitted;

[0151]15b. Corresponding to 15a, the CF located on the V-LS completes the collection of positioning and billing information in the LS. The V-LS CF can regenerate a new UDR record but associated with the UDR in 15a, or in 15a Add a new record item to the UDR generated in. In addition to the content contained in the UDR in 15a, the record should also contain the final positioning result data, the positioning method used in the actual positioning process, and the QoS parameters of the positioning result;

[0152] 15c. V-LS CF reports the generated UDR data to the AAA server;

[0153] 23. H-LS returns an LCS service response message to R-LS;

[0154] 24. H-LS replies to the LCS service response confirmation message, indicating that the positioning result has been successfully received; this step can also be omitted;

[0155] 11b. Corresponding to 11a, the CF located on the H-LS completes the collection of positioning and charging information in the LS. The H-LS CF can regenerate a new UDR record but associated with the UDR in 11a, or in 11a Add a new record item to the UDR generated in. In addition to the content contained in the UDR in 11a, the record should also contain the final positioning result data, the positioning method used in the actual positioning process, and the QoS parameters of the positioning result;

[0156] 11c. The H-LS CF reports the generated UDR data to the AAA server.

[0157] 25. R-LS returns an LCS service response message to the LCS Client;

[0158] 26. The LCS Client replies to the LCS service confirmation message, indicating that the positioning result has been successfully received. In order to prevent the user from refusing to send the confirmation message after receiving the positioning result to achieve the purpose of evading charging, this step can be omitted;

[0159] 2b. Corresponding to 2a, the CF located on the R-LS completes the collection of positioning and charging information in the LS. The R-LS CF can regenerate a new UDR record but associated with the UDR in 2a, or in 2a Add a new record item to the UDR generated in. In addition to the content contained in the UDR in 2a, the record should also contain the final positioning result data, the positioning method used in the actual positioning process, and the QoS parameters of the positioning result;

[0160] 2c. The R-LS CF reports the generated UDR data to the AAA server;

[0161] 27. If the final positioning result QoS level is lower than the positioning QoS level requested by the user, R-LSCF needs to request the PPS to return the remaining quota;

[0162] 28. PPS processes the quota return request message and responds with a quota return response message;

[0163] If the LCS Client indicates the requirements and information of periodic positioning in the positioning request, steps 18-26 need to be repeated according to the number of periodic positioning or the total duration indicated in the periodic positioning information. In V-LS, H-LS, R-LS and The UDR data generated in the V-LC can be uniformly sent to the charging server after all required periodic positioning is completed, or sent to the charging server after a set number of intervals.

[0164] It can be seen from the above process that in this way, the LS CF on the H-LS corresponding to the LCS Client needs to apply for quota from the corresponding PPS. When PPS receives a quota request from LS CF, PPS needs to allocate a certain quota to the user according to the QoS requirements of the service requested by the user and the user's positioning service subscription information. Only after LS CF obtains the quota, LS will perform further positioning operations. After the positioning is over, if the allocated quota is left, PPS needs to return the user's remaining quota. Similarly, if the targeted terminal is to be charged and it is an online charging user, the LS CF on the H-LS must also apply for quota from the corresponding PPS. If the positioned user is an offline charging user or the positioned user does not require to be charged, this step can be omitted. PPS and AAA in the figure correspond to different LSs and networks.

[0165] The process of online positioning and charging in other positioning modes is similar to the above process, and will not be described in detail here.

[0166] It can be seen from the description of the foregoing embodiments that the method of the embodiment of the present invention solves the charging problem of positioning services, which is different from general services (such as voice services and video services). Independent calculations are performed between the LS and the access service network. In addition, the charging of the positioning service is related to the position accuracy and time response of the positioning result. The positioning result should be differentiated according to the positioning accuracy, time response and other parameters of different QoS levels, the amount of positioning charging and the QoS of the positioning result The level is related, the higher the QoS level, the larger the billing amount, which improves the accuracy of billing. The method of the embodiment of the present invention can not only support charging in different positioning modes, but also realize offline and/or online charging.

[0167] The system and method provided by the embodiments of the present invention are described in detail above, and specific implementations are used to illustrate the present invention. The descriptions of the above embodiments are only used to help understand the systems and methods of the present invention; Those skilled in the art, based on the idea of ​​the present invention, will have changes in the specific implementation and application scope. In summary, the content of this specification should not be construed as limiting the present invention.