Sensing service privacy

Abstract

There are provided measures for sensing service privacy. Such measures in one embodiment comprise generating sensing services related privacy profile information indicative of a profile type of a sensing services related privacy profile corresponding to said sensing services related privacy profile information, and transmitting said sensing services related privacy profile information, wherein said sensing services related privacy profile information include an indication whether sensing with respect to a profile type dependent sensing target associated with said sensing services related privacy profile information is allowed.

Description

[0001] Title

[0002] Sensing service privacy

[0003] Field

[0004] Various example embodiments relate to sensing service privacy. More specifically, various example embodiments relate to measures (including methods, apparatuses and computer program products) for realizing sensing service privacy.

[0005] Background

[0006] The present specification generally relates to sensing services and privacy aspects in relation to sensing services.

[0007] The goal of a sensing service is to obtain awareness of the scene surrounding a sensing device, which includes the capability to detect, localize and track objects, to form images, and / or to extract features for recognition / classification purposes, etc.

[0008] The integration of sensing and communication (ISAC) can help to achieve both high-data rate communications and high-resolution obstacle detection using the same hardware and spectrum resource. Different types of applications could benefit from the integrated sensing and communication services that a 5thgeneration (5G) or beyond 5G system could provide.

[0009] The sensing service can be requested by a user equipment (UE) or an application function (AF), or an in-network client (e.g., location service (LCS) client) or a network function (NF).

[0010] Various example aspects of example embodiments are set out in the appended claims.

[0011] According to an example aspect, there is provided a method comprising generating sensing services related privacy profile information indicative of a profile type of a sensing services related privacy profile corresponding to said sensing services related privacy profile information, and transmitting said sensing services related privacy profile information, wherein said sensing services related privacy profile information include an indication whether sensing with respect to a profile type dependent sensing target associated with said sensing services related privacy profile information is allowed.

[0012] According to one example aspect, there is provided a method comprising receiving sensing services related privacy profile information indicative of a profile type of a sensing services related privacy profile corresponding to said sensing services related privacy profile information, and storing said sensing services related privacy profile information, wherein said sensing services related privacy profile information include an indication whether sensing with respect to a profile type dependent sensing target associated with said sensing services related privacy profile information is allowed.

[0013] According to one example aspect, there is provided a method comprising receiving a sensing service request, and performing a sensing privacy check in relation to said sensing service request based on sensing services related privacy profile information indicative of a profile type of a sensing services related privacy profile corresponding to said sensing services related privacy profile information, wherein said sensing services related privacy profile information include an indication whether sensing with respect to a profile type dependent sensing target associated with said sensing services related privacy profile information is allowed. According to one example aspect, there is provided an apparatus comprising generating circuitry configured to generate sensing services related privacy profile information indicative of a profile type of a sensing services related privacy profile corresponding to said sensing services related privacy profile information, and transmitting circuitry configured to transmit said sensing services related privacy profile information, wherein said sensing services related privacy profile information include an indication whether sensing with respect to a profile type dependent sensing target associated with said sensing services related privacy profile information is allowed.

[0014] According to one example aspect, there is provided an apparatus comprising receiving circuitry configured to receive sensing services related privacy profile information indicative of a profile type of a sensing services related privacy profile corresponding to said sensing services related privacy profile information, and storing circuitry configured to store said sensing services related privacy profile information, wherein said sensing services related privacy profile information include an indication whether sensing with respect to a profile type dependent sensing target associated with said sensing services related privacy profile information is allowed.

[0015] According to one example aspect, there is provided an apparatus comprising receiving circuitry configured to receive a sensing service request, and performing circuitry configured to perform a sensing privacy check in relation to said sensing service request based on sensing services related privacy profile information indicative of a profile type of a sensing services related privacy profile corresponding to said sensing services related privacy profile information, wherein said sensing services related privacy profile information include an indication whether sensing with respect to a profile type dependent sensing target associated with said sensing services related privacy profile information is allowed.

[0016] According to one example aspect, there is provided an apparatus comprising at least one processor, at least one memory including computer program code, and at least one interface configured for communication with at least another apparatus, the at least one processor, with the at least one memory and the computer program code, being configured to cause the apparatus to perform generating sensing services related privacy profile information indicative of a profile type of a sensing services related privacy profile corresponding to said sensing services related privacy profile information, and transmitting said sensing services related privacy profile information, wherein said sensing services related privacy profile information include an indication whether sensing with respect to a profile type dependent sensing target associated with said sensing services related privacy profile information is allowed.

[0017] According to one example aspect, there is provided an apparatus comprising at least one processor, at least one memory including computer program code, and at least one interface configured for communication with at least another apparatus, the at least one processor, with the at least one memory and the computer program code, being configured to cause the apparatus to perform receiving sensing services related privacy profile information indicative of a profile type of a sensing services related privacy profile corresponding to said sensing services related privacy profile information, and storing said sensing services related privacy profile information, wherein said sensing services related privacy profile information include an indication whether sensing with respect to a profile type dependent sensing target associated with said sensing services related privacy profile information is allowed.

[0018] According to one example aspect, there is provided an apparatus comprising at least one processor, at least one memory including computer program code, and at least one interface configured for communication with at least another apparatus, the at least one processor, with the at least one memory and the computer program code, being configured to cause the apparatus to perform receiving a sensing service request, and performing a sensing privacy check in relation to said sensing service request based on sensing services related privacy profile information indicative of a profile type of a sensing services related privacy profile corresponding to said sensing services related privacy profile information, wherein said sensing services related privacy profile information include an indication whether sensing with respect to a profile type dependent sensing target associated with said sensing services related privacy profile information is allowed.

[0019] According to one example aspect, there is provided a computer program product comprising computer-executable computer program code which, when the program is run on a computer (e.g. a computer of an apparatus according to any one of the aforementioned apparatus-related example aspects of the present disclosure), is configured to cause the computer to carry out the method according to any one of the aforementioned method-related example aspects of the present disclosure.

[0020] Such computer program product may comprise (or be embodied) a (tangible) computer-readable (storage) medium or the like on which the computerexecutable computer program code is stored, and / or the program may be directly loadable into an internal memory of the computer or a processor thereof.

[0021] Any one of the above aspects enables an efficient provision of privacy profiles appropriate for sensing service as well as of privacy checks for sensing services. Various of the above aspects may solve at least part of the problems and drawbacks identified herein in relation to the prior art.

[0022] By way of example embodiments, there is provided sensing service privacy. More specifically, by way of example embodiments, there are provided measures and mechanisms for realizing sensing service privacy.

[0023] Thus, improvement is achieved by methods, apparatuses and computer program products enabling / realizing sensing service privacy.

[0024] Brief description of the drawings

[0025] In the following, the present disclosure will be described in greater detail by way of non-limiting examples with reference to the accompanying drawings, in which Figure 1 is a block diagram illustrating an apparatus according to example embodiments,

[0026] Figure 2 is a block diagram illustrating an apparatus according to example embodiments,

[0027] Figure 3 is a block diagram illustrating an apparatus according to example embodiments,

[0028] Figure 4 is a block diagram illustrating an apparatus according to example embodiments,

[0029] Figure 5 is a block diagram illustrating an apparatus according to example embodiments,

[0030] Figure 6 is a block diagram illustrating an apparatus according to example embodiments,

[0031] Figure 7 is a schematic diagram of a procedure according to example embodiments,

[0032] Figure 8 is a schematic diagram of a procedure according to example embodiments,

[0033] Figure 9 is a schematic diagram of a procedure according to example embodiments,

[0034] Figure 10 shows a schematic diagram of signaling sequences according to example embodiments,

[0035] Figure 11 shows a schematic diagram of signaling sequences according to example embodiments, Figure 12 shows a schematic diagram of signaling sequences according to example embodiments,

[0036] Figure 13 shows a schematic diagram of signaling sequences according to example embodiments,

[0037] Figure 14 shows a schematic diagram of signaling sequences according to example embodiments, and

[0038] Figure 15 is a block diagram alternatively illustrating apparatuses according to example embodiments.

[0039] Detailed description

[0040] The present disclosure is described herein with reference to particular non-limiting examples and to what are presently considered to be conceivable embodiments. A person skilled in the art will appreciate that the disclosure is by no means limited to these examples, and may be more broadly applied.

[0041] It is to be noted that the following description of the present disclosure and its embodiments mainly refers to specifications being used as non-limiting examples for certain example network configurations and deployments. Namely, the present disclosure and its embodiments are mainly described in relation to 3GPP specifications being used as non-limiting examples for certain example network configurations and deployments. As such, the description of example embodiments given herein specifically refers to terminology which is directly related thereto. Such terminology is only used in the context of the presented non-limiting examples, and does naturally not limit the disclosure in any way. Rather, any other communication or communication related system deployment, etc. may also be utilized as long as compliant with the features described herein.

[0042] Hereinafter, various embodiments and implementations of the present disclosure and its aspects or embodiments are described using several variants and / or alternatives. It is generally noted that, according to certain needs and constraints, all of the described variants and / or alternatives may be provided alone or in any conceivable combination (also including combinations of individual features of the various variants and / or alternatives).

[0043] As used herein, "at least one of the following:" and "at least one of" and similar wording, where the list of two or more elements are joined by "and" or "or", mean at least any one of the elements, or at least any two or more of the elements, or at least all the elements.

[0044] Ensuring data privacy of the sensing service and the sensed objects is a key functionality that should be provided by a 5G and beyond communication system.

[0045] Since Sensing may be almost for the whole environment under a radio frequency (R.F) signal coverage, the privacy of sensing operation is an important consideration factor for real deployment.

[0046] For the private area, the private permission is required for sensing operation from such as a homeowner for in-home sensing or the building management for inbuilding sensing. For public areas, such as public road, park and airport, it is required to obtain a permission of the public area management. For specific objects (e.g., rain), content of the sensing result report is limited according to the authority of the sensing requester, for example, climate and rainfall detection can be reported to the Meteorological Bureau.

[0047] For the sensed object that supports 3rdGeneration Partnership Project (3GPP) UE capability, the 5GS should notify the UE about the sensing event and ensure consent of the user before sensing the object.

[0048] These privacy policies need to be configured on the 5GS and can be flexibly modified by the related parties under the operator control. There are various applications that could benefit by sensing services, which could be realized at various environments (e.g., public environments such as roads, indoor areas such as industrial premises), and sensing different type of information (e.g., vehicle, people, buildings, health features, environmental features, etc.), that may be privacy sensitive.

[0049] The different use cases have different privacy requirements, which is important to be embedded in the ISAC systems of 5G and beyond systems, and allow the data owner to define privacy rules and to use them in the different sensing methods and requests.

[0050] The existing privacy mechanisms defined for LCS have been developed having as a core part of their rational a specific UE, described e.g., by its subscription permanent identifier (SUPI). However, this is not adequate for the sensing services.

[0051] Namely, either there is no existing privacy profile data maintained in the 5G Core network or the existing privacy profile data does not support many of the privacy requirements that several use cases have, as follows:

[0052] - to allow or not the sensing of a defined region or geographical area (non UE privacy aspect),

[0053] - to allow or not the detection of connected objects that do not have a SUPI or in general cannot be described with communication related identifiers, and

[0054] - to obfuscate or hide or change important / sensitive features (e.g., size, shape, etc.) of detected objects.

[0055] Further, sensing requests from UE or AF to 5GC should also pass through the required privacy checks, since the area around a UE may include sensitive privacy data (e.g., objects, features, etc.), which is something that is not supported and not needed in the LCS related privacy checks.

[0056] In particular, it is known that a UE can generate (or update) the UE Location Privacy Indication, and that the UE sends the Location Privacy Indication to the AMF in N1 NAS message. The UE Location Privacy Indication indicates whether it allows or disallows responding to the subsequent LCS requests for the UE. Then, an access and mobility function (AMF) invokes a Nudm_ParameterProvision_Update (LCS privacy) service operation towards a unified data management (UDM), and the service operation carries the Location Privacy Indication information. The UDM stores or updates the UE LCS privacy profile in a unified data repository (UDR.) by invoking a Nudr_DM_Update (SUPI, Subscription Data) service operation accordingly.

[0057] Further, it is known that, in the case of a location service request, the target UE's privacy profile settings shall always be checked in the UE's home public land mobile network (PLMN) prior to delivering a location estimate. Specifically, the (H)GMLC invokes a Nudm_SDM_Get service operation towards the UDM of the target UE to get the privacy settings of the UE identified by its GPSI or SUPI.

[0058] The UDM returns the target UE Privacy setting of the UE and the (H)GMLC checks the UE LCS privacy profile. If the target UE is not allowed to be located, then location information of the respective UE is not provided. Similar privacy check takes place before providing location information.

[0059] It is further envisaged that a 5G system shall be able to provide a secure mechanism to ensure sensing result data privacy within the sensing service area. In other words, the need for privacy considerations in the sensing services is recognized, but not addressed in existing specifications yet, considering the specific requirements that sensing procedures have.

[0060] In other words, overall, existing / envisaged 5G system does not have specified privacy functionality for the sensing services, which have new requirements, as described above.

[0061] Hence, the problem arises that privacy functionality for the sensing services is needed. Hence, there is a need to provide for sensing service privacy.

[0062] Various example embodiments aim at addressing at least part of the above issues and / or problems and drawbacks.

[0063] According to example embodiments, in general terms, there are provided measures and mechanisms for (enabling / realizing) sensing service privacy.

[0064] In particular, according to example embodiments, approaches are provided on how e.g., an AF and a UE can define privacy profiles appropriate for a sensing service as well as on new privacy checks needed for sensing services.

[0065] Namely, in brief, according to example embodiments, profiles, methods and functionalities (e.g. 5GS specific functionalities) to enable privacy checks for sensing services in the 5G system are provided.

[0066] Heretofore, first, new privacy profiles and their management are defined.

[0067] Such new sensing privacy profiles are defined to support various types of sensing services including user and non-user related privacy data.

[0068] According to example embodiments, the following types of sensing privacy profiles are introduced:

[0069] - location-aware sensing privacy indication,

[0070] - UE sensing privacy indication, and

[0071] - object-aware sensing privacy indication.

[0072] For example, said profile type may be at least one of the following: location aware type, a terminal type or an object aware type.

[0073] The new sensing privacy profiles according to example embodiments provide information for the configuration and execution of a sensing procedure as well as about whether and which sensing data outputs should be exposed. Heretofore, according to example embodiments, a UDM is enhanced to store and manage user / subscriber related privacy profile information (e.g., UE sensing privacy indication), while non-user related privacy information (e.g., location- aware sensing privacy indication and object-aware sensing privacy indication) can be stored and managed by a new function according to example embodiments, e.g., a sensing management function (SeMF) and / or a repository according to example embodiments, e.g., a sensing data management (SDM), or this sensing data management can be implemented in an existing network function.

[0074] Further, according to example embodiments, signaling is defined to configure and update at the UDM and / or the SeMF or any other network function (NF) the sensing privacy profiles generated or updated by an external entity via an AF or by a UE.

[0075] Further and second, enforcement of the privacy and rules is defined.

[0076] Heretofore, according to example embodiments, a method is provided to enable the sensing privacy checks at the SeMF before the initiation of a sensing procedure, based on the sensing service request by a sensing client and taking into consideration the appropriate sensing privacy profiles.

[0077] In particular, according to example embodiments, the SeMF determines the appropriate sensing configuration according to restrictions or parameters provided by retrieved sensing privacy profiles. Further, according to example embodiments, sensing privacy checks can be performed by the SeMF after finalization of the sensing procedure to determine / check the sensing outputs that could be exposed from the SeMF to the sensing client, according to the relevant sensing privacy profiles.

[0078] In addition, signaling and procedures for privacy check in a sensing service request are defined, while enhancements on the LCS-based architecture, the GMLC function and interfaces / methods of existing location service are provided to enable sensing privacy checks for sensing service requests that use the LCS architecture. According to example embodiments, further, sensing privacy profiles may initiate obfuscation of the sensed data (e.g., obfuscate objects or specific type of objects) and may provide information on the obfuscation configuration, method, etc., that takes place at the SeMF or RAN or another NF.

[0079] Example embodiments are specified below in more detail.

[0080] Figure 1 is a block diagram illustrating an apparatus according to example embodiments. The apparatus may be a network node or entity 10, such as a user equipment or an application function entity, comprising a generating circuitry 11 and a transmitting circuitry 12. The generating circuitry 11 generates sensing services related privacy profile information indicative of a profile type of a sensing services related privacy profile corresponding to said sensing services related privacy profile information. In one example embodiment, a sensing services related privacy profile comprises a privacy profile related to a sensing service; the privacy profile may be of a policy type which may be, for example, a location- aware type, a UE type, and an object-aware type; sensing services related privacy profile information includes the sensing services related privacy profile and a profile type for the sensing services related privacy profile.

[0081] The transmitting circuitry 12 transmits said sensing services related privacy profile information. The sensing services related privacy profile information include an indication whether sensing with respect to a profile type dependent sensing target associated with said sensing services related privacy profile information is allowed. In one example embodiment, said sensing services related privacy profile information includes a profile type dependent sensing target and an indication whether sensing with respect to the profile type dependent sensing target is allowed; a profile type dependent sensing target comprises a target whose sensing is dependent upon the profile type of the target. Figure 7 is a schematic diagram of a procedure according to example embodiments. The apparatus according to Figure 1 may perform the method of Figure 7 but is not limited to this method. The method of Figure 7 may be performed by the apparatus of Figure 1 but is not limited to being performed by this apparatus.

[0082] As shown in Figure 7, a procedure according to example embodiments comprises an operation of generating (S71) sensing services related privacy profile information indicative of a profile type of a sensing services related privacy profile corresponding to said sensing services related privacy profile information, and an operation of transmitting (S72) said sensing services related privacy profile information. The sensing services related privacy profile information include an indication whether sensing with respect to a profile type dependent sensing target associated with said sensing services related privacy profile information is allowed.

[0083] Figure 2 is a block diagram illustrating an apparatus according to example embodiments. In particular, Figure 2 illustrates a variation of the apparatus shown in Figure 1. The apparatus according to Figure 2 may thus further comprise a sending circuitry 21.

[0084] In an embodiment at least some of the functionalities of the apparatus shown in Figure 1 (or 2) may be shared between two physically separate devices forming one operational entity. Therefore, the apparatus may be seen to depict the operational entity comprising one or more physically separate devices for executing at least some of the described processes.

[0085] According to further example embodiments, said profile type is at least one of the following: location-aware sensing privacy related, terminal sensing privacy related, or object-aware sensing privacy related.

[0086] For example, said profile type may be at least one of the following : location aware type, a terminal type or an object aware type. According to example embodiments, examples for a terminal include user equipments (UE), vehicles with communication capabilities, drones with communication capabilities, robots with communication capabilities, etc.

[0087] According to further example embodiments, said profile type is location-aware sensing privacy related, and said sensing services related privacy profile information include at least one of the following: information on a geographical area corresponding to said profile type dependent sensing target, information on a sensing allowance configuration, information on a validity time of said sensing services related privacy profile information, information on exceptions from said sensing services related privacy profile information, information on objects obfuscation, information on a validity time of said indication, information on receivers of outputs of a sensing procedure considering said sensing services related privacy profile information, or information on a setting entity setting said sensing services related privacy profile information.

[0088] According to example embodiments, examples for obfuscation or obfuscation processing (or masking, blurring) include, obfuscating or hiding or changing important / sensitive features (e.g., location, size, shape, etc.) of detected objects.

[0089] According to further example embodiments, said profile type is terminal sensing privacy related, and said sensing services related privacy profile information include at least one of the following: information on a sensing allowance configuration, information on a geographical area for which said indication is valid, information on a time or time period for which said indication is valid, or information on a sensing services role of said profile type dependent sensing target. According to further example embodiments, said profile type is object-aware sensing privacy related, and said sensing services related privacy profile information include at least one of the following: information on an object type of said profile type dependent sensing target, information on a sensing allowance configuration, or information on receivers of outputs of a sensing procedure considering said sensing services related privacy profile information.

[0090] According to further example embodiments, said sensing allowance configuration defines at least one of the following: that obfuscation of object features is enabled, or that no identifier of an object or a terminal is indicated.

[0091] According to a variation of the procedure shown in Figure 7, example details of the transmitting operation (S72) are given, which are inherently independent from each other as such. Such example transmitting operation (S72) according to example embodiments may comprise an operation of sending said sensing services related privacy profile information with a sensing services privacy profile setting request or a sensing services privacy profile create request or a sensing services privacy profile update request.

[0092] According to a variation of the procedure shown in Figure 7, example additional operations are given, which are inherently independent from each other as such. According to such variation, an example method according to example embodiments may comprise an operation of transmitting a sensing services privacy profile deletion request indicative of a sensing services related privacy profile.

[0093] Figure 3 is a block diagram illustrating an apparatus according to example embodiments. The apparatus may be a network node or entity 30, such as a unified data management entity or a sensing management function entity or a sensing data management entity or an entity providing such functionality, comprising a receiving circuitry 31 and a storing circuitry 32. The receiving circuitry 31 receives sensing services related privacy profile information indicative of a profile type of a sensing services related privacy profile corresponding to said sensing services related privacy profile information. The storing circuitry 32 stores said sensing services related privacy profile information. The sensing services related privacy profile information include an indication whether sensing with respect to a profile type dependent sensing target associated with said sensing services related privacy profile information is allowed. Figure 8 is a schematic diagram of a procedure according to example embodiments. The apparatus according to Figure 3 may perform the method of Figure 8 but is not limited to this method. The method of Figure 8 may be performed by the apparatus of Figure 3 but is not limited to being performed by this apparatus.

[0094] As shown in Figure 8, a procedure according to example embodiments comprises an operation of receiving (S81) sensing services related privacy profile information indicative of a profile type of a sensing services related privacy profile corresponding to said sensing services related privacy profile information, and an operation of storing (S82) said sensing services related privacy profile information. The sensing services related privacy profile information include an indication whether sensing with respect to a profile type dependent sensing target associated with said sensing services related privacy profile information is allowed.

[0095] Figure 4 is a block diagram illustrating an apparatus according to example embodiments. In particular, Figure 4 illustrates a variation of the apparatus shown in Figure 3. The apparatus according to Figure 4 may thus further comprise a deleting circuitry 41, a transmitting circuitry 42, a performing circuitry 43, a requesting circuitry 44, a deciding circuitry 45, a determining circuitry 46, and / or a subjecting circuitry 47.

[0096] In an embodiment at least some of the functionalities of the apparatus shown in Figure 3 (or 4) may be shared between two physically separate devices forming one operational entity. Therefore, the apparatus may be seen to depict the operational entity comprising one or more physically separate devices for executing at least some of the described processes.

[0097] According to a variation of the procedure shown in Figure 8, example additional operations are given, which are inherently independent from each other as such. According to such variation, an example method according to example embodiments may comprise an operation of determining at least one network entity to store the received sensing services related privacy profile information.

[0098] According to further example embodiments, said storage device comprises at least one of a unified data repository (UDR.) or unified data management (UDM) or a Sensing Management Function (SeMF) or any storage database.

[0099] Namely, UE specific sensing privacy setting may be initiated by a UE and sensing privacy setting may be initiated by a transmitter (e.g. AF).

[0100] Accordingly, according to example embodiments, the transmitter (e.g. AF) may send via NEF and not directly to UDM, SeMF, SDM, and then, the NEF may decide whether to store in the UDM / UDR. or the SeMF. On the other hand, according to example embodiments, the UE may send directly to the UDM (SeMF, SDM), and then it may be always stored in the UDM.

[0101] According to further example embodiments, said profile type is at least one of the following: location-aware sensing privacy related, terminal sensing privacy related, or object-aware sensing privacy related.

[0102] According to further example embodiments, said profile type is location-aware sensing privacy related, and said sensing services related privacy profile information include at least one of the following: information on a geographical area corresponding to said profile type dependent sensing target, information on a sensing allowance configuration, information on a validity time of said sensing services related privacy profile information, information on exceptions from said sensing services related privacy profile information, information on objects obfuscation, information on a validity time of said indication, information on receivers of outputs of a sensing procedure considering said sensing services related privacy profile information, or information on a setting entity setting said sensing services related privacy profile information.

[0103] According to further example embodiments, said profile type is terminal sensing privacy related, and said sensing services related privacy profile information include at least one of the following: information on a sensing allowance configuration, information on a geographical area for which said indication is valid, information on a time or time period for which said indication is valid, or information on a sensing services role of said profile type dependent sensing target.

[0104] According to further example embodiments, said profile type is object-aware sensing privacy related, and said sensing services related privacy profile information include at least one of the following: information on an object type of said profile type dependent sensing target, information on a sensing allowance configuration, or information on receivers of outputs of a sensing procedure considering said sensing services related privacy profile information.

[0105] According to further example embodiments, said sensing allowance configuration defines at least one of the following: that obfuscation of object features is enabled, or that no identifier of an object or a terminal is indicated. According to further example embodiments, said sensing services related privacy profile information are received with a sensing services privacy profile setting request or a sensing services privacy profile create request or a sensing services privacy profile update request.

[0106] According to a variation of the procedure shown in Figure 8, example additional operations are given, which are inherently independent from each other as such. According to such variation, an example method according to example embodiments may comprise an operation of receiving a sensing services privacy profile deletion request indicative of a sensing services related privacy profile, and an operation of deleting said sensing services related privacy profile information corresponding to said sensing services related privacy profile.

[0107] According to a variation of the procedure shown in Figure 8, example additional operations are given, which are inherently independent from each other as such. According to such variation, an example method according to example embodiments may comprise an operation of transmitting, to at least one subscriber entity, a subscription notification indicative of a sensing services related privacy profile change.

[0108] According to a variation of the procedure shown in Figure 8, example additional operations are given, which are inherently independent from each other as such. According to such variation, an example method according to example embodiments may comprise an operation of receiving a sensing service request, and an operation of performing a sensing privacy check in relation to said sensing service request based on said sensing services related privacy profile information.

[0109] According to a variation of the procedure shown in Figure 8, example additional operations are given, which are inherently independent from each other as such. According to such variation, an example method according to example embodiments may comprise an operation of requesting said sensing services related privacy profile information. According to a variation of the procedure shown in Figure 8, example additional operations are given, which are inherently independent from each other as such. According to such variation, an example method according to example embodiments may comprise an operation of deciding, based on a result of said sensing privacy check, on initiating a sensing procedure corresponding to said sensing service request.

[0110] According to a variation of the procedure shown in Figure 8, example additional operations are given, which are inherently independent from each other as such. According to such variation, an example method according to example embodiments may comprise an operation of determining a sensing configuration for said sensing procedure based on said sensing services related privacy profile information.

[0111] According to a variation of the procedure shown in Figure 8, example additional operations are given, which are inherently independent from each other as such. According to such variation, an example method according to example embodiments may comprise an operation of receiving sensing results in relation to said sensing procedure, and an operation of determining a sensing output based on said sensing results.

[0112] According to example embodiments, examples for sensing results (or sensing measurement information or sensing data) include data derived from radio signals (e.g., 3GPP, non-3GPP, WiFi, radar, Lidars, etc.) impacted (e.g. reflected, refracted, diffracted) by an object or environment of interest for sensing purposes, and optionally processed (e.g., within a 5G / 6G system, external server, application server, edge server, etc.).

[0113] According to example embodiments, examples for sensing output include processed sensing data e.g. requested by a service consumer. According to a variation of the procedure shown in Figure 8, example details of the determining operation are given, which are inherently independent from each other as such. Such example determining operation according to example embodiments may comprise an operation of subjecting said sensing results to an obfuscation processing based on said sensing services related privacy profile information, and / or an operation of subjecting said sensing results to a sensing privacy check based on said sensing services related privacy profile information.

[0114] According to a variation of the procedure shown in Figure 8, example additional operations are given, which are inherently independent from each other as such. According to such variation, an example method according to example embodiments may comprise an operation of deciding, based on a result of said obfuscation processing and / or a result of said sensing privacy check, to transmit said sensing results to a sensing consumer, or an operation of deciding, based on said result of said obfuscation processing and / or said result of said sensing privacy check, to modify features of said sensing results and to transmit said modified sensing results to a sensing consumer.

[0115] According to further example embodiments, said sensing configuration includes an obfuscation configuration. Alternatively, or in addition, according to further example embodiments, said sensing results include obfuscated sensing results.

[0116] According to further example embodiments, said obfuscation configuration includes at least one of the following: information on object features to be obfuscated, information on an obfuscation type, or information on object feature removal.

[0117] According to a variation of the procedure shown in Figure 8, example additional operations are given, which are inherently independent from each other as such. According to such variation, an example method according to example embodiments may comprise an operation of transmitting said obfuscation configuration. Figure 5 is a block diagram illustrating an apparatus according to example embodiments. The apparatus may be a network node or entity 50, such as a sensing management function entity or a sensing data management entity or an entity providing such functionality, comprising a receiving circuitry 51 and a performing circuitry (or checking circuitry) 52. The receiving circuitry 51 receives a sensing service request. The performing circuitry (or checking circuitry) 52 performs a sensing privacy check in relation to said sensing service request based on sensing services related privacy profile information indicative of a profile type of a sensing services related privacy profile corresponding to said sensing services related privacy profile information. The sensing services related privacy profile information include an indication whether sensing with respect to a profile type dependent sensing target associated with said sensing services related privacy profile information is allowed. Figure 9 is a schematic diagram of a procedure according to example embodiments. The apparatus according to Figure 5 may perform the method of Figure 9 but is not limited to this method. The method of Figure 9 may be performed by the apparatus of Figure 5 but is not limited to being performed by this apparatus.

[0118] As shown in Figure 9, a procedure according to example embodiments comprises an operation of receiving (S91) a sensing service request, and an operation of performing (S92) a sensing privacy check in relation to said sensing service request based on sensing services related privacy profile information indicative of a profile type of a sensing services related privacy profile corresponding to said sensing services related privacy profile information. The sensing services related privacy profile information include an indication whether sensing with respect to a profile type dependent sensing target associated with said sensing services related privacy profile information is allowed.

[0119] Figure 6 is a block diagram illustrating an apparatus according to example embodiments. In particular, Figure 6 illustrates a variation of the apparatus shown in Figure 5. The apparatus according to Figure 6 may thus further comprise a requesting circuitry 61, a deciding circuitry 62, a determining circuitry 63, a subjecting circuitry 64, and / or a transmitting circuitry 65.

[0120] In an embodiment at least some of the functionalities of the apparatus shown in Figure 5 (or 6) may be shared between two physically separate devices forming one operational entity. Therefore, the apparatus may be seen to depict the operational entity comprising one or more physically separate devices for executing at least some of the described processes.

[0121] According to a variation of the procedure shown in Figure 9, example additional operations are given, which are inherently independent from each other as such. According to such variation, an example method according to example embodiments may comprise an operation of requesting said sensing services related privacy profile information.

[0122] According to a variation of the procedure shown in Figure 9, example additional operations are given, which are inherently independent from each other as such. According to such variation, an example method according to example embodiments may comprise an operation of deciding, based on a result of said sensing privacy check, on initiating a sensing procedure corresponding to said sensing service request.

[0123] According to a variation of the procedure shown in Figure 9, example additional operations are given, which are inherently independent from each other as such. According to such variation, an example method according to example embodiments may comprise an operation of determining a sensing configuration for said sensing procedure based on said sensing services related privacy profile information.

[0124] According to a variation of the procedure shown in Figure 9, example additional operations are given, which are inherently independent from each other as such. According to such variation, an example method according to example embodiments may comprise an operation of receiving sensing results in relation to said sensing procedure, and an operation of determining a sensing output based on said sensing results.

[0125] According to example embodiments, examples for sensing results (or sensing measurement information or sensing data) include data derived from radio signals (e.g., 3GPP, non-3GPP, WiFi, radar, Lidars, etc.) impacted (e.g. reflected, refracted, diffracted) by an object or environment of interest for sensing purposes, and optionally processed (e.g., within a 5G / 6G system, external server, application server, edge server, etc.).

[0126] According to example embodiments, examples for sensing output include processed sensing data e.g. requested by a service consumer.

[0127] According to a variation of the procedure shown in Figure 8, example details of the determining operation are given, which are inherently independent from each other as such. Such example determining operation according to example embodiments may comprise an operation of subjecting said sensing results to an obfuscation processing based on said sensing services related privacy profile information, and / or an operation of subjecting said sensing results to a sensing privacy check based on said sensing services related privacy profile information.

[0128] According to a variation of the procedure shown in Figure 9, example additional operations are given, which are inherently independent from each other as such. According to such variation, an example method according to example embodiments may comprise an operation of deciding, based on a result of said obfuscation processing and / or a result of said sensing privacy check, to transmit said sensing results to a sensing consumer, or an operation of deciding, based on said result of said obfuscation processing and / or said result of said sensing privacy check, to modify features of said sensing results and to transmit said modified sensing results to a sensing consumer.

[0129] According to further example embodiments, said sensing configuration includes an obfuscation configuration. Alternatively, or in addition, according to further example embodiments, said received sensing results include obfuscated sensing results.

[0130] According to further example embodiments, said obfuscation configuration includes at least one of the following: information on object features to be obfuscated, information on an obfuscation type, or information on object feature removal.

[0131] According to a variation of the procedure shown in Figure 9, example additional operations are given, which are inherently independent from each other as such. According to such variation, an example method according to example embodiments may comprise an operation of transmitting said obfuscation configuration.

[0132] Example embodiments outlined and specified above are explained below in more specific terms.

[0133] With respect to the above outlined definition of new privacy profiles and their management to address the issue how an AF and a UE can define privacy profiles appropriate for a sensing service, according to example embodiments, sensing privacy profiles may be implemented as follows.

[0134] In detail, according to example embodiments, new privacy profiles are defined, and may be set and stored in the core network (CN) (e.g., in the UDM for UE specific profile and a new NF for non UE specific privacy profile) to allow or disallow the sensing service. Three types of privacy profiles have been identified: a) Location-aware sensing privacy indication may include one or more of the following information elements:

[0135] Geographical area description, e.g., using GPS coordinates, everywhere, etc.,

[0136] Sensing is allowed (default),

[0137] Sensing is disallowed, Time period that the sensing privacy indication is valid, Type of objects sensing privacy indication are excepted, Enable objects obfuscation,

[0138] - (Optionally) define the selected configuration or method for obfuscation / masking / blurring of defined or all identified objects, Timestamp or time period that sensing is allowed or not,

[0139] Sensing outputs are provided to defined receivers, in terms of type of consumer, or defined IPs, sensing privacy indication setter, e.g., AF, UE, etc. b) UE sensing privacy indication may include one or more of the following information elements:

[0140] Sensing is allowed (default),

[0141] Sensing is disallowed,

[0142] Sensing is allowed with specific configuration,

[0143] - Enable obfuscation of features of the object,

[0144] - No indication of identifier e.g., SUPI,

[0145] Geographical area where sensing is allowed or disallowed,

[0146] Timestamp,

[0147] Participation (e.g., as sounder or initiator or sensing signals transmitter) for sensing is allowed or not,

[0148] - This is applicable for the case that a UE is requested by another UE or by the network to initiate a sensing procedure. c) Object-aware sensing privacy indication may include one or more of the following information elements:

[0149] Object type,

[0150] - Descriptor of an object category (e.g., people, vehicle) or an object's feature (e.g., size, mobility profile, etc.),

[0151] - Identifier,

[0152] Sensing is allowed (default),

[0153] Sensing is disallowed,

[0154] Sensing is allowed with specific configuration,

[0155] - Enable obfuscation of features of the object,

[0156] - No indication of identifier e.g., SUPI, Sensing outputs are provided to defined receivers, in terms of type of consumer, or defined identifiers (e.g., IP address, credentials, etc.).

[0157] According to example embodiments, the location-aware sensing privacy indication indicates whether the subsequent sensing requests are allowed or disallowed in a specific area.

[0158] Further, according to example embodiments, the UE sensing privacy indication indicates whether the subsequent sensing requests are allowed or disallowed for a specific UE and / or whether to be involved in the sensing procedure.

[0159] Further, according to example embodiments, the object-aware sensing privacy indication indicates whether the subsequent sensing requests are allowed or disallowed for a specific object, according to the respective descriptors.

[0160] The above-mentioned profiles and the comprising features / information consist of two aspects:

[0161] How to configure and / or execute a sensing procedure, and How and whether to expose the sensing data outputs.

[0162] According to example embodiments, different network functions are used to store for different parts of a sensing privacy profile. For instance, the UDM / UDR. may be used for user related privacy profile information (e.g., UE sensing privacy indication), and another dedicated repository or function (e.g., sensing data management function, SeMF) may be used for non-user related privacy information (e.g., location-aware sensing privacy indication and object-aware sensing privacy indication).

[0163] According to further example embodiments, the UE sensing privacy indication is part of the LCS privacy profile stored in the UDM for a UE subscriber.

[0164] With respect to the above outlined definition of new privacy profiles and their management to address the issue how an AF and a UE can define privacy profiles appropriate for a sensing service, according to example embodiments, setting / registration of sensing privacy profiles may be implemented as follows.

[0165] In detail, according to example embodiments, the sensing privacy profiles can be set by an external entity via an AF (e.g., a regulator or a building owner) as shown in Figure 10, or by a UE as shown in Figure 11. Both can set and modify any type and parameter of a sensing privacy profile defined above. It is rational to consider that a UE can set a UE sensing privacy indication, while an AF can set a location- aware sensing privacy indication and / or an object-aware sensing privacy indication. However, example embodiments are not limited to such assignment.

[0166] Figure 10 shows a schematic diagram of signaling sequences according to example embodiments, and in particular illustrates signaling of a new procedure for sensing privacy setting initiated by an AF.

[0167] As illustrated in Figure 10, the AF requests the 5GS via the NEF the sensing privacy profile information (described above).

[0168] According to example embodiments, the AF uses a new service or uses an existing service with enhancements, e.g., Nnef_ParameterProvision_Create (Step 1).

[0169] According to example embodiments, the AF may request to update or delete a sensing privacy profile using new a service or using an existing service with enhancements e.g., Nnef_ParameterProvision_Update and Nnef_ParameterProvision_Delete, respectively.

[0170] If the AF is authorized by the NEF to provision the parameters, then the NEF stores in the 5GC data repository. This data repository could be for example UDM / UDR or SeMF.

[0171] The NEF may optionally determine to selectively store UE specific privacy setting to UDM / UDR. and the others (i.e. non-UE / general privacy setting) to SeMF or to any storage database. Accordingly, according to example embodiments, the NEF requests the UDM / UDR to create, update and store, or delete the provisioned parameters (e.g., via Nudm_ParameterProvision_Create, Nudm_ParameterProvision_Update Request message), which includes the sensing privacy profile information (Steps 3a and 3b).

[0172] In order to support architecture as in Figure 14 discussed below, the NEF may just forward received information from AF to GMLC, i.e., before steps 3a and 3b.

[0173] If the AF is not authorized to provide the sensing privacy profiles, then the NEF indicates the reason of the failure in a sensing privacy profile setting response message (e.g., using Nnef_ParameterProvision_Create / Update / Delete Response message).

[0174] According to example embodiments, the UDM and / or SeMF responds to the request with a sensing privacy parameter create response indicating its successful or unsuccessful creation or update of a sensing privacy profile. If the procedure has failed, the cause value indicates the reason (Step 4a and 4b).

[0175] According to example embodiments, the NEF provides the response to the AF, e.g., via a Nnef_ParameterProvision_Create / Update / Delete Response message (Step 5).

[0176] Figure 11 shows a schematic diagram of signaling sequences according to example embodiments, and in particular illustrates signaling of a new procedure for UE specific sensing privacy setting initiated by a UE.

[0177] As illustrated in Figure 11, according to example embodiments, then the UE sends sensing privacy profile information (UE sensing privacy indication, location-aware sensing privacy indication, or object-aware sensing privacy indication, as described above) to the AMF. The UE may send to AMF for example via UE sensing privacy profile setting request in a N1 NAS message (Step 1).

[0178] According to example embodiments, the AMF requests the UDM to create, update and store the provisioned parameters (e.g., via Nudm_ParameterProvision_Create, Nudm_ParameterProvision_Update Request message), which includes the sensing privacy profile information (Step 2).

[0179] According to example embodiments, the UDM can also store or update the privacy profile in the UD e.g., by invoking a Nudr_DM_Update (SUPI, Subscription Data) service operation accordingly in the case of a UE sensing privacy indication.

[0180] According to example embodiments, the UDM responds to the AMF with a sensing privacy parameter create response indicating its successful or unsuccessful creation or update of a sensing privacy profile. If the procedure failed, the cause value indicates the reason (Step 3).

[0181] According to example embodiments, the AMF responds to the UE via a sensing privacy profile setting response in an N1 NAS message (Step 4).

[0182] According to example embodiments, the UDM can use the UDR, e.g., by means of Nudr_DM, to allow the UDR and / or other NF consumers to retrieve, create, update, subscribe for change notifications, unsubscribe for change notifications and delete sensing privacy profiles stored in the UDR, based on the set of data applicable to the consumer.

[0183] According to example embodiments, a network function (NF) or management entity (e.g., OAM) may also generate or update sensing-related privacy settings using the signaling of Figure 10.

[0184] After the successful completion of step 3 either in an AF-initiated process (Figure 10) or of step 2 in the context of a UE-initiated process (Figure 11), according to example embodiments, the UDM (or SeMF) can notify the subscribed NF (e.g. SeMF, GMLC, NEF) about the updated sensing privacy profile, e.g., via Nudm_SDM_Notification Notify message. This information could be used in ongoing or future sensing procedures and / or privacy checks.

[0185] In the above description, it was assumed that UDM and UDR are used to manage and store, respectively, sensing privacy profiles. However, according to example embodiments, other network functions (existing or new) could be used to store and manage sensing privacy profiles, especially for non UE specific privacy profiles (see figure 10) for sensing privacy setting initiated either by a UE or by an AF. In that case, the setting / registration of sensing privacy profiles described above takes places with the other network functions (e.g., SeMF, sensing data management function, etc.).

[0186] With respect to the above outlined definition of enforcement of the privacy and rules to address the issue as to which the new privacy checks are that are needed for sensing services, according to example embodiments, sensing privacy checks may be implemented as follows.

[0187] Figure 12 shows a schematic diagram of signaling sequences according to example embodiments, and in particular illustrates signaling of a new procedure ensuring privacy concerns related to the sensing service request and corresponding sensing service response.

[0188] When a sensing client (e.g., UE, AF, BS, NF) sends a sensing request to the SeMF directly (NAS or SBA) or via NEF, according to example embodiments, privacy checks are made at the SeMF. Figure 12 presents the signaling of an example procedure for the privacy checks after the reception of a sensing service request according to example embodiments.

[0189] According thereto, the SeMF performs authorization of the sensing client, and according to the type and the attributes of the sensing service request, the SeMF can determine the respective privacy requirements as well as privacy checks that should be made (step 2). According to example embodiments, the SeMF requests from the UDM the sensing privacy profile information (step 3), where the request includes the descriptor of required privacy information such as identifiers of involved UEs (e.g., SUPI), target sensing area, target / requested objects etc.

[0190] According to example embodiments, the SeMF further requests the non UE specific privacy profile (information) from other storage or itself (depends on where non UE specific privacy profile is stored) (step 3), where the request includes the descriptor of required privacy information such as identifiers of involved target sensing area, target / requested objects, etc.

[0191] According to example embodiments, the UDM and / or other NF storing the non UE privacy profile retrieves the appropriate profile and provides to the SeMF (Step 4) the sensing privacy profile information: sensing privacy profiles of the target UE(s): in the case of a sensing request for one or more UEs identified e.g. by its GPSI or SUPI, sensing privacy profiles of the target sensing area: in the case of a sensing request for a defined area, e.g., described by GPS coordinates or other positioning information, sensing privacy profiles of the target object: to get the privacy settings of the objects identified e.g. by the object type, object category, object's features, etc.

[0192] According to example embodiments, the UDM and / or other NF storing the non UE privacy profile settings may also indicate the need to obfuscate objects or specific type of objects, providing also information about the obfuscation configuration, method, etc.

[0193] According to the different options for sensing privacy profiles discussed above, part or all of a sensing privacy profile or specific sensing privacy profiles (e.g., sensing privacy profiles of the target sensing area, sensing privacy profiles of the target object) may be stored in the SeMF or another dedicated function, e.g., sensing data management.

[0194] According to example embodiments, the SeMF conducts the appropriate privacy checks based on the (all) received privacy profiles and the information in the sensing service request (Step 5). For instance, if a sensing process is not allowed, according to the sensing privacy profile, in the described "Location of Sensing" of the sensing service request, then the process may stop and a notification for the reason of the failure may be provided to the sensing client. In addition, as another example, if the requested "Sensing Granularity / Resolution" is not allowed, according to the sensing privacy profile, then an alternative "Sensing Resolution" may be provided if this is acceptable by the sensing client or the sensing process to stop, indicating the reason of the failure.

[0195] Thereinafter, according to example embodiments, the SeMF determines the appropriate sensing configuration, according to the requirements included in the sensing service request and taking into consideration restrictions or parameters provided by the retrieved sensing privacy profiles (step 6), which can be provided to the entities involved in a sensing procedure (e.g., base station (BS), UE, etc.).

[0196] According to example embodiments, the SeMF in collaboration with the involved BSs and / or UEs requests and collects sensing measurement information, according to the selected sensing method. Based on the received inputs, the SeMF determines the sensing output (step 7).

[0197] Optionally, in step 8, the SeMF can obfuscate the objects that have been detected in step 7. The SeMF can change / blur / mask the detected objects to modify one or more of their features (e.g., shape, location, size, etc.), according to preconfigured information and / or privacy sensing profiles received by the UDM.

[0198] According to example embodiments, the SeMF can also apply additional privacy checks (step 9), on the detected objects according to privacy profiles that have been retrieved by the UDM / UDR. Similarly to step 5, the privacy checks can afford one or more of the following aspects: detected UE(s), the sensing area, detected objects, etc., and using information from sensing privacy profiles.

[0199] Finally, according to example embodiments, the SeMF provides the sensing service response to the sensing client (e.g., to the AF via the NEF).

[0200] As another option, the NEF or any existing network function could undertake a part or the whole functionality of "sensing privacy check" of step 5 of Figure 12. In that case, the NEF or an existing network function retrieves sensing privacy profiles from the UDM or another NF (e.g., SeMF). In addition, the NEF can also undertake to conduct the sensing output privacy check (Step 9 of Figure 12).

[0201] Figure 13 shows a schematic diagram of signaling sequences according to example embodiments, and in particular illustrates a procedure to enable and configure the obfuscation before providing the sensing response to the requested sensing services.

[0202] In particular, as a further option, the obfuscation takes place at the RAN side or both at the RAN and CN network side (e.g., SeMF).

[0203] In that case, as it is shown in Figure 13 (Step 7), after the sensing privacy check and the determination of the sensing configurations and determination of privacy information required for anonymization / obfuscation and / or privacy checks, according to example embodiments, the SeMF provides the indication to enable the obfuscation and provides the obfuscation configuration to the RAN entities (e.g., BSs) and / or UEs involved in the sensing process, or the SeMF itself can perform the obfuscation.

[0204] According to example embodiments, obfuscation information can be dedicated messages and / or part of other sensing relevant messages transmitted using NAS and / or RRC and / or application protocol (NGAP) signaling. According to example embodiments, the obfuscation configuration may indicate the type of obfuscation that should be applied: the features of the objects that should be changed / blurred / masked (e.g., object's size, shape, location accuracy), the type of the obfuscation to be applied either by referring to a specific method from a list of methods or by describing the modifications to be applied to a specific feature of an object (e.g., instead of providing the exact shape of an object to represent them as a geometric shape), and / or to remove features of an object that could directly indicate the identity of the object.

[0205] According to example embodiments, the involved UEs and / or RAN entities that have received the obfuscation configuration apply the received configuration during the sensing process and / or before providing their sensing outputs to another entity (e.g., the SeMF), as shown at step 9 of Figure 13.

[0206] Figure 14 shows a schematic diagram of signaling sequences according to example embodiments, and in particular illustrates signaling of a new procedure ensuring privacy concerns related to the sensing service request and corresponding sensing service response in a sensing service request using enhancements to the existing LCS architecture.

[0207] Specifically, this example shows enhancements of existing interfaces of existing location service (presented e.g. in TS 23.273) to provide sensing service.

[0208] The GMLC is the entity that receives the sensing request from the sensing client (e.g., AF) and conducts the steps 2 to 5 of Figure 12, including: determining the respective privacy requirements as well as privacy checks that should be made, requesting and receiving the sensing privacy profile information from the UDM; according to example embodiments, the GMLC may invoke Nudm_SDM_Get service operation towards the UDM to retrieve the appropriate privacy settings, and / or checking the sensing privacy profile in conjunction with the sensing service request; for instance, if one or more UEs or an area are not allowed to be sensed, then, according to example embodiments, the following / subsequent steps are skipped and notifications are provided to the sensing client.

[0209] Thereinafter, according to example embodiments, the GMLC provides the sensing privacy parameters to the AMF and then to the LMF (or SeMF), to be taken into consideration at the sensing configuration and / or sensing procedure. The GMLC is also involved in an additional privacy checks (step 9), on the detected objects according to privacy profiles that have been retrieved by the UDM / UDR. or new NF.

[0210] The above-described procedures and functions may be implemented by respective functional elements, processors, or the like, as described below.

[0211] In the foregoing example description of the network entity, only the units that are relevant for understanding the principles of the disclosure have been described using functional blocks. The network entity may comprise further units that are necessary for its respective operation. However, a description of these units is omitted in this specification. The arrangement of the functional blocks of the devices is not construed to limit the disclosure, and the functions may be performed by one block or further split into sub-blocks.

[0212] When in the foregoing description it is stated that the apparatus, i.e. network entity (or some other means) is configured to perform some function, this is to be construed to be equivalent to a description stating that a (i.e. at least one) processor or corresponding circuitry, potentially in cooperation with computer program code stored in the memory of the respective apparatus, is configured to cause the apparatus to perform at least the thus mentioned function. Also, such function is to be construed to be equivalently implementable by specifically configured circuitry or means for performing the respective function (i.e. the expression "unit configured to" is construed to be equivalent to an expression such as "means for").

[0213] In Figure 15, an alternative illustration of apparatuses according to example embodiments is depicted. As indicated in Figure 15, according to example embodiments, the apparatus (network node or entity) 10' (corresponding to the network node or entity 10) comprises a processor 151, a memory 152 and an interface 153, which are connected by a bus 154 or the like. Further, according to example embodiments, the apparatus (network node or entity) 30' (corresponding to the network node or entity 30) comprises a processor 151, a memory 152 and an interface 153, which are connected by a bus 154 or the like. Further, according to example embodiments, the apparatus (network node or entity) 50' (corresponding to the network node or entity 50) comprises a processor 151, a memory 152 and an interface 153, which are connected by a bus 154 or the like. The apparatuses 10', 30', 50' may be connected via link 155 with other apparatuses, e.g. respective others of apparatuses 10', 30', 50'.

[0214] The processor 151 and / or the interface 153 may also include a modem or the like to facilitate communication over a (hardwire or wireless) link, respectively. The interface 153 may include a suitable transceiver coupled to one or more antennas or communication means for (hardwire or wireless) communications with the linked or connected device(s), respectively. The interface 153 is generally configured to communicate with at least one other apparatus, i.e. the interface thereof.

[0215] The memory 152 may store respective programs assumed to include program instructions or computer program code that, when executed by the respective processor, enables the respective electronic device or apparatus to operate in accordance with the example embodiments.

[0216] In general terms, the respective devices / apparatuses (and / or parts thereof) may represent means for performing respective operations and / or exhibiting respective functionalities, and / or the respective devices (and / or parts thereof) may have functions for performing respective operations and / or exhibiting respective functionalities.

[0217] When in the subsequent description it is stated that the processor (or some other means) is configured to perform some function, this is to be construed to be equivalent to a description stating that at least one processor, potentially in cooperation with computer program code stored in the memory of the respective apparatus, is configured to cause the apparatus to perform at least the thus mentioned function. Also, such function is to be construed to be equivalently implementable by specifically configured means for performing the respective function (i.e. the expression "processor configured to [cause the apparatus to] perform xxx-ing" is construed to be equivalent to an expression such as "means for xxx-ing").

[0218] According to example embodiments, an apparatus representing the network node or entity 10 comprises at least one processor 151, at least one memory 152 including computer program code, and at least one interface 153 configured for communication with at least another apparatus. The processor (i.e. the at least one processor 151, with the at least one memory 152 and the computer program code) is configured to perform generating sensing services related privacy profile information indicative of a profile type of a sensing services related privacy profile corresponding to said sensing services related privacy profile information (thus the apparatus comprising corresponding means for generating), and to perform transmitting said sensing services related privacy profile information, wherein said sensing services related privacy profile information include an indication whether sensing with respect to a profile type dependent sensing target associated with said sensing services related privacy profile information is allowed (thus the apparatus comprising corresponding means for transmitting).

[0219] According to example embodiments, an apparatus representing the network node or entity 30 comprises at least one processor 151, at least one memory 152 including computer program code, and at least one interface 153 configured for communication with at least another apparatus. The processor (i.e. the at least one processor 151, with the at least one memory 152 and the computer program code) is configured to perform receiving sensing services related privacy profile information indicative of a profile type of a sensing services related privacy profile corresponding to said sensing services related privacy profile information (thus the apparatus comprising corresponding means for receiving), and to perform storing said sensing services related privacy profile information, wherein said sensing services related privacy profile information include an indication whether sensing with respect to a profile type dependent sensing target associated with said sensing services related privacy profile information is allowed (thus the apparatus comprising corresponding means for storing).

[0220] According to example embodiments, an apparatus representing the network node or entity 50 comprises at least one processor 151, at least one memory 152 including computer program code, and at least one interface 153 configured for communication with at least another apparatus. The processor (i.e. the at least one processor 151, with the at least one memory 152 and the computer program code) is configured to perform receiving a sensing service request (thus the apparatus comprising corresponding means for receiving), and to perform performing a sensing privacy check in relation to said sensing service request based on sensing services related privacy profile information indicative of a profile type of a sensing services related privacy profile corresponding to said sensing services related privacy profile information, wherein said sensing services related privacy profile information include an indication whether sensing with respect to a profile type dependent sensing target associated with said sensing services related privacy profile information is allowed (thus the apparatus comprising corresponding means for performing (or means for checking)).

[0221] For further details regarding the operability / functionality of the individual apparatuses, reference is made to the above description in connection with any one of Figures 1 to 14, respectively.

[0222] For the purpose of the present disclosure as described herein above, it should be noted that - method steps likely to be implemented as software code portions and being run using a processor at a network server or network entity (as examples of devices, apparatuses and / or modules thereof, or as examples of entities including apparatuses and / or modules therefore), are software code independent and can be specified using any known or future developed programming language as long as the functionality defined by the method steps is preserved;

[0223] - generally, any method step is suitable to be implemented as software or by hardware without changing the idea of the embodiments and its modification in terms of the functionality implemented;

[0224] - method steps and / or devices, units or means likely to be implemented as hardware components at the above-defined apparatuses, or any module(s) thereof, (e.g., devices carrying out the functions of the apparatuses according to the embodiments as described above) are hardware independent and can be implemented using any known or future developed hardware technology or any hybrids of these, such as MOS (Metal Oxide Semiconductor), CMOS (Complementary MOS), BiMOS (Bipolar MOS), BiCMOS (Bipolar CMOS), ECL (Emitter Coupled Logic), TTL (Transistor-Transistor Logic), etc., using for example ASIC (Application Specific IC (Integrated Circuit)) components, FPGA (Field- programmable Gate Arrays) components, CPLD (Complex Programmable Logic Device) components or DSP (Digital Signal Processor) components;

[0225] - devices, units or means (e.g. the above-defined network entity or network register, or any one of their respective units / means) can be implemented as individual devices, units or means, but this does not exclude that they are implemented in a distributed fashion throughout the system, as long as the functionality of the device, unit or means is preserved;

[0226] - an apparatus like the user equipment and the network entity / network register may be represented by a semiconductor chip, a chipset, or a (hardware) module comprising such chip or chipset; this, however, does not exclude the possibility that a functionality of an apparatus or module, instead of being hardware implemented, be implemented as software in a (software) module such as a computer program or a computer program product comprising executable software code portions for execution / being run on a processor; - a device may be regarded as an apparatus or as an assembly of more than one apparatus, whether functionally in cooperation with each other or functionally independently of each other but in a same device housing, for example.

[0227] In general, it is to be noted that respective functional blocks or elements according to above-described aspects can be implemented by any known means, either in hardware and / or software, respectively, if it is only adapted to perform the described functions of the respective parts. The mentioned method steps can be realized in individual functional blocks or by individual devices, or one or more of the method steps can be realized in a single functional block or by a single device.

[0228] Generally, any method step is suitable to be implemented as software or by hardware without changing the idea of the present disclosure. Devices and means can be implemented as individual devices, but this does not exclude that they are implemented in a distributed fashion throughout the system, as long as the functionality of the device is preserved. Such and similar principles are to be considered as known to a skilled person.

[0229] Software in the sense of the present description comprises software code as such comprising code means or portions or a computer program or a computer program product for performing the respective functions, as well as software (or a computer program or a computer program product) embodied on a tangible medium such as a computer-readable (storage) medium having stored thereon a respective data structure or code means / portions or embodied in a signal or in a chip, potentially during processing thereof.

[0230] The present disclosure also covers any conceivable combination of method steps and operations described above, and any conceivable combination of nodes, apparatuses, modules or elements described above, as long as the abovedescribed concepts of methodology and structural arrangement are applicable.

[0231] In view of the above, there are provided measures for sensing service privacy. Such measures in one embodiment comprise generating sensing services related privacy profile information indicative of a profile type of a sensing services related privacy profile corresponding to said sensing services related privacy profile information, and transmitting said sensing services related privacy profile information, wherein said sensing services related privacy profile information include an indication whether sensing with respect to a profile type dependent sensing target associated with said sensing services related privacy profile information is allowed.

[0232] Even though the disclosure is described above with reference to the examples according to the accompanying drawings, it is to be understood that the disclosure is not restricted thereto. Rather, it is apparent to those skilled in the art that the present disclosure can be modified in many ways without departing from the scope of the inventive idea as disclosed herein.

[0233] List of acronyms and abbreviations

[0234] 3GPP Third Generation Partnership Project

[0235] AF application function

[0236] AGV automated guided vehicle

[0237] AMF access and mobility management function

[0238] AMR autonomous mobile robots

[0239] BS base station

[0240] DL downlink

[0241] GMLC gateway mobile location center

[0242] GPS global positioning system

[0243] GPSI generic public subscription identifier

[0244] ISAC integrated sensing and communication

[0245] LCS location service

[0246] LMF location management function

[0247] NAS Non-access Stratum

[0248] NEF network exposure function

[0249] OAM operations, administration and maintenance

[0250] NF network function NLOS non-light of sight

[0251] PCF policy control function

[0252] PLMN Public Land Mobile Network

[0253] QoS quality of service SeMF sensing management function

[0254] SNPN stand-alone non-public network

[0255] V2X vehicular-to-everything

[0256] U2N UE-to-network

[0257] UAV unmanned aerial vehicles UDM unified data management

[0258] UDR unified data repository

[0259] U I uniform resource identifier

[0260] SUPI subscription permanent identifier

[0261] UE user equipment UL uplink

[0262] VR virtual reality

[0263] XR extended reality

Claims

Claims1. A method comprising generating sensing services related privacy profile information indicative of a profile type of a sensing services related privacy profile corresponding to said sensing services related privacy profile information, and transmitting said sensing services related privacy profile information, wherein said sensing services related privacy profile information include an indication whether sensing with respect to a profile type dependent sensing target associated with said sensing services related privacy profile information is allowed.

2. The method according to claim 1, wherein said profile type is at least one of the following: location-aware sensing privacy related, terminal sensing privacy related, or object-aware sensing privacy related.

3. The method according to claim 2, wherein said profile type is location-aware sensing privacy related, and said sensing services related privacy profile information include at least one of the following: information on a geographical area corresponding to said profile type dependent sensing target, information on a sensing allowance configuration, information on a validity time of said sensing services related privacy profile information, information on exceptions from said sensing services related privacy profile information, information on objects obfuscation, information on a validity time of said indication,information on receivers of outputs of a sensing procedure considering said sensing services related privacy profile information, or information on a setting entity setting said sensing services related privacy profile information.

4. The method according to claim 2, wherein said profile type is terminal sensing privacy related, and said sensing services related privacy profile information include at least one of the following: information on a sensing allowance configuration, information on a geographical area for which said indication is valid, information on a time or time period for which said indication is valid, or information on a sensing services role of said profile type dependent sensing target.

5. The method according to claim 2, wherein said profile type is object-aware sensing privacy related, and said sensing services related privacy profile information include at least one of the following: information on an object type of said profile type dependent sensing target, information on a sensing allowance configuration, or information on receivers of outputs of a sensing procedure considering said sensing services related privacy profile information.

6. The method according to any of claims 3 to 5, wherein said sensing allowance configuration defines at least one of the following: that obfuscation of object features is enabled, or that no identifier of an object or a terminal is indicated.

7. The method according to any of claims 1 to 6, wherein in relation to said transmitting, the method further comprisessending said sensing services related privacy profile information with a sensing services privacy profile setting request or a sensing services privacy profile create request or a sensing services privacy profile update request.

8. The method according to any of claims 1 to 7, further comprising transmitting a sensing services privacy profile deletion request indicative of a sensing services related privacy profile.

9. A method comprising receiving sensing services related privacy profile information indicative of a profile type of a sensing services related privacy profile corresponding to said sensing services related privacy profile information, and storing said sensing services related privacy profile information, wherein said sensing services related privacy profile information include an indication whether sensing with respect to a profile type dependent sensing target associated with said sensing services related privacy profile information is allowed.

10. The method according to claim 9, further comprising determining at least one network entity to store the received sensing services related privacy profile information.

11. The method of claim 10, wherein the storage device comprises at least one of a unified data repository (UDR.) or unified data management (UDM) or a Sensing Management Function (SeMF) or any storage database.

12. The method according to any of claims 9 to 11, wherein said profile type is at least one of the following: location-aware sensing privacy related, terminal sensing privacy related, or object-aware sensing privacy related.

13. The method according to claim 12, wherein said profile type is location-aware sensing privacy related, andsaid sensing services related privacy profile information include at least one of the following: information on a geographical area corresponding to said profile type dependent sensing target, information on a sensing allowance configuration, information on a validity time of said sensing services related privacy profile information, information on exceptions from said sensing services related privacy profile information, information on objects obfuscation, information on a validity time of said indication, information on receivers of outputs of a sensing procedure considering said sensing services related privacy profile information, or information on a setting entity setting said sensing services related privacy profile information.

14. The method according to claim 12, wherein said profile type is terminal sensing privacy related, and said sensing services related privacy profile information include at least one of the following: information on a sensing allowance configuration, information on a geographical area for which said indication is valid, information on a time or time period for which said indication is valid, or information on a sensing services role of said profile type dependent sensing target.

15. The method according to claim 12, wherein said profile type is object-aware sensing privacy related, and said sensing services related privacy profile information include at least one of the following: information on an object type of said profile type dependent sensing target,information on a sensing allowance configuration, or information on receivers of outputs of a sensing procedure considering said sensing services related privacy profile information.

16. The method according to any of claims 13 to 15, wherein said sensing allowance configuration defines at least one of the following: that obfuscation of object features is enabled, or that no identifier of an object or a terminal is indicated.

17. The method according to any of claims 9 to 16, wherein said sensing services related privacy profile information are received with a sensing services privacy profile setting request or a sensing services privacy profile create request or a sensing services privacy profile update request.

18. The method according to any of claims 9 to 17, further comprising receiving a sensing services privacy profile deletion request indicative of a sensing services related privacy profile, and deleting said sensing services related privacy profile information corresponding to said sensing services related privacy profile.

19. The method according to any of claims 9 to 18, further comprising transmitting, to at least one subscriber entity, a subscription notification indicative of a sensing services related privacy profile change.

20. The method according to any of claims 9 to 19, further comprising receiving a sensing service request, and performing a sensing privacy check in relation to said sensing service request based on said sensing services related privacy profile information.

21. The method according to any of claims 9 to 20, further comprising requesting said sensing services related privacy profile information.

22. The method according to claim 20 or 21, further comprising deciding, based on a result of said sensing privacy check, on initiating a sensing procedure corresponding to said sensing service request.

23. The method according to claim 22, further comprising determining a sensing configuration for said sensing procedure based on said sensing services related privacy profile information.

24. The method according to claim 22 or 23, further comprising receiving sensing results in relation to said sensing procedure, and determining a sensing output based on said sensing results.

25. The method according to claim 24, wherein in relation to said determining, the method further comprises subjecting said sensing results to an obfuscation processing based on said sensing services related privacy profile information, and / or subjecting said sensing results to a sensing privacy check based on said sensing services related privacy profile information.

26. The method according to claim 25, further comprising deciding, based on a result of said obfuscation processing and / or a result of said sensing privacy check, to transmit said sensing results to a sensing consumer, or deciding, based on said result of said obfuscation processing and / or said result of said sensing privacy check, to modify features of said sensing results and to transmit said modified sensing results to a sensing consumer.

27. The method according to claim 24, wherein said sensing configuration includes an obfuscation configuration, and / or said sensing results include obfuscated sensing results.

28. The method according to claim 27, wherein said obfuscation configuration includes at least one of the following:information on object features to be obfuscated, information on an obfuscation type, or information on object feature removal.

29. The method according to claim 27 or 28, further comprising transmitting said obfuscation configuration.

30. A method comprising receiving a sensing service request, and performing a sensing privacy check in relation to said sensing service request based on sensing services related privacy profile information indicative of a profile type of a sensing services related privacy profile corresponding to said sensing services related privacy profile information, wherein said sensing services related privacy profile information include an indication whether sensing with respect to a profile type dependent sensing target associated with said sensing services related privacy profile information is allowed.

31. The method according to claim 30, further comprising requesting said sensing services related privacy profile information.

32. The method according to claim 30 or 31, further comprising deciding, based on a result of said sensing privacy check, on initiating a sensing procedure corresponding to said sensing service request.

33. The method according to claim 32, further comprising determining a sensing configuration for said sensing procedure based on said sensing services related privacy profile information.

34. The method according to claim 32 or 33, further comprising receiving sensing results in relation to said sensing procedure, and determining a sensing output based on said sensing results.

35. The method according to claim 34, wherein in relation to said determining, the method further comprises subjecting said sensing results to an obfuscation processing based on said sensing services related privacy profile information, and / or subjecting said sensing results to a sensing privacy check based on said sensing services related privacy profile information.

36. The method according to claim 35, further comprising deciding, based on a result of said obfuscation processing and / or a result of said sensing privacy check, to transmit said sensing results to a sensing consumer, or deciding, based on said result of said obfuscation processing and / or said result of said sensing privacy check, to modify features of said sensing results and to transmit said modified sensing results to a sensing consumer.

37. The method according to claim 34, wherein said sensing configuration includes an obfuscation configuration, and / or said sensing results include obfuscated sensing results.

38. The method according to claim 37, wherein said obfuscation configuration includes at least one of the following: information on object features to be obfuscated, information on an obfuscation type, or information on object feature removal.

39. The method according to claim 37 or 38, further comprising transmitting said obfuscation configuration.

40. An apparatus comprising means for performing the method of any of claims 1 to 39.

41. A computer program comprising instructions, which, when executed by an apparatus, cause the apparatus to perform the method of any of claims 1 to 39.

Images