Method and apparatus for providing identification information for internet of things device in communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. The present disclosure can be applied to intelligent services (for example, smart homes, smart buildings, smart cities, smart cars or connected cars, healthcare, digital education, retail businesses, security- and safety-related services, and the like) on the basis of 5G communication technology and IoT-related technology. The present disclosure relates to a method and an apparatus for providing identification information for an IoT device in a communication system. According to an embodiment of the present disclosure, the method by which a network entity provides an IoT-based communication service in a wireless communication system comprises the steps of: checking IoT device identification information for identifying at least one IoT device for the IoT-based communication service; and transmitting, for the IoT-based communication service, the IoT device identification information to another network entity communicating with the network entity.

Description

Method and device for providing identification information for Internet of Things devices in a communication system

[0001] The present disclosure relates to a communication method and device for an Internet of Things (IoT) device in a communication system.

[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 present disclosure provides a method and apparatus for efficiently providing IoT device identification information for IoT-based communication services in a wireless communication system.

[0009] The present disclosure provides a method and apparatus capable of effectively providing a communication service using a device that does not use battery power or operates at low power in a wireless communication system.

[0010] In addition, the present disclosure provides a method and apparatus for efficiently allocating identification information for IoT devices in a communication environment in which a plurality of IoT devices are operated in a wireless communication system.

[0011] Additionally, the present disclosure provides a method and apparatus for efficiently allocating identification information for an Ambient IoT device in a wireless communication system.

[0012] According to an embodiment of the present disclosure, a method for a network entity to provide an IoT-based communication service in a wireless communication system includes a process of verifying IoT device identification information for identifying at least one IoT device for the IoT-based communication service, and a process of transmitting the IoT device identification information for the IoT-based communication service to another network entity communicating with the network entity.

[0013] In the above method, the IoT device identification information may include at least one of an identifier for identifying an MNO in the wireless communication system, an identifier for identifying a third party providing the IoT-based communication service, and an identifier for identifying a specific IoT device associated with the third party.

[0014] In the above method, the IoT device identification information may be assigned by the MNO or the third party server.

[0015] In the above method, the IoT device identification information can identify a group of multiple IoT devices.

[0016] In the above method, the IoT device identification information can be used for a location-based service of the at least one IoT device.

[0017] In addition, according to an embodiment of the present disclosure, a network entity providing an IoT-based communication service in a wireless communication system includes a transceiver, and a processor configured to identify IoT device identification information for identifying at least one IoT device for the IoT-based communication service, and to transmit the IoT device identification information for the IoT-based communication service to another network entity communicating with the network entity through the transceiver.

[0018] In addition, according to an embodiment of the present disclosure, an IoT device for an IoT-based communication service in a wireless communication system includes a transceiver, and a processor configured to identify IoT device identification information for identifying at least one IoT device for the IoT-based communication service, and to transmit and receive information related to the IoT-based communication service to and from another network entity through the transceiver based on the IoT device identification information.

[0019] FIG. 1 is a diagram showing an example configuration of a wireless communication system according to an embodiment of the present disclosure;

[0020] FIG. 2 is a diagram illustrating an example of a scenario using Ambient IoT in a communication system according to an embodiment of the present disclosure;

[0021] FIG. 3 is a diagram illustrating an example configuration of a Device ID, which is identification information of an Ambient IoT device according to an embodiment of the present disclosure;

[0022] FIG. 4 is a diagram for explaining a method of assigning a Device ID of an Ambient IoT device using a provisioned method according to an embodiment of the present disclosure;

[0023] FIG. 5 is a diagram for explaining a device ID allocation method of an Ambient IoT device using a self-configured method according to an embodiment of the present disclosure;

[0024] FIG. 6 is a flowchart illustrating a device ID allocation procedure using the provisioned method according to an embodiment of the present disclosure.

[0025] FIG. 7 is a flowchart illustrating a device ID allocation procedure using the self-configured method according to an embodiment of the present disclosure.

[0026] FIG. 8 is a diagram showing an example of a configuration of a terminal according to an embodiment of the present disclosure, and

[0027] FIG. 9 is a diagram illustrating a configuration of a base station or network entity according to an embodiment of the present disclosure.

[0028] 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 attached drawings. Furthermore, detailed descriptions of well-known functions and configurations that may obscure the gist of the present invention will be omitted.

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

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

[0031] The advantages and features of the present disclosure, and methods for achieving them, will become clearer with reference to the embodiments described below in detail 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.

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

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

[0034] Here, the term '~ unit' used in the present embodiment 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 play one or more processors. Accordingly, 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'. Additionally, components and '~parts' may be implemented to regenerate one or more CPUs within a device or secure multimedia card.

[0035] In this 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 component from other corresponding components and do not limit the corresponding components in any other respect (e.g., importance or order).

[0036] 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 an IoT device, 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 type 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.

[0037] 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 in a 5G core network (CN), and since a related description may refer to the standard specification (TS 23.501), a detailed description will be omitted.

[0038] In the following description, terms used to identify connection nodes, terms referring to network entities or network functions (NFs), terms referring to messages, terms referring to interfaces between network objects, terms referring to various identification information, etc. are provided as examples 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.

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

[0040] FIG. 1 is a diagram showing an example of a configuration of a wireless communication system according to an embodiment of the present disclosure, and FIG. 1 exemplifies the configuration of a 5G system.

[0041] Referring to FIG. 1, (R)AN ((Radio) Access Network) (101) is an entity that performs wireless resource allocation of a terminal (100), and may be at least one of an eNode B, a Node B, a BS (Base Station), an NG-RAN (NextGeneration Radio Access Network), a 5G-AN, a wireless access unit, a base station controller, or a node on a network.

[0042] The terminal (100) may include a UE (User Equipment), an NG UE (NextGeneration UE), an MS (Mobile Station), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing communication functions. Furthermore, while the embodiments of the present disclosure will be described below using a 5G system as an example, the embodiments of the present disclosure may also be applied to other communication systems with similar technical backgrounds. Furthermore, the embodiments of the present disclosure may 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.

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

[0044] According to one embodiment of the present disclosure, 5GC may include NFs illustrated in FIG. 1. In FIG. 1, 5GC may include network entities such as a User Plane Function (UPF) (102), an Authentication Server Function (AUSF) (104), an Access and Mobility Management Function (AMF) (105), a Session Management Function (SMF) (106), a Service Communication Proxy (SCP) (107), a Network Slice Selection Policy (NSSF) (108), a Network Exposure Function (NEF) (109), a Network Repository Function (NRF) (110), a Policy Control Function (PCF) (111), a Unified Data Management (UDM) (112), and an Application Function (AF) (113). In addition, UPF (102) may communicate with a data network (DN) (103), which is an external network such as the Internet, using a Nupf service. DN (103) may include AF of external network. For example, AF may exist as AF (113) within 5GC and AF included in DN (103) outside 5GC, and AF may be AF that communicates with UPF (102) in DN (103) outside 5GC. Description of entities among the above network entities that are not directly related to the present disclosure will be omitted for convenience. Of course, 5GC is not limited to the example of FIG. 1, and 5GC may include more or fewer NFs than NF illustrated in FIG. 1.

[0045] AMF (105) may be a network function that manages access and mobility of a terminal (UE) (100). For example, AMF (105) may perform network functions such as registration, connection, reachability, mobility management, access verification, authentication, and mobility event generation.

[0046] The SMF (106) may be a network function that manages a Packet Data Network (PDN) connection provided to a user equipment (UE) (100). The PDN connection may be referred to as a Packet Data Unit (PDU) Session. For example, the SMF (106) may perform network functions such as session management through establishing, modifying, and releasing sessions and maintaining a tunnel between the UPF (102) and the RAN (101) required therefor, allocation and management of the IP (Internet protocol) address of the UE, selection and control of a user plane, control of traffic processing in the UPF (102), and control of collection of charging data.

[0047] PCF (111) may be a network function that applies a mobile communication service provider's service policy, charging policy, and policy for PDU Session to the terminal (100).

[0048] The UDM (112) may be a network function that stores information about subscribers. For example, the UDM (112) may perform functions such as generating authentication information for 3GPP security, processing user identifiers (user IDs), managing a list of network functions supporting the terminal (100), and managing subscription information.

[0049] NEF (109) may have a function of providing information about the terminal (100) to a server outside the 5G network. In addition, NEF (109) may provide a function of providing information necessary for service to the 5G network and storing it in a Unified Data Repository (UDR) (not shown).

[0050] The UPF (102) may be a gateway that transmits user data (PDU) to the DN (103). More specifically, the UPF (102) may perform a data processing function so that data transmitted by the terminal (100) can be transmitted to an external network or data received from an external network can be transmitted to the terminal (100). For example, the UPF (102) 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 creation, buffering, etc.

[0051] NRF (110) can perform the function of discovering NF. AUSF (104) can perform terminal authentication in 3GPP access networks and non-3GPP access networks. NSSF (108) can perform the function of selecting a Network Slice Instance provided to the terminal. DN (103) can be a data network through which the terminal (100) transmits and receives data in order to use the network operator's service or a third-party service.

[0052] In the present disclosure, the terminal (100) may include an IoT device. In the present disclosure, the IoT device may include a device that does not use battery power or operates with very little power, and in the present disclosure, such an IoT device is referred to as an ambient IoT device (or simply Ambient IoT).

[0053] According to one embodiment of the present disclosure, an Ambient IoT Device may have no battery or may have very limited energy storage capabilities. The Ambient IoT Device may have at least one of the following characteristics:

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

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

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

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

[0058] - It has very low computational power, a very simple structure, and the size of the device is also very small.

[0059] - Does not have USIM (Universal Subscriber Identity Module) and does not include complex communication protocol stacks such as TCP / IP (Transmission Control Protocol / Internet Protocol)

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

[0061] In this disclosure, Ambient IoT devices can be divided into the following three types depending on whether there is a battery in the device and the form of communication used by the device.

[0062] Device Type DescriptionDevice Type A (TY_A) - No Energy Storage (Battery) - Independent signal generation / amplification not possibleDevice Type B (TY_B) - With Energy Storage (Battery) - Independent signal generation / amplification not possibleDevice Type C (TY_C) - With Energy Storage (Battery) - Independent signal generation / amplification possible (including active RF components)

[0063] In addition, in the present disclosure, Ambient IoT devices can have a connection topology classified into four types, as shown in the examples in [Table 2] below. In addition, the connection types of Ambient IoT devices in the present disclosure are not limited to the examples in [Table 2] below, and connection by various combinations of the connection topologies classified into four types is also possible.

[0064] Topology Type DescriptionTopology 1 (T1) - Connection between base station and Ambient IoT device (Base Station - Ambient IoT device)Topology 2 (T2) - Connection between base station and Ambient IoT device via intermediate node (Base Station - Intermediate node - Ambient IoT device)Topology 3 (T3) - Connection between base stations via auxiliary node and Ambient IoT device (Base Station - Assisting node - Ambient IoT device - Base Station)Topology 4 (T4) - Connection between terminal and Ambient IoT device (UE - Ambient IoT device)

[0065] FIG. 2 illustrates an example of a scenario utilizing Ambient IoT in a communication system according to an embodiment of the present disclosure.

[0066] The communication system of FIG. 2 may include a plurality of Ambient IoT devices (201) deployed in a mountainous area, at least one base station (202) capable of communicating with at least one of the Ambient IoT devices (201), a core network (203) to which the at least one base station (202) is connected, and a DN (205) including an AF (204) communicatively connected with the core network (203). In the example of FIG. 2, the basic functions and configuration of the DN (205) including the base station (202), the core network (203), and the AF (204) may refer to the example of FIG. 1.

[0067] Referring to FIG. 2, the Korea Forest Service or the National Fire Agency can deploy millions of Ambient IoT devices (201) on mountains for early detection of forest fires. Since the number of Ambient IoT devices (201) and the deployment area are vast and not easily accessible to humans, they are often deployed by air. Maintenance (e.g., battery replacement of Ambient IoT devices, replacement of broken parts, etc.) of Ambient IoT devices (201) deployed in this manner may be impossible for the reasons mentioned above. Once deployed, Ambient IoT devices (201) must operate and perform their duties for at least 10 years and at most 20 years. Therefore, it is important for Ambient IoT devices (201) to operate with little battery consumption. In the scenario of FIG. 2, the Ambient IoT devices (201) deployed after deployment can monitor fires around the mountain. Among the Ambient IoT devices (201), at least one Ambient IoT device that detects a fire transmits information notifying the occurrence of a fire to the NG-RAN (202) (in the case of a 5G network) using a wireless network, and the information can be transmitted to the AF (204) (e.g., a 3rd party server providing IoT services, such as a server of the National Fire Agency in the example of FIG. 2) via the 5G network (203) and the data network (205). As in the embodiment of FIG. 2, the Ambient IoT devices (201) can be deployed for the same purpose, such as notifying the occurrence of a fire, and the information notifying the occurrence of a fire and / or data related to the information can be transmitted to the AF (e.g., a 3rd party server) (204).Although the example in Fig. 2 illustrates a fire outbreak scenario in a mountain, Ambient IoT devices can also 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.

[0068] Embodiments of the present disclosure propose a method for allocating a device ID (or referred to as an Ambient IoT device ID) for an Ambient IoT device having the above-described characteristics. For example, devices operating according to the 3GPP standard can use SUPI (Subscription Permanent Identifier) / IMSI (International Mobile Subscriber Identity), which is identification information contained / stored in a USIM chip, as the ID of the corresponding device. However, Ambient IoT devices may not be able to use USIM, or the number of Ambient IoT devices may be too large for a mobile communication service provider to allocate a unique ID to each Ambient IoT device. Therefore, the present disclosure proposes a method for allocating a device ID suitable for the characteristics and / or purpose of use of Ambient IoT devices.

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

[0070] Since the number of Ambient IoT devices is large as in the scenario of FIG. 2, it may be efficient to group the Ambient IoT devices in order to control their operations. The Ambient IoT devices can be grouped according to their tasks, for example, based on the 3rd party provider of the AF that communicates with the Ambient IoT devices. The 3rd party provider can group the Ambient IoT devices for various reasons such as region, purpose, or number of Ambient IoT devices. In addition, grouping by the Ambient Device Type as exemplified in [Table 1] or the Connectivity Type as exemplified in [Table 2] is also possible, and Ambient IoT devices can be grouped according to specific use cases and business scenarios. The embodiment of FIG. 3 illustrates an example of one Device ID of an Ambient IoT device, and in addition to at least one combination of the various IDs exemplified in FIG. 3, various values ​​can be used as the Device ID of an Ambient IoT device.

[0071] In this embodiment, the definition of each of the fields (or elements or IDs) (301 to 308) that constitute the Device ID (300) of the Ambient IoT device is as shown in the example below. In the following description, the 3rd party provider can be understood as AF or a server of the 3rd party provider.

[0072] - MNO (mobile network operator) ID (301): Indicates the mobile carrier ID (i.e. network identifier) ​​used by third-party providers to communicate with Ambient IoT devices. The MNO ID (301) may include at least one of an MCC (Mobile Country Code) and an MNC (Mobile Network Code), or may consist of only an MNC.

[0073] - Enterprise ID (302): Indicates the company to which the 3rd party provider belongs. When performing work using multiple 3rd party servers, the Enterprise ID (302) can be used to identify all Ambient IoT devices belonging to the company.

[0074] - AF ID (303): This ID identifies a third-party provider / server. It can identify all Ambient IoT devices performing a single task or all Ambient IoT devices communicating with a single AF.

[0075] - Group ID (304): Since there are a large number of Ambient IoT devices, it is necessary to group them to control them. For this purpose, a Group ID can be used. Ambient IoT devices can be grouped based on various classification criteria such as purpose, capability, and status. In other words, the Ambient IoT device ID of Fig. 3 can be used to identify a group of Ambient IoT devices.

[0076] - Device Type ID (305): Ambient IoT can be classified into types A (TY_A), B (TY_B), and C (TY_C) as shown in the example in [Table 1] above, depending on battery capacity and communication capability. This is the ID that represents this. Ambient IoT devices can also be grouped by Device Type using this ID.

[0077] - Connectivity Type ID (306): 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 in [Table 2] above, depending on their ability to communicate with the network and UE, and their topology. This is the ID that represents this. Ambient IoT can also be grouped by Connectivity Type using this ID.

[0078] - Use Case Specific ID (307): This ID is 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 must report the location of the fire when it detects a fire. In other words, the location of the Ambient IoT device is important. At this time, 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. A 3rd party provider can identify the location of the Ambient IoT device with only the ID of the Ambient IoT device. This is one embodiment, and this ID can be utilized in various other use cases.

[0079] - Unique Device ID (308): This ID is a unique ID for distinguishing each Ambient IoT device. The Unique Device ID (308) can become a globally unique Device ID when used with at least one of IDs such as MNO ID (301), Enterprise ID (302), and AF ID (303). Since the number of Ambient IoT devices is so large, a 3rd party provider may arbitrarily assign a Unique Device ID (308) in a range of numbers, or may replace the Unique Device ID (308) with the manufacturing number of the Ambient IoT device. As an optional embodiment, the Unique Device ID (308) may be defined by the 3rd party provider as any value that can uniquely identify each Ambient IoT device.

[0080] The elements constituting the Device ID (300) of the above Ambient IoT device are only examples, and the elements of the Device ID (300) can be freely configured according to the purpose of use of the Ambient IoT device or the capabilities of the device. In addition, as in the examples of reference numbers 310 to 350, the Group ID of the Ambient IoT devices can be configured using various elements of the Device ID (300) in order to group the Ambient IoT devices. In addition, various elements not mentioned in the present embodiment may be added according to the purpose of use or function of the Ambient IoT device. Among the above elements, at least the AF ID (303) and the Unique Device ID (308) may be included in the Device ID (300) of the Ambient IoT device.

[0081] In an embodiment of the present disclosure, a method of assigning a Device ID (300) to an Ambient IoT device will be described.

[0082] Assigning a Device ID to an Ambient IoT device can be performed using at least one of the following methods a) to c).

[0083] a) Pre-Configured method

[0084] b) Provisioned method

[0085] c) Self-Configured method

[0086] The above Pre-Configured method is a method of assigning a Device ID before deploying an Ambient IoT device. The assignment of the Device ID (300) can be performed by a mobile communication service provider (i.e., MNO) or a third-party provider (i.e., AF). For example, it can be assigned to all Ambient IoT devices before deployment as follows. For example:<MNO ID><AF ID><TY_A> <t3><Serial No>The Device ID allocated as such includes the MNO ID (301), AF ID (303), Device Type of [Table 1] above, Topology of [Table 2] above, and Serial number of the Ambient IoT device.

[0087] FIG. 4 is a diagram for explaining a method of assigning a Device ID of an Ambient IoT device using the Provisioned method according to an embodiment of the present disclosure.

[0088] Ambient IoT devices can be partially assigned a Device ID by mobile carriers or third-party providers before deployment, similar to the pre-configured method described above. For example,<MNO ID><AF ID><TY_A> <t3><Serial No>can be allocated as follows. Afterwards, after Ambient IoT devices are deployed in the area through various means such as aviation, the Ambient IoT devices can receive the value provisioned by the 3rd party provider or mobile network operator (MNO) through the network to update / verify their own Device ID. For example, in the example of FIG. 4, as shown in reference numbers 401 to 405, the List of Tracking Areas (TA)s is set / mapped to at least one Area Code (AC) (AC_A, AC_B, AC_C, AC_D, AC_E), and the setting / mapping information is propagated to each Ambient IoT device through the NG-RAN through the network, and the Ambient IoT device that receives the setting / mapping information can update / verify its own Device ID by adding this value to the pre-configured Device ID. For example,<MNO ID><AF ID><AC_A><TY_A> <t3><Serial No>A Device ID configured as such can be assigned to an Ambient IoT deployed in an area with Area Code A (AC_A). This is only one embodiment, and various configuration / mapping information can be provisioned after Ambient IoTs are deployed and utilized as a Device ID.

[0089] FIG. 5 is a diagram for explaining a method of assigning a Device ID to an Ambient IoT device using the Self-Configured method according to an embodiment of the present disclosure.

[0090] Ambient IoT devices can be partially assigned a Device ID by mobile carriers or third-party providers before deployment, similar to the pre-configured method described above. For example,<MNO ID><AF ID><TY_A> <t3><Serial No>can be assigned as follows. Afterwards, after Ambient IoT devices are deployed through various means such as aviation, the Ambient IoT device can configure or update its Device ID value through various methods. The example of Fig. 5 illustrates two Use Cases. In the case of the forest fire detection Use Case with reference number 510, after all Ambient IoT devices are deployed, each Ambient IoT device can check / identify its own location using the GPS (Global Positioning System) sensor installed in its device. In this Use Case, it is important for the Ambient IoT device to know the location of the fire when it detects the fire. The Ambient IoT device can use its own location information as the Use Case Specific ID among the elements that make up the Device ID. For example, the Ambient IoT device can Self-Configure or update its Device ID as follows using its location information (e.g., 36.613012, 127.505038) through GPS. (In this case, the Device ID is<MNO ID><AF ID><TY_A> <t3><36.613012,127.505038> can be configured as follows.) At this time, since the location information of the Ambient IoT device itself can be a unique value, the Unique Device ID can be used instead of the Serial No. of the Ambient IoT device. The Use Case of reference number 520 in Fig. 5 is an example of a Use Case for tracking logistics in a logistics warehouse. In this case, each Ambient IoT device can sense the product ID of the logistics to be tracked using the sensor mounted on the Ambient IoT after being deployed in the logistics warehouse. In this Use Case, the current location of a product is important information. That is, in this Use Case, the ID of the product can be used as the Use Case Specific ID. Each Ambient IoT device can Self-Configure or update the Device ID as follows using the ID of the sensed product (e.g., 77712). (In this case, the Device ID is<MNO ID><AF ID><TY_A> <t3><77712> ) If the above product ID is a unique value, the Unique Device ID can be used instead of the Serial No of the Ambient IoT device, otherwise, the Device ID can be, for example,<MNO ID><AF ID><TY_A> <t3><77712><Serial No> It can be Self-Configured like this.

[0091] FIG. 6 is a flowchart illustrating a device ID allocation procedure using the provisioned method according to an embodiment of the present disclosure. The basic functions of each network entity in the example of FIG. 6 can be referenced from the example of FIG. 1.

[0092] Referring to FIG. 6, in step 600, all or some Ambient IoT devices may be pre-configured with a partial Device ID by an AF (server) of a mobile carrier or a 3rd Party Provider before being deployed in the field. The pre-configured partial Device ID may be elements whose values ​​do not change after the deployment of the Ambient IoT devices. For example, in the present embodiment, it is assumed that the partial Device ID includes at least one of the MNO ID, AF ID, Unique Device ID, Device Type ID, and Connectivity Type ID elements described in the example of FIG. 3. This is just one example, and various other elements may be pre-configured.

[0093] At step 601, Ambient IoT devices can be deployed in various sensing fields(es) such as airports, vehicles, people, mountains, factories, and shopping malls in various ways.

[0094] In step 602, a 3rd Party Provider (AF) or a mobile network operator (MNO) may transmit a Device ID Provisioning request message containing Device ID-related information to the AMF in order to update the Device IDs of the Ambient IoT devices. In this embodiment, for the convenience of explanation, the Device ID-related information is described as location-based information of each Ambient IoT device as an example. The provisioned Device ID-related information may be various information depending on the use case as well as the location information of the Ambient IoT device. For example, the Device ID-related information may utilize various information such as observed product information, local environment information, etc. This embodiment is described based on the embodiment of FIG. 4 described above. For example, the MNO / AF may transmit location information corresponding to each Area Code (AC) as the Device ID-related information to the AMF. The location information may be, for example, AC A: Latitude: 36.3-37.1, Longitude: 70-90.

[0095] In steps 603 and 604, the AMF resolves the location information received from the MNO / AF into a list of Tracking Areas (TAs). For example, the AMF changes the received location information, such as AC A: TA1, TA2, and TA3 as exemplified in the examples of FIGS. 4 and 5, and includes the information in a Device ID Provisioning Request message and transmits the message to the (R)AN responsible for each TA list. For example, a Device ID Provisioning Request message including AC A information may be transmitted to (R)AN 1, (R)AN 2, (R)AN 3, etc. in the corresponding region among multiple (R)ANs, and a Device ID Provisioning Request message including AC B information may be transmitted to (R)AN 4, (R)AN 5, (R)AN 6, etc. in the corresponding region. In the example of FIG. 6, one (R)AN is illustrated for convenience, but in reality, multiple (R)ANs may participate in the procedure of the present disclosure.

[0096] In step 605, each (R)AN may include the information received via the Device ID Provisioning Request message in a Device ID information message and broadcast it to the Ambient IoT devices. The Device ID information message may also be group-cast to the Ambient IoT devices.

[0097] In step 606, each Ambient IoT device can update its own Device ID using the information received through the Device ID information message and the received information (AC_A) to its pre-configured Device ID. For example, the updated Device ID may include the AC_A.<MNO ID><AF ID><AC_A><TY_A> <t3><Serial No>It can be composed as follows.

[0098] In step 607, each Ambient IoT device may include its updated Device ID in a Device ID Provisioning Response message and transmit it to the MNO / AF. Optionally, step 607 may be omitted depending on the use case.

[0099] In step 608, the MNO / AF that received the updated Device ID through the Device ID Provisioning Response message from each Ambient IoT updates the subscription information of each Ambient IoT.

[0100] In step 609, when the tasks assigned to the Ambient IoT(ies) change, or when changes occur in tasks or configurations, such as sensing report counts or sensing report data contents, the AF / MNO can include these in the TASK CHANG REQUET message and transmit them to all or some Ambient IoT device(s).At this time, when a change is limited to a specific Area Code, for example, in the case of a use case that measures precipitation, if heavy rain is expected in the southern region, the number of reports of precipitation per day is changed from 1 to 3 for only the Ambient IoT devices deployed in the southern region. Or, a device transmits a TASK CHANG REQUET message containing certain information (for example, the number of reports when the measured amount of rain is over a certain value, when the measured temperature is over or under a certain value, etc.) to the Ambient IoT devices under certain circumstances (for example, when the location of the devices is changed due to heavy rain, when the sensor function is abnormal due to a fire in the vicinity, etc.) or certain conditions (for example, when the measured amount of rain is over a certain value, when the measured temperature is over or under a certain value, etc.), and the Ambient IoT device that receives the message compares the Area Code information included in the Device ID of the received TASK CHANG REQUET message with the Area information set in the Ambient IoT device, and based on the comparison result, That is, if the Area information set in the Ambient IoT device is related to the Area Code included in the Device ID of the received TASK CHANG REQUET message, it is confirmed that the received TASK CHANG REQUET message is a TASK CHANG REQUET message for the Ambient IoT device, and the Ambient IoT device can update the setting information (number of precipitation reports) based on the information included in the received TASK CHANG REQUET message. For example, the Ambient IoT device can change the reporting from once a day to once every two days in the Gangwon-do region where a drought is expected.At this time, the TASK CHANGE REQUEST message can be selectively transmitted only to some regions, such as Area Code B in Gangwon-do and Area Code D in the southern region, for example. In addition, even if the TASK CHANGE REQUEST message is transmitted to all Ambient IoT devices nationwide, a different TASK can be assigned to each AC. For example, if the Ambient IoT device includes a multi-functional sensor, for example, AC_A: temperature measurement, AC_B: rainfall measurement, AC_C: no change, AC_D: forest fire detection, etc., the AF / MNO can assign a different TASK to each AC to the Ambient IoT devices, and the Ambient IoT devices that receive this can perform the TASK assigned to their AC.

[0101] In step 610, each Ambient IoT device can perform its assigned task and send reports and notifications to the MNO / AF. Examples include forest fire detection and daily rainfall reporting.

[0102] In the example of Fig. 6, a provisioned device ID allocation method based on the location of an Ambient IoT device is described as an example, but in various use cases, various information can be provisioned to the Ambient IoT device, and the operation of each Ambient IoT device and related NFs can be changed accordingly.

[0103] FIG. 7 is a flowchart illustrating a device ID assignment procedure using the self-configured method according to an embodiment of the present disclosure. The basic functions of each network entity in the example of FIG. 7 may be referenced from the example of FIG. 1.

[0104] In step 700, all or some Ambient IoT devices may be pre-configured with a partial Device ID by a mobile network operator (MNO) or a third-party provider (AF) server before being deployed in the field. The pre-configured partial Device ID may be elements whose values ​​do not change after the deployment of the Ambient IoT devices. For example, in the present embodiment, it is assumed that the partial Device ID includes at least one of the MNO ID, AF ID, Unique Device ID, Device Type ID, and Connectivity Type ID elements described in the example of FIG. 3. This is just one example, and various other elements may be pre-configured.

[0105] At step 701, Ambient IoT devices can be deployed in various sensing fields(es) such as airports, vehicles, people, mountains, factories, and shopping malls in various ways.

[0106] In step 702, each Ambient IoT device senses its surroundings according to its task after being deployed. For example, a device performing forest fire surveillance can sense its location information using GPS, and a device tracking the location of a product in a logistics warehouse can sense the ID of the product. For example, each Ambient IoT device can update its pre-configured Device ID with the sensed location information (36.613012, 127.505038) using the information it senses. For example, the Device ID including the location information is<MNO ID><AF ID><TY_A> <t3>It can be updated like <36.613012,127.505038>.

[0107] In step 703, each Ambient IoT device may include its updated Device ID in a Device ID Update message and transmit it to the MNO / AF. Optionally, step 703 may be omitted depending on the use case.

[0108] In step 704, the MNO / AF, which has received the updated Device ID from the Ambient IoT devices through the Device ID Provisioning Response message, updates the subscription information of each Ambient IoT.

[0109] In step 705, when the tasks assigned to Ambient IoT devices change, or when there is a change in tasks or configurations such as the number of sensing reports or the content of sensing report data, the AF / MNO can include this in the TASK CHANG REQUET message and transmit it to all Ambient IoT devices. In addition, depending on the use case, the area code can be divided and transmitted to the Ambient IoT devices according to the location of each Ambient IoT device, as in the example of FIG. 6. The Ambient IoT devices that receive the TASK CHANG REQUET message can update their Device IDs using the received information, as in the example of FIG. 6. At this time, when a change is limited to a specific Area Code, for example, in the case of a use case that measures precipitation, if heavy rain is expected in the southern region, the number of daily precipitation reports can be changed from 1 report to 3 reports only for Ambient IoT devices deployed in the southern region, or in an area where drought is expected, the number of reports can be changed from 1 report to 3 reports per day. At this time, the TASK CHANGE REQUEST can be selectively transmitted only to, for example, Area Code B, an area expected to experience drought, and Area Code D, a southern region. In addition, even if the TASK CHANGE REQUEST is transmitted to all Ambient IoT devices nationwide, a different TASK can be assigned to each AC.For example, if an Ambient IoT device includes a multi-functional sensor, for example, AC_A: temperature measurement, AC_B: rainfall measurement, AC_C: no change, AC_D: forest fire detection, etc., the AF / MNO can assign different tasks to each AC to the Ambient IoT devices, and the Ambient IoT devices that receive this can perform the tasks assigned to their AC.

[0110] In step 706, each Ambient IoT device can perform its assigned task and send reports and notifications to the MNO / AF. Examples include wildfire detection and daily rainfall reporting.

[0111] In the embodiment of FIG. 7, a self-configured device ID assignment method based on the location of an Ambient IoT device is described as an example, but in various use cases, Ambient IoT devices can sense various information and update their own device IDs, and accordingly, each Ambient IoT device and related NFs can change their operations.

[0112] FIG. 8 is a diagram illustrating an example of a configuration of a terminal according to an embodiment of the present disclosure. The terminal of FIG. 8 may include an IoT device.

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

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

[0115] According to one embodiment of the present disclosure, the processor (801) can control the operation of the terminal to perform at least one operation among the embodiments of FIGS. 1 to 7 described above. Meanwhile, the processor (801), the memory (803), and the transceiver (803) 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 (801) and the transceiver (803) can be electrically connected. In addition, the processor (801) can be an Application Processor (AP), a Communication Processor (CP), a circuit, an application-specific circuit, or at least one processor.

[0116] According to one embodiment of the present disclosure, the memory (803) can store data such as basic programs, application programs, and setting information for the operation of the terminal. In particular, the memory (510) provides the stored data according to a request from the processor (801). The memory (510) 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 (803). In addition, the processor (801) can perform at least one of the above-described embodiments based on a program for performing the above-described embodiments of the present disclosure stored in the memory (510).

[0117] FIG. 9 is a diagram illustrating a configuration of a base station or network entity according to an embodiment of the present disclosure.

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

[0119] According to one embodiment of the present disclosure, the transceiver (903) can transmit and receive signals via wired / wireless communication with at least one of other network entities or terminals. The signals transmitted and received with at least one of other network entities or terminals may include at least one of control information and data. If the network entity of FIG. 9 is a base station, the transceiver (903) may include a transceiver for transmitting and receiving wireless signals with the terminal, and a transceiver or communication interface for transmitting and receiving signals with other network entities in the core network.

[0120] According to one embodiment of the present disclosure, the processor (901) can control a network entity to perform at least one operation among the embodiments of FIGS. 1 to 7 described above. Meanwhile, the processor (901), the memory (905), and the transceiver (903) do not necessarily have to be implemented as separate modules, and may of course be implemented as a single component in the form of a single chip. In addition, the processor (901) and the transceiver (903) may be electrically connected. In addition, the processor (901) may be an Application Processor (AP), a Communication Processor (CP), a circuit, an application-specific circuit, or at least one processor.

[0121] According to one embodiment of the present disclosure, the memory (905) can store data such as basic programs, application programs, and setting information for the operation of the network entity. In particular, the memory (905) provides the stored data upon request of the processor (620). The memory (905) 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 (905). In addition, the processor (901) can perform at least one of the above-described embodiments based on a program for performing the above-described embodiments of the present disclosure stored in the memory (905).

[0122] 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 within a scope that does not detract 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.

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

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

[0125] 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 the embodiments described in the claims or specification of the present disclosure.

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

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

[0128] In the specific embodiments of the present disclosure described above, components included in the disclosure are expressed in the singular or plural form, 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 the plural form may be composed of singular elements, or components expressed in the singular form may be composed of plural elements.

[0129] Meanwhile, although the detailed description of the present disclosure has described specific embodiments, it is obvious 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 following claims but also by equivalents of the scope of the claims. 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, each of the above 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 embodiments have been presented based on a 5G, NR system, other modifications based on the technical idea of ​​the above embodiments can be implemented with other systems such as LTE, LTE-A, and LTE-A-Pro systems.

[0130] While the detailed description of this disclosure has described specific embodiments, it should be understood that various modifications are possible without departing from the scope of this disclosure. Therefore, the scope of this disclosure should not be limited to the described embodiments, but should be defined not only by the scope of the claims described below, but also by equivalents thereof.

Claims

1. In a method for a network entity to provide IoT (internet of things)-based communication services in a wireless communication system, A process for verifying IoT device identification information for identifying at least one IoT device for the IoT-based communication service; and A method comprising the step of transmitting the IoT device identification information for the IoT-based communication service to another network entity communicating with the network entity.

2. In paragraph 1, The above IoT device identification information is: An identifier for identifying a mobile network operator (MNO) in the above wireless communication system; An identifier for identifying a third party providing the IoT-based communication service, and A method comprising at least one identifier for identifying a particular IoT device associated with said third party.

3. In paragraph 2, A method in which the above IoT device identification information is allocated by the MNO or the third party server.

4. In paragraph 1, The above IoT device identification information is a method for identifying a group of multiple IoT devices.

5. In paragraph 1, A method in which the above IoT device identification information is used for location-based services of at least one IoT device.

6. In a network entity that provides IoT (Internet of Things)-based communication services in a wireless communication system, Transmitter and receiver; and Verify IoT device identification information for identifying at least one IoT device for the IoT-based communication service, A network entity comprising a processor configured to transmit, through said transceiver, said IoT device identification information to another network entity communicating with said network entity for said IoT-based communication service.

7. In paragraph 6, The above IoT device identification information is: An identifier for identifying a mobile network operator (MNO) in the above wireless communication system; An identifier for identifying a third party providing the IoT-based communication service, and A network entity comprising at least one identifier for identifying a particular IoT device associated with said third party.

8. In paragraph 7, The above IoT device identification information is a network entity assigned by the MNO or the third party server.

9. In paragraph 6, The above IoT device identification information is a network entity that identifies a group of multiple IoT devices.

10. In paragraph 6, The above IoT device identification information is a network entity used for location-based services of at least one IoT device.

11. In an IoT device for IoT (internet of things)-based communication service in a wireless communication system, Transmitter and receiver; and Verify IoT device identification information for identifying at least one IoT device for the IoT-based communication service, An IoT device including a processor configured to transmit and receive information related to the IoT-based communication service with another network entity based on the IoT device identification information through the transceiver.

12. In paragraph 11, The above IoT device identification information is: An identifier for identifying a mobile network operator (MNO) in the above wireless communication system; An identifier for identifying a third party providing the IoT-based communication service, and An IoT device comprising at least one identifier for identifying a particular IoT device associated with said third party.

13. In paragraph 12, The IoT device identification information is assigned to the IoT device by the MNO or the third party server.

14. In paragraph 11, The above IoT device identification information is an IoT device that identifies a group of multiple IoT devices.

15. In paragraph 11, The IoT device identification information is an IoT device used for location-based services of at least one IoT device.

Images