Method and apparatus for supporting sensing service in wireless communication system

The integration of SSF and SPF in the 5G Core Network allows controlled revocation of sensing service requests and entities, securing and regulating sensing data access, addressing unauthorized access and compliance issues in 5G wireless sensing systems.

WO2026235320A1PCT designated stage Publication Date: 2026-11-12SAMSUNG ELECTRONICS CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/KR2026/005751
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-05-05
Filing Date
2026-04-30
Publication Date
2026-11-12

AI Technical Summary

Technical Problem

The challenge in 5G wireless sensing systems is the need to protect sensing data from unauthorized access, interception, and eavesdropping while ensuring compliance with regulations and user awareness, particularly in the context of authorization and revocation of sensing service requests and entities.

Method used

A method and system are proposed to revoke the authorization of sensing service requests and entities by integrating a Sensing Service Function (SSF) and Sensing Profile Function (SPF) within the 5G Core Network, allowing entities like Application Function (AF) and Network Exposure Function (NEF) to trigger revocation through specific APIs when sensing services are no longer needed or authorization data updates occur.

Benefits of technology

This approach ensures secure and regulated handling of sensing data by enabling controlled revocation of sensing services, enhancing data privacy and compliance, thus addressing the challenges of unauthorized access and regulatory requirements.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure KR2026005751_12112026_PF_FP_ABST
    Figure KR2026005751_12112026_PF_FP_ABST
Patent Text Reader

Abstract

The disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. Embodiment herein disclose a method performed by a sensing service function (SSF) for supporting a sensing service. The method may comprise receiving, from a network entity, a request for revoking a sensing service handled by the SSF; terminating an operation for the sensing service based on receiving the request for revoking the sensing service; and transmitting, to the network entity, a response to the request for revoking the sensing service.
Need to check novelty before this filing date? Find Prior Art

Description

METHOD AND APPARATUS FOR SUPPORTING SENSING SERVICE IN WIRELESS COMMUNICATION SYSTEM

[0001] Embodiments disclosed herein relate to integrated sensing and communication in a wireless communication system, and more particularly to a method and the wireless communication system for revoking an authorization of application function of a sensing service request in the wireless communication system.

[0002] 5G mobile communication technologies define broad frequency bands such that high transmission rates and new services are possible, and can be implemented not only in "Sub 6GHz" bands such as 3.5GHz, but also in "Above 6GHz" bands referred to as mmWave including 28GHz and 39GHz. In addition, it has been considered to implement 6G mobile communication technologies (referred to as Beyond 5G systems) in terahertz bands (for example, 95GHz to 3THz bands) in order to accomplish transmission rates fifty times faster than 5G mobile communication technologies and ultra-low latencies one-tenth of 5G mobile communication technologies.

[0003] At the beginning of the development of 5G mobile communication technologies, in order to support services and to satisfy performance requirements in connection with enhanced Mobile BroadBand (eMBB), Ultra Reliable Low Latency Communications (URLLC), and massive Machine-Type Communications (mMTC), there has been ongoing standardization regarding beamforming and massive MIMO for mitigating radio-wave path loss and increasing radio-wave transmission distances in mmWave, supporting numerologies (for example, operating multiple subcarrier spacings) for efficiently utilizing mmWave resources and dynamic operation of slot formats, initial access technologies for supporting multi-beam transmission and broadbands, definition and operation of BWP (BandWidth Part), new channel coding methods such as a LDPC (Low Density Parity Check) code for large amount of data transmission and a polar code for highly reliable transmission of control information, L2 pre-processing, and network slicing for providing a dedicated network specialized to a specific service.

[0004] Currently, there are ongoing discussions regarding improvement and performance enhancement of initial 5G mobile communication technologies in view of services to be supported by 5G mobile communication technologies, and there has been physical layer standardization regarding technologies such as V2X (Vehicle-to-everything) for aiding driving determination by autonomous vehicles based on information regarding positions and states of vehicles transmitted by the vehicles and for enhancing user convenience, NR-U (New Radio Unlicensed) aimed at system operations conforming to various regulation-related requirements in unlicensed bands, NR UE Power Saving, Non-Terrestrial Network (NTN) which is UE-satellite direct communication for providing coverage in an area in which communication with terrestrial networks is unavailable, and positioning.

[0005] Moreover, there has been ongoing standardization in air interface architecture / protocol regarding technologies such as Industrial Internet of Things (IIoT) for supporting new services through interworking and convergence with other industries, IAB (Integrated Access and Backhaul) for providing a node for network service area expansion by supporting a wireless backhaul link and an access link in an integrated manner, mobility enhancement including conditional handover and DAPS (Dual Active Protocol Stack) handover, and two-step random access for simplifying random access procedures (2-step RACH for NR). There also has been ongoing standardization in system architecture / service regarding a 5G baseline architecture (for example, service based architecture or service based interface) for combining Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC) for receiving services based on UE positions.

[0006] As 5G mobile communication systems are commercialized, connected devices that have been exponentially increasing will be connected to communication networks, and it is accordingly expected that enhanced functions and performances of 5G mobile communication systems and integrated operations of connected devices will be necessary. To this end, new research is scheduled in connection with eXtended Reality (XR) for efficiently supporting AR (Augmented Reality), VR (Virtual Reality), MR (Mixed Reality) and the like, 5G performance improvement and complexity reduction by utilizing Artificial Intelligence (AI) and Machine Learning (ML), AI service support, metaverse service support, and drone communication.

[0007] Furthermore, such development of 5G mobile communication systems will serve as a basis for developing not only new waveforms for providing coverage in terahertz bands of 6G mobile communication technologies, multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), array antennas and large-scale antennas, metamaterial-based lenses and antennas for improving coverage of terahertz band signals, high-dimensional space multiplexing technology using OAM (Orbital Angular Momentum), and RIS (Reconfigurable Intelligent Surface), but also full-duplex technology for increasing frequency efficiency of 6G mobile communication technologies and improving system networks, AI-based communication technology for implementing system optimization by utilizing satellites and AI (Artificial Intelligence) from the design stage and internalizing end-to-end AI support functions, and next-generation distributed computing technology for implementing services at levels of complexity exceeding the limit of UE operation capability by utilizing ultra-high-performance communication and computing resources.

[0008] Currently, fifth generation (5G) wireless sensing is a technology enabler to acquire information about characteristics of an environment and / or objects within the environment, that uses radio waves to determine the distance (range), angle, or instantaneous linear velocity of objects, etc. The 5G wireless sensing service relies on analyzing the transmissions, reflections, and scattering of wireless sensing signals.

[0009] This technical report investigates the potential of integrated sensing and communication technology for enabling new services and use cases for various industries. The 5G wireless sensing service, as part of a cellular network provides new possibilities for enhanced usage of the telecommunication infrastructure in areas of object detection and tracking, environment monitoring and human motion monitoring. It provides input to various verticals - Unmanned Aerial Vehicles (UAVs), smart home, Vehicle-to-Everything (V2X), factories.

[0010] The use cases examined in the report cover a wide range of applications, including:

[0011] - Object and intruder detection for smart home, on a highway, for railways, for factory, for predefined secure areas around critical infrastructure.

[0012] - Collision avoidance and trajectory tracking of UAVs, vehicles, AGVs.

[0013] - Automotive maneuvering and navigation.

[0014] - Public safety search and rescue.

[0015] - Rainfall monitoring and flooding.

[0016] - Health and sports monitoring.

[0017] The use cases focus is on 5G wireless sensing and some of the use cases could include non-3GPP type sensors (e.g. Radar, camera or the like). The 5G wireless sensing service also brings challenges related to confidentiality and privacy. There is a need to protect the sensing data from unauthorized access, interception and eavesdropping, but also to make sure there is compliance with regulation and user awareness.

[0018] In Rel 20, 3GPP SA2 WG started studying the sensing service requirement and in TR 23700-14, some 6 Key Issues were identified.

[0019] KI 1 # System Architecture to Support Sensing:This key issue will address the general system architecture and function enhancements required to provide end-to-end support for sensing. The general architecture aspects that need to be studied include any new and / or existing functions in the Core Network and their interactions that should be involved in providing support for sensing. Potential privacy requirements if identified will be considered for this key issue.

[0020] Solutions for other key issues may also impact general architecture aspects covered by this key issue.

[0021] KI#2 Authorization and Revocation to Support Sensing Service:The key issue is to address the authorization and revocation for a particular sensing service, specifically:

[0022] - authorization of sensing service requests and revocation of an on-going sensing service; and

[0023] - authorization and revocation for the sensing entities if applicable.

[0024] For the authorization of the sensing service request, and the revocation of an on-going sensing service, the study needs to address the following aspects:

[0025] - whether and how to perform sensing service request authorization if required, and the criteria for the sensing service request authorization, based on the requirements from TS 22.137;

[0026] - whether and how to perform sensing service revocation if required, and the criteria for the revocation, based on the requirements from TS 22.137;

[0027] - whether, how and which entity( / entities) performs the sensing service request authorization and sensing service revocation if required;

[0028] - whether and where to store the sensing service request authorization information and sensing service revocation information, and when and how to update the authorization and revocation information if required.

[0029] For the authorization and revocation for the sensing entities if applicable, the study needs to address the following aspects:

[0030] - whether, when and which entity performs the authorization and revocation of the sensing entity( / entities);

[0031] - if needed, the granularity of the sensing entity authorization, e.g. based on TS 22.137;

[0032] - if needed, storage and management of the authorization information for the sensing entities.

[0033] NOTE: The authorization and revocation for the sensing entities can be related to the key issue #3 on sensing entities discovery and selection.

[0034] KI#3: Sensing Entity and Sensing Function Discovery and (Re-)Selection:This key issue aims to study how to perform the Sensing entity(ies) and Sensing Function(s) discovery and (re-)selection, in particular:

[0035] When required, for the discovery and (re-)selection of the Sensing entity(ies), the study needs to address the following aspects:

[0036] - Which entity(ies) performs the discovery and (re-)selection of the Sensing entity(ies);

[0037] - What the information and / or criteria are taken into account for the discovery and (re-)selection of the Sensing entity(ies); and

[0038] - The procedure(s) for the discovery and (re-)selection of the Sensing entity(ies).

[0039] When required, for the discovery and (re-)selection of the Sensing Function(s), the study needs to address the following aspects:

[0040] - Which entity(ies) performs the discovery and (re-)selection of Sensing Function(s);

[0041] - What the information and / or criteria are taken into account for the discovery and (re-)selection of Sensing Function(s); and

[0042] - The procedure(s) for the discovery and (re-)selection of the Sensing Function(s).

[0043] KI#4: Sensing Data and the Associated Information Collection and Transport:Integration of sensing and communication requires 3GPP network to collect and transfer sensing data and the associated information to a Sensing Function. This Key Issue aims to study:

[0044] - How to collect sensing data (and the associated information, if any) for sensing result generation?

[0045] - Which Sensing Function performs sensing result generation?

[0046] - Whether and what the above associated information is required for sensing result generation

[0047] NOTE: Implications to RAN or RAN dependent aspects will be coordinated with RAN WGs.

[0048] KI#5: Sensing Result Exposure:This key issue addresses the exposure of sensing results to support sensing services. The aspects to be studied in this key issue include:

[0049] Study what types of sensing results with or without the sensing contextual information defined in TS 22.137 could be exposed from the Core Network to the sensing service consumer.

[0050] - How the Core Network exposes sensing results to the sensing service consumer (e.g., one time, periodic or event trigger).

[0051] KI#6: Configuration and Parameter Provisioning of Sensing Entities.This Key Issue will study how parameter provisioning of sensing entities is performed.

[0052] In particular, this Key Issue will study: How and what parameters need to be exchanged between the sensing entities and the Core Network.

[0053] This KI needs to be aligned with RAN WGs.

[0054] In the proposed method and system, KI#2, solution will be provided which is to revoke the authorization of the application function and specific sensing service request before providing the sensing service in 5GC.

[0055] An object of the embodiments herein is to disclose a method and a wireless communication system for revoking an authorization of application function of a sensing service request in the wireless communication system.

[0056] An object of the embodiments herein is to disclose that revocation triggered by sensing service consumer itself (i.e. by an Application Function (AF) entity) when no longer needed sensing service.

[0057] An object of the embodiments herein is to disclose that revocation triggered by a network entity when there is some update happens in the AF authorization data or sensing service operation is finished.

[0058] An object of the embodiments herein is to disclose that for an untrusted AF entity, a Network Exposure Function (NEF) entity exposes one service application programming interface (API) using which AF (AF initiated) will trigger revoke service operation and then the NEF entity use a Sensing Function (SF) entity / Sensing Service Function (SSF) entity supported service API for revocation for the use cases like when the AF entity does not need sensing service anymore.

[0059] An object of the embodiments herein is to disclose that for trusted AF, the SF entity / the SSF entity supported service API for revocation can be used.

[0060] Another object of the embodiments herein is to disclose that the SF entity / SSF entity will revoke the authorization if the updated AF authorization data is no more authorized to get sensing service or sensing service operation is finished.

[0061] An object of the embodiments herein is to disclose that the SF entity / SSF entity and the NEF entity through the proposed NOTIFY service API to the AF entity that sensing service authorization has been revoked.

[0062] According to an embodiment of the present disclosure, a method performed by a sensing service function (SSF) for supporting a sensing service in a wireless communication system is provided. The method may comprise receiving, from a network entity, a request for revoking a sensing service handled by the SSF; terminating an operation for the sensing service based on receiving the request for revoking the sensing service; and transmitting, to the network entity, a response to the request for revoking the sensing service.

[0063] The network entity may be an application function (AF) or a network exposure function (NEF).

[0064] The revoking of the sensing service may be determined by the AF based on the AF needing the sensing service no longer.

[0065] The method may comprise receiving, from a sensing profile function (SPF), an updated authorization data for the AF; and determining to terminate the operation for the sensing service based on the received updated authorization data, or based on identifying the sensing service is completed.

[0066] The method may comprise transmitting, to the network entity, a notification indicating a termination of the sensing service.

[0067] According to an embodiment of the present disclosure, a sensing service function (SSF) for supporting a sensing service is provided in a wireless communication system. The SSF may comprise memory storing instruction; and at least one processor operably coupled to the memory. The instructions may be executable by the at least one processor to cause the SSF to perform operations. The operations may comprise receiving, from a network entity, a request for revoking a sensing service handled by the SSF; terminating an operation for the sensing service based on receiving the request for revoking the sensing service; and transmitting, to the network entity, a response to the request for revoking the sensing service.

[0068] According to an embodiment of the present disclosure, a method performed by a network exposure function (NEF) for supporting a sensing service in a wireless communication system is provided. The method may comprise receiving, from an application function (AF), a first request for revoking a sensing service; identifying a sensing service function (SSF) which handled the sensing service; and transmitting, to the identified SSF, a second request for revoking the sensing service.

[0069] These and other aspects of the embodiments herein will be better appreciated and understood when considered in conjunction with the following description and the accompanying drawings. It should be understood, however, that the following descriptions, while indicating at least one embodiment and numerous specific details thereof, are given by way of illustration and not of limitation. Many changes and modifications may be made within the scope of the embodiments herein without departing from the scope thereof, and the embodiments herein include all such modifications.

[0070] The embodiments disclosed herein are illustrated in the accompanying drawings, throughout which like reference letters indicate corresponding parts in the various figures. The embodiments herein will be better understood from the following description with reference to the drawings, in which:

[0071] FIG. 1 illustrates a procedure of revocation to support sensing service by an AF entity in a wireless communication system, according to embodiments as disclosed herein.

[0072] FIG. 2 illustrates a procedure of revocation to support sensing service by a network entity (e.g., SPF entity or the like), according to embodiments as disclosed herein.

[0073] FIG. 3 is a block diagram of a network entity, according to embodiments as disclosed herein.

[0074] FIG. 4 is a block diagram of a NEF entity, according to embodiments as disclosed herein.

[0075] FIG. 5 is a flow chart illustrating a method, implemented by the network entity, for revoking authorization of a sensing service request associated with an application function in the wireless communication system, according to embodiments as disclosed herein.

[0076] FIG. 6 is a flow chart illustrating a method, implemented by the NEF entity, for revoking authorization of a sensing service request associated with an application function in the wireless communication system, according to embodiments as disclosed herein.

[0077] The embodiments herein and the various features and advantageous details thereof are explained more fully with reference to the non-limiting embodiments that are illustrated in the accompanying drawings and detailed in the following description. Descriptions of well-known components and processing techniques are omitted so as to not unnecessarily obscure the embodiments herein. The examples used herein are intended merely to facilitate an understanding of ways in which the embodiments herein can be practiced and to further enable those of skill in the art to practice the embodiments herein. Accordingly, the examples should not be construed as limiting the scope of the embodiments herein.

[0078] For the purposes of interpreting this specification, the definitions (as defined herein) will apply and whenever appropriate the terms used in singular will also include the plural and vice versa. It is to be understood that the terminology used herein is for the purposes of describing particular embodiments only and is not intended to be limiting. The terms "comprising", "having" and "including" are to be construed as open-ended terms unless otherwise noted.

[0079] The words / phrases "exemplary", "example", "illustration", "in an instance", "and the like", "and so on", "etc.", "etcetera", "e.g.," , "i.e.," are merely used herein to mean "serving as an example, instance, or illustration." Any embodiment or implementation of the present subject matter described herein using the words / phrases "exemplary", "example", "illustration", "in an instance", "and the like", "and so on", "etc.", "etcetera", "e.g.," , "i.e.," is not necessarily to be construed as preferred or advantageous over other embodiments.

[0080] Embodiments herein may be described and illustrated in terms of blocks which carry out a described function or functions. These blocks, which may be referred to herein as managers, units, modules, hardware components or the like, are physically implemented by analog and / or digital circuits such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuits and the like, and may optionally be driven by a firmware. The circuits may, for example, be embodied in one or more semiconductor chips, or on substrate supports such as printed circuit boards and the like. The circuits constituting a block may be implemented by dedicated hardware, or by a processor (e.g., one or more programmed microprocessors and associated circuitry), or by a combination of dedicated hardware to perform some functions of the block and a processor to perform other functions of the block. Each block of the embodiments may be physically separated into two or more interacting and discrete blocks without departing from the scope of the disclosure. Likewise, the blocks of the embodiments may be physically combined into more complex blocks without departing from the scope of the disclosure.

[0081] It should be noted that elements in the drawings are illustrated for the purposes of this description and ease of understanding and may not have necessarily been drawn to scale. For example, the flowcharts / sequence diagrams illustrate the method in terms of the steps required for understanding of aspects of the embodiments as disclosed herein. Furthermore, in terms of the construction of the device, one or more components of the device may have been represented in the drawings by conventional symbols, and the drawings may show only those specific details that are pertinent to understanding the present embodiments so as not to obscure the drawings with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein. Furthermore, in terms of the system, one or more components / modules which comprise the system may have been represented in the drawings by conventional symbols, and the drawings may show only those specific details that are pertinent to understanding the present embodiments so as not to obscure the drawings with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein.

[0082] The accompanying drawings are used to help easily understand various technical features and it should be understood that the embodiments presented herein are not limited by the accompanying drawings. As such, the present disclosure should be construed to extend to any modifications, equivalents, and substitutes in addition to those which are particularly set out in the accompanying drawings and the corresponding description. Usage of words such as first, second, third etc., to describe components / elements / steps is for the purposes of this description and should not be construed as sequential ordering / placement / occurrence unless specified otherwise.

[0083] Hereinafter, embodiments of the disclosure will be described in detail with reference to the accompanying drawings.

[0084] In describing the embodiments, descriptions related to technical contents well-known in the art and not associated directly with the disclosure will be omitted. Such an omission of unnecessary descriptions is intended to prevent obscuring of the main idea of the disclosure and more clearly transfer the main idea.

[0085] For the same reason, in the accompanying drawings, some elements may be exaggerated, omitted, or schematically illustrated. Further, the size of each element does not completely reflect the actual size. In the drawings, identical or corresponding elements are provided with identical reference numerals or different reference numerals.

[0086] The advantages and features of the disclosure and ways to achieve them will be apparent by making reference to embodiments as described below in detail in conjunction with the accompanying drawings. However, the disclosure is not limited to the embodiments set forth below, but may be implemented in various different forms. The following embodiments are provided only to completely disclose the disclosure and inform those skilled in the art of the scope of the disclosure, and the disclosure is defined only by the scope of the appended claims. Throughout the specification, the same or like reference numerals designate the same or like elements. Furthermore, in describing the disclosure, a detailed description of known functions or constitution incorporated herein will be omitted in the case that it is determined that the description may make the subject matter of the disclosure unnecessarily unclear. The terms which will be described below are terms defined in consideration of the functions in the disclosure, and may be different according to users, intentions of the operators, or customs. Therefore, the definitions of the terms should be made based on the contents throughout the specification.

[0087] Herein, it will be understood that each block of the flowchart illustrations, and combinations of blocks in the flowchart illustrations, may be performed based on computer program instructions. These computer program instructions may be loaded individually or collectively onto at least one processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which perform through any one of, or in any combination of, the at least one processor of the computer or other programmable data processing apparatus, create means for performing the functions specified in the flowchart block(s). These computer program instructions may also be stored in a non-transitory computer usable or computer-readable memory that may direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer usable or computer-readable memory produce an article of manufacture including instruction means that perform the function specified in the flowchart block(s). The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable data processing apparatus to produce a computer executed process such that the instructions that perform on the computer or other programmable data processing apparatus provide steps for executing the functions specified in the flowchart block(s).

[0088] Further, each block may represent a module, segment, or portion of code, which includes one or more executable instructions for executing the specified logical function(s). It should also be noted that in some alternative implementations, the functions noted in the blocks may occur out of the order. For example, two blocks (or functions) shown in succession may in fact be performed substantially concurrently or the blocks may sometimes be performed in the reverse order, depending upon the functionality involved.

[0089] As used in embodiments of the disclosure, a "~unit / module" may refer to a software element or a hardware element, such as a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC), which performs a predetermined function. However, the term including the word "~unit / module" does not always have a meaning limited to software or hardware. The "~unit / module" may be constructed either to be stored in an addressable storage medium or to execute one or more processors. Therefore, the "~unit / module" includes, for example, software elements, object-oriented software elements, components such as class elements and task elements, processes, functions, properties, procedures, sub-routines, segments of a program code, drivers, firmware, micro-codes, circuits, data, database, data structures, tables, arrays, and parameters. The components and functions provided by the "~unit / module" may be either combined into a smaller number of components and a "~unit / module," or divided into additional components and a "~unit / module." Moreover, the components and "~units / module" may be implemented to reproduce one or more central processing units (CPUs) within a device or a security multimedia card. Further, in the embodiments, the "쪟unit / module" may include one or more processors.

[0090] The entirety of the one or more computer programs may be stored in a single memory device, or the one or more computer programs may be divided with different portions stored

[0091] Furthermore, the terms "first ~", "second ~", etc., as described in the present disclosure with respect to various elements (e.g., information, objects, operation, sequences, or the like), should not limit those elements. These terms may only be intended to distinguish one element from another, an in different multiple memory devices.

[0092] Any of the functions or operations described herein can be processed by one processor or a combination of processors. The one processor or the combination of processors is circuitry performing processing and includes circuitry like an application processor (AP, e.g. a CPU), a communication processor (CP, e.g., a modem), a graphics processing unit (GPU), a neural processing unit (NPU) (e.g., an artificial intelligence (AI) chip), a Wi-Fi chip, a Bluetooth® chip, a global positioning system (GPS) chip, a near field communication (NFC) chip, connectivity chips, a sensor controller, a touch controller, a finger-print sensor controller, a display driver integrated circuit (IC), an audio CODEC chip, a universal serial bus (USB) controller, a camera controller, an image processing IC, microprocessors, microcontrollers, digital signal processors, FPGA, ASIC, a microprocessor unit (MPU), a system on chip (SoC), an IC, or the like. The one processor or the combination of processors executes instructions that can be stored in a memory, such as the operating system, in order to control the overall operation of the device. Also, the one processor or the combination of processors is also capable of executing other processes and programs resident in the memory, such as processes for the disclosure.

[0093] It will be appreciated that various embodiments of the disclosure according to the claims and description in the specification can be realized in the form of hardware, software or a combination of hardware and software.

[0094] Any such software may be stored in non-transitory computer readable storage media. The non-transitory computer readable storage media store one or more computer programs (software modules), the one or more computer programs include computer-executable instructions that, when executed by one or more processors of an electronic device individually or collectively, cause the electronic device to perform a method of the disclosure. Additionally, or alternatively, such software may be a computer program [product] comprising instructions which, when executed by one or more processors of an electronic device individually or collectively, cause the electronic device to perform a method of the disclosure.

[0095] Any such software may be stored in the form of volatile or non-volatile storage such as, for example, a storage device like read only memory (ROM), whether erasable or rewritable or not, or in the form of memory such as, for example, random access memory (RAM), memory chips, device or integrated circuits or on an optically or magnetically readable medium such as, for example, a compact disk (CD), digital versatile disc (DVD), magnetic disk or magnetic tape or the like. It will be appreciated that the storage devices and storage media are various embodiments of non-transitory machine-readable storage that are suitable for storing a computer program or computer programs comprising instructions that, when executed, implement various embodiments of the disclosure. Accordingly, various embodiments of the present disclosure may provide a program comprising code for implementing apparatus or a method as claimed in any one of the claims of this specification and a non-transitory machine-readable storage storing such a program.

[0096] Hereinafter, the determination of priority between A and B in the present disclosure may refer to various actions such as selecting the one having a higher priority based on a predefined priority rule and performing an operation corresponding thereto, or omitting or dropping an operation corresponding to the one having a lower priority.

[0097] Hereinafter, "A or B" as described in the present disclosure may be understood as "A and / or B," which may include A, or B, or both A and B. In addition, "at least one of A, B, and C" as described in the present disclosure may be understood to include A, or B, or C, or any combination of A, B, and C.

[0098] In addition, "at least one of A, B, or C" as described in the present disclosure may be understood to include A, or B, or C, or any combination of A, B, and C. Furthermore, "A / B" as described in the present disclosure may be understood as "A and / or B," which may include A, or B, or both A and B.

[0099] Furthermore, "A, B" as described in the present disclosure may be understood as "A and / or B," which may include A, or B, or both A and B. Furthermore, "A and B" as described in the present disclosure may be understood as "A and / or B," which may include A, or B, or both A and B.

[0100] Furthermore, "if condition A and condition B are satisfied," as described in the present disclosure, may not be limited to a case where both condition A and condition B are satisfied, but may be understood to include a case where either condition A or condition B is individually satisfied, both condition A and condition B are satisfied, or one or more additional conditions are satisfied in combination.

[0101] Furthermore, throughout this disclosure, ordinal terms such as "first," "second," "third," etc., (and similar qualifiers) are used merely to distinguish between different instances, occurrences, configurations, messages, stages, elements or aspects of elements, operations, or information as described herein. Unless the context clearly dictates otherwise, the use of such ordinal terms does not itself require that the elements, operations, or information distinguished by these terms be structurally different, numerically distinct, or substantively dissimilar. For example, a "first signal" and a "second signal" may refer to instead may not be intended to indicate a specific order. For example, a first element could be termed a second element, and, similarly, a second element could be termed a first element.

[0102] Furthermore, even if "first ~" and "second ~" are described in the present disclosure, it may be understood that element(s) referred to by "first ~" and "second ~" may be the same or different. For example, in case of element(s) being information, first information and second information may both be the same information, and, in some cases, are separate and different information.

[0103] In addition, the terms "if ~" and "in case that ~" as used in the disclosure or claims may be interpreted to include the meanings of "when (or upon) ~," "in response to ~," "based on ~," or "according to ~," and may be used interchangeably with these expressions. In addition, expressions other than those exemplified herein may also be used, as long as they have substantially the same meaning and do not impair the technical features of the present disclosure. If a method step (e.g., transmit a signal) is performed according to the disclosure of the application in connection with one of the above terms (such as "in case that ~" or the like), it may be interpreted to include the meanings (disclosure) of a prior determination that a feature has a specific state "~" (e.g., a bit length is above X), and then perform the method step in response to said determination.

[0104] In addition, the term "not perform" as used in the present disclosure or claims may, in context, be understood to mean that the corresponding step is omitted or skipped. Such a term may be replaced with other terms having the same or substantially equivalent meaning.

[0105] In addition, "transmitting a message including A and B" as described in the present disclosure, may be understood as encompassing both (i) transmitting A and B in a single message, and (ii) transmitting A and B separately via multiple messages (e.g., transmitting a first message including A and a second message including B). This interpretation may also apply to messages that include two or more items (e.g., A, B, C), transmitted either together or separately.

[0106] In addition, "transmitting a message including A and transmitting a message including B" may also be interpreted as transmitting a message including A and B in a single message.

[0107] In the specific embodiments of the present disclosure described below, terms or components included in the disclosure may be expressed in singular or plural form depending on the specific embodiments presented. However, such singular or plural expressions are selected appropriately for convenience of description, and the present disclosure is not limited to a singular or plural number of components. A component expressed in the plural form may be implemented as a single component, and a component expressed in the singular form may be implemented as multiple components.

[0108] The drawings or flowcharts described below illustrate example methods that may be implemented according to the principles of the present disclosure, and various modifications may be made to the methods illustrated in the flowcharts of the present disclosure. For example, although illustrated as a series of steps, various steps in each drawing or flowchart may overlap, occur in parallel, occur in a different order, or be repeated. In other examples, any step may be omitted or replaced with another step.

[0109] The process of the flowchart may be performed by a device. One or more of the steps of the flowchart can be implemented by one or more processors / computer programs executing instructions to perform the noted functions.

[0110] The methods and apparatuses proposed in the embodiments of the present disclosure may be disclosed in connection with drawings disclosing flowcharts to illustrate example methods that may be implemented according to the principles of the present disclosure. Such flowcharts may contain different branches and / or sub-branches. It is understood that the principles of the present disclosure do not only contain the combination of all branches / sub-branches disclosed in the embodiment, but the present disclosure also contains at least one isolated branch / isolated sub-branch, in particular to a single branch / single sub-branch.

[0111] The methods and apparatuses proposed in the embodiments of the present disclosure are not limited to each embodiment individually, but may also be applied in combination of all or some of the embodiments proposed in the disclosure. Therefore, the embodiments of the present disclosure may be modified and applied without significantly departing from the scope of the present disclosure, as would be understood by those skilled in the art.

[0112] In this case, even if certain wordings are described differently across embodiments, they may be used interchangeably or in substitution or in combination if their underlying concepts are equivalent. For example, for the same or equivalent concept, even if one embodiment uses the expression "A" and another embodiment uses the expression "B", such expressions may be understood interchangeably, in substitution, or in combination.

[0113] The terms used in the following description to refer to access nodes, network entities, messages, interfaces between network entities, various types of identification information, and the like, are provided merely for the convenience of explanation by way of example. Therefore, the present disclosure is not limited to the terms described below, and other terms having equivalent technical meanings may also be used. Such terms may also be interchangeable with terms defined in any 3rd generation partnership project (3GPP) technical specifications (TS) or similar technical specifications, e.g., from ETSI, where appropriate.

[0114] Hereinafter, a base station (BS) is an entity that allocates resources to terminals, and may be at least one of a gNode B, an eNode B, a Node B, a wireless access unit, a BS controller, or a node on a network. Furthermore, the base station of the present disclosure may include a split architecture comprising a central unit (CU) and a distributed unit (DU). In this structure, the CU is configured to process the higher layers of the control and user planes, while the DU is configured to process lower-layer radio resource functions. The embodiments of the present disclosure may be equally applicable to 5G base station architectures in which such CU and DU functional splits are implemented.

[0115] A terminal may include a UE, a mobile station (MS), a cellular phone, a smartphone, a computer, a tablet, a wearable device, an Internet of Things (IoT) device, or any other device / system capable of performing communication functions.

[0116] In the disclosure, a downlink (DL) refers to a radio link through which a BS transmits a signal to a terminal, and an uplink (UL) refers to a radio link through which a terminal transmits a signal to a BS.

[0117] Furthermore, hereinafter, 5th generation (5G) mobile communication technologies (e.g., 5G new radio (NR)), 6th generation (6G) mobile communication technologies may be described by way of example, but the embodiments of the present disclosure may also be applied to other communication systems having similar technical backgrounds or channel types. For example, newly evolved mobile communication systems developed after 5G and 6G may be included. Furthermore, based on determinations by those skilled in the art, the embodiments of the present disclosure may also be applied to other communication systems (e.g., Wi-Fi systems) through some modifications without significantly departing from the scope of the present disclosure

[0118] Hereinafter, the expression that information is configured by the BS, as used in the present disclosure or claims, may, in context, be understood to mean that the terminal receives the corresponding information from the BS via a physical layer signaling or a higher layer signaling. Such an expression may be replaced with other terms having the same or substantially equivalent meaning.

[0119] Hereinafter, the operational principle of the present disclosure will be described in detail with reference to the accompanying drawings.

[0120] The embodiments herein achieve a method and an apparatus for revoking an authorization of application function of a sensing service request in the wireless communication system. The present invention relates generally to field of integrated sensing and communication in 3GPP, and more particularly, to a system and method of revoking the authorization of application function and the specific sensing service request for providing sensing service in the wireless communication system.

[0121] Referring now to the drawings, and more particularly to FIGS. 1 through 6, where similar reference characters denote corresponding features consistently throughout the figures, there are shown at least one embodiment.

[0122] This invention proposes solution for revocation of application function and specific sensing service request to support sensing service. It has been already assumed that a SSF entity (100) and a SPF entity (400) network function newly introduced in a fifth generation core (5GC) has been successfully authorized whether a particular application function is authorized to trigger a particular sensing service request.

[0123] The definition and functionality about the SSF entity (100) and the SPF entity (400) are explained below:

[0124] The Sensing Service Function (SSF) entity (100): This invention proposes a new network function such as SSF entity (100) to be introduced to the 5GC. The SSF entity (100) can receive the sensing service request from a NEF entity (200) or directly can receive from an AF entity (300). The SSF entity (100) can authorize the AF entity (300) by retrieving the AF authorization data present in sensing profile function before accepting the request. If sensing service request can be fulfilled and authorized then the SSF entity (100) accepts the request and invoke sensing function and sensing entities for further processing like configuring parameters to sensing entities. The SSF entity (100) will be also responsible for collecting sensing data and if any contextual information from sensing entities and calculate the sensing results. The sensing results later will be shared with the AF entity (300).

[0125] The Sensing Profile Function (SPF) entity (400): This invention proposes a new network function such as SPF entity (400) to be introduced to the 5GC. The SPF entity (400) will store the AF authorization data which will be used by the SSF entity (100) to authorize the AF entity (300) before accepting any sensing service request.

[0126] In terms of revocation when the AF entity (400) no longer needs the sensing service from the 5GC can provide the request to terminate or revoke the operation or when sensing operation is finished and there is no more active sensing task is pending, the SSF entity (100) can terminate or revoke the operation and update to the AF entity (300).

[0127] In an embodiment, the AF entity (300) when no longer needed sensing service can trigger the NEF entity (200) by invoking Nnef_SS_Revoke or Nnef_SS_Unsubscribe to terminate or revoke the sensing service operation.

[0128] NEF sensing service:

[0129] The following table 1 illustrates the NEF sensing Services provided by the NEF entity.

[0130] Service NameService OperationsOperationSemanticsExample Consumer(s)Nnef_SSRevokeRequest / ResponseAFNotifySubscribe / NotifyAF

[0131] Nnef_SS_Revoke service operation:

[0132] - Service operation name:Nnef_SS_Revoke

[0133] - Description:The consumer requests to revoke sensing service operation.

[0134] - Input, Required:AF ID, AF Transaction ID.

[0135] - Input, Optional:None.

[0136] - Output, Required:Result indication, Failure cause in case of Failure.

[0137] - Output, Optional:None.

[0138] Alternatively, the AF entity (300) can invoke Nnef_SS_Unsubscribe service operation to revoke the sensing operation. These Nnef_SS_Revoke or Nnef_SS_Unsubscribe are just an example of proposed service operation.

[0139] Nnef_SS_Revoke service operation:

[0140] - Service operation name:Nnef_SS_Unsubscribe

[0141] - Description:The consumer requests to revoke sensing service operation.

[0142] - Input, Required:AF ID, AF Transaction ID.

[0143] - Input, Optional:None.

[0144] - Output, Required:Result indication, Failure cause in case of Failure.

[0145] - Output, Optional:None.Nnef_SS_Notify service operation

[0146] - Service operation name:Nnef_SS_Notify

[0147] - Description:The consumer receives notification of the status or results of the requested service operation. If the consumer invokes the Nnef_SS_Invoke service operation, the consumer implicitly subscribes to the results of the requested service operation and when Nnef_SS_Invoke service operation is used, the implicit subscription is deleted.

[0148] - Input, Required:AF Transaction ID, Sensing result.

[0149] - Input, Optional:None.

[0150] - Output, Required:Result indication.

[0151] - Output, Optional:None.

[0152] In an embodiment, the NEF entity (200) invokes the SSF entity (100) after receiving request from the AF entity (300) by invoking Nssf_SS_Revoke or Nssf_SS_Unsubscribe to terminate or revoke the sensing service operation.

[0153] SSF sensing service: The following table 2 illustrates the SSF sensing services provided by the SSF.

[0154] Service NameService OperationsOperationSemanticsExample Consumer(s)RevokeRequest / ResponseNEF, AFNssf_SSNotifySubscribe / NotifyNEF, AF

[0155] Nssf_SS_Revoke service operation:

[0156] - Service operation name:Nssf_SS_Revoke

[0157] - Description:The consumer requests to revoke sensing service operation.

[0158] - Input, Required:AF ID, AF Transaction ID.

[0159] - Input, Optional:None.

[0160] - Output, Required:Result indication, Failure cause in case of Failure.

[0161] - Output, Optional:None.

[0162] Alternatively, the NEF entity (200) or the AF entity (300) can invoke Nssf_SS_Unsubscribe service operation to revoke the sensing operation. These Nssf_SS_Revoke or Nnef_SS_Unsubscribe are just an example of proposed service operation.

[0163] Nnef_SS_Unsubscribe service operation:

[0164] - Service operation name:Nssf_SS_Unsubscribe

[0165] - Description:The consumer requests to revoke sensing service operation.

[0166] - Input, Required:AF ID, AF Transaction ID.

[0167] - Input, Optional:None.

[0168] - Output, Required:Result indication, Failure cause in case of Failure.

[0169] - Output, Optional:None.

[0170] Nssf_SS_Notify service operation:

[0171] - Service operation name:Nssf_SS_Notify

[0172] - Description:The consumer receives notification of the status or results of the requested service operation. If the consumer invokes the Nssf_SS_Invoke service operation, the consumer implicitly subscribes to the results of the requested service operation and when Nssf_SS_revoke service operation is used, the implicit subscription is deleted.

[0173] - Input, Required:AF Transaction ID, Sensing result.

[0174] - Input, Optional:None.

[0175] - Output, Required:Result indication.

[0176] - Output, Optional:None.

[0177] In an embodiment, when there is some update happens to the AF authorization data, the SSF entity (100) will provide the updated AF authorization data in Nspf_SS_Notify to the SSF entity (100). The SSF entity (100) identifies for the need to terminate based on the sensing service based on the updated authorization data received.

[0178] SPF sensing service: The following table 3 illustrates the SPF sensing services provided by the SPF entity.

[0179] Service NameService OperationsOperation SemanticsExample Consumer(s)Nspf_SSNotifySubscribe / NotifySSF

[0180] Nspf_SS_Notify service operation:

[0181] - Service operation name:Nspf_SS_Notify

[0182] - Description:NF service consumer receives the updated the AF authorization from SPF.

[0183] - Inputs, Required:AF ID, AF authorization data.

[0184] - Inputs, Optional:None.

[0185] - Outputs, Required:.Success

[0186] - Outputs, Optional:None.

[0187] The detailed procedure of revocation by the AF entity (300) in a wireless communication system (1000) is described in FIG. 1.

[0188] 101. The AF entity (300) sends the sensing service request to the NEF entity (200) in Nnef_SS_Revoke for revoking the sensing service.

[0189] 102. The NEF entity (200) selects the SSF entity (100) which had handled the sensing service request.

[0190] 103. The NEF entity (200) invokes the SSF entity (100) in Nssf_SS_Revoke and sends the sensing service request to the SSF entity (100) to terminate the sensing service.

[0191] 103a. Alternatively, The AF entity (300) (i.e. Trusted AF) sends the sensing service request to the SSF entity (100) in Nssf_SS_Revoke for revoking the sensing service.

[0192] 104. The SSF entity (100) terminates the sensing service operation.

[0193] 105a. The SSF entity (100) provides Nssf_SS_Revoke response to the NEF entity (200).

[0194] 105b. The SSF entity (100) provides a response to the AF entity (300) in Nssf_SS_Revoke to the AF entity (300) if it has received the request from the AF entity (300) directly in step 103a.

[0195] 106. The NEF entity (200) forwards the response in Nnef_SS_Revoke to the AF entity (300).

[0196] The wireless communication system (1000) can be, for example, but not limited to a 4G system, 5G system, a 6G system, a 6G beyond system, or the like.

[0197] The detailed procedure of revocation by the network (e.g., SPF entity (400)) is described in FIG. 2.

[0198] 201. The SSF entity (100) receives the updated authorization data from the SPF entity (400).

[0199] 202. The SSF entity (100) decides to terminate the sensing service operation either after identifying that the ongoing sensing service is completed or identifies for the need to terminate the sensing service based on the updated authorization data received in step 1.

[0200] 203. The SSF entity (100) provides Nssf_SS_Notify to the NEF entity (200) indicating the termination of sensing service.

[0201] 203a. The SSF entity (100) provides a response to the AF entity (300) in Nssf_SS_Notify to the AF entity (300) if it has received the request from the AF entity (100) directly when the sensing service was invoked.

[0202] 204. The NEF entity (200) forwards the response in Nnef_SS_Notify to the AF entity (300).

[0203] FIG. 3 is a block diagram illustrating the network entity (100a), according to embodiments as disclosed herein. In an embodiment, the network entity (100a) can be, for example, but not limited to the SSF entity (100) and a SF entity. In an embodiment, the network entity (100a) includes a processor (110), a communicator (120), a memory (130), and a sensing service request authorization revoking controller (140). The processor (110) is operated with the communicator (120), the memory (130) and the sensing service request authorization revoking controller (140). Further, the sensing service request authorization revoking controller (140) is physically implemented by analog or digital circuits such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuits, or the like, and may optionally be driven by firmware.

[0204] The sensing service request authorization revoking controller (140) detects at least one event. The at least one event includes at least one of: the network entity (100a) receiving a sensing service request to terminate a sensing service from at least one of: the NEF entity (200) and the AF entity (200); the network entity (100a) deciding to terminate the sensing service operation after identifying that the ongoing sensing service is completed, and the network entity (100a) identifying for a need to terminate the sensing service based on an updated authorization data received from the SPF entity (400). Based on the at least one detected event, the sensing service request authorization revoking controller (140) terminates or revokes the sensing service operation.

[0205] The use cases related to sensing service examined in the report cover a wide range of applications, including:

[0206] - Object and intruder detection for smart home, on a highway, for railways, for factory, for predefined secure areas around critical infrastructure.

[0207] - Collision avoidance and trajectory tracking of UAVs, vehicles, AGVs.

[0208] - Automotive maneuvering and navigation.

[0209] - Public safety search and rescue.

[0210] - Rainfall monitoring and flooding.

[0211] - Health and sports monitoring.

[0212] In an embodiment, the sensing service request authorization revoking controller (140) sends the message comprising termination details of the sensing service operation to at least one of: the NEF entity (200) and the AF entity (300) based on the at least one detected event, wherein the message is the revoke response.

[0213] In another embodiment, based on the at least one detected event, the sensing service request authorization revoking controller (140) sends the notification message comprising termination details of the sensing service operation to at least one of: the NEF entity (200) and the AF entity (300).

[0214] Further, the processor (110) is configured to execute instructions stored in the memory (130) and to perform various processes. The communicator (120) is configured for communicating internally between internal hardware components and with external devices via one or more networks. The memory (130) also stores instructions to be executed by the processor (110). The memory (130) may include non-volatile storage elements. Examples of such non-volatile storage elements may include magnetic hard discs, optical discs, floppy discs, flash memories, or forms of electrically programmable memories (EPROM) or electrically erasable and programmable (EEPROM) memories. In addition, the memory (130) may, in some examples, be considered a non-transitory storage medium. The term "non-transitory" may indicate that the storage medium is not embodied in a carrier wave or a propagated signal. However, the term "non-transitory" should not be interpreted that the memory (130) is non-movable. In certain examples, a non-transitory storage medium may store data that can, over time, change (e.g., in Random Access Memory (RAM) or cache).

[0215] At least one of the plurality of modules may be implemented through the AI model. A function associated with AI may be performed through the non-volatile memory, the volatile memory, and the processor (110). The processor (110) may include one or a plurality of processors. At this time, one or a plurality of processors may be a general purpose processor, such as a central processing unit (CPU), an application processor (AP), or the like, a graphics-only processing unit such as a graphics processing unit (GPU), a visual processing unit (VPU), and / or an AI-dedicated processor such as a neural processing unit (NPU).

[0216] Although the FIG. 3 shows various hardware components of the network entity (100a) but it is to be understood that other embodiments are not limited thereon. In other embodiments, the network entity (100a) may include less or more number of components. Further, the labels or names of the components are used only for illustrative purpose and does not limit the scope of the invention. One or more components can be combined together to perform same or substantially similar function in the network entity (100a).

[0217] FIG. 4 is a block diagram illustrating the NEF entity (200), according to embodiments as disclosed herein. In an embodiment, the NEF entity (200) includes a processor (210), a communicator (220), a memory (230), and a sensing service request authorization revoking controller (240). The processor (210) is operated with the communicator (220), the memory (230) and the sensing service request authorization revoking controller (240). Further, the sensing service request authorization revoking controller (140) is physically implemented by analog or digital circuits such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuits, or the like, and may optionally be driven by firmware.

[0218] The sensing service request authorization revoking controller (240) receives the sensing service request for revoking the sensing service from the AF entity (300). Further, the sensing service request authorization revoking controller is configured to select the at least one network entity (100a) that handles the sensing service request. Further, the sensing service request authorization revoking controller (240) sends the sensing service request to terminate the sensing service to the network entity (100a). Based on the sensing service request, the sensing service request authorization revoking controller receives about terminating or revoking the sensing service operation from the network entity (100a).

[0219] Further, the processor (210) is configured to execute instructions stored in the memory (230) and to perform various processes. The communicator (220) is configured for communicating internally between internal hardware components and with external devices via one or more networks. The memory (230) also stores instructions to be executed by the processor (210). The memory (230) may include non-volatile storage elements. Examples of such non-volatile storage elements may include magnetic hard discs, optical discs, floppy discs, flash memories, or forms of electrically programmable memories (EPROM) or electrically erasable and programmable (EEPROM) memories. In addition, the memory (230) may, in some examples, be considered a non-transitory storage medium. The term "non-transitory" may indicate that the storage medium is not embodied in a carrier wave or a propagated signal. However, the term "non-transitory" should not be interpreted that the memory (230) is non-movable. In certain examples, a non-transitory storage medium may store data that can, over time, change (e.g., in Random Access Memory (RAM) or cache).

[0220] At least one of the plurality of modules may be implemented through the AI model. A function associated with AI may be performed through the non-volatile memory, the volatile memory, and the processor (210). The processor (210) may include one or a plurality of processors. At this time, one or a plurality of processors may be a general purpose processor, such as a central processing unit (CPU), an application processor (AP), or the like, a graphics-only processing unit such as a graphics processing unit (GPU), a visual processing unit (VPU), and / or an AI-dedicated processor such as a neural processing unit (NPU).

[0221] Although the FIG. 4 shows various hardware components of the NEF entity (200) but it is to be understood that other embodiments are not limited thereon. In other embodiments, the NEF entity (200) may include less or more number of components. Further, the labels or names of the components are used only for illustrative purpose and does not limit the scope of the invention. One or more components can be combined together to perform same or substantially similar function in the NEF entity (200).

[0222] FIG. 5 is a flow chart (S500) illustrating a method, implemented by the network entity (100a), for revoking authorization of the sensing service request associated with the application function in the wireless communication system (1000), according to embodiments as disclosed herein. The operations (S502-S508) handled by the sensing service request authorization revoking controller (140).

[0223] At S502, the method includes detecting the at least one event. The at least one event includes at least one of: the network entity (100a) receiving the sensing service request to terminate the sensing service from at least one of: the NEF entity (200) and the AF entity (300); the network entity (100a) deciding to terminate the sensing service operation after identifying that the ongoing sensing service is completed, and the network entity (100a) identifying for the need to terminate the sensing service based on an updated authorization data received from the SPF entity (400). At S504, the method includes terminating or revoking the sensing service operation.

[0224] In an embodiment, at S506, the method includes sending, the message comprising termination details of the sensing service operation to at least one of: the NEF entity (200) and the AF entity (300) based on the at least one detected event, wherein the message is the revoke response. In another embodiment, At S508, the method includes sending the notification message comprising termination details of the sensing service operation to at least one of: the NEF entity (200) and the AF entity (300) based on the at least one detected event.

[0225] FIG. 6 is a flow chart (S600) illustrating a method, implemented by the NEF entity (200), for revoking authorization of the sensing service request associated with the application function (300) in the wireless communication system (1000), according to embodiments as disclosed herein. The operations (S602-S608) handled by the sensing service request authorization revoking controller (240).

[0226] At S602, the method includes receiving the sensing service request for revoking the sensing service from the AF entity (300). At S604, the method includes selecting the at least one network entity (100a) that handles the sensing service request. At S606, the method includes sending the sensing service request to terminate the sensing service to the network entity (100a). At S608, the method includes receiving about terminating or revoking the sensing service operation from the network entity (100a) based on the sensing service request.

[0227] The various actions, acts, blocks, steps, or the like in the flow charts (S500-S600) may be performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some of the actions, acts, blocks, steps, or the like may be omitted, added, modified, skipped, or the like without departing from the scope of the invention.

[0228] The embodiments disclosed herein can be implemented through at least one software program running on at least one hardware device and performing network management functions to control the elements. The elements shown in figures can be at least one of a hardware device, or a combination of hardware device and software module.

[0229] The foregoing description of the specific embodiments will so fully reveal the general nature of the embodiments herein that others can, by applying current knowledge, readily modify and / or adapt for various applications such specific embodiments without departing from the generic concept, and, therefore, such adaptations and modifications should and are intended to be comprehended within the meaning and range of equivalents of the disclosed embodiments. It is to be understood that the phraseology or terminology employed herein is for the purpose of description and not of limitation. Therefore, while the embodiments herein have been described in terms of at least one embodiment, those skilled in the art will recognize that the embodiments herein can be practiced with modification within the spirit and scope of the embodiments as described herein.

Claims

1.A method performed by a sensing service function (SSF) for supporting a sensing service in a wireless communication system, the method comprising:receiving, from a network entity, a request for revoking a sensing service handled by the SSF;terminating an operation for the sensing service based on receiving the request for revoking the sensing service; andtransmitting, to the network entity, a response to the request for revoking the sensing service.2.The method of claim 1, wherein the network entity is an application function (AF) or a network exposure function (NEF).3.The method of claim 2, wherein the revoking of the sensing service is determined by the AF based on the AF needing the sensing service no longer.4.The method of claim 2, further comprising:receiving, from a sensing profile function (SPF), an updated authorization data for the AF; anddetermining to terminate the operation for the sensing service based on the received updated authorization data, or based on identifying the sensing service is completed.5.The method of claim 4, further comprising:transmitting, to the network entity, a notification indicating a termination of the sensing service.6.A sensing service function (SSF) for supporting a sensing service in a wireless communication system, the SSF comprising:memory storing instruction; andat least one processor operably coupled to the memory, wherein the instructions are executable by the at least one processor to cause the SSF to perform operations, the operations comprising:receiving, from a network entity, a request for revoking a sensing service handled by the SSF;terminating an operation for the sensing service based on receiving the request for revoking the sensing service; andtransmitting, to the network entity, a response to the request for revoking the sensing service.7.The SSF of claim 6, wherein the network entity is an application function (AF) or a network exposure function (NEF).8.The SSF of claim 7, wherein the revoking of the sensing service is determined by the AF based on the AF needing the sensing service no longer.9.The SSF of claim 7, wherein the operations further comprise:receiving, from a sensing profile function (SPF), an updated authorization data for the AF; anddetermining to terminate the operation for the sensing service based on the received updated authorization data, or based on identifying the sensing service is completed.10.The SSF of claim 9, wherein the operations further comprise:transmitting, to the network entity, a notification indicating a termination of the sensing service.11.A method performed by a network exposure function (NEF) for supporting a sensing service in a wireless communication system, the method comprising:receiving, from an application function (AF), a first request for revoking a sensing service;identifying a sensing service function (SSF) which handled the sensing service; andtransmitting, to the identified SSF, a second request for revoking the sensing service.12.The method of claim 11, wherein the first request for revoking the sensing service is received based on the AF needing the sensing service no longer.13.The method of claim 11, further comprising:receiving, from the identified SSF, a response for the second request for revoking the sensing service; andforwarding the response to the AF.14.The method of claim 11, further comprising:receiving, from the SSF, notification indicating a termination of the sensing service; andforwarding the notification to the AF.15.The method of claim 14, wherein the termination of the sensing service is based on an updated authorization of the AF or based on a completion of the sensing service.