Method and apparatus for authorizing sensing service request of AF in wireless communication system

The method and apparatus in the 5G wireless sensing system authorize sensing service requests through NEF and SSF entities, using AF authorization data to ensure secure and compliant sensing service provisioning.

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

Patent Information

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

AI Technical Summary

Technical Problem

The challenge in 5G wireless sensing systems is the need for secure authorization and revocation mechanisms to protect sensing data from unauthorized access and ensure compliance with regulations and user privacy, particularly in the context of sensing service requests and entity authorization.

Method used

A method and apparatus for authorizing sensing service requests in a wireless communication system, utilizing a network exposure function (NEF) and sensing service function (SSF) to validate application function (AF) requests based on service level agreements and operator policies, with AF authorization data containing properties for efficient authorization.

Benefits of technology

Provides secure and compliant sensing service provisioning by ensuring authorized access and preventing unauthorized use, enhancing data confidentiality and adhering to regulatory requirements.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure KR2026005635_12112026_PF_FP_ABST
    Figure KR2026005635_12112026_PF_FP_ABST
Patent Text Reader

Abstract

The disclosure relates to 5G or 6G communication system for supporting higher data transmission rates and satisfying various service requirements. In an example, a method performed by a network entity handling a sensing service in a communication system is provided. The method may include: receiving, from an AF, a sensing service request for the sensing service; performing an authorization of the sensing service request based on information on sensing authorization including AF authorization data; in case that the authorization is granted, proceeding the sensing service request; and in case that the authorization is not granted, rejecting the sensing service request.
Need to check novelty before this filing date? Find Prior Art

Description

METHOD AND APPARATUS FOR AUTHORIZING SENSING SERVICE REQUEST OF AF IN WIRELESS COMMUNICATION SYSTEM

[0001] The disclosure relates to the field of integrated sensing and communication in a wireless communication system. More particularly, to a system and method for authorizing application function and the specific sensing service request for providing sensing service in a wireless system (or 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 a 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, Automated Guided Vehicles (AGVs).

[0013] ● Automotive maneuvering and navigation.

[0014] ● Public safety search and rescue.

[0015] ● Rainfall monitoring and flooding.

[0016] ● Health and sports monitoring.

[0017] 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] Problem Definition:In Rel 20, 3GPP SA2 WG started studying the sensing service requirement and in technical report (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 a Core Network (CN) 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] NOTE: 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.

[0044] This Key Issue aims to study:

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

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

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

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

[0049] 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:

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

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

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

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

[0054] NOTE: This KI needs to be aligned with RAN WGs.

[0055] In the disclosure (proposed method and system), KI#2, solution will be provided which is to authorize the application function and specific sensing service request before providing the sensing service in a fifth generation core (5GC).

[0056] The disclosure relates to a method and apparatus for authorizing application function and the specific sensing service request for providing sensing service in a wireless system.

[0057] Accordingly, an aspect of the disclosure is to provide a method and wireless communication system for authorizing application function of sensing service request in the wireless communication system.

[0058] Another aspect of the disclosure is to provide that a network exposure function (NEF) entity, after receiving a sensing service request from an application function (AF) entity (AF which is outside of an operator's trusted domain), authorizes using a service level agreement and operator policy. According to an example of the disclosure, after successful authorization, the NEF may forward the sensing service request to a sensing function (SF) entity / a sensing service function (SSF) entity. The SF entity / SSF entity authorizes the sensing service request of the AF, based on AF authorization data.

[0059] Other aspect of the disclosure is to provide the AF authorization data which will contain the properties about the AF related to sensing service authorization based on which the SF entity / SSF entity will authorize the sensing service request.

[0060] The technical problems to be achieved in the various examples of the disclosure are not limited to those mentioned above, and other technical problems not mentioned can be considered by a person having ordinary skill in the art from the various examples of the disclosure described below.

[0061] According to an aspect of the disclosure, a method performed by a network entity handling a sensing service in a communication system is provided. The method may include: receiving, from an application function (AF), a sensing service request for the sensing service; performing an authorization of the sensing service request based on information on sensing authorization including AF authorization data; in case that the authorization is granted, proceeding the sensing service request; and in case that the authorization is not granted, rejecting the sensing service request.

[0062] According to another aspect of the disclosure, a method performed by a network exposure function (NEF) in a communication system is provided. The method may include: receiving, from an application function (AF), a sensing service request for a sensing service; performing an authorization of the AF; and transmitting, to a network entity handling the sensing service, the sensing service request for an authorization of the sensing service request by the network entity handling the sensing service, wherein the authorization of the sensing service request may be associated with information on sensing authorization including AF authorization data.

[0063] According to another aspect of the disclosure, a network entity handling a sensing service in a communication system is provided. The network entity handling the sensing service may include: a communicator; a processor coupled to the communicator; and memory coupled to the processor and storing instructions executable by the processor, wherein the instructions may cause the network entity handling the sensing service to: receive, from an application function (AF), a sensing service request for the sensing service, perform an authorization of the sensing service request based on information on sensing authorization including AF authorization data, in case that the authorization is granted, proceed the sensing service request, and in case that the authorization is not granted, reject the sensing service request.

[0064] According to another aspect of the disclosure, a network exposure function (NEF) in a communication system is provided. The NEF may include: a communicator; a processor coupled to the communicator; and memory coupled to the processor and storing instructions executable by the processor, wherein the instructions may cause the NEF to: receive, from an application function (AF), a sensing service request for a sensing service, perform an authorization of the AF, and transmit, to a network entity handling the sensing service, the sensing service request for an authorization of the sensing service request by the network entity handling the sensing service, wherein the authorization of the sensing service request may be associated with information on sensing authorization including AF authorization data.

[0065] Accordingly, the examples herein provide a method for authorizing a sensing service request of an application function (AF) in a wireless communication system. The method includes receiving, by a Sensing Service Function (SSF) entity, a sensing service request for invoking a sensing service from at least one of: an AF entity directly if the AF entity is inside a trusted domain or via the NEF entity if the AF is outside the trusted domain. Further, the method includes sending, by the SSF entity, a request to retrieve an AF authorization data to an SPF entity based on the sensing service request. Further, the method includes receiving, by the SSF entity, a response comprising the AF authorization data from the SPF entity based on the request.

[0066] In an example, the method includes performing, by the SSF entity, an authorization of the AF's sensing service request using the AF authorization data. In an example, the method includes accepting the sensing service request after successful authorization when the sensing service can be served. In another example, the method includes rejecting the sensing service request when the sensing service cannot be served.

[0067] In an example, the method includes sending, by the SSF entity, a result comprising one of: acceptance of the sensing service request and a rejection of the sensing service request to at least one of: the NEF entity and the AF entity.

[0068] In an example, the method includes storing, by the SSF entity, the result associated with the authorization of AF's sensing service request, wherein successful authorization result is stored at the SSF entity so that when the AF triggers a same sensing service request in future, there will be no need to repeating the authorization of AF's sensing service request again.

[0069] In an example, the SSF entity implicitly subscribes to the SPF entity to receive the AF authorization data.

[0070] In an example, the AF authorization data comprises at least one of: an AF identifier (ID), an allowed area, an allowed service operation and an allowed time period, wherein the AF identifier (ID) is used to identify the AF entity, wherein the allowed area indicates an allowed area for the AF to trigger at least one sensing services operation, wherein the allowed service operation indicates an allowed sensing service operation for an indicated AF, wherein the allowed time period indicates the allowed within which AF can trigger a particular sensing service operation.

[0071] In an example, the SSF entity and the SPF entity can act as a single entity, wherein the single entity is a Sensing Function (SF) entity, and wherein the SSF entity and the SPF entity are co-located.

[0072] Accordingly, the examples herein provide a method for authorizing a sensing service request of an AF in a wireless communication system. The method includes obtaining, by a Sensing Profile Function (SPF) entity, an AF authorization data. Further, the method includes receiving, by the SPF entity, a request or notification to provide an AF authorization data to a SSF entity. Further, the method includes sending, by the SPF entity, a response comprising the AF authorization data to the SSF entity based on the request or the notification.

[0073] In an example, obtaining, by the SPF entity, the AF authorization data comprises at least one of: obtaining the AF authorization data as part of a configuration by an Operations, Administration, and Maintenance (OAM) entity or the AF authorization data configured by the AF entity to the SPF entity.

[0074] Accordingly, the examples herein provide a method for authorizing of an AF for sensing service request in a wireless communication system. The method includes receiving, by a Network Exposure Function (NEF) entity, Authorization of an AF entity for Sensing Service request for invoking a sensing service from the application function (AF) entity when the AF entity is outside of a trusted domain. Further, the method includes performing, by the NEF entity, the authorization of the AF for the sensing service request based on a service level agreement (SLA) among a third party AF and a fifth generation system (5GS) of a mobile network operator, an operator policy and a local configuration.

[0075] In an example, further, the method includes sending, by the NEF entity, the sensing service request for invoking the sensing service to a SSF entity. Further, the method includes receiving, by the NEF entity, a result comprising one of: acceptance of the sensing service request and a rejection of the sensing service request from the SSF entity. Further, the method includes sending, by the NEF entity, the result comprising one of: acceptance of the sensing service request and the rejection of the sensing service request to the AF entity.

[0076] Accordingly, the examples herein provide a SSF entity including a sensing service request authorizing controller coupled with a processor and a memory. The sensing service request authorizing controller is configured to receive a sensing service request for invoking a sensing service from at least one of: an AF entity directly if the AF is inside trusted domain or via an NEF entity if AF is outside the trusted domain. Further, the sensing service request authorizing controller is configured to send a request to retrieve an AF authorization data to an SPF entity based on the sensing service request. Further, the sensing service request authorizing controller is configured to receive a response comprising the AF authorization data from the SPF entity based on the request.

[0077] Accordingly, the examples herein provide a SPF entity including a sensing service request authorizing controller coupled with a processor and a memory. The sensing service request authorizing controller is configured to obtain an AF authorization data. Further, the sensing service request authorizing controller is configured to receive a request or notification to provide an AF authorization data to a SSF entity. Further, the sensing service request authorizing controller is configured to send response comprising the AF authorization data to the SSF entity based on the request.

[0078] Accordingly, the examples herein provide a NEF entity including a sensing service request authorizing controller coupled with a processor and a memory. The sensing service request authorizing controller is configured to receive Authorization of the AF for Sensing Service request for invoking a sensing service from an AF entity when the AF entity is outside of a trusted domain. Further, the sensing service request authorizing controller is configured to perform the Authorization of the AF for Sensing Service request based on an SLA among a third party AF and a 5GS of a mobile network operator, an operator policy and a local configuration.

[0079] These and other aspects of the examples 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 example 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 examples herein without departing from the scope thereof, and the examples herein include all such modifications.

[0080] According to an example of the disclosure, a secure authorization framework for sensing service requests may be provided by utilizing the NEF and the SF / SSF, by enabling reliable sensing service provisioning for application functions in the communication system.

[0081] According to an example of the disclosure, an example of AF authorization data may be introduced which contains properties about the AF related to sensing service authorization, based on which the SF / SSF may efficiently authorize the sensing service request.

[0082] The effects that can be obtained from the disclosure are not limited to the effects mentioned in the various examples, and other effects that are not mentioned can be clearly understood by a person having ordinary skill in the art to which the disclosure belongs from the description below.

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

[0084] FIG. 1 illustrates an example procedure of AF authorization to support sensing service in a wireless communication system, according to examples as disclosed herein.

[0085] FIG. 2 is a block diagram illustrating a SSF entity, according to examples as disclosed herein

[0086] FIG. 3 is a block diagram illustrating a SPF entity, according to examples as disclosed herein.

[0087] FIG. 4 is a block diagram illustrating a NEF entity, according to examples as disclosed herein.

[0088] FIG. 5 is a flow chart illustrating a method, implemented by the SSF entity, for authorizing a sensing service request of the AF in the wireless communication system, according to examples as disclosed herein.

[0089] FIG. 6 is a flow chart illustrating a method, implemented by the SPF entity, for authorizing the sensing service request of the AF in the wireless communication system, according to examples as disclosed herein.

[0090] FIG. 7 is a flow chart illustrating a method, implemented by the NEF entity, for authorizing of an AF for sensing service request in the wireless communication system, according to examples as disclosed herein.

[0091] The examples herein and the various features and advantageous details thereof are explained more fully with reference to the non-limiting examples 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 examples herein. The examples used herein are intended merely to facilitate an understanding of ways in which the examples herein can be practiced and to further enable those of skill in the art to practice the examples herein. Accordingly, the examples should not be construed as limiting the scope of the examples herein.

[0092] 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 examples 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.

[0093] 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 example 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 examples.

[0094] Examples 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 examples 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 examples may be physically combined into more complex blocks without departing from the scope of the disclosure.

[0095] 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 examples 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 examples 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 examples 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.

[0096] The accompanying drawings are used to help easily understand various technical features and it should be understood that the examples presented herein are not limited by the accompanying drawings. As such, the 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.

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

[0098] In describing the examples, 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.

[0099] 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.

[0100] The advantages and features of the disclosure and ways to achieve them will be apparent by making reference to examples as described below in detail in conjunction with the accompanying drawings. However, the disclosure is not limited to the examples set forth below, but may be implemented in various different forms. The following examples 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.

[0101] 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).

[0102] 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.

[0103] As used in examples 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 examples, the "~unit / module" may include one or more processors.

[0104] 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

[0105] Furthermore, the terms "first ~", "second ~", etc., as described in the 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.

[0106] 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.

[0107] It will be appreciated that various examples 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.

[0108] 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.

[0109] 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 examples of non-transitory machine-readable storage that are suitable for storing a computer program or computer programs comprising instructions that, when executed, implement various examples of the disclosure. Accordingly, various examples of the 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.

[0110] Hereinafter, the determination of priority between A and B in the 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.

[0111] Hereinafter, "A or B" as described in the 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 disclosure may be understood to include A, or B, or C, or any combination of A, B, and C.

[0112] In addition, "at least one of A, B, or C" as described in the 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 disclosure may be understood as "A and / or B," which may include A, or B, or both A and B.

[0113] Furthermore, "A, B" as described in the 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 disclosure may be understood as "A and / or B," which may include A, or B, or both A and B.

[0114] Furthermore, "if condition A and condition B are satisfied," as described in the 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.

[0115] 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.

[0116] Furthermore, even if "first ~" and "second ~" are described in the 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.

[0117] 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 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.

[0118] In addition, the term "not perform" as used in the 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.

[0119] In addition, "transmitting a message including A and B" as described in the 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.

[0120] 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.

[0121] In the specific examples of the disclosure described below, terms or components included in the disclosure may be expressed in singular or plural form depending on the specific examples presented. However, such singular or plural expressions are selected appropriately for convenience of description, and the 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.

[0122] The drawings or flowcharts described below illustrate example methods that may be implemented according to the principles of the disclosure, and various modifications may be made to the methods illustrated in the flowcharts of the 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.

[0123] 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.

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

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

[0126] In this case, even if certain wordings are described differently across examples, 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 example uses the expression "A" and another example uses the expression "B", such expressions may be understood interchangeably, in substitution, or in combination.

[0127] 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 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.

[0128] 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 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 examples of the disclosure may be equally applicable to 5G base station architectures in which such CU and DU functional splits are implemented.

[0129] 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.

[0130] 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.

[0131] 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 examples of the 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 examples of the 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 disclosure.

[0132] Hereinafter, the expression that information is configured by the BS, as used in the 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.

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

[0134] The examples herein achieve a method and apparatus for authorizing application function of sensing service request in a wireless communication system. The disclosure relates generally to the field of integrated sensing and communication in 3GPP, and more particularly, to a system and method of authorizing application function and the specific sensing service request for providing sensing service in the wireless system. This disclosure proposes solution for authorization of application function and specific sensing service request before providing sensing service. The use cases examined in the report cover a wide range of applications, including:

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

[0136] ● Collision avoidance and trajectory tracking of UAVs, vehicles, Automated Guided Vehicles (AGVs).

[0137] ● Automotive maneuvering and navigation.

[0138] ● Public safety search and rescue.

[0139] ● Rainfall monitoring and flooding.

[0140] ● Health and sports monitoring.

[0141] In an example, UAV service supplier which needs to provide UAV related service like tracking UAVs in an area, assisting in providing direction to safely reach from one location to another etc., and this kind of requirement can be fulfilled through sensing service. As sensing service consumer (i.e. USS an AF) will get it from 5G wireless communication system. This is just one of the use cases needed by sensing service consumer and there can be many such who need sensing service. But before sensing service consumer gets service from network, there is a need for authorization of consumer and the kind or type of sensing service request authorization. The proposed method addresses both aspect which means authorization of AF for sensing service request and AF's sensing service request before accepting any request.

[0142] Referring now to the drawings, and more particularly to FIG. 1 to FIG. 7, where similar reference characters denote corresponding features consistently throughout the figures, there are shown at least one example.

[0143] Before 5GC accepts the sensing request from an AF entity (300) and does further processing, there is a need for AF authorization to ensure only authorized AF can access a 5GC and trigger sensing request. The authorization of the AF entity (300) to get sensing service from 5GC includes two steps:

[0144] ○ The NEF entity (200) performs sensing AF request authorization based on a service level agreement (SLA) between a 3rdparty AF and a 5GS of a mobile network operator, an operator policy and local configuration as in TS 33.501.

[0145] ○ The SSF entity (100) shall perform authorization of sensing service requested by the AF entity (300), using the AF authorization data retrieved from the SPF entity (400) as described in the below table 1 or local configuration available at the SSF entity (100).

[0146] Table 1:AFAuthorization Data for Sensing ServiceAFAuthorization DataDescriptionAF IDIdentifier used to identify the AF.Allowed areaIndicate the allowed area for the indicated AF to trigger the sensing services operations.Allowed service operationsIndicate the allowed sensing service operation (s) for the indicated AF, e.g. object detection and tracking, environment monitoring, motion monitoringAllowed time periodIndicate the allowed time period within which AF can trigger a particular sensing service operation

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

[0148] Sensing Service Function (SSF) entity (100):This disclosure 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 the 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 the sensing entities and calculate the sensing results. The sensing results later will be shared with the AF entity (300).

[0149] Sensing Profile Function (SPF) entity (400):This disclosure 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.

[0150] In an example, it is proposed that the AF entity (300) sends the sensing service request by invoking Nnef_SS_Invoke or Nnef_SS_Subscribe service operation.

[0151] The following table 2 illustrates the NEF sensing Services.

[0152] Table 2: Sensing Services provided byNEFService NameService OperationsOperationSemanticsExample Consumer(s)Nnef_SSInvokeRequest / ResponseAF

[0153] Nnef_SS_Invoke service operation

[0154] Service operation name:Nnef_SS_Invoke

[0155] Description:The consumer requests to invoke sensing service operation.

[0156] Input, Required:Type of sensing service operation (e.g. object detection and tracking, environment monitoring, motion monitoring, AF ID, target area, sensing duration, sensing KPI

[0157] Input, Optional:None.

[0158] Output, Required:AF Transaction ID, Result indication, Failure cause in case of Failure.

[0159] Output, Optional:None.

[0160] Alternatively, the AF entity (300) can use Nnef_SS_Subscribe service operation to send sensing service request.

[0161] Nnef_SS_Subscribe service operation

[0162] Service operation name:Nnef_SS_Subscribe

[0163] Description:The consumer requests to invoke sensing service operation.

[0164] Input, Required:Type of sensing service operation (e.g. object detection and tracking, environment monitoring, motion monitoring, AF ID, target area, sensing duration, sensing KPI

[0165] Input, Optional:None.

[0166] Output, Required:AF Transaction ID, Result indication, Failure cause in case of Failure.

[0167] Output, Optional:None.

[0168] In an example, it is proposed that the NEF entity (200) discovers the SSF entity (100) and sends the sensing service request by invoking Nssf_SS_Invoke or Nssf_SS_Subscribe service operation.

[0169] In an example, it is proposed that the NEF entity (200) performs authorization of the AF entity (300) before accepting the sensing service request based on the SLA between third party and 5GS of the mobile network operator, the operator policy and local configuration.

[0170] In another example, it is proposed that Trusted AF discovers the SSF entity (100) and then sends the sensing service request by invoking Nssf_SS_Invoke or Nssf_SS_Subscribe service operation.

[0171] SSFsensing service: The following table 3 illustrates the SSF sensing Services.

[0172] Table 3: Sensing Services provided bySSFService NameService OperationsOperationSemanticsExample Consumer(s)Nssf_SSInvokeRequest / ResponseNEF, AF

[0173] Nssf_SS_Invoke service operation

[0174] Service operation name:Nssf_SS_Invoke

[0175] Description:The consumer requests to invoke sensing service operation.

[0176] Input, Required:Type of sensing service operation (e.g. object detection and tracking, environment monitoring, motion monitoring, AF ID, target area, sensing duration, sensing KPI

[0177] Input, Optional:None.

[0178] Output, Required:AF Transaction ID, Result indication, Failure cause in case of Failure.

[0179] Output, Optional:None.

[0180] Alternatively, the NEF entity (200) or Trusted AF can use Nssf_SS_Subscribe service operation to send sensing service request.

[0181] Nssf_SS_Subscribe service operation

[0182] Service operation name:Nssf_SS_Subscribe

[0183] Description:The consumer requests to invoke sensing service operation.

[0184] Input, Required:Type of sensing service operation (e.g. object detection and tracking, environment monitoring, motion monitoring, AF ID, target area, sensing duration, sensing KPI

[0185] Input, Optional:None.

[0186] Output, Required:AF Transaction ID, Result indication, Failure cause in case of Failure.

[0187] Output, Optional:None.

[0188] In an example, it is proposed that the SSF entity (100) before accepting the sensing service request from the NEF entity (200) or trusted AF for further processing, shall authorize whether the AF entity (300) is authorized to trigger the particular sensing service request and hence retrieve the AF authorization data from the SPF entity (400) by invoking Nspf_SS_Get service operation.

[0189] SPF sensing service:

[0190] The following table 4 illustrates the SPF sensing Services.

[0191] Table 4: Sensing services provided by SPFService NameService OperationsOperation SemanticsExample Consumer(s)Nspf_SSGetRequest / ResponseSSF

[0192] Nspf_SS_Get service operation

[0193] Service operation name:Nspf_SS_Get

[0194] Description:NF service consumer gets the AF authorization data stored in SPF.

[0195] Inputs, Required:AF ID.

[0196] Inputs, Optional:None.

[0197] Outputs, Required:AF authorization data.

[0198] Outputs, Optional:None.

[0199] The detailed procedure of authorization is described in FIG. 1.

[0200] FIG. 1 illustrates an example procedure of AF authorization to support sensing service in a wireless communication system, according to examples as disclosed herein.

[0201] 1. The AF entity (300) sends the sensing service request to the NEF entity (200) in Nnef_SS_Invoke for invoking the sensing service.

[0202] 2. The NEF entity (200) performs authorization of the AF entity (300) based on the service level agreement (SLA) between the 3rd party AF and the 5GS of the mobile network operator, the operator policy and local configuration as in TS 33.501. When it is authorized, then the NEF entity (200) performs the SSF entity selection based on local configuration or by querying the network repository function (NRF) entity (200).

[0203] 3. The NEF entity (200) invokes the SSF entity (100) in Nssf_SS_Invoke and sends the Sensing service request to the SSF entity (100) with the inputs received in step 1.

[0204] 3a. The AF (i.e. Trusted AF) entity (300) sends the sensing service request to the SSF entity (100) in Nssf_SS_Invoke for invoking the sensing service.

[0205] 4. The SSF entity (100) discovers and selects SPF entity (400) and then sends the request to the SPF entity (400) in Nspf_SS_Get to retrieve AF authorization data. The SSF entity (100) implicitly subscribes to the SPF entity (400) to receive any updated authorization data.

[0206] 5. The SPF entity (400) provides the AF authorization data to the SSF entity (100).

[0207] 6. The SSF entity (100) performs authorization of Sensing service request using the AF authorization data. After successful authorization and if sensing service can be served, the SSF entity (100) accepts the request. If request cannot be served, then provides reject response. The NEF entity (200) sends the result from the SF for the Sensing Service request to AF. Successful authorization data can be stored in the SSF entity (100) so that in future when same AF entity (300) triggers the similar sensing service request, there will be no need to repeat the authorization of the sensing service request again.

[0208] NOTE: This authorization data can be stored in the SSF entity (100) or the SPF entity (400) or a Unified Data Management (UDM) entity or a Unified Data Repository (UDR) entity or the NEF entity (200) or any other NF but the purpose is to avoid repeating the authorization of same AF.

[0209] 7. The SSF entity (100) provides Nssf_SS_Invoke response to the NEF entity (200).

[0210] 7a. The SSF entity (100) provides response to AF in Nssf_SS_Invoke if it has received the request from AF entity (300) directly in step 3a.

[0211] 8. The NEF entity (200) forwards the response in Nnef_SS_Invoke to AF.

[0212] FIG. 2 is a block diagram illustrating the SSF entity (100), according to examples as disclosed herein. In an example, the SSF entity (100) includes a processor (110), a communicator (120), a memory (130), and a sensing service request authorizing controller (140). The processor (110) is operated with the communicator (120), the memory (130) and the sensing service request authorizing controller (140). Further, the sensing service request authorizing 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.

[0213] In an example, the SSF entity (100) and the SPF entity (400) can act as a single entity, where the single entity is the Sensing Function (SF) entity. The SSF entity (100) and the SPF entity (400) are co-located.

[0214] The sensing service request authorizing controller (140) receives the sensing service request for invoking the sensing service from at least one of: the AF entity (300) directly if the AF entity (300) is inside the trusted domain or via the NEF entity (200) if the AF entity (300) is outside the trusted domain. Further, the sensing service request authorizing controller (140) sends a request to retrieve the AF authorization data to the SPF entity (400) based on the sensing service request. Based on the request, the sensing service request authorizing controller receives the response comprising the AF authorization data from the SPF entity (400). The SSF entity (100) implicitly subscribes to the SPF entity (400) to receive the AF authorization data.

[0215] The sensing service request authorizing controller (140) performs the authorization of the AF's sensing service request using the AF authorization data. In an example, the sensing service request authorizing controller (140) accepts the sensing service request after successful authorization when the sensing service can be served. In an example, the sensing service request authorizing controller (140) rejects the sensing service request when the sensing service cannot be served.

[0216] Further, the sensing service request authorizing controller (140) sends a result comprising one of: acceptance of the sensing service request and a rejection of the sensing service request to at least one of: the NEF entity (200) and the AF entity (300). Further, the sensing service request authorizing controller (140) stores the result associated with the authorization of AF's sensing service request, where successful authorization result is stored at the SSF entity (100) so that when the AF (300) triggers a same sensing service request in future, there will be no need to repeating the authorization of AF's sensing service request again.

[0217] 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).

[0218] 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).

[0219] Although the FIG. 2 illustrates various hardware components of the SSF entity (100) but it is to be understood that other examples are not limited thereon. In other examples, the SSF entity (100) may include less or more number of components. Further, the labels or names of the components are used only for illustrative purpose and do not limit the scope of the disclosure. One or more components can be combined together to perform same or substantially similar function in the SSF entity (100).

[0220] FIG. 3 is a block diagram illustrating the SPF entity (400), according to examples as disclosed herein. In an example, the SPF entity (400) includes a processor (410), a communicator (420), a memory (430), and a sensing service request authorizing controller (440). The processor (410) is operated with the communicator (420), the memory (430) and the sensing service request authorizing controller (440). Further, the sensing service request authorizing controller (440) 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.

[0221] The sensing service request authorizing controller (440) obtains the AF authorization data. In an example, the sensing service request authorizing controller (440) obtains the AF authorization data as part of the configuration by an Operations, Administration, and Maintenance (OAM) entity. In another example, the AF authorization data is configured by the AF entity (300) to the SPF entity (400). The sensing service request authorizing controller (440) receives the request or notification to provide the AF authorization data to the SSF entity (100). The sensing service request authorizing controller (440) sends the response comprising the AF authorization data to the SSF entity (100) based on the request or the notification.

[0222] Further, the processor (410) is configured to execute instructions stored in the memory (430) and to perform various processes. The communicator (420) is configured for communicating internally between internal hardware components and with external devices via one or more networks. The memory (430) also stores instructions to be executed by the processor (410). The memory (430) 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 (430) 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 (430) 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).

[0223] 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 (410). The processor (410) 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).

[0224] Although the FIG. 3 illustrates various hardware components of the SPF entity (400) but it is to be understood that other examples are not limited thereon. In other examples, the SPF entity (400) may include less or more number of components. Further, the labels or names of the components are used only for illustrative purpose and do not limit the scope of the disclosure. One or more components can be combined together to perform same or substantially similar function in the SPF entity (400).

[0225] FIG. 4 is a block diagram illustrating the NEF entity (200), according to examples as disclosed herein. In an example, the NEF entity (200) includes a processor (210), a communicator (220), a memory (230), and a sensing service request authorizing controller (240). The processor (210) is operated with the communicator (220), the memory (230) and the sensing service request authorizing controller (240). Further, the sensing service request authorizing controller (240) 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.

[0226] The sensing service request authorizing controller (240) receives the authorization of the AF entity (300) for the sensing service request for invoking the sensing service from the AF entity (300) when the AF entity (300) is outside of a trusted domain. The sensing service request authorizing controller (240) performs the authorization of the AF (300) for the sensing service request based on the SLA among the third party AF (300) and the 5GS of the mobile network operator, the operator policy and the local configuration.

[0227] The sensing service request authorizing controller (240) sends the sensing service request for invoking the sensing service to the SSF entity (100). The sensing service request authorizing controller (240) receives the result comprising one of: acceptance of the sensing service request and a rejection of the sensing service request from the SSF entity (100). The sensing service request authorizing controller (240) sends the result comprising one of: acceptance of the sensing service request and the rejection of the sensing service request to the AF entity (300).

[0228] 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).

[0229] 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).

[0230] Although the FIG. 4 illustrates various hardware components of the NEF entity (200) but it is to be understood that other examples are not limited thereon. In other examples, 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 do not limit the scope of the disclosure. One or more components can be combined together to perform same or substantially similar function in the NEF entity (200).

[0231] FIG. 5 is a flow chart (S500) illustrating a method for authorizing the sensing service request of the AF entity (300) in the wireless communication system (1000), according to examples as disclosed herein. The operations (S502-S514) are handled by the sensing service request authorizing controller (140).

[0232] At S502, the method includes receiving the sensing service request for invoking the sensing service from at least one of: the AF entity (300) directly if the AF entity (300) is inside the trusted domain or via the NEF entity (200) if the AF entity (300) is outside the trusted domain. At S504, the method includes sending the request to retrieve the AF authorization data to the SPF entity (400) based on the sensing service request. At S506, the method includes receiving the response comprising the AF authorization data from the SPF entity (400) based on the request.

[0233] At S508, the method includes performing the authorization of the AF's sensing service request using the AF authorization data. In an example, at S510, the method includes accepting the sensing service request after successful authorization when the sensing service can be served. In another example, at S512, the method includes rejecting the sensing service request when the sensing service cannot be served. At S514, the method includes sending the result comprising one of: acceptance of the sensing service request and a rejection of the sensing service request to at least one of: the NEF entity (200) and the AF entity (300).

[0234] FIG. 6 is a flow chart (S600) illustrating a method, implemented by the SPF entity (400), for authorizing the sensing service request of the AF entity (300) in the wireless communication system (1000), according to examples as disclosed herein. The operations (S602-S606) are handled by the sensing service request authorizing controller (440).

[0235] At S602, the method includes obtaining the AF authorization data. In an example, obtaining the AF authorization data comprises at least one of: obtaining the AF authorization data as part of a configuration by an Operations, Administration, and Maintenance (OAM) entity or the AF authorization data configured by the AF entity (300) to the SPF entity (400).

[0236] At S604, the method includes receiving the request or notification to provide an AF authorization data to the SSF entity (100). At S606, the method includes sending the response comprising the AF authorization data to the SSF entity (100) based on the request or the notification.

[0237] FIG. 7 is a flow chart (S700) illustrating a method, implemented by the NEF entity (200), for authorizing of the AF entity (300) for sensing service request in the wireless communication system (1000), according to examples as disclosed herein. The operations (S702-S710) are handled by the sensing service request authorizing controller (240). The wireless communication system (1000) can be, for example, but is not limited to a 4G system, a 5G system, 6G system, beyond 6G system or the like.

[0238] At S702, the method includes receiving the Authorization of the AF entity (300) for sensing the service request for invoking a sensing service from the AF entity (300) when the AF entity (300) is outside of the trusted domain. At S704, the method includes performing the authorization of the AF (300) for the sensing service request based on the SLA among the third party AF and the 5GS of the mobile network operator, the operator policy and the local configuration.

[0239] At S706, further, the method includes sending the sensing service request for invoking the sensing service to the SSF entity (100). At S708, the method includes receiving the result comprising one of: acceptance of the sensing service request and a rejection of the sensing service request from the SSF entity (100). At S710, the method includes sending the result comprising one of: acceptance of the sensing service request and the rejection of the sensing service request to the AF entity (300).

[0240] The various actions, acts, blocks, steps, or the like in the flow charts (S500-S700) may be performed in the order presented, in a different order or simultaneously. Further, in some examples, 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 disclosure.

[0241] The examples 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 illustrated in figures can be at least one of a hardware device, or a combination of hardware device and software module.

[0242] The foregoing description of the specific examples will so fully reveal the general nature of the examples herein that others can, by applying current knowledge, readily modify and / or adapt for various applications such specific examples 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 examples. 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 examples herein have been described in terms of at least one example, those skilled in the art will recognize that the examples herein can be practiced with modification within the scope of the examples as described herein.

Claims

1.A method performed by a network entity handling a sensing service in a communication system, the method comprising:receiving, from an application function (AF), a sensing service request for the sensing service;performing an authorization of the sensing service request based on information on sensing authorization including AF authorization data;in case that the authorization is granted, proceeding the sensing service request; andin case that the authorization is not granted, rejecting the sensing service request.2.The method of claim 1,wherein the AF authorization data includes at least one of an identifier (ID) used to identify the AF, first information on allowed or not allowed area for the AF to request the sensing service, second information on an allowed time period within which the AF can be authorized for the sensing service, and third information on type of the sensing service allowed for the AF, andwherein the type of the sensing service includes at least one of an object tracking and an object detection.3.The method of claim 1,wherein, in case that the AF is outside a trusted domain, the sensing service request is received from the AF via a network exposure function (NEF), the AF being authorized by the NEF before the sensing service request is received by the network entity handling the sensing service.4.The method of claim 3,wherein the network entity handling the sensing service is selected by the NEF based on local configuration or a query of a network repository function (NRF).5.A method performed by a network exposure function (NEF) in a communication system, the method comprising:receiving, from an application function (AF), a sensing service request for a sensing service;performing an authorization of the AF; andtransmitting, to a network entity handling the sensing service, the sensing service request for an authorization of the sensing service request by the network entity handling the sensing service,wherein the authorization of the sensing service request is associated with information on sensing authorization including AF authorization data.6.The method of claim 5,wherein the AF authorization data includes at least one of an identifier (ID) used to identify the AF, first information on allowed or not allowed area for the AF to request the sensing service, second information on an allowed time period within which the AF can be authorized for the sensing service, and third information on type of the sensing service allowed for the AF, andwherein the type of the sensing service includes at least one of an object tracking and an object detection.7.The method of claim 5,wherein the AF is outside a trusted domain.8.The method of claim 5, further comprising:selecting the network entity handling the sensing service based on local configuration or a query of a network repository function (NRF).9.A network entity handling a sensing service in a communication system, the network entity handling the sensing service comprising:a communicator;a processor coupled to the communicator; andmemory coupled to the processor and storing instructions executable by the processor,wherein the instructions cause the network entity handling the sensing service to:receive, from an application function (AF), a sensing service request for the sensing service,perform an authorization of the sensing service request based on information on sensing authorization including AF authorization data,in case that the authorization is granted, proceed the sensing service request, andin case that the authorization is not granted, reject the sensing service request.10.The network entity handling the sensing service of claim 9,wherein the AF authorization data includes at least one of an identifier (ID) used to identify the AF, first information on allowed or not allowed area for the AF to request the sensing service, second information on an allowed time period within which the AF can be authorized for the sensing service, and third information on type of the sensing service allowed for the AF, andwherein the type of the sensing service includes at least one of an object tracking and an object detection.11.The network entity handling the sensing service of claim 9,wherein, in case that the AF is outside a trusted domain, the sensing service request is received from the AF via a network exposure function (NEF), the AF being authorized by the NEF before the sensing service request is received by the network entity handling the sensing service.12.The network entity handling the sensing service of claim 11,wherein the network entity handling the sensing service is selected by the NEF based on local configuration or a query of a network repository function (NRF).13.A network exposure function (NEF) in a communication system, the NEF comprising:a communicator;a processor coupled to the communicator; andmemory coupled to the processor and storing instructions executable by the processor,wherein the instructions cause the NEF to:receive, from an application function (AF), a sensing service request for a sensing service,perform an authorization of the AF, andtransmit, to a network entity handling the sensing service, the sensing service request for an authorization of the sensing service request by the network entity handling the sensing service,wherein the authorization of the sensing service request is associated with information on sensing authorization including AF authorization data.14.The NEF of claim 13,wherein the AF authorization data includes at least one of an identifier (ID) used to identify the AF, first information on allowed or not allowed area for the AF to request the sensing service, second information on an allowed time period within which the AF can be authorized for the sensing service, and third information on type of the sensing service allowed for the AF, andwherein the type of the sensing service includes at least one of an object tracking and an object detection.15.The NEF of claim 13,wherein the AF is outside a trusted domain, andwherein the instructions further cause the NEF to select the network entity handling the sensing service based on local configuration or a query of a network repository function (NRF).