Method and device for providing external service for ultra-power-saving device in wireless communication system

Abstract

The present invention provides a device and method capable of effectively providing a service in a wireless communication system. More specifically, the present invention relates to an operation between a network operator and an external service operator in a wireless communication system, and provides a method and device for providing a network service to the external service operator when the external service operator uses an ultra-power-saving device through a mobile communication network in the wireless communication system.

Description

Method and device for providing external services for ultra-low power devices in wireless communication systems

[0001] The present disclosure relates to operations between a network operator and an external service provider in a wireless communication system. More specifically, the present disclosure relates to a method and device for providing network services to an external service provider in a wireless communication system when the external service provider uses an ultra-low-power device over a mobile communication network.

[0002] 5G mobile communication technology defines a wide frequency band to enable fast transmission speeds and new services, and can be implemented not only in the sub-6GHz frequency band such as 3.5 gigahertz (3.5GHz), but also in the ultra-high frequency band called millimeter wave (mmWave) such as 28GHz and 39GHz ('Above 6GHz'). In addition, for 6G mobile communication technology, which is called the system after 5G communication (Beyond 5G), implementation in the terahertz (THz) band (for example, 3 THz band at 95GHz) is being considered to achieve a transmission speed that is 50 times faster than 5G mobile communication technology and an ultra-low latency time that is reduced to one-tenth.

[0003] In the early stages of 5G mobile communication technology, the goal is to support services and satisfy performance requirements for enhanced Mobile Broadband (eMBB), Ultra-Reliable Low-Latency Communications (URLLC), and massive Machine-Type Communications (mMTC). These include beamforming and massive MIMO to mitigate path loss of radio waves in ultra-high frequency bands and increase the transmission distance of radio waves, support for various numerologies (such as operation of multiple subcarrier intervals) and dynamic operation of slot formats for efficient use of ultra-high frequency resources, initial access technology to support multi-beam transmission and wideband, definition and operation of BWP (Bidth Part), new channel coding methods such as LDPC (Low Density Parity Check) codes for large-capacity data transmission and Polar Code for reliable transmission of control information, and L2 pre-processing (L2). Standardization has been made for network slicing, which provides dedicated networks specialized for specific services, and pre-processing.

[0004] Currently, discussions are underway to improve and enhance the initial 5G mobile communication technology in consideration of the services that 5G mobile communication technology was intended to support, and physical layer standardization is in progress for technologies such as V2X (Vehicle-to-Everything) to help autonomous vehicles make driving decisions and increase user convenience based on their own location and status information transmitted by vehicles, NR-U (New Radio Unlicensed) for the purpose of system operation that complies with various regulatory requirements in unlicensed bands, NR terminal low power consumption technology (UE Power Saving), Non-Terrestrial Network (NTN), which is direct terminal-satellite communication to secure coverage in areas where communication with terrestrial networks is impossible, and Positioning.

[0005] In addition, standardization of wireless interface architecture / protocols is in progress for technologies such as intelligent factories (Industrial Internet of Things, IIoT) to support new services through linkage and convergence with other industries, Integrated Access and Backhaul (IAB) that provides nodes for expanding network service areas by integrating wireless backhaul links and access links, Mobility Enhancement technology including Conditional Handover and Dual Active Protocol Stack (DAPS) handover, and 2-step random access (2-step RACH for NR) that simplifies random access procedures. Standardization is also in progress for system architecture / services such as 5G baseline architecture (e.g., Service-based Architecture, Service-based Interface) for grafting Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC) that provides services based on the location of the terminal.

[0006] Once these 5G mobile communication systems are commercialized, an explosive increase in connected devices will be connected to the communication network, necessitating enhanced functionality and performance of 5G mobile communication systems and integrated operation of these connected devices. To this end, new research will be conducted on improving 5G performance and reducing complexity, supporting AI services, supporting metaverse services, and drone communications by utilizing eXtended Reality (XR), Artificial Intelligence (AI), and Machine Learning (ML) to efficiently support Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR).

[0007] In addition, the development of these 5G mobile communication systems includes new waveforms to ensure coverage in the terahertz band of 6G mobile communication technology, multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), Array Antenna, and Large Scale Antenna, metamaterial-based lenses and antennas to improve the coverage of terahertz band signals, high-dimensional spatial multiplexing technology using Orbital Angular Momentum (OAM), Reconfigurable Intelligent Surface (RIS) technology, as well as full duplex technology to improve the frequency efficiency and system network of 6G mobile communication technology, satellite, AI (Artificial Intelligence) from the design stage and AI-based communication technology that realizes system optimization by internalizing end-to-end AI support functions, and ultra-high-performance communication and computing resources to provide services with complexity that exceeds the limits of terminal computing capabilities. It can serve as a basis for the development of next-generation distributed computing technologies that can be realized by utilizing them.

[0008] The purpose of the present disclosure is to provide a method and device for providing an external service capable of managing ultra-low power devices to an external service provider conducting business using ultra-low power devices in a wireless communication system.

[0009] The technical problems to be achieved in the present invention are not limited to the technical problems mentioned above, and other technical problems not mentioned can be clearly understood by a person having ordinary skill in the technical field to which the present invention belongs from the description below.

[0010] According to various embodiments of the present disclosure, a method for processing a control signal in a wireless communication system may include: receiving a first control signal transmitted from a base station; processing the received first control signal; and transmitting a second control signal generated based on the processing to the base station.

[0011] One embodiment of the present invention provides a device and method capable of effectively providing a service in a wireless communication system.

[0012] The effects that can be obtained from the present invention are not limited to the effects mentioned above, and other effects not mentioned can be clearly understood by a person having ordinary skill in the art to which the present disclosure pertains from the description below.

[0013] FIG. 1 illustrates the structure of a wireless communication system according to various embodiments of the present disclosure.

[0014] FIG. 2 illustrates an example of a scenario in which an Ambient IoT (Internet of Things) device is used in a wireless communication system according to an embodiment of the present disclosure.

[0015] FIG. 3 illustrates an example of a Device ID (identifier), which is identification information of an Ambient IoT device in a wireless communication system according to an embodiment of the present disclosure.

[0016] FIG. 4 illustrates an example of an external network service for an external service provider required for managing Ambient IoT devices after deploying Ambient IoT devices to an area of ​​interest in a wireless communication system according to an embodiment of the present disclosure.

[0017] FIG. 5 illustrates a procedure for subscribing to a Monitoring Coverage of Interesting Area (CCA) Event Exposure Service for managing Ambient IoT devices in a wireless communication system according to an embodiment of the present disclosure.

[0018] FIG. 6 illustrates an example of a case where no header exists in each cell in a wireless communication system according to an embodiment of the present disclosure.

[0019] Figure 7 illustrates the configuration of a terminal according to an embodiment of the present disclosure.

[0020] Figure 8 illustrates the configuration of a base station according to an embodiment of the present disclosure.

[0021] FIG. 9 illustrates the configuration of a network entity according to an embodiment of the present disclosure.

[0022] Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the attached drawings. It should be noted that, where possible, identical components are represented by identical reference numerals throughout the drawings. Furthermore, detailed descriptions of well-known functions and configurations that may obscure the gist of the present invention will be omitted.

[0023] In describing the embodiments herein, descriptions of technical details that are well known in the technical field to which the present disclosure pertains and are not directly related to the present invention will be omitted. This is to avoid obscuring the gist of the present disclosure by omitting unnecessary explanations and to convey the gist more clearly.

[0024] For the same reason, some components in the attached drawings are exaggerated, omitted, or schematically depicted. Furthermore, the dimensions of each component do not entirely reflect its actual size. Identical or corresponding components in each drawing are assigned the same reference numbers.

[0025] The advantages and features of the present disclosure, and the methods for achieving them, will become clearer with reference to the embodiments described in detail below together with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below and may be implemented in various different forms. These embodiments are provided only to ensure that the disclosure of the present disclosure is complete and to fully inform those skilled in the art of the scope of the disclosure, and the present disclosure is defined only by the scope of the claims. Like reference numerals refer to like elements throughout the specification.

[0026] Furthermore, when describing the present disclosure, detailed descriptions of related functions or configurations will be omitted if they are deemed to unnecessarily obscure the gist of the present disclosure. Furthermore, the terms described below are defined based on the functions of the present disclosure and may vary depending on the intent or custom of the user or operator. Therefore, their definitions should be based on the content throughout this specification.

[0027] Hereinafter, the base station is an entity that performs resource allocation of the terminal, and may be at least one of a gNode B (gNB), an eNode B (eNB), a Node B, a BS (Base Station), a wireless access unit, a base station controller, or a node on a network. The terminal may include a UE (User Equipment), an MS (Mobile Station), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing a communication function. In the present disclosure, downlink (DL) refers to a wireless transmission path of a signal transmitted from a base station to a terminal, and uplink (UL) refers to a wireless transmission path of a signal transmitted from a terminal to a base station. In addition, in the following, LTE (long-term evolution), LTE-A (LTE-advanced) or 5G (5 thAlthough the present disclosure may be described as an example of a 5G (new radio (NR)) system, the embodiments of the present disclosure may also be applied to other communication systems with similar technical backgrounds or channel types. For example, this may include the 5G (new radio (NR)) mobile communication technology developed after LTE-A, and the 5G below may be a concept that includes existing LTE, LTE-A, and other similar services. In addition, the present disclosure may be applied to other communication systems with some modifications within a range that does not significantly deviate from the scope of the present disclosure, as determined by a person having skilled technical knowledge.

[0028] At this time, it will be understood that each block of the processing flow diagrams and combinations of the flow diagrams can be performed by computer program instructions. These computer program instructions can be installed in a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing equipment, so that the instructions executed by the processor of the computer or other programmable data processing equipment create a means for performing the functions described in the flow diagram block(s). These computer program instructions can also be stored in a computer-available or computer-readable memory that can direct a computer or other programmable data processing equipment to implement the functions in a specific manner, so that the instructions stored in the computer-available or computer-readable memory can also produce a manufactured item that includes an instruction means for performing the functions described in the flow diagram block(s). Since the computer program instructions may be installed on a computer or other programmable data processing device, a series of operational steps may be performed on the computer or other programmable data processing device to create a computer-executable process, and the instructions that cause the computer or other programmable data processing device to perform the steps for performing the functions described in the flowchart block(s) may also provide steps for performing the functions described in the flowchart block(s).

[0029] Additionally, each block may represent a module, segment, or portion of code that contains one or more executable instructions for performing a specific logical function(s). It should also be noted that in some alternative implementation examples, the functions described in the blocks may occur out of order. For example, two blocks depicted in succession may actually be executed substantially concurrently, or the blocks may sometimes be executed in reverse order, depending on their respective functions.

[0030] Here, the term '~ unit' used in the present embodiments means a software or hardware component such as an FPGA or ASIC, and the '~ unit' performs certain roles. However, the '~ unit' is not limited to software or hardware. The '~ unit' may be configured to be on an addressable storage medium and may be configured to reproduce one or more processors. Thus, as an example, the '~ unit' includes components such as software components, object-oriented software components, class components, and task components, processes, functions, properties, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functions provided within the components and '~ units' may be combined into a smaller number of components and '~ units' or further separated into additional components and '~ units'. In addition, the components and '~ units' may be implemented to reproduce one or more CPUs within a device or a secure multimedia card. Additionally, in the embodiment, '~bu' may include one or more processors.

[0031] Wireless communication systems have evolved from providing voice-oriented services in the early days to broadband wireless communication systems that provide high-speed, high-quality packet data services, such as communication standards such as 3GPP's HSPA (High Speed ​​Packet Access), LTE (or E-UTRA (Evolved Universal Terrestrial Radio Access)), LTE-Advanced (LTE-A), LTE-Pro, 3GPP2's HRPD (High Rate Packet Data), UMB (Ultra Mobile Broadband), and IEEE's 802.16e.

[0032] As a representative example of a broadband wireless communication system, the LTE system uses the OFDM (Orthogonal Frequency Division Multiplexing) method in the downlink and the SC-FDMA (Single Carrier Frequency Division Multiple Access) method in the uplink. The uplink refers to a wireless link in which a terminal (User Equipment (UE) or Mobile Station (MS)) transmits data or control signals to a base station (eNode B, gNode B, or base station (BS)), and the downlink refers to a wireless link in which a base station transmits data or control signals to a terminal. The above-described multiple access method can distinguish the data or control information of each user by allocating and operating the time-frequency resources to be transmitted, including data or control information, so that they do not overlap with each other (i.e., so that orthogonality is established).

[0033] As a future communication system beyond LTE, 5G communication systems must be able to freely reflect the diverse needs of users and service providers. Therefore, they must support services that simultaneously satisfy these diverse requirements. Services being considered for 5G communication systems include enhanced Mobile Broadband (eMBB), massive Machine Type Communication (mMTC), and Ultra-Reliable Low Latency Communication (URLLC).

[0034] eMBB aims to provide data transmission rates that are significantly higher than those supported by existing LTE, LTE-A, or LTE-Pro. For example, in a 5G communication system, eMBB must be able to support a peak data rate of 20 Gbps in the downlink and a peak data rate of 10 Gbps in the uplink from the perspective of a single base station. Furthermore, 5G communication systems must simultaneously provide the peak data rate and an increased user-perceived data rate for terminals. To meet these requirements, improvements in various transmission and reception technologies, including improved multi-input, multi-output (MIMO) transmission technology, are required. Furthermore, while LTE transmits signals using a maximum transmission bandwidth of 20 MHz in the 2 GHz band, 5G communication systems can meet the data transmission rates required by 5G communication systems by using a wider frequency bandwidth than 20 MHz in the 3-6 GHz or higher 6 GHz band.

[0035] At the same time, massive Machine Type Communications (mMTC) is being considered to support application services such as the Internet of Things (IoT) in 5G communication systems. To efficiently provide the IoT, mMTC requires supporting a large number of terminals within a cell, improving terminal coverage, extending battery life, and reducing terminal costs. The IoT requires the ability to support a large number of terminals (e.g., 1,000,000 terminals / km^2) within a cell, as it provides communication capabilities through the attachment of various sensors and devices. Furthermore, terminals supporting mMTC are likely to be located in shadow areas, such as basements, beyond cell coverage due to the nature of the service, and thus may require wider coverage than other services provided by 5G communication systems. Terminals supporting mMTC must be inexpensive, and because frequent battery replacement is difficult, they may require extremely long battery lifespans, such as 10 to 15 years.

[0036] Finally, URLLC refers to a cellular-based wireless communication service used for a specific purpose (mission-critical). Examples include remote control of robots or machinery, industrial automation, unmanned aerial vehicles (UAVs), remote health care, and emergency alerts. Therefore, URLLC communications must provide extremely low latency and high reliability. For example, services supporting URLLC must meet air interface latency requirements of less than 0.5 milliseconds and a packet error rate (PER) of less than 10^-5. Therefore, for services supporting URLLC, 5G systems must provide a shorter transmission time interval (TTI) than other services, and design requirements may require the allocation of extensive resources in the frequency band to ensure communication link reliability.

[0037] The three 5G services—eMBB, URLLC, and mMTC—can be multiplexed and transmitted within a single system. To meet the differing requirements of each service, different transmission and reception techniques and parameters can be used. Of course, 5G is not limited to the three services described above.

[0038] According to various embodiments of the present disclosure, phrases such as “A and / or B,” “A or B,” “at least one of A and B,” “at least one of A or B,” “A, B, or C,” “at least one of A, B, and C,” and “at least one of A, B, or C” can each include any one of the items listed together in that phrase, or all possible combinations thereof. Terms such as “first,” “second,” or “first” or “second” may be used merely to distinguish the corresponding element from other corresponding elements and do not limit the corresponding elements in any other respect (e.g., importance or order).

[0039] Hereinafter, the base station is an entity that performs resource allocation of a terminal, and may be at least one of a Node B, a BS (Base Station), an eNB (eNode B), a gNB (gNode B), a wireless access unit, a base station controller, or a node on a network. The terminal may include a UE (User Equipment), an MS (Mobile Station), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing a communication function. In addition, the embodiments of the present disclosure may be applied to other communication systems having a similar technical background or channel form to the embodiments of the present disclosure described below. In addition, the embodiments of the present disclosure may be applied to other communication systems through some modifications without significantly departing from the scope of the present disclosure at the discretion of a person having skilled technical knowledge.

[0040] In the present disclosure, network technology may refer to standard specifications defined by the International Telecommunication Union (ITU) or 3GPP (e.g., TS 23.501, TS 23.502, TS 23.503, etc.), and components included in the network structure of FIG. 1 may each mean a physical entity, or may mean software performing an individual function, or hardware combined with software. Reference symbols shown as Nx, such as N1, N2, N3, ..., in the drawings represent known interfaces between NFs (network functions) in a 5G core network (CN), and since a related description may refer to a standard specification (e.g., TS 23.501), a detailed description will be omitted.

[0041] In the following description, terms used to identify connection nodes, terms referring to network entities (NEs) or network functions (NFs), terms referring to messages, terms referring to interfaces between network objects, terms referring to various identification information, etc. are examples provided for convenience of explanation. Therefore, the present disclosure is not limited to the terms described below, and other terms referring to objects having equivalent technical meanings may be used.

[0042] For convenience of explanation, some terms and names defined in the 3rd generation partnership project long-term evolution (3GPP) standards may be used. However, the present disclosure is not limited to these terms and names, and can be equally applied to systems conforming to other standards.

[0043] FIG. 1 illustrates the architecture of a wireless communication system according to various embodiments of the present disclosure. More specifically, FIG. 1 illustrates an example of the configuration of a 5G system. Referring to FIG. 1, a 5G network may include at least one of the following network entities (NEs) or network functions (NFs).

[0044] According to one embodiment, the (R)AN ((Radio) Access Network) is an entity that performs radio resource allocation of a terminal, and may include at least one of an eNode B, a Node B, a BS (Base Station), an NG-RAN (Next Generation Radio Access Network), a 5G-AN (5G Access Network), a 5G NR (5G New Radio), a radio access unit, a base station controller, or a node on a network.

[0045] According to one embodiment, the terminal may include a User Equipment (UE), a Next Generation UE (NG UE), a Mobile Station (MS), a cellular phone, a smartphone, a computer, an Internet of Things (IoT) device, or a multimedia system capable of performing a communication function.

[0046] Furthermore, while the embodiments of the present disclosure are described below using a 5G system as an example, the embodiments of the present disclosure can also be applied to other communication systems with similar technical backgrounds. Furthermore, the embodiments of the present disclosure can be applied to other communication systems with some modifications, as determined by a person skilled in the art, without significantly departing from the scope of the present disclosure.

[0047] As wireless communication systems evolve from 4G to 5G, a new core network (CN) called the Next Generation Core (NG Core) or 5GC (5G Core Network) is defined. This new core network can virtualize all existing network entities (NEs) into network functions (NFs). According to one embodiment of the present disclosure, a network function may refer to a network entity, a network component, or a network resource.

[0048] According to one embodiment of the present disclosure, 5GC may include one or more NFs illustrated in FIG. 1. Of course, the present invention is not limited to the example illustrated in FIG. 1, and 5GC may include more or fewer NFs than the NFs illustrated in FIG. 1.

[0049] In one embodiment, the Access and Mobility Management Function (AMF) may be a network function that manages access and mobility of a terminal (UE). For example, the AMF may perform network functions such as terminal registration, connection, reachability, mobility management, access verification, authentication, and mobility event generation.

[0050] In one embodiment, a Session Management Function (SMF) may be a network function that manages a Packet Data Network (PDN) connection provided to a User Equipment (UE). The PDN connection may be referred to as a Protocol Data Unit (PDU) Session. For example, the SMF may perform network functions such as session management through establishing, modifying, and releasing sessions and maintaining tunnels between a User Plane Function (UPF) and the RAN, selecting and controlling a User Plane (UPF), controlling traffic processing in the UPF, and controlling the collection of charging data.

[0051] In one embodiment, the Policy Control Function (PCF) may be a network function that applies a mobile communication operator's service policy, charging policy, and policy for PDU Session to a terminal.

[0052] In one embodiment, Unified Data Management (UDM) may be a network function that stores subscriber information. For example, UDM may perform functions such as generating authentication information for 3GPP security, processing user identifiers (User IDs), managing a list of network functions supporting UEs, and managing subscription information.

[0053] In one embodiment, the Network Exposure Function (NEF) may provide information about a terminal to a server outside the 5G network. Furthermore, NEF may provide the ability to provide information necessary for 5G network services and store it in the Unified Data Repository (UDR).

[0054] In one embodiment, the User Plane Function (UPF) may be a gateway function that transmits user data (e.g., PDU) to the Data Network (DN). More specifically, the UPF may perform a data processing function so that data transmitted by a terminal can be transmitted to an external network or data received from an external network can be transmitted to the terminal. For example, the UPF may perform network functions such as serving as an anchor between Radio Access Technologies (RATs), packet routing and forwarding, packet inspection, user plane policy application, traffic usage report generation, and buffering.

[0055] In one embodiment, the Network Repository Function (NRF) may store profiles of NFs and perform discovery of NFs.

[0056] In one embodiment, the Authentication Server Function (AUSF) can perform terminal authentication in a 3GPP access network and a non-3GPP access network.

[0057] According to one embodiment, the Network Slice Selection Function (NSSF) may perform a function of selecting a Network Slice Instance provided to a terminal.

[0058] In one embodiment, the Network Data Analytics Function (NWDAF) may collect data from multiple NFs (NFs) for the purpose of efficiently operating the 5GC network. In one embodiment, the collected data may be analyzed using a machine learning (ML) model, and the analyzed results may be provided back to the NFs to help each NF provide efficient network services.

[0059] In one embodiment, an Application Function (AF) can communicate with a network operator so that an external server (Application Server) can utilize network services provided by the network operator. Depending on the deployment entity, an AF can be classified as an internal AF or an external AF. An internal AF deployed by a network operator can communicate directly with network function providers (NFs) within the network operator. An AF deployed by a third-party service provider (3rd-party service provider) may need to go through an NEF to communicate with NFs within the network operator.

[0060] In one embodiment, the DN (Data Network) may be a data network through which a terminal transmits and receives data in order to use a network operator's service or a third-party service.

[0061] In one embodiment, the Network Slice Admission Control Function (NSACF) may limit the number of PDU sessions of registered terminals in each slice, thereby performing a resource management function.

[0062] In one embodiment, the Network Slice-Specific Authentication and Authorization Function (NSSAAF) may create a slice authentication context for a terminal and perform slice-specific authentication and authorization procedures.

[0063] In one embodiment, the Edge Application Server Discovery Function (EASDF) may create a domain name system (DNS) context for a PDU session and may perform functions such as storing a UE IP (internet protocol) address, DNS message processing rules, etc. in the context.

[0064] In one embodiment, a Service Communication Proxy (SCP) may perform indirect communication functions such as service discovery, call response, etc.

[0065] In one embodiment, the terminal may include an IoT device. The IoT device may include a device that does not use battery power or operates with very little power, and such an IoT device may be referred to as an ambient IoT device (or Ambient IoT).

[0066] In the 3GPP system, a conceptual link connecting NFs within a 5G system is defined as a reference point. The following illustrates a reference point included in the 5G system architecture depicted in Figure 1.

[0067] - N1: Reference point between UE and AMF

[0068] - N2: Reference point between (R)AN and AMF

[0069] - N3: Reference point between (R)AN and UPF

[0070] - N4: Reference point between SMF and UPF

[0071] - N6: Reference point between UPF and DN

[0072] - N9: Reference point between two core UPFs

[0073] Additionally, in 3GPP systems, the 5G system architecture may include service-based interfaces such as the following examples.

[0074] - Nnssf: Service-based interface by NSSF

[0075] - Nnssaaf: Service-based interface by NSSAAF (Network Slice-Specific Authentication and Authorization Function)

[0076] - Nnef: Service-based interface by NEF

[0077] - Nausf: Service-based interface by AUSF

[0078] - Nnrf: Service-based interface by NRF

[0079] - Namf: Service-based interface by AMF

[0080] - Npcf: Service-based interface by PCF

[0081] - Nsmf: Service-based interface by SMF

[0082] - Nupf: Service-based interface by UPF

[0083] - Nudm: Service-based interface by UDM

[0084] - Naf: Service-based interface by AF

[0085] - Nasaf: Service-based interface by AUSF

[0086] - Neasdf: Service-based interface by EASDF (Edge Application Server Discovery Function)

[0087] - Nnwdaf: Service-based interface by NWDAF

[0088] According to one embodiment of the present disclosure, an Ambient IoT device may be a device that does not have a battery or has very limited energy storage capacity, and also has very limited communication and computing capabilities. Accordingly, the device is very inexpensive, and typically hundreds of thousands to millions of devices can be deployed in an area of ​​interest and operate to perform common tasks.

[0089] In this disclosure, a method is proposed to provide an external service provider that conducts business using Ambient IoT devices (or Ambient IoT devices) having the above-described characteristics with an external service that can efficiently manage Ambient IoT devices.

[0090] Ambient IoT Explained

[0091] Ambient IoT devices may have at least one of the following characteristics:

[0092] - Very low power consumption for device operation (e.g. 1-500μW)

[0093] - The device is very cheap (e.g. $0.01~$0.5)

[0094] - Very low data transfer speed (e.g. 10kbps)

[0095] - The number of devices being deployed is very large (e.g., hundreds, thousands, tens of thousands, hundreds of thousands, or more than 1,000,000).

[0096] - It has very low computational power, simple structure, and very small device size.

[0097] - May not include USIM (Universal Subscriber Identity Module)

[0098] - May not include complex communication protocol stacks such as TCP / IP (Transmission Control Protocol / Internet Protocol)

[0099] - They can be deployed primarily in environments that are difficult for people to access, making maintenance after deployment impossible (e.g., high pressure, extremely high / low temperature, humid environment)

[0100] In the present disclosure, Ambient IoT devices can be divided into three types, as shown in Table 1 below, depending on the presence or absence of a battery within the device and the communication method used by the device. Of course, the present disclosure is not limited to the examples below. For example, the types of Ambient IoT devices in the present disclosure are not limited to the examples in Table 1 below, and it may also be possible to distinguish the types of Ambient IoT devices using other criteria.

[0101]

[0102] In addition, the Ambient IoT devices in the present disclosure may have a connectivity topology classified into four types, as shown in the examples in Table 2 below. Of course, the present disclosure is not limited to the examples below. For example, the connectivity types of the Ambient IoT devices in the present disclosure are not limited to the examples in Table 2 below, and connections may also be made through various combinations of the four types of connectivity topologies.

[0103]

[0104] The traffic types of Ambient IoT devices can also be defined as follows. Of course, they are not limited to the examples below.

[0105] - Device-Terminated (DT): A traffic type that receives data from the network.

[0106] - Device-Originated-Device-Terminated Triggered (DO-DTT): A traffic type in which data received from the network triggers device data transmission.

[0107] [Ambient IoT Usage Scenarios]

[0108] FIG. 2 illustrates an example of a scenario in which an Ambient IoT device is used in a wireless communication system according to an embodiment of the present disclosure.

[0109] The communication system of FIG. 2 may include a data network including a plurality of Ambient IoT devices deployed in a mountainous area, at least one base station capable of communicating with at least one of the Ambient IoT devices, a core network to which the at least one base station is connected, and an AF communicably connected to the core network. The basic functions and configuration of the data network including the base station, the core network, and the AF in the example of FIG. 2 may refer to the example of FIG. 1.

[0110] Referring to Figure 2, the Korea Forest Service or the National Fire Agency can deploy millions of Ambient IoT devices on mountains for early detection of forest fires. Because the number of Ambient IoT devices and the vast deployment areas are difficult for humans to access, they are often deployed by air. For the reasons mentioned above, maintenance (e.g., battery replacement, replacement of defective components, etc.) of deployed Ambient IoT devices may be impossible. Once deployed, Ambient IoT devices must operate for at least 10 years and up to 20 years to perform their duties. Therefore, it is crucial that Ambient IoT devices operate with minimal battery consumption. In the scenario of Figure 2, the deployed Ambient IoT devices can monitor fires around the mountain. Among the Ambient IoT devices, at least one Ambient IoT device that detects a fire transmits information notifying of the fire to the NG-RAN (in the case of a 5G network) using a wireless network, and the information can be transmitted to the AF (3rd party server / provider, such as the server of the National Fire Agency in the example of FIG. 2) via the 5G network and the data network. As in the embodiment of FIG. 2, Ambient IoT devices can be deployed for the same purpose, such as notifying of a fire, and information notifying of a fire and / or data related to the information can be transmitted to a 3rd party server (AF). Although the example of FIG. 2 exemplifies a fire outbreak scenario in a mountain, Ambient IoT devices can be deployed to provide relevant information in various disaster situations or in various commercial services, such as sports stadiums or shopping malls used by many people.

[0111] [Ambient IoT ID]

[0112] FIG. 3 illustrates an example configuration of a Device ID, which is identification information of an Ambient IoT device, in a wireless communication system according to an embodiment of the present disclosure.

[0113] Referring to FIG. 3, devices operating according to the 3GPP standard can use the SUPI (Subscription Permanent Identifier) / IMSI (International Mobile Subscriber Identity), which is identification information contained in the USIM chip, as the device's ID. However, Ambient IoT devices may not be able to use USIM chips, or the number of Ambient IoT devices may be so large that it may be impossible for mobile carriers to assign unique IDs to each device. Accordingly, FIG. 3 illustrates an embodiment related to the Ambient IoT device ID.

[0114] Since the number of Ambient IoT devices is large as in the scenario of FIG. 2, grouping the Ambient IoT devices may be efficient in controlling their operations. Ambient IoT devices may be grouped according to their tasks. In one embodiment, Ambient IoT devices may be grouped based on a third-party provider of an AF that communicates with the Ambient IoT devices. Accordingly, the third-party provider may group Ambient IoT devices for various reasons, such as by region, purpose, or simply a certain number. In one embodiment, grouping by Ambient IoT Device Type as exemplified in [Table 1] or by Connectivity Type as exemplified in [Table 2] may also be possible. In one embodiment, Ambient IoT devices may be grouped according to a specific Use Case or task scenario. The embodiment of FIG. 3 illustrates an example of a Device ID of an Ambient IoT device, and various other values ​​may be used as the Device ID of an Ambient IoT device.

[0115] In this embodiment, the definitions for each field that constitutes the Device ID of an Ambient IoT device are as shown in the example below. In the following description, the 3rd party provider can be understood as AF or a 3rd party provider's server. Of course, the present invention is not limited to the following example.

[0116] - MNO ID: This represents the mobile carrier ID used by third-party providers to communicate with Ambient IoT devices. The MNO ID may include at least one of a Mobile Country Code (MCC) and a Mobile Network Code (MNC). Alternatively, the MNO ID may consist solely of an MNC.

[0117] - Enterprise ID: This can indicate the company to which a third-party provider belongs. When work is performed using multiple third-party servers, all Ambient IoT devices belonging to the company can be grouped using the Enterprise ID.

[0118] - AF ID: The AF ID can be an ID that distinguishes a third-party provider / server. All Ambient IoT devices performing a single task or all Ambient IoT devices communicating with a single AF can be distinguished through the AF ID.

[0119] - TASK ID: This can be an ID that can be used to group Ambient IoT devices that perform a series of common TASKs.

[0120] - Group ID: Because there are a large number of Ambient IoT devices, grouping them may be necessary to control them. A Group ID can be used to group Ambient IoT devices. Grouping Ambient IoT devices can be based on at least one classification criterion, such as purpose, capability, or status.

[0121] - Device Type ID: Ambient IoT devices can be classified into types A (TY_A), B (TY_B), and C (TY_C) as in the example of [Table 1] above, depending on battery capacity and communication capability. This may be an ID indicating the device type described above. Ambient IoT devices can also be grouped by Device Type using the Device Type ID.

[0122] - Connectivity Type ID: Ambient IoT devices can be classified into Topology 1 (T1), Topology 2 (T2), Topology 3 (T3), and Topology 4 (T4) as shown in the example of [Table 2] above, depending on their ability to communicate with networks and terminals and their connection topology. This may be an ID indicating the connection type described above. Using the Connectivity Type ID, Ambient IoT devices can also be grouped by Connectivity Type.

[0123] - Use Case Specific ID: The Use Case Specific ID may be an ID that can be assigned according to the Use Case or scenario in which the Ambient IoT device is used. For example, in a scenario for detecting a forest fire, each Ambient IoT device may need to report the location of the fire when it detects a fire. For example, the location of the Ambient IoT device may be important. In this case, if the location of the Ambient IoT device is used as the Use Case Specific ID of the Ambient IoT device, the Ambient IoT device only needs to send a notification that a forest fire has occurred without having to separately send the location of the forest fire as data, and a 3rd party provider can identify the location with only the ID of the Ambient IoT device. However, the above-described example is one embodiment, and the Use Case Specific ID may be utilized in various other Use Cases.

[0124] - Unique Device ID: The Unique Device ID can be a unique ID to distinguish each Ambient IoT device. The Unique Device ID can be a globally unique Device ID when used with at least one of the MNO ID, Enterprise ID, or AF ID. Since the number of Ambient IoT devices is so large, 3rd party providers can arbitrarily assign a range of Unique Device IDs. Alternatively, the Unique Device ID can be replaced with the manufacturing number of each device. The Unique Device ID can be defined as any value that can uniquely distinguish each device within the 3rd party provider or mobile operator.

[0125] The above-described examples are only examples of the elements that constitute the Device ID of an Ambient IoT device, and each value that constitutes the Device ID can be freely configured according to the purpose of use or the capabilities of the Ambient IoT device. In addition, a Group ID can be configured using various components to group Ambient IoT devices. In addition, various components not mentioned in this embodiment can be added according to the purpose of use or function of the Ambient IoT device. Among the components, at least the AF ID and the Unique Device ID can be included in the Device ID of the Ambient IoT device.

[0126] FIG. 4 illustrates an example of an external network service for an external service provider required for managing Ambient IoT devices after deploying Ambient IoT devices to an area of ​​interest in a wireless communication system according to an embodiment of the present disclosure.

[0127] Referring to Figure 4, since Ambient IoT devices are numerous, aircraft can be used to deploy them to areas of interest. For example, Ambient IoT devices for forest fire monitoring could be deployed on a mountain. In this case, the deployed Ambient IoT devices should be evenly distributed to ensure they sense the entire area of ​​interest. If they are deployed too loosely, a forest fire monitoring hole may be created, preventing detection of forest fires in undeployed areas.

[0128] In another example, deployed Ambient IoT devices may no longer be able to perform wildfire sensing tasks for a number of reasons. Ambient IoT devices may not be able to operate due to battery life exhaustion or small batteries. Alternatively, Ambient IoT devices may be driven out of the area of ​​interest by flooding or may be damaged by physical external factors (e.g., animal attacks, natural disasters, or external impacts). Because Ambient IoT devices are often deployed in areas that are difficult for people to access and are numerous, it may be impossible for humans to manually address Ambient IoT devices when their batteries run out or they become inoperable.

[0129] In this disclosure, an external network service capable of providing information necessary for managing Ambient IoT devices to an external service provider is proposed for managing the Ambient IoT devices described above.

[0130] FIG. 4 illustrates an embodiment in which an area of ​​interest is divided into a grid, and when the number of Ambient IoT devices operating within each cell falls below a certain ratio (e.g., less than 50%) compared to the number of Ambient IoT devices sufficient to cover the cell area, it is reported to the network that there are not enough Ambient IoT devices to cover the cell area.

[0131] To subscribe to the Event Exposure service for managing Ambient IoT devices on the network, an external service provider may provide at least one of the following pieces of information to the network, including but not limited to the examples below:

[0132] (1) Event ID(s): IDs that identify the Event Exposure services to subscribe to. In one embodiment, the Monitoring Coverage of Interesting service may be an event exposure service that reports whether sufficient Ambient IoT devices are operating in the area of ​​interest to perform a task. For example, when Ambient IoT devices are initially deployed in the area of ​​interest, the external service provider may report at least one of whether they are uniformly deployed in the area of ​​interest to perform the task without any problems, or whether the number of operating Ambient IoT devices is maintained to a level where they can perform the task without any problems. If not enough Ambient IoT devices are deployed to perform the task, the network may send a notification to the external service provider. The external service provider may then redeploy new Ambient IoT devices in the area (e.g., the area where not enough Ambient IoT devices are deployed to perform the task).

[0133] (2) Event Filter Information: It can be composed of Event Parameter Types and Event Parameter Values ​​that express the conditions for transmitting a Notification for the event to be subscribed to. According to one embodiment, the Event Parameter Type can be a Sensing Covered Area, and the Event Parameter Value can be the Geographical Position Information of the Ambient IoT device. The network can provide information to an external service provider on whether the Ambient IoT devices were uniformly deployed so that all areas of interest can be sensed when they were first deployed. Based on the location information of the Ambient IoT devices, the network can redeploy areas where insufficient Ambient IoT devices are deployed to perform the task among the areas of interest so that all areas of interest can be sensed. In one embodiment, the event parameter type may be Sensing Coverage in Cell, and the event parameter value may be The Number of Operable Ambient IoT Devices in a Cell or the Ratio of Operable Ambient IoT compared to Total Ambient IoT in a Cell. Deployed Ambient IoT devices may be unable to operate during the execution of a task for multiple reasons. Therefore, a sensing hole may occur in a specific area.Accordingly, the network can provide information related to the occurrence of sensing holes to external service providers and redeploy new Ambient IoT devices in specific areas to ensure that all areas of interest are within sensing coverage. The external service provider can determine specific values ​​(e.g., thresholds) based on the purpose and importance of the task, and send a notification to the external service provider when the specified value is met.

[0134] (3) Event Reporting Information: In one embodiment, information related to reporting on events may be defined, such as at least one of whether reporting on events is to be done periodically, how many times at most, or by when.

[0135] a. Event Reporting Mode: Reporting modes such as maximum number of reports and periodic reporting can be defined.

[0136] b. Immediate Reporting Flag: Can be used when immediate reporting is required when an event occurs.

[0137] c. Maximum Number of Reports / Maximum Duration of Reporting: After subscribing to the event exposure service, the maximum number of reports or duration can be set.

[0138] In one embodiment, event reporting information may include an immediate reporting flag depending on the urgency of the task, which may be set to various values ​​depending on the purpose of the task. Furthermore, since Ambient IoT devices typically have their communication modules turned off and wake up at specific times to communicate in order to minimize battery consumption, Ambient IoT devices may be configured to report when their communication modules are turned on and communication is possible.

[0139] (4) Target of Event Reporting: This may be a target of an event to be observed. For example, at least one of a UE, a PDU Session, a group of UE(s), or any UE may be included. In one embodiment, the target of event reporting may include at least one of the number of operable Ambient IoT devices, the sensing area of ​​each Ambient IoT device (Geographical Positioning of Ambient IoT Device), or the ratio of operable Ambient IoT devices to the total number of Ambient IoT devices in a cell.

[0140] (5) Notification Target Address and / or Notification Correlation ID): The address and / or subscription-related ID of the NF that will receive the notification when an event occurs can be defined. If an external service provider and / or other NFs within the 5GC send a subscription request on behalf of another NF that will receive the event, they can also send their own address to change the address and subscription information of the NF that will receive the event.

[0141] (6) Expiry Time: The duration of the subscription can be defined.

[0142] FIG. 5 illustrates a procedure for subscribing to a Monitoring Coverage of Interesting Area (CCA) Event Exposure Service for managing Ambient IoT devices in a wireless communication system according to an embodiment of the present disclosure.

[0143] Referring to FIG. 5, FIG. 5 may assume an embodiment in which a header exists that aggregates or collates information transmitted by Ambient IoT devices within each cell. For example, the header node (hereinafter referred to as the header) may be another Ambient IoT device or a terminal such as a smartphone. The header can communicate with the BS (Base Station) and the Ambient IoT devices it manages.

[0144] In Step 1, an external service provider (hereinafter referred to as AF) may request the network to subscribe to an event exposure service (Monitoring Coverage of Interesting Area) to be notified whether the deployed Ambient IoT devices are uniformly deployed to perform a task (e.g., deployed without sensing holes in an area of ​​interest) or whether the number of operating Ambient IoT devices falls below a certain number and the task cannot be performed. To subscribe to the event exposure service, AF may include the above-described information in a message transmitted to the core network (e.g., 5GC).

[0145] In step 2, the network that has received a request to subscribe to the AF's event exposure service can store related information on the network for future service subscription management. (The event exposure service subscription service requested by the AF can be performed by an existing NF (e.g., UDM or AMF) via the NEF, or can be processed by a newly designed NF for Ambient IoT devices.) At this time, the ID of the AF that requested the service subscription and the ID of the TASK performed by the Ambient IoT devices can be stored together.

[0146] In Step 3, the core network (e.g., 5GC) may send a report request message to at least one BS covering the area where the Ambient IoT devices are deployed. The report request message may include information requested by the AF.

[0147] In step 4, the BS can send a report command message to the headers managing the Ambient IoT devices. For example, the report command message may be a message instructing the BS to the Ambient IoT devices to report information requested by the AF. Accordingly, the report command message may include information requested by the AF.

[0148] In step 5, each header can instruct the member Ambient IoT devices it is responsible for to report based on the report command message received from the BS. The header can process the information requested by the AF and transmit it to the member Ambient IoT devices. In one embodiment, the Ambient IoT devices can operate in Power Saving Mode (PSM) to minimize battery power consumption. For example, PSM can be an operation mode in which the communication module is turned off for a certain period of time to reduce standby power consumption, and then all Ambient IoT devices and headers turn on the communication module and perform communication at a predetermined time (Rendezvous Time).

[0149] In step 6, member Ambient IoT devices can periodically report to the header based on event reporting information.

[0150] In step 7, the header can be compiled with event reports received from member Ambient IoT devices.

[0151] In step 8, the header can transmit the collected information to the AF via the BS and the core network. The collected information may be simply a compilation of information received from member Ambient IoT devices. Alternatively, the collected information may be information processed using averages, sums, and / or ratios based on information contained in event reports received from member Ambient IoT devices.

[0152] If the event reporting information in step 9 includes an immediate reporting request indication (e.g., an immediate reporting flag), when the target event occurs, the member Ambient IoT device can immediately transmit the event report received from the member Ambient IoT device to the header.

[0153] In step 10, the header can immediately transmit event reports received from member Ambient IoT devices to the AF via the BS and the core network. For example, the header can transmit each event report received from member Ambient IoT devices to the AF via the BS and the core network, without compiling each event report.

[0154] FIG. 6 illustrates an example of a case where no header exists in each cell in a wireless communication system according to an embodiment of the present disclosure.

[0155] In Step 1, an external service provider (hereinafter referred to as AF) may request the network to subscribe to an event exposure service (Monitoring Coverage of Interesting Area) to be notified whether the deployed Ambient IoT devices are uniformly deployed to perform a task (e.g., deployed without sensing holes in an area of ​​interest) or whether the number of operating Ambient IoT devices falls below a certain number and the task cannot be performed. To subscribe to the event exposure service, AF may include the above-described information in a message transmitted to the core network (e.g., 5GC).

[0156] In step 2, the network that has received a request to subscribe to the AF's event exposure service can store related information on the network for future service subscription management. (The event exposure service subscription service requested by the AF can be performed by an existing NF (e.g., UDM or AMF) via the NEF, or can be processed by a newly designed NF for Ambient IoT devices.) At this time, the ID of the AF that requested the service subscription and the ID of the TASK performed by the Ambient IoT devices can be stored together.

[0157] In Step 3, the core network (e.g., 5GC) may send a report request message to at least one BS covering the area where the Ambient IoT devices are deployed. The report request message may include information requested by the AF.

[0158] In step 4, the BS can send a report command message to the Ambient IoT devices. For example, the report command message may be a message instructing the BS to the Ambient IoT devices to report information requested by the AF. Accordingly, the report command message may include information requested by the AF.

[0159] In step 5, as an example, the Ambient IoT devices may operate in Power Saving Mode (PSM) to minimize battery power consumption. For example, PSM may be an operation mode in which the communication module is powered off for a certain period of time to reduce standby power consumption, and then all Ambient IoT devices power on the communication module and perform communication at a predetermined time (Rendezvous Time). In step 4, a message instructing the BS to report to the Ambient IoT devices may also be transmitted while in PSM mode. According to the event reporting information, member Ambient IoT devices may periodically transmit event reports to the BS.

[0160] In step 6, the BS or core network (e.g., 5GC) may aggregate reports received from Ambient IoT devices and report them to the AF. The information aggregated by the BS or core network (e.g., 5GC) may be aggregated information received from member Ambient IoT devices. Alternatively, the information aggregated by the BS or core network (e.g., 5GC) may be information processed using averages, sums, and / or ratios based on information included in event reports received from member Ambient IoT devices.

[0161] In step 7, if the event reporting information includes an immediate reporting request indication (e.g., an immediate reporting flag), when a target event occurs, the Ambient IoT device can immediately transmit the event report to the AF via the BS and the core network. For example, the BS or the core network can transmit each event report received from member Ambient IoT devices to the AF without compiling each event report.

[0162] Figure 7 illustrates the configuration of a terminal according to embodiments of the present disclosure.

[0163] A terminal according to one embodiment of the present disclosure may include a processor (720) that controls the overall operation of the terminal, a transceiver (700) including a transmitter and a receiver, and a memory (710). Of course, the terminal is not limited to the above-described examples, and the terminal may include more or fewer components than those illustrated in FIG. 7.

[0164] According to one embodiment of the present disclosure, the transceiver (700) can transmit and receive signals with a base station, network entities, or other terminals. The signals transmitted and received with the base station or network entities may include control information and data. In addition, the transceiver (700) can receive signals via a wireless channel, output them to the processor (720), and transmit the signals output from the processor (720) via the wireless channel.

[0165] According to one embodiment of the present disclosure, the processor (720) can control the terminal to perform any one of the operations described above. Meanwhile, the processor (720), the memory (710), and the transceiver (700) do not necessarily have to be implemented as separate modules, and of course, they can be implemented as a single component in the form of a single chip. In addition, the processor (720) and the transceiver (700) can be electrically connected. In addition, the processor (720) can include an Application Processor (AP), a Communication Processor (CP), a circuit, an application-specific circuit, a controller, or at least one processor.

[0166] According to one embodiment of the present disclosure, the memory (710) can store data such as basic programs, application programs, and setting information for the operation of the terminal. In particular, the memory (710) provides the stored data upon request of the processor (720). The memory (710) can be configured as a storage medium or a combination of storage media such as a ROM, a RAM, a hard disk, a CD-ROM, and a DVD. In addition, there can be a plurality of memories (710). In addition, the processor (720) can perform the above-described embodiments based on a program for performing the above-described embodiments of the present disclosure stored in the memory (710).

[0167] FIG. 8 is a diagram showing the configuration of a base station according to an embodiment of the present disclosure.

[0168] The base station of FIG. 8 may refer to the RAN node or BS described in the embodiments of FIGS. 1 to 6.

[0169] A base station according to one embodiment of the present disclosure may include a processor (820) that controls the overall operation of the base station, a transceiver (800) including a transmitter and a receiver, and a memory (810). Of course, the present invention is not limited to the above example, and the base station may include more or fewer components than those illustrated in FIG. 8.

[0170] According to one embodiment of the present disclosure, the transceiver (800) can transmit and receive signals with at least one of a terminal, another base station, or a network entity. The transmitted and received signals can include at least one of control information and data.

[0171] According to one embodiment of the present disclosure, the processor (820) can control the overall operation of the base station to perform any one of the operations described above. Meanwhile, the processor (820), the transceiver (800), and the memory (810) do not necessarily have to be implemented as separate modules, and of course, they can be implemented as a single component in the form of a single chip. In addition, the processor (820) can be an Application Processor (AP), a Communication Processor (CP), a circuit, an application-specific circuit, or at least one processor. The transceiver (800) can include at least one communication interface for transmitting and receiving signals wired / wirelessly to and from a terminal, another base station, or a network entity.

[0172] According to one embodiment of the present disclosure, the memory (810) can store data such as basic programs, application programs, and setting information for the operation of the corresponding base station. In addition, the memory (810) provides the stored data upon request of the processor (820). The memory (810) can be configured as a storage medium or a combination of storage media such as a ROM, a RAM, a hard disk, a CD-ROM, and a DVD. In addition, there can be a plurality of memories (810). In addition, the processor (820) can perform at least one of the above-described embodiments based on a program for performing an operation according to at least one of the above-described embodiments of the present disclosure stored in the memory (810).

[0173] FIG. 9 illustrates a configuration of a network entity according to embodiments of the present disclosure.

[0174] The network entity of FIG. 9 may mean at least one network entity constituting the core network described in the embodiments of FIGS. 1 to 6.

[0175] A network entity according to one embodiment of the present disclosure may include a processor (920) that controls the overall operation of the network entity, a transceiver (900) including a transmitter and a receiver, and a memory (910). Of course, the present invention is not limited to the above-described examples, and the network entity may include more or fewer components than those illustrated in FIG. 9.

[0176] According to one embodiment of the present disclosure, the transceiver (900) can transmit and receive signals with at least one of other network entities or terminals. The signals transmitted and received with at least one of the other network entities or terminals may include control information and data.

[0177] According to one embodiment of the present disclosure, the processor (920) can control a network entity to perform any one of the operations described above. Meanwhile, the processor (920), the memory (910), and the transceiver (900) do not necessarily have to be implemented as separate modules, and can of course be implemented as a single component in the form of a single chip. In addition, the processor (920) and the transceiver (900) can be electrically connected. In addition, the processor (920) can include an Application Processor (AP), a Communication Processor (CP), a circuit, an application-specific circuit, a controller, or at least one processor.

[0178] According to one embodiment of the present disclosure, the memory (910) can store data such as basic programs, application programs, and setting information for the operation of a network entity. In particular, the memory (910) provides the stored data upon request of the processor (920). The memory (910) can be configured as a storage medium or a combination of storage media such as a ROM, a RAM, a hard disk, a CD-ROM, and a DVD. In addition, there can be a plurality of memories (910). In addition, the processor (920) can perform the above-described embodiments based on a program for performing the above-described embodiments of the present disclosure stored in the memory (910).

[0179] It should be noted that the aforementioned configuration diagrams, examples of control / data signal transmission methods, examples of operational procedures, and configuration diagrams are not intended to limit the scope of the present disclosure. That is, not all components, entities, or operational steps described in the embodiments of the present disclosure should be construed as essential components for implementing the disclosure, and implementations may be made without detracting from the essence of the disclosure even if only some components are included. Furthermore, each embodiment may be combined and operated as needed. For example, parts of the methods proposed in the present disclosure may be combined to operate network entities and terminals.

[0180] The operations of the base station or terminal described above can be realized by providing a memory device storing the corresponding program code in any component within the base station or terminal device. That is, the control unit of the base station or terminal device can execute the operations described above by reading and executing the program code stored in the memory device using a processor or CPU (Central Processing Unit).

[0181] The various components and modules of the entity, base station or terminal device described in this specification may be operated using hardware circuits, such as logic circuits based on complementary metal oxide semiconductors, firmware, software and / or hardware and firmware and / or software embedded in a machine-readable medium. For example, various electrical structures and methods may be implemented using electrical circuits such as transistors, logic gates and application-specific semiconductors.

[0182] When implemented in software, a computer-readable storage medium storing one or more programs (software modules) may be provided. The one or more programs stored in the computer-readable storage medium are configured for execution by one or more processors within an electronic device. The one or more programs include instructions that cause the electronic device to execute methods according to embodiments described in the claims or specification of the present disclosure.

[0183] These programs (software modules, software) may be stored in random access memory, non-volatile memory including flash memory, read only memory (ROM), electrically erasable programmable read only memory (EEPROM), magnetic disc storage device, compact disc ROM (CD-ROM), digital versatile discs (DVDs) or other forms of optical storage device, magnetic cassette. Or, they may be stored in a memory configured as a combination of some or all of these. In addition, each configuration memory may be included in multiple numbers.

[0184] Additionally, the program may be stored in an attachable storage device that is accessible via a communication network such as the Internet, an intranet, a local area network (LAN), a wide local area network (WLAN), a storage area network (SAN), or a combination thereof. Such a storage device may be connected to a device performing an embodiment of the present disclosure via an external port. Additionally, a separate storage device on the communication network may be connected to a device performing an embodiment of the present disclosure.

[0185] In the specific embodiments of the present disclosure described above, components included in the disclosure are expressed singularly or plurally, depending on the specific embodiment presented. However, the singular or plural expressions are selected to suit the presented situation for convenience of explanation, and the present disclosure is not limited to singular or plural components. Components expressed in plural may be composed of singular elements, or components expressed in singular may be composed of plural elements.

[0186] While the detailed description of the present disclosure has described specific embodiments, it should be understood that various modifications are possible 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 determined not only by the scope of the claims described below but also by equivalents thereof. In other words, it will be apparent to those skilled in the art that other modifications based on the technical idea of ​​the present disclosure are possible. In addition, the above-described embodiments can be combined and operated with each other as needed. For example, parts of the methods proposed in the present disclosure can be combined with each other to operate a base station and a terminal. In addition, although the above-described embodiments have been presented based on a 5G, NR system, other modifications based on the technical idea of ​​the above-described embodiments can be implemented with other systems such as LTE, LTE-A, and LTE-A-Pro systems.

Claims

1. A method performed by a first network entity of a wireless communication system, A step of receiving a first request message regarding an ambient IoT (internet of things) service from a second network entity; A step of transmitting a second request message to the base station for requesting reports from ambient IoT devices based on the first request message; A step of receiving, from the base station, responses of the ambient IoT devices to the second request message or aggregated information of the responses; and A method comprising the step of transmitting a response message to the first request message to the second network entity.

2. In paragraph 1, A method, wherein the first request message includes at least one of local information related to the ambient IoT devices or information regarding the number of the ambient IoT devices.

3. In paragraph 1, A method wherein, when the responses are received from the base station, the responses are collated at the first network entity.

4. In paragraph 1, The above first network entity is a network exposure function (NEF) entity, A method wherein the second network entity is an AF (application function) entity.

5. In a method performed by a base station of a wireless communication system, A step of receiving a first request message from a first network entity for requesting reporting of ambient IoT (internet of things) devices; A step of transmitting the first request message to the above ambient IoT devices; A step of receiving responses from the ambient IoT devices to the first request message from the ambient IoT devices; and comprising a step of transmitting the responses or the aggregated information of the responses to the first network entity; A method wherein the first request message is based on a request from a second network entity regarding an ambient IoT service.

6. In paragraph 5, A method wherein the second request message is based on at least one of local information related to the ambient IoT devices or information regarding the number of the ambient IoT devices.

7. In paragraph 5, A method wherein, when transmitting the responses to the first network entity, the responses are collated at the first network entity.

8. In paragraph 5, The above first network entity is a network exposure function (NEF) entity, A method wherein the second network entity is an AF (application function) entity.

9. In the first network entity of the wireless communication system, Transmitter and receiver; and At least one control unit connected to the above transceiver unit, At least one control unit: Receive a first request message regarding an ambient IoT (internet of things) service from a second network entity, Transmitting a second request message to the base station to request reports from ambient IoT devices based on the first request message; Receive, from the base station, responses of the ambient IoT devices to the second request message or aggregated information of the responses, and The second network entity is configured to transmit a response message to the first request message, and the first network entity.

10. In paragraph 9, A first network entity, wherein the first request message includes at least one of local information related to the ambient IoT devices or information regarding the number of the ambient IoT devices.

11. In paragraph 9, A first network entity, wherein when the responses are received from the base station, the responses are collated at the first network entity.

12. In paragraph 9, The above first network entity is a network exposure function (NEF) entity, The first network entity, wherein the second network entity is an AF (application function) entity.

13. In a base station of a wireless communication system, Transmitter and receiver; and At least one control unit connected to the above transceiver unit, At least one control unit: A step of receiving a first request message from a first network entity for requesting reporting of ambient IoT (internet of things) devices; Transmitting the first request message to the above ambient IoT devices, Receive responses from the ambient IoT devices to the first request message, and is configured to transmit the responses or aggregated information of the responses to the first network entity; A base station, wherein the first request message is based on a request from a second network entity regarding an ambient IoT service.

14. In paragraph 13, A base station, wherein the second request message is based on at least one of local information related to the ambient IoT devices or information regarding the number of the ambient IoT devices.

15. In paragraph 13, When transmitting the responses to the first network entity, the responses are collated at the first network entity, The above first network entity is a network exposure function (NEF) entity, A base station, wherein the second network entity is an AF (application function) entity.

Images