Environmental IoT management

Abstract

The embodiment of the invention relates to equipment, a method and a device for environmental Internet of Things (IoT) management and a computer readable storage medium. A method includes receiving, at a first device, configuration information about an Internet of Things (IoT) service from a second network device, the IoT service being subscribed by the IoT device, the IoT device being attached to the first network device; and creating a device context of the IoT device based at least on the configuration information.

Description

TECHNICAL FIELD

[0001] Various example embodiments of the present disclosure relate generally to the field of telecommunications, and more specifically, to methods, devices, apparatuses, and computer-readable storage media for ambient Internet of Things (IoT) management. BACKGROUND

[0002] IoT technology is expected to greatly change the prospects of various industries. Ambient IoT (AIoT) is a promising area in the fifth generation mobile communication technology (5G) New Radio (NR) and academia. Ambient IoT refers to IoT that does not have a power and energy source. Specifically, ambient IoT terminal nodes (also referred to as ambient IoT devices or tags) obtain energy from the environment. For example, ambient IoT devices based on radio electromagnetic energy harvesting technology can capture and collect energy by collecting radio waves to accomplish data collection, transmission, and distributed computing, etc. Therefore, there is a need to manage ambient IoT devices. SUMMARY

[0003] Embodiments of the present disclosure provide one or more network devices, one or more corresponding methods, and one or more computer-readable media as disclosed in the appended independent claims. Optional but advantageous features are disclosed in the appended dependent claims. In addition, one or more mobile devices, one or more ambient IoT devices, and one or more network entities are also disclosed.

[0004] A first network device is also disclosed. The first network device includes at least one processor; at least one memory, the at least one memory storing instructions that, when executed by the at least one processor, cause the first network device to at least perform: receiving, from a second network device, configuration information about an Internet of Things (IoT) service, the IoT service being subscribed to by an IoT device, the IoT device being attached to the first network device; and creating a device context of the IoT device based at least on the configuration information.

[0005] A second network device is also disclosed. The second network device includes at least one processor; and at least one memory, the at least one memory storing instructions that, when executed by the at least one processor, cause the second network device to at least perform: determining an IoT service subscribed to by an IoT device; determining configuration information about the IoT service; and providing the configuration information to a first network device, the IoT device being attached to the first network device.

[0006] A method is also disclosed. The method includes: receiving, at a first network device from a second network device, configuration information about an IoT service, the IoT service being subscribed to by an IoT device, the IoT device being attached to the first network device; and creating a device context of the IoT device based at least on the configuration information.

[0007] A method is also disclosed. The method comprises determining, at a second network device, an Internet of Things, IoT, service to which an IoT device is subscribed; determining configuration information about the IoT service; and providing the configuration information to a first network device to which the IoT device is attached.

[0008] A first apparatus is also disclosed. The first apparatus comprises means for receiving, from a second apparatus, configuration information about an Internet of Things, IoT, service to which an IoT device is subscribed, the IoT device being attached to a first network device; and means for creating a device context of the IoT device based at least on the configuration information.

[0009] A second apparatus is also disclosed. The second apparatus comprises means for determining an Internet of Things, IoT, service to which an IoT device is subscribed; means for determining configuration information about the IoT service; and means for providing the configuration information to a first apparatus to which the IoT device is attached.

[0010] A computer readable medium is also disclosed. The computer readable medium comprises instructions stored thereon for causing an apparatus to perform at least the instructions of the method according to the third aspect.

[0011] A computer readable medium is also disclosed. The computer readable medium comprises instructions stored thereon for causing an apparatus to perform at least the instructions of the method according to the fourth aspect.

[0012] It should be understood that the summary section is not intended to identify key or essential features of embodiments of the disclosure, nor is it intended to be used in limiting the scope of the disclosure. Other features, aspects, and advantages of the disclosure will become apparent from the following description. BRIEF DESCRIPTION OF DRAWINGS

[0013] Some example embodiments will now be described with reference to the drawings, in which:

[0014] Figure 1 An example communication environment in which example embodiments of the disclosure can be implemented is shown;

[0015] Figure 2A An example communication environment comprising generic network functions (NFs) according to some example embodiments of the disclosure is shown;

[0016] Figure 2B An example communication environment comprising dedicated network functions according to some example embodiments of the disclosure is shown;

[0017] Figure 3 A signalling diagram for IoT management according to some example embodiments of the disclosure is shown;

[0018] Figure 4A signaling diagram for IoT management using generic network functions is shown in accordance with some example embodiments of the present disclosure;

[0019] Figure 5 A signaling diagram for IoT management using dedicated network functions is shown in accordance with some example embodiments of the present disclosure;

[0020] Figure 6 A signaling diagram for performing a query is shown in accordance with some example embodiments of the present disclosure;

[0021] Figure 7 A flow diagram of a method implemented at a first network device is shown in accordance with some example embodiments of the present disclosure;

[0022] Figure 8 A flow diagram of a method implemented at a second network device is shown in accordance with some example embodiments of the present disclosure;

[0023] Figure 9 A simplified block diagram of a device suitable for implementing example embodiments of the present disclosure is shown; and

[0024] Figure 10 A block diagram of an example computer readable medium in accordance with some example embodiments of the present disclosure is shown.

[0025] Throughout the drawings, identical or similar reference labels can represent same or similar elements. DETAILED DESCRIPTION

[0026] The principles of the present disclosure will now be described with reference to some example embodiments. It should be understood that these embodiments are described for illustrative purposes only and help the skilled person to understand and implement the present disclosure, without implying any limitation to the scope of the present disclosure. The embodiments described herein can be implemented in various ways other than those described below.

[0027] In the following description and claims, unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs.

[0028] References in the present disclosure to “one embodiment”, “an embodiment”, “example embodiments”, etc., indicate that the embodiment described can include a particular feature, structure, or characteristic, but every embodiment can not necessarily include the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Furthermore, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of those skilled in the art to effect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.

[0029] It should be understood that, although terms, such as “first,” “second,” and the like can be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first element could be termed a second element, and, similarly, a second element could be termed a first element without departing from the scope of the example embodiments. As used herein, the term “and / or” includes any and all combinations of one or more of the associated listed terms.

[0030] As used herein, “at least one of ” and “one or more of ,” and the like, wherein the list of two or more elements is

[0031] As used herein, unless expressly stated otherwise, performing a step “in response to A” does not indicate that the step is performed immediately following the occurrence of “A,” and can include one or more intervening steps.

[0032] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of example embodiments. As used herein, the singular forms “a,” “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises,” “comprising,” “includes” and / or “including,” when used herein, specify the presence of stated features, elements and / or components, but do not preclude the presence or addition of one or more other features, elements, components and / or combinations thereof.

[0033] As used in this application, the term “circuitry” can refer to one or more or all of the following: (a) hardware-only circuit implementations (such as implementations in only analog and / or digital circuitry) and (b) combinations of hardware circuits and software, such as (as applicable): (i) a combination of analog and / or digital hardware circuit(s) with software / firmware and (ii) portions of hardware processor(s) with software (including digital signal processors); software, including digital signal processors; and memory parts 16) that work together to cause an apparatus, such as a mobile phone or server, to perform various functions and (c) hardware circuit(s) and / or processor(s), such as a microprocessor(s) or a portion of a microprocessor(s), that requires software (e.g., firmware) for operation, but it does not require software to be present when it is not operating.

[0034] Such definition of circuitry applies to all uses of this term in this application, including in any claims. As a further example, as used in this application, the term circuitry also covers an implementation that is at least partially functional and / or an implementation that is at least partially virtualized. The term circuitry also encompasses a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in a server, cellular network device, or other computing or network device (e.g., if applicable to a particular claim element).

[0035] As used herein, the term “communication network” refers to a network that follows any suitable communication standard, such as New Radio (NR), Long Term Evolution (LTE), LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High-Speed Packet Access (HSPA), Narrow Band Internet of Things (NB-IoT), etc. Further, communication between terminal devices and network devices in a communication network can be performed according to any suitable generation communication protocol, including but not limited to, first generation (1G), second generation (2G), 2.5G, 2.75G, third generation (3G), fourth generation (4G), 4.5G, fifth generation (5G) communication protocols, and / or any other protocols that are currently known or developed in the future. Embodiments of the present disclosure can be applied to various communication systems. In view of the rapid development in communications, it is understood that future types of communication technologies and systems that can embody the present disclosure will of course also be applicable. The scope of the present disclosure should not be seen as limited only to the aforementioned systems.

[0036] As used herein, the term “network device” refers to a node in a communication network via which terminal devices access the network and receive services therefrom. The network device can refer to a base station (BS) or an access point (AP), such as a Node B (NodeB or NB), an evolved NodeB (eNodeB or eNB), an NR NB (also known as gNB), a remote radio unit (RRU), a radio head (RH), a remote radio head (RRH), a relay, an integrated access and backhaul (IAB) node, a low power node (such as a femto, pico), a non-terrestrial network (NTN) or non-terrestrial network device (such as a satellite network device, low earth orbit (LEO) satellite, and geosynchronous earth orbit (GEO) satellite), a flying aircraft network device, etc., depending on the terminology applied and the technology. In some example embodiments, a radio access network (RAN) split architecture includes a centralized unit (CU) and a distributed unit (DU) at an IAB donor node. An IAB node includes a mobile terminal (IAB-MT) part, which behaves like a UE to a parent node, and a DU part of the IAB node, which behaves like a base station to a next-hop IAB node.

[0037] The term “terminal device” refers to any terminal device capable of wireless communication. By way of example, and without limitation, a terminal device can also be referred to as a communication device, user equipment (UE), a subscriber station (SS), a portable subscriber station, a mobile station (MS), or an access terminal (AT). A terminal device can include, but is not limited to, a mobile phone, a cellular phone, a smart phone, a voice over Internet Protocol (VoIP) phone, a wireless local loop phone, a tablet, a wearable terminal device, a personal digital assistant (PDA), a portable computer, a desktop computer, an image capture terminal device, such as a digital camera, a game terminal device, a music storage and playback appliance, a vehicle-mounted wireless terminal device, a wireless endpoint, a mobile station, a laptop-embedded equipment (LEE), a laptop-mounted equipment (LME), a USB dongle, a smart device, a wireless customer-premises equipment (CPE), an Internet of Things (IoT) device, a watch or other wearable device, a head-mounted display (HMD), a vehicle, a drone, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in industrial and / or

[0038] As used herein, the terms “resource,” “transmission resource,” “resource block,” “physical resource block” (PRB), “uplink resource,” or “downlink resource” can refer to any resource used to perform communication, e.g., between a terminal device and a network device, such as a time-domain resource, a frequency-domain resource, a spatial-domain resource, a code-domain resource, or any other resource capable of communication, etc. Hereinafter, unless explicitly stated otherwise, resources in the frequency and time domains will be used as examples of transmission resources to describe some example embodiments of the present disclosure. Note that example embodiments of the present disclosure are equally applicable to other resources in other domains.

[0039] Note that any section / subsection headings provided herein are not intended to be limiting. Embodiments are described throughout this document, and any type of embodiment can be included under any section / subsection. Furthermore, embodiments disclosed in any section / subsection can be combined in any manner with any other embodiments described in the same section / subsection and / or in different sections / subsections.

[0040] The term "environmental IoT device," "passive IoT," or "IoT device" is used herein. However, it should be understood that in some example embodiments, the term "environmental IoT device," "passive IoT," or "IoT device" can also be referred to as a "tag." The terms "environmental IoT device" and "passive IoT" can be used interchangeably.

[0041] As briefly mentioned above, environmental IoT is a promising technology. Some design goals have been agreed upon. Design goals include improved link budget compared to existing RFID solutions, frequency bands for global usability (e.g., licensed and unlicensed bands), ultra-low cost, no need for battery charging or replacement (enabling low-maintenance long-life cycle operation), ultra-low power (e.g., < 100 microwatts to enable operation with backscatter or energy harvesting), small device size and form factor, positioning accuracy (e.g., 3 m - 5 m), data rate (e.g., 10 m - 100 kbps), environmental devices based on backscatter technology, semi-environmental devices operating with energy harvesting or with very small batteries (e.g., < 100 mAh), mobile-originated and mobile-terminated data.

[0042] Environmental IoT technology is also a promising technology for the Third Generation Partnership Project. For example, some studies are directed to new 3GPP IoT technologies suitable for deployment in 3GPP systems that rely on ultra-low complexity devices with ultra-low power consumption for very low-end IoT applications.

[0043] A candidate technology for ultra-low energy or zero-energy devices is backscatter, by which a reader sends a radio frequency (RF) signal that illuminates a tag, and the tag modulates the incident RF signal with an information-bearing signal. The reflected signal is then demodulated at the reader. All backscatter systems are Reader Talks First (RTF), i.e., the tag only modulates the reflected wave with its stored information after receiving a signal sent by the reader.

[0044] For example, Electronic Product Code Generation 2 (EPC Gen2)-based Radio Frequency Identification (RFID) can support data rates from the tag to the reader of 40 kbps - 640 kbps with a sensitivity of -85 dBm. Typical rates can vary between 60 to 70 kbps using Miller (M = 4) encoding. For RFID, a typical range of 3 m can be achieved using environmental transponders, and a range of up to 30 m can be achieved using active transponders. All remote tags operate using ultra-high frequency (UHF) or microwave frequencies and communicate with the reader using backscatter modulation.

[0045] Currently, there have been studies on the aforementioned scenarios of supporting backscatter environment IoT devices by cellular networks. Advanced radio technologies are studied, such as to extend the communication range of environment IoT devices and support backscatter communication. Multi-illuminator deployments and bistatic or multistatic configurations in 5G cells are also considered.

[0046] In an example scenario, multiple illuminators and receivers (or readers) can be deployed according to the density of tags and their locations. These illuminators and receivers can be 5G terminal devices. Thus, these illuminators and receivers have the characteristics of 5G terminal devices and can communicate with gNBs, for example, by following traditional procedures. Illuminators and receivers are optimally deployed near environment IoT devices to reduce the transmit power requirements for these environment IoT devices.

[0047] In the coverage of a 5G cell, tags can be distributed unevenly, with high density in some areas and low density in other areas. Terminal devices, tags, and illuminators and receivers can move within a cell, move across cells, and even roam to different cellular network coverage if available.

[0048] If environment IoT devices are registered at the network with known locations, as with traditional NR, so that these environment IoT devices can be efficiently queried by application servers when needed, it would be beneficial to the application servers. However, due to the potential movement of environment IoT devices, it is more complex for application servers to query environment IoT devices.

[0049] Therefore, the following problems need to be solved: how to manage environment IoT devices, including registration, storage, and updating information associated with environment IoT devices, in a cellular network, considering their very large number and extremely low power transmission capability.

[0050] There are different potential ways for the network to (re)discover tags. A potential way is the discovery enabled by the tag for the first time. When a tag is deployed for the first time and connected to the network, the factory circuit protection is removed and the tag is connected manually. Typically, this operation can be done on site, so a handheld reader or writer (also a 5G terminal device) can identify the tag and register the tag's information to the network.

[0051] In another possible way, the tag can have its own energy storage and can accordingly and autonomously sleep and wake up (e.g., without network pre-configuration). In this case, a battery is typically used for sensor power, rather than wireless signal transmission. During the interval between potential data collection, the tag will enter a sleep state. Therefore, the network needs periodic polling or querying to discover or rediscover the tag. When the tag is in a sleep state, it will not backscatter the polling signal to reduce potential uplink collisions.

[0052] Another way is tag mobility. Tags move from one cell to another, e.g. tags in logistics. Compared to the current mobility management procedures for traditional NR UEs, tags cannot actively inform the network about their mobility status, so the network can only be informed about the location of the tags by regular polling or querying.

[0053] Considering the above observations and in order to enable efficient tag management at the network (including registration, authentication, context maintenance), the following questions need to be solved. The question is which network functions will be involved and which new interfaces and behaviors will be defined. Another question is that tags should not be considered as traditional NR UEs, as they have specific connectivity and mobility requirements. Therefore, it is needed to define what (new) procedures and functions should be enhanced and / or redesigned to ensure the connectivity of tags in 3GPP cellular networks and to solve the problem of tag mobility.

[0054] According to some example embodiments of the present disclosure, a scheme for IoT management is provided. In the scheme, a core network (CN) function can register one or more IoT services and create a corresponding service context for the one or more IoT services. If an IoT device is registered, the core network function determines the IoT service to which the IoT device subscribes. The core network function then provides configuration information about the IoT service to a radio access network (RAN) node to which the IoT device is attached. The RAN node creates a device context for the IoT device based on the configuration information. For example, the configuration information can be incorporated into the device context.

[0055] In this way, management of IoT devices is enabled at the core network. Further, at the RAN, the configuration information is combined with the device context. In this way, IoT devices can be quickly and accurately discovered to complete IoT services. It should be noted that although the above problem is described for environmental IoT devices, the concepts of example embodiments of the present disclosure are applicable to any type of IoT device.

[0056] Example embodiments of the present disclosure will be described in detail below with reference to the accompanying drawings. Example Environment

[0057] Figure 1 An example communication environment 100 in which example embodiments of the present disclosure can be implemented is shown. In the communication environment 100, a plurality of communication devices including a terminal device 130, a first network device 110, and a second network device 120 can communicate with each other. In the communication environment 100, the terminal device 130 can be connected to the first network device 110 via the second network device 120. Figure 1In the example of FIG. 1, the first network device 110 can be a RAN node serving the terminal device 130. The service area of the first network device 110 can be referred to as a cell 102, which can be configured with multiple cells. In examples, the terminal device 130 can be a UE and the first network device 110 can be a base station (e.g., gNB) serving the UE.

[0058] The IoT device 140 or tag is attached to the first network device 110 and is associated with the terminal device 130. The IoT device 140 can be of any type. In particular, in some example embodiments, the IoT device 140 can be an environmental IoT device. In example embodiments of the present disclosure, if an IoT device is associated with a terminal device, it means that the terminal device acts as an illuminator, receiver, or reader of the IoT device. The communication between the network and the IoT device 140 is performed via the associated terminal device. In some embodiments, the communication can be performed between the network device 110 and the IoT device 140 without the terminal device 130.

[0059] The second network device 120 in communication with the first network device 110 can be a core network (CN) node for implementing one or more network functions. In some example embodiments, the second network device 120 can be in communication with a network entity 150. The network entity 150 can be an application server, which can be from a third party and provide services by communicating with the core network. For example, the network entity 150 can include an application function (AF).

[0060] The communication in the communication environment 100 can be implemented according to any suitable communication protocol, including but not limited to cellular communication protocols of first generation (1G), second generation (2G), third generation (3G), fourth generation (4G), fifth generation (5G), sixth generation (6G), etc., wireless local area network communication protocols such as Institute of Electrical and Electronics Engineers (IEEE) 802.11, and / or any other protocol that is currently known or developed in the future. Further, the communication can utilize any suitable wireless communication technology, including but not limited to: code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), frequency division duplex (FDD), time division duplex (TDD), multiple-input multiple-output (MIMO), orthogonal frequency division multiple access (OFDM), discrete Fourier transform spread OFDM (DFT-s-OFDM), and / or any other technology that is currently known or developed in the future.

[0061] Typically, the second network device 120 may implement functions for managing IoT services (e.g., AIoT services), including but not limited to service registration, service authentication, and service initialization and maintenance. The second network device 120 may also implement functions for managing IoT devices (e.g., AIoT devices), including but not limited to device registration, device authentication, and device context initialization and maintenance. These functions may be referred to as IoT management functions hereinafter.

[0062] In some example embodiments, one or more of the above IoT management functions may be implemented by one or more general network functions in the CN (e.g., access and mobility management function (AMF), session management function (SMF), and network exposure function (NEF)). Figure 2A . Figure 2A An example communication environment 200A is shown that includes general network functionality.

[0063] In environment 200A, IoT device 240, which is an example implementation of IoT device 140, is associated with UE 230, which is an example implementation of terminal device 130. UE 230 communicates with gNB 210 via a Uu interface. gNB 210 can be considered an example implementation of first network device 110.

[0064] The gNB 210 communicates with the AMF 260 via the N2 interface. The UE communicates with the AMF 260 via the N1 interface. Environment 200A also includes the SMF 222, the NEF 221, and the Unified Data Repository (UDR) 223. The NEF can communicate with the Application Function (AF) 250, which is an example implementation of the network entity 150. Internet Protocol (IP) flows enter the CN through the User Plane Function (UPF) 270. The UPF 270 communicates with the gNB 210 via the N3 interface.

[0065] In the example environment 200A, one or more of the NEF 221, SMF 222, UDR 223, and AMF 260 may implement IoT management functions. Such examples will be referred to below. Figure 5 describe.

[0066] Alternatively, in some example embodiments, one or more of the IoT management functions may be implemented by a network function dedicated to IoT management, which may be referred to as a PIoT or AIoT Management Function (PMF). Figure 2B . Figure 2B An example communication environment 200B including dedicated network functionality is shown. Elements with the same reference numerals are the same as those referenced above. Figure 2A The elements described are the same, so their description will not be repeated.

[0067] In the communication environment 200B, the PMF 220 communicates with the AMF 260 and the AF 250. The IoT management function can be implemented by the PMF 220. Examples of such will be described below with reference to Figure 5 described. Example Signaling Diagram for IoT Management

[0068] In example embodiments of the disclosure, the second network device 120 can determine configuration information about an IoT service to which an IoT device subscribes, and provide the configuration information to the first network device 110.

[0069] Figure 3 A signaling diagram 300 for IoT management according to some example embodiments of the disclosure is shown. Reference is made to Figure 1 The signaling diagram 300 is described by way of example. The signaling diagram 300 involves the first network device 110, the second network device 120, and optionally the network entity 150. However, it should be understood that the signaling diagram 300 can involve more devices or fewer devices, and Figure 3 The number of devices shown in the figures is for the purpose of illustration only and does not imply any limitation.

[0070] The second network device 120 provides the first network device 110 with configuration information about an IoT service to which the IoT device 140 subscribes. To this end, in some example embodiments, registration of the IoT device 140 and the IoT service can be performed. Figure 3 An example procedure is shown in

[0071] The second network device 120 can receive (305) from the network entity 150 a request for registering the IoT service, which is also referred to as a "service registration request". The request includes service information about the IoT service. The service information can include, but is not limited to, a type of IoT device, an identification range or a list of target IoT devices. The request can also include other information, e.g., an ID of the network entity 150, subscription information, etc. It is noted that if the identifications of the target IoT devices are consecutive, an identification range can be included, and if the identifications of the target IoT devices are not consecutive, a list of identifications can be included.

[0072] The second network device 120 can then register (310) the IoT service based on the service information. For example, the second network device 120 can perform mapping of the service information, and store the service information in a local or a data repository (e.g., a UDR).

[0073] The second network device 120 can create (315) a service context of the IoT service based on the service information. The service context is used to record any suitable content related to the IoT service.

[0074] The service context can comprise an identity of the IoT service, e.g., a service ID, a service name, etc. Alternatively or additionally, the service context can comprise an address of a server offering the IoT service, e.g., an address of a computing system hosting the IoT service. Alternatively or additionally, the service context can comprise a coverage of the IoT service, e.g., a cell involved by some local service.

[0075] Subsequently, in some example embodiments, the service context can be updated based on a registration request from the network entity 150. For example, if the address of the server is changed, the network entity 150 can send a request indicating the change, and the second network device 120 can update the service context of the IoT device 140 accordingly.

[0076] In some example embodiments, the second network device 120 can authenticate the IoT service based on the subscription information or a local policy. For example, the second network device 120 can check an authorization certificate of the IoT service.

[0077] In some example embodiments, the second network device 120 can subscribe (320) to an IoT device 140 registration event for the IoT service with another network entity (not shown, and also referred to as a second network entity). For example, the second network device 120 can subscribe to an AIoT device registration event from a CN function, e.g., an AMF or an SMF. The registration of the IoT device 140 can be detected (325). For example, the second network device 120 can receive a notification of the registration of the IoT device 140 from the second network entity.

[0078] Then, the second network device 120 determines 330 the IoT service subscribed by the IoT device 140. In other words, the second network device 120 can perform a device-service mapping. The device-service mapping can be performed based on the service context or the service information. For example, if the unique identity (UID) of the IoT device 140 is included in a range or a list of identities of target IoT devices, the second network device 120 can determine that the IoT service is subscribed by the IoT device 140. In some example embodiments, the second network device 120 can also perform an authentication of the IoT device 140 with the network entity 150. For example, the network entity 150 can check a list of IoT devices, e.g., a list of UIDs. If the UID of the IoT device 140 is included in a list of authorized IoT devices, the authentication of the IoT device 140 is successful.

[0079] The second network device 120 determines 335 configuration information about the IoT service, which is also referred to as service configuration information. The configuration information can include any suitable parameter of an operation associated with the IoT service. In some example embodiments, the operation can include a query to the IoT device 140 issued from the IoT service. With the query, the IoT service can request data from the IoT device 140. For example, if the IoT device 140 includes a sensor, the IoT service can request the IoT device 140 to report its sensing data.

[0080] In such example embodiments, the configuration information can include one or more parameters of the query, which is also referred to as query parameters. The query parameters can include an indication whether the query is triggered periodically or by an event, i.e. a trigger indication. If the query is triggered periodically, the query parameters can include a query command, also referred to as a second query command, to initiate the query.

[0081] Alternatively or additionally, if the query is triggered periodically, the query parameters can include a configuration of the periodic query. The configuration can include a period of the query and / or a time offset of the query. Based on the configuration, the occasion to send the query command can be determined.

[0082] It should be appreciated that although some example embodiments are described with respect to a query, this is an example and not any limitation. Aspects described with respect to a query apply to other operations associated with the IoT service.

[0083] The above example embodiments are described with respect to an individual IoT device. It should be appreciated that more than one IoT device can be attached to the first network device 110. Thus, the query can be associated with one or more IoT devices including the IoT device 140. In other words, the IoT service can request data from one or more IoT devices and the configuration information applies to the query to the one or more IoT devices.

[0084] To determine the configuration information, in some example embodiments, the second network device 120 can communicate with the network entity 150 to obtain the configuration information from the network entity 150. Alternatively or additionally, in some example embodiments, the service context can include the configuration information and the second network device 120 can retrieve the configuration information from the service context. For example, if the registration request for the IoT service can include the configuration information, the second network device 120 can incorporate the configuration information into the service context when the service context is created.

[0085] In some example embodiments, the second network device 120 can also create 340 a device context of the IoT device 140. The device context is used to record any suitable content related to the IoT device 140.

[0086] In some example embodiments, the device context can comprise a UID of the IoT device 140. Alternatively or additionally, the device context can comprise an identification of one or more IoT services to which the IoT device 140 is subscribed. It will be appreciated that service subscriptions can be independent of devices and / or server deployments, and it is possible that a certain IoT device can be registered to more than one service. Thus, the device context can comprise the IDs of multiple IoT services.

[0087] Alternatively or additionally, the device context can comprise a device type of the IoT device 140. Alternatively or additionally, the device context can comprise a location of the IoT device 140. The location can be a geographical location of the IoT device 140, which can be represented by coordinates. The location can have any suitable accuracy.

[0088] Alternatively or additionally, the device context can comprise an association of the IoT device 140 with another entity in the communication system, e.g., a base station, or a UE, etc. For example, the device context can comprise an identification of a cell to which the IoT device 140 is attached, e.g., a cell ID. As another example, the device context can comprise an identification of a terminal device associated with the IoT device 140, e.g., an ID of a UE associated with the IoT device 140.

[0089] Alternatively or additionally, the device context can comprise one or more parameters related to a power source of the IoT device 140. For example, the device context can indicate whether the IoT device 140 has a power source or a battery, whether the IoT device 140 can harvest energy, whether the IoT device 140 has a sleep cycle, etc.

[0090] Alternatively or additionally, the device context can comprise capability information of the IoT device 140. For example, the device context can indicate an operating frequency, a maximum response distance, etc.

[0091] In view of the IoT device 140 subscribing to the IoT service, the second network device 120 can associate the IoT device 140 with the IoT service. For example, the second network device 120 can construct and store binding information between a service context of the IoT service and a device context of the IoT device 140. In this way, if there is any change to the service context, the device context can be updated accordingly.

[0092] Additionally, in some example embodiments, in response to the registration of the IoT device, the service context can be updated to comprise the UID of the IoT device 140 that subscribes to the IoT service.

[0093] Continuing the signaling diagram 300, the second network device 120 provides 345 configuration information to the first network device 110 to which the IoT device 140 is attached. The configuration information can be provided to the first network device 110 directly or via another network entity.

[0094] The first network device 110 receives the configuration information and creates 350 a device context for the IoT device 140 based on the configuration information. For example, if a previous version of the device context has already been created, the first network device 110 can incorporate the configuration information into the previous version to update the content of the device context. For another example, the first network device 110 can generate the content of the device context based on at least the configuration information.

[0095] In some example embodiments, the second network device 120 can provide the content of the device context to the first network device 110 in addition to the configuration information. For example, one or more content of the device context described with respect to the action 340 can be provided to the first network device 110. Then, the device context at the first network device 110 can be created based on the configuration information and the received content.

[0096] In other words, in such example embodiments, the content of the device context for the IoT device 140 can be passed and inherited from an upstream entity to a downstream entity.

[0097] In some example embodiments, if the status of the IoT device 140 changes, the device context can be updated based on the change. The status of the IoT device 140 can include, but is not limited to, the location of the IoT device 140, a subscription status such as which service the IoT device 140 subscribes to, an association with one or more terminal devices. For example, if the association relationship between the IoT device 140 and a terminal device changes, the device context can be updated to include the ID of the new terminal device associated with the IoT device 140.

[0098] After the device context is created based on the configuration information, the first network device 110 can perform operations associated with the IoT service according to the device context. In some example embodiments, a query for the IoT device 140 from the IoT service can be performed based on the device context. Such example embodiments will be described below with reference to Figure 6

[0099] In such example embodiments, by incorporating the configuration information into the device context, the first network device 110 can accurately and efficiently find the IoT device. In this way, the IoT service can be efficiently provisioned. For example, the IoT service can timely obtain sensing data.

[0100] ​From the above example procedures, it can be seen that one or more NFs can manage IoT services, including at least service registration, service authentication, and service initialization and maintenance. For example, an IoT service can be authenticated based on subscription information or local policy, e.g., by checking authorization credentials. For another example, an IoT service context can be maintained (e.g., created, stored, and updated) based on a registration request from a third-party AF. For another example, IoT device registration events can be subscribed to and / or unsubscribed from by a network function (e.g., AMF or SMF). Further, binding information between an IoT service context and a subscribed IoT device(s) can be constructed and stored.

[0101] In another aspect, one or more NFs can manage IoT devices, including at least device registration, device authentication, and device context initialization and maintenance. For example, a new device registration can be detected and notified to a subscribed NF based on a device-initiated procedure. For another example, a device context can be maintained (e.g., created, stored, and updated) if authentication of an IoT device is successfully completed, e.g., a UID of the IoT device is included in a list of authorized IoT device(s). For another example, in the case of mobility, a device context can be transferred to a target RAN.

[0102] Reference Figure 3 Example procedures for IoT management are described. Further example embodiments are described below. Example Signaling Diagram in Case of Generic NF

[0103] As described above, in some example embodiments, IoT management functions can be implemented by one or more generic NFs. Figure 4 A signaling diagram 400 for IoT management using generic NFs is shown in accordance with some example embodiments of the present disclosure. The signaling diagram 400 can be implemented in the communication environment 200A and involves an IoT device 240, a UE 230, a gNB 210, an AMF 260, an SMF 222, a UDR 223, a NEF 221, and an AF 250. However, it should be understood that the signaling diagram 400 can involve more entities or fewer entities, and Figure 4 The number of entities shown in the signaling diagram 400 is for illustration purposes only and does not imply any limitation.

[0104] Generally, the signaling diagram 400 includes a service registration procedure 450 and a device registration procedure 460. During the service registration procedure 450, the AF 250 initiates a new IoT service creation procedure with certain service parameters to the communication system. For example, a new Nnef_service request or an existing Nnef_service request can be used to initiate the service registration procedure 450.

[0105] As Figure 4As shown, AF 250 may send (402) a request to NEF 221 for registering an IoT service, which is also referred to as a service request. The service request may be used to call NEF 221 to create service parameters for the IoT service. The request may include service information about the IoT service, such as the type of target IoT device, a range or list of identifiers of target IoT devices. The request may also include the address of the AF application, subscription information about IoT device registration, and the like. For example, the subscription information may include a range or list of identifiers of target IoT devices that subscribe to the IoT service.

[0106] In response to the request, NEF 221 may identify (404) the service and store the service information in UDR 223. NEF 221 may store any other suitable information in UDR 223, such as a description of the IoT service, parameters, and IoT service information (e.g., service type, service UID, etc.).

[0107] In such Figure 4 In the example shown, NEF 221 may create (406) a service context for the IoT service. The service context is explained in the same manner as in the above reference. Figure 3 Alternatively, in some example embodiments, the service context may be created in a unified data management (UDM). In such an example embodiment, the NEF 221 may forward the received request to the UDM ( Figure 4 not shown).

[0108] NEF 221 may then send (408) a service response to the service request to AF 250. For successfully created IoT services, NEF 221 may subscribe (410) to IoT device registration events in the core network (e.g., AF 250). In this way, when an IoT device registration event is detected by the core network (e.g., SMF 222), NEF 221 will be notified of the event, as described below.

[0109] The IoT service is registered in the core network through the above service registration process 450. The service context of the IoT service can be maintained in the core network.

[0110] During the device registration process 460, the IoT device attach process may be performed between the gNB 210, the UE 230, and the IoT device 240 (412). After the attach process is successfully completed, the IoT device 240 is attached to the gNB 210 and associated with the UE 230. The UE 230 may then initiate registration of the IoT device 240. Figure 4As shown, the UE 230 can send (414) an IoT device registration request to the AMF 260. For example, the UE 230 can initiate a device registration procedure by sending a device registration request.

[0111] The registration request can include device information about the IoT device 240. The device information can include a UID of the IoT device 240 and any other information or parameters related to the IoT device 240. The registration request can also include an ID of a protocol data unit (PDU) session, a data network name (DNN), single-network slice selection assistance information (S-NSSAI), which can help identify the IoT device 240. In some example embodiments, non-access stratum (NAS) signaling can be used to carry the registration request. Additionally, the registration request or the device information can include an ID of a terminal device associated with the IoT device 240.

[0112] The AMF 260 can receive the registration request and forward (416) at least the device information in the registration request to the SMF 222. For example, the device information can be included in a Nsmf_service request. Other information such as a PDU session ID, a DNN, and a S-NSSAI can also be forwarded to the SMF 222.

[0113] Upon receiving the device information, the SMF 222 can detect an IoT device registration event. Thus, the SMF 222 can associate an ID of the UE 230 with the UID of the IoT device 240. In other words, the SMF 222 can bind a reported UE ID and a carried IoT device UID.

[0114] The SMF 222 can then notify the NEF 221 of the newly registered UID, which subscribes to the event. As Figure 4 shown, the SMF 222 can send (418) a notification of the registration of the IoT device 240. The notification can include the UID of the IoT device 240 and any other suitable information related to the IoT device 240. In an example, the notification can be included in a Nsmf_EventExposure service message.

[0115] The NEF 221 can perform 420 device service mapping. In other words, the NEF 221 can determine one or more IoT services to which the IoT device 240 is subscribed. The mapping can be performed based on service information stored in the UDR 223 or the service context created 406 during the service registration procedure. The NEF 221 can associate the IoT device 240 with an IoT service if the UID of the IoT device 240 is included in the service information or the service context as one of the range or list of identities of target IoT devices, and / or the ID of the IoT service is included in the device information. The NEF 221 can also perform device authentication of the IoT device 240 with the AF 250. For example, the AF 250 can check a list of IoT device(s) (e.g., including UIDs). The device authentication of the IoT device 240 is successful if the UID of the IoT device 240 is included in the list of authorized IoT device(s).

[0116] In some example embodiments, after the IoT device 240 has been registered, the NEF 221 can request 422 configuration information, e.g., service configuration parameters, about the IoT device from the AF 250 and receive the requested configuration information. The configuration information is similar to the configuration information described above with reference to FIG. 3, and thus the description thereof is not repeated here. Figure 3 Alternatively or additionally, in some example embodiments, the NEF 221 can request the configuration information from the AF 250 after the service response is sent 408, or the NEF 221 can include a request for the configuration information within the service response.

[0117] The configuration information can be passed 424 from the NEF 221 to the SMF 222. In some example embodiments, the configuration information can be passed via a policy control function (PCF, not shown in FIG. 2) and / or a network exposure function (NEF, not shown in FIG. 2). The device authentication result of the newly registered IoT device 240 can also be notified to the SMF 222 in terms of the UID of the IoT device 240. The configuration information can be carried in a Nnef service or Npcf / Nsmf service message. Figure 4

[0118] If the UID of the IoT device 240 is included, the SMF 222 can derive the corresponding UE based on the stored binding information of the UE ID and the UID of the IoT device. In this example, the SMF 222 determines that the IoT device 240 is associated with the UE 230. The SMF 222 can create 426 a device context for the IoT device 240. The interpretation of the device context is the same or similar to the device context described above with reference to FIG. 3, and thus the description thereof is not repeated here. Figure 3

[0119] ​​The SMF 222 can notify a serving AMF for the associated UE of the indication and configuration information of the IoT device 240 received. In this example, the SMF 222 can send (428) the configuration information to the AMF 260. The configuration information can be carried in an Nsmf_service message.

[0120] Upon receiving the configuration information, the AMF 260 can create (430) a device context for the IoT device 240. The interpretation of the device context is the same or similar to the device context described above with reference to the AMF 260, and thus the description thereof is not repeated here. The device context can be created based on the configuration information. For example, the configuration information can be incorporated into the device context. In some example embodiments, the SMF 222 can provide the content of the device context created (426) at the SMF 222 to the AMF 260. The AMF 260 can create its own device context based on the provided content. In other words, the device context can be transferred and inherited from the SMF 222 to the AMF 260. Figure 3

[0121] The AMF 260 can then send (432) the configuration information to the gNB 210. For example, the AMF 260 can send a device registration response including the configuration information to the gNB 210 over the N2 interface. Any existing or further developed N2 signaling can be used to carry the configuration information to the gNB 210 in the RAN.

[0122] The gNB 210 can create (434) a device context for the IoT device 240 when the IoT device 240 is registered in the core network and authenticated by the AF 250. For example, the device context can be created based at least on the configuration information. The context device can further be created based on device information of the IoT device 240, e.g., the device information can be provided to the gNB 210 during the IoT device attach procedure (412). For example, the device context can first be created based on the device information obtained during the IoT device attach procedure (412), and then be updated based on the configuration information.

[0123] In some example embodiments, the AMF 260 can provide the content of the device context created (430) at the AMF 260 to the gNB 210. The gNB 210 can create its own device context based on the provided content. In other words, the device context can be transferred and inherited from the AMF 260 to the gNB 210.

[0124] ​In some example embodiments, the SMF 222 can provide the content of the device context created (426) at the SMF 222 to the gNB 210 via the AMF 260. The gNB 210 can create its own device context based on the provided content. In other words, the device context can be passed and inherited from the SMF 222 to the gNB 210.

[0125] As can be seen, the device context can be passed and inherited from the core network to the RAN.

[0126] In some example embodiments, the UE initiates the transmission (414) of the registration request, which is different from in the device attach procedure (412). Accordingly, the gNB 210 can update the device context with the new relationship between the IoT device 240 and the UE associated with the IoT device 240.

[0127] In some example embodiments, the gNB 210 can provide (436) configuration information to the UE 230 associated with the IoT device 240. For example, the configuration information can be sent to the UE 230 through radio resource control (RRC) reconfiguration signaling.

[0128] In reference to Figure 4 In the example embodiments described above, IoT management can be enhanced by using some generic NFs. Example Signaling Diagram in Case of Specialized NF Figure 5

[0129] Alternatively, as mentioned above, in some example embodiments, a new logical network function in the core network can be introduced, which is referred to as PMF. The PMF can be specifically used for PIoT or AIoT service and device management, including one or more of service registration, service authentication, device registration, device authentication, device service mapping, device and service context maintenance, and configuration information.

[0130] Figure 3 A signaling diagram for IoT management using a dedicated network function is shown in accordance with some example embodiments of the present disclosure. The signaling diagram 500 can be implemented in the communication environment 200B and involves the IoT device 240, the UE 230, the gNB 210, the AMF 260, the PMF 220, and the AF 250. However, it should be understood that the signaling diagram 500 can involve more entities or fewer entities, and Figure 5 The number of entities shown in the communication environment 200B is for illustration purposes only and does not imply any limitation.

[0131] Generally, the signaling diagram 500 includes a service registration process 550 and a device registration process 560. During the service registration process 550, the AF 250 initiates a new IoT service creation process to the communication system using certain service parameters. For example, the service registration process 550 can be initiated using an Npmf_ServiceParameter_Create request.

[0132] like Figure 3 As shown, the AF 250 may send (502) a request to the PMF 220 for registering an IoT service, which is also referred to as a service request. The service request may be used to call the PMF 220 to create service parameters for the IoT service. The request may include service information about the IoT service, such as the type of target IoT device, the UID of the target IoT device, or a range or list of identifiers of target IoT devices. The request may also include the ID of the AF application, subscription information about IoT device registration, etc. For example, the subscription information may include the UID of the target IoT device that subscribes to the IoT service.

[0133] In response to the request, the PMF 220 may identify the service and store the service information in the UDR 223 or locally.

[0134] The PMF 220 may create (504) a service context for the IoT service. The service context is explained in the same manner as above with reference to Figure 4 The service context described in

[15] is the same or similar, so its description is not repeated here. Alternatively, in some example embodiments, the service context may be created in a unified data management (UDM). In such an example embodiment, PMF 220 may forward the received request to the UDM ( Figure 5 not shown).

[0135] The PMF 220 may then send (506) a service response to the service request to the AF 250. For successfully created IoT services, the PMF 220 may subscribe (508) to IoT device registration events in the core network. In this way, when the core network (e.g., AMF 260) detects an IoT device registration event, the event will be notified to the PMF 220, as described below.

[0136] The IoT service is registered in the core network through the above process 550. The service context of the IoT service can be maintained in the core network.

[0137] During the device registration procedure 560, an IoT device attach procedure can be performed (510) between the gNB 210, the UE 230, and the IoT device 240. After successfully completing the attach procedure, the IoT device 240 is attached to the gNB 210 and associated with the UE 230. Then, the UE 230 can initiate registration of the IoT device 240. As Figure 5 shown, the UE 230 can send (512) an IoT device registration request to the AMF 260. For example, the UE 230 can initiate the device registration procedure by sending the device registration request.

[0138] The registration request can include device information about the IoT device 240. The device information can include the UID of the IoT device 240 and any other information or parameters related to the IoT device 240. The registration request can also include the ID of the PDU session, the DNN, the S-NSSAI, which can help identify the IoT device 240. In some example embodiments, NAS signaling can be used to carry the registration request.

[0139] Upon receiving the registration request, the AMF 260 can detect an IoT device registration event. Accordingly, the AMF 260 can associate the ID of the UE 230 with the UID of the IoT device 240. In other words, the AMF 260 can bind the reported UE ID and the carried IoT device UID.

[0140] The AMF 260 can then notify the PMF 220 of the newly registered UID of the IoT device 240, which subscribes to the event. As Figure 3 shown, the AMF 260 can send (514) a notification of the registration of the IoT device 240. The notification can include the UID of the IoT device 240 and any other suitable information related to the IoT device 240. In an example, the notification can be included in a Npmf_service message.

[0141] The PMF 220 can perform (516) device service mapping. In other words, the PMF 220 can determine one or more IoT services subscribed by the IoT device 240. The mapping can be performed based on the stored service information or the service context created (504) during the service registration procedure 550. The PMF 220 can associate the IoT device 240 with the IoT services if the UID of the IoT device 240 is included in the service information or the service context as the UID of the target IoT device, and / or the ID of the IoT services is included in the device information.

[0142] PMF 220 can also perform device authentication of IoT device 240 with AF 250. For example, a list of IoT device(s) can be checked by AF 250. If the UID of IoT device 240 is included in the list of authorized IoT device(s), the device authentication of IoT device 240 is successful.

[0143] In some example embodiments, after IoT device 240 has been registered, PMF 220 can request (518) configuration information, e.g., service configuration parameters, about the IoT device from AF 250. The configuration information is similar to the configuration information described above with reference to Figure 3 FIG. 4, and thus the description thereof is not repeated here. Alternatively or additionally, in some example embodiments, PMF 220 can request the configuration information from AF 250 after the service response is sent (506), or PMF 220 can include a request for the configuration information within the service response.

[0144] PMF 220 can create (520) a device context for IoT device 240. The device context is the same or similar to the device context described above with reference to Figure 3 FIG. 4, and thus the description thereof is not repeated here.

[0145] PMF 220 can notify the serving AMF for the associated UE about IoT device 240 and the configuration information. In this example, PMF 220 can send (522) the configuration information to AMF 260. The configuration information can be carried in a Npmf_service message.

[0146] Upon receiving the configuration information, AMF 260 can create (524) a device context for IoT device 240. The device context is similar to the device context described above with reference to Figure 4 FIG. 4, and thus the description thereof is not repeated here. The device context can be created based on the configuration information. For example, the configuration information can be incorporated into the device context. In some example embodiments, PMF 220 can provide the content of the device context created (520) at PMF 220 to AMF 260. AMF 260 can create its own device context based on the provided content. In other words, the device context can be transferred and inherited from PMF 220 to AMF 260.

[0147] AMF 260 can then send (526) the configuration information to gNB 210. For example, AMF 260 can send a device registration response including the configuration information to gNB 210 over a N2 interface. Any existing or further developed N2 signaling can be used to carry the configuration information to gNB 210 in the RAN.

[0148] When the IoT device 240 is registered in the core network and authenticated by the AF 250, the gNB 210 can create (528) a device context for the IoT device 240. For example, the device context can be created based at least on the configuration information. The context device can further be created based on device information of the IoT device 240, e.g., which can be provided to the gNB 210 during the IoT device attach procedure (510). For example, the device context can be first created based on the obtained device information during the IoT device attach procedure (510), and then updated based on the configuration information.

[0149] In some example embodiments, the AMF 260 can provide the content of the device context created (524) at the AMF 260 to the gNB 210. The gNB 210 can create its own device context based on the provided content. In other words, the device context can be transferred and inherited from the AMF 260 to the gNB 210.

[0150] In some example embodiments, the PMF 220 can provide the content of the device context created (520) at the PMF 220 to the gNB 210 via the AMF 260. The gNB 210 can create its own device context based on the provided content. In other words, the device context can be transferred and inherited from the PMF 220 to the gNB 210.

[0151] It can be seen that the device context can be transferred and inherited from the core network to the RAN.

[0152] In some example embodiments, the transmission (512) of the registration request by the UE is different from the device attach procedure (510). Accordingly, the gNB 210 can update the device context with the new relationship between the IoT device 240 and the UE associated with the IoT device 240.

[0153] In some example embodiments, the gNB 210 can provide (530) the configuration information to the UE 230 associated with the IoT device 240. For example, the configuration information can be sent to the UE 230 through RRC reconfiguration signaling.

[0154] The advantage of introducing the new NF is that the operations and signaling associated with the ambient IoT can be grouped together. The AIoT features can evolve as independently as possible from other features, and with minimal impact on the functionality of existing NFs.

[0155] In these example embodiments, the PMF 220 takes on the distribution of Example Signaling Diagram for QueryThe functions of NEF 221, UDR 223 and SMF 222 are shown in FIG. Their operation, signaling initiation and termination are all included in PMF 220. However, it should be noted that in some example embodiments, the signaling interaction between AF 250 and PMF 220 (e.g., actions 502 and 506) may need to be forwarded through the NEF, which is a provision of the core network from a security perspective. Figure 6

[0156] As briefly mentioned above, in some example embodiments, queries to the IoT device 140 from the IoT service may be performed based on the device context of the IoT device 140. Figure 6 . Figure 6 6 shows a signaling diagram 600 for performing a query according to some example embodiments of the present disclosure. The signaling diagram 600 involves the first network device 110, the terminal device 130, the IoT device 140 and the network entity 150. However, it should be understood that the signaling diagram 600 may involve more devices or fewer devices, and Figure 6 The number of devices shown in FIG. 5 is for illustrative purposes only and does not imply any limitation.

[0157] In some example embodiments, the query may be triggered periodically. Process 650 illustrates an example of a periodic query. In this example embodiment, the configuration information may include a query command, also referred to as a second query command.

[0158] First network device 110 may determine a time to initiate a query based on the configuration information. For example, the time may be determined based on the query period and time offset. At the determined time, first network device 110 may send a second query command to IoT device 140 directly or via terminal device 130 associated with IoT device 140. For example, if first network device 110 is within the maximum response distance of IoT device 140 and the IoT device is not associated with any terminal device, the query command may be sent directly to IoT device 140.

[0159] exist Figure 6 In the example of , the first network device 110 can send ( 602 ) a second query command to the end device 130 associated with the IoT device 140. The end device 130 can forward ( 604 ) the second query command to the IoT device 140.

[0160] In response to the second query command, the IoT device 140 can send (606) the data report to the terminal device 130, which can then forward (608) the data report to the first network device 110. Alternatively, the IoT device 140 can send the data report directly to the first network device 110. The first network device 110 also forwards (610) the data report to the network entity 150. In this way, the application can obtain its desired data. The periodic query action is initiated by the RAN without the involvement of the AF.

[0161] As mentioned above, in some example embodiments, the query can be associated with multiple IoT devices attached to the first network device 110, including the IoT device 140. In this case, the first network device 110 can determine the respective device contexts of the multiple IoT devices from all device contexts maintained by the first network device 110. Based on the respective device contexts, the first network device 110 can perform the query for each of the multiple IoT devices, similar to the procedure 650.

[0162] In some example embodiments, the query can be triggered by an event. The procedure 660 shows an example of an event-triggered query. In this example embodiment, triggered by the event, the network entity 150 can send (612) a query command, also referred to as a first query command, to the first network device 110.

[0163] The first network device 110 can send the first query command to the IoT device 140 directly or via the terminal device 130 associated with the IoT device 140. In the example where the first network device 110 sends (614) the first query command to the terminal device 130 associated with the IoT device 140, the terminal device 130 can forward (616) the first query command to the IoT device 140. Example Method The first network device 110 can send the first query command to the IoT device 140 directly or via the terminal device 130 associated with the IoT device 140. In the example where the first network device 110 sends (614) the first query command to the terminal device 130 associated with the IoT device 140, the terminal device 130 can forward (616) the first query command to the IoT device 140.

[0164] In response to the first query command, the IoT device 140 can send (618) the data report to the terminal device 130, which can then forward (620) the data report to the first network device 110. Alternatively, the IoT device 140 can send the data report directly to the first network device 110. The first network device 110 also forwards (622) the data report to the network entity 150. In this way, the application can obtain its desired data.

[0165] As mentioned above, in some example embodiments, the query can be associated with multiple IoT devices attached to the first network device 110, including the IoT device 140. Alternatively or additionally, the query can be from multiple IoT services, which means that these IoT services need data from the same IoT device.

[0166] In view of this, in some example embodiments, the first query command can include an identification of one or more IoT services including the IoT service, or a UID of one or more IoT devices including the IoT device 140. In such example embodiments, the first network device 110 can determine a respective device context of the one or more IoT devices from all device contexts maintained by the first network device 110. Based on the respective device context, the first network device 110 can perform a query for each of the one or more IoT devices, similar to the procedure 660. If more than one IoT service requests data from the same IoT device (e.g., from the IoT device 140), the data from the IoT device 140 can be distributed by the network entity 150 to each of these IoT services.

[0167] From the above description, the network device in the CN implements core network functions to expose the query capability to the third-party AF and allow the AF to request data with certain requirements to the communication system. Both event-triggered query (e.g., immediate query) and periodic query can be supported. Further, the query request can be interpreted as query parameters, and the query parameters can be passed to the RAN. The network device in the RAN implements the function of storing the query parameters and performing the query accordingly.

[0168] In example embodiments of the present disclosure, the query parameters can be incorporated into the device context and thus can be combined with the device information (e.g., obtained during the attach procedure). In this way, the RAN can quickly and accurately find the IoT device. Therefore, the query can be efficiently performed. Figure 7

[0169] Figure 1 A flowchart illustrating an example method 700 implemented at a first network device according to some example embodiments of the present disclosure is shown. For purposes of discussion, the method 700 will be described from the perspective of the first network device 110 in the communication system 100. Figure 8 The method 700 will be described from the perspective of the first network device 110 in the communication system 100.

[0170] At block 710, the first network device 110 receives configuration information about an IoT service from a second network device 120, the IoT service being subscribed by an IoT device. The IoT device is attached to the first network device 110.

[0171] At block 720, the first network device 110 creates a device context of the IoT device based at least on the configuration information.

[0172] In some example embodiments, the first network device 110 can receive content related to the device context from the second network device 120. The device context is created based on the content and the configuration information.

[0173] In some example embodiments, the first network device 110 can update the device context based on a change in the status of the IoT device.

[0174] In some example embodiments, the device context comprises at least one of: a unique identity of the IoT device, an identity of one or more IoT services to which the IoT device is subscribed, a device type of the IoT device, a location of the IoT device, an identity of a cell to which the IoT device is attached, an identity of a terminal device associated with the IoT device, one or more parameters related to a power supply of the IoT device, capability information or configuration information of the IoT device.

[0175] In some example embodiments, the configuration information comprises one or more parameters of a query from the IoT service to request data from at least the IoT device.

[0176] In some example embodiments, the one or more parameters comprise at least one of: an indication of whether the query is triggered periodically or by an event, a second query command to initiate the query to the IoT device in case the query is triggered periodically, or a configuration of the query in case the query is triggered periodically.

[0177] In some example embodiments, the first network device 110 can perform the query based on the device context of the IoT device.

[0178] In some example embodiments, the query is triggered by an event, and the first network device 110 can receive a first query command from the first network entity to initiate the query. The first network device 110 can send the first query command directly to the IoT device, or via a terminal device associated with the IoT device.

[0179] In some example embodiments, the first query command comprises at least one of: an identity of one or more IoT services comprising the IoT service, or a unique identity of one or more IoT devices comprising the IoT device.

[0180] In some example embodiments, the query is triggered periodically, and the first network device 110 can determine a time occasion for initiating the query based on the configuration information; and send a second query command directly to the IoT device, or via a terminal device associated with the IoT device, at the time occasion.

[0181] Figure 1 A flowchart illustrating an example method 800 implemented at a second network device according to some example embodiments of the present disclosure is shown. For the purpose of discussion, the example method 800 will be discussed with reference to the example network environment 100 of FIG. 1. Example Apparatus, Device, and MediumFIG. 8 illustrates an example of a method 800 for angle description of a second network device 120 in the system 100. In some example embodiments, the method 800 can be implemented at one or more of the NEF, the AMF, the SMF, and the UDR. In some example embodiments, the method 800 can be implemented at the PMF.

[0182] At block 810, the second network device 120 determines IoT services subscribed by the IoT device.

[0183] At block 820, the second network device 120 determines configuration information about the IoT services.

[0184] At block 830, the second network device 120 provides the configuration information to the first network device 110 to which the IoT device is attached.

[0185] In some example embodiments, the second network device 120 can receive, from the first network entity, a request for registering the IoT services, the second request including service information about the IoT services; register the IoT services based on the service information; and create a service context of the IoT services based on the service information.

[0186] In some example embodiments, the service context includes at least one of an identity of the IoT services, an address of a server provisioning the IoT services, a coverage of the IoT services, unique identities of one or more IoT devices subscribing to the IoT services, or the configuration information.

[0187] In some example embodiments, the second network device 120 can subscribe, to the second network entity, for an IoT registration event for the IoT services; and receive, from the second network entity, a notification of a registration of the IoT device.

[0188] In some example embodiments, in response to the registration of the IoT device, the second network device 120 can create a device context of the IoT device.

[0189] In some example embodiments, the second network device 120 can provide, to the first network device 110, contents of the device context.

[0190] In some example embodiments, the device context includes at least one of a unique identity of the IoT device, identities of one or more IoT services to which the IoT device subscribes, a device type of the IoT device, a location of the IoT device, an identity of a cell to which the IoT device is attached, an identity of a terminal device associated with the IoT device, one or more parameters related to a power source of the IoT device, or capability information of the IoT device.

[0191] In some example embodiments, in response to the registration of the IoT device, the second network device 120 performs authentication of the IoT device with the first network entity.

[0192] In some example embodiments, the configuration information is received from the first network entity.

[0193] In some example embodiments, the configuration information comprises one or more parameters of a query from an IoT service to request data from the IoT device.

[0194] In some example embodiments, the configuration information comprises at least one of an indication whether the query is triggered periodically or by an event, a second query command to initiate the query in case the query is triggered periodically, or a configuration of the query in case the query is triggered periodically. Figure 1

[0195] In some example embodiments, a first apparatus (e.g., the first network device 110 in Figure 1 ) capable of performing any of the methods 700 can comprise means for performing the respective operations of the methods 700. The means can be implemented in any suitable form. For example, the means can be implemented in circuitry or software modules. The first apparatus can be implemented as or included in the first network device 110 in Figure 1 .

[0196] In some example embodiments, the first apparatus comprises means for receiving configuration information about an Internet of Things (IoT) service from a second apparatus, the IoT service being subscribed to by an IoT device, the IoT device being attached to the first apparatus, and means for creating a device context of the IoT device based at least on the configuration information.

[0197] In some example embodiments, the first apparatus comprises means for receiving content related to the device context from the second apparatus, and wherein the device context is created based on the content and the configuration information.

[0198] In some example embodiments, the first apparatus comprises means for updating the device context based on a change of a status of the IoT device.

[0199] In some example embodiments, the device context comprises at least one of a unique identity of the IoT device, an identity of one or more IoT services the IoT device subscribes to, a device type of the IoT device, a location of the IoT device, an identity of a cell the IoT device is attached to, an identity of a terminal device associated with the IoT device, one or more parameters related to a power supply of the IoT device, capability information of the IoT device, or the configuration information.

[0200] In some example embodiments, the configuration information comprises one or more parameters of a query from the IoT service to request data from at least the IoT device.

[0201] In some example embodiments, the one or more parameters comprise at least one of an indication of whether the query is triggered periodically or by an event, a second query command to initiate the query to the IoT device in case the query is triggered periodically, or a configuration of the query in case the query is triggered periodically.

[0202] In some example embodiments, the first apparatus comprises means for performing the query based on a device context of the IoT device.

[0203] In some example embodiments, the query is triggered by an event, and the first apparatus comprises means for receiving a first query command from the first network entity to initiate the query, and means for sending the first query command directly to the IoT device or to the IoT device via a terminal device associated with the IoT device.

[0204] In some example embodiments, the first query command comprises at least one of an identification of one or more IoT services comprising the IoT service, or a unique identification of one or more IoT devices comprising the IoT device.

[0205] In some example embodiments, the query is triggered periodically, and the first apparatus comprises means for determining a time occasion for initiating the query based on the configuration information, and means for sending a second query command directly to the IoT device or to the IoT device via a terminal device associated with the IoT device at the time occasion.

[0206] In some example embodiments, the first apparatus further comprises means for performing the other operations of the method 700 or other operations of some example embodiments of the first network device 110. In some example embodiments, the means comprises at least one processor, and at least one memory storing instructions which, when executed by the at least one processor, cause the first apparatus to perform.

[0207] In some example embodiments, a second apparatus (e.g., the second network device 120 in Figure 1 capable of performing any of the methods 800 can comprise means for performing the respective operations of the method 800. The apparatus can be implemented in any suitable form. By way of example, the apparatus can be implemented in circuitry or software modules. The second apparatus can be implemented as or included in the second network device 120 in Figure 9 .

[0208] In some example embodiments, the second apparatus comprises: means for determining an IoT service to which an IoT device is attached; means for determining configuration information about the IoT service; and means for providing the configuration information to the first apparatus.

[0209] In some example embodiments, the second apparatus comprises: means for receiving, from a first network entity, a request for registering an IoT service, the second request comprising service information about the IoT service; means for registering the IoT service based on the service information; and means for creating a service context of the IoT service based on the service information.

[0210] In some example embodiments, the service context comprises at least one of: an identity of the IoT service, an address of a server provisioning the IoT service, a coverage of the IoT service, unique identities of one or more IoT devices subscribing to the IoT service, or configuration information.

[0211] In some example embodiments, the second apparatus comprises: means for subscribing, to a second network entity, to an IoT registration event for the IoT service; and means for receiving, from the second network entity, a notification of a registration of the IoT device.

[0212] In some example embodiments, the second apparatus comprises means for creating a device context of the IoT device in response to the registration of the IoT device.

[0213] In some example embodiments, the second apparatus comprises means for providing content of the device context to the first apparatus.

[0214] In some example embodiments, the device context comprises at least one of: a unique identity of the IoT device, identities of one or more IoT services to which the IoT device subscribes, a device type of the IoT device, a location of the IoT device, an identity of a cell to which the IoT device is attached, an identity of a terminal device associated with the IoT device, one or more parameters related to a power supply of the IoT device, or capability information of the IoT device.

[0215] In some example embodiments, the second apparatus comprises means for performing, with the first network entity, an authentication of the IoT device in response to the registration of the IoT device.

[0216] In some example embodiments, the configuration information is received from the first network entity.

[0217] In some example embodiments, the configuration information comprises one or more parameters of a query to the IoT service to request data from the IoT device.

[0218] In some example embodiments, the configuration information comprises at least one of an indication whether the query is triggered periodically or triggered by an event, a second query command to initiate the query in case the query is triggered periodically, or a configuration of the query in case the query is triggered periodically.

[0219] In some example embodiments, the second apparatus further comprises means for performing the operations of the method 800 or other operations in some example embodiments of the second network device 120. In some example embodiments, the means comprises at least one processor; and at least one memory storing instructions which, when executed by the at least one processor, cause the execution of the second apparatus.

[0220] Figure 1 is a simplified block diagram of a device 900 suitable for implementing example embodiments of the present disclosure. The device 900 can be used to implement a communication device, such as the first network device 110, the terminal device 130, or the second device 120 shown. As shown, the device 900 includes one or more processors 910, one or more memories 920 coupled to the processor(s) 910, and one or more communication modules 940 coupled to the processor(s) 910. Figures 3-8

[0221] The communication module 940 is for bidirectional communication. The communication module 940 has one or more communication interfaces to facilitate communication with one or more other modules or devices. The communication interface can represent any interface necessary to communicate with other network elements. In some example embodiments, the communication module 940 can include at least one antenna.

[0222] As non-limiting examples, the processor(s) 910 can be of any type suitable to the local technical network and can include one or more of general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on multi-core processor architectures, as non-limiting examples. The device 900 can have multiple processors such as a dedicated integrated circuit chip that is clocked in time from a synchronous master processor.

[0223] The memory 920 can include one or more non-transitory memories and one or more transitory memories. Examples of non-transitory memories include, but are not limited to, read-only memory (ROM) 924, electrically programmable read-only memory (EPROM), flash memory, hard drive, compact disc (CD), digital video disc (DVD), optical disc, laser disc, and other magnetic and / or optical storage. Examples of transitory memories include, but are not limited to, random access memory (RAM) 922 and other volatile memory that will not persist for more than a duration of power loss.

[0224] ​The computer program 930 includes computer-executable instructions executed by the associated processor 910. The instructions of the program 930 can include instructions for performing the operations / acts of some example embodiments of the present disclosure. The program 930 can be stored in a memory, such as the ROM 924. The processor 910 can perform any suitable action and processing by loading a program 930 into the RAM 922.

[0225] Example embodiments of the present disclosure can be implemented with the aid of the program 930, such that the apparatus 900 can perform any processes of the present disclosure as discussed with reference to Figure 10 Example embodiments of the present disclosure can also be implemented by hardware or by a combination of software and hardware.

[0226] In some example embodiments, the program 930 can be tangibly embodied in a computer-readable medium, which can be included in the apparatus 900 (such as in the memory 920) or in another storage device accessible by the apparatus 900. The apparatus 900 can load the program 930 from the computer-readable medium into the RAM 922 for execution. In some example embodiments, the computer-readable medium can include any type of non-transitory storage medium, such as ROM, EPROM, flash memory, a hard disk, CD-ROM, DVD, etc. The term “non-transitory,” as used herein with respect to a medium, is merely to

[0227] ​ An example of a computer-readable medium 1000, which can be in the form of a CD, DVD, or other optical storage disk, is shown. The computer-readable medium 1000 has the program 930 stored thereon.

[0228] In general, the various embodiments of the present disclosure can be implemented in hardware or special-purpose circuits, software, logic or any combination thereof. Some aspects can be implemented in hardware, while other aspects can be implemented in firmware or software which can be executed by a controller, microprocessor or other computing device, although the embodiments are not limited thereto. While various aspects of embodiments of this disclosure can be illustrated and described as block diagrams, flow charts, or using some other pictorial representation, it is well understood that these blocks, apparatus, systems, techniques or methods described herein can be implemented in hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controlers or other computing devices, or some combination thereof.

[0229] Some example embodiments of the present disclosure also provide at least one computer program product tangibly stored on a computer readable medium, such as a non-transitory computer readable medium. The computer program product includes computer executable instructions, such as those included in program modules, executed by devices, such as on a target physical or virtual processor, to perform any of the methods as described above. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The functionality of the program modules can be combined or split between program modules as desired in various embodiments. Machine executable instructions for program modules can be executed within a local or distributed device. In a distributed device, program modules can be located in both local and remote storage media.

[0230] Program code for carrying out methods of the present disclosure can be written in any combination of one or more programming languages. The program code can be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the program code, when executed by the processor or controller, causes the machine to perform the functions / operations specified in the flow diagrams and / or block diagrams. The program code can be executed entirely on a machine, partially on a machine, as a stand-alone software package, partially on a machine and partially on a remote machine or entirely on a remote machine or server.

[0231] In the context of the present disclosure, computer program code or related data can be embodied by any suitable carrier wave, including a signal, computer readable medium, etc.

[0232] The computer readable medium can be a computer readable signal medium or a computer readable storage medium. The computer readable medium can include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of the computer readable storage medium would include an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0233] Moreover, while operations may be depicted in a particular order, this should not be understood as requiring such order nor that all illustrated operations be performed, to achieve desirable results. In certain circumstances, multitasking and parallel processing can be advantageous. Likewise, while several specific implementation details have been included herein, these should not be taken as limiting the scope of the disclosure, but rather as describing features that can be specific to particular embodiments. Certain features that are described in the context of separate embodiments can also be implemented in combination with each other. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments, singly or in any suitable sub-combination.

[0234] Although the present disclosure has been described in language specific to structural features and / or methodological acts, it is to be understood that the present disclosure defined in the appended claims is not necessarily limited to the specific features or acts described. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.

Claims

1. A first network device, comprising: at least one processor; as well as At least one memory storing instructions, which, when executed by the at least one processor, cause the first network device to at least perform: receiving, from a second network device, configuration information about an Internet of Things (IoT) service, to which an IoT device subscribes, the IoT device being attached to the first network device; and A device context for the IoT device is created based at least on the configuration information.

2. The first network device according to claim 1, wherein the first network device is configured to perform: receiving content related to the device context from the second network device, and The device context is created based on the content and the configuration information.

3. The first network device of claim 1 , wherein the first network device is configured to: The device context is updated based on a change in the state of the IoT device.

4. The first network device according to any one of claims 1 to 3, wherein the device context comprises at least one of the following: The unique identifier of the IoT device, the identifiers of one or more IoT services subscribed by the IoT device, The device type of the IoT device, The location of the IoT device, The identity of the cell to which the IoT device is attached, The identifier of the terminal device associated with the IoT device, One or more parameters related to the power supply of the IoT device, The IoT device's capability information, or The configuration information. 5 . The first network device according to claim 1 , wherein the configuration information comprises one or more parameters of a query from the IoT service to request data from at least the IoT device.

6. The first network device according to claim 5, wherein the one or more parameters include at least one of the following: an indication of whether the query is triggered periodically or by an event, Initiate a second query command of the query to the IoT device when the query is periodically triggered, or Configuration of the query in case the query is triggered periodically.

7. The first network device according to any one of claims 5 to 6, wherein the first network device is configured to perform: The query is performed based on the device context of the IoT device.

8. The first network device of claim 7, wherein the query is triggered by the event, and the first network device is caused to perform: receiving a first query command from a first network entity to initiate the query; and The first query command is sent directly to the IoT device, or is sent to the IoT device via the terminal device associated with the IoT device.

9. The first network device according to claim 8, wherein the first query command comprises at least one of the following: including the identifiers of one or more IoT services of the IoT service, or One or more unique identifiers of the IoT device.

10. The first network device of claim 7, wherein the query is triggered periodically, and the first network device is caused to perform: Determining a time opportunity for initiating the query based on the configuration information; and At the time opportunity, the second query command is sent directly to the IoT device, or is sent to the IoT device via the terminal device associated with the IoT device.

11. A second network device, comprising: at least one processor; as well as at least one memory storing instructions, which, when executed by the at least one processor, cause the second network device to at least execute: Determine the IoT services subscribed by IoT devices; Determining configuration information about the IoT service; and The configuration information is provided to a first network device to which the IoT device is attached.

12. The second network device according to claim 11, wherein the second network device is configured to perform: receiving a request for registering the IoT service from a first network entity, the second request including service information about the IoT service; Registering the IoT service based on the service information; and A service context of the IoT service is created based on the service information.

13. The second network device according to claim 12, wherein the service context comprises at least one of the following: The identifier of the IoT service, The address of the server that provides the IoT service, The coverage of the IoT service, The unique identifier of one or more IoT devices that subscribe to the IoT service, or The configuration information.

14. The second network device according to any one of claims 11 to 13, wherein the second network device is configured to perform: subscribing to an IoT registration event for the IoT service from a second network entity; and A notification of registration of the IoT device is received from the second network entity.

15. The second network device according to any one of claims 11 to 14, wherein the second network device is configured to perform: In response to the registration of the IoT device, a device context of the IoT device is created.

16. The second network device according to claim 15, wherein the second network device is caused to perform: The content of the device context is provided to the first network device.

17. The second network device according to any one of claims 15 to 16, wherein the device context comprises at least one of the following: The unique identifier of the IoT device, the identifiers of one or more IoT services subscribed by the IoT device, The device type of the IoT device, The location of IoT devices, The identity of the cell to which the IoT device is attached, The identifier of the terminal device associated with the IoT device, One or more parameters related to the power supply of the IoT device, or Capability information of the IoT device.

18. The second network device according to any one of claims 11 to 17, wherein the second network device is configured to perform: In response to the registration of the IoT device, authentication of the IoT device is performed using a first network entity.

19. The second network device according to any one of claims 11 to 18, wherein the configuration information is received from a first network entity.

20. The second network device according to any one of claims 11 to 19, wherein the configuration information comprises one or more parameters of a query from the IoT service to request data from the IoT device.

21. The second network device according to claim 20, wherein the configuration information comprises at least one of the following: an indication of whether the query is triggered periodically or by an event, Initiate a second query command of the query when the query is periodically triggered, or Configuration of the query in case the query is triggered periodically.

22. A method comprising: receiving, at a first network device, configuration information about an Internet of Things (IoT) service from a second network device, the IoT service being subscribed to by an IoT device, the IoT device being attached to the first network device; as well as A device context for the IoT device is created based at least on the configuration information.

23. A method comprising: determining, at the second network device, an IoT service subscribed to by the IoT device; Determining configuration information about the IoT service; as well as The configuration information is provided to a first network device to which the IoT device is attached.

24. A first device comprising: means for receiving, from a second apparatus, configuration information about an Internet of Things (IoT) service, the IoT service being subscribed to by an IoT device, the IoT device being attached to the first apparatus; as well as Means for creating a device context for the IoT device based at least on the configuration information.

25. A second device comprising: A component for determining IoT services subscribed to by an IoT device; A component for determining configuration information about the IoT service; as well as means for providing the configuration information to a first apparatus, to which the IoT device is attached.

26. A computer-readable medium comprising instructions stored thereon, the instructions being configured to cause an apparatus to at least perform the method of claim 22 or the method of claim 23.

Images