Privacy issues in wireless sensing systems
By implementing methods to manage UE privacy profiles and ensure consent-based sensing operations, the patent addresses privacy issues in wireless sensing systems, enhancing user control and reducing unauthorized data collection.
Patent Information
- Application Number
- PCT/CN2024/078945
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2024-02-28
- Publication Date
- 2025-07-31
AI Technical Summary
Privacy issues arise in wireless sensing systems due to the potential unauthorized sensing and tracking of user equipment (UEs) without user consent, particularly in integrated sensing and communication (ISAC) systems, which can detect and track nearby objects without permission.
Implementing methods to perform sensing, request assisted sensing, and associate sensing results based on UE privacy profiles, ensuring user consent and control over data usage by storing and updating privacy settings through Access and Mobility Management Function (AMF), Unified Data Management (UDM), and Sensing Function (SF) nodes.
The proposed methods respect user privacy choices by ensuring consent-based sensing operations, reducing unauthorized data collection and tracking, thereby enhancing privacy in wireless sensing systems.
Smart Images

Figure CN2024078945_31072025_PF_FP_ABST
Abstract
Description
PRIVACY ISSUES IN WIRELESS SENSING SYSTEMSTECHNICAL FIELD
[0001] This patent document is directed generally to wireless communications.BACKGROUND
[0002] Mobile telecommunication technologies are moving the world toward an increasingly connected and networked society. In comparison with the existing wireless networks, next-generation systems and wireless communication techniques will need to support a much wider range of use-case characteristics and provide a more complex and sophisticated range of access requirements and flexibilities.
[0003] Long-Term Evolution (LTE) is a standard for wireless communication for mobile devices and data terminals developed by 3rd Generation Partnership Project (3GPP) . LTE Advanced (LTE-A) is a wireless communication standard that enhances the LTE standard. The 5th generation of wireless system, known as 5G, advances the LTE and LTE-A wireless standards and is committed to supporting higher data rates, large number of connections, ultra-low latency, high reliability, and other emerging business needs.SUMMARY
[0004] This patent document provides some solutions to privacy issues in wireless sensing systems. The disclosed methods include performing sensing, requesting assisted sensing, and associating sensing results based on user equipment (UE) sensing privacy profiles. The techniques disclosed in this patent document, among other benefits, reduce the privacy issues by respecting user choices.
[0005] A first example wireless communication method includes receiving, by an access and mobility management function (AMF) , a user equipment (UE) sensing privacy setting request. The method further includes transmitting, by the AMF and based on the UE sensing privacy setting request, a sensing privacy service operation indication, where the sensing privacy service operation indication causes a unified data management (UDM) node or a subscribing sensing function (SF) to store or update a UE sensing privacy profile. The method further includes transmitting, by the AMF and based on receiving an indication that the UDM node or the subscribing SF has stored or updated the UE sensing privacy profile, a UE sensing privacy setting response.
[0006] A second example wireless communication method includes determining, by a sensing function (SF) , that a user equipment (UE) sensing privacy profile associated with a UE indicates that the UE supports or is willing to support a sensing. The method further includes transmitting, by the SF and based on the determination, a sensing service request, where the sensing service request includes an identity of the UE requested to perform the sensing. The method further includes receiving, by the SF and in response to the sensing service request, a sensing service response.
[0007] A third example wireless communication method includes receiving, by a radio access network (RAN) , a sensing service request for a target area, where the sensing service request includes an identifier of the RAN. The method further includes determining, by the RAN, whether to request a user equipment (UE) to assist with a sensing. The method further includes transmitting, by the RAN and based on the determination, a sensing result either performed by the RAN or performed by the RAN and an assisting UE.
[0008] A fourth example wireless communication method includes receiving, by a sensing function (SF) , a sensing result of a sensing target that includes a user equipment (UE) . The method further includes determining, by the SF and based on a UE sensing privacy profile associated with the UE, whether to associate the sensing result with an identifier of the UE and transmit an associated result. The method further includes transmitting, by the SF and based on the determination, either the sensing result without association or the associated result.
[0009] A fifth example wireless communication method includes transmitting, by a wireless device, a registration request, where the registration request includes a new or updated user equipment (UE) sensing privacy profile. The method further includes receiving, by the wireless device and in response to the registration request, a registration acknowledgement message.
[0010] Note that where the patent document discloses a method of transmitting an information by a first device to a second device, it will be understood that a method of receiving the information by the second device from the first device is also disclosed. Similarly, where a method of receiving a message by a first device from a second device is disclosed, it will be understood that the message is transmitted by the second device to the first device.
[0011] In yet another example embodiment, a device that is configured or operable to perform the above-described methods is disclosed. The device includes at least one processor configured to implement the above-described methods.
[0012] In yet another example embodiment, the above-described methods are embodied in the form of processor-executable code and stored in a non-transitory computer-readable storage medium. The code included in the computer readable storage medium when executed by a processor, causes the processor to implement the methods described in this patent document.
[0013] The above and other aspects and their implementations are described in greater detail in the drawings, the descriptions, and the claims.BRIEF DESCRIPTION OF THE DRAWINGS
[0014] FIG. 1 illustrates example mono-static integrated sensing and communication (ISAC) systems.
[0015] FIG. 2 illustrates example bi-static ISAC systems.
[0016] FIG. 3 illustrates an example user equipment (UE) sensing privacy setting procedure.
[0017] FIG. 4 illustrates an example sensing service procedure performed by a UE.
[0018] FIG. 5 illustrates an example sensing service procedure performed by a radio access network (RAN) .
[0019] FIG. 6 illustrates an example sensing result exposure procedure.
[0020] FIG. 7 illustrates another example UE sensing privacy setting procedure.
[0021] FIG. 8 illustrates an example UE registration procedure.
[0022] FIG. 9 illustrates another example UE registration procedure.
[0023] FIG. 10 is an example flowchart for setting a UE sensing privacy profile.
[0024] FIG. 11 is an example flowchart for requesting a UE to perform a sensing.
[0025] FIG. 12 is an example flowchart for requesting a UE to assist with a sensing.
[0026] FIG. 13 is an example flowchart for associating a sensing result with a UE.
[0027] FIG. 14 is an example flowchart for registering a UE.
[0028] FIG. 15 illustrates an example block diagram of a hardware platform that may be a part of a network device or a wireless device.
[0029] FIG. 16 illustrates example wireless communication including a Base Station (BS) and User Equipments (UEs) based on some implementations of the disclosed technology.DETAILED DESCRIPTION
[0030] The example headings for the various sections below are used to facilitate the understanding of the disclosed subject matter and do not limit the scope of the claimed subject matter in any way. Accordingly, one or more features of one example section can be combined with one or more features of another example section. Furthermore, 5G terminology is used for the sake of clarity of explanation, but the techniques disclosed in the present document are not limited to 5G technology only and may be used in wireless systems that implemented other protocols.
[0031] I. Introduction
[0032] The present patent document discloses performing sensing, requesting assisted sensing, and associating sensing results based on user equipment (UE) sensing privacy profiles. The disclosed methods, among other benefits, reduce the privacy issues in wireless sensing systems.
[0033] This patent document intends to propose methods to solve the privacy issues in integrated sensing and communication (ISAC) systems. In ISAC systems, all objects (vehicles, humans, objects inside a private property, etc. ) nearby can theoretically be imaged and sensed (detected, tracked, localized) , and thus, may cause privacy issues (people or property that don’ t want to be sensed / localized) .
[0034] Integrated sensing and communication (ISAC) allows the wireless network (Third Generation Partnership Project (3GPP) long-term evolution (LTE) , new radio (NR) , 5th generation (5G) -Advanced, sixth generation (6G) or WiFi, etc. ) to be used as a “radar network” as well, by supporting sensing functions. There are many academic papers discussing the broad concept of ISAC.
[0035] The general procedure of ISAC goes as the following. It can be simply modeled that the reference signal (RS) is a signal completely known to the receiver (including the time and frequency to send it as well as every bit in it) , so when the receiver receives the signal, it can use the received signal y and RS x to calculate channel response h. A simple matched filtering can do it. This is exactly the same as a channel estimation task -to estimate a channel using a known RS. (The relationship is y = h*x, *being the convolution operator. )
[0036] In ISAC, after getting the channel information, the receiver can do some local computing to identify / detect / track target (s) , or to image the surrounding environment, and so on. Theoretically, with enough sensing resolution, any moving or static object can be detected (no matter it is a user device connected to the network or just any object not connected to the network) .
[0037] There are many possible modes to do ISAC, two of them being mono-static and bi-static. Intuitively, they differ from if the ISAC transmitter and receiver are the same or different. FIG. 1 shows mono-static ISAC systems. FIG. 2 shows bi-static ISAC systems.
[0038] ISAC is different from positioning in a way that it is pervasive: positioning can only be used on user equipments (UEs) that are connected to the network, and thus, requires asking for permission in advance, while sensing will apply to all objects within the sensing range. Thus, new privacy issues emerge in ISAC systems.
[0039] In order to protect user’s privacy, it is important to have the user consent before the network uses UEs in providing sensing service. If the sensing results and user IDs are brought together for further processing, user consent is also needed.
[0040] II. Embodiment 1
[0041] Embodiment 1-1 describes procedures performed by a SF relayed by a UDM.
[0042] FIG. 3 shows a UE sensing privacy setting procedure.
[0043] 0. The Sensing Function (SF) (or Network Exposure Function (NEF) , etc. ) may subscribe to Unified Data Management (UDM) notifications of UE sensing privacy profile updates in a certain area. The subscribe request may include the target sensing area so that it can receives all the UE’s privacy profile information in the area.
[0044] 1. If the UE has generated or updated the UE sensing privacy indication, the UE sends the sensing privacy indication to the Access and Mobility Management Function (AMF) via UE Sensing Privacy Setting Request in N1 Network Access Stratum (NAS) message. The UE sensing willingness indication indicates whether it can perform sensing as a sensing node, and / or whether it wants to be sensed as a sensing target.
[0045] UE sensing willingness indication at least includes one of the following global settings:
[0046] - Sensing is not (or not willing to be) supported, which means UE cannot perform sensing operations.
[0047] - Sensing is supported, which means UE has sensing ability. It cannot only act as a sensing object but also act as a sensing node if required. In such cases, UE shall send its sensing capability along with UE sensing willingness indication.
[0048] - Sensing requires notification and verification by the UE user, which means UE has sensing ability but whether it can be used to perform sensing is decided by the UE user. Sensing is supported only if granted by the UE user.
[0049] - Sensed as a potential target is acceptable, which means UE is acceptable to be sensed as a target. Its identity is allowed to be associated with the sensing result for further processing.
[0050] - Sensed as a potential target is prohibited, which means the sensing results and user identification are not allowed to be brought together for further processing.
[0051] - Sensed as a potential target requires notification and verification by the UE user, which means UE’s identity can be associated with the sensing result only if granted by the UE user.
[0052] UE sensing willingness indication can also include the following optional settings:
[0053] - Valid time period for sensing, including start time and end time.
[0054] - Valid geographic area for sensing.
[0055] 2. The AMF invokes a Nudm_ParameterProvision_Update (sensing privacy) service operation towards the UDM and the service operation carries the sensing willingness indication information. The UDM stores or updates the UE sensing privacy profile.
[0056] 3. The AMF responds to the UE via UE Sensing Privacy Setting Response in N1 NAS message.
[0057] 4. UDM notifies the subscribed SF (or NEF, etc. ) of the updated UE sensing privacy profile via Nudm_SDM_Notification Notify message. The SF stores or updates the UE sensing privacy profile.
[0058] 5. AMF also sends the notification of UE sensing privacy to Radio Access Network ( (R) AN) . The RAN stores or updates the UE sensing privacy profile.
[0059] FIG. 4 shows a sensing service procedure performed by a UE. The procedure is implemented when the SF initials a sensing service to ask UE performing sensing.
[0060] 1. If the SF decides to request UE to perform sensing, it should first check UE’s sensing privacy profile. If the UE sensing willingness indication indicates that sensing is not supported, the following procedures should be skipped.
[0061] 2. The SF sends a sensing service request to AMF. The message includes the identity of the UE requested to perform sensing. If the UE sensing willingness indication in UE’s sensing privacy profile indicates that sensing requires notification and verification by the UE user, the message should also include the privacy check indicator.
[0062] 3. If the privacy check indicator is received, AMF asks UE whether it can perform sensing.
[0063] 4. The target UE waits for the user to grant or withhold permission. The UE then returns a notification result to the AMF indicating whether permission is granted or denied for the sensing request. If the UE user denies permission, step 5 should be skipped.
[0064] 5. The UE performs sensing and report the sensing result to AMF.
[0065] 6. The AMF forwards the sensing result to SF. If sensing is refused in step 4 by UE user, the AMF shall return an error response with the error cause indicating that UE user denies permission.
[0066] FIG. 5 shows a sensing service procedure performed by a RAN. The procedure is implemented when the SF initials a sensing service to ask RAN performing sensing.
[0067] 1. The SF requests sensing service for a target area. The request may include the identity of the RAN to perform sensing and the accuracy requirements of the sensing.
[0068] 2. The AMF requests the RAN to perform sensing. The request may include the accuracy requirements of the sensing.
[0069] 3. If the required sensing accuracy is hard to satisfied by the RAN, it may choose to ask UE to perform sensing as assisting node to enhance the accuracy. It should check UE’s sensing privacy profile.
[0070] - If the UE sensing willingness indication indicates that sensing is supported, the RAN can request the UE to perform sensing and report the sensing result. Step 4-5 can be skipped.
[0071] - If the UE sensing willingness indication indicates that sensing is not supported, the RAN cannot request the UE to perform sensing. RAN should perform sensing by itself or ask other UE’s for help. Step 4-5 can be skipped.
[0072] - If the UE sensing willingness indication indicates that the UE must be notified with privacy verification, a notification message is sent from the RAN to the target UE. The RAN can request the UE to perform sensing only if permission is received. Step 4 is continued.
[0073] 4. The RAN asks UE whether it can perform sensing.
[0074] 5. The target UE waits for the user to grant or withhold permission. The UE then returns a notification result to the RAN indicating whether permission is granted or denied for the sensing request. If the UE user denies permission, RAN should perform sensing by itself or ask other UE’s for help.
[0075] 6. The RAN (and UE) perform sensing and report the sensing result to AMF.
[0076] 7. The AMF forwards the sensing result to SF.
[0077] FIG. 6 shows a sensing result exposure procedure. The procedure is implemented when SF receives the sensing result of a sensing target that has a UE,
[0078] 0. The Application Function (AF) may subscribe to the sensing result notification to SF via NEF.
[0079] 1. After the sensing service completed, the sensing result should be sent to SF.
[0080] 2. When SF receives the sensing result of a sensing target that has a UE, it shall first check the UE sensing privacy profile before notifying the subscribed NEF (or AF) about the sensing result.
[0081] - If the UE sensing willingness indication indicates that being sensed as a potential target is acceptable, the SF can associate the sensing results of the target UE with its identity together. Step 3-6 should be skipped.
[0082] - If the UE sensing willingness indication indicates that being sensed as a potential target is prohibited, the SF cannot associate the sensing results of the target UE with its identity. Step 3-6 should be skipped.
[0083] - If the UE sensing willingness indication indicates that being sensed as a potential target requires notification and verification by the UE user, Step 3 should be continued.
[0084] 3. SF sends sensing result association request to AMF. The message should include the UE ID.
[0085] 4. AMF forward the request to UE.
[0086] 5. The UE waits for the user to grant or withhold permission. The UE then returns the result to the AMF indicating whether permission is granted or denied for the sensing result association request. If the UE user denies permission.
[0087] 6. AMF forward the response to SF.
[0088] 7. If the association of UE identity and sensing result is granted by UE user, the SF can associate the sensing results of the target UE with its identity. If the permission is not granted, the SF cannot associate the sensing results of the target UE with its identity. The result is sent to NEF.
[0089] 8. NEF forwards the result to AF.
[0090] Embodiment 1-2 describes procedures performed by a SF directly. Similar to Embodiment 1-1, the AMF can directly notify the subscribed SF (or NEF, etc. ) about UE sensing privacy generating or updating.
[0091] FIG. 7 shows another UE sensing privacy setting procedure.
[0092] 0. The Sensing Function (SF) (or NEF, etc. ) may subscribe to AMF notifications of UE sensing privacy profile updates. The subscribe request may include the target sensing area so that it can receives all the UEs privacy profile information in the area.
[0093] 1. If the UE has generated or updated the UE sensing privacy indication, the UE sends the sensing privacy indication to the AMF via UE Sensing Privacy Setting Request in N1 NAS message. The UE sensing willingness indication indicates whether it can perform sensing as a sensing node, and / or whether it wants to be sensed a sensing target.
[0094] UE sensing willingness indication at least includes one of the following global settings:
[0095] - Sensing is not (or not willing to be) supported, which means UE cannot perform sensing operations.
[0096] - Sensing is supported, which means UE has sensing ability. It cannot only act as a sensing object but also act as a sensing node if required. In such cases, UE shall send its sensing capability along with UE sensing willingness indication.
[0097] - Sensing requires notification and verification by the UE user, which means UE has sensing ability but whether it can be used to perform sensing is decided by the UE user. Sensing is supported only if granted by the UE user.
[0098] - Sensed as a potential target is acceptable, which means UE is acceptable to be sensed as a target. Its identity is allowed to be associated with the sensing result for further processing.
[0099] - Sensed as a potential target is prohibited, which means the sensing results and user identification are not allowed to be brought together for further processing.
[0100] - Sensed as a potential target requires notification and verification by the UE user, which means UE’s identity can be associated with the sensing result only if granted by the UE user.
[0101] UE sensing willingness indication can also include the following optional settings:
[0102] - Valid time period for sensing, including start time and end time.
[0103] - Valid geographic area for sensing.
[0104] 2. The AMF responds to the UE via UE Sensing Privacy Setting Response in N1 NAS message.
[0105] 3. AMF notifies the subscribed SF (or NEF, etc. ) of the updated UE sensing privacy profile. The SF stores or updates the UE sensing privacy profile.
[0106] 4. AMF also sends the notification of UE sensing privacy to (R) AN. The RAN stores or updates the UE sensing privacy profile.
[0107] The privacy check procedure in this embodiment is similar to Embodiment 1-1.
[0108] Embodiment 1-3 describes procedures performed by a UDM directly.
[0109] Similar to Embodiment 1-1, if the sensing function didn’ t subscribe to notifications of UE sensing privacy profile updates, it can obtain the sensing privacy profile of UE from UDM using Nudm_SDM_Get by its Subscription Permanent Identifier (SUPI) or Generic Public Subscription Identifier (GPSI) .
[0110] The privacy check procedure in this embodiment is similar to Embodiment 1-1.
[0111] III. Embodiment 2
[0112] Embodiment 2-1 describes procedures performed by a SF relayed by a UDM.
[0113] FIG. 8 shows a UE indicating its sensing privacy via the registration request message.
[0114] 0. The Sensing Function (SF) (or NEF, etc. ) may subscribe to UDM notifications of UE sensing privacy profile updates in a certain area. The subscribe request may include the target sensing area so that it can receives all the UE’s privacy profile information in the area.
[0115] 1. UE to (R) AN: AN message (AN parameters, Registration Request) . In the registration request, UE should include sensing privacy indication to indicate whether and how it wants to be a part of sensing function.
[0116] UE sensing willingness indication at least includes one of the following global settings:
[0117] - Sensing is not (or not willing to be) supported, which means UE cannot perform sensing operations.
[0118] - Sensing is supported, which means UE has sensing ability. It cannot only act as a sensing object but also act as a sensing node if required. In such cases, UE shall send its sensing capability along with UE sensing willingness indication.
[0119] - Sensing requires notification and verification by the UE user, which means UE has sensing ability but whether it can be used to perform sensing is decided by the UE user. Sensing is supported only if granted by the UE user.
[0120] - Sensed as a potential target is acceptable, which means UE is acceptable to be sensed as a target. Its identity is allowed to be associated with the sensing result for further processing.
[0121] - Sensed as a potential target is prohibited, which means the sensing results and user identification are not allowed to be brought together for further processing.
[0122] - Sensed as a potential target requires notification and verification by the UE user, which means UE’s identity can be associated with the sensing result only if granted by the UE user.
[0123] UE sensing willingness indication can also include the following optional settings:
[0124] - Valid time period for sensing, including start time and end time.
[0125] - Valid geographic area for sensing.
[0126] 2. The (R) AN stores the sensing privacy profile of the UE and selects an AMF .
[0127] 3. (R) AN forward the Registration Request message to the AMF based on the N2 connection of the UE.
[0128] 4. AMF should send UE’s sensing privacy profile to UDM and UDM should store it.
[0129] 5. UDM notifies the subscribed SF (or NEF, etc. ) of the UE sensing privacy profile via Nudm_SDM_Notification Notify message. The SF stores the UE sensing privacy profile.
[0130] 6. AMF to UE: Registration Accept.
[0131] The privacy check procedure in this embodiment is similar to Embodiment 1-1.
[0132] Embodiment 2-2 describes procedures performed by a SF directly. Similar to Embodiment 2-1, the AMF can directly notify the subscribed SF (or NEF, etc. ) about UE sensing privacy generating or updating.
[0133] FIG. 9 shows a UE registration procedure.
[0134] 0. The Sensing Function (SF) (or NEF, etc. ) may subscribe to AMF notifications of UE sensing privacy profile updates in a certain area. The subscribe request may include the target sensing area so that it can receives all the UE’s privacy profile information in the area.
[0135] 1. UE to (R) AN: AN message (AN parameters, Registration Request) . In the registration request, UE should include sensing privacy indication to indicate whether and how it wants to be a part of sensing function.
[0136] UE sensing willingness indication at least includes one of the following global settings:
[0137] - Sensing is not (or not willing to be) supported, which means UE cannot perform sensing operations.
[0138] - Sensing is supported, which means UE has sensing ability. It cannot only act as a sensing object but also act as a sensing node if required. In such cases, UE shall send its sensing capability along with UE sensing willingness indication.
[0139] - Sensing requires notification and verification by the UE user, which means UE has sensing ability but whether it can be used to perform sensing is decided by the UE user. Sensing is supported only if granted by the UE user.
[0140] - Sensed as a potential target is acceptable, which means UE is acceptable to be sensed as a target. Its identity is allowed to be associated with the sensing result for further processing.
[0141] - Sensed as a potential target is prohibited, which means the sensing results and user identification are not allowed to be brought together for further processing.
[0142] - Sensed as a potential target requires notification and verification by the UE user, which means UE’s identity can be associated with the sensing result only if granted by the UE user.
[0143] UE sensing willingness indication can also include the following optional settings:
[0144] - Valid time period for sensing, including start time and end time.
[0145] - Valid geographic area for sensing.
[0146] 2. The (R) AN stores the sensing privacy profile of the UE and selects an AMF .
[0147] 3. (R) AN forward the Registration Request message to the AMF based on the N2 connection of the UE.
[0148] 4. AMF can send UE’s sensing privacy profile to UDM and UDM can store it.
[0149] 5. AMF notifies the subscribed SF (or NEF, etc. ) of the UE sensing privacy. The SF stores the UE sensing privacy profile.
[0150] 6. AMF to UE: Registration Accept.
[0151] The privacy check procedure in this embodiment is similar to Embodiment 1-1.
[0152] Embodiment 2-3 describes procedures performed by a UDM directly.
[0153] Similar to Embodiment 2-1, if the sensing function didn’ t subscribe to notifications of UE sensing privacy profile in advance, it can obtain the sensing privacy profile of UE from UDM using Nudm_SDM_Get by its SUPI or GPSI.
[0154] The privacy check procedure in this embodiment is similar to Embodiment 1-1.
[0155] This patent document discloses:
[0156] - that a UE can send its sensing privacy information to the network, indicating whether it wants to be a part of sensing function, including becoming a potential target, and / or, a functioning node to assist sensing. (This configuration can be changed in time by dynamic indication) .
[0157] - that the sensing privacy profile of the UE can be distributed by AMF to different entities in the network (e.g., UDM, SF, RAN) .
[0158] - that the sensing privacy profile of the UE can be stored by a sensing function in the network. It shall take proper action according to the privacy profile of the UE in sensing process.
[0159] - that the sensing privacy profile of the UE can be stored by RAN. It shall take proper action according to the privacy profile of the UE in sensing process.
[0160] FIG. 10 is an example flowchart for setting a UE sensing privacy profile. Operation 1002 includes receiving, by an access and mobility management function (AMF) , a user equipment (UE) sensing privacy setting request. Operation 1004 includes transmitting, by the AMF and based on the UE sensing privacy setting request, a sensing privacy service operation indication, where the sensing privacy service operation indication causes a unified data management (UDM) node or a subscribing sensing function (SF) to store or update a UE sensing privacy profile. Operation 1006 includes transmitting, by the AMF and based on receiving an indication that the UDM node or the subscribing SF has stored or updated the UE sensing privacy profile, a UE sensing privacy setting response. In some embodiments, the method can be implemented according to Embodiment 1 and Embodiment 2. In some embodiments, performing further steps of the method can be based on a better system performance than a legacy protocol.
[0161] In some embodiments, the UDM node receives a subscription request from a SF or a network exposure function (NEF) and transmits a response acknowledging that a subscription procedure is completed.
[0162] In some embodiments, the subscription request includes a target sensing area, and the SF or the NEF requests to receive all UE sensing privacy profiles in the target sensing area.
[0163] In some embodiments, the UDM node transmits, based on a subscription, a notification to a subscribed SF or a subscribed network exposure function (NEF) when there is a new or updated UE sensing privacy profile.
[0164] In some embodiments, a SF or a network exposure function (NEF) obtains the stored or updated UE sensing privacy profile from the UDM node by a subscription permanent identifier (SUPI) or a generic public subscription identifier (GPSI) of the SF or the NEF.
[0165] In some embodiments, the method further includes transmitting, by the AMF, a UE sensing privacy change notification, where the UE sensing privacy change notification causes a radio access network to store or update the UE sensing privacy profile.
[0166] In some embodiments, the UE sensing privacy setting request includes a UE sensing willingness indication, where the UE sensing willingness indication includes at least one of the following settings: sensing is not or not willing to be supported; sensing is supported; sensing requires a notification and / or verification by a UE user associated with the UE sensing willingness indication; being sensed as a potential target is acceptable; being sensed as a potential target is prohibited; being sensed as a potential target requires a notification and / or verification by a UE user associated with the UE sensing willingness indication; a valid time period for sensing; or a valid geographic area for sensing.
[0167] FIG. 11 is an example flowchart for requesting a UE to perform a sensing. Operation 1102 includes determining, by a sensing function (SF) , that a user equipment (UE) sensing privacy profile associated with a UE indicates that the UE supports or is willing to support a sensing. Operation 1104 includes transmitting, by the SF and based on the determination, a sensing service request, where the sensing service request includes an identity of the UE requested to perform the sensing. Operation 1106 includes receiving, by the SF and in response to the sensing service request, a sensing service response. In some embodiments, the method can be implemented according to Embodiment 1 and Embodiment 2. In some embodiments, performing further steps of the method can be based on a better system performance than a legacy protocol.
[0168] In some embodiments, the sensing service response includes a sensing result performed by the UE or an error response indicating that a UE user associated with the UE has denied a sensing permission request.
[0169] In some embodiments, the sensing service request further includes a privacy check indicator requiring a notification and / or verification by a UE user associated with the UE, where an access and mobility management function (AMF) transmits, based on the privacy check indicator, a sensing permission request and receives, in response to the sensing permission request, a sensing permission response.
[0170] FIG. 12 is an example flowchart for requesting a UE to assist with a sensing. Operation 1202 includes receiving, by a radio access network (RAN) , a sensing service request for a target area, where the sensing service request includes an identifier of the RAN. Operation 1204 includes determining, by the RAN, whether to request a user equipment (UE) to assist with a sensing. Operation 1206 includes transmitting, by the RAN and based on the determination, a sensing result either performed by the RAN or performed by the RAN and an assisting UE. In some embodiments, the method can be implemented according to Embodiment 1 and Embodiment 2. In some embodiments, performing further steps of the method can be based on a better system performance than a legacy protocol.
[0171] In some embodiments, the sensing service request further includes an accuracy requirement of the sensing, where the determination is based on the accuracy requirement of the sensing.
[0172] In some embodiments, the sensing service request is received from a sensing function (SF) and relayed by an access and mobility management function (AMF) , and the sensing result is transmitted to the SF and relayed by the AMF.
[0173] In some embodiments, the accuracy requirement of the sensing requires a UE to assist with the sensing or the RAN decides, based on a local policy, to involve a UE to assist with the sensing, and the method further includes determining, by the RAN, whether a UE sensing privacy profile associated with a UE indicates that the UE supports or is willing to support a sensing.
[0174] In some embodiments, the UE sensing privacy profile associated with the UE indicates that the UE does not support or is not willing to support the sensing, and the method further includes transmitting, by the RAN, a sensing request to another UE to assist with the sensing and / or performing, by the RAN, the sensing.
[0175] In some embodiments, the UE sensing privacy profile associated with the UE indicates that the UE supports or is willing to support the sensing, and the method further includes transmitting, by the RAN, a sensing request for the UE to assist with the sensing.
[0176] In some embodiments, the UE sensing privacy profile associated with the UE includes a UE sensing willingness indication, where the UE sensing willingness indication requires a notification and / or verification by a UE user associated with the UE, and the method further includes transmitting, by the RAN, a sensing permission request and receiving, by the RAN and in response to the sensing permission request, a sensing permission response.
[0177] In some embodiments, the sensing permission request is denied, and the method further includes transmitting, by the RAN, a sensing request to another UE to assist with the sensing and / or performing, by the RAN, the sensing.
[0178] FIG. 13 is an example flowchart for associating a sensing result with a UE. Operation 1302 includes receiving, by a sensing function (SF) , a sensing result of a sensing target that includes a user equipment (UE) . Operation 1304 includes determining, by the SF and based on a UE sensing privacy profile associated with the UE, whether to associate the sensing result with an identifier of the UE and transmit an associated result. Operation 1306 includes transmitting, by the SF and based on the determination, either the sensing result without association or the associated result. In some embodiments, the method can be implemented according to Embodiment 1 and Embodiment 2. In some embodiments, performing further steps of the method can be based on a better system performance than a legacy protocol.
[0179] In some embodiments, the sensing result without association or the associated result is transmitted, in response to a sensing result subscription received from an application function (AF) , to the AF and relayed by a network exposure function (NEF) .
[0180] In some embodiments, the UE sensing privacy profile includes a UE sensing willingness indication, where the UE sensing willingness indication indicates that being sensed as a potential target is prohibited, and the sensing result without association is transmitted.
[0181] In some embodiments, the UE sensing privacy profile includes a UE sensing willingness indication, where the UE sensing willingness indication indicates that being sensed as a potential target is acceptable, and the associated result is transmitted.
[0182] In some embodiments, the UE sensing privacy profile includes a UE sensing willingness indication, where the UE sensing willingness indication requires a notification and / or verification by a UE user associated with the UE, and the method further includes transmitting, by the SF, a sensing result association request, where the sensing result association request includes the identifier of the UE; and receiving, by the SF and in response to the sensing result association request, a sensing result association response.
[0183] In some embodiments, the sensing result association request is denied and the sensing result without association is transmitted, or the sensing result association request is granted and the associated result is transmitted.
[0184] In some embodiments, the sensing result association request is transmitted to the UE and relayed by an access and mobility management function (AMF) , and the sensing result association response is received from the UE and relayed by the AMF.
[0185] FIG. 14 is an example flowchart for registering a UE. Operation 1402 includes transmitting, by a wireless device, a registration request, where the registration request includes a new or updated user equipment (UE) sensing privacy profile. Operation 1404 includes receiving, by the wireless device and in response to the registration request, a registration acknowledgement message. In some embodiments, the method can be implemented according to Embodiment 1 and Embodiment 2. In some embodiments, performing further steps of the method can be based on a better system performance than a legacy protocol.
[0186] In some embodiments, a radio access network (RAN) stores the new or updated UE sensing privacy profile and forwards the registration request to an access and mobility management function (AMF) selected by the RAN, and the registration acknowledgement message is received from the AMF.
[0187] In some embodiments, the AMF transmits a sensing privacy service operation indication, where the sensing privacy service operation indication causes a unified data management (UDM) node or a subscribing sensing function (SF) to store the new or updated UE sensing privacy profile.
[0188] In some embodiments, the UDM node or the AMF receives a subscription request from a SF or a network exposure function (NEF) and transmits a response acknowledging that a subscription procedure is completed.
[0189] In some embodiments, the subscription request includes a target sensing area, and the SF or the NEF requests to receive all UE sensing privacy profiles in the target sensing area.
[0190] In some embodiments, the UDM node or the AMF transmits, based on a subscription, a notification to a subscribed SF or a subscribed network exposure function (NEF) when there is a new or updated UE sensing privacy profile.
[0191] In some embodiments, a SF or a network exposure function (NEF) obtains the new or updated UE sensing privacy profile from the UDM node or the AMF by a subscription permanent identifier (SUPI) or a generic public subscription identifier (GPSI) of the SF or the NEF.
[0192] In some embodiments, the new or updated UE sensing privacy profile includes a UE sensing willingness indication, where the UE sensing willingness indication includes at least one of the following settings: sensing is not or not willing to be supported; sensing is supported; sensing requires a notification and / or verification by a UE user associated with the UE sensing willingness indication; being sensed as a potential target is acceptable; being sensed as a potential target is prohibited; being sensed as a potential target requires a notification and / or verification by a UE user associated with the UE sensing willingness indication; a valid time period for sensing; or a valid geographic area for sensing.
[0193] FIG. 15 shows an example block diagram of a hardware platform 1500 that may be a part of a network device (e.g., a base station (BS) , a transmission and reception point (TRP) , an access and mobility management function (AMF) , a unified data management (UDM) node, a sensing function (SF) , a network exposure function (NEF) , a radio access network (RAN) , or an application function (AF) ) or a wireless device (e.g., a user equipment (UE) ) . The hardware platform 1500 includes at least one processor 1510 and a memory 1505 having instructions stored thereupon. The instructions upon execution by the processor 1510 configure the hardware platform 1500 to perform the operations described in FIGS. 1-14 and in the various embodiments described in this patent document. The transmitter 1515 transmits or sends information or data to another device. For example, a network device transmitter can send a message to a user equipment. The receiver 1520 receives information or data transmitted or sent by another device. For example, a user equipment can receive a message from a network device. For example, a UE, a wireless device, or a network device, as described in the present document, may be implemented using the hardware platform 1500.
[0194] The implementations as discussed above will apply to a wireless communication. FIG. 16 shows an example of a wireless communication system (e.g., a 5G or NR cellular network) that includes a base station 1620 and one or more user equipment (UE) 1611, 1612, and 1613. In some embodiments, the UEs access the BS (e.g., the network) using a communication link to the network (sometimes called uplink direction, as depicted by dashed arrows 1631, 1632, 1633) , which then enables subsequent communication (e.g., shown in the direction from the network to the UEs, sometimes called downlink direction, shown by arrows 1641, 1642, 1643) from the BS to the UEs. In some embodiments, the BS sends information to the UEs (sometimes called downlink direction, as depicted by arrows 1641, 1642, 1643) , which then enables subsequent communication (e.g., shown in the direction from the UEs to the BS, sometimes called uplink direction, shown by dashed arrows 1631, 1632, 1633) from the UEs to the BS. The UE may be, for example, a smartphone, a tablet, a mobile computer, a machine to machine (M2M) device, an Internet of Things (IoT) device, and so on. The UEs described in the present document may be communicatively coupled to the base station 1620 depicted in FIG. 16.
[0195] It will be appreciated by one of skill in the art that the present patent document discloses methods that, among other benefits, reduce privacy issues in wireless sensing systems. The methods disclosed include performing sensing, requesting assisted sensing, and associating sensing results based on user equipment (UE) sensing privacy profiles.
[0196] Some of the embodiments described herein are described in the general context of methods or processes, which may be implemented in one embodiment by a computer program product, embodied in a computer-readable medium, including computer-executable instructions, such as program code, executed by computers in networked environments. A computer-readable medium may include removable and non-removable storage devices including, but not limited to, Read Only Memory (ROM) , Random Access Memory (RAM) , compact discs (CDs) , digital versatile discs (DVD) , etc. Therefore, the computer-readable media can include a non-transitory storage media. Generally, program modules may include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. Computer-or processor-executable instructions, associated data structures, and program modules represent examples of program code for executing steps of the methods disclosed herein. The particular sequence of such executable instructions or associated data structures represents examples of corresponding acts for implementing the functions described in such steps or processes.
[0197] Some of the disclosed embodiments can be implemented as devices or modules using hardware circuits, software, or combinations thereof. For example, a hardware circuit implementation can include discrete analog and / or digital components that are, for example, integrated as part of a printed circuit board. Alternatively, or additionally, the disclosed components or modules can be implemented as an Application Specific Integrated Circuit (ASIC) and / or as a Field Programmable Gate Array (FPGA) device. Some implementations may additionally or alternatively include a digital signal processor (DSP) that is a specialized microprocessor with an architecture optimized for the operational needs of digital signal processing associated with the disclosed functionalities of this application. Similarly, the various components or sub-components within each module may be implemented in software, hardware, or firmware. The connectivity between the modules and / or components within the modules may be provided using any one of the connectivity methods and media that is known in the art, including, but not limited to, communications over the Internet, wired, or wireless networks using the appropriate protocols.
[0198] While this document contains many specifics, these should not be construed as limitations on the scope of an invention that is claimed or of what may be claimed, but rather as descriptions of features specific to particular embodiments. Certain features that are described in this document in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable sub-combination. Moreover, although features may be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claimed combination may be directed to a sub-combination or a variation of a sub-combination. Similarly, while operations are depicted in the drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results.
[0199] Only a few implementations and examples are described, and other implementations, enhancements and variations can be made based on what is described and illustrated in this patent document.
Claims
1.A method of wireless communication, comprising:receiving, by an access and mobility management function (AMF) , a user equipment (UE) sensing privacy setting request;transmitting, by the AMF and based on the UE sensing privacy setting request, a sensing privacy service operation indication, wherein the sensing privacy service operation indication causes a unified data management (UDM) node or a subscribing sensing function (SF) to store or update a UE sensing privacy profile; andtransmitting, by the AMF and based on receiving an indication that the UDM node or the subscribing SF has stored or updated the UE sensing privacy profile, a UE sensing privacy setting response.2.The method of claim 1, wherein the UDM node receives a subscription request from a SF or a network exposure function (NEF) and transmits a response acknowledging that a subscription procedure is completed.3.The method of claim 2, wherein the subscription request comprises a target sensing area, and wherein the SF or the NEF requests to receive all UE sensing privacy profiles in the target sensing area.4.The method of any of claims 1-3, wherein the UDM node transmits, based on a subscription, a notification to a subscribed SF or a subscribed network exposure function (NEF) when there is a new or updated UE sensing privacy profile.5.The method of any of claims 1-4, wherein a SF or a network exposure function (NEF) obtains the stored or updated UE sensing privacy profile from the UDM node by a subscription permanent identifier (SUPI) or a generic public subscription identifier (GPSI) of the SF or the NEF.6.The method of any of claims 1-5, further comprising transmitting, by the AMF, a UE sensing privacy change notification, wherein the UE sensing privacy change notification causes a radio access network to store or update the UE sensing privacy profile.7.The method of any of claims 1-6, wherein the UE sensing privacy setting request comprises a UE sensing willingness indication, and wherein the UE sensing willingness indication comprises at least one of the following settings:sensing is not or not willing to be supported;sensing is supported;sensing requires a notification and / or verification by a UE user associated with the UE sensing willingness indication;being sensed as a potential target is acceptable;being sensed as a potential target is prohibited;being sensed as a potential target requires a notification and / or verification by a UE user associated with the UE sensing willingness indication;a valid time period for sensing; ora valid geographic area for sensing.8.A method of wireless communication, comprising:determining, by a sensing function (SF) , that a user equipment (UE) sensing privacy profile associated with a UE indicates that the UE supports or is willing to support a sensing;transmitting, by the SF and based on the determination, a sensing service request, wherein the sensing service request comprises an identity of the UE requested to perform the sensing; andreceiving, by the SF and in response to the sensing service request, a sensing service response.9.The method of claim 8, wherein the sensing service response comprises:a sensing result performed by the UE; oran error response indicating that a UE user associated with the UE has denied a sensing permission request.10.The method of claim 8 or 9, wherein the sensing service request further comprises a privacy check indicator requiring a notification and / or verification by a UE user associated with the UE, and wherein an access and mobility management function (AMF) transmits, based on the privacy check indicator, a sensing permission request and receives, in response to the sensing permission request, a sensing permission response.11.A method of wireless communication, comprising:receiving, by a radio access network (RAN) , a sensing service request for a target area, wherein the sensing service request comprises an identifier of the RAN;determining, by the RAN, whether to request a user equipment (UE) to assist with a sensing; andtransmitting, by the RAN and based on the determination, a sensing result either performed by the RAN or performed by the RAN and an assisting UE.12.The method of claim 11, wherein the sensing service request further comprises an accuracy requirement of the sensing, and wherein the determination is based on the accuracy requirement of the sensing.13.The method of claim 11 or 12, wherein the sensing service request is received from a sensing function (SF) and relayed by an access and mobility management function (AMF) , and wherein the sensing result is transmitted to the SF and relayed by the AMF.14.The method of claim 12 or 13, wherein the accuracy requirement of the sensing requires a UE to assist with the sensing or the RAN decides, based on a local policy, to involve a UE to assist with the sensing, further comprising determining, by the RAN, whether a UE sensing privacy profile associated with a UE indicates that the UE supports or is willing to support a sensing.15.The method of claim 14, wherein the UE sensing privacy profile associated with the UE indicates that the UE does not support or is not willing to support the sensing, further comprising:transmitting, by the RAN, a sensing request to another UE to assist with the sensing; and / orperforming, by the RAN, the sensing.16.The method of claim 14, wherein the UE sensing privacy profile associated with the UE indicates that the UE supports or is willing to support the sensing, further comprising transmitting, by the RAN, a sensing request for the UE to assist with the sensing.17.The method of claim 14 or 16, wherein the UE sensing privacy profile associated with the UE comprises a UE sensing willingness indication, and wherein the UE sensing willingness indication requires a notification and / or verification by a UE user associated with the UE, further comprising:transmitting, by the RAN, a sensing permission request; andreceiving, by the RAN and in response to the sensing permission request, a sensing permission response.18.The method of claim 17, wherein the sensing permission request is denied, further comprising:transmitting, by the RAN, a sensing request to another UE to assist with the sensing; and / orperforming, by the RAN, the sensing.19.A method of wireless communication, comprising:receiving, by a sensing function (SF) , a sensing result of a sensing target that comprises a user equipment (UE) ;determining, by the SF and based on a UE sensing privacy profile associated with the UE, whether to associate the sensing result with an identifier of the UE and transmit an associated result; andtransmitting, by the SF and based on the determination, either the sensing result without association or the associated result.20.The method of claim 19, wherein the sensing result without association or the associated result is transmitted, in response to a sensing result subscription received from an application function (AF) , to the AF and relayed by a network exposure function (NEF) .21.The method of claim 19 or 20, wherein the UE sensing privacy profile comprises a UE sensing willingness indication, wherein the UE sensing willingness indication indicates that being sensed as a potential target is prohibited, and wherein the sensing result without association is transmitted.22.The method of claim 19 or 20, wherein the UE sensing privacy profile comprises a UE sensing willingness indication, wherein the UE sensing willingness indication indicates that being sensed as a potential target is acceptable, and wherein the associated result is transmitted.23.The method of any of claims 19, 20, or 22, wherein the UE sensing privacy profile comprises a UE sensing willingness indication, and wherein the UE sensing willingness indication requires a notification and / or verification by a UE user associated with the UE, further comprising:transmitting, by the SF, a sensing result association request, wherein the sensing result association request comprises the identifier of the UE; andreceiving, by the SF and in response to the sensing result association request, a sensing result association response.24.The method of claim 23, wherein the sensing result association request is denied and the sensing result without association is transmitted, or wherein the sensing result association request is granted and the associated result is transmitted.25.The method of claim 23 or 24, wherein the sensing result association request is transmitted to the UE and relayed by an access and mobility management function (AMF) , and wherein the sensing result association response is received from the UE and relayed by the AMF.26.A method of wireless communication, comprising:transmitting, by a wireless device, a registration request, wherein the registration request comprises a new or updated user equipment (UE) sensing privacy profile; andreceiving, by the wireless device and in response to the registration request, a registration acknowledgement message.27.The method of claim 26, wherein a radio access network (RAN) stores the new or updated UE sensing privacy profile and forwards the registration request to an access and mobility management function (AMF) selected by the RAN, and wherein the registration acknowledgement message is received from the AMF.28.The method of claim 27, wherein the AMF transmits a sensing privacy service operation indication, and wherein the sensing privacy service operation indication causes a unified data management (UDM) node or a subscribing sensing function (SF) to store the new or updated UE sensing privacy profile.29.The method of claim 28, wherein the UDM node or the AMF receives a subscription request from a SF or a network exposure function (NEF) and transmits a response acknowledging that a subscription procedure is completed.30.The method of claim 29, wherein the subscription request comprises a target sensing area, and wherein the SF or the NEF requests to receive all UE sensing privacy profiles in the target sensing area.31.The method of any of claims 28-30, wherein the UDM node or the AMF transmits, based on a subscription, a notification to a subscribed SF or a subscribed network exposure function (NEF) when there is a new or updated UE sensing privacy profile.32.The method of any of claims 28-31, wherein a SF or a network exposure function (NEF) obtains the new or updated UE sensing privacy profile from the UDM node or the AMF by a subscription permanent identifier (SUPI) or a generic public subscription identifier (GPSI) of the SF or the NEF.33.The method of any of claims 26-32, wherein the new or updated UE sensing privacy profile comprises a UE sensing willingness indication, and wherein the UE sensing willingness indication comprises at least one of the following settings:sensing is not or not willing to be supported;sensing is supported;sensing requires a notification and / or verification by a UE user associated with the UE sensing willingness indication;being sensed as a potential target is acceptable;being sensed as a potential target is prohibited;being sensed as a potential target requires a notification and / or verification by a UE user associated with the UE sensing willingness indication;a valid time period for sensing; ora valid geographic area for sensing.34.An apparatus for wireless communication, comprising a processor, wherein the processor is configured to implement a method recited in any one or more of claims 1 to 33.35.A computer readable program storage medium having code stored thereon, the code, when executed by a processor, causing the processor to implement a method recited in any one or more of claims 1 to 33.
Citation Information
Patent Citations
Method for sensing terminal equipment and communication device
CN115734200A
Implementation method and equipment for perception service
CN116094632A
Perception implementation method and device, communication equipment and storage medium
CN116097689A
Information processing method and device, communication equipment and storage medium
CN117280765A
Perception method and apparatus, and communication device
WO2023083131A1