Method and apparatus for providing a wireless sensing service

The method and system for discovering and selecting sensing entities in 5G wireless networks address the lack of a clear core network architecture, improving entity selection and service quality by using authorized parameters through a network repository function.

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

Patent Information

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

AI Technical Summary

Technical Problem

Current 5G wireless sensing technologies lack a clearly defined end-to-end core network architecture for sensing operations, leading to suboptimal selection of sensing entities, higher latency, and inconsistent service quality due to inadequate authorization and entity definition for sensing service requests.

Method used

A method and system for discovering and selecting Sensing Service Functions (SSF) and sensing entities, such as NG-RAN nodes and UEs, through a network repository function (NRF) based on target sensing service area information, using authorized sensing parameters and capabilities, to provide a wireless sensing service.

Benefits of technology

Enhances the selection of sensing entities, reduces latency, and ensures consistent service quality by defining a clear end-to-end core network architecture for integrated sensing and communication.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure KR2026096572_12112026_PF_FP_ABST
    Figure KR2026096572_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. In one embodiment, a method performed by a sensing function comprises receiving, from a network entity, a sensing service request comprising target sensing service area information, obtaining, from an operations, administration, and maintenance (OAM) entity, sensing entity information, selecting at least one sensing entity based on at least one of the sensing service request or the sensing entity information, and transmitting, to the selected at least one sensing entity, at least one sensing parameter, wherein the sensing function is selected by the network entity via a network repository function (NRF) based on the target sensing service area information.
Need to check novelty before this filing date? Find Prior Art

Description

METHOD AND APPARATUS FOR PROVIDING A WIRELESS SENSING SERVICE

[0001] The present disclosure generally relates to network management, in particular, but not exclusively, to a method of providing a wireless sensing service, by a Sensing Service Function (SSF), in a communication network, and a method of obtaining a wireless sensing service, by an Application Function (AF), in the communication network and their associated systems.

[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] In one embodiment, a method performed by a sensing function comprises receiving, from a network entity, a sensing service request comprising target sensing service area information, obtaining, from an operations, administration, and maintenance (OAM) entity, sensing entity information, selecting at least one sensing entity based on at least one of the sensing service request or the sensing entity information, and transmitting, to the selected at least one sensing entity, at least one sensing parameter, wherein the sensing function is selected by the network entity via a network repository function (NRF) based on the target sensing service area information.

[0009] In one embodiment, the network entity is a trusted application function (AF) or a network exposure function (NEF).

[0010] In one embodiment, the at least one sensing parameter is transmitted to the selected at least one sensing entity via the selected AMF.

[0011] In one embodiment, a method performed by a network entity comprises, transmitting, to a network repository function (NRF), sensing function discovery information comprising target sensing service area information, receiving, from the NRF, information of at least one sensing function corresponding to the target sensing service area information, selecting a sensing function among the at least one sensing function, and transmitting, to the selected sensing function, a sensing service request comprising the target sensing service area information.

[0012] In one embodiment, the network entity is a trusted application function (AF) or a network exposure function (NEF).

[0013] In one embodiment, the selected sensing function is registered to the NRF with a network function (NF) profile comprising supported sensing service area information.

[0014] In one embodiment, a sensing function comprises at least one transceiver, at least one processor communicatively coupled to the at least one transceiver, and at least one memory, communicatively coupled to the at least one processor, storing instructions executable by the at least one processor individually or in any combination to cause the sensing function to receive, from a network entity, a sensing service request comprising target sensing service area information, obtain, from an operations, administration, and maintenance (OAM) entity, sensing entity information, select at least one sensing entity based on at least one of the sensing service request or the sensing entity information, and transmit, to the selected at least one sensing entity, at least one sensing parameter, wherein the sensing function is selected by the network entity via a network repository function (NRF) based on the target sensing service area information.

[0015] In one embodiment, the instructions further cause the sensing function to register to the NRF with a network function (NF) profile comprising supported sensing service area information.

[0016] In one embodiment, the network entity is a trusted application function (AF) or a network exposure function (NEF).

[0017] In one embodiment, the instructions further cause the sensing function to select an access and mobility function (AMF) associated with the selected at least one sensing entity, and the at least one sensing parameter is transmitted to the selected at least one sensing entity via the selected AMF.

[0018] In one embodiment, a network entity comprises at least one transceiver, at least one processor communicatively coupled to the at least one transceiver, and at least one memory, communicatively coupled to the at least one processor, storing instructions executable by the at least one processor individually or in any combination to cause the network entity to transmit, to a network repository function (NRF), sensing function discovery information comprising target sensing service area information, receive, from the NRF, information of at least one sensing function corresponding to the target sensing service area information, select a sensing function among the at least one sensing function, and transmit, to the selected sensing function, a sensing service request comprising the target sensing service area information.

[0019] In one embodiment, the network entity is a trusted application function (AF) or a network exposure function (NEF).

[0020] In one embodiment, the selected sensing function is registered to the NRF with a network function (NF) profile comprising supported sensing service area information.

[0021] The embodiments of the disclosure itself, as well as a preferred mode of use, further objectives, and advantages thereof, will best be understood by reference to the following detailed description of an illustrative embodiment when read in conjunction with the accompanying drawings. One or more embodiments are now described, by way of example only, with reference to the accompanying drawings in which:

[0022] FIG. 1 illustrates an environment diagram for providing a wireless sensing service, by a Sensing Service Function (SSF), and obtaining a wireless sensing service, by an Application Function (AF), in a communication network, in accordance with some embodiments of the present disclosure;

[0023] FIG. 2 illustrates a block diagram of a Sensing Service Function (SSF) for providing a wireless sensing service, in accordance with some embodiments of the present disclosure;

[0024] FIG. 3 illustrates a block diagram of an Application Function (AF) for obtaining a wireless sensing service, in accordance with some embodiments of the present disclosure;

[0025] FIG. 4 illustrates a data flow representation of providing a wireless sensing service, in accordance with some embodiments of the present disclosure;

[0026] FIG. 5 illustrates a data flow representation of authorizing the received sensing request, in accordance with some embodiments of the present disclosure;

[0027] FIG. 6 illustrates a data flow representation of selecting one or more sensing entities comprising at least Next Generation Radio Access Network (NG-RAN) nodes, in accordance with some embodiments of the present disclosure;

[0028] FIG. 7 illustrates a data flow representation of selecting one or more sensing entities comprising at least User Equipment (UEs), in accordance with some embodiments of the present disclosure;

[0029] FIG. 8 illustrates a data flow representation of discovery and selection of sensing function(s) and sensing entities, in accordance with the embodiments of the present disclosure;

[0030] FIG. 9 illustrates a flowchart representation of method of providing a wireless sensing service, by a Sensing Service Function (SSF), in accordance with the embodiments of the present disclosure; and

[0031] FIG. 10 illustrates a flowchart representation of method of obtaining a wireless sensing service, by an Application Function (AF), in accordance with the embodiments of the present disclosure.

[0032] FIG. 11 is a block diagram of a terminal or user equipment according to an embodiment of the disclosure.

[0033] FIG. 12 is a block diagram of a base station according to an embodiment of the disclosure.

[0034] FIG. 13 is a block diagram of a network entity according to an embodiment of the disclosure.

[0035] It should be appreciated by those skilled in the art that any block diagrams herein represent conceptual views of illustrative systems embodying the principles of the present subject matter. Similarly, it will be appreciated that any flow charts, flow diagrams, state transition diagrams, pseudo code, and the like represent various processes which may be substantially represented in computer-readable medium and executed by a computer or processor, whether or not such computer or processor is explicitly shown.

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

[0037] In describing the embodiments, while numerous details are set forth for the purpose of illustration, it is understood that some aspects of the disclosure may be practiced with less than all of these details. Numerous variations and alternatives to the details provided herein are possible and are considered within the scope of the disclosure. In some instances, descriptions related to technical contents well-known in the art may be omitted so as to not obscure an understanding of the disclosure, and such omitted descriptions are understood to be within the scope of the disclosure.

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

[0039] The advantages and features of the disclosure and ways to achieve them will be apparent by making reference to embodiments as described herein in detail in conjunction with the accompanying drawings. However, the disclosure is not limited to the embodiments set forth herein, but may be implemented in various different forms. Other features, aspects, and advantages of the subject matter described herein will become apparent from the disclosure. The following embodiments are merely examples to aid in an understanding of the disclosure and should not be construed to narrow the scope or spirit of the subject matter described herein in any way, but on the contrary, the disclosure covers all modifications, equivalents and alternatives falling within the spirit and scope of the subject matter as defined by the appended claims and equivalents thereof. Throughout the specification, the same or like reference numerals designate the same or like elements. Furthermore, terms which will be described herein 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.

[0040] Herein, it will be understood that each block of 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 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).

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

[0042] 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 / modules" 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.

[0043] 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 in different multiple memory devices.

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

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

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

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

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

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

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

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

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

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

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

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

[0056] 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 instances of the same signal transmitted at different times or containing the same core information despite minor variations, or they may refer to signals with different content or characteristics, depending on the specific context. Similarly, a "first value" and a "second value" may represent the same magnitude but measured or applied in different circumstances, or they may represent different magnitudes. The interpretation should be guided by the specific technical context, function, and relationship described in the relevant portion of the specification and claims.

[0057] 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, and 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.

[0058] 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 same information and, in some cases, are separate and different information.

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

[0060] For example, the physical layer signaling may be referred to as Layer 1 (L1) signaling and may include downlink control information (DCI). In addition, the higher layer signaling may include a medium access control (MAC) control message, a radio resource control (RRC) signaling message, a non-access stratum (NAS) signaling message, or an application layer message. The RRC signaling message may be referred to as L3 (layer 3) signaling. It should be noted, however, that the higher layer signaling is not limited to the aforementioned examples.

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

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

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

[0064] In the embodiments of the present disclosure described herein, 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.

[0065] The drawings or flowcharts described herein 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.

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

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

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

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

[0070] 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 describedherein, 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 the European telecommunications standards institute (ETSI), where appropriate.

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

[0072] 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 5th generation (5G) base station architectures in which such CU and DU functional splits are implemented.

[0073] A terminal may include a user equipment (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.

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

[0075] Furthermore, hereinafter, 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

[0076] In the following description, the terms physical channel and signal may be used interchangeably with data or control signal. For example, the term physical downlink shared channel (PDSCH) refers to a physical channel through which data is transmitted, but the term PDSCH may also be used to refer to the data itself. That is, in the present disclosure, the expression "transmit a physical channel" may be interpreted as being equivalent to the expression "transmit data or a signal via a physical channel."

[0077] Hereinafter, in the context of the present disclosure, higher layer signaling may refer to signaling corresponding to at least one or any combination of the following: master information block (MIB), system information block (SIB) or SIB M (M = 1, 2, ...), RRC, or MAC control element (CE), or a non-access stratum (NAS) signaling message, or an application layer message. The RRC signaling message may be referred to as Layer 3 (L3) signaling.

[0078] In addition, L1 signaling may refer to signaling corresponding to at least one or any combination of signaling techniques using the at least one or any combination of the following physical layer channels or signaling: physical downlink control channel (PDCCH), DCI, UE-specific DCI, group-common DCI, common DCI, scheduling DCI (e.g., DCI used for scheduling downlink or uplink data), non-scheduling DCI (e.g., DCI not used for scheduling downlink or uplink data) physical uplink control channel (PUCCH), or uplink control information (UCI). The L1 signaling message may be referred to as a physical layer signaling.

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

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

[0081] The Fifth Generation (5G) wireless sensing uses radio waves to infer properties of the environment and objects such as distance (range), angle, and instantaneous velocity by analysing transmissions, reflections, and scattering of sensing signals. Integrated sensing and communication unlocks new services across sectors (e.g., smart homes, Unmanned Aerial vehicles (UAVs), Vehicle-to-Everything (V2X), factories) by building on the cellular network for object detection / tracking, environmental monitoring, and human motion monitoring. Examples include intrusion detection (homes, highways, railways, factories, critical infrastructure), collision avoidance / trajectory tracking (UAVs, vehicles), automotive navigation, public-safety search and rescue, rainfall / flood monitoring, and health / sports monitoring.

[0082] However, in the existing technologies, there is a lack of a clearly defined end to end core network architecture for sensing operations. More specifically, current solutions do not fully specify about authorizing sensing service requests and sensing entities. Further, existing mechanisms don't clearly define entities configured to perform sensing operations. This leads to sub optimal selection, higher latency, and inconsistent service quality―precisely the area your solution addresses.

[0083] In view of the above, there is a need to address above-mentioned one or more problems.

[0084] The information disclosed in this background of the disclosure section is only for enhancement of understanding of the general background of the invention and should not be taken as an acknowledgement or any form of suggestion that this information forms the prior art already known to a person skilled in the art.

[0085] The present disclosure generally relates to the field of integrated sensing and communication in 3rdGeneration Partnership Project (3GPP). More particularly, the present disclosure relates to a method and a system for discovery and selection of sensing function(s) and sensing entities in order to provide a sensing service in a wireless system.

[0086] 5th Generation (5G) wireless sensing technology enables acquisition of information relating to an environment and / or objects within the environment. The 5G wireless sensing technology functions by analysing transmission, reflection, and scattering of wireless sensing signals. It utilizes radio waves to determine the distance (range), angle, or instantaneous linear velocity of the objects within the environment.

[0087] The 5G wireless sensing service of a cellular network provides new possibilities for enhanced usage of the telecommunication infrastructure in areas relating to object detection and tracking, environment monitoring and human motion monitoring. The 5G wireless technology provides supports across a variety of sectors such as Unmanned Aerial Vehicles (UAVs), smart homes, Vehicle-to-Everything (V2X), factories and the like.

[0088] In particular, the use cases for a 5G wireless sensing service cover a wide range of applications. Few exemplary usage scenarios include object and intruder detection for smart homes, on roads / highways, for railways, for factories, for restricted areas around critical infrastructure, collision avoidance and trajectory tracking of UAVs, road vehicles, Automated Guided Vehicles (AGVs), for automotive manoeuvring and navigation of vehicles, for search and rescue operations related to public safety, for rainfall monitoring and flooding, for health and sports monitoring and the like. These exemplary usage scenarios of 5G wireless sensing may also additionally utilize non-3GPP type sensors such as Radio Detection and Ranging (RADAR) and camera.

[0089] However, 5G wireless sensing service also brings challenges related to data confidentiality and privacy. Therefore, there exists a need to protect sensing data from unauthorized access, interception and eavesdropping, while also ensuring regulatory compliance.

[0090] The above-mentioned drawbacks / difficulties / disadvantages of conventional techniques are explained just for exemplary purpose and this disclosure and description mentioned below would never limit its scope to only such a problem. A person skilled in the art may understand that this disclosure and below mentioned description may also solve other problems or overcome the above-mentioned drawbacks / difficulties / disadvantages of the conventional arts which are not explicitly captured above.

[0091] The present disclosure relates to the field of integrated sensing and communication in 3rdGeneration Partnership Project (3GPP). The techniques of the present disclosure determine the potential of integrated sensing and communication technology for enabling new services and use cases for various industries.

[0092] The present disclosure describes a method and a system for discovery and selection of sensing function(s) and sensing entities in order to provide a sensing service in a wireless system. Few network functions such as SSF, SPF and AMF and sensing entities such as NG-RAN(s) and UE(s) are needed to be discovered and selected for providing the sensing service.

[0093] In an embodiment the present disclosure provides a method of providing a wireless sensing service, by a Sensing Service Function (SSF), in a communication network. The method comprises receiving a sensing service request from one of an Application Function (AF) or a Network Exposure Function (NEF), in which the sensing service request comprises at least target sensing area information. The method further comprises authorizing the received sensing request by obtaining AF authorization data from a Sensing Profile Function (SPF). Further, the method comprises selecting, from a plurality of entities, one or more sensing entities comprising at least Next Generation Radio Access Network (NG-RAN) nodes and / or User Equipment (UEs) for sensing operations, based on at least the target sensing area information, and capability information of the plurality of entities, upon authorization of the received sensing request, in which the capability information comprises at least one of sensing mode information, supported sensing area information, and user content information. Furthermore, the method comprises generating sensing results based on sensing data received from the selected one or more sensing entities. Subsequently, the method comprises providing the wireless sensing service by transmitting the generated sensing results to the AF.

[0094] Another aspect of the present disclosure includes a Sensing Service Function (SSF) for providing a wireless sensing service in a communication network. The SSF comprises a processor, and a memory coupled with the processor. The processor is configured to receive a sensing service request from one of an Application Function (AF) or a Network Exposure Function (NEF), in which the sensing service request comprises at least target sensing area information. The processor is further configured to authorize the received sensing request by obtaining AF authorization data from a Sensing Profile Function (SPF). Further, the processor is configured to select, from a plurality of entities, one or more sensing entities comprising at least Next Generation Radio Access Network (NG-RAN) nodes and / or User Equipment (UEs) for sensing operations, based on at least the target sensing area information, and capability information of the plurality of entities, upon authorization of the received sensing request, in which the capability information comprises at least one of sensing mode information, supported sensing area information, and user content information. Furthermore, the processor is configured to generate sensing results based on sensing data received from the selected one or more sensing entities. Subsequently, the processor is configured to provide the wireless sensing service by transmitting the generated sensing results to the AF.

[0095] In another embodiment, the present disclosure provides a method of obtaining a wireless sensing service, by an Application Function (AF), in a communication network. The method comprises transmitting a discovery request to a Network Repository Function (NRF), in which the discovery request comprises at least an identifier of the AF. The method comprises discovering, through the NRF, one or more Sensing Service Function (SSF) instances and selecting an SSF for providing the wireless sensing service, based on the transmitted discovery request. Further, the method comprises transmitting a sensing service request to the selected SSF, in which the sensing service request comprises at least target sensing area information. Furthermore, the method comprises obtaining the wireless sensing service by receiving sensing results from the SSF, based on the transmitted sensing service request, in which the sensing results are generated by the SSF, based on sensing data received from selected one or more sensing entities for sensing operations.

[0096] Another aspect of the present disclosure provides an Application Function (AF) for obtaining a wireless sensing service, in a communication network. The AF comprises a processor, and a memory coupled with the processor. The processor is configured to transmit a discovery request to a Network Repository Function (NRF), in which the discovery request comprises at least an identifier of the AF. The processor is further configured to discover, through the NRF, one or more Sensing Service Function (SSF) instances and select an SSF for providing the wireless sensing service, based on the transmitted discovery request. Further, the processor is configured to transmit a sensing service request to the selected SSF, in which the sensing service request comprises at least target sensing area information. Furthermore, the processor is configured to obtain the wireless sensing service by receiving sensing results from the SSF, based on the transmitted sensing service request, in which the sensing results are generated by the SSF, based on sensing data received from selected one or more sensing entities for sensing operations.

[0097] The foregoing summary is illustrative only and is not intended to be in any way limiting. In addition to the illustrative aspects, embodiments, and features described above, further aspects, embodiments, and features will become apparent by reference to the drawings and the following detailed description.

[0098] In the present document, the word "exemplary" is used herein to mean "serving as an example, instance, or illustration." Any embodiment or implementation of the present subject matter described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other embodiments.

[0099] The terms "comprises," "comprising," or any other variations thereof, are intended to cover a non-exclusive inclusion, such that a setup, device, or method that comprises a list of components or steps does not include only those components or steps but may include other components or steps not expressly listed or inherent to such setup or device or method. In other words, one or more elements in a system or apparatus proceeded by "comprises... a" does not, without more constraints, preclude the existence of other elements or additional elements in the system or apparatus.

[0100] In Release 20, 3rd Generation Partnership Project (3GPP) - Service and System Aspects (SA) Working Group (WG) 2 identified sensing service requirement. In 3GPP Technical Report (TR) 23.700-14, six key issues (KI#1 to #6) related to the sensing service requirement were identified.

[0101] Key Issue #1 (KI#1): System Architecture to Support Sensing, addresses 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 may be considered for KI#1.

[0102] NOTE: Solutions for other key issues may also impact general architecture aspects covered by KI#1.

[0103] Key Issue #2 (KI#2): Authorization and Revocation to Support Sensing Service addresses the authorization and revocation for a particular sensing service, specifically:

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

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

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

[0107] - 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 Technical Specification (TS) 22.137;

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

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

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

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

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

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

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

[0115] NOTE: The authorization and revocation for the sensing entities is related to the Key Issue #3 on sensing entities discovery and selection.

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

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

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

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

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

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

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

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

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

[0125] In Key Issue #4 (KI#4): Sensing Data and the Associated Information Collection and Transport, it was identified that the integration of sensing and communication requires 3GPP network to collect and transfer sensing data and the associated information to a Sensing Function.

[0126] The KI#4 aims to study:

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

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

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

[0130] NOTE: Implications to RAN or RAN dependent aspects are coordinated with RAN WGs.

[0131] Key Issue #5 (KI#5): Sensing Result Exposure, addresses the exposure of sensing results to support sensing services. The aspects studied in KI#5 include:

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

[0133] - How the core network exposes sensing results to the sensing service consumer (e.g., one time, periodic or event trigger).

[0134] Key Issue #6 (KI#6): Configuration and Parameter Provisioning of Sensing Entities studies how parameter provisioning of sensing entities is performed.

[0135] In particular, KI#6 will study:

[0136] - How and what parameters need to be exchanged between the sensing entities and the Core Network.

[0137] NOTE: KI#6 needs to be aligned with Radio Access Network (RAN) Working Groups (WGs).

[0138] In the present disclosure, solution to KI#3 is described which is the discovery and selection of sensing function(s) and sensing entities in order to provide the sensing service in 5GC.

[0139] The present disclosure describes techniques for discovery and selection of sensing function(s) and sensing entities which are involved in providing sensing service. The network functions that needed to be discovered and selected for providing sensing service, are described below:

[0140] Sensing Service Function (SSF): The present disclosure describes a new network function SSF to be introduced to the 5GC. SSF can receive the sensing service request from Network Exposure Function (NEF) or directly can receive from Application Function (AF). SSF can authorize the AF's sensing service request by retrieving the AF authorization data present in sensing profile function before accepting the request. If sensing service request is fulfilled and authorized, then SSF accepts the request and invokes sensing function and sensing entities for further processing like configuring parameters to sensing entities. SSF is also responsible for collecting sensing data and if any contextual information from sensing entities and calculate the sensing results. The sensing results later are shared with AF.

[0141] The SSF discovery and selection functionality is supported by the NEF, AF, AMF, or any NF to determine a SSF to provide sensing services.

[0142] When the NEF or AF perform SSF discovery and selection for a sensing service operation request, the following applies:

[0143] - The NEF or AF shall utilize the Network Repository Function (NRF) to discover SSF instance(s) unless SSF information is available by other means, e.g., locally configured in the NEF or AF. The NEF or AF provides to the NRF the Target Area information, when trying to discover SSF instance(s) as there can be multiple SSF(s) in deployment and each SSF serves different target areas. The NRF provides SSF instance(s) to the NEF or AF. For this to be realized, SSF shall register in NRF by mentioning the target area it supports for sensing service in its NF profile.

[0144] NOTE: The local configuration in the NEF is used for example to select a specific SSF instance for the request from a given AF.

[0145] - The NEF or the AF selects the SSF instance(s) based on the available SSF instance(s) (obtained from the NRF or locally configured)

[0146] Sensing Profile Function (SPF): The present disclosure describes a new network function SPF to be introduced to the 5GC. SPF will store the AF authorization data that is used by SSF to authorize AF before accepting any sensing service request.

[0147] The SPF discovery and selection functionality is supported by the SSF to determine a SPF to provide sensing services.

[0148] The SPF discovery and selection function is supported by the SSF to select an SPF instance to retrieve AF authorization data. When the SPF discovery is performed, the SSF utilizes the NRF to discover the SPF instance(s) unless the SPF information is available by other means, e.g., locally configured. The SSF provides to the NRF the AF ID, when trying to discover SPF instance(s). The SSF selects an SPF instance based on the available SPF instances (obtained from the NRF or locally configured). For this to be realized, SPF shall register in NRF by mentioning the AF ID it stores the Authorization data for sensing service in its NF profile. Similarly, the SPF can be discovered to get the UE as sensing entity because SPF may store the UE as sensing entity information. In this case SPF shall register in NRF by mentioning the UE ID like Subscription Permanent Identifier (SUPI) for which it stores the information for sensing service in its NF profile. When SSF needs to discover SPF to receive UE as sensing entity information, it will provide SUPI as the input to NRF to get the instances(s) of SPF.

[0149] New Generation -Radio Access Network (NG-RAN) (Sensing Entities):

[0150] The SSF selects NG-RAN node(s) which provides sensing service.

[0151] The SSF obtains the NG-RAN information (capability of providing sensing service, sensing service as Tx or Rx or both Tx and Rx, supported Area) via Operations, Administration, and Maintenance (OAM). The SSF receives sensing service request may include target area information from the NEF or trusted AF. Based on the received Target Area information and the NG-RAN information configured by OAM, the SSF selects the NG-RAN node(s).

[0152] NOTE 1: The Target Area information can span the supported Area of multiple NG-RAN node(s) or may be a subset of the supported Area of a NG-RAN node.

[0153] If multiple NG-RAN nodes are selected, the SSF sends the sensing service request to each selected NG-RAN node along with its corresponding RAN Area information.

[0154] If sensing service request includes target object as a User Equipment (UE) or UAV, then SSF will utilize the existing Location Services (LCS) or Access and Mobility Management Function (AMF) procedure to get positioning information of the UE or UAV and then find the NG-RAN, which serves the UE or UAV.

[0155] Access Mobility Function (AMF): SSF may use AMF to route the sensing service message to sensing entities (i.e., NG-RAN and / or UE) containing sensing operation parameters. Additionally, AMF if receives the capability of supporting sensing services from UE and optionally along with the user consent, can forward the message to SSF or SPF.

[0156] AMF discovery and selection functionality is implemented in SSF when indirect connectivity via AMF is used to transfer the sensing operation parameters.

[0157] When the SSF performs AMF discovery and selection in order to forward sensing service operation messages to the sensing entities (i.e., NG-RAN or UE) via AMF, the following applies:

[0158] - After Next Generation Application Protocol (NGAP) connection setup with NG-RAN, the AMF need to notify the NG-RAN ID to the SSF.

[0159] - After the NG-RAN selection for the sensing service operation, the SSF selects the AMF that has association with the selected NG-RAN nodes in order to forward the sensing service operation messages.

[0160] UE (Sensing Entities):

[0161] The SSF selects UE(s) which provide sensing service.

[0162] The SSF obtains the UE(s) information (capability of providing sensing service, sensing service as Tx or Rx or both Tx and Rx, supported area, user consent in general or for the area) either from AMF or from SPF. The SSF receives sensing service request may include target area information from the NEF or trusted AF. Based on the received Target Area information, if the UE(s) is inside the target area (SSF may subscribe with AMF or use LCS to get the UE positioning information), the SSF selects the UE(s). In some cases, SSF may have received sensing assistance information which include a UE ID attached to or in the proximity of the sensing target, UE position information, UE velocity information etc. So, using the above information SSF can select the UE(s) assuming these UEs have already provided consent to AF.

[0163] Abbreviations used:

[0164]

[0165] Despite the growing interest in wireless sensing, current 5G systems do not natively support end-to-end sensing service enablement. The existing architecture lacks standardized processes for authorizing sensing services, managing sensing entities, or discovering and selecting sensing functions and sensing nodes dynamically. There are also unresolved challenges in how sensing data should be collected, processed, and transported within the 5GC, and how sensing results should be securely exposed to consumers. Additionally, current systems do not define how sensing entities, whether NG-RAN nodes or UEs should be provisioned, configured, or re-selected, leading to gaps in scalability, privacy protection, and interoperability. These limitations collectively motivate the need for new mechanisms, particularly to support efficient and reliable discovery and selection of sensing functions and sensing entities.

[0166] Embodiments described herein provide a method and a Sensing Service Function (SSF) for providing a wireless sensing service, in a communication network. The method comprises receiving a sensing service request from one of an Application Function (AF) or a Network Exposure Function (NEF), in which the sensing service request comprises at least target sensing area information. The method further comprises authorizing the received sensing request by obtaining AF authorization data from a Sensing Profile Function (SPF). Further, the method comprises selecting, from a plurality of entities, one or more sensing entities comprising at least Next Generation Radio Access Network (NG-RAN) nodes and / or User Equipment (UEs) for sensing operations, based on at least the target sensing area information, and capability information of the plurality of entities, upon authorization of the received sensing request, in which the capability information comprises at least one of sensing mode information, supported sensing area information, and user content information. Furthermore, the method comprises generating sensing results based on sensing data received from the selected one or more sensing entities. Subsequently, the method comprises providing the wireless sensing service by transmitting the generated sensing results to the AF.

[0167] In one embodiment, authorizing the received sensing request, comprises transmitting Identifier (ID) of the AF to a Network Repository Function (NRF), discovering one or more SPF instances through the NRF, based on the transmitted ID of the AF, selecting, from the one or more SPF instances, the SPF comprising the AF authorization data, obtaining the AF authorization data from the selected SPF, and authorizing the received sensing request, based on the obtained AF authorization data.

[0168] In one embodiment, selecting, from the plurality of entities, the one or more sensing entities comprising at least the NG-RAN nodes, comprises obtaining capability information of the plurality of entities from an Operation, Administration and Maintenance (OAM) system, extracting the sensing mode information, and the supported sensing area information from the obtained capability information, the sensing mode information indicates transmission capability and / or reception capability of the one or more sensing entities, and selecting, from the plurality of entities, one or more sensing entities comprising at least the NG-RAN nodes for the sensing operations, based on the target sensing area information, and the extracted sensing mode information and the supported sensing area information.

[0169] In one embodiment, selecting, from the plurality of entities, the one or more sensing entities comprising at least the UEs, comprises obtaining capability information of the plurality of entities from one of Access and Mobility Management Function (AMF) or the SPF, extracting the supported sensing mode information, the supported sensing area information, and the user consent information from the obtained capability information, the sensing mode information transmission indicates capability and / or reception capability of the one or more sensing entities, determining whether the one or more sensing entities of the plurality of entities are within the target sensing area using positioning information obtained via one of the AMF or a Location Services (LCS) function, and selecting the one or more sensing entities comprising the UEs for the sensing operations, based on determined one or more sensing entities being within the target sensing area, and the extracted sensing mode information, the supported area information, and the user consent information.

[0170] In one embodiment, the method further comprises, discovering, through a Network Repository Function (NRF), one or more Access Mobility Function (AMF) instances and selecting the AMF having an association with the selected one or more sensing entities, transmitting the sensing service request to the one or more sensing entities via the selected AMF, in response to determining an indirect connectivity between the SSF and the one or more sensing entities, and transmitting the sensing service request directly to the one or more sensing entities, in response to determining a direct connectivity between the SSF and the one or more sensing entities.

[0171] The above method ensures that only valid and authorized sensing service requests are processed, by retrieving AF authorization data from the Sensing Profile Function (SPF) before execution. This prevents unauthorized sensing operations, improving network security and privacy compliance. By selecting sensing entities (NG-RAN nodes and / or UEs) based on: target sensing area information, sensing capability (Tx / Rx mode, supported area), and user-related info (e.g., consent), the above method ensures that only the most suitable entities are chosen. This leads to: more accurate sensing coverage, reduced latency in sensing result retrieval, and improved reliability of sensing operations.

[0172] The SSF comprises a processor, and a memory coupled with the processor. The processor is configured to receive a sensing service request from one of an Application Function (AF) or a Network Exposure Function (NEF), in which the sensing service request comprises at least target sensing area information. The processor is further configured to authorize the received sensing request by obtaining AF authorization data from a Sensing Profile Function (SPF). Further, the processor is configured to select, from a plurality of entities, one or more sensing entities comprising at least Next Generation Radio Access Network (NG-RAN) nodes and / or User Equipment (UEs) for sensing operations, based on at least the target sensing area information, and capability information of the plurality of entities, upon authorization of the received sensing request, in which the capability information comprises at least one of sensing mode information, supported sensing area information, and user content information. Furthermore, the processor is configured to generate sensing results based on sensing data received from the selected one or more sensing entities. Subsequently, the processor is configured to provide the wireless sensing service by transmitting the generated sensing results to the AF.

[0173] In one embodiment, wherein to authorize the received sensing request, the processor is configured to transmit Identifier (ID) of the AF to a Network Repository Function (NRF), discover one or more SPF instances through the NRF, based on the transmitted ID of the AF, select, from the one or more SPF instances, the SPF comprising the AF authorization data, obtain the AF authorization data from the selected SPF and authorize the received sensing request, based on the obtained AF authorization data.

[0174] In one embodiment, wherein to select, from the plurality of entities, the one or more sensing entities comprising at least the NG-RAN nodes, the processor is configured to obtain capability information of the plurality of entities from an Operation, Administration and Maintenance (OAM) system, extract the sensing mode information, and the supported sensing area information from the obtained capability information, wherein the sensing mode information transmission capability and / or reception capability of the one or more sensing entities, and select, from the plurality of entities, one or more sensing entities comprising at least the NG-RAN nodes for the sensing operations, based on the target sensing area information, and the extracted sensing mode information and the supported sensing area information.

[0175] In one embodiment, wherein to select, from the plurality of entities, the one or more sensing entities comprising at least the UEs, the processor is configured to obtain capability information of the plurality of entities from one of: Access and Mobility Management Function (AMF) or the SPF, extract the supported sensing mode information, the supported sensing area information, and the user consent information from the obtained capability information, wherein the sensing mode information transmission capability and / or reception capability of the one or more sensing entities, determine whether the one or more sensing entities of the plurality of entities are within the target sensing area using positioning information obtained via one of the AMF or a Location Services (LCS) function, and select the one or more sensing entities comprising the UEs for the sensing operations, based on determined one or more sensing entities being within the target sensing area, and the extracted sensing mode information, the supported area information, and the user consent information.

[0176] In one embodiment, wherein the processor is configured to discover, through a Network Repository Function (NRF), one or more Access Mobility Function (AMF) instances and selecting the AMF having an association with the selected one or more sensing entities, transmit the sensing service request to the one or more sensing entities via the selected AMF, in response to determining an indirect connectivity between the SSF and the one or more sensing entities, and transmit the sensing service request directly to the one or more sensing entities, in response to determining a direct connectivity between the SSF and the one or more sensing entities.

[0177] The SSF collects sensing data and any associated contextual information to generate sensing results. This produces: higher-quality sensing outputs, context-aware and situationally accurate sensing insights, and improved precision for downstream applications (e.g., tracking, monitoring), The SSF intelligently selects entities based on capability and area support.

[0178] This prevents: overloading certain RAN nodes, unnecessary involvement of UEs, and redundant sensing operations.

[0179] In another embodiment, the present disclosure provides a method of obtaining a wireless sensing service, by an Application Function (AF), in a communication network. The method comprises transmitting a discovery request to a Network Repository Function (NRF), in which the discovery request comprises at least an identifier of the AF. The method comprises discovering, through the NRF, one or more Sensing Service Function (SSF) instances and selecting an SSF for providing the wireless sensing service, based on the transmitted discovery request. Further, the method comprises transmitting a sensing service request to the selected SSF, in which the sensing service request comprises at least target sensing area information. Furthermore, the method comprises obtaining the wireless sensing service by receiving sensing results from the SSF, based on the transmitted sensing service request, in which the sensing results are generated by the SSF, based on sensing data received from selected one or more sensing entities for sensing operations.

[0180] By allowing the AF to send a discovery request containing identifier, to the NRF and retrieve available SSF instances, the above method enables precise and efficient selection of an appropriate SSF for the required sensing service. This ensures: Faster service setup, Reduced signalling overhead, and Correct association between AF requirements and SSF capabilities, Because the AF selects the SSF based on discovery results from the NRF, the above method guarantees that the AF interacts with an SSF instance that is: Registered, Valid, and Capable of handling the sensing request in the target area. This provides robustness and reliability in provisioning the wireless sensing service.

[0181] Another aspect of the present disclosure provides an Application Function (AF) for obtaining a wireless sensing service, in a communication network. The AF comprises a processor, and a memory coupled with the processor. The processor is configured to transmit a discovery request to a Network Repository Function (NRF), in which the discovery request comprises at least an identifier of the AF. The processor is further configured to discover, through the NRF, one or more Sensing Service Function (SSF) instances and select an SSF for providing the wireless sensing service, based on the transmitted discovery request. Further, the processor is configured to transmit a sensing service request to the selected SSF, in which the sensing service request comprises at least target sensing area information. Furthermore, the processor is configured to obtain the wireless sensing service by receiving sensing results from the SSF, based on the transmitted sensing service request, in which the sensing results are generated by the SSF, based on sensing data received from selected one or more sensing entities for sensing operations.

[0182] The AF receives the sensing results back from the SSF after submitting the sensing service request, enabling: Automated service flow, Minimal AF-side complexity, and Timely access to sensing insights for higher-layer applications (e.g., V2X, UAV, smart home). This improves overall service efficiency and AF application performance.

[0183] FIG. 1 illustrates an environment diagram 100 for providing a wireless sensing service, by a Sensing Service Function (SSF), and obtaining a wireless sensing service, by an Application Function (AF), in a communication network, in accordance with some embodiments of the present disclosure. As shown in FIG. 1, the environment diagram 100 comprises a SSF 101, an AF 103, one or more sensing entities 105, a communication network 107, and a Sensing Profile Function (SPF).

[0184] The SSF 101 is configured to receive a sensing service request from one of the AF 103 or a Network Exposure Function (NEF) (not shown in FIG. 1), in which the sensing service request comprises at least target sensing area information. More specifically, the SSF 101 may receive the sensing service request from the AF 103, through the communication network 107. In an embodiment, the communication network 107 may include, for example, but not limited to, 5G core network.

[0185] The SSF 101 is further configured to authorize the received AF sensing service request by obtaining AF 103 authorization data from the SPF 109. More specifically, the SSF 101 may receive the AF 103 authorization data from the SPF 109, through the communication network 107. Further, the SSF 101 is configured to select, from a plurality of entities, one or more sensing entities 105 comprising at least Next Generation Radio Access Network (NG-RAN) nodes and / or User Equipment (UEs) for sensing operations, based on at least the target sensing area information, and capability information of the plurality of entities, upon authorization of the received sensing request, in which the capability information comprises at least one of sensing mode information, supported sensing area information, and user content information. Furthermore, the SSF 101 is configured to generate sensing results based on sensing data received from the selected one or more sensing entities 105. Subsequently, the SSF 101 is configured to provide the wireless sensing service by transmitting the generated sensing results to the AF 103.

[0186] In an embodiment, the AF 103 may transmit a discovery request to a Network Repository Function (NRF) (not shown in FIG. 1), in which the discovery request comprises at least an identifier of the AF 103 and target sensing area information. Further, the AF 103 may discover, through the NRF, one or more Sensing Service Function (SSF) instances and select the SSF 101 for providing the wireless sensing service, based on the transmitted discovery request. Further, the AF 103 may transmit a sensing service request to the selected SSF 101, in which the sensing service request comprises at least target sensing area information. Furthermore, the AF 103 may obtain the wireless sensing service by receiving sensing results from the SSF 101, based on the transmitted sensing service request, in which the sensing results are generated by the SSF 101, based on sensing data received from selected one or more sensing entities 105 for sensing operations.

[0187] FIG. 2 illustrates a block diagram of a Sensing Service Function (SSF) 101 for providing a wireless sensing service, in accordance with some embodiments of the present disclosure. In an embodiment, the SSF 101 may include an I / O interface 203, a processor 205 and a memory 207 storing instructions, executable by the processor 205, which, on execution, may cause the SSF 101 to provide a wireless sensing service. In an embodiment, the memory 207 may include data 209. Further, the SSF 101 may also include a transceiver 210. More specifically, the SSF 101 may optionally incorporate the transceiver 210 to support centralized or cooperative sensing operations.

[0188] In an embodiment, the data 209 may include for example, but not limited to, sensing service request, AF 103 authorization data, and sensing results. In an embodiment, without limiting, the data 209 may be dynamically updated based on real-time data received by the SSF 101. The real-time data received may be received from the AF 103.

[0189] In an embodiment, the processor 205 may be configured to receive a sensing service request from one of an Application Function (AF) 103 or a Network Exposure Function (NEF) (not shown in FIG. 2), in which the sensing service request comprises at least target sensing area information. More specifically, the transceiver 210 may receive the sensing service request from the AF 103 and may further transmit the sensing service request for further processing. In an embodiment, the AF 103 is a 5G Core network function used by external or internal applications to request specific network services or capabilities. Further, the NEF is a 5G Core network function responsible for securely exposing internal network capabilities to external applications or other network functions.

[0190] In an embodiment, the processor 205 may be configured to authorize the received sensing request by obtaining AF 103 authorization data from the SPF 109. In an embodiment, the SPF is a network function that stores and provides authorization data for the AF 103, when the AF 103 requests for a sensing service. More specifically, the processor 205 may transmit Identifier (ID) of the AF 103 to a Network Repository Function (NRF) (not shown in FIG. 2). Further, the processor 205 may discover one or more SPF instances through the NRF, based on the transmitted ID of the AF 103. Further, the processor 205 may select, from the one or more SPF instances, the SPF 109 comprising the AF 103 authorization data. Furthermore, the processor 205 may obtain the AF 103 authorization data from the selected SPF 109. Subsequently, the processor 205 may authorize the received sensing request, based on the obtained AF 103 authorization data. In an embodiment, the NRF is a 5G Core network function responsible for service discovery. The NRF allows other network functions (such as the SSF 101) to discover instances of required network functions (e.g., SPF, AMF), and select the appropriate instance based on the information stored in the NRF.

[0191] In an embodiment, the processor 205 may select, from a plurality of entities, one or more sensing entities 105 comprising at least Next Generation Radio Access Network (NG-RAN) nodes and / or User Equipment (UEs) for sensing operations, based on at least the target sensing area information, and capability information of the plurality of entities, upon authorization of the received sensing request. The capability information comprises at least one of sensing mode information, supported sensing area information, and user content information. In an embodiment, the UEs may include, for example, but not limited to, a smartphone, a mobile phone, a personal digital assistant, a tablet computer, a tablet computer, a wearable device, a computer, a laptop computer, an Augmented Reality / Virtual Reality (AR / VR) device, Internet Of Things (IoT) device, a camera, any other device, and the combination thereof. Further, the NG-RAN nodes may include, for example, but not limited to, gNodeB (gNB).

[0192] More specifically, the processor 205 may obtain capability information of the plurality of entities from an Operation, Administration and Maintenance (OAM) system (not shown in FIG. 2). Further, the processor 205 may extract the sensing mode information, and the supported sensing area information from the obtained capability information, in which the sensing mode information indicates transmission capability and / or reception capability of the one or more sensing entities 105. Furthermore, the processor 205 may select, from the plurality of entities, one or more sensing entities 105 comprising at least the NG-RAN nodes for the sensing operations, based on the target sensing area information, and the extracted sensing mode information and the supported sensing area information.

[0193] In another embodiment, the processor 205 may obtain capability information of the plurality of entities from one of: Access and Mobility Management Function AMF (not shown in FIG. 2) or the SPF 109. In an embodiment, the AMF is a 5G core network function responsible for managing registration, connection, reachability, mobility, and UE-related access control.

[0194] Further, the processor 205 may extract the supported sensing mode information, the supported sensing area information, and the user consent information from the obtained capability information, in which the sensing mode information indicates transmission capability and / or reception capability of the one or more sensing entities 105. Further, the processor 205 may determine whether the one or more sensing entities 105 of the plurality of entities are within the target sensing area using positioning information obtained via one of the AMF or a Location Services (LCS) function. Furthermore, the processor 205 may select the one or more sensing entities 105 comprising the UEs for the sensing operations, based on determined one or more sensing entities being within the target sensing area, and the extracted sensing mode information, the supported area information, and the user consent information. In an embodiment, user consent information refers to data indicating whether a user (typically the UE owner) has granted permission for UE to participate in wireless sensing operations. This information is part of the capability information obtained by the SSF 101 from functions such as AMF or SPF 109 and is used to ensure privacy-compliant selection of the one or more sensing entities 105.

[0195] In an embodiment, the processor 205 may discover, through the NRF, one or more Access Mobility Function (AMF) instances and select the AMF having an association with the selected one or more sensing entities 105. Further, the processor 205 may transmit the sensing service request to the one or more sensing entities 105 via the selected AMF, in response to determining an indirect connectivity between the SSF 101 and the one or more sensing entities 105. In another embodiment, the processor 205 may transmit the sensing service request directly to the one or more sensing entities 105, in response to determining a direct connectivity between the SSF 101 and the one or more sensing entities 105. More specifically, the processor 205 may transmit the sensing service, using the transceiver 210.

[0196] Further, the processor 205 may generate sensing results based on sensing data received from the selected one or more sensing entities 105 and provide the wireless sensing service by transmitting the generated sensing results to the AF 103.

[0197] Furthermore, the SSF 101 may optionally include one or more modules (not shown in FIG. 2) for performing one or more operations performed by the processor 205. In an embodiment, each of the one or more modules may be a hardware unit / software module / firmware module which may be outside the memory 207 and coupled with the processor 205. In another embodiment, the one or more modules may be within the processor 205.

[0198] In an embodiment, the processor 205 may perform the above steps using the one or more modules. More specifically, the one or more modules may enable the processor 205 to perform the above recited steps of receiving a sensing service request, authorizing the received sensing request, selecting one or more sensing entities, generating sensing results, and providing the wireless sensing service.

[0199] FIG. 3 illustrates a block diagram of an Application Function (AF) 103 for obtaining a wireless sensing service, in accordance with some embodiments of the present disclosure. In an embodiment, the AF 103 may include an I / O interface 303, a processor 305 and a memory 307 storing instructions, executable by the processor 305, which, on execution, may cause the AF 103 to obtain a wireless sensing service. In an embodiment, the memory 307 may include data 309. Further, the AF 103 may also include a transceiver 310.

[0200] In an embodiment, the data 309 may include for example, but not limited to, discovery request, and the sensing service request. In an embodiment, without limiting, the data 209 may be dynamically updated based on real-time data transmitted by the AF 103. The real-time data may be transmitted to the SSF 101.

[0201] In an embodiment, the processor 305 may be configured to transmit a discovery request to the NRF (not shown in FIG. 3), in which the discovery request comprises at least an identifier of the AF 103 and target sensing area information. More specifically, the transceiver 310 may receive the discovery request from the processor 305 and further transmit the discovery request to the NRF for further processing.

[0202] The processor 305 may further be configured to discover, through the NRF, one or more Sensing Service Function (SSF) instances and select the SSF 101 for providing the wireless sensing service, based on the transmitted discovery request. Further, the processor may be configured to transmit the sensing service request to the selected SSF 101, in which the sensing service request comprises at least target sensing area information. Furthermore, the processor 305 may be configured to obtain the wireless sensing service by receiving sensing results from the SSF 101, based on the transmitted sensing service request, in which the sensing results are generated by the SSF 101, based on sensing data received from selected one or more sensing entities 105 for sensing operations.

[0203] Furthermore, the AF 103 may optionally include one or more modules (not shown in FIG. 3) for performing one or more operations performed by the processor 305. In an embodiment, each of the one or more modules may be a hardware unit / software module / firmware module or a combination thereof which may be outside the memory 307 and coupled with the processor 305. In another embodiment, the one or more modules may be within the processor 305.

[0204] In an embodiment, the processor 305 may perform the above steps using the one or more modules. More specifically, the one or more modules may enable the processor 305 to perform the above recited steps of transmitting a discovery request, discovering, through the NRF, one or more Sensing Service Function (SSF) instances, transmitting a sensing service, and obtaining the wireless sensing service.

[0205] FIG. 4 illustrates a data flow representation 400 of providing a wireless sensing service, in accordance with some embodiments of the present disclosure. In an embodiment, the data flow representation 400 comprises the AF 103, a NEF 401, the SPF 109, a plurality of entities 403, and one or more sensing entities 105.

[0206] In an embodiment, the SSF 101 may be configured to receive the sensing service request from one of the Application Function (AF) 103 or a Network Exposure Function (NEF) 401, in which the sensing service request comprises at least target sensing area information. That is, the SSF 101 may receive the sensing service request from NEF 401 as shown in block 410, or directly from the AF 103, as shown in block 411.

[0207] Further, the SSF 101 may be configured to authorize the received sensing request by obtaining AF 103 authorization data from the SPF 109, as shown in block 412. The SSF 101 may authorize the AF 103 by retrieving the AF 103 authorization data present in sensing profile function before accepting the request. If sensing service request may be fulfilled and authorized then the SSF 101 accepts the request and invoke sensing function and sensing entities for further processing such as configuring parameters to sensing entities. The SSF 101 may also be also responsible for collecting sensing data and if any contextual information from the one or more sensing entities 105 and calculate the sensing results. The sensing results later will be shared with AF 103.

[0208] In an embodiment, the SSF 101 may select, from a plurality of entities 403, one or more sensing entities 105 comprising at least Next Generation Radio Access Network (NG-RAN) nodes and / or User Equipment (UEs) for sensing operations. The SSF 101 may select the one or more sensing entities 403based on at least the target sensing area information, and capability information of the plurality of entities, upon authorization of the received sensing request. The capability information comprises at least one of sensing mode information, supported sensing area information, and user content information. In an embodiment, the UEs may include, for example, but not limited to, a smartphone, a mobile phone, a personal digital assistant, a tablet computer, a tablet computer, a wearable device, a computer, a laptop computer, an Augmented Reality / Virtual Reality (AR / VR) device, Internet Of Things (IoT) device, a camera, any other device, and the combination thereof. Further, the NG-RAN nodes may include, for example, but not limited to, gNodeB (gNB).

[0209] Further, the processor 205 may generate sensing results based on sensing data received from the selected one or more sensing entities 105 and provide the wireless sensing service by transmitting the generated sensing results to the AF 103, as shown in block 413.

[0210] Let us consider an example scenario of smart-highway object detection service, where a highway authority wants to detect obstacles on a 5-km stretch of road using 5G wireless sensing. The AF 103 triggers this service.

[0211] Step 1: AF 103 sends sensing service request → SSF 101

[0212] The AF 103 prepares a sensing-service request containing:

[0213] · Target Sensing Area: Highway Zone A (5 km stretch)

[0214] · QoS Requirements: High reliability

[0215] · Requested sensing mode: Both Tx / Rx required

[0216] The request is then sent either via NEF 401 (block 410) or directly to SSF (block 411). For example, the AF 103 sends the request through the NEF 401 → SSF 101.

[0217] Step 2: SSF 101 authorizes the sensing service request using the SPF 109

[0218] Once SSF 101 receives the request, the SSF 101 must verify that the AF 103 is authorized.

[0219] The SSF 101 contacts the SPF 109 (block 412) to retrieve AF 103 authorization data.

[0220] The SPF 109 checks whether the AF 103 has permissions for Highway Zone A sensing service.

[0221] If permission exists, the SSF 101 accepts the request and proceeds. For example, the SPF 109 confirms that the AF 103 is allowed to run obstacle-detection services for the highway authority. The SSF 101 authorizes the request.

[0222] Step 3: The SSF 101 selects one or more sensing entities 105 (NG-RAN nodes / UEs)

[0223] The SSF 101 evaluates the plurality of entities 403 and filters the plurality of entities 403 using:

[0224] · Target sensing area Information (from AF 103)

[0225] · Capability Info: sensing mode, supported sensing area, user-consent info

[0226] Entities in the Area:

[0227] · Three NG-RAN gNBs covering the 5 km zone

[0228] · Several UEs capable of sensing (e.g., roadside cameras, IoT devices, AR glasses worn by road workers)

[0229] For example, the SSF 101 selects:

[0230] · NG-RAN Node gNB-A: supports Tx + Rx sensing across entire zone

[0231] · NG-RAN Node gNB-B: supports Rx, covers 60% of zone

[0232] · Two IoT roadside devices: camera + radar sensors located along the highway.

[0233] Step 4: The SSF 101 collects sensing data and generates sensing results

[0234] Once the one or more sensing entities 105 are selected, the SSF 101:

[0235] · sends sensing operation parameters to each selected entity.

[0236] · receives sensing data (reflections, radar info, camera data, etc.).

[0237] · processes and fuses the collected data to detect obstacles.

[0238] Produces sensing results (block 413).

[0239] For example, result produced by SSF 101:

[0240] "Obstacle detected at 3.2 km mark; estimated size 1.5 m, stationary."

[0241] "No additional obstacles in the remaining zone."

[0242] Step 5: The SSF 101 sends sensing results back to the AF 103

[0243] Finally, the SSF 101 transmits the generated sensing results to AF 103. For example:

[0244] the AF 103 receives the obstacle detection and notifies the highway authority for immediate removal.

[0245] FIG. 5 illustrates a data flow representation 500 of authorizing the received sensing request, in accordance with some embodiments of the present disclosure. The data flow representation comprises the SSF 101, the AF 103, the NRF 501, and one or more SPF instances 503.

[0246] The SSF 101 may transmit Identifier (ID) of the AF 103 to the NRF 501, as shown in block 510. Further, the SSF 101 may discover one or more SPF instances 503 through the NRF 501, based on the transmitted ID of the AF 103. Further, the SSF 101 may select, from the one or more SPF instances 503, the SPF 109 comprising the AF 103 authorization data. Furthermore, the SSF 101 may obtain the AF 103 authorization data from the selected SPF 109, as shown in block 411. Subsequently, the SSF 101 may authorize the received sensing request, based on the obtained AF 103 authorization data. In an embodiment, the NRF is a 5G Core network function responsible for service discovery. The NRF allows other network functions (such as the SSF 101) to discover instances of required network functions (e.g., SPF, AMF), and select the appropriate instance based on the information stored in the NRF 501.

[0247] More specifically, the SSF 101 discovery and selection functionality is supported by the NEF 401 and the AF 103 to determine the SSF 101 to provide sensing services. The NEF 401 or AF 103 shall utilize the NRF 501 to discover SSF instance(s) unless the SSF 101 information is available by other means, e.g. locally configured in the NEF 401 or AF 103. The NEF 401 or AF 103 provides to the NRF 501 the target sensing area information, when trying to discover SSF instance(s). The NRF 501 provides SSF instance(s) to the NEF 401 or the AF 103. The NEF 401 or the AF 103 selects the SSF instance(s) based on the available SSF instance(s) (obtained from the NRF 501 or locally configured).

[0248] The SPF 109 discovery and selection functionality is supported by the SSF 101 to determine the SPF 109 to provide sensing services. The SPF 109 discovery and selection function is supported by the SSF 101 to select an SPF instance to retrieve AF 103 authorization data. When the SPF 109 discovery is performed, the SSF 101 utilizes the NRF 501 to discover the SPF instance(s) unless the SPF information is available by other means, e.g., locally configured. The SSF 101 provides to the NRF 501 the AF 103 ID, when trying to discover SPF instance(s). The SSF 101 selects an SPF instance based on the available SPF instances (obtained from the NRF or locally configured).

[0249] Let us consider an example of a highway authority intending to detect obstacles along a 5-km stretch of road using 5G wireless sensing.

[0250] Step 1: AF 103 sends the sensing service request to SSF 101

[0251] The AF 103 triggers the obstacle-detection service and sends a sensing service request (including the 5-km target area) to the SSF 101.

[0252] Step 2: SSF 101 sends AF Identifier (ID) to NRF 501

[0253] After receiving the sensing service request, the SSF 101 must verify whether the AF 103 is authorized to perform sensing. Therefore, the SSF 101 transmits the Identifier (ID) of AF 103 to the NRF 501 so that SPF discovery may begin (block 510). For example, the AF 103 ID is "AF-HighwayMonitor-01". The SSF 101 sends the ID to NRF 501 so the SSF 101 identify which SPF instances store authorization data for the AF 103.

[0254] Step 3: NRF 501 returns available one or more SPF instances 503

[0255] The NRF 501 is responsible for service discovery in the 5G core and returns a list of one or more SPF instances 503 that potentially contain AF-related authorization profiles. For example, NRF 501 finds three SPF candidates:

[0256] · SPF-North-1

[0257] · SPF-HighwaySector-A

[0258] · SPF-Backup-2

[0259] Step 4: SSF 101 selects the correct SPF instance:

[0260] The SSF 101 evaluates the returned SPF instances and selects the SPF instance (SPF 109) that contains authorization data specifically for AF-HighwayMonitor-01. For example, only SPF-HighwaySector-A stores the authorization data for the AF 103 monitoring the 5-km highway zone. Therefore, the SSF 101 chooses SPF-HighwaySector-A = SPF 109.

[0261] Step 5: The SSF 101 obtains AF 103 authorization data from the SPF 109

[0262] After selecting the correct SPF instance, the SSF 101 retrieves:

[0263] · Allowed sensing areas,

[0264] · Allowed sensing modes (Tx / Rx),

[0265] · Validity period, Policy constraints, etc.

[0266] For example, SPF 109 confirms that AF-HighwayMonitor-01 is authorized to request sensing on the 5-km segment. The AF 103 is allowed to use Tx / Rx mode for obstacle detection.

[0267] Step 6: SSF 101 authorizes the sensing service request

[0268] Once the AF 103 authorization data is obtained, the SSF 101 verifies that the request is valid.

[0269] The SSF 101 then authorizes the sensing service request based on SPF 109 data. For example, since the AF 103 has valid authorization for sensing in the target highway area, the SSF 101 approves the service request.

[0270] FIG. 6 illustrates a data flow representation of selecting one or more sensing entities comprising at least Next Generation Radio Access Network (NG-RAN) nodes, in accordance with some embodiments of the present disclosure. The data flow representation 600 comprises an OAM system 601, the SSF 101, the plurality of entities 403, and the one or more sensing entities 105.

[0271] In an embodiment, the SSF 101 may obtain capability information (as shown in block 610) of the plurality of entities 403 from an Operation, Administration and Maintenance (OAM) system 601. Further, the SSF 101 may extract the sensing mode information, and the supported sensing area information from the obtained capability information, wherein the sensing mode information indicates transmission capability and / or reception capability of the one or more sensing entities 105. Further, the SSF 101 may select, from the plurality of entities 403, one or more sensing entities 105 comprising at least the NG-RAN nodes for the sensing operations, based on the target sensing area information, and the extracted sensing mode information and the supported sensing area information.

[0272] The SSF 101 selects NG-RAN node(s) which provides sensing service. The SSF 101 obtains the NG-RAN information (capability of providing sensing service, sensing service as Tx or Rx or both Tx and Rx, supported Area) via the OAM system 601. The SSF 101 receives sensing service request including target sensing area information from the NEF 401 or trusted AF 103. Based on the received target sensing area information and the NG-RAN information configured by OAM system 601, the SSF 101 selects the NG-RAN node(s). In an embodiment, the target sensing area information may span the supported area of multiple NG-RAN node(s) or may be a subset of the supported area of a NG-RAN node. If multiple NG-RAN nodes are selected, the SSF 101 sends the sensing service request to each selected NG-RAN node along with corresponding RAN Area information.

[0273] Let us consider an example where a highway authority wants to detect obstacles (e.g., fallen trees, stalled vehicles, debris) along a 5 km stretch of highway using 5G wireless sensing infrastructure.

[0274] Step 1: SSF 101 obtains capability information from the OAM system 601

[0275] The SSF 101 requests capability information from the OAM system 601 for a group of NG-RAN nodes located along the 5 km highway section.

[0276] The capability information includes:

[0277] · Whether the NG-RAN node supports sensing

[0278] · Sensing modes: Tx, Rx, or Tx+Rx

[0279] · Supported sensing area (e.g., 1.5 km radius, 2 km linear coverage)

[0280] Step 2: SSF 101 extracts relevant sensing information

[0281] From the OAM system 601-provided capability data, the SSF 101 extracts:

[0282] Sensing mode information (e.g., Node A = Tx only, Node B = Tx+Rx)

[0283] Supported sensing area information (e.g., each node covers a portion of the 5 km stretch)

[0284] Step 3: Target sensing area is provided

[0285] The highway authority’s application sends a sensing service request via AF 103 / NEF 401 specifying target sensing area = 5 km stretch (from km marker 50 to 55)

[0286] Step 4: SSF 101 selects appropriate one or more sensing entities 105 (NG RAN Nodes)

[0287] The SSF 101 now evaluates which NG-RAN nodes supported areas overlap with the 5 km target area. Assume OAM system 601 reports the following three NG RAN nodes, as shown in Table 1:

[0288] NG-RAN NodeSensing ModeSupported Area CoverageOverlaps 5 km Target?Node ATx+RxCovers km 50-52YESNode BTx+RxCovers km 52-54YESNode CRx onlyCovers km 54-56Partially (54-55)

[0289] The SSF 101 selects:

[0290] Node A and Node B (full overlap with target area and support Tx+Rx)

[0291] Node C (partial overlap; can participate as Rx-only, enhancing sensing resolution)

[0292] Step 5: SSF 101 sends sensing service request to the selected NG-RAN nodes

[0293] Since the target area spans multiple NG-RAN nodes, the SSF 101 sends the sensing operation request to:

[0294] Node A (RAN Area = km 50-52)

[0295] Node B (RAN Area = km 52-54)

[0296] Node C (RAN Area = km 54-55)

[0297] Each node receives only relevant portion of the RAN area.

[0298] FIG. 7 illustrates a data flow representation 700 of selecting one or more sensing entities comprising at least User Equipment (UEs), in accordance with some embodiments of the present disclosure. The data flow representation 700 comprises an AMF 701, the SPF 109, the SSF 101, the plurality of entities 403, and the one or more sensing entities 105.

[0299] In an embodiment, the SSF 101 may obtain capability information of the plurality of entities 403 from one of a Access and Mobility Management Function (AMF) 701, as shown in block 710, or the SPF 109, as shown in block 711. Further, the SSF 101 may extract the supported sensing mode information, the supported sensing area information, and the user consent information from the obtained capability information, in which the sensing mode information transmission indicates capability and / or reception capability of the one or more sensing entities 105. Further, the SSF 101 may determine whether the one or more sensing entities 105 of the plurality of entities 403 are within the target sensing area using positioning information obtained via one of the AMF 701, as shown in block 712, or a Location Services (LCS) function (not shown in FIG. 7). Furthermore, the SSF 101 may select the one or more sensing entities 105 comprising the UEs for the sensing operations, based on determined one or more sensing entities 105 being within the target sensing area, and the extracted sensing mode information, the supported area information, and the user consent information.

[0300] The SSF 101 selects UE(s), which provides sensing service. The SSF 101 obtains the UE(s) information (capability of providing sensing service, sensing service as Tx or Rx or both Tx and Rx, supported Area, user consent in general or for the area) either from the AMF 701 or from SPF 109. The SSF 101 receives sensing service request may including target area information from the NEF 401 or trusted AF 103. Based on the received target sensing area information if the UE(s) is inside the target area (SSF 101 may subscribe with AMF 701 or use LCS to get the UE positioning information), the SSF 101 selects the UE(s). In some cases, the SSF 101 may have received sensing assistance information including UE ID attached to or in the proximity of the sensing target, UE position information, UE velocity information etc, to select the UE(s).

[0301] In an embodiment, if sensing service request includes target object as an UE or UAV, then the SSF 101 may utilize the existing LCS or AMF 701 procedure to get positioning information of the UE or UAV and then find the NG-RAN, serving the UE or UAV. The SSF 101 may use AMF 701 to route the sensing service request to sensing entities (i.e. NG-RAN and / or UE) containing sensing operation parameters. Additionally, the AMF 701 receives the capability of supporting sensing services from UE and optionally along with the user consent, and forward the message to SSF 101 or SPF 109. AMF 701 discovery and selection functionality is implemented in SSF 101 when indirect connectivity via AMF 701 is used to transfer the sensing operation parameters. When the SSF 101 performs AMF 701 discovery and selection in order to forward sensing service operation messages to the sensing entities (i.e. NG-RAN or UE) via AMF 701, the following applies:

[0302] · After NGAP connection setup with NG-RAN, the AMF 701 need to notify the NG-RAN ID to the SSF 101.

[0303] · After the NG-RAN selection for the sensing service operation, the SSF 101 selects the AMF 701 that has association with the selected NG-RAN nodes in order to forward the sensing service operation messages.

[0304] Let us consider the case where a highway authority intends to detect obstacles such as fallen trees, stalled vehicles, or debris, along a 5 km stretch of highway using 5G wireless sensing enabled by UE-based sensing entities.

[0305] Step 1: SSF 101 obtains capability information of UE-based sensing entities

[0306] The SSF 101 first obtains capability information for a plurality of potential sensing entities (UEs) either from the AMF 701 (as per block 710), or from the SPF 109 (as per block 711).

[0307] The capability information includes:

[0308] · Supported sensing mode (Tx, Rx, or Tx+Rx)

[0309] · Supported sensing area information

[0310] · User consent information for participation in sensing operations

[0311] The SSF 101 extracts required information from the obtained capability information. That is, the SSF 101 extracts:

[0312] · Sensing mode information indicating Tx / Rx capability

[0313] · Supported sensing area per UE (e.g., based on the UE’s typical operating region or cell coverage)

[0314] · User consent information (general or area-specific consent)

[0315] Step 3: Determining whether UEs are within the 5 km target sensing area

[0316] The highway authority submits a sensing request for target sensing area = 5 km highway segment (e.g., km 100 to km 105). To identify which UEs are physically within this region, the SSF obtains positioning information using AMF 701 (as per block 712), or LCS function

[0317] Positional checks allow the SSF 101 to determine:

[0318] · Which UEs are currently driving within the 5 km segment

[0319] · Whether those UEs have consented to sensing

[0320] · Whether sensing mode of the UEs supports the required obstacle-detection operation

[0321] Step 4: Example Identification of Available UEs

[0322] Assume the following UEs are detected by the AMF / LCS within the 5 km stretch, as shown in Table 2:

[0323] UELocation within the 5 km stretchSensing ModeUser ConsentSupported Sensing AreaUE-AAt km 100.5Tx+RxConsent given500 m radiusUE-BAt km 102.1Rx onlyConsent given300 m radiusUE-CAt km 104.7Tx onlyNo consent400 m radiusUE-DOutside areaTx+RxConsent givenN / A

[0324] Step 5: SSF 101 selects UE-Based sensing entities for obstacle detection

[0325] The SSF 101 applies the selection criteria as follows:

[0326] UE must be within the target sensing area

[0327] UE must have appropriate sensing mode

[0328] UE must have user consent

[0329] UE must have a supported sensing area that covers part of the 5 km stretch

[0330] Thus, the SSF 101 selects:

[0331] UE-A → Within area, Tx+Rx (ideal sensing), 500 m coverage, consent granted

[0332] UE-B → Within area, Rx only (helps in cooperative sensing), consent granted

[0333] UE-C is not selected because user consent is not present.

[0334] UE-D is outside the target area.

[0335] Step 6: Final Sensing Operation Setup

[0336] The SSF 101 then sends:

[0337] sensing operation parameters to UE-A and UE-B

[0338] Coordinates Tx / Rx roles for obstacle detection

[0339] Aggregates returned sensing data to infer obstacles along the 5 km segment

[0340] FIG. 8 illustrates a data flow representation 800 of discovery and selection of sensing function(s) and sensing entities, in accordance with the embodiments of the present disclosure. FIG. 8 illustrates three entities NG-RAN 801, the OAM system 601 and the SSF 101.

[0341] At block 810, the OAM system 601 is configured with a sensing capability to provide a sensing service to the NG-RAN 801. The sensing service supports sensing as Tx or Rx or both Tx and Rx, in a sensing service area. At block 811, the OAM system 601 is configured to discover SSF 101 through NRF 501 based on the sensing service area. At block 812, the OAM system 601 is configured to configure NG-RAN information to the SSF 101, wherein the NG-RAN information provides the sensing service to the SSF 101. At block 813, the SSF 106 either requests specific NG-RAN information (that supports sensing service for the sensing service area received from AF 103) via OAM system 601 or requests for all NG-RAN information which supports the sensing service via OAM system 601. At block 814, the SSF 101 is configured to select the NG-RANs that serves the sensing service area, the sensing service area being received from a trusted AF 103 or NEF 401. At block 815, the SSF 101 is configured to provide parameters of the sensing service to the NG-RAN 801.

[0342] FIG. 9 illustrates a flowchart representation of method 900 of providing a wireless sensing service, by a Sensing Service Function (SSF), in accordance with the embodiments of the present disclosure.

[0343] At step 901, the method 900 includes receiving a sensing service request from one of an Application Function (AF) 103 or a Network Exposure Function (NEF) 401, in which the sensing service request comprises at least target sensing area information.

[0344] At step 902, the method 900 includes authorizing the received sensing request by obtaining AF 103 authorization data from a Sensing Profile Function (SPF) 109. More specifically, the method 900 includes transmitting Identifier (ID) of the AF 103 to a Network Repository Function (NRF) 501, and discovering one or more SPF instances 503 through the NRF 501, based on the transmitted ID of the AF 103. Further, the method 900 includes selecting, from the one or more SPF instances 503, the SPF 109 comprising the AF 103 authorization data. Furthermore, the method 900 includes obtaining the AF 103 authorization data from the selected SPF 109, and authorizing the received sensing request, based on the obtained AF 103 authorization data.

[0345] At step 903, the method 900 includes selecting, from the plurality of entities 403, one or more sensing entities 105 comprising at least Next Generation Radio Access Network (NG-RAN) nodes and / or User Equipment (UEs) for sensing operations, based on at least the target sensing area information, and capability information of the plurality of entities, upon authorization of the received sensing request. The capability information comprises at least one of sensing mode information, supported sensing area information, and user content information. More specifically, the method 900 includes obtaining capability information of the plurality of entities from an Operation, Administration and Maintenance (OAM) system 601. Further, the method 900 includes extracting the sensing mode information, and the supported sensing area information from the obtained capability information, in which the sensing mode information indicates transmission capability and / or reception capability of the one or more sensing entities. Furthermore, the method 900 includes selecting, from the plurality of entities 403, one or more sensing entities 105 comprising at least the NG-RAN nodes for the sensing operations, based on the target sensing area information, and the extracted sensing mode information and the supported sensing area information.

[0346] In another embodiment, the method 900 includes obtaining capability information of the plurality of entities 403 from one of: Access and Mobility Management Function (AMF) 701 or the SPF 109. Further, the method 900 includes extracting the supported sensing mode information, the supported sensing area information, and the user consent information from the obtained capability information, in which the sensing mode information transmission indicates capability and / or reception capability of the one or more sensing entities 105. Further, the method 900 includes determining whether the one or more sensing entities 105 of the plurality of entities 403 are within the target sensing area using positioning information obtained via one of the AMF 701 or a Location Services (LCS) function. Furthermore, the method 900 includes selecting the one or more sensing entities 105 comprising the UEs for the sensing operations, based on determined one or more sensing entities 105 being within the target sensing area, and the extracted sensing mode information, the supported area information, and the user consent information.

[0347] At step 904, the method 900 includes generating sensing results based on sensing data received from the selected one or more sensing entities 105. At step 905, the method 900 includes providing the wireless sensing service by transmitting the generated sensing results to the AF 103.

[0348] The method 900 also includes discovering, through a Network Repository Function (NRF) 501, one or more Access Mobility Function (AMF) instances and selecting the AMF 701 having an association with the selected one or more sensing entities 105. Further, the method 900 includes transmitting the sensing service request to the one or more sensing entities 105 via the selected AMF 701, in response to determining an indirect connectivity between the SSF 101 and the one or more sensing entities 105. Furthermore, the method 900 includes transmitting the sensing service request directly to the one or more sensing entities 105, in response to determining a direct connectivity between the SSF 101 and the one or more sensing entities 105.

[0349] By authorizing the sensing service request using AF 103 authorization data retrieved from the SPF 109 (via NRF-based discovery), the method 900 ensures that only valid and permitted applications can request sensing services. This prevents unauthorized access to sensitive sensing capabilities and data. The method 900 enables the precise identification and selection of suitable sensing entities (NG-RAN nodes and / or UEs) based on: Target sensing area, Sensing mode (Tx / Rx capability), Supported sensing area, User consent (for UEs), and Entity positioning (via AMF or LCS). This ensures optimal coverage, accuracy, and efficiency of the sensing operation by using only those entities capable of performing sensing within the required area.

[0350] FIG. 10 illustrates a flowchart representation of method of obtaining a wireless sensing service, by an Application Function (AF), in accordance with the embodiments of the present disclosure.

[0351] At step 1001, the method 1000 includes transmitting a discovery request to a Network Repository Function (NRF) 501, in which the discovery request comprises at least an identifier of the AF 103 and target sensing area information. At step 1002, the method 1000 includes discovering, through the NRF 501, one or more Sensing Service Function (SSF) instances and selecting an SSF 101 for providing the wireless sensing service, based on the transmitted discovery request. At step 1003, the method 1000 includes transmitting a sensing service request to the selected SSF 101, in which the sensing service request comprises at least target sensing area information. At step 1004, the method 1000 includes obtaining the wireless sensing service by receiving sensing results from the SSF 101, based on the transmitted sensing service request, in which the sensing results are generated by the SSF 101, based on sensing data received from selected one or more sensing entities 105 for sensing operations.

[0352] By transmitting a discovery request containing the AF 103 identifier and target sensing area information to the NRF 501, the method 1000 allows the SSF 101 to accurately identify and select the most suitable SSF instance among potentially multiple deployed SSFs. This ensures that the chosen SSF has the correct scope, capabilities, and proximity to handle the specific sensing service request effectively. Once a relevant SSF is selected through NRF-based discovery, the method 1000 efficiently invokes the sensing service by transmitting the sensing service request including target area information, directly to the selected SSF 101. This reduces latency and streamlines the startup of sensing operations.

[0353] FIG. 11 is a block diagram of a terminal or user equipment (UE) 1100 according to an embodiment of the disclosure.

[0354] The terminal is an electronic device capable of wireless communication and having various form factors, examples of the 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 wireless communication with a base station (BS) and / or another terminal through a wireless channel.

[0355] Referring to FIG. 11, the UE 1100 may include at least one transceiver (hereinafter, referred to as simply “transceiver”) 1101, at least one processor (hereinafter, referred to as simply “processor”) 1102, and at least one memory (hereinafter, referred to as simply “memory”) 1103. According to at least one or a combination of methods corresponding to the embodiments described in the present disclosure, the transceiver 1101, the processor 1102, and the memory 1103 of the UE 1100 may operate. However, components of the UE 1100 are not limited to the example components illustrated in FIG. 11. In another embodiment, the UE 1100 may further include additional components in addition to the above-mentioned components, or some components may be omitted. Further, in some embodiments, any combination of the transceiver 1101, the processor 1102, or the memory 1103 may be integrated in the form of one component.

[0356] The transceiver 1101 may be a communication circuit or communication circuitry that enables the UE 1100 to perform wireless communication with a node or an entity of a network. For example, the transceiver 1101 may enable the UE 1100 to transmit or receive a signal to or from a BS through cellular communication, or to transmit or receive a signal to or from another UE through cellular communication. For example, the transceiver 1101 may support at least one of various cellular communication technologies including 3rd generation (3G), 4th generation (4G), long term evolution (LTE), 5th generation (5G) NR, 6th generation (6G), and various cellular wireless communication technologies supported by the transceiver (1101) may include all subsequent generations of evolved wireless communications.

[0357] According to an embodiment, the UE 1100 may include a plurality of transceivers. For example, in the case of supporting evolved-universal terrestrial radio access-new radio (E-UTRA-NR) dual connectivity (EN-DC), the UE 1100 may include a first transceiver supporting the 4G LTE wireless communication and a second transceiver supporting the 5G NR wireless communication. According to another embodiment, in the case of supporting NR-dual connectivity (NR-DC), the UE 1100 may include a plurality of transceivers supporting the 5G NR wireless communication. According to still another embodiment, in the case of supporting near field wireless communication, the UE 1100 may separately include a transceiver supporting at least one standard in the group of wireless communication protocol standards as defined in the protocol standards for Bluetooth®, wireless local area network (WLAN) network (including institute of electrical and electronics engineers (IEEE) 802.11-2016 standard or its amendments, e.g., 802.11ah, 802.11ad, 802.11ay, 802.11ax, 802.11az, 802.11ba, and 802.11be, without being limited thereto).

[0358] According to an embodiment, the transceiver 1101 may include various circuit structures used to transmit or receive signals to or from a BS through a wireless channel. The signals may include control information and data. For example, the transceiver 1101 may include a radio frequency (RF) transmitter for up-converting and amplifying the frequency of a transmitted signal and an RF receiver for low-noise-amplifying a received signal and down-converting the frequency thereof. The transceiver 1101 may output a signal received through a wireless channel to the processor 1102 and may transmit, through a wireless channel, a signal output from the processor 1102.

[0359] The processor 1102 may control general operations of the UE 1100 according to embodiments of the disclosure. The processor 1102 may be implemented by one or more integrated circuit (or circuitry) (IC) chips and may execute various data processing operations. The processor 1102 may include at least one electric circuit, and may execute instructions (or a program, codes, data, etc.) stored in the memory 1103, individually, collectively or in any combination thereof. Further, the processor 1102 may include a single-core processor or multi-core processor, and may include a processor assembly including a plurality of processing circuits (circuitry) according to a specific implementation scheme.

[0360] The processor 1102 may be electrically, operatively, and / or communicatively coupled to the transceiver 1101 to control the transceiver 1101.

[0361] The processor 1102 may include at least one processor (or processing circuitry), and the at least one processor may perform the following operations individually, collectively or in any combination thereof. For example, the processor 1102 may include a communication processor (CP) configured to control communication operations and an application processor (AP) configured to control execution of an upper layer (for example, an application layer). In a specific embodiment, at least a part of the processor 1102 may be included in one chip (or IC) and the other part of the processor 1102 may be included in another chip (or IC). Otherwise, at least one processor may be included in another component, for example, the transceiver 1101 or the memory 1103.

[0362] The processor 1102 may perform or control or cause an operation of the UE 1100 for executing at least one or a combination of methods according to embodiments of the disclosure. For example, the processor 1102 may control operations of the UE 1100 for processing a downlink signal received from a BS or generating and transmitting an uplink signal to a BS. To this end, the processor 1102 may execute a computer program, codes, or instructions stored in the memory 1103, so as to control other components of the UE 1100 to enable execution of various operations.

[0363] The memory 1103 corresponds to a hardware storage device capable of temporarily or permanently storing information and may include one or more storage media. For example, the memory 1103 may include a memory assembly including one or more storage media. For example, the one or more storage media may include permanent memory, such as a hard drive, flash memory, or read-only memory (ROM), semipermanent memory, such as random access memory (RAM), cache memory, or a combination thereof.

[0364] The memory 1103 may be electrically, operatively, and / or communicatively coupled to the processor 1102 and may be accessed by the processor 1102.

[0365] The memory 1103 may store a computer program, codes, or instructions executable by the processor 1102. According to an embodiment, a computer program, codes, or instructions executable by the processor 1102 may be either stored in a single memory device or separated and distributedly stored in two or more memory devices. By executing the instructions stored in the memory 1103, the processor 1102 may perform various functions according to an embodiment of the disclosure.

[0366] According to an embodiment of the disclosure, operations of the UE 1100 may be caused to be performed based on execution of instructions (or a computer program or codes) stored in the memory 1103 by at least one processor (or processing circuitry) configured to execute the same individually, collectively, or in any combination thereof, based on processing circuitry that is not configured to execute instructions, and / or based on components of processing circuitry that is not configured to execute instructions.

[0367] FIG. 12 is a block diagram of a base station (BS) 1200 according to an embodiment of the disclosure.

[0368] The BS 1200 may perform wireless communication with at least one user equipment (UE) located within the area of the BS 1200 through a wireless channel. The BS 1200 may perform communication with a node or an entity of a network through wired or wireless communication.

[0369] Referring to FIG. 12, the BS 1200 may include at least one transceiver (hereinafter, referred to as simply “transceiver”) 1201, at least one processor (hereinafter, referred to as simply “processor”) 1202, and at least one memory (hereinafter, referred to as simply “memory”) 1203. According to at least one or a combination of methods corresponding to the embodiments described in the present disclosure, the transceiver 1201, the processor 1202, and the memory 1203 of the BS 1200 may operate. However, components of the BS 1200 are not limited to the example components illustrated in FIG. 12. In another embodiment, the BS 1200 may further include additional components in addition to the above-mentioned components, or some components may be omitted. Further, in some embodiments, any combination of the transceiver 1201, the processor 1202, or the memory 1203 may be integrated in the form of one component.

[0370] The transceiver 1201 may be a communication circuit or communication circuitry that enables the BS 1200 to perform wireless communication with a node or an entity of a network. For example, the transceiver 1201 may enable the BS 1200 to transmit or receive a signal to or from the UE X00 through cellular communication, or to transmit or receive a signal to or from another network entity through wireless communication. For example, the transceiver 1201 may support various cellular communication technologies including 3rd generation (3G), 4th generation (4G), long term evolution (LTE), 5th generation (5G) NR, 6th generation (6G), and various cellular wireless communication technologies supported by the transceiver (1201) may include all subsequent generations of evolved wireless communications.. According to an embodiment, the transceiver 1201 may include various circuit structures used to transmit or receive signals to or from a UE through a wireless channel. The signals may include control information and data. For example, the transceiver 1201 may include a radio frequency (RF) transmitter for up-converting and amplifying the frequency of a transmitted signal and an RF receiver for low-noise-amplifying a received signal and down-converting the frequency thereof. The transceiver 1201 may output a signal received through a wireless channel to the processor 1202 and may transmit, through a wireless channel, a signal output from the processor 1202.

[0371] Meanwhile, according to an embodiment of the present disclosure, the BS 1200 may perform communication with a node or an entity of a network through wired or wireless communication. For example, the BS 1200 may perform wired or wireless communication with an adjacent BS, or a node or an entity of a core network through a backhaul network. Although not illustrated in FIG. 12, when the BS 1200 performs wired communication, the BS 1200 may further include a separate network interface for wired communication in addition to the transceiver 1201. The network interface may be referred to as network interface circuitry or communication interface circuitry.

[0372] The processor 1202 may control general operations of the BS 1200 according to embodiments of the disclosure. The processor 1202 may be implemented by one or more integrated circuit (or circuitry) (IC) chips and may execute various data processing operations. The processor 1202 may include at least one electric circuit, and may execute instructions (or a program, codes, data, etc.) stored in the memory 1203, individually, collectively or in any combination thereof. Further, the processor 1202 may include a single-core processor or multi-core processor, and may include a processor assembly including a plurality of processing circuits (circuitry) according to a specific implementation scheme.

[0373] The processor 1202 may be electrically, operatively, and / or communicatively coupled to the transceiver 1201 to control the transceiver 1201.

[0374] The processor 1202 may include at least one processor (or processing circuitry), and the at least one processor may perform the following operations individually, collectively or in any combination thereof. In a specific embodiment, at least a part of the processor 1202 may be included in one chip (or IC) and the other part of the processor 1202 may be included in another chip (or IC). Otherwise, at least one processor may be included in another component, for example, the transceiver 1201 or the memory 1203.

[0375] The processor 1202 may perform or control or cause an operation of the BS 1200 for executing at least one or a combination of methods according to embodiments of the disclosure. For example, the processor 1202 may control operations of the BS 1200 for generating and transmitting a downlink signal to a UE or processing an uplink signal received from a UE. Otherwise, the BS 1200 may transmit or receive a signal to or from a neighboring BS, transfer a signal received from a UE to an upper node of the network, or transmit a signal transferred from an upper node of the network to a UE. To this end, the processor 1202 may execute a computer program, codes, or instructions stored in the memory 1203, so as to control other components of the BS 1200 to enable execution of various operations.

[0376] The memory 1203 corresponds to a hardware storage device capable of temporarily or permanently storing information and may include one or more storage media. For example, the memory 1203 may include a memory assembly including one or more storage media. For example, the one or more storage media may include permanent memory, such as a hard drive, flash memory, or read-only memory (ROM), semipermanent memory, such as random access memory (RAM), cache memory, or a combination thereof.

[0377] The memory 1203 may be electrically, operatively, and / or communicatively coupled to the processor 1202 and may be accessed by the processor 1202.

[0378] The memory 1203 may store a computer program, codes, or instructions executable by the processor 1202. According to an embodiment, a computer program, codes, or instructions executable by the processor 1202 may be either stored in a single memory device or separated and distributedly stored in two or more memory devices. By executing the instructions stored in the memory 1203, the processor 1202 may perform various functions according to an embodiment of the disclosure.

[0379] According to an embodiment of the disclosure, operations of the BS 1200 may be caused to be performed based on execution of instructions (or a computer program or codes) stored in the memory 1203 by at least one processor (or processing circuitry) configured to execute the same individually, collectively, or in any combination thereof, based on processing circuitry that is not configured to execute instructions, and / or based on components of processing circuitry that is not configured to execute instructions.

[0380] The UE or the base station may perform various communication procedures related to the control plane or the user plane by cooperating with one or more network entities based on wireless communication. For example, the UE may communicate with a network entity (for example, an Access and Mobility Management Function (AMF), a Session Management Function (SMF), rtc.) via the base station, or the base station may perform at least one communication procedure by directly transmitting and receiving signals to / from, or relaying signals between, the network entities.

[0381] The structure of the above-described network entity will be described in more detail with reference to the drawings.

[0382] FIG. 13 is a block diagram of a network entity 1300 according to an embodiment of the disclosure. The network entity of FIG. 13 may correspond to the SSF of FIG. 2 or the AF of FIG. 3.

[0383] The network entity 1300 may include an entity (apparatus, device, or server, etc.) that performs one or more network functions (NFs) or a part of a network function constituting a core network (e.g., a 5th generation (5G) core (5GC)) in a communication system. In this case, multiple NFs may be implemented within a single network entity, or a single NF may be distributed and implemented across a plurality of network entities. In addition, when an NF is implemented within the network entity, the NF may be implemented in the form of software, and in such a case, a program for operating the NF may be stored in memory of the network entity 1300.

[0384] A single NF may be implemented by one or more instances, which may be deployed on the same network entity or distributed across multiple network entities to operate. The instance may be a software unit that logically executes a specific network function, and may be implemented in a form that is decoupled from physical hardware resources. Further, one or more NFs may be implemented in the form of one network slice to operate to satisfy specifications required by a particular service.

[0385] The NF may include at least one of an access and mobility management function (AMF), a session management function (SMF), a local session management function (L-SMF), a user plane function (UPF), a local user plane function (L-UPF), a policy control function (PCF), a unified data management (UDM), a unified data repository (UDR), a network exposure function (NEF), a network repository function (NRF), an application function (AF), a network slice selection function (NSSF), a network data analytics function (NWDAF), a network slice admission control function (NSACF), an authentication server function (AUSF), or a data network (DN), etc.

[0386] Referring to FIG. 13, the network entity 1300 may include at least one network interface 1301, at least one processor 1302 (hereinafter, "processor"), and at least one memory 1303 (hereinafter, "memory"). As described above, a NF may be implemented in the form of a physical device such as the network entity 1300, or may be virtualized and executed in the form of an instance. When implemented as an instance, the NF need not necessarily include physical components as illustrated in FIG. 13. In such a case, the instance may be logically represented as comprising one or more logical functional elements.

[0387] According to at least one or a combination of methods corresponding to the embodiments described in the present disclosure, the network interface 1301, the processor 1302, and the memory 1303 of the network entity 1300 may operate. However, components of the network entity 1300 are not limited to the example components illustrated in FIG. 13. In another embodiment, the network entity 1300 may further include additional components in addition to the above-mentioned components, or some components may be omitted. Further, in an embodiment, the network interface 1301, the processor 1302, or the memory 1303 may be integrated in the form of one component.

[0388] The network interface 1301 is a collective term for a transmitter part of the network entity 1300 and a receiver part of the network entity 1300, and may be a communication circuit for transmitting or receiving a signal to or from a user equipment (UE), a base station (BS), or another network entity. Here, the communication circuit may include both a communication circuit for wireless communication and a communication circuit for a wired communication. For example, the network interface 1301 may include a circuit, logic, hardware, etc., configured to exchange a control plane message or a user plane message with a UE, a BS, or other core network entities through wireless communication or wired communication. The network interface 1301 may operate using various protocols (e.g., non-access stratum (NAS) protocol). The network interface 1301 may also be referred to, for convenience of description or depending on implementation, as communication circuitry, network interface circuitry, or a communication interface circuitry.

[0389] The processor 1302 may control general operations of the network entity 1300 according to embodiments of the disclosure. The processor 1302 may be implemented by one or more integrated circuit (or circuitry) (IC) chips and may execute various data processing operations. The processor 1302 may include at least one electric circuit, and may execute instructions (or a program, codes, data, etc.) stored in the memory 1303, individually, collectively or in any combination thereof. Further, the processor 1302 may include a single-core processor or multi-core processor, and may include a processor assembly including a plurality of processing circuits (circuitry) according to a specific implementation scheme. Further, it should be noted that, according to another embodiment, in a case where NF is implemented in the form of an instance, the network function may be not necessarily configured by physical hardware.

[0390] According to an embodiment, the processor 1302 may be electrically, operatively, and / or communicatively coupled to the network interface 1301 to control the network interface 1301.

[0391] The processor 1302 may include at least one processor (or processing circuitry), and the at least one processor may perform the following operations individually, collectively or in any combination thereof. In a specific embodiment, at least a part of the processor 1302 may be included in one chip (or IC) and the other part of the processor 1302 may be included in another chip (or IC). Otherwise, at least one processor may be included in another component, for example, the network interface 1301 or the memory 1303.

[0392] The processor 1302 may perform or control or cause an operation of the network entity 1300 for executing at least one or a combination of methods according to embodiments of the disclosure. For example, the processor 1302 may control operations of the network entity 1300 for exchanging a control plane message or a user plane message with a UE, a BS, or other core network entities through wireless or wired communication, using various protocols (e.g., NAS protocol). To this end, the processor 1302 may execute a computer program, codes, or instructions stored in the memory 1303, so as to control other components of the network entity 1300 to enable execution of various operations.

[0393] The memory 1303 corresponds to a hardware storage device capable of temporarily or permanently storing information and may include one or more storage media. For example, the memory 1303 may include a memory assembly including one or more storage media. For example, the one or more storage media may include permanent memory, such as a hard drive, flash memory, or read-only memory (ROM), semipermanent memory, such as random access memory (RAM), cache memory, or a combination thereof.

[0394] The memory 1303 may be electrically, operatively, and / or communicatively coupled to the processor 1302 and may be accessed by the processor 1302.

[0395] The memory 1303 may store a computer program, codes, or instructions executable by the processor 1302. According to an embodiment, a computer program, codes, or instructions executable by the processor 1302 may be either stored in a single memory device or separated and distributedly stored in two or more memory devices. By executing the instructions stored in the memory 1303, the processor 1302 may perform various functions according to an embodiment of the disclosure.

[0396] According to an embodiment of the disclosure, operations of the network entity 1300 may be caused to be performed based on execution of instructions (or a computer program or codes) stored in the memory 1303 by at least one processor (or processing circuitry) configured to execute the same individually, collectively, or in any combination thereof, based on processing circuitry that is not configured to execute instructions, and / or based on components of processing circuitry that is not configured to execute instructions.

[0397] The illustrated steps are set out to explain the exemplary embodiments shown, and it should be anticipated that ongoing technological development will change the manner in which particular functions are performed. These examples are presented herein for purposes of illustration, and not limitation. Further, the boundaries of the functional building blocks have been arbitrarily defined herein for the convenience of the description. Alternative boundaries can be defined so long as the specified functions and relationships thereof are appropriately performed. Alternatives (including equivalents, extensions, variations, deviations, etc., of those described herein) will be apparent to persons skilled in the relevant art(s) based on the teachings contained herein. Such alternatives fall within the scope and spirit of the disclosed embodiments. Also, the words "comprising," "having," "containing," and "including," and other similar forms are intended to be equivalent in meaning and be open ended in that an item or items following any one of these words is not meant to be an exhaustive listing of such item or items or meant to be limited to only the listed item or items or items. It must also be noted that as used herein, the singular forms “a,” “an,” and “the” include plural references unless the context clearly dictates otherwise.

[0398] Finally, the language used in the specification has been principally selected for readability and instructional purposes, and it may not have been selected to delineate or circumscribe the inventive subject matter. Accordingly, the embodiments of the disclosure are intended to be illustrative, but not limiting, of the scope of the disclosure.

[0399] Meanwhile, although specific embodiments of the present disclosure have been described in detail, various modifications may be made without departing from the scope of the present disclosure. Therefore, the scope of the present disclosure should not be limited to the described embodiments, but should be defined by the claims and equivalents thereof.

Claims

1.A method performed by a sensing function, the method comprising:receiving, from a network entity, a sensing service request comprising target sensing service area information;obtaining, from an operations, administration, and maintenance (OAM) entity, sensing entity information;selecting at least one sensing entity based on at least one of the sensing service request or the sensing entity information; andtransmitting, to the selected at least one sensing entity, at least one sensing parameter,wherein the sensing function is selected by the network entity via a network repository function (NRF) based on the target sensing service area information.2.The method of claim 1, further comprising:registering to the NRF with a network function (NF) profile comprising supported sensing service area information.3.The method of claim 1,wherein the network entity is a trusted application function (AF) or a network exposure function (NEF).4.The method of claim 1, further comprising:selecting an access and mobility function (AMF) associated with the selected at least one sensing entity.5.The method of claim 4,wherein the at least one sensing parameter is transmitted to the selected at least one sensing entity via the selected AMF.6.A method performed by a network entity, the method comprising:transmitting, to a network repository function (NRF), sensing function discovery information comprising target sensing service area information;receiving, from the NRF, information of at least one sensing function corresponding to the target sensing service area information;selecting a sensing function among the at least one sensing function; andtransmitting, to the selected sensing function, a sensing service request comprising the target sensing service area information.7.The method of claim 6,wherein the network entity is a trusted application function (AF) or a network exposure function (NEF).8.The method of claim 6,wherein the selected sensing function is registered to the NRF with a network function (NF) profile comprising supported sensing service area information.9.A sensing function comprising:at least one transceiver;at least one processor communicatively coupled to the at least one transceiver; andat least one memory, communicatively coupled to the at least one processor, storing instructions executable by the at least one processor individually or in any combination to cause the sensing function to:receive, from a network entity, a sensing service request comprising target sensing service area information,obtain, from an operations, administration, and maintenance (OAM) entity, sensing entity information,select at least one sensing entity based on at least one of the sensing service request or the sensing entity information, andtransmit, to the selected at least one sensing entity, at least one sensing parameter,wherein the sensing function is selected by the network entity via a network repository function (NRF) based on the target sensing service area information.10.The sensing function of claim 9,wherein the instructions further cause the sensing function to register to the NRF with a network function (NF) profile comprising supported sensing service area information.11.The sensing function of claim 9,wherein the network entity is a trusted application function (AF) or a network exposure function (NEF).12.The sensing function of claim 9,wherein the instructions further cause the sensing function to select an access and mobility function (AMF) associated with the selected at least one sensing entity, andwherein the at least one sensing parameter is transmitted to the selected at least one sensing entity via the selected AMF.13.A network entity comprising:at least one transceiver;at least one processor communicatively coupled to the at least one transceiver; andat least one memory, communicatively coupled to the at least one processor, storing instructions executable by the at least one processor individually or in any combination to cause the network entity to:transmit, to a network repository function (NRF), sensing function discovery information comprising target sensing service area information;receive, from the NRF, information of at least one sensing function corresponding to the target sensing service area information;select a sensing function among the at least one sensing function; andtransmit, to the selected sensing function, a sensing service request comprising the target sensing service area information.14.The network entity of claim 13,wherein the network entity is a trusted application function (AF) or a network exposure function (NEF).15.The network entity of claim 13,wherein the selected sensing function is registered to the NRF with a network function (NF) profile comprising supported sensing service area information.