Data processing method and apparatus

By assisting the unified data management UDM entity to process the privacy profile of the terminal device, the problem of unclear UE privacy profile information is solved, and the security and reliability of the ranging/SL positioning service is realized, ensuring that only authorized devices can obtain information.

WO2024234273A1PCT designated stage expired Publication Date: 2024-11-21BEIJING XIAOMI MOBILE SOFTWARE CO LTD
View PDF 4 Cites 0 Cited by

Patent Information

Application Number
PCT/CN2023/094382
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Filing Date
2023-05-15
Publication Date
2024-11-21

AI Technical Summary

Technical Problem

In the existing ranging/SL positioning services, the specific information in the UE's privacy configuration file is not clear, resulting in whether network functions, application functions, location service clients, etc. are allowed to obtain ranging/SL positioning information, which affects the service. Safety and reliability.

Method used

Through the information provided by the first entity, the UDM entity assists in creating, updating or deleting the privacy profile of the terminal device, ensuring that the privacy profile is associated with ranging and/or side chain positioning services, and thus accurately determine the privacy profile of the terminal device. File, GMLC entity obtains a privacy profile from the UDM entity to determine whether the service request is allowed.

Benefits of technology

Improve the security of terminal equipment ranging and/or side chain positioning services, ensure that only authorized network functions and applications can obtain ranging/SL positioning information, and enhance the reliability of the service and user privacy protection.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2023094382_21112024_PF_FP_ABST
    Figure CN2023094382_21112024_PF_FP_ABST
Patent Text Reader

Abstract

Disclosed in embodiments of the present disclosure are a data processing method and an apparatus, applicable to the technical field of communications. The method executed by a first entity comprises: providing first information, wherein the first information is used for assisting a unified data management (UDM) entity in creating, updating or deleting a privacy configuration file of a terminal device, and the privacy configuration file is a file associated with ranging and / or sidelink positioning service. In this way, the UDM entity can be assisted in creating, updating or deleting the privacy configuration file of the terminal device, such that the privacy configuration file corresponding to the terminal device can be accurately determined.
Need to check novelty before this filing date? Find Prior Art

Description

Data processing method and device Technical Field

[0001] The present disclosure relates to the field of communication technology, and in particular to a data processing method and device. Background Art

[0002] Ranging services determine the relative distance between two user equipment (UEs) and / or the relative direction or angle of one UE relative to another. Sidelink (SL) positioning services enable UEs to use a direct communication interface (PC5) link to obtain their absolute position, relative position, or ranging information. Ranging / SL positioning services can be applied to various verticals, such as consumer, smart home, smart city, smart transportation, smart retail, and Industry 4.0.

[0003] Summary of the Invention

[0004] The disclosed embodiments provide a data processing method and apparatus that, using first information provided by a first entity, assists a unified data management (UDM) entity in creating, updating, or deleting first information of a privacy profile for a terminal device. This assists the unified data management (UDM) entity in creating, updating, or deleting a privacy profile for a terminal device, thereby accurately determining the privacy profile corresponding to the terminal device.

[0005] In a first aspect, an embodiment of the present disclosure provides a data processing method, which is executed by a first entity, and the method includes: providing first information, wherein the first information is used to assist the unified data management (UDM) entity in creating, updating or deleting a privacy profile of the terminal device, and the privacy profile is a file associated with ranging and / or side-chain positioning services.

[0006] In a second aspect, an embodiment of the present disclosure provides a data processing method, which is performed by a gateway mobile location center (GMLC) entity. The method includes:

[0007] Receiving a service request sent by a sending end, wherein the service request includes an identifier of a terminal device;

[0008] Obtaining a privacy profile associated with the identifier of the terminal device from a unified data management (UDM) entity, wherein the privacy profile is a file associated with ranging and / or sidechain positioning services;

[0009] Based on the privacy profile, it is determined whether the service request is allowed.

[0010] In a third aspect, an embodiment of the present disclosure provides a data processing method, which is executed by a unified data management (UDM) entity. The method includes:

[0011] receiving a first message;

[0012] Based on the first information, a privacy profile of the terminal device is created, updated or deleted, where the privacy profile is a file associated with ranging and / or sidechain positioning services.

[0013] In a fourth aspect, an embodiment of the present disclosure provides a communication device having the function of implementing some or all of the functions of the first entity in the method described in the first aspect above. For example, the functions of the communication device may have the functions of some or all of the embodiments of the present disclosure, or may have the function of implementing any one of the embodiments of the present disclosure alone. The functions may be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the above functions.

[0014] In one implementation, the communication device may include a transceiver module and a processing module, wherein the processing module is configured to support the communication device in performing corresponding functions in the above method. The transceiver module is used to support communication between the communication device and other devices.

[0015] The communication device may further include a storage module, which is coupled to the transceiver module and the processing module and stores computer programs and data necessary for the communication device.

[0016] In one implementation, the communication device includes:

[0017] The transceiver module is used to provide first information, wherein the first information is used to assist the unified data management (UDM) entity in creating, updating or deleting a privacy profile of the terminal device, and the privacy profile is a file associated with ranging and / or side chain positioning services.

[0018] In a fifth aspect, an embodiment of the present disclosure provides another communication device that has some or all of the functions of the Gateway Mobile Location Center (GMLC) entity in the method example described in the second aspect. For example, the functions of the communication device may have some or all of the functions in the embodiments of the present disclosure, or may have the functions of implementing any one of the embodiments of the present disclosure alone. The functions may be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the above functions.

[0019] In one implementation, the communication device may include a transceiver module and a processing module, the processing module being configured to support the communication device in performing the corresponding functions of the above-described method. The transceiver module is configured to support communication between the communication device and other devices. The communication device may also include a storage module, coupled to the transceiver module and the processing module, which stores computer programs and data necessary for the communication device.

[0020] In one implementation, the communication device includes:

[0021] a transceiver module, configured to receive a service request sent by a sending end, wherein the service request includes an identifier of a terminal device;

[0022] A processing module, configured to obtain a privacy profile associated with the identifier of the terminal device from a unified data management (UDM) entity, wherein the privacy profile is a file associated with ranging and / or sidechain positioning services;

[0023] The processing module is further configured to determine whether the service request is allowed based on the privacy profile.

[0024] In a sixth aspect, an embodiment of the present disclosure provides another communication device, which has some or all of the functions of the unified data management (UDM) entity in the method example described in the second aspect above. For example, the functions of the communication device may have some or all of the functions in the embodiments of the present disclosure, or may have the functions of implementing any one of the embodiments of the present disclosure alone. The functions may be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the above functions.

[0025] In one implementation, the communication device may include a transceiver module and a processing module, the processing module being configured to support the communication device in performing the corresponding functions of the above-described method. The transceiver module is configured to support communication between the communication device and other devices. The communication device may also include a storage module, coupled to the transceiver module and the processing module, which stores computer programs and data necessary for the communication device.

[0026] In one implementation, the communication device includes:

[0027] a transceiver module, configured to receive first information;

[0028] A processing module is used to create, update or delete a privacy profile of the terminal device based on the first information, where the privacy profile is a file associated with the ranging and / or side chain positioning service.

[0029] In a seventh aspect, an embodiment of the present disclosure provides a communication device, which includes a processor. When the processor calls a computer program in a memory, it executes the method described in the first aspect above.

[0030] In an eighth aspect, an embodiment of the present disclosure provides a communication device, which includes a processor. When the processor calls a computer program in a memory, it executes the method described in the second aspect above.

[0031] In a ninth aspect, an embodiment of the present disclosure provides a communication device, which includes a processor. When the processor calls a computer program in a memory, the method described in the third aspect is executed.

[0032] In the tenth aspect, an embodiment of the present disclosure provides a communication device, which includes a processor and a memory, in which a computer program is stored; the processor executes the computer program stored in the memory so that the communication device executes the method described in the first aspect above.

[0033] In the eleventh aspect, an embodiment of the present disclosure provides a communication device, which includes a processor and a memory, in which a computer program is stored; the processor executes the computer program stored in the memory so that the communication device executes the method described in the second aspect above.

[0034] In the twelfth aspect, an embodiment of the present disclosure provides a communication device, which includes a processor and a memory, in which a computer program is stored; the processor executes the computer program stored in the memory so that the communication device executes the method described in the third aspect above.

[0035] In a thirteenth aspect, an embodiment of the present disclosure provides a communication device, which includes a processor and an interface circuit, wherein the interface circuit is used to receive code instructions and transmit them to the processor, and the processor is used to run the code instructions to enable the device to execute the method described in the first aspect above.

[0036] In a fourteenth aspect, an embodiment of the present disclosure provides a communication device, which includes a processor and an interface circuit, wherein the interface circuit is used to receive code instructions and transmit them to the processor, and the processor is used to run the code instructions to enable the device to execute the method described in the second aspect above.

[0037] In a fifteenth aspect, an embodiment of the present disclosure provides a communication device, which includes a processor and an interface circuit, wherein the interface circuit is used to receive code instructions and transmit them to the processor, and the processor is used to run the code instructions to enable the device to execute the method described in the third aspect above.

[0038] In the sixteenth aspect, an embodiment of the present disclosure provides a communication system, which includes the communication device described in aspects four to six, or the system includes the communication device described in aspects seven to nine, or the system includes the communication device described in aspects ten to twelfth, or the system includes the communication device described in aspects thirteen to fifteenth.

[0039] In a seventeenth aspect, an embodiment of the present invention provides a computer-readable storage medium for storing instructions used by the above-mentioned first entity, and when the instructions are executed, the receiving end executes the method described in the above-mentioned first aspect.

[0040] In an eighteenth aspect, an embodiment of the present invention provides a readable storage medium for storing instructions used by the above-mentioned Gateway Mobile Location Center GMLC entity. When the instructions are executed, the transmitting end executes the method described in the above-mentioned second aspect.

[0041] In the nineteenth aspect, an embodiment of the present invention provides a readable storage medium for storing instructions used for the above-mentioned unified data management (UDM) entity. When the instructions are executed, the transmitting end executes the method described in the above-mentioned second aspect.

[0042] In a twentieth aspect, the present disclosure further provides a computer program product comprising a computer program, which, when executed on a computer, enables the computer to execute the method described in the first aspect above.

[0043] In a twenty-first aspect, the present disclosure further provides a computer program product comprising a computer program, which, when executed on a computer, enables the computer to execute the method described in the second aspect above.

[0044] In a twenty-second aspect, the present disclosure further provides a computer program product comprising a computer program, which, when executed on a computer, enables the computer to execute the method described in the third aspect above.

[0045] In a twenty-third aspect, the present disclosure provides a chip system comprising at least one processor and an interface for supporting a receiving end in implementing the functions described in the first aspect, such as determining or processing at least one of the data and information described in the aforementioned method. In one possible design, the chip system further comprises a memory for storing computer programs and data necessary for the first entity. The chip system may consist of a chip alone or may include a chip and other discrete components.

[0046] In a twenty-fourth aspect, the present disclosure provides a chip system comprising at least one processor and an interface for supporting a transmitter in implementing the functions described in the second aspect, such as determining or processing at least one of the data and information described in the aforementioned method. In one possible design, the chip system further comprises a memory for storing computer programs and data necessary for a Gateway Mobile Location Center (GMLC) entity. The chip system may consist solely of a chip or may include a chip and other discrete components.

[0047] In aspect 25, the present disclosure provides a chip system comprising at least one processor and an interface for supporting a receiving end to implement the functions involved in aspect 3, for example, determining or processing at least one of the data and information involved in the above method. In one possible design, the chip system further comprises a memory for storing computer programs and data necessary for a unified data management (UDM) entity. The chip system may be composed of a chip, or may include a chip and other discrete devices.

[0048] In a twenty-sixth aspect, the present disclosure provides a computer program which, when executed on a computer, enables the computer to execute the method described in the first aspect above.

[0049] In aspect 27, the present disclosure provides a computer program which, when executed on a computer, enables the computer to execute the method described in aspect 2 above.

[0050] In a twenty-eighth aspect, the present disclosure provides a computer program which, when executed on a computer, enables the computer to execute the method described in the third aspect above. BRIEF DESCRIPTION OF THE DRAWINGS

[0051] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure or the background technology, the drawings required for use in the embodiments of the present disclosure or the background technology will be described below.

[0052] FIG1 is a schematic diagram of the architecture of a communication system provided by the present disclosure;

[0053] FIG2 is a flow chart of a data processing method provided by an embodiment of the present disclosure;

[0054] FIG3 is a flow chart of another data processing method provided by an embodiment of the present disclosure;

[0055] FIG4 is a flow chart of another data processing method provided by an embodiment of the present disclosure;

[0056] FIG5 is a flowchart of another data processing method provided by an embodiment of the present disclosure;

[0057] FIG6 is an interactive schematic diagram of a data processing method provided by an embodiment of the present disclosure;

[0058] FIG7 is an interactive schematic diagram of another data processing method provided by an embodiment of the present disclosure;

[0059] FIG8 is a structural diagram of a communication device provided by an embodiment of the present disclosure;

[0060] FIG9 is a structural diagram of another communication device provided in an embodiment of the present disclosure;

[0061] FIG10 is a schematic structural diagram of a chip provided in an embodiment of the present disclosure. DETAILED DESCRIPTION

[0062] To facilitate understanding of the technical solutions of the present disclosure, some terms involved in the embodiments of the present disclosure are briefly introduced below.

[0063] 1. Application Function (AF)

[0064] AF is another functional network element on the core network side, which can interact with the 3GPP core network to provide services and support the following functions: application-side impact on service flow routing; access to network exposure functions; exchange with the policy framework for policy control; based on the operator's deployment, application functions trusted by the operator can directly interact with related network functions.

[0065] 2. Unified Data Management (UDM)

[0066] UDM is responsible for the management of user identification, contract data, authentication data, and user service network element registration management.

[0067] In order to better understand the data processing method and device disclosed in the embodiments of the present disclosure, the communication system to which the embodiments of the present disclosure are applicable is first described below.

[0068] Please refer to Figure 1, which is a schematic diagram of the architecture of a communication system provided in an embodiment of the present disclosure. The communication system may include, but is not limited to, one network device and one terminal. The number and form of devices shown in Figure 1 are for example purposes only and do not constitute a limitation on the embodiments of the present disclosure. In actual applications, two or more network devices and two or more terminals may be included. The communication system shown in Figure 1 includes a network device 101 and a terminal 102.

[0069] It should be noted that the technical solutions of the embodiments of the present disclosure can be applied to various communication systems, such as long-term evolution (LTE) systems, fifth-generation (5G) mobile communication systems, 5G new radio (NR) systems, or other future new mobile communication systems.

[0070] The network device 101 in the embodiment of the present disclosure is an entity on the network side for transmitting or receiving signals and a device for communicating with a terminal. The network device 101 can be a base transceiver station (BTS) in a global system for mobile communications (GSM) system or a code division multiple access (CDMA) system, a base station B (nodeB, NB) in a wideband code division multiple access (WCDMA) system, an evolved nodeB (eNB or eNodeB) in an LTE system, a wireless controller in a cloud radio access network (CRAN) scenario, a radio network controller (RNC), a base station controller (BSC), a home base station (for example, a home evolved nodeB or home nodeB, HNB), a baseband unit (BBU), or a cellular network controller. The network-side device may be a baseband unit (BBU), or the network-side device may be a relay station, an access point, an in-vehicle device, a wearable device, a network-side device in a 5G network, or a network-side device in a future-evolved PLMN network, etc. It may be an access point (AP) in a WLAN, a wireless relay node, a wireless backhaul node, a transmission point (TP), or a transmission and reception point (TRP), etc. It may be a gNB or a transmission point (TRP or TP) in a new radio (NR) system, or one or a group of antenna panels (including multiple antenna panels) of a base station in a 5G system, or it may also be a network node constituting a gNB or a transmission point, such as a baseband unit (BBU) or a distributed unit (DU), etc. The embodiments of the present disclosure do not limit the specific technology and specific device form adopted by the network-side device.The network side device provided by the embodiment of the present disclosure may be composed of a centralized unit (CU) and a distributed unit (DU), wherein the CU may also be referred to as a control unit. The CU-DU structure may be used to split the network side device, such as the protocol layer of the network side device, and the functions of some protocol layers may be centrally controlled by the CU, while the functions of the remaining part or all of the protocol layers may be distributed in the DU, and the DU may be centrally controlled by the CU.

[0071] The network side device 101 in the embodiment of the present disclosure may be an application function AF entity on the network side, or it may also be a unified data management UDM entity on the network side, or it may also be a gateway mobile location center (GMLC) entity, etc., and the present disclosure does not limit this.

[0072] The terminal 102 in the embodiment of the present disclosure may be a device that provides voice / data connectivity to a user, for example, a handheld device or a vehicle-mounted device with a wireless connection function. Some examples of terminals include: mobile phones, tablet computers, laptop computers, PDAs, mobile internet devices (MIDs), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, cellular phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), handheld devices with wireless communication capabilities, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, terminals in 5G networks or future evolved public land mobile communication networks (PLMNs), and so on. The present invention relates to a terminal in a wireless communication system (PLMN) and / or any other suitable device for communicating on a wireless communication system, and the embodiments of the present disclosure are not limited thereto.

[0073] Wearable devices, also known as wearable smart devices, are a general term for wearable devices developed by applying wearable technology to intelligently design everyday wearables, such as glasses, wristbands, watches, clothing, and shoes. A wearable device is a portable device that is worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not just hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. In a broad sense, wearable smart devices include those that are fully functional, large in size, and can achieve full or partial functions without relying on smartphones, such as smart watches or smart glasses, as well as those that focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0074] In addition, in the embodiment of the present disclosure, the terminal 102 can also be a terminal in the Internet of Things system. The IoT (Internet of Things) is an important part of the future development of information technology. Its main technical feature is to connect objects to the network through communication technology, thereby realizing an intelligent network of human-machine interconnection and object-to-object interconnection.

[0075] In addition, in the embodiment of the present disclosure, the terminal 102 may also include sensors such as smart printers, train detectors, and gas stations. Its main functions include collecting data (partial terminals), receiving control information and downlink data from network-side devices, and sending electromagnetic waves to transmit uplink data to network-side devices.

[0076] It should be noted that the technical solutions of the embodiments of the present disclosure can be applied to various communication systems, such as long-term evolution (LTE) systems, fifth-generation (5G) mobile communication systems, 5G new radio (NR) systems, or other future new mobile communication systems.

[0077] It can be understood that the communication system described in the embodiment of the present disclosure is for the purpose of more clearly illustrating the technical solution of the embodiment of the present disclosure, and does not constitute a limitation on the technical solution provided by the embodiment of the present disclosure. Ordinary technicians in this field can know that with the evolution of the system architecture and the emergence of new business scenarios, the technical solution provided by the embodiment of the present disclosure is also applicable to similar technical problems.

[0078] In addition, in order to facilitate understanding of the embodiments of the present disclosure, the following points are explained.

[0079] First, the first, second, and various numerical numbers in the present disclosure are merely distinctions for convenience of description and are not intended to limit the scope of the embodiments of the present disclosure, for example, to distinguish different information, different intervals, different time slots, etc.

[0080] Second, the "protocol" involved in the embodiments of the present disclosure may refer to a standard protocol in the communication field, for example, it may include an LTE protocol, a NR protocol, and related protocols used in future communication systems, and the present disclosure does not limit this.

[0081] Third, the embodiments of the present disclosure list multiple implementation methods to clearly illustrate the technical solutions of the embodiments of the present disclosure. Of course, those skilled in the art will understand that the multiple embodiments provided in the embodiments of the present disclosure can be implemented individually, combined with the methods of other embodiments of the embodiments of the present disclosure, or implemented individually or in combination with some methods in other related technologies; the embodiments of the present disclosure are not limited to this.

[0082] The following is a detailed introduction to a data processing method and device provided by the present disclosure with reference to the accompanying drawings.

[0083] Ranging services determine the relative distance between two user equipment (UEs) and / or the relative direction or angle of one UE relative to another. Sidelink (SL) positioning services enable UEs to use a direct communication interface (PC5) link to obtain their absolute position, relative position, or ranging information. Ranging / SL positioning services can be applied to various verticals, such as consumer, smart home, smart city, smart transportation, smart retail, and Industry 4.0.

[0084] In the related art, in order to authorize the application server or network function (NF) to obtain the results (for example, location information) obtained by ranging / SL positioning service measurements, the Gateway Mobile Location Center (GMLC) interacts with the Unified Data Management (UDM) to check the UE's privacy profile, and interacts with the Access and Mobility Management Function (AMF) to perform UE privacy verification.

[0085] However, the specific information contained in the UE's privacy profile is still unclear, that is, it is not yet clear which network functions (NF), application functions (AF), location services (LCS) clients, client terminal devices (Client UE), server terminal devices (Server UE), etc. are allowed or not allowed to obtain the UE's ranging / SL positioning information.

[0086] Therefore, the present disclosure proposes a data processing method that uses first information provided by a first entity to assist a unified data management (UDM) entity in creating, updating, or deleting first information of a privacy profile for a terminal device. This method assists the unified data management (UDM) entity in creating, updating, or deleting a privacy profile for a terminal device, thereby accurately determining the privacy profile corresponding to the terminal device.

[0087] Please refer to Figure 2, which is a flow chart of a data processing method provided by an embodiment of the present disclosure. As shown in Figure 2, the method is applied to a first entity, and the method may include but is not limited to the following steps:

[0088] Step 201: Provide first information, wherein the first information is used to assist the unified data management (UDM) entity in creating, updating, or deleting a privacy profile of a terminal device, where the privacy profile is a file associated with ranging and / or sidechain positioning services.

[0089] In some possible implementations, the first entity may be at least one of the following: a terminal device and an application function AF network element.

[0090] The first information may include ranging and / or sidechain positioning authorization data of the terminal device. For example, whether the terminal device allows the NF, AF, LCS client, client terminal device (Client UE), server terminal device (Server UE), etc. to obtain ranging and / or sidechain positioning information; if obtaining ranging and / or sidechain positioning information is allowed, whether it is necessary to further send a notification to the first entity, whether privacy verification is required, whether a response needs to be received before the location of the first entity can be obtained, etc.

[0091] Among them, client terminal equipment (Client UE): a terminal equipment that initiates a ranging service request.

[0092] Among them, server terminal equipment (Server UE) is a terminal equipment that provides method determination, auxiliary data distribution and / or position calculation function and / or positioning calculation function for services based on sidelink positioning and ranging.

[0093] For example, the terminal device registers application A for the first time and allows application A to obtain ranging and / or sidechain positioning services after sending a notification. The first information may include the identification of application A, permission for ranging and / or sidechain positioning services, but a notification needs to be sent to the terminal device.

[0094] In some possible implementations, the first information further includes an identifier corresponding to the terminal device, so that the UDM can create, update, or delete a privacy profile of the terminal device based on the identifier of the terminal device.

[0095] In the present disclosure, when the unified data management UDM entity receives the first information and determines that the UDM does not contain a privacy profile corresponding to the terminal device, the first information is used to assist the unified data management UDM entity in creating a privacy profile for the terminal device; when the unified data management UDM entity receives the first information and determines that the unified data management UDM entity contains a privacy profile corresponding to the terminal device, but they are not the same, the first information is used to assist the unified data management UDM entity in updating the privacy profile of the terminal device; when the first information provided by the first entity includes a deletion indication, the first information is used to assist the unified data management UDM entity in deleting the privacy profile of the terminal device.

[0096] In some possible implementations, when the first entity is a terminal device, the terminal device needs to first provide the first information to the Authentication Management Function (AMF) entity, and the AMF entity forwards the first information to the unified data management (UDM) entity. When the first entity is an AF network element, the AF network element directly provides the first information to the unified data management (UDM) entity.

[0097] It should be noted that the role and implementation of the privacy profile can be referred to the detailed description of other embodiments of the present disclosure and will not be repeated here.

[0098] In the present disclosure, a first entity provides first information for assisting a unified data management (UDM) entity in creating, updating, or deleting a privacy profile for a terminal device. The privacy profile is a file associated with ranging and / or sidechain positioning services. This can assist the unified data management (UDM) entity in creating, updating, or deleting a privacy profile for a terminal device, thereby accurately determining the privacy profile corresponding to the terminal device.

[0099] Please refer to Figure 3, which is a flow chart of a data processing method provided by an embodiment of the present disclosure. As shown in Figure 3, the method is applied to a Gateway Mobile Location Center (GMLC) entity. The method may include but is not limited to the following steps:

[0100] Step 301: Receive a service request sent by a sending end, wherein the service request includes an identifier of a terminal device.

[0101] Among them, the sending end can be any NF that sends a service request, AF, LCS client, client terminal equipment (Client UE), server terminal equipment (Server UE), etc.

[0102] Among them, the terminal device can be a terminal device that requests the sending end to perform ranging and / or side chain positioning services.

[0103] The service request may be used to request the Gateway Mobile Location Center (GMLC) entity to provide ranging and / or side-link positioning services corresponding to the terminal device.

[0104] Step 302: Obtain a privacy profile associated with the identifier of the terminal device from a unified data management (UDM) entity, wherein the privacy profile is a file associated with ranging and / or sidechain positioning services.

[0105] It should be noted that the UDM entity stores the privacy profile corresponding to each terminal device. When the GMLC entity receives a service request from the sender, it can obtain the privacy profile associated with the terminal device's identity from the UDM entity and then determine whether the service request is allowed based on the privacy profile.

[0106] Optionally, the GMLC entity may send a privacy profile acquisition request to the UDM entity, wherein the acquisition request includes the identifier of the terminal device, so as to obtain the privacy profile associated with the identifier of the terminal device from the UDM entity.

[0107] In some possible implementations, the privacy profile may include at least one of the following:

[0108] Ranging and / or side chain positioning privacy indicator, each call and / or session independent class, location service client list, Gateway Mobile Location Center GMLC address list.

[0109] In some possible implementations, the ranging and / or sidechain positioning privacy indicator is used to indicate one or more of the following: allowing ranging and / or sidechain positioning, not allowing ranging and / or sidechain positioning, and the valid time period of the ranging and / or sidechain positioning indication bit.

[0110] Among them, when the ranging and / or sidechain positioning privacy indicator indicates that ranging and / or sidechain positioning is allowed, it can be understood that the terminal device allows the NF, AF, LCS client, client UE, server UE, etc. that the terminal device has authorized to provide it with ranging and / or sidechain positioning services.

[0111] Among them, the ranging and / or sidechain positioning privacy indicator indicates that ranging and / or sidechain positioning is not allowed, which can be understood as the terminal device not allowing any NF, AF, LCS client, client UE, server UE, etc. to provide it with ranging and / or sidechain positioning services.

[0112] Among them, the valid time period of the ranging and / or side chain positioning privacy indicator indicated by the privacy indicator can be understood as the valid time of the ranging and / or side chain positioning privacy indicator. After exceeding this valid time, the privacy indicator becomes invalid.

[0113] In some possible implementations, the call and / or session-independent class may include at least one of the following:

[0114] Core network elements, trusted AFs, or non-external LCS clients;

[0115] A first list, wherein the first list includes a first identifier of one or more of the following items: an untrusted AF entity, an external location service LCS client;

[0116] A second list, wherein the second list includes second identifiers of one or more of the following items: a client terminal device (Client UE), a server terminal device (Server UE);

[0117] The third list includes third identifiers of one or more ranging and / or side chain positioning applications.

[0118] It should be noted that the trusted AF entity may be an AF deployed by the operator itself, and the untrusted AF entity may be an AF deployed by a third party.

[0119] In some possible implementations, the call and / or session-independent class may further include at least one of the following:

[0120] A first privacy configuration associated with a core network element, a trusted AF, or a non-external LCS client, a second privacy configuration associated with each first identifier in the first list, a third privacy configuration associated with each second identifier in the second list, and a fourth privacy configuration associated with each third identifier in the third list.

[0121] In some possible implementations, the privacy configuration may include privacy setting information, time setting information, and area range setting information.

[0122] In some possible implementations, the privacy setting information may include any one of the following:

[0123] Ranging and / or sidechain positioning services are not permitted;

[0124] Allowing ranging and / or sidechain positioning services without sending a notification to the first entity (i.e., obtaining the location of the first entity without sending a notification to the first entity)

[0125] Allow ranging and / or sidechain positioning services, and need to send a notification to the first entity; (i.e., need to send a notification to the first entity to obtain the first entity's location)

[0126] Allowing ranging and / or sidechain positioning services requires sending a notification to the first entity and performing information verification with the first entity; (i.e., it is necessary to send a notification to the first entity and obtain the location of the first entity if the information verification passes)

[0127] Allowing ranging and / or sidechain positioning services requires sending a notification to the first entity and performing information verification with the first entity. If the first entity does not feedback a verification response, the location of the first entity can be exposed. (i.e., it is necessary to send a notification to the first entity and perform information verification with the first entity. By default, if the first entity does not feedback a verification response, the information verification passes and the location of the first entity can be exposed.)

[0128] To allow ranging and / or sidechain positioning services, a notification must be sent to the first entity and information verification must be performed with the first entity. If the first entity does not provide a verification response, the location of the first entity must not be disclosed. (That is, a notification must be sent to the first entity and information verification must be performed with the first entity. By default, if the first entity does not provide a verification response, the information verification fails and the location of the first entity must not be disclosed.)

[0129] In some possible implementations, the settings of the privacy setting information in the privacy configurations associated with different call and / or session-independent classes may be different.

[0130] For example, the privacy setting information included in the first privacy configuration associated with the core network element, the trusted AF, or the non-external LCS client may be any of the following:

[0131] Ranging and / or sidechain positioning services are not permitted;

[0132] Ranging and / or sidechain positioning services are allowed, and notification needs to be sent to the first entity;

[0133] Allowing ranging and / or sidechain positioning services requires sending a notification to the first entity and performing information verification with the first entity;

[0134] Allowing ranging and / or sidechain positioning services requires sending a notification to the first entity and performing information verification with the first entity. If the first entity does not provide a verification response, the location of the first entity is allowed to be disclosed.

[0135] Allowing ranging and / or sidechain positioning services requires sending a notification to the first entity and performing information verification with the first entity. Disclosure of the first entity's location is prohibited if the first entity does not provide a verification response.

[0136] For example, the privacy setting information in the second privacy configuration associated with the first list and the privacy setting information in the fourth privacy configuration associated with the third list may be any of the following:

[0137] Allowing ranging and / or sidechain positioning services without sending notification to the first entity;

[0138] Ranging and / or sidechain positioning services are allowed, and notification needs to be sent to the first entity;

[0139] Allowing ranging and / or sidechain positioning services requires sending a notification to the first entity and performing information verification with the first entity;

[0140] Allowing ranging and / or sidechain positioning services requires sending a notification to the first entity and performing information verification with the first entity. If the first entity does not provide a verification response, the location of the first entity is allowed to be disclosed.

[0141] To allow ranging and / or side chain positioning services, a notification must be sent to the first entity and information verification must be performed with the first entity. If the first entity does not provide a verification response, the location of the first entity must not be exposed.

[0142] For example, the privacy setting information in the third privacy configuration associated with the second list may be any of the following:

[0143] Ranging and / or sidechain positioning services are not permitted;

[0144] Allowing ranging and / or sidechain positioning services without sending notification to the first entity;

[0145] Ranging and / or sidechain positioning services are allowed, and notification needs to be sent to the first entity;

[0146] Allowing ranging and / or sidechain positioning services requires sending a notification to the first entity and performing information verification with the first entity;

[0147] Allowing ranging and / or sidechain positioning services requires sending a notification to the first entity and performing information verification with the first entity. If the first entity does not provide a verification response, the location of the first entity is allowed to be disclosed.

[0148] Allowing ranging and / or sidechain positioning services requires sending a notification to the first entity and performing information verification with the first entity. Disclosure of the first entity's location is prohibited if the first entity does not provide a verification response.

[0149] In some possible implementations, the time setting information may include any of the following: a time period during which ranging and / or sidechain positioning services are allowed, and a time period during which ranging and / or sidechain positioning services are not allowed;

[0150] In some possible implementations, the area range setting information may include any one of the following: an area range in which ranging and / or side chain positioning services are allowed, and an area range in which ranging and / or side chain positioning services are not allowed.

[0151] In some possible implementations, the location service client list may include:

[0152] LCS clients that broadcast location-related information;

[0153] Operation and maintenance LCS client in the Home Public Land Mobile Network (HPLMN);

[0154] Operator and maintenance LCS client in Visited Public Land Mobile Network (VPLMN);

[0155] LCS client that records anonymous location information;

[0156] LCS client supporting bearer services, remote services or supplementary services to the target UE;

[0157] LCS client of the Network Data Analytics Function (NWDAF) in the HPLMN (when the UE is currently being served by the HPLMN);

[0158] LCS client of NWDAF in VPLMN.

[0159] In some possible implementations, the gateway mobile location center GMLC address list may include: the address of the GMLC in the local network that is allowed to provide ranging / SL positioning services for the first entity.

[0160] Step 303: Determine whether the service request is allowed based on the privacy profile.

[0161] It is understandable that after obtaining the privacy profile, the privacy profile corresponding to the terminal device can be queried to determine whether the service request sent by the sender is allowed.

[0162] In some possible implementations, if the ranging and / or sidechain positioning privacy indicators in the privacy profile indicate permission, it is determined that the service is allowed. In some possible implementations, if the ranging and / or sidechain positioning privacy indicators in the privacy profile indicate permission and the identifier of the sender is not included in the privacy profile, it is determined that the service request is not allowed.

[0163] In some possible implementations, if the ranging and / or sidechain positioning privacy indicator in the privacy profile indicates that it is not allowed, even if the identifier of the sender is included in the privacy profile, it is determined that the service request is not allowed.

[0164] In the present disclosure, the GMLC entity receives a service request sent by a sender, then obtains a privacy profile associated with the identifier of the terminal device from a unified data management (UDM) entity, and finally determines whether the service request is allowed based on the privacy profile. Thus, it is possible to accurately determine whether the service request sent by the sender is allowed based on the privacy profile, thereby improving the security of the terminal device's ranging and / or side-chain positioning services.

[0165] Please refer to Figure 4, which is a flow chart of a data processing method provided by an embodiment of the present disclosure. As shown in Figure 4, the method is applied to a Gateway Mobile Location Center (GMLC) entity. The method may include but is not limited to the following steps:

[0166] Step 401: Receive a service request sent by a sending end, wherein the service request includes an identifier of a terminal device.

[0167] Step 402: Obtain a privacy profile associated with the identifier of the terminal device from a unified data management (UDM) entity, wherein the privacy profile is a file associated with ranging and / or sidechain positioning services.

[0168] Step 403: Determine whether the service request is allowed based on the privacy profile.

[0169] In some possible implementations, whether the service request is allowed may be determined based on an indication of a ranging and / or sidechain positioning privacy indicator in a privacy profile.

[0170] Specifically, if the ranging and / or sidechain positioning privacy indicator indicates that ranging and / or sidechain positioning are not allowed, it is determined that the service request is not allowed.

[0171] If the ranging and / or side-chain positioning privacy indicator indicates that ranging and / or side-chain positioning is allowed, it is necessary to further determine whether the sender's identifier is included in the call and / or session-independent classes, location service client list, and GMLC address list of the privacy profile. If it is determined that the sender's identifier is not included in the privacy profile, the sender's service request is not allowed; if the sender's identifier is included in the call and / or session-independent classes of the privacy profile, it is necessary to further determine whether the service request is allowed in combination with the privacy configuration associated with the sender's identifier in the privacy profile.

[0172] In some possible implementations, whether the service request is allowed may be determined based on whether each call and / or session-independent class in the privacy profile contains the sender's identifier and satisfies the privacy configuration associated with the sender's identifier.

[0173] Specifically, if the identifier of the sending end is not included in each call and / or session-independent class, it is determined that the service request is not allowed.

[0174] Alternatively, the identifier of the sending end is included in each call and / or session-independent class, and whether the service request is allowed can be determined by further combining the first privacy configuration associated with the identifier of the sending end.

[0175] For example, the privacy setting information in the first privacy configuration associated with the sender's identifier is that ranging and / or sidechain positioning services are allowed, and there is no need to send a notification to the first entity; the time setting information is the time period for allowing ranging and / or sidechain positioning services; and the area range setting information is the area range for allowing ranging and / or sidechain positioning services. If the time when the sender sends the service request is within the time period for allowing ranging and / or sidechain positioning services, and the sender's location is within the area range for allowing ranging and / or sidechain positioning services, then it is determined that the sender's service request is allowed.

[0176] In some possible implementations, whether the service request is allowed is determined based on whether the location service client list in the privacy profile contains the identifier of the sender.

[0177] Specifically, if the location service client list includes the identifier of the sender, it is determined that the service request is allowed; if the location service client list does not include the identifier of the sender, it is determined that the service request is not allowed.

[0178] In some possible implementations, whether the service request is allowed is determined based on whether the GMLC address is included in the GMLC address list in the privacy profile.

[0179] Specifically, if the GMLC address list includes the address of the GMLC, it is determined that the service request is allowed; if the GMLC address list does not include the address of the GMLC, it is determined that the service request is not allowed.

[0180] In the present disclosure, the GMLC entity receives a service request sent by a sender, then obtains a privacy profile associated with the terminal device's identity from a unified data management (UDM) entity, and finally determines whether the service request is allowed based on the privacy profile. Thus, it is possible to accurately determine whether the service request sent by the sender is allowed based on the privacy profile, thereby improving the security of the terminal device's ranging and / or side-chain positioning services.

[0181] Please refer to Figure 5, which is a flow chart of a data processing method provided by an embodiment of the present disclosure. As shown in Figure 5, the method is applied to a unified data management (UDM) entity. The method may include but is not limited to the following steps:

[0182] Step 501: Receive first information.

[0183] The first information is used to assist the unified data management (UDM) entity in creating, updating or deleting a privacy profile of the terminal device.

[0184] The first information may include ranging and / or sidechain positioning authorization data of the first entity. For example, whether the first entity allows the NF, AF, LCS client, client UE, server UE, etc. to obtain ranging and / or sidechain positioning information; if obtaining ranging and / or sidechain positioning information is allowed, whether it is necessary to further send a notification to the first entity, whether privacy verification is required, whether a response needs to be received before the location of the first entity can be obtained, etc.

[0185] For example, the first entity registers application A for the first time and allows application A to obtain ranging and / or sidechain positioning services after sending a notification. The first information may include the identification of application A, permission for ranging and / or sidechain positioning services, but a notification needs to be sent to the first entity.

[0186] In some possible implementations, the UDM entity may receive the first information provided by the terminal device through the AMF entity, or may also receive the first information provided by the AF network element through the AF network element.

[0187] It should be noted that when the UDM entity receives the first information provided by the terminal device through the AMF entity, the terminal device first provides the first information to the authentication management function (Authentication Management Function, AMF) entity, and the AMF entity forwards the first information to the unified data management UDM entity, so that the unified data management UDM entity receives the first information provided by the terminal device through the AMF.

[0188] Step 502: Create, update or delete a privacy profile of the terminal device based on the first information. The privacy profile is a file associated with the ranging and / or side chain positioning service.

[0189] In the present disclosure, when the unified data management UDM entity receives the first information and determines that the UDM does not contain a privacy profile corresponding to the terminal device, the first information is used to assist the unified data management UDM entity in creating a privacy profile for the terminal device; when the unified data management UDM entity receives the first information and determines that the unified data management UDM entity contains a privacy profile corresponding to the terminal device, but they are not the same, the first information is used to assist the unified data management UDM entity in updating the privacy profile of the terminal device; when the first information provided by the first entity includes a deletion indication, the first information is used to assist the unified data management UDM entity in deleting the privacy profile of the terminal device.

[0190] In some possible implementations, the privacy profile may include at least one of the following:

[0191] Ranging and / or side chain positioning privacy indicator, each call and / or session independent class, location service client list, Gateway Mobile Location Center GMLC address list.

[0192] In some possible implementations, the ranging and / or sidechain positioning privacy indicator is used to indicate one or more of the following: allowing ranging and / or sidechain positioning, not allowing ranging and / or sidechain positioning, and the valid time period of the ranging and / or sidechain positioning indication bit.

[0193] Among them, when the ranging and / or sidechain positioning privacy indicator indicates that ranging and / or sidechain positioning is allowed, it can be understood that the terminal device allows the NF, AF, LCS client, client UE, server UE, etc. that the terminal device has authorized to provide it with ranging and / or sidechain positioning services.

[0194] Among them, the ranging and / or sidechain positioning privacy indicator indicates that ranging and / or sidechain positioning is not allowed, which can be understood as the terminal device not allowing any NF, AF, LCS client, client UE, server UE, etc. to provide it with ranging and / or sidechain positioning services.

[0195] Among them, the valid time period of the ranging and / or side chain positioning privacy indicator indicated by the privacy indicator can be understood as the valid time of the ranging and / or side chain positioning privacy indicator. After exceeding this valid time, the privacy indicator becomes invalid.

[0196] In some possible implementations, the call and / or session-independent class may include at least one of the following:

[0197] Core network elements, trusted AFs, or non-external LCS clients;

[0198] A first list, wherein the first list includes a first identifier of one or more of the following items: an untrusted AF entity, an external location service LCS client;

[0199] A second list, wherein the second list includes second identifiers of one or more of the following items: a client terminal device (Client UE), a server terminal device (Server UE);

[0200] The third list includes third identifiers of one or more ranging and / or side chain positioning applications.

[0201] Any client identified as being irrelevant to a call and / or session may include an LCS client. Any entity identified as being irrelevant to a call and / or session may be any NF entity or a trusted AF entity.

[0202] It should be noted that the trusted AF entity may be an AF deployed by the operator itself, and the untrusted AF entity may be an AF deployed by a third party.

[0203] In some possible implementations, the call and / or session-independent class may further include at least one of the following:

[0204] A first privacy configuration associated with a core network element, a trusted AF, or a non-external LCS client, a second privacy configuration associated with each first identifier in the first list, a third privacy configuration associated with each second identifier in the second list, and a fourth privacy configuration associated with each third identifier in the third list.

[0205] In some possible implementations, the privacy configuration may include privacy setting information, time setting information, and area range setting information.

[0206] In some possible implementations, the privacy setting information may include any one of the following:

[0207] Ranging and / or sidechain positioning services are not permitted;

[0208] Allowing ranging and / or sidechain positioning services without sending a notification to the first entity (i.e., obtaining the location of the first entity without sending a notification to the first entity)

[0209] Allow ranging and / or sidechain positioning services, and need to send a notification to the first entity; (i.e., need to send a notification to the first entity to obtain the first entity's location)

[0210] Allowing ranging and / or sidechain positioning services requires sending a notification to the first entity and performing information verification with the first entity; (i.e., it is necessary to send a notification to the first entity and obtain the location of the first entity if the information verification passes)

[0211] Allowing ranging and / or sidechain positioning services requires sending a notification to the first entity and performing information verification with the first entity. If the first entity does not feedback a verification response, the location of the first entity can be exposed. (i.e., it is necessary to send a notification to the first entity and perform information verification with the first entity. By default, if the first entity does not feedback a verification response, the information verification passes and the location of the first entity can be exposed.)

[0212] To allow ranging and / or sidechain positioning services, a notification must be sent to the first entity and information verification must be performed with the first entity. If the first entity does not provide a verification response, the location of the first entity must not be disclosed. (That is, a notification must be sent to the first entity and information verification must be performed with the first entity. By default, if the first entity does not provide a verification response, the information verification fails and the location of the first entity must not be disclosed.)

[0213] In some possible implementations, the privacy setting information in the privacy configurations associated with different call and / or session-independent classes may be different.

[0214] For example, the privacy setting information included in the first privacy configuration associated with the core network element, the trusted AF, or the non-external LCS client may be any of the following:

[0215] Ranging and / or sidechain positioning services are not permitted;

[0216] Ranging and / or sidechain positioning services are allowed, and notification needs to be sent to the first entity;

[0217] Allowing ranging and / or sidechain positioning services requires sending a notification to the first entity and performing information verification with the first entity;

[0218] Allowing ranging and / or sidechain positioning services requires sending a notification to the first entity and performing information verification with the first entity. If the first entity does not provide a verification response, the location of the first entity is allowed to be disclosed.

[0219] Allowing ranging and / or sidechain positioning services requires sending a notification to the first entity and performing information verification with the first entity. Disclosure of the first entity's location is prohibited if the first entity does not provide a verification response.

[0220] For example, the privacy setting information in the second privacy configuration associated with the first list and the privacy setting information in the fourth privacy configuration associated with the third list may be any of the following:

[0221] Allowing ranging and / or sidechain positioning services without sending notification to the first entity;

[0222] Ranging and / or sidechain positioning services are allowed, and notification needs to be sent to the first entity;

[0223] Allowing ranging and / or sidechain positioning services requires sending a notification to the first entity and performing information verification with the first entity;

[0224] Allowing ranging and / or sidechain positioning services requires sending a notification to the first entity and performing information verification with the first entity. If the first entity does not provide a verification response, the location of the first entity is allowed to be disclosed.

[0225] To allow ranging and / or side chain positioning services, a notification must be sent to the first entity and information verification must be performed with the first entity. If the first entity does not provide a verification response, the location of the first entity must not be exposed.

[0226] For example, the privacy setting information in the third privacy configuration associated with the second list may be any of the following:

[0227] Ranging and / or sidechain positioning services are not permitted;

[0228] Allowing ranging and / or sidechain positioning services without sending notification to the first entity;

[0229] Ranging and / or sidechain positioning services are allowed, and notification needs to be sent to the first entity;

[0230] Allowing ranging and / or sidechain positioning services requires sending a notification to the first entity and performing information verification with the first entity;

[0231] Allowing ranging and / or sidechain positioning services requires sending a notification to the first entity and performing information verification with the first entity. If the first entity does not provide a verification response, the location of the first entity is allowed to be disclosed.

[0232] Allowing ranging and / or sidechain positioning services requires sending a notification to the first entity and performing information verification with the first entity. Disclosure of the first entity's location is prohibited if the first entity does not provide a verification response.

[0233] In some possible implementations, the time setting information may include any of the following: a time period during which ranging and / or sidechain positioning services are allowed, and a time period during which ranging and / or sidechain positioning services are not allowed;

[0234] In some possible implementations, the area range setting information may include any one of the following: an area range in which ranging and / or side chain positioning services are allowed, and an area range in which ranging and / or side chain positioning services are not allowed.

[0235] In some possible implementations, the location service client list may include:

[0236] LCS clients that broadcast location-related information;

[0237] Operation and maintenance LCS client in the Home Public Land Mobile Network (HPLMN);

[0238] Operator and maintenance LCS client in Visited Public Land Mobile Network (VPLMN);

[0239] LCS client that records anonymous location information;

[0240] LCS client supporting bearer services, remote services or supplementary services to the target UE;

[0241] LCS client of the Network Data Analytics Function (NWDAF) in the HPLMN (when the UE is currently being served by the HPLMN);

[0242] LCS client of NWDAF in VPLMN.

[0243] In some possible implementations, the gateway mobile location center GMLC address list may include: the address of the GMLC in the local network that is allowed to provide ranging / SL positioning services for the first entity.

[0244] In the present disclosure, the unified data management (UDM) entity receives first information for assisting the unified data management (UDM) entity in creating, updating, or deleting a privacy profile of a terminal device, and creates, updates, or deletes a privacy profile of the terminal device based on the first information, thereby accurately determining the privacy profile corresponding to the terminal device.

[0245] Please refer to Figure 6, which is a signaling interaction diagram of a data processing method provided by an embodiment of the present disclosure. As shown in the figure, the method may include but is not limited to the following steps:

[0246] In step 601, the terminal device provides first information to the AMF, where the first information is used to assist the unified data management (UDM) entity in creating, updating, or deleting a privacy profile for the terminal device, where the privacy profile is a file associated with the residual ranging and / or side chain positioning service.

[0247] Step 602: After obtaining the first information, the AMF sends the first information to the unified data management (UDM) entity.

[0248] Step 603: After receiving the first information, the UDM entity creates, updates or deletes a privacy profile of the terminal device based on the first information.

[0249] Step 604: The GMLC entity receives a service request sent by the sending end, wherein the service request includes an identifier of the terminal device.

[0250] Step 605: The GMLC entity obtains the privacy profile associated with the terminal device's identifier from the UDM entity.

[0251] Step 606: The GMLC entity determines whether the service request is allowed based on the privacy profile.

[0252] Thus, the first information provided by the terminal device assists the unified data management (UDM) entity in creating, updating, or deleting the first information of the terminal device's privacy profile, and the GMLC entity then determines whether the service request is permitted based on the privacy profile. This not only accurately determines the privacy profile corresponding to the terminal device, but also enables the GMLC entity to accurately determine whether the service request sent by the sender is permitted, thereby improving the security of the terminal device's ranging and / or sidelink positioning services.

[0253] Please refer to Figure 7, which is a signaling interaction diagram of a data processing method provided by an embodiment of the present disclosure. As shown in the figure, the method may include but is not limited to the following steps:

[0254] In step 701, the AF network element provides first information to the UDM entity, wherein the first information is used to assist the UDM entity in creating, updating or deleting a privacy profile of the terminal device, where the privacy profile is a file associated with the residual ranging and / or side chain positioning service.

[0255] Step 702: After receiving the first information, the UDM entity creates, updates or deletes a privacy profile of the terminal device based on the first information.

[0256] Step 703: The GMLC entity receives a service request sent by the sending end, wherein the service request includes an identifier of the terminal device.

[0257] Step 704: The GMLC entity obtains the privacy profile associated with the terminal device's identifier from the UDM entity.

[0258] Step 705: The GMLC entity determines whether the service request is allowed based on the privacy profile.

[0259] Thus, the first information provided by the AF network element assists the unified data management (UDM) entity in creating, updating, or deleting the first information of the terminal device's privacy profile, and the GMLC entity then determines whether the service request is permitted based on the privacy profile. This not only accurately determines the privacy profile corresponding to the terminal device, but also enables the GMLC entity to accurately determine whether the service request sent by the sender is permitted, thereby improving the security of the terminal device's ranging and / or sidelink positioning services.

[0260] Please refer to Figure 8, which is a schematic diagram of the structure of a communication device provided in an embodiment of the present disclosure. The communication device 800 shown in Figure 8 may include a transceiver module 801 and a processing module 802. The transceiver module 801 may include a sending module and / or a receiving module. The sending module is used to implement a sending function, and the receiving module is used to implement a receiving function. The transceiver module 801 can implement the sending function and / or the receiving function.

[0261] The communication device 800 may also be the first entity, or a device in the first entity, or a device that can be used in conjunction with the first entity.

[0262] The communication device 800 is on the first entity side, wherein:

[0263] The transceiver module 801 is used to provide first information, wherein the first information is used to assist the unified data management (UDM) entity in creating, updating or deleting a privacy profile of the terminal device, where the privacy profile is a file associated with ranging and / or sidechain positioning services.

[0264] In some possible implementations, the first entity is at least one of the following: a terminal device and an application function AF network element.

[0265] In summary, the first entity provides first information for assisting the unified data management (UDM) entity in creating, updating, or deleting a privacy profile for a terminal device. The privacy profile is a file associated with ranging and / or sidechain positioning services. This can assist the unified data management (UDM) entity in creating, updating, or deleting a privacy profile for a terminal device, thereby accurately determining the privacy profile corresponding to the terminal device.

[0266] The communication device 800 may also be a gateway mobile location center GMLC entity, or a device in the gateway mobile location center GMLC entity, or a device that can be used in conjunction with the gateway mobile location center GMLC entity.

[0267] The communication device 800 is located at the Gateway Mobile Location Center (GMLC) entity side, wherein:

[0268] The transceiver module 801 is configured to receive a service request sent by a sending end, wherein the service request includes an identifier of a terminal device;

[0269] Processing module 802 is configured to obtain a privacy profile associated with the identifier of the terminal device from a unified data management (UDM) entity, wherein the privacy profile is a file associated with ranging and / or sidechain positioning services;

[0270] The processing module 802 is further configured to determine whether the service request is allowed based on the privacy profile.

[0271] In some possible implementations, the processing module 802 is further configured to:

[0272] Determining whether the service request is allowed based on an indication of the ranging and / or sidechain positioning privacy indicator in the privacy profile; and / or,

[0273] Determining whether the service request is allowed based on whether the call and / or session-independent class in the privacy profile contains the identifier of the sender and whether the privacy configuration associated with the identifier of the sender is satisfied; and / or,

[0274] Determining whether the service request is allowed based on whether the location service client list in the privacy profile contains the identifier of the sender; and / or,

[0275] Whether the service request is allowed is determined based on whether the GMLC address list in the privacy profile contains the GMLC address.

[0276] In some possible implementations, the ranging and / or sidechain positioning privacy indicator is used to indicate one or more of the following: ranging and / or sidechain positioning is allowed, ranging and / or sidechain positioning is not allowed, and the valid time period of the ranging and / or sidechain positioning privacy indicator.

[0277] In some possible implementations, the call and / or session-independent class includes at least one of the following:

[0278] Core network elements, trusted AFs, or non-external LCS clients;

[0279] A first list, wherein the first list includes a first identifier of one or more of the following items: an untrusted AF entity, an external location service LCS client;

[0280] A second list, wherein the second list includes second identifiers of one or more of the following items: a client terminal device (Client UE), a server terminal device (Server UE);

[0281] The third list includes third identifiers of one or more ranging and / or side chain positioning applications.

[0282] In some possible implementations, the call and / or session-independent class further includes at least one of the following:

[0283] A first privacy configuration associated with a core network element, a trusted AF, or a non-external LCS client, a second privacy configuration associated with each first identifier in the first list, a third privacy configuration associated with each second identifier in the second list, and a fourth privacy configuration associated with each third identifier in the third list.

[0284] In some possible implementations, the privacy configuration includes privacy setting information, time setting information, and area range setting information.

[0285] In some possible implementations, the privacy setting information includes any one of the following:

[0286] Ranging and / or sidechain positioning services are not permitted;

[0287] Allowing ranging and / or sidechain positioning services without sending notification to the first entity;

[0288] Ranging and / or sidechain positioning services are allowed, and notification needs to be sent to the first entity;

[0289] Allowing ranging and / or sidechain positioning services requires sending a notification to the first entity and performing information verification with the first entity;

[0290] Allowing ranging and / or sidechain positioning services requires sending a notification to the first entity and performing information verification with the first entity. If the first entity does not provide a verification response, the location of the first entity is allowed to be disclosed.

[0291] Allowing ranging and / or sidechain positioning services requires sending a notification to the first entity and performing information verification with the first entity. Disclosure of the first entity's location is prohibited if the first entity does not provide a verification response.

[0292] The time setting information includes any of the following: a time period during which ranging and / or sidechain positioning services are allowed, and a time period during which ranging and / or sidechain positioning services are not allowed;

[0293] The area range setting information includes any of the following: the area range in which ranging and / or side chain positioning services are allowed, and the area range in which ranging and / or side chain positioning services are not allowed.

[0294] In some possible implementations, the processing module 802 is used to

[0295] When the ranging and / or sidechain positioning privacy indicator in the privacy profile indicates permission and the identifier of the sender is not included in the privacy profile, it is determined that the service request is not allowed.

[0296] The communication device 800 provided in the above embodiments of the present disclosure achieves the same or similar beneficial effects as the data processing methods provided in some of the above embodiments, and will not be described in detail here.

[0297] In summary, the GMLC entity receives the service request sent by the sender, then obtains the privacy profile associated with the terminal device's identity from the unified data management (UDM) entity, and finally determines whether the service request is allowed based on the privacy profile. Thus, it is possible to accurately determine whether the service request sent by the sender is allowed based on the privacy profile, thereby improving the security of the terminal device's ranging and / or side-chain positioning services.

[0298] The communication device 800 may also be a unified data management (UDM) entity, or a device in the unified data management (UDM) entity, or a device that can be used in conjunction with the unified data management (UDM) entity.

[0299] The communication device 800 is on the unified data management (UDM) entity side, wherein:

[0300] The transceiver module 801 is configured to receive first information;

[0301] The processing module 802 is used to create, update or delete a privacy profile of the terminal device based on the first information. The privacy profile is a file associated with the ranging and / or side chain positioning service.

[0302] In some possible implementations, the privacy profile includes at least one of the following:

[0303] Ranging and / or sidechain positioning privacy indicators, call and / or session independence class, location service client list, Gateway Mobile Location Center GMLC address list.

[0304] In some possible implementations, the ranging and / or sidechain positioning privacy indicator is used to indicate one or more of the following: allowing ranging and / or sidechain positioning, not allowing ranging and / or sidechain positioning, and the valid time period of the ranging and / or sidechain positioning indication bit.

[0305] In some possible implementations, the call and / or session-independent class includes at least one of the following:

[0306] Core network elements, trusted AFs, or non-external LCS clients;

[0307] A first list, wherein the first list includes a first identifier of one or more of the following items: an untrusted AF entity, an external location service LCS client;

[0308] A second list, wherein the second list includes second identifiers of one or more of the following items: a client terminal device (Client UE), a server terminal device (Server UE);

[0309] The third list includes third identifiers of one or more ranging and / or side chain positioning applications.

[0310] In some possible implementations, the call and / or session-independent class further includes at least one of the following:

[0311] A first privacy configuration associated with a core network element, a trusted AF, or a non-external LCS client, a second privacy configuration associated with each first identifier in the first list, a third privacy configuration associated with each second identifier in the second list, and a fourth privacy configuration associated with each third identifier in the third list.

[0312] In some possible implementations, the privacy configuration includes privacy setting information, time setting information, and area range setting information.

[0313] In some possible implementations, the privacy setting information includes any one of the following:

[0314] Ranging and / or sidechain positioning services are not permitted;

[0315] Allowing ranging and / or sidechain positioning services without sending notification to the first entity;

[0316] Ranging and / or sidechain positioning services are allowed, and notification needs to be sent to the first entity;

[0317] Allowing ranging and / or sidechain positioning services requires sending a notification to the first entity and performing information verification with the first entity;

[0318] Allowing ranging and / or sidechain positioning services requires sending a notification to the first entity and performing information verification with the first entity. If the first entity does not provide a verification response, the location of the first entity is allowed to be disclosed.

[0319] Allowing ranging and / or sidechain positioning services requires sending a notification to the first entity and performing information verification with the first entity. Disclosure of the first entity's location is prohibited if the first entity does not provide a verification response.

[0320] The time setting information includes any of the following: a time period during which ranging and / or sidechain positioning services are allowed, and a time period during which ranging and / or sidechain positioning services are not allowed;

[0321] The area range setting information includes any of the following: the area range in which ranging and / or side chain positioning services are allowed, and the area range in which ranging and / or side chain positioning services are not allowed.

[0322] The communication device 800 provided in the above embodiments of the present disclosure achieves the same or similar beneficial effects as the data processing methods provided in some of the above embodiments, and will not be described in detail here.

[0323] In the present disclosure, the unified data management (UDM) entity receives first information for assisting the unified data management (UDM) entity in creating, updating, or deleting a privacy profile of a terminal device, and creates, updates, or deletes a privacy profile of the terminal device based on the first information, thereby accurately determining the privacy profile corresponding to the terminal device.

[0324] Please refer to Figure 9, which is a schematic diagram of the structure of another communication device 900 provided in an embodiment of the present disclosure. Communication device 900 can be a first entity, a UDM entity, a GMLC entity, or a chip, chip system, or processor that supports the first entity in implementing the above-mentioned method. It can also be a chip, chip system, or processor that supports the UDM entity in implementing the above-mentioned method. It can also be a chip, chip system, or processor that supports the GMLC entity in implementing the above-mentioned method. This communication device 900 can be used to implement the method described in the above-mentioned method embodiment. For details, please refer to the description of the above-mentioned method embodiment.

[0325] The communication device 900 may include one or more processors 901. The processor 901 may be a general-purpose processor or a dedicated processor. For example, it may be a baseband processor or a central processing unit. The baseband processor may be used to process communication protocols and communication data, and the central processing unit may be used to control the communication device (e.g., network-side equipment, baseband chips, terminals, terminal chips, DUs or CUs, etc.), execute computer programs, and process computer program data.

[0326] In some possible implementations, the communication device 900 may further include one or more memories 902, on which a computer program 904 may be stored. The memories 902 execute the computer program 904, so that the communication device 900 performs the methods described in the above method embodiments. In some possible implementations, the memories 902 may also store data. The communication device 900 and the memories 902 may be provided separately or integrated together.

[0327] In some possible implementations, the communication device 900 may further include a transceiver 905 and an antenna 906. The transceiver 905 may be referred to as a transceiver unit, a transceiver, or a transceiver circuit, and is configured to implement transceiver functions. The transceiver 905 may include a receiver and a transmitter. The receiver may be referred to as a receiver or a receiving circuit, and is configured to implement a receiving function; the transmitter may be referred to as a transmitter or a transmitting circuit, and is configured to implement a transmitting function.

[0328] In some possible implementations, the communication device 900 may further include one or more interface circuits 909. The interface circuit 909 is configured to receive code instructions and transmit them to the processor 901. The processor 901 executes the code instructions to enable the communication device 900 to perform the method described in the above method embodiment.

[0329] In one implementation, processor 901 may include a transceiver for implementing receiving and transmitting functions. For example, the transceiver may be a transceiver circuit, an interface, or an interface circuit. The transceiver circuit, interface, or interface circuit for implementing the receiving and transmitting functions may be separate or integrated. The transceiver circuit, interface, or interface circuit may be used for reading and writing code / data, or may be used for transmitting or delivering signals.

[0330] In one implementation, processor 901 may store a computer program 903. Computer program 903, when executed on processor 901, enables communication device 900 to perform the method described in the above method embodiment. Computer program 903 may be embedded in processor 901, in which case processor 901 may be implemented by hardware.

[0331] In one implementation, the communication device 900 may include a circuit that can implement the functions of sending, receiving, or communicating in the aforementioned method embodiments. The processor and transceiver described in the present disclosure can be implemented on an integrated circuit (IC), an analog IC, a radio frequency integrated circuit RFIC, a mixed signal IC, an application specific integrated circuit (ASIC), a printed circuit board (PCB), an electronic device, etc. The processor and transceiver can also be manufactured using various IC process technologies, such as complementary metal oxide semiconductor (CMOS), N-type metal oxide semiconductor (nMetal-oxide-semiconductor, NMOS), P-type metal oxide semiconductor (positive channel metal oxide semiconductor, PMOS), bipolar junction transistor (bipolar junction transistor, BJT), bipolar CMOS (BiCMOS), silicon germanium (SiGe), gallium arsenide (GaAs), etc.

[0332] The communication device described in the above embodiments may be a first entity, a UDM entity, or a GMLC entity, but the scope of the communication device described in this disclosure is not limited thereto, and the structure of the communication device may not be limited to FIG9 . The communication device may be an independent device or may be part of a larger device. For example, the communication device may be:

[0333] (1) An independent integrated circuit (IC), or chip, or chip system or subsystem;

[0334] (2) having a set of one or more ICs, which, in some possible implementations, may also include a storage component for storing data and computer programs;

[0335] (3) ASIC, such as modem;

[0336] (4) Modules that can be embedded in other devices;

[0337] (5) Receivers, terminals, smart terminals, cellular phones, wireless devices, handheld devices, mobile units, vehicle-mounted devices, network devices, cloud devices, artificial intelligence devices, etc.;

[0338] (6)Others, etc.

[0339] For the case where the communication device may be a chip or a chip system, please refer to FIG10 , which is a structural diagram of a chip provided in an embodiment of the present disclosure.

[0340] The chip 1000 includes a processor 1001 and an interface 1003. The number of the processor 1001 can be one or more, and the number of the interface 1003 can be multiple.

[0341] For the case where the chip is used to implement the functions of the terminal in the embodiments of the present disclosure:

[0342] Interface 1003 is used to receive code instructions and transmit them to the processor.

[0343] The processor 1001 is configured to execute code instructions to execute the data processing methods described in some of the above embodiments.

[0344] For the case where the chip is used to implement the function of the transmitter in the embodiments of the present disclosure:

[0345] Interface 1003 is used to receive code instructions and transmit them to the processor.

[0346] The processor 1001 is configured to execute code instructions to execute the data processing methods described in some of the above embodiments.

[0347] In some possible implementations, the chip 1000 further includes a memory 1002 , which is used to store necessary computer programs and data.

[0348] Those skilled in the art will also appreciate that the various illustrative logical blocks and steps listed in the embodiments of the present disclosure may be implemented by electronic hardware, computer software, or a combination of both. Whether such functionality is implemented by hardware or software depends on the specific application and the design requirements of the entire system. Those skilled in the art may use various methods to implement functionality for each specific application, but such implementation should not be construed as exceeding the scope of protection of the embodiments of the present disclosure.

[0349] An embodiment of the present disclosure also provides a communication system, which includes the communication device as the first entity in the embodiment of Figure 8 above, the communication device as the gateway mobile location center GMLC entity, and the communication device as the unified data management UDM entity body, or the system includes the communication device as the first entity end in the embodiment of Figure 9 above, the communication device as the gateway mobile location center GMLC entity, and the communication device as the unified data management UDM entity body.

[0350] The present disclosure also provides a readable storage medium having instructions stored thereon, which implement the functions of any of the above method embodiments when executed by a computer.

[0351] The present disclosure also provides a computer program product, which implements the functions of any of the above method embodiments when executed by a computer.

[0352] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer programs. When the computer program is loaded and executed on a computer, the process or function according to the embodiment of the present disclosure is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer program can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer program can be transmitted from one website, computer, server or data center to another website, computer, server or data center via wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or data center that includes one or more available media integrated therein. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a high-density digital video disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).

[0353] Those skilled in the art will understand that the various numerical numbers such as first and second involved in the present disclosure are only for the convenience of description and are not used to limit the scope of the embodiments of the present disclosure, and also indicate the order of precedence.

[0354] At least one in the present disclosure can also be described as one or more, and multiple can be two, three, four or more. "And / or" describes the association relationship of associated objects, indicating that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship. "At least one of the following items" or similar expressions refers to any combination of these items, including any combination of single items or plural items. For example, at least one of a, b and c can represent: a, or b, or c, or a and b, or a and c, or b and c, or a, b and c. Wherein a, b and c can be single or multiple, respectively. This disclosure is not limited. In the embodiments of the present disclosure, for a technical feature, the technical features in the technical feature are distinguished by "first", "second", "third", "A", "B", "C" and "D", and there is no order of precedence or size between the technical features described by "first", "second", "third", "A", "B", "C" and "D".

[0355] The correspondences shown in the tables of the present disclosure can be configured or predefined. The values ​​of the information in each table are merely examples and can be configured to other values, which are not limited by the present disclosure. When configuring the correspondences between information and parameters, it is not necessarily required to configure all the correspondences shown in each table. For example, in the tables of the present disclosure, the correspondences shown in certain rows may not be configured. For another example, appropriate deformation adjustments can be made based on the above tables, such as splitting, merging, etc. The names of the parameters shown in the titles of the above tables may also adopt other names that can be understood by the communication device, and the values ​​or representations of the parameters may also adopt other values ​​or representations that can be understood by the communication device. When implementing the above tables, other data structures may also be used, such as arrays, queues, containers, stacks, linear lists, pointers, linked lists, trees, graphs, structures, classes, heaps, hash tables or hash tables, etc.

[0356] The predefined in the present disclosure may be understood as defined, predefined, stored, pre-stored, pre-negotiated, pre-configured, solidified, or pre-burned.

[0357] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this disclosure.

[0358] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0359] The above description is merely a specific embodiment of the present disclosure, but the scope of protection of the present disclosure is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this disclosure should be included in the scope of protection of the present disclosure. Therefore, the scope of protection of the present disclosure should be based on the scope of protection of the claims.

Claims

1. A data processing method, characterized in that: Executed by a first entity, the method comprises: Provide first information, wherein the first information is used to assist a unified data management (UDM) entity in creating, updating or deleting a privacy profile of a terminal device, wherein the privacy profile is a file associated with ranging and / or sidechain positioning services.

2. The method according to claim 1, characterized in that The first entity is at least one of the following: a terminal device and an application function AF network element.

3. A data processing method, characterized in that: The method is performed by a gateway mobile location center GMLC entity, and includes: Receiving a service request sent by a sending end, wherein the service request includes an identifier of a terminal device; Obtaining a privacy profile associated with the identifier of the terminal device from a unified data management (UDM) entity, wherein the privacy profile is a file associated with ranging and / or sidechain positioning services; Based on the privacy profile, it is determined whether the service request is allowed.

4. The method according to claim 3, characterized in that The determining, based on the privacy profile, whether the service request is allowed includes: Determining whether the service request is allowed based on an indication of a ranging and / or sidechain positioning privacy indicator in the privacy profile; and / or, Determining whether the service request is allowed based on whether the call and / or session-independent class in the privacy profile contains the identifier of the sender and whether the privacy configuration associated with the identifier of the sender is satisfied; and / or, determining whether the service request is allowed based on whether the location service client list in the privacy profile contains the identifier of the sender; and / or, Whether the service request is allowed is determined based on whether the GMLC address list in the privacy profile contains the address of the GMLC.

5. The method according to claim 4, characterized in that The ranging and / or sidechain positioning privacy indicator is used to indicate one or more of the following: allowing ranging and / or sidechain positioning, not allowing ranging and / or sidechain positioning, and a valid time period of the ranging and / or sidechain positioning privacy indicator.

6. The method according to claim 4, characterized in that The call and / or session-independent class includes at least one of the following: Core network elements, trusted AFs or non-external LCS clients; A first list, wherein the first list includes a first identification of one or more of the following items: an untrusted AF entity, an external location service LCS client; A second list, wherein the second list includes second identifiers of one or more of the following items: a client terminal device (Client UE), a server terminal device (Server UE); A third list includes third identifiers of one or more ranging and / or side-chain positioning applications.

7. The method according to claim 6, characterized in that The call and / or session independent class also includes at least one of the following: A first privacy configuration associated with the core network element, the trusted AF or the non-external LCS client, a second privacy configuration associated with each first identifier in the first list, a third privacy configuration associated with each second identifier in the second list, and a fourth privacy configuration associated with each third identifier in the third list.

8. The method according to claim 7, characterized in that The privacy configuration includes privacy setting information, time setting information and area range setting information.

9. The method according to claim 8, characterized in that The privacy setting information includes any one of the following: Ranging and / or sidechain positioning services are not permitted; Allowing ranging and / or sidechain positioning services without sending notification to the first entity; Allowing ranging and / or side chain positioning services, and sending a notification to the first entity; Allowing ranging and / or side chain positioning services requires sending a notification to the first entity and performing information verification with the first entity; To allow ranging and / or sidechain positioning services, a notification needs to be sent to the first entity and information verification needs to be performed with the first entity. When the first entity does not feed back a verification response, exposing the location of the first entity is allowed; Allowing ranging and / or side chain positioning services requires sending a notification to the first entity and performing information verification with the first entity. If the first entity does not feedback a verification response, it is not allowed to expose the location of the first entity; The time setting information includes any one of the following: a time period in which ranging and / or sidechain positioning services are allowed, and a time period in which ranging and / or sidechain positioning services are not allowed; The area range setting information includes any one of the following: an area range where ranging and / or sidechain positioning services are allowed, and an area range where ranging and / or sidechain positioning services are not allowed.

10. The method according to any one of claims 3 to 9, characterized in that: Also includes: When the ranging and / or sidelink positioning privacy indicator in the privacy profile indicates permission, and the identifier of the sender is not included in the privacy profile, it is determined that the service request is not allowed.

11. A data processing method, characterized in that: Executed by a unified data management (UDM) entity, the method includes: receiving a first message; Based on the first information, a privacy profile of the terminal device is created, updated or deleted, where the privacy profile is a file associated with ranging and / or sidechain positioning services.

12. The method according to claim 11, characterized in that The privacy profile includes at least one of the following: Ranging and / or sidechain positioning privacy indicators, call and / or session independence class, location service client list, Gateway Mobile Location Center GMLC address list.

13. The method according to claim 12, characterized in that The ranging and / or sidechain positioning privacy indicator is used to indicate one or more of the following items: allowing ranging and / or sidechain positioning, not allowing ranging and / or sidechain positioning, and the valid time period of the ranging and / or sidechain positioning indication bit.

14. The method according to claim 12, characterized in that The call and / or session-independent class includes at least one of the following: Core network elements, trusted AFs or non-external LCS clients; A first list, wherein the first list includes a first identification of one or more of the following items: an untrusted AF entity, an external location service LCS client; A second list, wherein the second list includes second identifiers of one or more of the following items: a client terminal device (Client UE), a server terminal device (Server UE); A third list includes third identifiers of one or more ranging and / or side-chain positioning applications.

15. The method according to claim 14, characterized in that The call and / or session independent class also includes at least one of the following: A first privacy configuration associated with the core network element, the trusted AF or the non-external LCS client, a second privacy configuration associated with each first identifier in the first list, a third privacy configuration associated with each second identifier in the second list, and a fourth privacy configuration associated with each third identifier in the third list.

16. The method according to claim 15, characterized in that The privacy configuration includes privacy setting information, time setting information and area range setting information.

17. The method according to claim 16, characterized in that The privacy setting information includes any one of the following: Ranging and / or sidechain positioning services are not permitted; Allowing ranging and / or sidechain positioning services without sending notification to the first entity; Allowing ranging and / or side chain positioning services, and sending a notification to the first entity; Allowing ranging and / or side chain positioning services requires sending a notification to the first entity and performing information verification with the first entity; Allowing ranging and / or side chain positioning services requires sending a notification to the first entity and performing information verification with the first entity, and allowing the location of the first entity to be exposed when the first entity does not feedback a verification response; Allowing ranging and / or side chain positioning services requires sending a notification to the first entity and performing information verification with the first entity. If the first entity does not feedback a verification response, it is not allowed to expose the location of the first entity; The time setting information includes any one of the following: a time period in which ranging and / or sidechain positioning services are allowed, and a time period in which ranging and / or sidechain positioning services are not allowed; The area range setting information includes any one of the following: an area range where ranging and / or sidechain positioning services are allowed, and an area range where ranging and / or sidechain positioning services are not allowed.

18. A first entity, characterized in that: include: The transceiver module is used to provide first information, wherein the first information is used to assist the unified data management (UDM) entity to create, update or delete a privacy profile of the terminal device, and the privacy profile is a file associated with ranging and / or side chain positioning services.

19. A Gateway Mobile Location Center (GMLC) entity, characterized in that: include: A transceiver module, configured to receive a service request sent by a sender, wherein the service request includes an identifier of a terminal device; A processing module, configured to obtain a privacy profile associated with the identifier of the terminal device from a unified data management (UDM) entity, wherein the privacy profile is a file associated with ranging and / or sidechain positioning services; The processing module is further configured to determine whether the service request is allowed based on the privacy profile.

20. A unified data management (UDM) entity, characterized in that: include: A transceiver module, configured to receive first information; A processing module is used to create, update or delete a privacy profile of a terminal device based on the first information, where the privacy profile is a file associated with ranging and / or side chain positioning services.

21. A communication device, characterized in that: The device includes a processor and a memory, wherein a computer program is stored in the memory, and the processor executes the computer program stored in the memory so that the device performs the method as described in any one of claims 1 to 2, or the processor executes the computer program stored in the memory so that the device performs the method as described in any one of claims 3 to 10, or the processor executes the computer program stored in the memory so that the device performs the method as described in any one of claims 11 to 17.

22. A communication device, characterized in that: include: processor and interface circuits; The interface circuit is used to receive code instructions and transmit them to the processor; The processor is used to run the code instructions to execute the method as described in any one of claims 1 to 2, or to run the code instructions to execute the method as described in any one of claims 3 to 10, or to run the code instructions to execute the method as described in any one of claims 11 to 17.

23. A communication system, characterized in that: It includes a first entity, a gateway mobile location center GMLC entity, and a unified data management UDM entity; The first entity is used to execute the method as described in any one of claims 1 to 2, the gateway mobile location center GMLC entity is used to execute the method as described in any one of claims 3 to 10, and the unified data management UDM entity is used to execute the method as described in any one of claims 11 to 17.

24. A computer-readable storage medium for storing instructions, which, when executed, implement the method according to any one of claims 1 to 2, or, when executed, implement the method according to any one of claims 3 to 10, or, when executed, implement the method according to any one of claims 11 to 17.

Citation Information

Patent Citations

  • Data transmission system, method and device thereof

    CN111464934A

  • Location service processing method and related equipment

    CN112788518A

  • Method and network system for performing direct link positioning / ranging procedure in communication system

    CN116097797A

  • Positioning method and apparatus, communication device, and storage medium

    WO2023065086A1