Patent Description:
With continuous expansion of business modes, a current mobile communications network needs to notify a third-party device of location information of a terminal in some scenarios. For example, to determine a location of a courier, location information of a terminal of the courier needs to be sent to a third-party device of an express company through a network side device, to monitor and manage a working status of the courier in real time.

In a <NUM> network architecture, it has been currently determined that a network exposure function entity (network exposure function, NEF) serves as an interface node for providing a service for a third-party device in a mobile communications network, but currently, a terminal positioning operation service cannot be provided for the third-party device through the NEF.

In conclusion, currently, a terminal positioning operation service cannot be provided for a third-party device through a network exposure function entity.

Document <CIT> generally discloses a method and an apparatus for providing location information for narrow band Internet of Things (NB-IoT) devices in a mobile communication system.

Document <NPL> generally evaluates support of location in 5GC and focuses on comparing two currently proposed solutions, namely whether location support should be concentrated in the location management function (LMF) or split between the access and mobility management function (AMF) and LMF.

This application provides a positioning operation method, apparatus, and system, to resolve a problem that currently, a terminal positioning operation service cannot be provided for a third-party device through a network exposure function entity. In particular, there is provided a positioning operation method, an apparatus, a communications system, and a computer-readable storage medium, having the features of respective independent claims. The dependent claims relate to preferred embodiments.

Embodiments of this application provide a positioning operation method, apparatus, and system. According to the method, a location management function entity receives a first message sent by a network exposure function entity, where the first message carries first positioning operation information, and the first positioning operation information is used to request the location management function entity to perform a first positioning operation on a terminal; the location management function entity may determine positioning configuration information of the terminal, and further determine, based on the positioning configuration information of the terminal, whether the first positioning operation is allowed on the terminal; and the location management function entity may further send a third message to the network exposure function entity based on a determining result. According to the foregoing positioning operation method, the network exposure function entity can send the first message to the location management function entity, so that the location management function entity performs the first positioning operation on the terminal based on the first positioning operation information in the first message.

In the description of this application, unless otherwise stated, "a plurality" means two or more than two. In addition, it should be understood that, in the description of the embodiments of this application, terms such as "first" and "second" are merely used for distinction and description, and shall not be understood as an indication or implication of relative importance or an indication or implication of an order.

It should be noted that, the positioning operation method provided in this application may be performed by an apparatus, or the positioning operation method may be performed by a system including a connection relationship between apparatuses.

As shown in <FIG>, a positioning operation system provided in an embodiment of this application includes a location management function entity <NUM>, a network exposure function entity <NUM>, a unified data management platform <NUM>, and a third-party device <NUM>.

It should be understood that, the location management function entity in this embodiment of this application is a function entity that is in a core network and that is configured to perform location management on UE, and a function supported by the location management function entity includes one or more of the following: checking and authorizing a positioning request for a terminal, managing privacy of terminal location, and charging for a location service for the terminal. Specifically, a location management function entity in a 5th generation (the 5th generation, <NUM>) wireless communications system may be an LMF (location management function, LMF) network element. The LMF may determine location information of UE based on a request of a core network entity (for example, an access and mobility management function entity (access and mobility management function, AMF)), and provide the location information of the UE to the corresponding core network entity (for example, the AMF) that requests to position the UE, to provide a location service (location services, LCS). During implementation, the AMF may allocate at least one LMF to the UE, to provide the location service for the UE. When the UE needs to obtain location information, the UE may request the location information from the LMF through the AMF. The location management function entity in the 5th generation (the 5th generation, <NUM>) wireless communications system may alternatively be a gateway mobile location center (gateway mobile location center, GMLC) or have another name. This is not limited in this application. In future communications (for example, in a <NUM> or another network), the location management function entity may still be an LMF network element, or have another name. This is not limited in this application.

An example in which the location management function entity <NUM> is an LMF network element is used below to describe a possible structure of the location management function entity provided in this embodiment of this application.

During implementation, the LMF <NUM> for a positioning operation provided in this embodiment of this application may have a structure shown in <FIG>. The LMF <NUM> includes a transceiver <NUM>, a memory <NUM>, and a processor <NUM>. The transceiver <NUM> may be used for communication by the LMF <NUM>. The memory <NUM> stores a computer program. The processor <NUM> is configured to execute the computer program stored in the memory <NUM>, so that the LMF <NUM> implements the positioning operation method provided in the embodiment of this application. It should be noted that, a specific connection medium between the processor <NUM>, the memory <NUM>, and the transceiver <NUM> is not limited in this embodiment of this application. In this embodiment of this application, in <FIG>, an example in which the processor <NUM>, the memory <NUM>, and the transceiver <NUM> are connected to each other by using a bus <NUM> is used. The bus <NUM> is represented by using a bold line in <FIG>, and a connection manner between other components is merely described by using an example, and is not limited thereto. The bus <NUM> may be classified into an address bus, a data bus, a control bus, and the like. For ease of representation, only one bold line is used to represent the bus in <FIG>, but this does not mean that there is only one bus or only one type of bus.

The network exposure function entity in this embodiment of this application is a function entity that is in the core network and that is configured to provide an interface for a third-party device other than a network side device and UE. A network capability can be externally exposed through the network exposure function entity. Specifically, the network exposure function entity may be an NEF in a <NUM> communications system. The NEF can receive a service request of the third-party device, or the NEF sends, to the third-party device, a response message and/or service data corresponding to the service request. In future communications (for example, in a <NUM> or another network), network exposure function entity may still be an NEF network element, or have another name. This is not limited in this application.

An example in which the network exposure function entity <NUM> is an NEF network element is used below to describe a possible structure of the network exposure function entity provided in this embodiment of this application.

During implementation, the NEF <NUM> for a positioning operation provided in this embodiment of this application may have a structure shown in <FIG>. The NEF <NUM> includes a transceiver <NUM>, a memory <NUM>, and a processor <NUM>. The transceiver <NUM> may be used for communication by the NEF <NUM>. The memory <NUM> stores a computer program. The processor <NUM> is configured to execute the computer program stored in the memory <NUM>, so that the NEF <NUM> implements the positioning operation method provided in the embodiments of this application. It should be noted that, a specific connection medium between the processor <NUM>, the memory <NUM>, and the transceiver <NUM> is not limited in this embodiment of this application. In this embodiment of this application, in <FIG>, an example in which the processor <NUM>, the memory <NUM>, and the transceiver <NUM> are connected to each other by using a bus <NUM> is used. The bus <NUM> is represented by using a bold line in <FIG>, and a connection manner between other components is merely described by using an example, and is not limited thereto. The bus <NUM> may be classified into an address bus, a data bus, a control bus, and the like. For ease of representation, only one bold line is used to represent the bus in <FIG>, but this does not mean that there is only one bus or only one type of bus.

The unified data management platform in this embodiment of this application is a unified device for data storage and management in the core network. Specifically, the unified data management platform may be a UDM (unified data management) network element. In a location service for UE, the UDM may store positioning configuration information of the UE. The positioning configuration information may include content such as information indicating whether the UE enables the location service and/or information about a positioning operation that is allowed on the UE. During implementation, the information indicating whether the UE enables the location service may be represented as location service exposure setting information, and the information about the positioning operation that is allowed on the UE may be represented as content such as subscription data and privacy protection setting information of the location service. In future communications (for example, in a <NUM> or another network), the unified data management platform may still be a UDM network element, or have another name. This is not limited in this application.

An example in which the unified data management platform <NUM> is a UDM network element is used below to describe a possible structure of the unified data management platform provided in this embodiment of this application.

During implementation, the UDM <NUM> for a positioning operation provided in this embodiment of this application may have a structure shown in <FIG>. The UDM <NUM> includes a transceiver <NUM>, a memory <NUM>, and a processor <NUM>. The transceiver <NUM> may be used for communication by the UDM <NUM>. The memory <NUM> stores a computer program. The processor <NUM> is configured to execute the computer program stored in the memory <NUM>, so that the UDM <NUM> implements the positioning operation method provided in the embodiments of this application. It should be noted that, a specific connection medium between the processor <NUM>, the memory <NUM>, and the transceiver <NUM> is not limited in this embodiment of this application. In this embodiment of this application, in <FIG>, an example in which the processor <NUM>, the memory <NUM>, and the transceiver <NUM> are connected to each other by using a bus <NUM> is used. The bus <NUM> is represented by using a bold line in <FIG>, and a connection manner between other components is merely described by using an example, and is not limited thereto. The bus <NUM> may be classified into an address bus, a data bus, a control bus, and the like. For ease of representation, only one bold line is used to represent the bus in <FIG>, but this does not mean that there is only one bus or only one type of bus.

The third-party device in this embodiment of this application is a device that requests, through the NEF, core network capability exposure, and the third-party device is a device other than a network side device and UE. Specifically, the third-party device is connected to the NEF through an application interface provided by the NEF, and the NEF requests a core network device to provide a network service required by the third-party device.

It should be understood that, the third-party device in this embodiment of this application may be a terminal device or a server device. The terminal device may be a device that provides a user with voice and/or data connectivity, a handheld device having a wireless connection function, or another processing device connected to a wireless modem. The terminal device may alternatively be a wireless terminal. The wireless terminal may communicate with one or more core networks by using a radio access network (radio access network, RAN) or a next generation radio access network (Next Generation Radio Access Networks, NG-RAN). The wireless terminal may be a mobile terminal, for example, a mobile phone (or referred to as a "cellular" phone) or a computer with a mobile terminal, for example, the computer with a mobile terminal may be a portable, pocket-sized, handheld, computer built-in, or vehicle mounted mobile apparatus that exchanges languages and/or data with the radio access network. A specific type of the mobile terminal is not limited in this embodiment of this application. The server device may be a computer device that has a fixed internet protocol (internet protocol, IP) address and that is configured to provide a service for a network user.

During implementation, the third-party device <NUM> for a positioning operation provided in this embodiment of this application may have a structure shown in <FIG>. The third-party device <NUM> includes a transceiver <NUM>, a memory <NUM>, and a processor <NUM>. The transceiver <NUM> may be used for communication by the third-party device <NUM>. The memory <NUM> stores a computer program. The processor <NUM> is configured to execute the computer program stored in the memory <NUM>, so that the third-party device <NUM> implements the positioning operation method provided in the embodiments of this application. It should be noted that, a specific connection medium between the processor <NUM>, the memory <NUM>, and the transceiver <NUM> is not limited in this embodiment of this application. In this embodiment of this application, in <FIG>, an example in which the processor <NUM>, the memory <NUM>, and the transceiver <NUM> are connected to each other by using a bus <NUM> is used. The bus <NUM> is represented by using a bold line in <FIG>, and a connection manner between other components is merely described by using an example, and is not limited thereto. The bus <NUM> may be classified into an address bus, a data bus, a control bus, and the like. For ease of representation, only one bold line is used to represent the bus in <FIG>, but this does not mean that there is only one bus or only one type of bus.

In addition, during implementation, the positioning operation system provided in this embodiment of this application may further include a terminal <NUM>, a radio access network <NUM>, and an access and mobility management function entity <NUM>. The terminal <NUM> is connected to the access and mobility management function entity <NUM> through the radio access network <NUM>. In this embodiment of this application, the terminal <NUM> may be a terminal on which the third-party device <NUM> requests to perform a first positioning operation. To be specific, the third-party device <NUM> requests, through the positioning operation system provided in this embodiment of this application, to perform the first positioning operation on the terminal <NUM>.

During implementation, the terminal <NUM> may be a device having a wireless communication function, and may be deployed on land, including an indoor, outdoor, handheld, wearable, or vehicle-mounted device; or may be deployed on a water surface (for example, on a steamboat); or may be deployed in the air (for example, on a plane, a balloon, or a satellite). The terminal may be a mobile phone (mobile phone), a tablet computer (pad), a computer having a wireless receiving and sending function, a virtual reality (virtual reality, VR) terminal, an augmented reality (augmented reality, AR) terminal, a wireless terminal in industrial control (industrial control), a wireless terminal in self driving (self driving), a wireless terminal in remote medical (remote medical), a wireless terminal in a smart grid (smart grid), a wireless terminal in transportation safety (transportation safety), a wireless terminal in a smart city (smart city), a wireless terminal in a smart home (smart home), or the like; or may be user equipments (user equipment, UE), mobile stations (mobile station, MS), or terminal devices (terminal device) in various forms.

An example in which the terminal <NUM> is UE is used below to describe a possible structure of the unified data management platform provided in this embodiment of this application.

During implementation, the UE <NUM> for a positioning operation provided in this embodiment of this application may have a structure shown in <FIG>. The UE <NUM> includes a transceiver <NUM>, a memory <NUM>, and a processor <NUM>. The transceiver <NUM> may be used for communication by the UE <NUM>. The memory <NUM> stores a computer program. The processor <NUM> is configured to execute the computer program stored in the memory <NUM>, so that the UE <NUM> implements the positioning operation method provided in the embodiments of this application. It should be noted that, a specific connection medium between the processor <NUM>, the memory <NUM>, and the transceiver <NUM> is not limited in this embodiment of this application. In this embodiment of this application, in <FIG>, an example in which the processor <NUM>, the memory <NUM>, and the transceiver <NUM> are connected to each other by using a bus <NUM> is used. The bus <NUM> is represented by using a bold line in <FIG>, and a connection manner between other components is merely described by using an example, and is not limited thereto. The bus <NUM> may be classified into an address bus, a data bus, a control bus, and the like. For ease of representation, only one bold line is used to represent the bus in <FIG>, but this does not mean that there is only one bus or only one type of bus.

The access and mobility management function entity in this embodiment of this application is a core network entity that is in the core network and that provides a service for the terminal <NUM>. Specifically, the access and mobility management function entity may be an AMF network element in a <NUM> communications system. As shown in <FIG>, the AMF <NUM> may receive a registration request (Registration Request) that is sent by the UE <NUM> in a registration process, and after the UE <NUM> is registered, the AMF <NUM> may provide a service for the UE <NUM>. In future communications (for example, in a <NUM> or another network), the access and mobility management function entity may still be an AMF network element, or have another name. This is not limited in this application.

The radio access network in this embodiment of this application may be an NG-RAN. In future communications (for example, in a <NUM> or another network), the radio access network may still be an NG-RAN network element, or have another name. This is not limited in this application.

The foregoing network elements and/or entities may be network elements or devices in a hardware device, or may be software functions run on dedicated hardware, or may be instantiated virtualization functions on a platform (for example, a cloud platform). The positioning operation system shown in <FIG> is used as an example below to describe the positioning operation method provided in the embodiments of this application. The location management function entity <NUM> is an LMF network element, the network exposure function entity <NUM> is an NEF network element, the unified data management platform <NUM> is a UDM network element, the terminal <NUM> is UE, the radio access network <NUM> is an NG-RAN, and the access and mobility management function entity is an AMF.

As shown in <FIG>, a positioning operation method provided in an embodiment of this application includes the following steps.

Step S101: An NEF <NUM> receives an identifier (identity, ID) of UE <NUM> and first positioning operation information that are sent by a third-party device <NUM>, where the first positioning operation information is used to request an LMF to perform a first positioning operation on the UE <NUM>. Optionally, the identifier of the UE <NUM> may be a public UE identifier of the UE, the first positioning operation may be some or all of a type identifier and/or a parameter of a positioning operation that needs to be performed, a type identifier and/or a parameter of a positioning operation that needs to be stopped, or a type identifier and/or a parameter of a positioning operation that needs to be modified. For example, a type of a positioning operation may be positioning the UE at a preset interval, and a parameter of the positioning operation may be information indicating that the preset interval is <NUM> minutes. Optionally, the first positioning operation may further include information about the third-party device <NUM>, for example, an identifier of the third-party device or an identifier of an App (application) in the third-party device <NUM>. The third-party device <NUM> sends, as triggered by the App, the identifier of the UE <NUM> and the first positioning operation information to the NEF <NUM>. Step S102: The NEF <NUM> determines, based on the identifier of the UE <NUM>, an LMF <NUM> that provides a location service for the UE <NUM>.

Step S103: The NEF <NUM> sends a first message to the LMF <NUM>, where the first message includes the first positioning operation information. Optionally, the first message may further include the identifier of the UE <NUM>, the identifier of the UE <NUM> is an SUPI, the SUPI of the UE <NUM> may be determined by the NEF <NUM> based on the public UE identifier of the UE <NUM>, and the first positioning operation information may be sent by the third-party device <NUM> to the NEF <NUM>. Optionally, the first positioning operation information may further include the information about the third-party device <NUM>.

Step S104: The LMF <NUM> receives the first message sent by the NEF <NUM>.

Step S105: The LMF <NUM> obtains positioning configuration information of the UE <NUM>. Step S106: The LMF <NUM> determines, based on the positioning configuration information of the UE <NUM>, whether the first positioning operation is allowed on the UE <NUM>.

Step S107: The LMF <NUM> sends a third message to the NEF <NUM> based on a determining result. Optionally, if the LMF <NUM> determines that the first positioning operation is allowed on the UE <NUM>, the LMF <NUM> may further send, after step S106, the identifier of the UE <NUM>, the first positioning operation information, and the information about the third-party device <NUM> to a UDM <NUM>, for the UDM <NUM> to store information related to a positioning operation on the UE <NUM>. Optionally, after storing the identifier of the UE <NUM>, the first positioning operation information, and the information about the third-party device <NUM>, the UDM <NUM> may send a response message to the LMF <NUM>.

Step S108: The NEF <NUM> receives a third message sent by the LMF <NUM>.

Step S109: The NEF <NUM> sends a second message to the third-party device <NUM>. According to the foregoing method, the NEF <NUM> can implement a location service for the UE <NUM> based on a request of the third-party device <NUM>, so that a location service capability of the LMF <NUM> is externally exposed.

In a feasible implementation, the identifier of the UE <NUM> that is sent by the third-party device <NUM> to the NEF <NUM> in step S101 may be the public UE identifier (public UE identity) of the UE <NUM>, to identify an identity of the UE <NUM>. It should be noted that, in this embodiment of this application, a specific form of the identifier of the UE <NUM> that is transferred between nodes in a core network is not clearly limited. A form of the identifier of the UE <NUM> in the steps may also be converted, provided that the UE <NUM> can be uniquely identified. For example, in step S102, the NEF <NUM> may convert the received identifier of the UE <NUM> into a subscription permanent identifier (subscription permanent identifier, SUPI), and the UE <NUM> is identified in the core network by using the SUPI subsequently.

The first positioning operation information sent by the third-party device <NUM> may include or include only the type identifier and/or the parameter of the positioning operation that needs to be performed, to request the LMF <NUM> to perform the positioning operation based on the type identifier and/or the parameter of the positioning operation. Alternatively, the first positioning operation information may include or include only the type identifier and/or the parameter of the positioning operation that needs to be stopped, to request the LMF <NUM> to stop the positioning operation based on the type identifier and/or the parameter of the positioning operation. Alternatively, the first positioning operation information may include or include only the type identifier and/or the parameter of the positioning operation that needs to be modified, to request the LMF <NUM> to modify, based on the type identifier and/or the parameter of the positioning operation, a type identifier and/or a parameter of a positioning operation that has been performed or has not been performed.

Specifically, a type of a positioning operation may be that the LMF determines location information of the UE <NUM> based on a specified time interval and reports the location information of the UE <NUM> to the third-party device. In this case, a parameter of the positioning operation may be the specified time interval. Alternatively, a type of a positioning operation may be that when entering or leaving a specified area, the UE <NUM> reports the location information to the third-party device. In this case, a parameter of the positioning operation may be an identifier of the specified area, coordinate information of the specified area, and/or the like.

In addition, during implementation, alternatively, the first positioning operation information may include or include only the information about the third-party device, for example, the identifier of the third-party device, an IP address of the third-party device, or an identifier of an application program (for example, an App) that initiates a positioning operation in the third-party device. Because the UE <NUM> may be set to allow exposure of the location service only to a third-party device having one or more types of preset information, the third-party device <NUM> may add a part or all of information such as the identifier and the IP address of the third-party device <NUM> and the identifier of the application program that initiates the positioning operation to the first positioning operation information to be sent to the NEF <NUM>.

In this embodiment of this application, the third-party device may further add the information about the third-party device when sending the identifier of the UE and the first positioning operation information, to indicate the third-party device that sends the identifier of the UE and the first positioning operation information. In addition, if the third-party device sends the identifier of the UE and the first positioning operation information to the NEF based on a request of an application program, for example, an APP, of the third-party device, the third-party device may further add an identifier of the application program when sending the identifier of the UE and the first positioning operation information, so that the third-party device notifies the application program of the received second message or information corresponding to the second message.

In a feasible implementation, in step S102, the NEF <NUM> may send the identifier of the UE <NUM> to the UDM <NUM>, and receive information, returned by the UDM <NUM>, about the LMF <NUM> that provides the location service for the UE <NUM>. The information about the LMF <NUM> may be an identifier of the LMF <NUM> or an IP address of the LMF <NUM>.

Through this step, the UDM <NUM> may store the information about the LMF <NUM> that serves the UE <NUM>. When the third-party device <NUM> requests a location of a specified user from the NEF <NUM>, the NEF <NUM> may learn, from the UDM <NUM>, of the LMF <NUM> that serves the UE <NUM>.

During implementation, after receiving the identifier of the UE <NUM> that is sent by the NEF <NUM>, the UDM <NUM> may determine, based on a previously stored correspondence between an identifier of UE and information about an LMF, the information about the LMF <NUM> that provides the location service for the UE <NUM>. The correspondence between an identifier of UE and information about an LMF that is stored in the UDM <NUM> may be sent by the LMF to the UDM after the LMF determines to provide the location service for the UE. For example, after determining to provide the location service for the UE <NUM>, the LMF <NUM> may send the identifier of the UE <NUM> and the information about the LMF <NUM> to the UDM <NUM>, to indicate that the LMF <NUM> provides the location service for the UE <NUM>. In this case, after receiving the identifier of the UE <NUM> that is sent by the NEF <NUM>, the UDM <NUM> can determine that the LMF <NUM> is an LMF that provides the location service for the UE <NUM>.

In another implementation, in step S102, after receiving the identifier of the UE <NUM> that is sent by the third-party device <NUM>, the NEF <NUM> may determine, based on a first correspondence stored by the NEF <NUM>, the LMF <NUM> that provides the location service for the UE <NUM>. The first correspondence is a correspondence between an identifier of UE and information about an LMF that provides a location service for the UE. Specifically, the first correspondence may be obtained by the NEF <NUM> from the UDM <NUM>. For example, the NEF <NUM> obtains an updated first correspondence from the UDM <NUM> at a preset time interval, or after the stored correspondence between an identifier of UE and information about an LMF that provides a location service for the UE changes, the UDM <NUM> sends changed content in the correspondence or a changed correspondence to the NEF <NUM>, so that the NEF <NUM> can determine the first correspondence. The first correspondence may alternatively be a correspondence, previously determined by the NEF <NUM> based on the identifier of the UE <NUM> that is sent by the third-party device <NUM>, between the identifier of the UE <NUM> and the LMF <NUM> that provides a service for the UE <NUM>.

During implementation, the LMF <NUM> may determine, in a process in which the UE <NUM> requests registration from an AMF <NUM>, to provide the location service for the UE <NUM>. A feasible solution is as follows: After the AMF <NUM> receives a registration request sent by the UE <NUM>, the AMF <NUM> may determine, based on service area (serving area) information and the like of the LMF, to use the LMF <NUM> as an LMF that can provide a service for the UE <NUM>, and the AMF <NUM> sends a fourth message to the LMF <NUM>. The fourth message may be a location service activation request (Location Service Activate request), and the fourth message may carry information indicating that the UE <NUM> enables the location service, to request the LMF <NUM> to provide the location service for the UE <NUM>. After receiving the fourth message, the LMF <NUM> determines to provide the location service for the UE <NUM>. In another feasible solution, the UE <NUM> sends, in a process of requesting registration from the AMF <NUM>, a registration request that carries the positioning configuration information. After determining that the registration request includes the positioning configuration information of the UE <NUM>, the AMF <NUM> determines to use the LMF <NUM> as an LMF that can provide a service for the UE <NUM>. The positioning configuration information of the UE <NUM> may include information indicating that the UE <NUM> enables the location service, and the information indicating that the UE <NUM> enables the location service may be location service enabled indication information (LCS enabled indication) of the UE <NUM>, or may be other information indicating that the UE <NUM> enables the location service.

In addition, during implementation, after determining to provide a service for the UE <NUM>, the LMF <NUM> may further add, to a feedback message to be sent to the AMF <NUM>, information identifying that the fourth message sent by the AMF <NUM> is received. In addition, the LMF <NUM> may further send the identifier and/or the coordinate information of the service area of the LMF <NUM> to the AMF <NUM>. For example, the service area of the LMF may be an entire public land mobile network (public land mobile network, PLMN), and the identifier of the service area of the LMF may be an identifier of the PLMN.

Specifically, the LMF <NUM> may determine, based on the positioning configuration information of the UE <NUM>, whether to provide the location service for the UE <NUM>. For example, the positioning configuration information of the UE <NUM> may include or include only location service subscription data of the UE <NUM>, and the location service subscription data may be used to indicate a positioning operation that is allowed on the UE <NUM>. For example, the location service subscription data may include a parameter indicating that the UE is allowed to initiate a positioning operation on the UE to a network to enable the UE to obtain the location information of the UE and a related positioning operation, or may include a parameter indicating that a network side device is allowed to initiate a positioning operation on the UE to enable the network side device to obtain the location information of the UE and a related positioning operation. The positioning configuration information of the UE <NUM> may further include or include only positioning privacy setting information (privacy profile) of the UE <NUM>, and the positioning privacy setting information may be used to indicate a positioning operation that is not allowed on the UE <NUM>. For example, the positioning privacy setting information may include information indicating that a positioning operation on the UE that is initiated by a device other than the UE is rejected. The positioning configuration information of the UE <NUM> may further include or include only location service exposure setting information of the UE <NUM>. For example, the location service exposure setting information may include information indicating whether the UE <NUM> enables the location service; and/or information about a type and/or a parameter of a positioning operation that the third-party device is allowed to or not allowed to request the LMF to perform on the UE <NUM>; and/or information about a third-party device that is allowed to and/or not allowed to perform a positioning operation on the UE <NUM>. Specifically, the information about the third-party device may include an application ID. During implementation, the positioning configuration information of the UE <NUM> may be stored in the UDM <NUM>. Before performing determining, the LMF <NUM> may obtain, from the UDM <NUM> based on the identifier of the UE <NUM>, the positioning configuration information corresponding to the identifier of the UE <NUM>.

In a feasible implementation, the positioning configuration information of the UE <NUM> may be sent by the UE <NUM> to the UDM <NUM> through a core network entity, namely, the AMF. For example, after the positioning configuration information changes, the UE <NUM> may send changed positioning configuration information to the LMF <NUM> through the AMF, and the positioning configuration information is sent by the LMF <NUM> to the UDM <NUM>. In addition, the positioning configuration information of the UE <NUM> may alternatively be default content preconfigured in the UDM <NUM>. For example, the UDM <NUM> stores, by default, positioning configuration information that is of the UE <NUM> and that indicates that all location services are allowed to be performed.

In a feasible implementation, the first message sent by the NEF <NUM> in step S103 further includes the identifier of the UE <NUM>. In this case, in step <NUM>, the LMF <NUM> may obtain the positioning configuration information of the UE <NUM> based on the identifier of the UE <NUM>. The identifier of the UE in this step may be the SUPI.

During implementation, the LMF <NUM> may send the identifier of the UE <NUM> to the UDM <NUM>, and receive the positioning configuration information of the UE <NUM> that is sent by the UDM <NUM>. Specifically, after receiving the identifier of the UE <NUM> that is sent by the LMF <NUM>, the UDM <NUM> may determine, based on a stored correspondence between an identifier of UE and positioning configuration information, the positioning configuration information corresponding to the UE <NUM>, and then send the determined positioning configuration information to the LMF <NUM>. In addition, if the LMF <NUM> stores the positioning configuration information of the UE <NUM>, the LMF <NUM> may alternatively determine the positioning configuration information of the UE <NUM> from the locally stored positioning configuration information based on the identifier of the <NUM>. For example, the LMF <NUM> obtains the positioning configuration information of the UE <NUM> from the UDM <NUM> in a process of determining whether to provide the location service for the UE <NUM>, so that the LMF <NUM> may determine the positioning configuration information of the UE <NUM> based on the identifier of the UE <NUM> in the first message sent by the NEF <NUM>.

Specifically, before step S105, the LMF <NUM> may receive the positioning configuration information sent by the UE <NUM>, and then the LMF <NUM> may send the positioning configuration information sent by the UE <NUM> and the identifier of the UE <NUM> to the UDM <NUM>. In this case, the LMF <NUM> may send the identifier of the UE <NUM> to the UDM <NUM> in step S105 to obtain the positioning configuration information of the UE <NUM>. Alternatively, the LMF <NUM> may locally store the positioning configuration information sent by the UE <NUM> and establish a correspondence between the identifier of the UE <NUM> and the positioning configuration information of the UE <NUM>. In this case, the LMF <NUM> may determine the positioning configuration information of the UE <NUM> based on the identifier of the UE <NUM> in step S <NUM>.

Specifically, the positioning configuration information of the UE <NUM> may be information that is determined and sent through the AMF <NUM> to the LMF <NUM> by the UE <NUM> after a positioning status or a related setting of the UE <NUM> changes. For example, after information indicating enabling or disabling of a positioning operation changes, the UE <NUM> may send the positioning configuration information to the AMF <NUM>, where the positioning configuration information carries information about a change of the information indicating enabling or disabling of a positioning operation, for example, carries changed information identifying enabling or disabling of a positioning operation. In addition, when accessing the AMF <NUM> for the first time, the UE <NUM> may add the positioning configuration information determined by the UE <NUM> to the registration request to be sent to the AMF <NUM>, and the AMF <NUM> may send the positioning configuration information to the LMF <NUM>, so that the LMF <NUM> positions the UE <NUM>.

The positioning configuration information of the UE <NUM> may include positioning status information of the UE <NUM>, and the positioning status information is used to indicate a positioning operation allowed by the UE <NUM> and/or a positioning operation rejected by the UE <NUM>, so that the LMF <NUM> may send the identifier of the UE <NUM> and the positioning status information of the UE <NUM> to the UDM <NUM> or store the identifier of the UE <NUM> and the positioning status information of the UE <NUM>, or locally store the identifier of the UE <NUM> and the positioning status information of the UE <NUM>. The positioning status information may be a type identifier and/or a parameter of a positioning operation that is allowed on the UE <NUM>.

In step S106, the LMF <NUM> may determine, based on the positioning status information in the positioning configuration information of the UE <NUM>, whether the first positioning operation is allowed on the UE <NUM>. The positioning status information may be used to indicate the positioning operation allowed by the UE <NUM> and/or the positioning operation rejected by the UE <NUM>. Specifically, the positioning status information of the UE <NUM> may include the type identifier and/or the parameter of the positioning operation that is allowed on the UE <NUM>. After determining the positioning status information of the UE <NUM>, the LMF <NUM> may determine whether the type identifier and/or the parameter of the positioning operation that is allowed on the UE <NUM> includes a type identifier and/or a parameter of a positioning operation that needs to be performed by the LMF <NUM> and that is indicated by the first positioning operation information. If the type identifier and/or the parameter of the positioning operation that is allowed to be performed on the UE <NUM> includes the type identifier and/or the parameter of the positioning operation that needs to be performed by the LMF <NUM> and that is indicated by the first positioning operation information, the LMF <NUM> determines that the first positioning operation is allowed to be performed; or if the type identifier and/or the parameter of the positioning operation that is allowed to be performed on the UE <NUM> does not include the type identifier and/or the parameter of the positioning operation that needs to be performed by the LMF <NUM> and that is indicated by the first positioning operation information, the LMF <NUM> determines that the first positioning operation is not allowed to be performed. In addition, the positioning status information of the UE <NUM> may alternatively include a type identifier and/or a parameter of a positioning operation that is allowed to be stopped on the UE <NUM>, for the LMF <NUM> to determine whether the first positioning operation indicated by the first positioning operation information is allowed to be stopped. The positioning status information of the UE <NUM> may alternatively include a type identifier and/or a parameter of a positioning operation that is allowed to be modified on the UE <NUM>, for the LMF <NUM> to determine whether a type identifier and/or a parameter of the positioning operation indicated by the first positioning operation information is allowed to be modified.

In addition, in step S106, after the LMF <NUM> determines that the first positioning operation is allowed on the UE <NUM>, the LMF <NUM> may further determine second positioning operation information, to indicate a positioning operation that is allowed on the UE <NUM>. The second positioning operation information may be the same as or different from the first positioning operation information. The LMF <NUM> may send the identifier of the UE <NUM> and the second positioning operation information to the NEF <NUM>, so that the NEF <NUM> may store a correspondence between the identifier of the UE <NUM> and the second positioning operation information, or send the second positioning operation information to the third-party device <NUM>, so that the third-party device <NUM> can determine content of a positioning operation performed by the LMF <NUM>; or the NEF <NUM> may send the identifier of the UE <NUM> and the second positioning operation information to the UDM <NUM>, for the UDM <NUM> to store a correspondence between the identifier of the UE <NUM> and the second positioning operation information; and/or the LMF <NUM> may send the identifier of the UE <NUM> and the second positioning operation information to the UDM <NUM>, for the UDM <NUM> to store a correspondence between the identifier of the UE <NUM> and the second positioning operation information.

An example in which the positioning operation is a positioning operation that needs to be performed by the LMF <NUM> is used. If the LMF <NUM> determines that the first positioning operation that needs to be performed and that is indicated by the first positioning operation information is included in an operation that is allowed on the UE <NUM>, the LMF <NUM> may send the first positioning operation information as the second positioning operation information to the NEF <NUM> or the UDM <NUM>. In another implementation, if the LMF <NUM> determines that a type of the positioning operation that needs to be performed and that is indicated by the first positioning operation information is a type of a positioning operation that is allowed by the UE <NUM>, the LMF <NUM> may determine to accept a request for the positioning operation indicated by the first positioning operation information, determine a second positioning operation based on a type identifier and/or a parameter of the positioning operation that is allowed on the UE <NUM> (in this case, a parameter of the second positioning operation may be different from a parameter of the first positioning operation), and perform the second positioning operation. The LMF <NUM> may determine, based on at least one of a plurality of factors such as network load caused by performing the first positioning operation, whether a positioning capability of the network allows the first positioning operation, and whether the parameter of the first positioning operation is a parameter of the positioning operation that is allowed on the UE <NUM>, whether to determine the second positioning operation based on the type identifier and/or the parameter of the positioning operation that is allowed on the UE <NUM>.

For example, if the first positioning operation indicates that the LMF <NUM> needs to periodically report a location of the UE <NUM> at an interval of <NUM> minutes, but the LMF <NUM> can avoid network overload caused by frequent positioning of a terminal, so that the LMF changes, based on a network load management policy, parameter information, namely, "a time interval for UE periodic reporting" to <NUM> minutes. To be specific, the second positioning operation requires the LMF <NUM> to determine and report the location of the UE at an interval of <NUM> minutes. In another case, a "positioning precision" parameter described in parameter information of the first positioning operation is <NUM> meters, but the LMF changes the positioning precision parameter to <NUM> meters based on a positioning capability of a current network or UE location precision that is allowed to be externally provided. Specifically, the LMF <NUM> may use, in the positioning operation that is allowed on the UE <NUM>, a positioning operation whose positioning operation type is the same as the type of the first positioning operation indicated by the first positioning operation information and whose positioning operation parameter is closest to the parameter of the first positioning operation indicated by the first positioning operation information, as the second positioning operation. In this case, the LMF <NUM> may send, to the NEF <NUM>, a third message carrying accept information, and the LMF <NUM> may further add the second positioning operation information to the third message. The second positioning operation information includes a type identifier and/or a parameter of the second positioning operation, to indicate that the LMF <NUM> accepts a request for the positioning operation, and the positioning operation is the second positioning operation that is performed based on the second positioning operation information. According to the foregoing method, the UDM <NUM> can obtain the identifier of the UE <NUM> and the second positioning operation information from the NEF <NUM> or the LMF <NUM>, so that the UDM <NUM> can store the correspondence between the identifier of the UE <NUM> and the second positioning operation information in the positioning configuration information corresponding to the UE <NUM>. The correspondence is used by the UDM <NUM> to determine, after the UDM <NUM> receives the identifier of the UE <NUM> that is sent by the LMF, the second positioning operation information corresponding to the identifier of the UE <NUM>, so that the LMF can perform the positioning operation on the UE <NUM> based on the second positioning operation information. The LMF may be the LMF <NUM>, or may be another LMF. Therefore, even if the correspondence between the identifier of the UE <NUM> and the second positioning operation information that is stored in the LMF <NUM> is lost or discarded, or the LMF that provides the location service for the UE <NUM> changes to an LMF other than the LMF <NUM> due to a reason such as a location change of the UE <NUM>, the LMF that provides the location service for the UE <NUM> can still obtain, from the UDM <NUM>, the second positioning operation information corresponding to the UE <NUM>, to implement a continuation of the location service for the UE <NUM>.

Specifically, the second positioning operation information may include the positioning operation that is allowed on the UE <NUM>, for example, information used to indicate that the LMF <NUM> is requested to position the UE <NUM> based on the type identifier and/or the parameter of the positioning operation; or may include information that is of the UE <NUM> and that is used to indicate that the LMF <NUM> is requested to stop positioning the UE <NUM> based on the type identifier and/or the parameter of the positioning operation; or may include information used to indicate that the LMF <NUM> is requested to modify the type identifier and/or the parameter of the positioning operation that is used as a basis when the UE <NUM> is positioned, based on the type identifier and/or parameter of the positioning operation.

In step S <NUM>, after determining that the first positioning operation is allowed on the UE <NUM>, the LMF <NUM> may add accept information and/or generated positioning information to the third message to be sent to the NEF <NUM>, to indicate that a request for performing the first positioning operation on the UE <NUM> that is sent by the NEF <NUM> is accepted. The accept information may be an accept indication (accept indication), an acknowledgement character (acknowledgement, ACK), or other accept information indicating that the first positioning operation is allowed to be performed. The generated positioning information may be location information of the UE <NUM> that is determined by the LMF <NUM> after the LMF <NUM> performs the first positioning operation on the UE <NUM> based on the first positioning operation information. In addition, after determining that the first positioning operation is not allowed on the UE <NUM>, the LMF <NUM> may add reject information to the third message to be sent to the NEF <NUM>, to indicate that a request for performing the first positioning operation on the UE <NUM> that is sent by the NEF <NUM> is rejected. The reject information may be a reject indication (reject indication), a negative acknowledgement character (negative acknowledgement, NACK), or other information indicating that the first positioning operation is not allowed to be performed.

In step S109, the NEF <NUM> may send the second message to the third-party device <NUM> after receiving the third message sent by the LMF <NUM>. If the third message sent by the LMF <NUM> includes the positioning information generated by the LMF <NUM>, the NEF <NUM> may add the positioning information to the second message and send the second message to the third-party device <NUM>, to provide the positioning information of the UE <NUM> to the third-party device based on a request of the third-party device <NUM>. In addition, the NEF <NUM> may further add, to the second message, the accept information or the reject information carried in the third message.

A positioning operation method provided in an embodiment of this application is described below by using <FIG> and <FIG> as an example.

The positioning operation system shown in <FIG> is used as an example. In a positioning operation method provided in this embodiment of this application, a schematic flowchart in which when the UE <NUM> registers with a wireless network, the LMF <NUM> determines to provide a location service for the UE <NUM> and sends an identifier of the UE <NUM> and information about the LMF <NUM> to the UDM <NUM> is shown in <FIG>. The method includes the following steps:.

According to the foregoing method, the UDM <NUM> can obtain a correspondence between the identifier of the UE <NUM> and the information about the LMF <NUM> that provides a service for the UE <NUM>. Based on the correspondence, the UDM <NUM> can determine, based on the identifier of the UE <NUM> that is sent by the NEF <NUM>, the information about the LMF <NUM> that provides the location service for the UE <NUM>, and send the information about the LMF <NUM> to the NEF <NUM> in step S102. Therefore, in step S103, the NEF <NUM> can determine, based on the identifier of the UE <NUM>, the information about the LMF <NUM> that provides a service for the UE <NUM>, and further send a first message to the LMF <NUM>.

In addition, during implementation, the UE <NUM> may further add positioning configuration information of the UE <NUM> to the registration request to be sent to the AMF <NUM> in step <NUM>. The positioning configuration information may include information indicating that the UE <NUM> enables the location service or include information about a positioning operation that is allowed on the UE <NUM>, to indicate that the UE <NUM> enables the location service. In this case, the AMF <NUM> may allocate the LMF <NUM> to the UE <NUM> based on the positioning configuration information of the UE <NUM>, and send the positioning configuration information to the LMF <NUM> allocated to the UE. Subsequently, in step <NUM>, the LMF <NUM> may send the positioning configuration information of the UE <NUM> and the identifier of the UE <NUM> to the UDM <NUM>, for the UDM <NUM> to store the positioning configuration information of the UE <NUM>, so that the UDM <NUM> can obtain the correspondence between the identifier of the UE <NUM> and the positioning configuration information of the UE <NUM>, to provide, after the LMF that provides a service for the UE <NUM> changes, the positioning configuration information of the UE <NUM> to a changed LMF. Specifically, after receiving the identifier of the UE <NUM> that is sent by the LMF that provides a service for the UE <NUM>, the UDM <NUM> may send the positioning configuration information of the UE <NUM> to the LMF.

The positioning operation system shown in <FIG> is still used as an example. If positioning configuration information of the UE <NUM> changes, the UE <NUM> may send positioning configuration information to the LMF <NUM> through the AMF <NUM> after the positioning configuration information changes, and then the LMF <NUM> sends the positioning configuration information of the UE <NUM> to the UDM <NUM> for storage. Alternatively, the UE <NUM> may send the positioning configuration information of the UE <NUM> to the LMF <NUM> through the AMF <NUM> at an interval of preset duration, or after a preset time is reached, and then the LMF <NUM> sends the positioning configuration information of the UE <NUM> to the UDM <NUM> for storage.

A detailed process in which the UE <NUM> reports the positioning configuration information of the UE <NUM> to the LMF <NUM> and the UDM <NUM> through the AMF <NUM> is shown in <FIG>, and includes the following steps:.

According to the foregoing method, the positioning configuration information of the UE <NUM> may be stored in the LMF <NUM> and the UDM <NUM>, so that after the LMF <NUM> receives first positioning operation information for the UE <NUM>, the LMF <NUM> determines, based on the locally stored positioning status information of the UE <NUM> or based on positioning status information of the UE <NUM> that is stored in the UDM <NUM>, whether a first positioning operation is allowed on the UE <NUM>.

The positioning operation system shown in <FIG> is still used as an example. If a first App in the third-party device <NUM> requests, from the NEF <NUM>, obtaining of location information of the UE <NUM> at an interval of <NUM> minutes, a specific schematic flowchart of a positioning operation method provided in this embodiment of this application is shown in <FIG> and <FIG>. The procedure specifically includes the following steps:.

Specifically, in step <NUM>, the LMF <NUM> may position the UE <NUM>, stops the positioning operation, or modifies the type and/or the parameter of the positioning operation based on a type identifier and/or the parameter of the positioning operation indicated by the second positioning operation information.

In another feasible implementation, referring to the specific schematic flowchart of the positioning operation method shown in <FIG> and <FIG>, in step <NUM>, the LMF <NUM> may further add the determined second positioning operation information and the identifier of the UE <NUM> to the third message to be sent to the NEF <NUM>, and the second positioning operation information and the identifier of the UE <NUM> may not need to be sent to the UDM <NUM> any longer. After receiving the second positioning operation information and the identifier of the UE <NUM>, the NEF <NUM> may send the second positioning operation information and the identifier of the UE <NUM> to the third-party device <NUM> and/or the UDM <NUM>, so that the third-party device <NUM> can learn of information about the second positioning operation performed by the LMF <NUM>; and/or the UDM <NUM> can store the information about the second positioning operation performed by the LMF <NUM>. Subsequently, when the LMF <NUM> or another LMF performs a positioning operation on the UE <NUM>, the information about the second positioning operation that needs to be performed can be quickly determined.

Based on an inventive concept the same as that of the method embodiments, an embodiment of this application further provides an apparatus <NUM>. The apparatus <NUM> is applied to a location management function entity. The apparatus <NUM> may be specifically a processor, a chip, a chip system, a functional module, or the like in the location management function entity. The apparatus may include a sending unit <NUM>, a receiving unit <NUM>, and a processing unit <NUM>. The processing unit <NUM> is configured to control and manage an action of the apparatus <NUM>. The sending unit <NUM> is configured to perform step S107. The receiving unit <NUM> is configured to perform step S104. The processing unit <NUM> is configured to perform step S105 and step S106. Repeated parts are not described in detail herein again. The processing unit <NUM> may be further configured to indicate a processing process of the location management function entity (including the LMF <NUM>) in any one of the foregoing embodiments and/or another process in the technical solutions described in this application.

In hardware implementation, the processing unit <NUM> may be a processor, a processing circuit, or the like. The sending unit <NUM> may be a transmitter, a transmitter circuit, or the like. The receiving unit <NUM> may be a receiver, a receiver circuit, or the like. The sending unit <NUM> and the receiving unit <NUM> may form a transceiver.

For a possible schematic logical structural diagram that is of the location management function entity <NUM> in the foregoing embodiment and that is provided in this embodiment of this application, refer to <FIG>. The location management function entity <NUM> includes a processor <NUM>. In this embodiment of this application, the processor <NUM> is configured to control and manage an action of the location management function entity <NUM>. For example, the processor <NUM> is configured to support a related step of determining first information by the location management function entity <NUM> in this embodiment. Optionally, the location management function entity <NUM> may further include a transceiver <NUM> and a memory <NUM>. The transceiver <NUM>, the memory <NUM>, and the processor <NUM> may be connected to each other or may be connected to each other by using a bus structure <NUM>. The memory <NUM> is configured to store code and data of the location management function entity <NUM>. The transceiver <NUM> is configured to support the location management function entity <NUM> in performing communication.

In the location management function entity <NUM> shown in <FIG>, the processor <NUM> may be a central processing unit, a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field programmable gate array or another programmable logic device, a transistor logic device, a hardware component, or any combination thereof. The processor may implement or execute various example logical blocks, modules, and circuits described with reference to content disclosed in this application. Alternatively, the processor may be a combination of processors implementing a computing function, for example, a combination of one or more microprocessors, or a combination of the digital signal processor and a microprocessor. Based on an inventive concept the same as that of the method embodiments, an embodiment of this application further provides an apparatus <NUM>. The apparatus <NUM> is applied to a network exposure function entity. The apparatus <NUM> may be specifically a processor, a chip, a chip system, a functional module, or the like in the network exposure function entity. The apparatus may include a sending unit <NUM>, a receiving unit <NUM>, and a processing unit <NUM>. As shown in <FIG>, the processing unit <NUM> is configured to control and manage an action of the apparatus <NUM>. The sending unit <NUM> is configured to perform step S103 and step S109. The receiving unit <NUM> is configured to perform step S101 and S108. The processing unit <NUM> is configured to perform step S102. Repeated parts are not described in detail herein again. The processing unit <NUM> may be further configured to indicate a processing process of the network exposure function entity (including the NEF <NUM>) in any one of the foregoing embodiments and/or another process in the technical solutions described in this application.

For a possible schematic logical structural diagram that is of the network exposure function entity <NUM> in the foregoing embodiment and that is provided in this embodiment of this application, refer to <FIG>. The network exposure function entity <NUM> includes a processor <NUM>. In this embodiment of this application, the processor <NUM> is configured to control and manage an action of the network exposure function entity <NUM>. For example, the processor <NUM> is configured to support a related step of determining first information by the network exposure function entity <NUM> in this embodiment. Optionally, the network exposure function entity <NUM> may further include a transceiver <NUM> and a memory <NUM>. The transceiver <NUM>, the memory <NUM>, and the processor <NUM> may be connected to each other or may be connected to each other by using a bus structure <NUM>. The memory <NUM> is configured to store code and data of the network exposure function entity <NUM>. The transceiver <NUM> is configured to support the network exposure function entity <NUM> in performing communication.

In the network exposure function entity <NUM> shown in <FIG>, the processor <NUM> may be a central processing unit, a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field programmable gate array or another programmable logic device, a transistor logic device, a hardware component, or any combination thereof. The processor may implement or execute various example logical blocks, modules, and circuits described with reference to content disclosed in this application. Alternatively, the processor may be a combination of processors implementing a computing function, for example, a combination of one or more microprocessors, or a combination of the digital signal processor and a microprocessor. Based on an inventive concept the same as that of the method embodiments, an embodiment of this application further provides an apparatus <NUM>. The apparatus <NUM> is applied to a unified data management platform. The apparatus <NUM> may be specifically a processor, a chip, a chip system, a functional module, or the like in the unified data management platform. As shown in <FIG>, the apparatus may include a sending unit <NUM>, a receiving unit <NUM>, and a processing unit <NUM>. The sending unit <NUM> is used by the apparatus <NUM> to send information. The receiving unit <NUM> is used by the apparatus <NUM> to receive information. The processing unit <NUM> is configured to control and manage an action of the apparatus <NUM>. The processing unit <NUM> may be further configured to indicate a processing process of the unified data management platform (including the UDM <NUM>) in any one of the foregoing embodiments and/or another process in the technical solutions described in this application.

For a possible schematic logical structural diagram that is of the unified data management platform <NUM> in the foregoing embodiment and that is provided in this embodiment of this application, refer to <FIG>. The unified data management platform <NUM> includes a processor <NUM>. In this embodiment of this application, the processor <NUM> is configured to control and manage an action of the unified data management platform <NUM>. For example, the processor <NUM> is configured to support a related step of determining first information by the unified data management platform <NUM> in this embodiment. Optionally, the unified data management platform <NUM> may further include a transceiver <NUM> and a memory <NUM>. The transceiver <NUM>, the memory <NUM>, and the processor <NUM> may be connected to each other or may be connected to each other by using a bus structure <NUM>. The memory <NUM> is configured to store code and data of the unified data management platform <NUM>. The transceiver <NUM> is configured to support the unified data management platform <NUM> in performing communication.

In the unified data management platform <NUM> shown in <FIG>, the processor <NUM> may be a central processing unit, a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field programmable gate array or another programmable logic device, a transistor logic device, a hardware component, or any combination thereof. The processor may implement or execute various example logical blocks, modules, and circuits described with reference to content disclosed in this application. Alternatively, the processor may be a combination of processors implementing a computing function, for example, a combination of one or more microprocessors, or a combination of the digital signal processor and a microprocessor. Based on an inventive concept the same as that of the method embodiments, an embodiment of this application further provides an apparatus <NUM>. The apparatus <NUM> is applied to a terminal. The apparatus <NUM> may be specifically a processor, a chip, a chip system, a functional module, or the like in the terminal. As shown in <FIG>, the apparatus may include a sending unit <NUM>, a receiving unit <NUM>, and a processing unit <NUM>. The sending unit <NUM> is used by the apparatus <NUM> to send information. The receiving unit <NUM> is used by the apparatus <NUM> to receive information. The processing unit <NUM> is configured to control and manage an action of the apparatus <NUM>. The processing unit <NUM> may be further configured to indicate a processing process of the terminal (including the UE <NUM>) in any one of the foregoing embodiments and/or another process in the technical solutions described in this application.

For a possible schematic logical structural diagram that is of the terminal <NUM> in the foregoing embodiment and that is provided in this embodiment of this application, refer to <FIG>. The terminal <NUM> includes a processor <NUM>. In this embodiment of this application, the processor <NUM> is configured to control and manage an action of the terminal <NUM>. For example, the processor <NUM> is configured to support a related step of determining first information by the terminal <NUM> in this embodiment. Optionally, the terminal <NUM> may further include a transceiver <NUM> and a memory <NUM>. The transceiver <NUM>, the memory <NUM>, and the processor <NUM> may be connected to each other or may be connected to each other by using a bus structure <NUM>. The memory <NUM> is configured to store code and data of the terminal <NUM>. The transceiver <NUM> is configured to support the terminal <NUM> in performing communication.

In the terminal <NUM> shown in <FIG>, the processor <NUM> may be a central processing unit, a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field programmable gate array or another programmable logic device, a transistor logic device, a hardware component, or any combination thereof. The processor may implement or execute various example logical blocks, modules, and circuits described with reference to content disclosed in this application. Alternatively, the processor may be a combination of processors implementing a computing function, for example, a combination of one or more microprocessors, or a combination of the digital signal processor and a microprocessor.

Based on a concept the same as that of the foregoing method embodiments, an embodiment of this application further provides a positioning operation system. The system may include a location management function entity. In addition, during implementation, the positioning operation system may further include one or more of a unified data management platform, a terminal, or a network exposure function entity. In addition, the system may further include another device, for example, an access and mobility management function entity or a radio access network, that can interact with one or more of the location management function entity, the unified data management platform, the terminal, or the network exposure function entity.

As shown in <FIG>, a positioning operation system <NUM> provided in an embodiment of this application includes a location management function entity <NUM>, a network exposure function entity <NUM>, a unified data management platform <NUM>, and a terminal <NUM>. The location management function entity <NUM> may have the structure shown in <FIG> or <FIG>, the network exposure function entity <NUM> may have the structure shown in <FIG> or <FIG>, the unified data management platform <NUM> may have the structure shown in <FIG> or <FIG>, and the terminal <NUM> may have the structure shown in <FIG> or <FIG>.

Based on a same concept as the foregoing method embodiments, an embodiment of this application further provides a computer-readable storage medium, storing some instructions. When these instructions are invoked and executed by a computer, the computer may be enabled to complete the method in any one of the foregoing method embodiments and the possible designs of the method embodiments. In this embodiment of this application, the computer-readable storage medium is not limited. For example, the computer-readable storage medium may be a RAM (random-access memory, random access memory) or a ROM (read-only memory, read-only memory).

Based on a same concept as the foregoing method embodiments, this application further provides a computer program product. When being invoked and executed by a computer, the computer program product can implement the method in any one of the method embodiments and the possible designs of the foregoing method embodiments. Based on a concept the same as that of the foregoing method embodiments, this application further provides a chip. The chip is coupled to a transceiver, and is configured to complete the method in any one of the foregoing method embodiments and the possible implementations of the method embodiments. "Coupling" means that two components are directly or indirectly combined with each other, the combination may be fixed or movable, and the combination may allow communication of a fluid, electricity, an electrical signal, or another type of signal between the two parts.

Persons skilled in the art should understand that the embodiments of this application may be provided as a method, a system, or a computer program product. In addition, this application may use a form of a computer program product that is implemented on one or more computer-usable storage media (including but not limited to a magnetic disk memory, a CD-ROM (a compact disc read-only memory), an optical memory, and the like) that include computer-usable program code.

This application is described with reference to the flowcharts and/or block diagrams of the method, the device (system), and the computer program product according to the embodiments of this application. It should be understood that computer program instructions may be used to implement each process and/or each block in the flowcharts and/or the block diagrams and a combination of a process and/or a block in the flowcharts and/or the block diagrams. These computer program instructions may be provided for a general-purpose computer, a special-purpose computer, an embedded processor, or a processor of another programmable data processing device to generate a machine, so that the instructions executed by a computer or a processor of another programmable data processing device generate an apparatus for implementing a specific function in one or more processes in the flowcharts and/or in one or more blocks in the block diagrams.

These computer program instructions may be stored in a computer-readable memory that can instruct the computer or the another programmable data processing device to work in a specific manner, so that the instructions stored in the computer-readable memory generate an artifact that includes an instruction apparatus.

Although some possible embodiments of this application have been described, persons skilled in the art can make other changes and modifications to these embodiments once they learn the basic inventive concept. Therefore, the following claims are intended to be construed as to cover the embodiments of this application and all changes and modifications falling within the scope of this application.

Claim 1:
A positioning operation method, comprising:
receiving, by a network exposure function entity (<NUM>) in a communications system, an identifier of a terminal and first positioning operation information from a third-party device (<NUM>), wherein the first positioning operation information is used to request a first positioning operation on the terminal;
determining (S102), by the network exposure function entity (<NUM>) based on the identifier of the terminal, a location management function entity (<NUM>) that provides a location service for the terminal;
sending (S103), by the network exposure function entity (<NUM>), a first message to the location management function entity (<NUM>), wherein the first message comprises the first positioning operation information;
receiving, by the network exposure function entity (<NUM>), positioning information of the terminal from the location management function entity (<NUM>); and
sending, by the network exposure function entity (<NUM>), the positioning information of the terminal to the third-party device (<NUM>),
wherein the determining, by the network exposure function entity (<NUM>) based on the identifier of the terminal, a location management function entity (<NUM>) that provides a location service for the terminal comprises:
sending, by the network exposure function entity (<NUM>), the identifier of the terminal to a unified data management platform (<NUM>); and
receiving, by the network exposure function entity (<NUM>), information about the location management function entity (<NUM>) from the unified data management platform (<NUM>).