A method and an apparatus for managing sensing parameters in a wireless communication system
The introduction of a Sensing Service Function (SSF) for managing sensing parameter configuration addresses the inefficiencies in existing systems, enabling effective execution of sensing operations and ensuring regulatory compliance and data security in wireless communication networks.
Patent Information
- Application Number
- PCT/KR2026/096398
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-05-05
- Filing Date
- 2026-04-28
- Publication Date
- 2026-11-12
AI Technical Summary
Current wireless communication systems face challenges in efficiently managing sensing operations due to the lack of effective methods for configuring and provisioning sensing parameters to sensing entities, which is crucial for supporting advanced services like 5G and 6G wireless sensing services, particularly in areas such as object detection, tracking, and environmental monitoring, while ensuring data confidentiality and compliance with regulations.
A Sensing Service Function (SSF) is introduced to manage sensing operations by configuring sensing parameters directly or indirectly through a sensing service container via an Access and Mobility Management Function (AMF) to sensing entities, enabling efficient execution of sensing operations based on received requests.
This approach enhances the capability of wireless communication networks to support advanced sensing services by ensuring proper parameter configuration, improving data security, and adhering to regulatory requirements, thereby optimizing network performance and user privacy.
Smart Images

Figure KR2026096398_12112026_PF_FP_ABST
Abstract
Description
A METHOD AND AN APPARATUS FOR MANAGING SENSING PARAMETERS IN A WIRELESS COMMUNICATION SYSTEM
[0001] This application is based on and derives the benefit of Indian Provisional Application 202541043628, the contents of which are incorporated herein by reference. Embodiments disclosed herein relate to wireless sensing service in wireless communication networks, and more particularly to methods and systems for providing one or more sensing parameters to one or more sensing entities for wireless sensing services.
[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 an application function, a sensing service request and sensing parameters associated with the sensing service request, determining at least one sensing parameter based on the sensing parameters received from the AF, and transmitting, to a sensing entity, the at least one sensing parameter.
[0009] In one embodiment, the at least one sensing parameter is transmitted to the sensing entity via an access and mobility management function (AMF).
[0010] In one embodiment, the at least one sensing parameter is included in a sensing service container.
[0011] In one embodiment, transmitting the at least one sensing parameter comprises transmitting, to the AMF, the sensing service container, an identifier of the sensing entity, and an identifier of the sensing function.
[0012] In one embodiment, the at least one sensing parameter is transmitted directly to the sensing entity.
[0013] In one embodiment, the at least one sensing parameter comprises at least one of target sensing service area information, a sensing duration, a sensing service type, a sensing key performance indicator (KPI), or an identifier of the sensing function.
[0014] In one embodiment, the sensing entity is a base station.
[0015] In one embodiment, the sensing parameters comprise at least one of target sensing service area information or a sensing key performance indicator (KPI).
[0016] In one embodiment, a method performed by a sensing entity comprises, receiving, from a sensing function, at least one sensing parameter, and acquiring sensing data based on the at least one sensing parameter, the at least one sensing parameter is determined by the sensing function based on sensing parameters associated with a sensing service request of an application function (AF).
[0017] In one embodiment, the at least one sensing parameter is received from the sensing function via an access and mobility management function (AMF), and the at least one sensing parameter is included in a sensing service container.
[0018] In one embodiment, receiving the at least one sensing parameter comprises receiving, from the AMF, the sensing service container, an identifier of the sensing entity, and an identifier of the sensing function.
[0019] In one embodiment, the at least one sensing parameter is received directly from the sensing function.
[0020] In one embodiment, a sensing function comprises, at least one processor, 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 an application function, a sensing service request and sensing parameters associated with the sensing service request, determine at least one sensing parameter based on the sensing parameters received from the AF, and transmit, to a sensing entity, the at least one sensing parameter
[0021] In one embodiment, a sensing entity comprises, at least one processor, 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 entity to receive, from a sensing function, at least one sensing parameter, and acquire sensing data based on the at least one sensing parameter, the at least one sensing parameter is determined by the sensing function based on sensing parameters associated with a sensing service request of an application function (AF).
[0022] Embodiments herein are illustrated in the accompanying drawings, throughout which like reference letters indicate corresponding parts in the various figures. The embodiments herein will be better understood from the following description with reference to the following illustrator drawings. Embodiments herein are illustrated by way of examples in the accompanying drawings, and in which:
[0023] FIG. 1 depicts a system for managing a sensing operation by a network entity in a wireless communication network, according to embodiments as disclosed herein;
[0024] FIG. 2 depicts a block diagram of the network entity, according to embodiments as disclosed herein;
[0025] FIG. 3 depicts a block diagram of a processor of a network entity or a Sensing Service Function (SSF), according to embodiments as disclosed herein;
[0026] FIG. 4 depicts a method for managing a sensing operation in a wireless communication network by the SSF, according to embodiments as disclosed herein;
[0027] FIG. 5 depicts a message sequence diagram indicating a procedure to provision the sensing parameters to the sensing entities with direct connectivity, according to embodiments as disclosed herein;
[0028] FIG. 6 depicts a message sequence diagram indicating a procedure to provision the sensing parameters to the sensing entities with indirect connectivity via an Access and Mobility Management Function (AMF), according to embodiments as disclosed herein;
[0029] FIG. 7 is a block diagram of a terminal or user equipment according to an embodiment of the disclosure;
[0030] FIG. 8 is a block diagram of a base station according to an embodiment of the disclosure; and
[0031] FIG. 9 is a block diagram of a network entity according to an embodiment of the disclosure.
[0032] Hereinafter, embodiments of the disclosure will be described in detail with reference to the accompanying drawings.
[0033] 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.
[0034] 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.
[0035] 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.
[0036] 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).
[0037] 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.
[0038] 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.
[0039] 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.
[0040] 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.
[0041] 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.
[0042] 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.
[0043] 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.
[0044] 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.
[0045] 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.
[0046] 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.
[0047] 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.
[0048] 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.
[0049] 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.
[0050] 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.
[0051] 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.
[0052] 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.
[0053] 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.
[0054] 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.
[0055] 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.
[0056] 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.
[0057] 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.
[0058] 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.
[0059] 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.
[0060] 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.
[0061] 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.
[0062] 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.
[0063] 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.
[0064] 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.
[0065] 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.
[0066] 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.
[0067] 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.
[0068] 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.
[0069] 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.
[0070] 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.
[0071] 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
[0072] 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."
[0073] 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.
[0074] 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.
[0075] 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.
[0076] Hereinafter, the operational principle of the present disclosure will be described in detail with reference to the accompanying drawings.
[0077] Fifth Generation (5G) wireless sensing is a technology enabler to acquire information about characteristics of the environment and / or objects within the environment, that uses radio waves to determine the distance (range), angle, or instantaneous linear velocity of objects, and so on. The 5G wireless sensing service relies on analyzing the transmissions, reflections, and scattering of wireless sensing signals.
[0078] 5G wireless sensing service, as part of a cellular network provides new possibilities for enhanced usage of the telecommunication infrastructure in areas of object detection and tracking, environment monitoring, and human motion monitoring. The wireless sensing service provides input to various verticals such as Unmanned Aerial Vehicles (UAVs), smart homes, Vehicle-to-Everything (V2X), factories, and so on.
[0079] The use cases examined in the report cover a wide range of applications, including:
[0080] - Object and intruder detection for smart home, on a highway, for railways, for factory, for predefined secure areas around critical infrastructure.
[0081] - Collision avoidance and trajectory tracking of UAVs, vehicles, Automated Guided Vehicles (AGVs).
[0082] - Automotive maneuvering and navigation.
[0083] - Public safety search and rescue.
[0084] - Rainfall monitoring and flooding.
[0085] - Health and sports monitoring.
[0086] Use cases focus on 5G wireless sensing, and some of the use cases could include non-3GPP type sensors (for example, Radar, camera).
[0087] 5G wireless sensing service also brings challenges related to confidentiality and privacy. There is a need to protect the sensing data from unauthorized access, interception and eavesdropping, but also to make sure there is compliance with regulation and user awareness.
[0088] Problem Definition:
[0089] In Rel 20, 3GPP SA2 WG started studying the sensing service requirement and in TR 23700-14, some 6 Key Issues were identified.
[0090] KI 1 # System Architecture to Support Sensing:This key issue will address the general system architecture and function enhancements required to provide end-to-end support for sensing. The general architecture aspects that need to be studied include any new and / or existing functions in the core network and their interactions that should be involved in providing support for sensing. Potential privacy requirements if identified will be considered for this key issue.
[0091] NOTE: Solutions for other key issues may also impact general architecture aspects covered by this key issue.
[0092] KI#2 Authorization and Revocation to Support Sensing Service:The key issue is to address the authorization and revocation for a particular sensing service, specifically:
[0093] - authorization of sensing service requests and revocation of an on-going sensing service; and
[0094] - authorization and revocation for the sensing entities if applicable.
[0095] 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:
[0096] - whether and how to perform sensing service request authorization if required, and the criteria for the sensing service request authorization, based on the requirements from TS 22.137 [2];
[0097] - whether and how to perform sensing service revocation if required, and the criteria for the revocation, based on the requirements from TS 22.137 [2];
[0098] - whether, how and which entity( / entities) performs the sensing service request authorization and sensing service revocation if required;
[0099] - 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.
[0100] For the authorization and revocation for the sensing entities if applicable, the study needs to address the following aspects:
[0101] - whether, when and which entity performs the authorization and revocation of the sensing entity( / entities);
[0102] - if needed, the granularity of the sensing entity authorization, for example, based on TS 22.137 [2];
[0103] - if needed, storage and management of the authorization information for the sensing entities.
[0104] NOTE: The authorization and revocation for the sensing entities can be related to the key issue #3 on sensing entities discovery and selection.
[0105] KI#3 Sensing Entity and Sensing Function Discovery and (Re-)Selection: This key issue aims to study how to perform the Sensing entity(ies) and Sensing Function(s) discovery and (re-)selection, in particular:
[0106] - When required, for the discovery and (re-)selection of the Sensing entity(ies), the study needs to address the following aspects:
[0107] - Which entity(ies) performs the discovery and (re-)selection of the Sensing entity(ies);
[0108] - What the information and / or criteria are taken into account for the discovery and (re-)selection of the Sensing entity(ies); and
[0109] - The procedure(s) for the discovery and (re-)selection of the Sensing entity(ies).
[0110] - When required, for the discovery and (re-)selection of the Sensing Function(s), the study needs to address the following aspects:
[0111] - Which entity(ies) performs the discovery and (re-)selection of Sensing Function(s);
[0112] - What the information and / or criteria are taken into account for the discovery and (re-)selection of Sensing Function(s); and
[0113] - The procedure(s) for the discovery and (re-)selection of the Sensing Function(s).
[0114] KI#4 Sensing Data and the Associated Information Collection and Transport:Integration of sensing and communication requires 3GPP network to collect and transfer sensing data and the associated information to a Sensing Function.
[0115] This Key Issue aims to study:
[0116] - How to collect sensing data (and the associated information, if any) for sensing result generation?
[0117] - Which Sensing Function performs sensing result generation?
[0118] - Whether and what the above associated information is required for sensing result generation
[0119] NOTE: Implications to RAN or RAN dependent aspects will be coordinated with RAN WGs.
[0120] KI#5 Sensing Result Exposure:This key issue addresses the exposure of sensing results to support sensing services. The aspects to be studied in this key issue include:
[0121] - 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.
[0122] - How the Core Network exposes sensing results to the sensing service consumer (e.g., one time, periodic or event trigger).
[0123] KI#6: Configuration and Parameter Provisioning of Sensing Entities:This Key Issue will study how parameter provisioning of sensing entities is performed.
[0124] In particular, this Key Issue will study: How and what parameters need to be exchanged between the sensing entities and the core network.
[0125] NOTE: This KI needs to be aligned with RAN WGs.
[0126] Hence, there is a need in the art for solutions which will overcome the above-mentioned drawback(s), among others.
[0127] The principal object of the embodiments herein is to disclose methods and systems for managing a sensing operation in a wireless communication network by configuring one or more sensing parameters to one or more sensing entities.
[0128] Another object of embodiments herein is to disclose a Sensing Service Function (SSF) for sending the sensing parameters directly to the sensing entities in case of a direct connection between the SSF and the sensing entities.
[0129] Another object of embodiments herein is to disclose an SSF for sending the sensing parameters indirectly to the sensing entities over a sensing service container via an Access and Mobility Management Function (AMF).
[0130] Accordingly, the embodiments herein provide a method for managing a sensing operation in a wireless communication network by a network entity. The method includes receiving a sensing service request from at least one Application Function (AF). The sensing service request comprises at least one sensing service requirement. Thereafter, the method includes sending a configuration of one or more sensing parameters one of directly, and indirectly to one or more sensing entities, on receiving the sensing service request.
[0131] Accordingly, the embodiments herein provide a network entity which comprises a processor, a network interface, and a memory module. The processor is coupled with the network interface and the memory module. The processor is configured to receive a sensing service request from at least one AF. Further, the processor is configured to send a configuration of one or more sensing parameters one of directly, and indirectly to one or more sensing entities, on receiving the sensing service request.
[0132] In one embodiment, a method (400) for managing a sensing operation in a wireless communication network comprises, receiving, by a network entity (102), a sensing service request from at least one Application Function (AF) (104), the sensing service request comprises at least one sensing service requirement, and sending, by the network entity (102), a configuration of one or more sensing parameters one of directly, and indirectly to one or more sensing entities (106), on receiving the sensing service request.
[0133] In one embodiment, the network entity (102) is a Sensing Service Function (SSF), the SSF receives the sensing service request directly from the AF (104) if the AF (104) is a trusted domain, the SSF receives the sensing service request from the AF (104) via a Network Exposure Function (NEF) if the AF (104) is not the trusted domain.
[0134] In one embodiment, the at least one sensing service requirement comprises at least one of a target sensing service area, and a sensing Quality of Service (QoS).
[0135] In one embodiment, the one or more sensing entities (106) comprises at least one of one or more gNBs, and one or more User Equipment (UEs).
[0136] In one embodiment, the one or more sensing parameters comprises at least one of a type of sensing service operation, the target sensing service area, a sensing service duration, a type of sensing data reporting, a sensing Key Performance Indicator (KPI), a Next-Generation Radio Access Network (NG-RAN) Identifier (ID), and an SSF ID.
[0137] In one embodiment, the method (400) of sending the configuration of the one or more sensing parameters to the one or more selected sensing entities (106) directly, comprises deriving, by the network entity (102), the one or more sensing parameters based on the at least one sensing service requirement from the received sensing service request, and sending, by the network entity (102), the configuration of the one or more derived sensing parameters directly to the one or more sensing entities (106) for performing execution of at least one sensing operation.
[0138] In one embodiment, the method (400) of sending the configuration of the one or more sensing parameters to the one or more selected sensing entities (106) indirectly, comprises deriving, by the network entity (102), the one or more sensing parameters based on the at least one sensing service requirement from the received sensing service request, and creating, by the network entity (102), a sensing service container for the one or more derived sensing parameters, and sending, by the network entity (102), the created sensing service container including the one or more sensing parameters indirectly to the one or more sensing entities (106) via an Access and Mobility Management Function (AMF) for performing execution of at least one sensing operation, the network entity (102) includes at least one of the type of sensing service operation, the target sensing service area, the sensing service duration, the type of sensing data reporting, and the sensing KPI inside the sensing service container, the network entity (102) sends at least one of the NG-RAN ID and the SSF ID outside the sensing service container.
[0139] In one embodiment, a network entity (102), comprises, a processor (204), a network interface (202), and a memory module (206), the processor (204) is coupled with the network interface (202) and the memory module (206), and is configured to receive a sensing service request from at least one Application Function (AF) (104), the sensing service request comprises at least one sensing service requirement, and send a configuration of one or more sensing parameters one of directly, and indirectly to one or more sensing entities (106), on receiving the sensing service request.
[0140] In one embodiment, the network entity (102) is a Sensing Service Function (SSF), the SSF receives the sensing service request directly from the AF (104) if the AF (104) is a trusted domain, the SSF receives the sensing service request from the AF (104) via a Network Exposure Function (NEF) if the AF (104) is not the trusted domain.
[0141] In one embodiment, the at least one sensing service requirement comprises at least one of a target sensing service area, and a sensing Quality of Service (QoS).
[0142] In one embodiment, the one or more sensing entities (106) comprises at least one of one or more gNBs, and one or more User Equipment (UEs).
[0143] In one embodiment, the one or more sensing parameters comprises at least one of a type of sensing service operation, the target sensing service area, a sensing service duration, a type of sensing data reporting, a sensing Key Performance Indicator (KPI), a Next-Generation Radio Access Network (NG-RAN) Identifier (ID), and an SSF ID.
[0144] In one embodiment, the processor (204) is configured to derive the one or more sensing parameters based on the at least one sensing service requirement from the received sensing service request, and send the configuration of the one or more derived sensing parameters directly to the one or more sensing entities (106) for performing execution of at least one sensing operation. The network entity (102) as claimed in claim 8, the processor (204) is configured to derive the one or more sensing parameters based on the at least one sensing service requirement from the received sensing service request, and create a sensing service container for the one or more derived sensing parameters, and send the created sensing service container including the one or more sensing parameters indirectly to the one or more sensing entities (106) via an Access and Mobility Management Function (AMF) for performing execution of at least one sensing operation, the network entity (102) includes at least one of the type of sensing service operation, the target sensing service area, the sensing service duration, the type of sensing data reporting, and the sensing KPI inside the sensing service container, the network entity (102) sends at least one of the NG-RAN ID and the SSF ID outside the sensing service container.
[0145] These and other aspects of the example embodiments herein will be better appreciated and understood when considered in conjunction with the following description and the accompanying drawings. It should be understood, however, that the following descriptions, while indicating example embodiments and numerous specific details thereof, are given by way of illustration and not of limitation. Many changes and modifications may be made within the scope of the example embodiments herein without departing from the spirit thereof, and the example embodiments herein include all such modifications.
[0146] The embodiments herein disclose methods and systems for providing one or more sensing parameters applicable to sensing entities so that sensing entities can start executing at least one sensing operation based on the received sensing parameters. Referring now to the drawings, and more particularly to FIGS. 1 through 6, where similar reference characters denote corresponding features consistently throughout the figures, there are shown embodiments.
[0147] FIG. 1 depicts a system 100 for managing a sensing operation by a network entity in a wireless communication network. The system 100 comprises the network entity 102, one or more Application Functions (AFs) 104, and one or more sensing entities 106.
[0148] The structure of the above-described network entity 102 will be described in more detail with reference to the drawings.
[0149] FIG. 2 depicts a block diagram of the network entity 102, according to an embodiment of the disclosure.
[0150] In an embodiment herein, the network entity 102 may include an entity (apparatus, device, or server, etc.) that performs one or more sensing operations or a part of a sensing operation constituting a core network (e.g., a 5th generation (5G) core (5GC)) in a communication system.
[0151] In an embodiment herein, the network entity 102 is a Sensing Service Function (SSF). The SSF 102 is responsible for configuring the sensing parameters to the sensing entities 106 who is responsible for starting measurement of sensing operation. Henceforth, the network entity 102 can be interchangeably used as SSF 102 in the entire description.
[0152] Sensing Service Function (SSF): The SSF 102 is a new Network Function (NF) introduced to the 5GC. The SSF 102 can receive a sensing service request from at least one AF 104. In an embodiment herein, the SSF 102 can receive the sensing service request directly from the AF 104 if the AF 104 is a trusted domain. In an embodiment herein, the SSF 102 can receive the sensing service request from the AF 104 via a Network Exposure Function (NEF) if the AF 104 is not the trusted domain. The SSF 102 can authorize the AF's sensing service request by retrieving the AF authorization data present in a sensing profile function before accepting the request. For example, when a sensing service request is initiated by the AF 104, authorization of the AF's 104 sensing service request shall be performed. The AF authorization profile for the sensing service is stored in the sensing profile function, which is used to authorize whether the request from the AF's sensing service is allowed. If the sensing service request can be fulfilled and authorized, then the SSF 102 can accept the request and invoke sensing function and sensing entities 106 for further processing like configuring parameters to the sensing entities 106. The SSF 102 is also responsible for collecting sensing data and any contextual information from the sensing entities 106, and calculating the sensing results. The sensing results later will be shared with the AF 104.
[0153] Sensing Entities (SE): Sensing entities 106 such as UE and / or Next-Generation Radio Access Network (NG-RAN) if have capability to provide the sensing service may receive the sensing parameters from an Access and Mobility Management Function (AMF) or the SSF 102 to start sensing the target object, and provide sensing data upon finishing it as per the received request.
[0154] Referring to FIG. 2, the network entity 102 may include at least one network interface 202, at least one processor 204 (hereinafter, "processor"), and at least one memory module 206 (hereinafter, "memory"). As described above, the SSF 102 may be implemented in the form of a physical device such as the network entity 102, or may be virtualized and executed in the form of an instance. When implemented as an instance, the SSF 102 need not necessarily include physical components as illustrated in FIG. 2. In such a case, the instance may be logically represented as comprising one or more logical functional elements.
[0155] According to at least one or a combination of methods corresponding to the embodiments described in the present disclosure, the network interface 202, the processor 204, and the memory module 206 of the network entity 102 may operate. However, components of the network entity 102 are not limited to the example components illustrated in FIG. 2. In another embodiment, the network entity 102 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 202, the processor 204, or the memory module 206 may be integrated in the form of one component.
[0156] The network interface 202 is a collective term for a transmitter part of the network entity 102 and a receiver part of the network entity 102, and may be a communication circuit for transmitting or receiving a signal to or from a terminal, 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 202 may include a circuit, logic, hardware, etc., configured to exchange a control plane message or a user plane message with a terminal, a BS, or other core network entities through wireless communication or wired communication. The network interface 202 may operate using various protocols (e.g., non-access stratum (NAS) protocol). The network interface 202 may also be referred to, for convenience of description or depending on implementation, as communication circuitry, network interface circuitry, or a communication interface circuitry.
[0157] The processor 204 may control general operations of the network entity 102 according to embodiments of the disclosure. The processor 204 may be implemented by one or more integrated circuit (or circuitry) (IC) chips and may execute various data processing. The processor 204 may include at least one electric circuit, and may execute instructions (or a program, codes, data, etc.) stored in the memory module 206, individually, collectively or in any combination thereof. Further, the processor 204 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.
[0158] According to an embodiment, the processor 204 may be electrically, operatively, and / or communicatively coupled to the network interface 202 to control the network interface 202.
[0159] The processor 204 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 204 may be included in one IC and the other part of the processor 204 may be included in another IC. Otherwise, at least one processor may be included in another component, for example, the network interface 202 or the memory module 206.
[0160] The processor 204 may perform or control or cause an operation of the network entity 102 for executing at least one or a combination of methods according to embodiments of the disclosure. For example, the processor 204 may control operations of the network entity 102 for exchanging a control plane message or a user plane message with a terminal, a BS, or other core network entities through wireless or wired communication, using various protocols (e.g., NAS protocol). To this end, the processor 204 may execute a computer program, codes, or instructions stored in the memory module 206, so as to control other components of the network entity 102 to enable execution of various operations.
[0161] The processor 204 can further comprise a configuration module 302, as depicted in FIG. 3.
[0162] In an embodiment herein, the configuration module 302 can receive a sensing service request from at least one AF 104. The sensing service request can include at least one sensing service requirement. The sensing service requirement can include, but not limited to a target sensing service area, and a sensing Quality of Service (QoS). The configuration module 302 can send a configuration of one or more sensing parameters one of directly, and indirectly to the sensing entities 106, on receiving the sensing service request for performing execution of at least one sensing operation. The sensing parameters can include, but not limited to a type of sensing service operation, the target sensing service area, a sensing service duration, a type of sensing data reporting, a sensing Key Performance Indicator (KPI), an NG-RAN Identifier (ID), and an SSF ID. The sensing entities 106 can include, but not limited to one or more gNBs, and one or more User Equipment (UEs).
[0163] Configuration of sensing parameter at sensing entities 106: Upon successful discovery and selection of the sensing entities 106 (i.e., NG-RAN and UE), the SSF 102 shall provide the sensing parameters for the sensing entities 106 to start executing the sensing operation.
[0164] In an embodiment herein, the configuration module 302 can derive the sensing parameters based on the sensing service requirement from the received sensing service request. The configuration module 302 can update sensing parameters using additional parameters based on the derived sensing parameters in accordance with the sensing service request. The configuration module 302 can send the configuration of the derived sensing parameters directly to the sensing entities 106 for performing execution of at least one sensing operation.
[0165] In an embodiment herein, the configuration module 302 can create a sensing service container for the derived sensing parameters. The configuration module 302 can send the created sensing service container including the sensing parameters indirectly to the sensing entities 106 via an AMF for performing execution of at least one sensing operation. In this case, the configuration module 302 can include at least one of the type of sensing service operation, the target sensing service area, the sensing service duration, the type of sensing data reporting (for example, one time or periodic), and the sensing KPI inside the sensing service container. The configuration module 302 can send at least one of the NG-RAN ID, and the SSF ID outside the sensing service container.
[0166] The memory module 206 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 module 206 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.
[0167] The memory module 206 may be electrically, operatively, and / or communicatively coupled to the processor 204 and may be accessed by the processor 204.
[0168] The memory module 206 may store a computer program, codes, or instructions executable by the processor 204. According to an embodiment, a computer program, codes, or instructions executable by the processor 204 may be either stored in a single memory device or separated and stored in a distributed manner in two or more memory devices. By executing the instructions stored in the memory module 206, the processor 204 may perform various functions according to an embodiment of the disclosure.
[0169] According to an embodiment of the disclosure, operations of the network entity 102 may be caused to be performed based on execution of instructions (or a computer program or codes) stored in the memory module 206 by at least one processor (or processing circuitry) 204 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.
[0170] FIG. 4 depicts a method 400 for managing a sensing operation in a wireless communication network by the SSF 102. The method 400 comprises receiving a sensing service request including a sensing service requirement from at least one AF 104, as depicted in step 402. Thereafter, the method 400 comprises sending a configuration of sensing parameters one of directly, and indirectly to one or more sensing entities 106, as depicted in step 404, on receiving the sensing service request for performing execution of at least one sensing operation.
[0171] The various actions in method 400 may be performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some actions listed in FIG. 4 may be omitted.
[0172] NG-RAN (Rx / Tx): In case of NG-RAN, there are two ways of configuring the sensing parameters by the SSF 102.
[0173] In the first approach, there will be direct connectivity between the SSF 102 to the NG-RAN 504. In this case, the SSF 102 provides all the sensing parameters received from the NEF or trusted AF 104 like type of sensing service operation (for example, objection detection and tracking, environment monitoring, and motion monitoring), a target sensing service area, a sensing duration, a sensing KPI, and an SSF ID to the NG-RAN 504.
[0174] In the second approach, there will be indirect connectivity where the SSF 102 can provision the sensing parameters to the NG-RAN 504 via the AMF 506. In this case, it is proposed to introduce one new sensing service container, within which all the sensing parameters will be provided. Outside the sensing service container, the SSF 102 can provide the NG-RAN ID, and the SSF ID to the AMF 506.
[0175] UE (Rx / Tx): In case of UE, there are two ways of configuring the sensing parameters by the SSF 102.
[0176] In the first approach, there will be direct connectivity between the SSF 102 to the UE 502. In this case, the SSF 102 can provide all the sensing parameters received from the NEF or trusted AF like type of sensing service operation (for example, objection detection and tracking, environment monitoring, and motion monitoring), a target sensing service area, a sensing duration, a sensing KPI, and an SSF ID to the UE 502.
[0177] In the second approach, there will be indirect connectivity where the SSF 102 can provision the sensing parameters to the UE 502 via the AMF 506. In this case, it is proposed to introduce one new sensing service container, within which all the sensing parameters can be provided. Outside the container, the SSF 102 can provide the Subscription Permanent Identifier SUPI, and the SSF ID to the AMF 506.
[0178] To fulfil the delivery of sensing parameters, the AMF 506 shall provide a new service operation as defined below.
[0179] Namf_SS_ParameterDelivery service operation:
[0180] Service operation name: Namf_SS_ParameterDelivery
[0181] Description: The NF consumer (e.g. SSF 102) requests to send sensing parameters data (i.e., objection detection and tracking, environment monitoring, motion monitoring, AF ID, target sensing service area, sensing duration, sensing KPI) towards NG-RAN 504 or UEs 502.
[0182] Inputs Required:
[0183] 1) Sensing parameters to deliver to NG-RAN or UE.
[0184] 2) NG-RAN ID.
[0185] 3) SUPI
[0186] 4) SSF ID
[0187] Outputs Required: Sensing data received from NG-RAN 504 or UE 502, result indication (success or failure), failure cause in case of failure.
[0188] Namf_SS_Notify service operation:
[0189] Service operation name: Namf_SS_Notify
[0190] Description: The NF consumer requests to receive the sensing data from sensing entities (i.e. NG-RAN 504 or UE 502) 106. If the NF consumer invokes the Namf_SS_ParameterDelivery, the NF consumer implicitly subscribes to receive the sensing data from the sensing entities 106.
[0191] Inputs Required:
[0192] 1) Sensing data messages received from sensing entities.
[0193] Input Optional:None.
[0194] Outputs, Required: Operation execution result indication.
[0195] Output, Optional: None.
[0196] FIG. 5 depicts a message sequence diagram 500 indicating a procedure to provision the sensing parameters to the sensing entities 106 with direct connectivity.
[0197] As depicted in step 5-1, the SSF 102 discovers NG-RAN(s) 504, and provides all the sensing parameters it receives from the NEF or trusted AF, like sensing service operation (e.g. objection detection and tracking, environment monitoring, motion monitoring), target sensing service area, sensing duration, sensing KPI, and SSF ID.
[0198] As depicted in step 5-2, the SSF 102 discovers UE(s) 502 and provide all the sensing parameters it receives from the NEF or trusted AF, like sensing service operation (e.g. objection detection and tracking, environment monitoring, motion monitoring), target sensing service area, sensing duration, sensing KPI, and SSF ID.
[0199] As depicted in step 5-3, the NG-RAN(s) 504 acknowledges about receiving the parameters to the SSF 102.
[0200] As depicted in step 5-4, the UE(s) 502 acknowledges about receiving the parameters to the SSF 102.
[0201] The various actions in method 500 may be performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some actions listed in FIG. 5 may be omitted.
[0202] FIG. 6 depicts a message sequence diagram 600 indicating a procedure to provision the sensing parameters to the sensing entities 106 with indirect connectivity via AMF 506.
[0203] As depicted in step 6-1, the SSF 102 discovers the AMF(s) 506, and provides the sensing parameters received from the NEF or AF (i.e., sensing service container) along with NG-RAN ID, and SSF ID by invoking Namf_SS_ParameterDelivery service operation message.
[0204] As depicted in step 6-2, the AMF(s) 506 provides the received sensing parameters from the SSF 102 to the NG-RAN(s) 504.
[0205] As depicted in step 6-3, the NG-RAN 504 acknowledges to the AMF 506.
[0206] As depicted in step 6-4, the AMF 506 provides the received sensing parameters from the SSF 102 to the UE 502.
[0207] As depicted in step 6-5, the AMF 506 provides all the sensing data receives from sensing entities (i.e., NG-RAN 504 and / or UE 502) to the SSF 102 in Namf_SS_Notify service operation message.
[0208] The various actions in method 600 may be performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some actions listed in FIG. 6 may be omitted.
[0209] FIG. 7 is a block diagram of a terminal or user equipment (UE) 700 according to an embodiment of the disclosure.
[0210] 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.
[0211] Referring to FIG. 7, the UE 700 may include at least one transceiver (hereinafter, referred to as simply "transceiver") 701, at least one processor (hereinafter, referred to as simply "processor") 702, and at least one memory (hereinafter, referred to as simply "memory") 703. According to at least one or a combination of methods corresponding to the embodiments described in the present disclosure, the transceiver 701, the processor 702, and the memory 703 of the UE 700 may operate. However, components of the UE 700 are not limited to the example components illustrated in FIG. 7. In another embodiment, the UE 700 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 701, the processor 702, or the memory 703 may be integrated in the form of one component.
[0212] The transceiver 701 may be a communication circuit or communication circuitry that enables the UE 700 to perform wireless communication with a node or an entity of a network. For example, the transceiver 701 may enable the UE 700 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 701 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 (701) may include all subsequent generations of evolved wireless communications.
[0213] According to an embodiment, the UE 700 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 700 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 700 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 700 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).
[0214] According to an embodiment, the transceiver 701 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 701 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 701 may output a signal received through a wireless channel to the processor 702 and may transmit, through a wireless channel, a signal output from the processor 702.
[0215] The processor 702 may control general operations of the UE 700 according to embodiments of the disclosure. The processor 702 may be implemented by one or more integrated circuit (or circuitry) (IC) chips and may execute various data processing operations. The processor 702 may include at least one electric circuit, and may execute instructions (or a program, codes, data, etc.) stored in the memory 703, individually, collectively or in any combination thereof. Further, the processor 702 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.
[0216] The processor 702 may be electrically, operatively, and / or communicatively coupled to the transceiver 701 to control the transceiver 701.
[0217] The processor 702 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 702 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 702 may be included in one chip (or IC) and the other part of the processor 702 may be included in another chip (or IC). Otherwise, at least one processor may be included in another component, for example, the transceiver 701 or the memory 703.
[0218] The processor 702 may perform or control or cause an operation of the UE 700 for executing at least one or a combination of methods according to embodiments of the disclosure. For example, the processor 702 may control operations of the UE 700 for processing a downlink signal received from a BS or generating and transmitting an uplink signal to a BS. To this end, the processor 702 may execute a computer program, codes, or instructions stored in the memory 703, so as to control other components of the UE 700 to enable execution of various operations.
[0219] The memory 703 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 703 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.
[0220] The memory 703 may be electrically, operatively, and / or communicatively coupled to the processor 702 and may be accessed by the processor 702.
[0221] The memory 703 may store a computer program, codes, or instructions executable by the processor 702. According to an embodiment, a computer program, codes, or instructions executable by the processor 702 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 703, the processor 702 may perform various functions according to an embodiment of the disclosure.
[0222] According to an embodiment of the disclosure, operations of the UE 700 may be caused to be performed based on execution of instructions (or a computer program or codes) stored in the memory 703 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.
[0223] FIG. 8 is a block diagram of a base station (BS) 800 according to an embodiment of the disclosure.
[0224] The BS 800 may perform wireless communication with at least one user equipment (UE) located within the area of the BS 800 through a wireless channel. The BS 800 may perform communication with a node or an entity of a network through wired or wireless communication.
[0225] Referring to FIG. 8, the BS 800 may include at least one transceiver (hereinafter, referred to as simply "transceiver") 801, at least one processor (hereinafter, referred to as simply "processor") 802, and at least one memory (hereinafter, referred to as simply "memory") 803. According to at least one or a combination of methods corresponding to the embodiments described in the present disclosure, the transceiver 801, the processor 802, and the memory 803 of the BS 800 may operate. However, components of the BS 800 are not limited to the example components illustrated in FIG. 8. In another embodiment, the BS 800 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 801, the processor 802, or the memory 803 may be integrated in the form of one component.
[0226] The transceiver 801 may be a communication circuit or communication circuitry that enables the BS 800 to perform wireless communication with a node or an entity of a network. For example, the transceiver 801 may enable the BS 800 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 801 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 (801) may include all subsequent generations of evolved wireless communications.. According to an embodiment, the transceiver 801 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 801 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 801 may output a signal received through a wireless channel to the processor 802 and may transmit, through a wireless channel, a signal output from the processor 802.
[0227] Meanwhile, according to an embodiment of the present disclosure, the BS 800 may perform communication with a node or an entity of a network through wired or wireless communication. For example, the BS 800 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. 8, when the BS 800 performs wired communication, the BS 800 may further include a separate network interface for wired communication in addition to the transceiver 801. The network interface may be referred to as network interface circuitry or communication interface circuitry.
[0228] The processor 802 may control general operations of the BS 800 according to embodiments of the disclosure. The processor 802 may be implemented by one or more integrated circuit (or circuitry) (IC) chips and may execute various data processing operations. The processor 802 may include at least one electric circuit, and may execute instructions (or a program, codes, data, etc.) stored in the memory 803, individually, collectively or in any combination thereof. Further, the processor 802 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.
[0229] The processor 802 may be electrically, operatively, and / or communicatively coupled to the transceiver 801 to control the transceiver 801.
[0230] The processor 802 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 802 may be included in one chip (or IC) and the other part of the processor 802 may be included in another chip (or IC). Otherwise, at least one processor may be included in another component, for example, the transceiver 801 or the memory 803.
[0231] The processor 802 may perform or control or cause an operation of the BS 800 for executing at least one or a combination of methods according to embodiments of the disclosure. For example, the processor 802 may control operations of the BS 800 for generating and transmitting a downlink signal to a UE or processing an uplink signal received from a UE. Otherwise, the BS 800 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 802 may execute a computer program, codes, or instructions stored in the memory 803, so as to control other components of the BS 800 to enable execution of various operations.
[0232] The memory 803 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 803 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.
[0233] The memory 803 may be electrically, operatively, and / or communicatively coupled to the processor 802 and may be accessed by the processor 802.
[0234] The memory 803 may store a computer program, codes, or instructions executable by the processor 802. According to an embodiment, a computer program, codes, or instructions executable by the processor 802 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 803, the processor 802 may perform various functions according to an embodiment of the disclosure.
[0235] According to an embodiment of the disclosure, operations of the BS 800 may be caused to be performed based on execution of instructions (or a computer program or codes) stored in the memory 803 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.
[0236] 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.
[0237] The structure of the above-described network entity will be described in more detail with reference to the drawings.
[0238] FIG. 9 is a block diagram of a network entity 900 according to an embodiment of the disclosure. The network entity 900 may correspond to the network entity illustrated in FIG. 2.
[0239] The network entity 900 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 900.
[0240] 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.
[0241] 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.
[0242] Referring to FIG. 9, the network entity 900 may include at least one network interface 901, at least one processor 902 (hereinafter, "processor"), and at least one memory 903 (hereinafter, "memory"). As described above, a NF may be implemented in the form of a physical device such as the network entity 900, 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. 9. In such a case, the instance may be logically represented as comprising one or more logical functional elements.
[0243] According to at least one or a combination of methods corresponding to the embodiments described in the present disclosure, the network interface 901, the processor 902, and the memory 903 of the network entity 900 may operate. However, components of the network entity 900 are not limited to the example components illustrated in FIG. 9. In another embodiment, the network entity 900 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 901, the processor 902, or the memory 903 may be integrated in the form of one component.
[0244] The network interface 901 is a collective term for a transmitter part of the network entity 900 and a receiver part of the network entity 900, 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 901 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 901 may operate using various protocols (e.g., non-access stratum (NAS) protocol). The network interface 901 may also be referred to, for convenience of description or depending on implementation, as communication circuitry, network interface circuitry, or a communication interface circuitry.
[0245] The processor 902 may control general operations of the network entity 900 according to embodiments of the disclosure. The processor 902 may be implemented by one or more integrated circuit (or circuitry) (IC) chips and may execute various data processing operations. The processor 902 may include at least one electric circuit, and may execute instructions (or a program, codes, data, etc.) stored in the memory 903, individually, collectively or in any combination thereof. Further, the processor 902 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.
[0246] According to an embodiment, the processor 902 may be electrically, operatively, and / or communicatively coupled to the network interface 901 to control the network interface 901.
[0247] The processor 902 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 902 may be included in one chip (or IC) and the other part of the processor 902 may be included in another chip (or IC). Otherwise, at least one processor may be included in another component, for example, the network interface 901 or the memory 903.
[0248] The processor 902 may perform or control or cause an operation of the network entity 900 for executing at least one or a combination of methods according to embodiments of the disclosure. For example, the processor 902 may control operations of the network entity 900 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 902 may execute a computer program, codes, or instructions stored in the memory 903, so as to control other components of the network entity 900 to enable execution of various operations.
[0249] The memory 903 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 903 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.
[0250] The memory 903 may be electrically, operatively, and / or communicatively coupled to the processor 902 and may be accessed by the processor 902.
[0251] The memory 903 may store a computer program, codes, or instructions executable by the processor 902. According to an embodiment, a computer program, codes, or instructions executable by the processor 902 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 903, the processor 902 may perform various functions according to an embodiment of the disclosure.
[0252] According to an embodiment of the disclosure, operations of the network entity 900 may be caused to be performed based on execution of instructions (or a computer program or codes) stored in the memory 903 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.
[0253] 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 an application function, a sensing service request and sensing parameters associated with the sensing service request;determining at least one sensing parameter based on the sensing parameters received from the AF; andtransmitting, to a sensing entity, the at least one sensing parameter.2.The method of claim 1,wherein the at least one sensing parameter is transmitted to the sensing entity via an access and mobility management function (AMF).3.The method of claim 2,wherein the at least one sensing parameter is included in a sensing service container.4.The method of claim 3,wherein transmitting the at least one sensing parameter comprises:transmitting, to the AMF, the sensing service container, an identifier of the sensing entity, and an identifier of the sensing function.5.The method of claim 1,wherein the at least one sensing parameter is transmitted directly to the sensing entity.6.The method of claim 1,wherein the at least one sensing parameter comprises at least one of target sensing service area information, a sensing duration, a sensing service type, a sensing key performance indicator (KPI), or an identifier of the sensing function.7.The method of claim 1,wherein, in case that the AF is a trusted AF, the sensing service request is received directly from the AF, andwherein, in case that the AF is not a trusted AF, the sensing service request is received from the AF via a network exposure function (NEF).8.The method of claim 1,wherein the sensing entity is a base station.9.The method of claim 1,wherein the sensing parameters comprise at least one of target sensing service area information or a sensing key performance indicator (KPI).10.A method performed by a sensing entity, the method comprising:receiving, from a sensing function, at least one sensing parameter; andacquiring sensing data based on the at least one sensing parameter,wherein the at least one sensing parameter is determined by the sensing function based on sensing parameters associated with a sensing service request of an application function (AF).11.The method of claim 10,wherein the at least one sensing parameter is received from the sensing function via an access and mobility management function (AMF), andwherein the at least one sensing parameter is included in a sensing service container.12.The method of claim 11,wherein receiving the at least one sensing parameter comprises:receiving, from the AMF, the sensing service container, an identifier of the sensing entity, and an identifier of the sensing function.13.The method of claim 10,wherein the at least one sensing parameter is received directly from the sensing function.14.A sensing function comprising:at least one processor; 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 an application function, a sensing service request and sensing parameters associated with the sensing service request,determine at least one sensing parameter based on the sensing parameters received from the AF, andtransmit, to a sensing entity, the at least one sensing parameter.15.A sensing entity comprising:at least one processor; 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 entity to:receive, from a sensing function, at least one sensing parameter, andacquire sensing data based on the at least one sensing parameter,wherein the at least one sensing parameter is determined by the sensing function based on sensing parameters associated with a sensing service request of an application function (AF).
