Method for controlling quality of service in wireless communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. According to an embodiment, a method for operating a sensing network function in a communication system supporting integrated sensing and communication (ISAC) may include: receiving a first request message for a sensing service; transmitting a second request message for requesting sensing policy data based on the first request message; and receiving a response message corresponding to the second request message and including the sensed quality of service information.

Description

Technical Field

[0001] This disclosure provides a method for controlling the quality of integrated sensing and communication or combined communication and sensing services among services provided in a wireless communication system. Background Technology

[0002] Fifth-generation (5G) mobile communication technology defines a wide frequency band, enabling high transmission rates and new services. This can be achieved not only in "sub-6GHz" bands such as 3.5GHz, but also in "above 6GHz" bands known as millimeter waves, including 28GHz and 39GHz. Furthermore, 6G mobile communication technology (referred to as "super 5G systems") is being considered in terahertz bands (e.g., the 95GHz to 3THz band) to achieve transmission rates fifty times faster than 5G and ultra-low latency one-tenth that of 5G.

[0003] At the outset of 5G mobile communication technology development, to support services and meet performance requirements related to enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), and massive machine-type communication (mMTC), standardization was carried out on the following: beamforming and massive MIMO for mitigating radio wave path loss and increasing radio wave transmission distance in millimeter waves; parameter sets supporting dynamic operation for efficient utilization of millimeter wave resources and time slot formats (e.g., operating multiple subcarrier spacings); initial access technologies for supporting multi-beam transmission and broadband; definition and operation of bandwidth portions (BWP); new channel coding methods (such as low-density parity-check (LDPC) codes for large data transmissions and polar codes for highly reliable transmission of control information); L2 preprocessing; and network slicing for providing dedicated networks for specific services.

[0004] Currently, given the services that 5G mobile communication technology needs to support, discussions are underway regarding improvements and performance enhancements to the initial 5G mobile communication technology. Physical layer standardization is also underway for technologies such as Vehicle-to-Everything (V2X) for assisting autonomous vehicle driving decisions based on information sent by the vehicle regarding its location and status, enhancing user convenience; New Radio Unlicensed (NR-U) designed to comply with various regulatory requirements in unlicensed frequency bands; NR UE power saving; Non-Terrestrial Networks (NTN) for providing coverage in areas where communication with terrestrial networks is unavailable, as well as positioning.

[0005] Furthermore, standardization is underway in air interface architectures / protocols for technologies such as: Industrial Internet of Things (IIoT) to support new services through interoperability and convergence with other industries; Integrated Access and Backhaul (IAB) for nodes to provide network service area extension by supporting wireless backhaul and access links in an integrated manner; mobility enhancements including conditional handover and Dual Active Protocol Stack (DAPS) handover; and two-step random access (two-step RACH for NR) to simplify the random access process. Standardization is also underway for 5G baseline architectures (e.g., service-based architectures or service-based interfaces) for combining Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, as well as system architectures / services for Mobile Edge Computing (MEC) based on UE location reception services.

[0006] With the commercialization of 5G mobile communication systems, the number of connected devices will increase exponentially, necessitating enhanced functionality and performance of 5G mobile communication systems and integrated operation of connected devices. To this end, new research has been conducted combining the following technologies: effectively supporting extended reality (XR) such as augmented reality (AR), virtual reality (VR), and mixed reality (MR); improving 5G performance and reducing complexity by leveraging artificial intelligence (AI) and machine learning (ML); AI service support; metaverse service support; and drone communication.

[0007] Furthermore, this development of 5G mobile communication systems will serve as the foundation not only for the following developments: new waveforms for providing coverage in the terahertz band of 6G mobile communication technology; multi-antenna transmission such as full-dimensional MIMO (FD-MIMO), array antennas, and massive MIMO; metamaterial-based lenses and antennas for improving coverage of terahertz band signals; high-dimensional spatial multiplexing technology using orbital angular momentum (OAM); and reconfigurable smart surfaces (RIS), but also for the following developments: full-duplex technology for improving the frequency efficiency of 6G mobile communication technology and improving system networks; AI-based communication technologies for system optimization by leveraging satellites and artificial intelligence (AI) from the design phase and internalizing end-to-end AI support capabilities; and next-generation distributed computing technologies for achieving services at complexity levels exceeding the limitations of UE operational capabilities by utilizing ultra-high-performance communication and computing resources. Summary of the Invention

[0008] Technical issues When providing integrated sensing / communication services via wireless communication systems, a method is needed to determine, configure, and apply the corresponding quality of service (QoS). Quality control methods and devices supported in systems that only provide communication services are designed to guarantee the service transmission / reception quality of a pair of transmitting / receiving devices or a specific session. In integrated sensing / communication services, quality control for a specific session is not the primary objective, and communication quality control for a pair of transceivers is not directly related to the quality of sensing services.

[0009] Technical solution According to an embodiment, a method for operating a sensing network function in a communication system supporting Integrated Sensing and Communication (ISAC) may include: receiving a first request message for a sensing service; sending a second request message for requesting sensing policy data based on the first request message; and receiving a response message corresponding to the second request message and including sensing service quality information.

[0010] According to an embodiment, the network entity implementing sensing network functionality in a communication system supporting Integrated Sensing and Communication (ISAC) includes a transceiver and a controller. The controller can receive a first request message for sensing services, control the transmission of a second request message for requesting sensing policy data based on the first request message, and receive a response message corresponding to the second request message and including sensing service quality information.

[0011] The embodiments of this disclosure can guarantee the quality of integrated sensing / communication services provided by a wireless communication system.

[0012] Beneficial effects of the present invention This disclosure provides various methods for controlling the quality of integrated sensing and communication or combined communication and sensing services provided in a wireless communication system.

[0013] This disclosure provides key parameters that can represent the quality of integrated sensing / communication services.

[0014] This disclosure provides a method for generating, authenticating, and configuring integrated sensing / communication service quality information based on integrated sensing / communication service requests. Attached Figure Description

[0015] A more comprehensive understanding of this disclosure and its many related aspects will be more readily achieved by referring to the following detailed description and accompanying drawings, in which: Figure 1 A 5G system architecture supporting integrated sensing and communication services is illustrated according to an embodiment of the present disclosure.

[0016] Figure 2A and Figure 2BAn ISAC quality of service determination and configuration method (based on sensor network functionality) according to an embodiment of the present disclosure is illustrated.

[0017] Figure 3A and Figure 3B An ISAC service quality determination and configuration method based on PCF and sensor network functional interoperability according to embodiments of the present disclosure is illustrated.

[0018] Figure 4 A UE according to an embodiment of the present disclosure is shown.

[0019] Figure 5 A network entity according to an embodiment of this disclosure is shown. Detailed Implementation

[0020] Before proceeding with the detailed description below, it may be advantageous to define certain words and phrases used throughout this patent document: the terms “comprising” and “including” and their derivatives mean including but not limited to; the term “or” is inclusive, meaning and / or; the phrases “associated with” and “associated with” and their derivatives may mean including, being included in, interconnected with, containing, contained within, connected to or connected to, linked to or connected to, able to communicate with, cooperate with, intertwine, juxtapose, proximate, bound to or bound to, having, possessing the properties of, etc.; and the term “controller” means any device, system or part thereof that controls at least one operation, such device may be implemented in hardware, firmware or software, or some combination of at least two of these. It should be noted that the functionality associated with any particular controller can be centralized or distributed, whether local or remote.

[0021] Furthermore, the various functions described below can be implemented or supported by one or more computer programs, each computer program being formed by computer-readable program code and embodied in a computer-readable medium. The terms "application" and "program" refer to one or more computer programs, software components, instruction sets, procedures, functions, objects, classes, instances, associated data, or portions thereof suitable for implementation in appropriate computer-readable program code. The phrase "computer-readable program code" includes any type of computer code, including source code, object code, and executable code. The phrase "computer-readable medium" includes any type of medium accessible by a computer, such as read-only memory (ROM), random access memory (RAM), hard disk drive, optical disc (CD), digital video disc (DVD), or any other type of storage. "Non-transitory" computer-readable media does not include wired, wireless, optical, or other communication links that transmit transient electrical or other signals. Non-transitory computer-readable media includes media that can permanently store data and media that can store data and subsequently rewrite it, such as rewritable optical discs or erasable memory devices.

[0022] Throughout this patent document, definitions of certain words and phrases are provided, and those skilled in the art will understand that, in many (if not most) cases, such definitions apply to the prior and future use of the words and phrases defined in this way.

[0023] The following discussion Figures 1 to 5 The various embodiments used to describe the principles of this disclosure in this patent document are for illustrative purposes only and should not be construed as limiting the scope of this disclosure in any way. Those skilled in the art will understand that the principles of this disclosure can be implemented in any suitably arranged system or device.

[0024] The operating principles of this disclosure are described below with reference to the accompanying drawings. The terminology described below is defined in consideration of the functions within this disclosure. Since the terms may vary depending on the intent or habits of the user or operator, their definitions should be determined within the context of the entire disclosure.

[0025] For ease of description, terms relating to network entities or network functions and objects of wireless communication systems as used herein, terms relating to messages, and terms relating to identification information are provided as examples. Therefore, this disclosure is not limited to these terms, and these terms may be replaced by other terms representing objects having equivalent technical concepts.

[0026] While the terms and names defined in the 5G system standard are used herein for ease of description, embodiments of this disclosure are not limited thereto, and the terms and names are equally applicable to wireless communication systems conforming to other standards or next-generation standards.

[0027] Figure 1 A 5G system architecture supporting integrated sensing and communication services (e.g., referred to hereinafter as ISAC services for ease of description) according to embodiments of the present disclosure is illustrated.

[0028] 5G system architectures supporting ISAC services can include various network functions (NFs), some of which are... Figure 1 Examples shown include, for example, Access and Mobility Management Function (AMF), Session Management Function (SMF), Policy Control Function (PCF), Unified Data Management (UDM), Unified Data Repository (UDR), Data Network (DN) or a local portion of a DN capable of local access to a data network, User Plane Function (UPF), (Radio) Access Network ((R)AN), and User Equipment (UE).

[0029] Each NF supports the following functions.

[0030] -AMF provides access and mobility management functions for each UE, and each UE can essentially connect to one AMF.

[0031] -DN refers to, for example, carrier services, internet access, or third-party services. The DN sends downlink protocol data units (PDUs) to the UPF or receives PDUs sent from the UPF. The local portion of the DN refers to a data network with a short data transmission path because it can locally access a part of the DN. It can be used to represent a DN for deploying edge application servers that support edge computing services.

[0032] The PCF receives information about packet flows from the application server and provides the ability to determine policies such as mobility management or session management. Specifically, the PCF supports functions such as: supporting a single policy framework for controlling network operations, providing policy rules to allow CP functions (e.g., AMF or SMF) to enforce policy rules, and implementing a front-end for accessing subscription information related to policy decisions in the Unified Data Repository (UDR).

[0033] -SMF provides session management functionality, and if the UE has multiple sessions, this can be managed by different SMFs for each session.

[0034] -UDM stores data such as user subscription data and policy data.

[0035] The UPF transmits downlink PDUs received from the DN to the UE via the (R)AN, and uplink PDUs received from the UE to the DN via the (R)AN. The Uplink Classifier (ULCL) refers to a UPF that has the function of classifying and transmitting uplink data. The Local UPF (L-UPF) serves as the PDU session anchor for sessions sent to the local portion of the DN.

[0036] - The sensing network function is a network function that supports ISAC services. The sensing network function can receive ISAC service requests and perform at least one of the following: authentication for the corresponding request, generation and configuration of ISAC service quality control policies, discovery and selection of network devices and UEs performing sensing operations, compilation of sensing results, and processing. The above operations can be configured or implemented as a sensing service gateway / center and a sensing management function, which are two logically separate network functions. For example, when configured / implemented as logically separate network functions, the sensing service gateway / center can be centrally deployed to receive ISAC service requests and perform authentication operations, and can perform operations such as generating ISAC service quality control policies, while the sensing management function can be distributed and locally deployed to perform: discovery and selection of network devices and UEs, compilation of sensing results, and processing for performing actual sensing operations. In this disclosure, the methods for configuring the sensing network function are not limited, and embodiments in which they are integrated and configured and operated as a single function, as well as embodiments in which they are separated and operated, are all included within the scope of this disclosure.

[0037] -UEs can be classified into UEs that actually request ISAC services and UEs that are used as sensors to detect sensing targets (or simply sensing objects) to provide ISAC services in wireless communication systems.

[0038] - The base station of the (R)AN that constitutes the radio access network can perform operations as a sensor to detect objects and to send / receive signals for communication.

[0039] According to embodiments, integrated sensing / communication quality of service information can be used in wireless communication systems and external ISAC service request devices to control the quality of ISAC services. For the purpose of describing the following embodiments, ISAC service quality related information is represented as Sensing Quality of Service (SSQ) information. Sensing Quality of Service information may include at least one of the multiple pieces of information described in Table 1 below.

[0040] Table 1 contains information related to ISAC service quality (Sensing Service Quality (SSQ) information).

[0041] [Table 1]

[0042] Figure 2A and 2B An ISAC quality of service determination and configuration method (based on sensor network functionality) according to an embodiment of the present disclosure is illustrated.

[0043] refer to Figure 2AIn step 201, the UE, AF, or a standalone ISAC client may send an ISAC service request to a sensing network function (e.g., a sensing service GW / center, hereinafter referred to as "SSGC"). Request messages sent by the AF may be sent directly to the sensing network function or via the NEF. Messages sent by the UE may be sent to the sensing network function via the RAN or UPF, or via the RAN or AMF. Depending on the client's location, messages sent by a standalone ISAC client may be sent directly, via the NEF, via the RAN / UPF, or via the RAN / AMF to the sensing network function. The ISAC service request message may include information such as an identifier of the requested object (UE identifier, AF ID, or ISAC client identifier), as well as the ISAC service type, ISAC service identifier, ISAC service target area, or similar information, and Sensing Service Quality (SSQ) information indicating the required ISAC service quality information.

[0044] As an example, the Sensing Quality of Service (SSQ) information may include at least one of the information described in Table 1. Alternatively, the Sensing Quality of Service (SSQ) information may only include the Sensing Quality of Service (SSQ) index or identifier (SSQ index / identifier) ​​value. When an SSQ index / identifier is given, the sensing network function may specify the corresponding SSQ element information (at least one quality information item listed in Table 1).

[0045] As another embodiment, SSQ information can be provided for an ISAC service type or ISAC service identifier. In this case, the remaining SSQ information besides the first SSQ information can refer to alternative SSQs. Alternative SSQs can refer to SSQs that are applied sequentially instead of the highest-requested SSQ when the highest-requested SSQ may not be satisfied in the ISAC service providing system.

[0046] In step 202, a sensing network function (e.g., a sensing service GW / center, hereinafter referred to as "SSGC") may perform authentication on the sensing service requester. This authentication may be performed using the information received in step 1 and through interworking with another network function (e.g., UDM or NEF).

[0047] In step 203, after successfully authenticating the sensing service request, the sensing network function can perform operations to determine the SSQ to be applied. The sensing network function can send sensing policy data or sensing service profile request messages to the UDR. The request message may include an ISAC service requester identifier (UE identifier or AF ID), an ISAC service identifier, an ISAC service type, and the requested SSQ information (e.g., including at least one of the information in Table 1 (with the attribute name and request value of the information received in step 1) or a sensing service quality information index).

[0048] In step 204, the UDR may select and provide sensing policy data or sensing service profile information corresponding to the information received from the sensing network function. The sensing policy data or sensing service profile information may include SSQ information that the system can provide to the service requester in step 201. The SSQ information provided by the UDR may include at least one of the information described in Table 1, and each piece of information represents the ISAC quality of service previously set from the OAM or external application function.

[0049] In step 205, when the sensing network function receives an ISAC service request from the UE in step 201, the sensing network function can request and obtain the corresponding UE's sensing policy data or sensing service profile information from the UDM. The subscribed SSQ information can be included in the information provided by the UDM. The subscribed SSQ information can include at least one of the information described in Table 1, and each piece of information represents the ISAC service quality that can be provided based on the subscriber information. The operation of step 205 can be performed immediately after step 201.

[0050] In step 206, the sensing network function may consider the requested SSQ received in step 201, the SSQ obtained from the UDR, and the subscribed SSQ information obtained from the UDM to determine the SSQ to be actually applied.

[0051] According to an embodiment, when the SSQ guarantee type information received in step 201 includes the guaranteed sensing service category, if the applied SSQ information determined by the sensing network function is lower than the requested SSQ (i.e., if the requested SSQ may not be guaranteed), the sensing network function may provide the service requesting device (UE, AF, or ISAC service client) in step 201 with information indicating that the requested SSQ may not be guaranteed and indicating which specific SSQ quality may not be guaranteed.

[0052] According to another embodiment, when the SSQ guarantee type information received in step 201 includes a non-guaranteed sensing service category (or a best-effort category), if the sensing network function determines that an SSQ lower than the SSQ requested in step 201 is applied, the sensing network function can provide the determined applied SSQ information to the requesting device (UE, AF, or ISAC service client) in step 201. The sensing network function can receive confirmation of the applied SSQ from the requesting device in step 201.

[0053] In step 207, the sensing network function may provide the applied SSQ determined in the previous steps to the network function directly involved in the actual execution of sensing. According to an embodiment, the applied SSQ may be sent when providing sensing service policy information to a sensing management function capable of configuring the sensing network function.

[0054] In step 208, the sensing management function can select a network device (e.g., a sensing-enabled base station) or a UE to actually perform sensing. Multiple UEs or network devices can be selected.

[0055] In step 209, the sensing management function may send a sensing service policy, including the applied SSQ information, to the selected network device used as a sensor. The sensing service policy may include information such as the applied SSQ information, ISAC service identifier, ISAC service type, application spatial range, and application time range.

[0056] In step 210, the UE or network device used as a sensor can perform sensing operation-related configurations (radio resource allocation, non-3GPP sensing device activation, etc.) and sensing operations based on the SSQ information applied in the sensing service policy.

[0057] When performing at least one of the above operations, the sensing network function may receive ISAC service request information, including the ISAC service type or ISAC service identifier, but may not receive the element information constituting the SSQ in Table 1. The sensing network function may determine the applied SSQ itself based on its local configuration. Alternatively, as another example, when performing operation 204, the sensing network function may obtain SSQ information corresponding to the ISAC service type or ISAC service identifier from the UDR.

[0058] As described above, the sensing network function can receive SSQ information from the ISAC service requester, or it can generate the applied SSQ information during the execution of steps 203 to 205 and provide it to the device used as a sensor. When generating the applied SSQ information, SSQ information other than that indicating the highest quality SSQ can be used as alternative SSQ information.

[0059] Figure 3A and Figure 3B An ISAC quality of service determination and configuration method (based on PCF and sensor network interoperability) according to an embodiment of the present disclosure is illustrated.

[0060] refer to Figure 3A In step 301, the UE, AF, or a separate ISAC client may provide an ISAC service request to a sensing network function (e.g., a sensing service GW / center, hereinafter referred to as "SSGC"), as shown in step 201 of FIG2. The ISAC service request message may include information such as: an identifier of the requested object (UE identifier, AF ID, or ISAC client identifier), and information such as the ISAC service type, ISAC service identifier, ISAC service target area, and sensing service quality (SSQ) information indicating the required ISAC service quality information. As an example, the sensing service quality information SSQ may include at least one of the information described in Table 1. Alternatively, the sensing service quality information SSQ may only include a sensing service quality information index or identifier (SSQ index / identifier) ​​value. When an SSQ index / identifier is given, the sensing network function may specify the corresponding SSQ element information (at least one quality information item listed in Table 1).

[0061] As another embodiment, SSQ information can be provided for an ISAC service type or ISAC service identifier. In this case, the remaining SSQ information besides the first SSQ information can refer to alternative SSQs. Alternative SSQs can refer to SSQs that are applied sequentially instead of the highest-requested SSQ when the highest-requested SSQ may not be satisfied in the ISAC service providing system.

[0062] In step 302, a sensing network function (e.g., a sensing service GW / center, hereinafter referred to as "SSGC") can perform authentication on the sensing service requester. Such authentication can be performed using the information received in step 301 and by interworking with another network function (e.g., UDM or NEF).

[0063] In step 303, when the sensing network function receives an ISAC service request from the UE in step 1, the sensing network function may request and obtain the corresponding UE's sensing policy data or sensing service profile information from the UDM. The subscribed SSQ information may be included in the information provided by the UDM. The subscribed SSQ information may include at least one of the information described in Table 1, and each piece of information represents the ISAC service quality that can be provided based on the subscriber information.

[0064] In step 304, after successfully authenticating the sensing service request, the sensing network function can perform operations to determine the SSQ to be applied. The sensing network function can send sensing policy data or sensing service profile request messages (e.g., ISAC policy requests) to the PCF. The request message may include an ISAC service requester identifier (UE identifier or AF ID), an ISAC service identifier, an ISAC service type, and the requested SSQ information (e.g., including at least one of the multiple pieces of information in Table 1 (with the attribute name and request value of the information received in step 1) or a sensing service quality information index). If the sensing network function obtained subscribed SSQ information from the UDM in previous steps, the subscribed SSQ information can also be provided to the PCF. The PCF that receives and processes the SSQ-related requests from the sensing network function can be represented as a sensing management PCF or an ISAC management PCF (hereinafter referred to as "IM PCF").

[0065] In step 305, the IM PCF can provide the UDR with information received from the sensing network function and, in response, obtain sensing policy data or sensing service profile information. For example, the UDR can select sensing policy data or sensing service profile information corresponding to the ISAC service type or ISAC service identifier, ISAC requester identifier (UE identifier, AF identifier, or ISAC client identifier) ​​(which is information received from the IM PCF), and provide it to the IM PCF. The sensing policy data or sensing service profile information may include SSQ information that the system can provide to the service requester in step 301. The SSQ information provided by the UDR may include at least one of the information described in Table 1, and each piece of information represents the ISAC service quality previously set from OAM or external application functions.

[0066] In step 306, the IM PCF may consider at least one of the requested SSQ received in step 1, the subscribed SSQ information, or the SSQ obtained from the UDR to determine the SSQ to be actually applied, and may provide it to the sensing network function.

[0067] According to an embodiment, when the SSQ guarantee type information received in step 301 includes the guaranteed sensing service category, if the applied SSQ information determined by the IM PCF is lower than the requested SSQ (i.e., if the requested SSQ may not be guaranteed), the IM PCF may provide the sensing network function with information indicating that the requested SSQ may not be guaranteed and indicating which specific SSQ quality may not be guaranteed.

[0068] In step 307, the sensing network function can provide the service requesting device (UE, AF, or ISAC service client) of step 1 with information indicating that the requested SSQ may not be guaranteed and information indicating which specific SSQ quality may not be guaranteed (307-1). According to another embodiment, when the SSQ guarantee type information provided in step 1 includes a non-guaranteed sensing service category (or best-effort category) and is provided to the IM PCF, if the IM PCF determines that an SSQ lower than the requested SSQ is applied, the sensing network function can receive the determined applied SSQ information from the IM PCF and subsequently provide it to the requesting device (UE, AF, or ISAC service client) of step 1. The sensing network function can receive confirmation of the applied SSQ from the requesting device in step 301 and can provide the corresponding confirmation to the IM PCF from the sensing network function (307-2).

[0069] In step 308, the IM PCF can determine information about the ultimately applied SSQ and provide it to the sensing network function. The sensing network function can then provide the applied SSQ, determined in the previous steps, to network functions directly involved in the actual performance of sensing (e.g., a sensing management function). According to an embodiment, the applied SSQ can be sent during the provision of sensing service policy information to a sensing management function capable of configuring the sensing network function.

[0070] In step 309, the sensing management function can select a network device (e.g., a sensing-enabled base station) or a UE to actually perform sensing. Multiple UEs or network devices can be selected.

[0071] In step 310, the sensing management function may send a sensing service policy, including the applied SSQ information, to the selected network device used as a sensor. The sensing service policy may include information such as the applied SSQ information, the ISAC service identifier, the ISAC service type, the application spatial range, and the application time range.

[0072] In step 311, the UE or network device used as a sensor can perform sensing operation-related configurations (radio resource allocation, non-3GPP sensing device activation, etc.) and sensing operations based on the SSQ information applied in the sensing service policy.

[0073] exist Figures 2A to 3BIn the description, the sensing management function and sensing service GW / center constituting the sensing network function can be implemented as independent network function instances and can perform the described operations as separate network function instances. Alternatively, the sensing management function and sensing service GW / center can be implemented as independent functions and included in existing network function instances. For example, the sensing management function can be implemented as some functions of the location management function, and the sensing service GW / center can be implemented as some functions of the gateway mobile location center. Thus, when implemented as some functions of existing network functions, the operations and services provided by the sensing management function and sensing service GW / center can be defined as additional operations and additional services instances provided by existing network functions.

[0074] Figure 4 A UE according to an embodiment of the present disclosure is shown.

[0075] exist Figure 4 In some embodiments, the UE can be Figures 1 to 3B Each of the UEs or UE devices shown in the diagram.

[0076] refer to Figure 4 The UE may include a transceiver 410, a controller 420, and a storage device 430. In this disclosure, the controller may be defined as a circuit or an application-specific integrated circuit or at least one processor.

[0077] Transceiver 410 can send and receive signals to / from a base station or network entity. Transceiver 410 can use, for example, wireless communication to send / receive data to / from a base station or network entity.

[0078] According to an embodiment, controller 420 can control the overall operation of the UE. For example, controller 420 can control the signal flow between blocks to perform coupling. Figures 1 to 3B The described operation.

[0079] Storage device 430 can store at least one of the information transmitted / received via transceiver 410 and information generated via controller 420. For example, storage device 430 can store the information mentioned above. Figures 1 to 3B The information and data required for the described method.

[0080] Figure 5 A network entity according to an embodiment of this disclosure is shown.

[0081] exist Figure 5 In this embodiment, the network entity can be Figures 1 to 3B Each of the base station or network entity devices shown in the diagram. According to embodiments, the network entity can be implemented as any one of RAN, AMF, Sensing Network Function, UDR, UDM, NEF, and AF, such as Figures 1 to 3BAs shown.

[0082] refer to Figure 5 The network entity may include a transceiver 510, a controller 520, and a storage device 530. In this disclosure, the controller may be defined as a circuit or an application-specific integrated circuit or at least one processor.

[0083] Transceiver 510 can send and receive signals to / from a UE, a base station, or another network entity. Transceiver 510 can use, for example, wireless communication to send / receive data to / from a UE, a base station, or another network entity.

[0084] According to an embodiment, controller 520 can control the overall operation of network entities. For example, controller 520 can control the signal flow between blocks to perform bonding. Figures 1 to 3B The described operation.

[0085] Storage device 530 can store at least one of the information transmitted / received via transceiver 510 and information generated via controller 520. For example, storage device 530 can store the information mentioned above. Figures 1 to 3B The information and data required for the described method.

[0086] Although this disclosure has been described with reference to various embodiments, various changes and modifications may be suggested to those skilled in the art. This disclosure is intended to cover such changes and modifications that fall within the scope of the appended claims.

Claims

1. A method performed by a network entity for operating sensing network functions in a communication system supporting Integrated Sensing and Communication (ISAC), the method comprising: Receive a first request message for sensing services from the user equipment (UE) or application function (AF); Based on the first request message, a second request message for requesting sensing policy data is sent to the Unified Data Repository (UDR). as well as In response to sending the second request message, a response message is received from the UDR, wherein the response message includes Sensing Quality of Service (SSQ) information.

2. The method according to claim 1, wherein, The first request message includes at least one of the following: UE identifier, AF identifier, ISAC service type, ISAC service identifier, ISAC service target area, and SSQ information indicating the required ISAC quality of service information.

3. The method according to claim 1, wherein, The second request message includes at least one of the following: the identifier information of the sensing service, the requested sensing service quality information, or information about the sensing target area.

4. The method according to claim 1, further comprising: After receiving the response message, a negotiation operation is performed on the sensing service quality information.

5. The method according to claim 1, further comprising: Send a message to the Unified Data Management (UDM) to request sensing policy data or sensing service configuration file information for the UE; as well as Receive the subscribed Sensing Service Quality (SSQ) information from the UDM.

6. The method according to claim 1, further comprising: Send a sensing service policy to the UE, the sensing service policy including at least one of the following: SSQ information, ISAC service identifier, ISAC service type, application spatial range, or application time range.

7. The method according to claim 1, further comprising: Authentication is performed on the requester of sensing services by interoperating with Unified Data Management (UDM) or Network Open Function (NEF).

8. A network entity for operating sensing network functions in a communication system supporting Integrated Sensing and Communication (ISAC), the network entity comprising: transceiver; as well as A controller operatively connected to the transceiver is configured to: Receive a first request message for sensing services from the user equipment (UE) or application function (AF). Based on the first request message, a second request message for requesting sensing policy data is sent to the Unified Data Repository (UDR). In response to sending the second request message, a response message is received from the UDR, wherein the response message includes Sensing Quality of Service (SSQ) information.

9. The network entity according to claim 8, wherein, The first request message includes at least one of the following: UE identifier, AF identifier, ISAC service type, ISAC service identifier, ISAC service target area, and SSQ information indicating the required ISAC quality of service information.

10. The network entity according to claim 8, wherein, The second request message includes at least one of the following: the identifier information of the sensing service, the requested sensing service quality information, or information about the sensing target area.

11. The network entity according to claim 8, wherein, The controller is also configured to: After receiving the response message, a negotiation operation is performed on the sensing service quality information.

12. The network entity according to claim 8, wherein, The controller is also configured to: Send a message to the Unified Data Management (UDM) requesting sensing policy data or sensing service configuration file information for the UE, and Receive the subscribed Sensing Service Quality (SSQ) information from the UDM.

13. The network entity according to claim 8, wherein, The controller is also configured to: Send a sensing service policy to the UE, the sensing service policy including at least one of the following: SSQ information, ISAC service identifier, ISAC service type, application spatial range, or application time range.

14. The network entity according to claim 8, wherein, The controller is also configured to: Authentication is performed on the requester of sensing services by interoperating with Unified Data Management (UDM) or Network Open Function (NEF).

Images