Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
In the prior art, the response process for the user location service request is shown in fig. 1:
step 101, the application function AF sends a location service request to the network open function NEF, that is, initiates a location information request for the target ue, such as sending an LCS service request message, where the message carries a user identifier.
Step 102, the NEF invokes a subscription data query Request of the unified data management UDM, for example, invokes a numm _ SDM _ Get Request, to obtain location privacy configuration data of the user corresponding to the user identifier.
Step 103, the UDM returns subscription data containing the location privacy configuration of the user to the NEF, for example, returns a numm _ SDM _ Get Response.
Step 104, the NEF performs authorization determination on whether the AF can request the location service of the user based on the location privacy configuration of the user returned by the UDM, for example, determines whether the location privacy configuration is set to allow providing the location service for the application.
Step 105, if the authorization is successful, the NEF invokes a Location providing Request of the gateway mobile Location center GMLC, for example, invokes an Ngmlc _ Location _ providedlocation Request, to Request the GMLC to provide the Location service of the user.
Step 106, the GMLC invokes a subscription data query Request of the UDM to obtain the location privacy configuration data of the user, for example, invokes a numm _ SDM _ Get Request.
Step 107, the UDM returns subscription data containing the location privacy configuration of the user to the GMLC, such as returning a numm _ SDM _ Get Response.
Step 108, the GMLC performs privacy check according to the location privacy configuration returned by the UDM, for example, determines whether the location query process needs to notify the user, whether the location query operation has geographical location restriction, and the like, and executes a corresponding location query operation according to the privacy check result.
Step 109, after the GMLC queries the Location of the user, returns a Location query result to NEF, for example, returns Ngmlc _ Location _ providedlocation Response.
Step 110, the NEF sends a location service response to the AF, such as sending an LCS service response message, i.e. returns the queried user location information.
Therefore, in the location service authorization process in the prior art, NEF and GMLC need to respectively execute the subscription data query operation of UDM, and the interaction operation is cumbersome and the efficiency is low.
Referring to fig. 2, fig. 2 is a flowchart of a processing method of a location service according to an embodiment of the present invention, for a network open function NEF, as shown in fig. 2, the processing method of the location service includes the following steps:
step 201, in the case of receiving a location service request carrying a first identifier sent by an application function AF, obtaining location privacy configuration of a second identifier corresponding to the first identifier from a unified data management UDM.
In this embodiment of the present invention, the application function AF may be a network node in a communication system, the AF may be configured to provide a location service function for some applications, such as a location service function for providing a map application, the unified data management UDM may be a platform for centrally managing data in a unified manner, and the network open function NEF may verify and authorize and assist the application function AF in providing a location service. And the NEF, AF, and UDM may each be a functional entity or a virtual device running on the platform.
The receiving of the location service request with the first identifier sent by the AF may be that the AF sends a location service request with an identifier of a certain user equipment to the NEF, for example, sends an LCS service request message to obtain location information of the user equipment, so that the NEF receives the location service request sent by the AF.
The location service request may carry a first identifier, where the first identifier may be an identifier of a user equipment initiating the location service request, and the first identifier may be a single user identifier or a group of user identifiers, that is, multiple user identifiers, or may be one user group identifier or multiple user group identifiers. That is, the NEF may receive a location service request of a user equipment or a plurality of user equipments.
After receiving the location service Request, the NEF may obtain, according to the first identifier, a location privacy configuration of a corresponding second identifier from the UDM, that is, may initiate a subscription data Request to the UDM, for example, may invoke a numm _ SDM _ Get Request, where the UDM may centrally store subscription data including location privacy configurations of different applications of different user equipment, and the location privacy configuration of an application of a certain user equipment may refer to location privacy data configured for the application by the user equipment, and the location privacy data may specifically include, for example: whether the application function is allowed to access the location of the user device, whether the user needs to be notified, whether user verification is required, a geographical location range within which location services may be allowed, and the like.
The second identifier may be different according to different situations of the first identifier, and specifically, when the first identifier is a single user identifier, the second identifier corresponding to the first identifier may be the same as the first identifier; when the first identifier is a plurality of user identifiers, such as a group of user identifiers, the corresponding second identifier may be part or all of the user identifiers in the group of user identifiers; when the first identifier is a user group identifier, the corresponding second identifier may be the same as the user group identifier, or may be part or all of the group member identifiers in the user group identifier; when the first identifier is a plurality of user group identifiers, the corresponding second identifier may be a part or all of the plurality of user group identifiers, or may also be a part or all of group member identifiers of the part or all of the plurality of user group identifiers.
The above manner of obtaining the location privacy configuration of the second identifier may also include the following two different cases:
one is that the second identifier is at least one user identifier, and a single user identifier is associated with one location privacy configuration, so that the location privacy configurations associated with the single user identifiers can be obtained respectively, for example, if the second identifier is 3 user identifiers, then the location privacy configurations associated with each user identifier can be obtained respectively, and the UDM returns 3 location privacy configurations to the NEF;
alternatively, the second identifier is at least one user group identifier, and one user group identifier is associated with one location privacy configuration, so that the location privacy configurations associated with one user group identifier can be obtained respectively, for example, 1 user group identifier is used, then the location privacy configurations associated with the user group identifier can be obtained, and the UDM returns 1 location privacy configuration to the NEF.
The UDM may query the subscription data corresponding to the second identifier and including the location privacy configuration, specifically, if the second identifier includes one or more user identifiers, the subscription data corresponding to each user identifier may be queried respectively, and if the second identifier includes one or more user identifiers, the UDM may query the group member identifiers in each group of user identifiers respectively first, and then query the subscription data corresponding to each group member identifier respectively.
After querying the subscription data corresponding to the second identifier, the UDM may return the location privacy configuration of the second identifier to the NEF, for example, return a numm _ SDM _ Get Response, that is, may return the location privacy configuration of each user identifier included in the second identifier.
After obtaining the location privacy configuration of the second identifier, the NEF may perform authorization determination on whether the AF may request the location service of the user equipment corresponding to the user identifier based on the location privacy configuration of each user identifier, and if it is determined that the AF is set to "allow access" for the AF in the location privacy configuration, it may determine that the authorization is successful and send a location providing request to the GMLC, otherwise, it may refuse to provide the location service to the AF.
Optionally, the first identifier includes at least one user identifier or at least one user group identifier, where the user identifier is used to indicate a user; the user group identification is used to indicate a user group comprising at least one user.
In this embodiment, the first identifier may include at least one user identifier or at least one user group identifier, that is, the first identifier may be one user identifier for indicating one user or the first identifier includes a plurality of user identifiers for indicating a plurality of users, the first identifier may also be one user group identifier for indicating one user group, which includes one or more users, or the first identifier includes a plurality of user group identifiers for indicating a plurality of user groups, each of which may include one or more users, according to different application scenarios.
In this way, the AF may directly carry a single or multiple user identifiers in the location service request sent to the NEF according to actual requirements, or form different users into a user group, and carry one or multiple user group identifiers in the location service request, so as to request to obtain location services of one or multiple user devices at a time.
Optionally, in a case that the first identifier includes the at least one user identifier, the second identifier includes all or part of the at least one user identifier; or
In case the first identity comprises the at least one user group identity, the second identity comprises: and part or all of the at least one user group identifier, or all or part of the first group member identifiers, wherein the first group member identifiers are group member identifiers corresponding to part or all of the user group identifiers.
In this embodiment, the second identifier corresponding to the first identifier may include all or part of the first identifier, and specifically, the second identifier may be a single user identifier when the first identifier is the single user identifier or includes multiple user identifiers, or may be part or all of the multiple user identifiers.
Or, in a case that the first identifier includes at least one user group identifier, the second identifier may be a part or all of the user group identifiers, or may also be a part or all of the group member identifiers, and more specifically, in a case that the first identifier includes one user group identifier, the second identifier may be the one user group identifier, or a part of or all of the group member identifiers in the user group identifier; and under the condition that the first identifier comprises a plurality of user group identifiers, the second identifier is part or all of the plurality of user group identifiers, or part or all of the group member identifiers in part of the user group identifiers corresponding to the group member identifiers, or part or all of the group member identifiers in all of the user group identifiers corresponding to the group member identifiers.
In this way, the NEF may obtain, according to actual needs, location privacy configurations of some or all of the users indicated by the first identifier from the UDM, and further obtain location services of one or more user devices.
That is, in conjunction with the above-mentioned alternative embodiments, during the process of initiating the user location service request, there may be a plurality of different situations, which are respectively illustrated below:
the first method is as follows: the first identifier is a single user identifier, the second identifier is the same as the first identifier, namely, the AF sends a location service request carrying the single user identifier to the NEF, the NEF obtains the location privacy configuration of the single user identifier from the UDM, and the UDM returns the location privacy configuration associated with the single user identifier to the NEF;
the second method comprises the following steps: the first identifier is at least two user identifiers, the second identifier is a part of or all of the at least two user identifiers, that is, the AF sends a location service request carrying the at least two user identifiers to the NEF, the NEF obtains location privacy configurations of the part of or all of the at least two user identifiers from the UDM, and the UDM returns the location privacy configurations associated with each of the part of or all of the at least two user identifiers to the NEF;
the third method comprises the following steps: the first identification is a user group identification, the second identification is the same as the first identification, namely AF sends a location service request carrying a user group identification to NEF, NEF obtains location privacy configuration of the user group identification from UDM, UDM returns the location privacy configuration associated with the user group identification to NEF;
the method is as follows: the first identifier is a user group identifier, the second identifier is part of or all of the group member identifiers in the user group identifier, that is, the AF sends a location service request carrying a user group identifier to the NEF, the NEF obtains location privacy configurations of part or all of the group member identifiers in the user group identifier from the UDM, and the UDM returns the location privacy configurations associated with each group member in part or all of the group member identifiers in the user group identifier to the NEF;
the fifth mode is as follows: the first identifier is at least two user group identifiers, the second identifier is a part of or all of the at least two user group identifiers, that is, the AF sends a location service request carrying the at least two user group identifiers to the NEF, the NEF obtains location privacy configurations of the part of or all of the at least two user group identifiers from the UDM, and the UDM returns the location privacy configurations associated with each of the part of or all of the at least two user group identifiers to the NEF;
the method six: the first identification is at least two user group identifications, and the second identification is part or all of the group member identifications corresponding to part of the user group identifications in the at least two user group identifications, or part or all of the group member identifications corresponding to all of the user group identifications; in this case, the AF sends a location service request carrying at least two user group identifiers to the NEF, the NEF obtains location privacy configurations of part or all of the group member identifiers in part or all of the at least two user group identifiers from the UDM, and the UDM returns the location privacy configurations associated with part or all of the group member identifiers in part or all of the at least two user group identifiers or each of the group member identifiers in all of the group member identifiers to the NEF.
Step 202, sending a location providing request to a GMLC, where the location providing request carries the second identifier and the application configuration information, and the application configuration information is the configuration information associated with the AF in the location privacy configuration.
In this step, in order to further obtain Location information of the user equipment corresponding to the second identifier, so as to provide Location service to the AF, a Location providing Request may be sent to the GMLC after obtaining the Location privacy configuration of the second identifier, for example, the Ngmlc _ Location _ provisionlocation Request is called, and the second identifier and the application configuration information may be carried in the Location providing Request, where the application configuration information is configuration information associated with the AF in the Location privacy configuration, so that the GMLC may directly perform privacy check on the user equipment corresponding to the second identifier according to the second identifier and the application configuration information, and need not perform a subscription data query operation to the UDM again.
Since each location privacy configuration of the location privacy configurations of the second identifier may include configuration information of a plurality of applications, in order to avoid resource waste and improve location service response efficiency, only the configuration information associated with the AF in each location privacy configuration may be carried in the location providing request, for example, a certain location privacy configuration includes configuration information of application 1, application 2, application 3, application 4, and application 5, and an application associated with the AF is application 1, and then only the configuration information of application 1 included in the location privacy configuration may be carried in the location providing request.
Optionally, the application configuration information includes part or all of configuration information associated with the AF in the location privacy configuration.
That is to say, in this manner, the location providing request may carry all configuration information associated with the AF in the location privacy configuration, so that the GMLC may perform a comprehensive privacy check on the user equipment corresponding to the second identifier according to all configuration information associated with the AF in the location privacy configuration, or the location providing request may also carry only part of configuration information associated with the AF in the location privacy configuration, where the part of configuration information may be privacy configuration information of which a user is interested or important privacy configuration information, so that the GMLC may perform some important privacy checks only on the user equipment corresponding to the second identifier according to part of configuration information associated with the AF in the location privacy configuration, to further improve location response efficiency.
Optionally, the application configuration information includes at least one of the following:
first indication information, the first indication information being used for: indicating whether a location service for a user corresponding to the second identity notifies the user;
second indication information for: indicating whether the user verification is required for the location service of the user corresponding to the second identifier;
geographical location range information indicating a geographical location range in which location services are allowed.
In this embodiment, the application configuration information may include first indication information, which is used to indicate whether the user is notified of the location service for the user corresponding to the second identifier, so that by carrying the first indication information in the location providing request, the GMLC may know whether the user needs to be notified in the process of querying the location, and further when the first indication information indicates that the user needs to be notified, the GMLC may notify the user when a location response is provided, for example, a location service enabling icon is displayed in a status display bar of a user device, and when the first indication information indicates that the user does not need to be notified, the GMLC may not notify the user when a location response is provided.
The application configuration information may also include second indication information used to indicate whether the user verification is required for the location service of the user corresponding to the second identifier, so that the GMLC may know whether the user verification needs to be notified in the process of providing the location service by carrying the second indication information in the location providing request, and may further notify the user verification first when the second indication information indicates that the user verification is required, for example, perform pop-up window reminding on a user equipment interface to determine whether to approve location service, so as to ensure user privacy security, and may not notify the user verification when the second indication information indicates that the user verification is not required.
The application configuration information may also include geographical location range information for indicating a geographical location range in which location service is allowed, so that by carrying the geographical location range information in the location providing request, the GMLC may know whether the current location of the user is within the geographical location range in which location service is allowed, and may further provide a location service response if the user is currently within the geographical location range in which location service is allowed, and reject a location service response if the user is not currently within the geographical location range in which location service is allowed.
The application configuration information may further include various combinations or all of the above first indication information, second indication information, and geographic location range information, so that the GMLC may perform privacy checking and provide corresponding location services based on the application configuration information.
Thus, after receiving the location providing request sent by the NEF, the GMLC may perform privacy check based on the application configuration information, for example, determine whether the location query process requires notification of the user, whether the user needs verification, whether the location query operation has a geographic location limit, and the like based on information such as whether the user needs to be notified, an indication of whether the user needs verification, and a geographic location range in which location service is allowed to be provided in the application configuration information, so as to obtain a corresponding check result, for example, obtain a check result that the user needs to be notified, the user needs verification, the location query operation has a geographic location limit, and the like.
Then, the GMLC may perform, based on the check result, a Location query operation corresponding to the second identifier, that is, query Location information of the user equipment corresponding to the second identifier to obtain a corresponding Location query result, and after obtaining the Location information of the user equipment corresponding to the second identifier, the GMLC may return the Location query result to the NEF, that is, provide a Location Response result, for example, return an Ngmlc _ Location _ providedlocation Response.
Finally, the NEF may return the location query result to the AF, that is, send a location service response to the AF, for example, send an LCS service response message, so that the ue corresponding to the second identifier may enable a location service in its corresponding application.
In the method for processing location service in this embodiment, when receiving a location service request carrying a first identifier sent by an AF, an NEF obtains location privacy configuration of a second identifier corresponding to the first identifier from the UDM, and sends a location providing request carrying the second identifier and configuration information associated with the AF in the obtained location privacy configuration to a GMLC, so that the GMLC can directly perform privacy check based on the information carried in the request without inquiring the configuration information associated with the AF from the UDM again, thereby saving part of operations in a location service response and further improving response efficiency of a wireless communication system in providing location service.
Referring to fig. 3, fig. 3 is a flowchart of a location service processing method according to an embodiment of the present invention, for a GMLC, and as shown in fig. 3, the location service processing method includes the following steps:
step 301, receiving a location providing request sent by the NEF, where the location providing request carries the second identifier and the application configuration information.
Step 302, responding to the location providing request, and performing privacy check based on the application configuration information to obtain a check result.
And 303, performing a location query operation corresponding to the second identifier based on the checking result.
It should be noted that, this embodiment is used as an implementation of the GMLC corresponding to the method embodiment shown in fig. 2, and specific implementation thereof may refer to relevant descriptions in the method embodiment shown in fig. 2, and may achieve the same beneficial effects, and in order to avoid repeated descriptions, the detailed description of this embodiment is not repeated.
Optionally, the application configuration information includes part or all of configuration information associated with the AF in the location privacy configuration.
Optionally, the application configuration information includes at least one of the following:
first indication information, the first indication information being used for: indicating whether a location service for a user corresponding to the second identity notifies the user;
second indication information for: indicating whether the user verification is required for the location service of the user corresponding to the second identifier;
geographical location range information indicating a geographical location range in which location services are allowed.
Optionally, the second identifier includes at least one user identifier or at least one user group identifier.
For the description of the above alternative embodiment, reference may be made to the description of the related embodiment in the method embodiment shown in fig. 2, and the same beneficial effects may be achieved, and in order to avoid repetition, no further description is provided herein.
The following describes, with reference to fig. 4 and 5, a specific implementation of an embodiment of the present invention:
as shown in fig. 4, an interaction process of initiating and responding to a location service between devices is described by taking a user identifier as an example:
step 401, the AF sends a location service request to the NEF, and carries the user identifier.
Step 402, the NEF invokes a subscription data query request of the UDM to obtain location privacy configuration data of the user corresponding to the user identifier.
Step 403, the UDM returns subscription data containing the location privacy configuration of the user to the NEF.
Step 404, NEF makes an authorization determination on whether the AF can request the location service of the user based on the location privacy configuration of the user returned by the UDM, for example, determines whether the location privacy configuration is set as "allowed" for the application.
Step 405, after the authorization is successful, the NEF invokes a location providing request of the GMLC, and carries the obtained part or all of the location privacy configuration information related to the application, such as an indication whether the user needs to be notified or verified, the geographical location range information of the location service allowed, and the like.
Step 406, the GMLC performs privacy check according to the received location privacy configuration information related to the application, for example, determines whether the location query process needs to notify the user, or whether the user needs to check, or whether the location query operation has geographic location restrictions, and executes a corresponding location query operation according to the privacy check result.
Step 407, after the GMLC queries the location of the user, returning a location query result to the NEF.
Step 408, the NEF sends a location service response to the AF.
As shown in fig. 5, an interaction process of initiating and responding to a location service between devices is described by taking a group of user identifiers or user group identifiers as an example:
step 501, the AF sends a location service request to the NEF, and carries a group of user identifiers or user group identifiers.
Step 502, NEF invokes a subscription data query request of UDM, if the user identifier is a group of user identifiers, queries the subscription data corresponding to each user identifier, and if the user identifier is a group of user identifiers, queries a group of user identifiers included in the user group identifiers first, and then queries the subscription data corresponding to each user identifier.
Step 503, the UDM returns subscription data containing the location privacy configuration of the user to the NEF, where each user identifier returns corresponding subscription data.
Step 504, NEF makes an authorization determination based on the location privacy configuration of each user as to whether the application can request the location service of the user, such as determining whether the application is set to "allowed" in the location privacy configuration.
Step 505, after the authorization is successful, the NEF invokes a location providing request of the GMLC, carries the user identifiers that pass the authorization, and carries, for each user identifier that passes the authorization, corresponding obtained partial or all location privacy configuration information related to the application, such as an indication whether the user needs to be notified or verified, geographical location range information that allows location service, and the like.
Step 506, the GMLC performs privacy check on each user identifier according to the received location privacy configuration information related to the application, for example, determines whether the location query process needs to be notified to the user, whether user verification is needed, whether the location query operation has geographic location restrictions, and the like, and executes a corresponding location query operation according to a privacy check result.
Step 507, after the GMLC inquires the location of each user, returning the location inquiry result to the NEF.
Step 508, the NEF sends a location service response to the AF.
Referring to fig. 6, fig. 6 is a schematic structural diagram of a network open function NEF according to an embodiment of the present invention, and as shown in fig. 6, the network open function 600 includes:
an obtaining module 601, configured to obtain, from a unified data management UDM, a location privacy configuration of a second identifier corresponding to a first identifier when receiving a location service request carrying the first identifier sent by an application function AF;
a sending module 602, configured to send a location providing request to a GMLC, where the location providing request carries the second identifier and application configuration information, and the application configuration information is configuration information associated with the AF in the location privacy configuration.
Optionally, the application configuration information includes part or all of configuration information associated with the AF in the location privacy configuration.
Optionally, the application configuration information includes at least one of the following:
first indication information, the first indication information being used for: indicating whether a location service for a user corresponding to the second identity notifies the user;
second indication information for: indicating whether the user verification is required for the location service of the user corresponding to the second identifier;
geographical location range information indicating a geographical location range in which location services are allowed.
Optionally, the first identifier includes at least one user identifier or at least one user group identifier, where the user identifier is used to indicate a user; the user group identification is used to indicate a user group comprising at least one user.
Optionally, in a case that the first identifier includes the at least one user identifier, the second identifier includes all or part of the at least one user identifier; or
In case the first identity comprises the at least one user group identity, the second identity comprises: and part or all of the at least one user group identifier, or all or part of the first group member identifiers, wherein the first group member identifiers are group member identifiers corresponding to part or all of the user group identifiers.
The NEF provided by the embodiment of the present invention can implement each process in the method embodiment shown in fig. 2, and can obtain the same beneficial effects, and is not described herein again to avoid repetition.
Referring to fig. 7, fig. 7 is a schematic structural diagram of a gateway mobile location center GMLC according to an embodiment of the present invention, and as shown in fig. 7, a gateway mobile location center 700 includes:
a receiving module 701, configured to receive a location providing request sent by an NEF, where the location providing request carries a second identifier and application configuration information;
a privacy checking module 702, configured to perform privacy checking based on the application configuration information in response to the location providing request, so as to obtain a checking result;
a location query module 703, configured to perform a location query operation corresponding to the second identifier based on the check result.
Optionally, the application configuration information includes part or all of configuration information associated with the AF in the location privacy configuration.
Optionally, the application configuration information includes at least one of the following:
first indication information, the first indication information being used for: indicating whether a location service for a user corresponding to the second identity notifies the user;
second indication information for: indicating whether the user verification is required for the location service of the user corresponding to the second identifier;
geographical location range information indicating a geographical location range in which location services are allowed.
Optionally, the second identifier includes at least one user identifier or at least one user group identifier.
The NEF provided by the embodiment of the present invention can implement each process in the method embodiment shown in fig. 2, and can obtain the same beneficial effects, and is not described herein again to avoid repetition.
Referring to fig. 8, fig. 8 is a schematic structural diagram of another network-side device according to an embodiment of the present invention. As shown in fig. 8, the network-side device 800 includes: a processor 801, a memory 802, a bus interface 803, and a transceiver 804, wherein the processor 801, the memory 802, and the transceiver 804 are all connected to the bus interface 803.
In this embodiment of the present invention, the network side device 800 further includes: a computer program stored in the memory 802 and operable on the processor 801, which computer program when executed by the processor 801 implements the following steps when the network-side device 800 is a NEF:
under the condition of receiving a location service request which is sent by an Application Function (AF) and carries a first identifier, obtaining location privacy configuration of a second identifier corresponding to the first identifier from a Unified Data Management (UDM);
and sending a location providing request to a GMLC, wherein the location providing request carries the second identifier and application configuration information, and the application configuration information is configuration information associated with the AF in the location privacy configuration.
Optionally, the application configuration information includes part or all of configuration information associated with the AF in the location privacy configuration.
Optionally, the application configuration information includes at least one of the following:
first indication information, the first indication information being used for: indicating whether a location service for a user corresponding to the second identity notifies the user;
second indication information for: indicating whether the user verification is required for the location service of the user corresponding to the second identifier;
geographical location range information indicating a geographical location range in which location services are allowed.
Optionally, the first identifier includes at least one user identifier or at least one user group identifier, where the user identifier is used to indicate a user; the user group identification is used to indicate a user group comprising at least one user.
Optionally, in a case that the first identifier includes the at least one user identifier, the second identifier includes all or part of the at least one user identifier; or
In case the first identity comprises the at least one user group identity, the second identity comprises: and part or all of the at least one user group identifier, or all or part of the first group member identifiers, wherein the first group member identifiers are group member identifiers corresponding to part or all of the user group identifiers.
When the network-side device 800 is a GMLC, the computer program implements the following steps when executed by the processor 801:
receiving a position providing request sent by NEF, wherein the position providing request carries a second identifier and application configuration information;
responding to the position providing request, and performing privacy check based on the application configuration information to obtain a check result;
and performing position query operation corresponding to the second identifier based on the checking result.
Optionally, the application configuration information includes part or all of configuration information associated with the AF in the location privacy configuration.
Optionally, the application configuration information includes at least one of the following:
first indication information, the first indication information being used for: indicating whether a location service for a user corresponding to the second identity notifies the user;
second indication information for: indicating whether the user verification is required for the location service of the user corresponding to the second identifier;
geographical location range information indicating a geographical location range in which location services are allowed.
Optionally, the second identifier includes at least one user identifier or at least one user group identifier.
An embodiment of the present invention further provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the computer program implements each process of the location service processing method embodiment shown in fig. 2 or fig. 3, or when the computer program is executed by the processor, the computer program implements each process of the location service processing method embodiment shown in fig. 3, and can achieve the same technical effect, and in order to avoid repetition, details are not repeated here. The computer-readable storage medium may be a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal (such as a mobile phone, a computer, a server, an air conditioner, or a network device) to execute the method according to the embodiments of the present invention.
While the present invention has been described with reference to the embodiments shown in the drawings, the present invention is not limited to the embodiments, which are illustrative and not restrictive, and it will be apparent to those skilled in the art that various changes and modifications can be made therein without departing from the spirit and scope of the invention as defined in the appended claims.