WO2024182981A1

WO2024182981A1 - Ambient iot management

Info

Publication number: WO2024182981A1
Application number: PCT/CN2023/079917
Authority: WO
Inventors: Yonggang Wang; Muhammad Majid BUTT; Ahlem KHLASS; Hua Chao
Original assignee: Nokia Shanghai Bell Co Ltd; Nokia Solutions and Networks Oy
Current assignee: Nokia Shanghai Bell Co Ltd; Nokia Solutions and Networks Oy
Priority date: 2023-03-06
Filing date: 2023-03-06
Publication date: 2024-09-12
Anticipated expiration: 2025-09-06
Also published as: CN120814271A

Abstract

Embodiments of the present disclosure relate to devices, methods, apparatuses and computer readable storage media for ambient Internet of Things (IoT) management. A method comprising: at a first device, receiving, from a second network device, configuration information regarding an Internet of Things, IoT, service subscribed by to 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.

Description

AMBIENT IOT MANAGEMENT

FIELDS

Various example embodiments of the present disclosure generally relate to the field of telecommunication and in particular, to methods, devices, apparatuses and computer readable storage medium for ambient Internet of Things (IoT) management.

BACKGROUND

IoT technologies are expected to drastically change landscape of various industries. Ambient IoT (AIoT) is a promising field in both the 5th Generation Mobile Communication Technology (5G) new radio (NR) and academy. The ambient IoT refers to the IoT without power and energy sources. Specifically, the ambient IoT terminal node, which is also referred to as an ambient IoT device or tag, obtains energy from the environment. For example, an ambient IoT device based on wireless electromagnetic energy capture technology may capture and collect energy by collecting radio waves to complete data collection, transmission and distributed computing, etc. Therefore, there is a need to manage the ambient IoT device.

SUMMARY

The embodiments of the disclosure provide one or more network devices, one or more corresponding methods, and one or more computer readable medium 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.

Also disclosed is a first network device. The first network device comprises at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the first network device at least to perform: receiving, from a second network device, configuration information regarding an Internet of Things, IoT, service subscribed 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.

Also disclosed is a second network device. The second network device comprises at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the second network device at least to perform: determining an Internet of Things, IoT, service subscribed by an IoT device; determining configuration information regarding the IoT service; and providing the configuration information to a first network device to which the IoT device is attached.

Also disclosed is a method. The method comprises: receiving, at a first network device from a second network device, configuration information regarding an Internet of Things, IoT, service subscribed 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.

Also disclosed is a method. The method comprises: determining, at a second network device, an Internet of Things, IoT, service subscribed by an IoT device; determining configuration information regarding the IoT service; and providing the configuration information to a first network device to which the IoT device is attached.

Also disclosed is a first apparatus. The first apparatus comprises means for receiving, from a second apparatus, configuration information regarding an Internet of Things, IoT, service subscribed by an IoT device, the IoT device being attached to the first network device; and means for creating a device context of the IoT device based at least on the configuration information.

Also disclosed is a second apparatus. The second apparatus comprises means for determining an Internet of Things, IoT, service subscribed by an IoT device; means for determining configuration information regarding the IoT service; and means for providing the configuration information to a first apparatus to which the IoT device is attached.

Also disclosed is a computer readable medium. The computer readable medium comprises instructions stored thereon for causing an apparatus to perform at least the method according to the third aspect.

Also disclosed is a computer readable medium. The computer readable medium comprises instructions stored thereon for causing an apparatus to perform at least the method according to the fourth aspect.

It is to be understood that the Summary section is not intended to identify key or essential features of embodiments of the present disclosure, nor is it intended to be used to limit the scope of the present disclosure. Other features of the present disclosure will become easily comprehensible through the following description.

BRIEF DESCRIPTION OF THE DRAWINGS

Some example embodiments will now be described with reference to the accompanying drawings, where:

FIG. 1 illustrates an example communication environment in which example embodiments of the present disclosure can be implemented;

FIG. 2A illustrates an example communication environment including general network functions (NFs) according to some example embodiments of the present disclosure;

FIG. 2B illustrates an example communication environment including a dedicated network function according to some example embodiments of the present disclosure;

FIG. 3 illustrates a signaling chart for IoT management according to some example embodiments of the present disclosure;

FIG. 4 illustrates a signaling chart for IoT management using general network functions according to some example embodiments of the present disclosure;

FIG. 5 illustrates a signaling chart for IoT management using a dedicated network function according to some example embodiments of the present disclosure;

FIG. 6 illustrates a signaling chart for performing the query according to some example embodiments of the present disclosure;

FIG. 7 illustrates a flowchart of a method implemented at a first network device according to some example embodiments of the present disclosure;

FIG. 8 illustrates a flowchart of a method implemented at a second network device according to some example embodiments of the present disclosure;

FIG. 9 illustrates a simplified block diagram of a device that is suitable for implementing example embodiments of the present disclosure; and

FIG. 10 illustrates a block diagram of an example computer readable medium in accordance with some example embodiments of the present disclosure.

Throughout the drawings, the same or similar reference numerals represent the same or similar element.

DETAILED DESCRIPTION

Principle of the present disclosure will now be described with reference to some example embodiments. It is to be understood that these embodiments are described only for the purpose of illustration and help those skilled in the art to understand and implement the present disclosure, without suggesting any limitation as to the scope of the disclosure. Embodiments described herein can be implemented in various manners other than the ones described below.

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

References in the present disclosure to “one embodiment, ” “an embodiment, ” “an example embodiment, ” and the like indicate that the embodiment described may include a particular feature, structure, or characteristic, but it is not necessary that every embodiment includes the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.

It shall be understood that although the terms “first, ” “second” and the like may 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 example embodiments. As used herein, the term “and/or” includes any and all combinations of one or more of the listed terms.

As used herein, “at least one of the following: <a list of two or more elements>” and “at least one of <a list of two or more elements>” and similar wording, where the list of two or more elements are joined by “and” or “or” , mean at least any one of the elements, or at least any two or more of the elements, or at least all the elements.

As used herein, unless stated explicitly, performing a step “in response to A” does not indicate that the step is performed immediately after “A” occurs and one or more intervening steps may be included.

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” , “has” , “having” , “includes” and/or “including” , when used herein, specify the presence of stated features, elements, and/or components etc., but do not preclude the presence or addition of one or more other features, elements, components and/or combinations thereof.

As used in this application, the term “circuitry” may 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) any portions of hardware processor (s) with software (including digital signal processor (s) ) , software, and memory (ies) 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 the software may not be present when it is not needed for operation.

This 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 of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and/or firmware. The term circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device.

As used herein, the term “communication network” refers to a network following any suitable communication standards, 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) and so on. Furthermore, the communications between a terminal device and a network device in the communication network may be performed according to any suitable generation communication protocols, including, but not limited to, the first generation (1G) , the second generation (2G) , 2.5G, 2.75G, the third generation (3G) , the fourth generation (4G) , 4.5G, the fifth generation (5G) communication protocols, and/or any other protocols either currently known or to be developed in the future. Embodiments of the present disclosure may be applied in various communication systems. Given the rapid development in communications, there will of course also be future type communication technologies and systems with which the present disclosure may be embodied. It should not be seen as limiting the scope of the present disclosure to only the aforementioned system.

As used herein, the term “network device” refers to a node in a communication network via which a terminal device accesses the network and receives services therefrom. The network device may refer to a base station (BS) or an access point (AP) , for example, a node B (NodeB or NB) , an evolved NodeB (eNodeB or eNB) , an NR NB (also referred to as a gNB) , a Remote Radio Unit (RRU) , a radio header (RH) , a remote radio head (RRH) , a relay, an Integrated Access and Backhaul (IAB) node, a low power node such as a femto, a pico, a non-terrestrial network (NTN) or non-ground network device such as a satellite network device, a low earth orbit (LEO) satellite and a geosynchronous earth orbit (GEO) satellite, an aircraft network device, and so forth, depending on the applied terminology and technology. In some example embodiments, radio access network (RAN) split architecture comprises a Centralized Unit (CU) and a Distributed Unit (DU) at an IAB donor node. An IAB node comprises a Mobile Terminal (IAB-MT) part that behaves like a UE toward the parent node, and a DU part of an IAB node behaves like a base station toward the next-hop IAB node.

The term “terminal device” refers to any end device that may be capable of wireless communication. By way of example rather than limitation, a terminal device may 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) . The terminal device may include, but not limited to, a mobile phone, a cellular phone, a smart phone, voice over IP (VoIP) phones, wireless local loop phones, a tablet, a wearable terminal device, a personal digital assistant (PDA) , portable computers, desktop computer, image capture terminal devices such as digital cameras, gaming terminal devices, music storage and playback appliances, vehicle-mounted wireless terminal devices, wireless endpoints, mobile stations, laptop-embedded equipment (LEE) , laptop-mounted equipment (LME) , USB dongles, smart devices, wireless customer-premises equipment (CPE) , an Internet of Things (loT) device, a watch or other wearable, a head-mounted display (HMD) , a vehicle, a drone, a medical device and applications (e.g., remote surgery) , an industrial device and applications (e.g., a robot and/or other wireless devices operating in an industrial and/or an automated processing chain contexts) , a consumer electronics device, a device operating on commercial and/or industrial wireless networks, and the like. The terminal device may also correspond to a Mobile Termination (MT) part of an IAB node (e.g., a relay node) . In the following description, the terms “terminal device” , “communication device” , “terminal” , “user equipment” and “UE” may be used interchangeably.

As used herein, the term “resource, ” “transmission resource, ” “resource block, ” “physical resource block” (PRB) , “uplink resource, ” or “downlink resource” may refer to any resource for performing a communication, for example, a communication between a terminal device and a network device, such as a resource in time domain, a resource in frequency domain, a resource in space domain, a resource in code domain, or any other resource enabling a communication, and the like. In the following, unless explicitly stated, a resource in both frequency domain and time domain will be used as an example of a transmission resource for describing some example embodiments of the present disclosure. It is noted that example embodiments of the present disclosure are equally applicable to other resources in other domains.

It is noted that any section/subsection headings provided herein are not intended to be limiting. Embodiments are described throughout this document, and any type of embodiment may be included under any section/subsection. Furthermore, embodiments disclosed in any section/subsection may be combined with any other embodiments described in the same section/subsection and/or a different section/subsection in any manner.

The term “ambient IoT device” , “passive IoT” or “IoT device” is used herein. However, it is to be understood that in some example embodiments, the term “ambient IoT device” , “passive IoT” or “IoT device” may be also referred to as “tag” . The terms “ambient IoT device” and “passive IoT” can be used interchangeably.

As briefly mentioned above, the ambient IoT is a promising technology. Some design targets have been agreed. The design targets include improved link budget compared to existing RFID solutions, frequency bands for global useability (for example, 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 micro-Watts, to enable operation with back-scattering or energy harvesting) , small device size and form-factor, positioning accuracy (e.g., 3m -5m) , data rate (e.g., 10m -100 kbps) , ambient devices based on backscattering techniques, semi-ambient devices operating with energy harvesting or with a very small battery (e.g., <100mAh) , mobile originated and mobile terminated data.

Ambient IoT technology is also a promising technology for 3rd Generation Partnership Project. For example, some studies target at a new 3GPP IoT technology, suitable for deployment in a 3GPP system, which relies on ultra-low complexity devices with ultra-low power consumption for the very-low end IoT applications.

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

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

Currently, it has been studied for the aforementioned scenarios where backscattering ambient IoT devices are supported by cellular networks. Advanced radio technologies are studied, such as to extend the communication range of ambient IoT devices with supporting backscattering communications. Multi-illuminator deployment in the 5G cells and the bistatic or multi-static configuration is also considered.

In an example scenario, multiple illuminators as well as receivers (or readers) may be deployed depending on the density of the tags and their locations. These illuminators and receivers may be 5G terminal devices. Thus, these illuminators and receivers have the characteristics of 5G terminal device and can communicate with gNB for example by following the legacy procedures. The illuminators and receivers are optimally deployed nearby the ambient IoT devices in order to reduce transmit power requirements on these ambient IoT devices.

In the coverage of a 5G cell, tags may be non-uniformly distributed with high density in some areas and low density in other areas. The terminal devices, tags and illuminators and receivers could move within the cell, across cells and may even roam to a different cellular network coverage, if available.

It would be beneficial for an application server if the ambient IoT devices are registered at the network with known location, just like the legacy NR, so that these ambient IoT devices can be efficiently queried by the application server when needed. However, due to the potential movement of the ambient IoT devices, it is more complicated for the application server to query the ambient IoT devices.

Therefore, the following problem needs to be solved: how to and manage ambient IoT devices, including register, store and update the information associated with ambient IoT device, in cellular networks given their very large number and extremely low power transmission capabilities.

There are different potential ways for the network to (re-) discover the tags. A potential way is tag-enabled discovery for the first time. When a tag is deployed and connected for the first time to the network, the factory circuit protection is removed and the tag is connected manually. Usually, this operation might be done on site, so the handheld reader or writer (which is also a 5G terminal device) can recognize the tag and register the information of the tag to the network.

In another possible way, the tag can have its own energy storage and can sleep and wake up accordingly and autonomously (for example, no need for network pre-configuration) . In this case, the battery is usually used for sensor power supply, rather than wireless signal transmission. During the interval between potential data collection, the tag will enter sleep state. Accordingly, the network needs regular polling or query to discover or rediscovery the tag. When the tag is in a sleep state, it will not backscatter the polling signal to reduce the potential uplink collision.

A further way is tag mobility. The tag moves from one cell to another cell, for example, tags in logistics. In contrast to current mobility management procedure for legacy NR UEs, the tags cannot actively inform the network of its mobility status, so the network can only be informed on the location of the tag through regular polling or query.

Given the above observations and in order to enable efficient tag management at the network (including registration, authentication, context maintenance) , the following problems need to be solved. A problem is which network functions will be involved and what new interfaces and behaviors are to be defined. Another problem is due to that the tags should not be treated as legacy NR UEs as they have specific connectivity and mobility requirements. Accordingly, it needs to be defined what (new) procedures and functionalities shall be enhanced and/or re-designed to ensure the connectivity of the tags in 3GPP cellular networks and to solve the problem of tag mobility.

According to some example embodiments of the present disclosure, there is provided a solution for IoT management. In the solution, a core network (CN) function may register one or more IoT services and create respective service contexts of the one or more IoT services. If an IoT device is registered, the core network function determines an IoT service subscribed by the IoT device. Then, the core network function provides configuration information regarding the IoT service to a radio access network (RAN) node to which the IoT device is attached. The RAN node creates a device context of the IoT device based on the configuration information. For example, the configuration information may be incorporated into the device context.

In this way, management of the IoT device is enabled at the core network. Moreover, at the RAN, the configuration information is combined with the device context. In this way, the IoT device can be quickly and accurately found to fulfill the IoT service. It is to be noted that although the above problems are described with respect to ambient IoT devices, the concept of the example embodiments of the present disclosure are applicable to any type of IoT devices.

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

Example environment

FIG. 1 illustrates an example communication environment 100 in which example embodiments of the present disclosure can be implemented. 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 example of FIG. 1, the first network device 110 may be a RAN node serving the terminal device 130. The serving area of the first network device 110 may be called a cell 102, and the serving area may be configured with the plurality of cells. In an example, the terminal device 130 may be a UE and the first network device 110 may be a base station (for example, a gNB) serving the UE.

The IoT device 140, or a tag, is attached to the first network device 110 and associated with the terminal device 130. The IoT device 140 may be of any type. Particularly, in some example embodiments, the IoT device 140 may be an ambient 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, a receiver or a reader for the IoT device. The communication between the network and IoT device 140 is performed via the associated terminal device. In some embodiments, the communication may be performed between the network device 110 and the IoT device 140 without terminal device 130.

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

Communications in the communication environment 100 may be implemented according to any proper communication protocol (s) , comprising, but not limited to, cellular communication protocols of the first generation (1G) , the second generation (2G) , the third generation (3G) , the fourth generation (4G) , the fifth generation (5G) , the sixth generation (6G) , and the like, wireless local network communication protocols such as Institute for Electrical and Electronics Engineers (IEEE) 802.11 and the like, and/or any other protocols currently known or to be developed in the future. Moreover, the communication may utilize any proper wireless communication technology, comprising 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 (OFDM) , Discrete Fourier Transform spread OFDM (DFT-s-OFDM) and/or any other technologies currently known or to be developed in the future.

In general, the second network device 120 may implement functionalities to manage IoT services (for example, AIoT services) , including but not limited to service registration, service authentication and service initialization and maintenance. The second network device 120 may further implement functionalities to manage IoT devices (for example, AIoT devices) , including but not limited to, device registration, device authentication and device context initialization and maintenance. These functionalities may be referred to as IoT management functionalities in the following.

In some example embodiments, one or more of the above IoT management functionalities may be implemented by one or more general network functions in the CN, for example, Access and Mobility Management Function (AMF) , Session Management Function (SMF) , and Network Exposure Function (NEF) . Reference is now made to FIG. 2A. FIG. 2A illustrates an example communication environment 200A including general network functions.

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

The gNB 210 communicates with AMF 260 via an N2 interface. The UE communicates with the AMF 260 via an N1 interface. The environment 200A further includes SMF 222, NEF 221 and a Unified Data Repository (UDR) 223. The NEF can communicate with an application function (AF) 250, which is an example implementation of the network entity 150. Internet protocol (IP) flows come into the CN through a User plane Function (UPF) 270. The UPF 270 communicates with the gNB 210 via an N3 interface.

In the example environment 200A, one or more of the NEF 221, SMF 222, UDR 223 and AMF 260 may implement the IoT management functionalities. Such an example will be described above below with reference to FIG. 5.

Alternatively, in some example embodiments, one or more of the IoT management functionalities may be implemented by a network function dedicated for IoT management, which may be referred to as PIoT or AIoT Management Function (PMF) . Reference is now made to FIG. 2B. FIG. 2B illustrates an example communication environment 200B including the dedicated network function. The elements with the same reference number are the same as those described above with reference to FIG. 2A and thus description thereof is not repeated.

In the communication environment 200B, the PMF 220 communicates with the AMF 260 and the AF 250. The IoT management functionalities may be implemented by the PMF 220. Such an example will be described above below with reference to FIG. 5.

Example signaling chart for IoT management

In example embodiments of present disclosure, the second network device 120 may determine configuration information regarding an IoT service subscribed by an IoT device and provide the configuration information to the first network device 110.

FIG. 3 illustrates a signaling chart 300 for IoT management according to some example embodiments of the present disclosure. The signaling chart 300 is described with reference to FIG. 1 as an example. The signaling chart 300 involves the first network device 110, the second network device 120 and optionally the network entity 150. However, it is to be understood that the signaling chart 300 may involves more devices or less devices, and the number of devices illustrated in FIG. 3 is only for the purpose of illustration without suggesting any limitations.

The second network device 120 provides, to the first network device 110, configuration information regarding an IoT service subscribed by an IoT device 140. To this end, in some example embodiments, registration of the IoT device 140 and IoT service may be performed. An example procedure is shown in FIG. 3.

The second network device 120 may receive (305) a request for registering the IoT service, from the network entity 150, which is also referred to as “service registration request” . The request comprises service information regarding the IoT service. The service information may include, but not limited to, a type of an IoT device, a range or list of identifications of the target IoT devices. The request may further include another information, for example, the ID of the network entity 150, subscription information, etc. It is to be noted that if the identifications of the target IoT devices are continuous, the range or the list of the identifications may be included, and if the identifications of the target IoT devices are not continuous, the list of the identifications may be included.

Then, the second network device 120 may register (310) the IoT service based on the service information. For example, the second network device 120 may perform mapping of the service information and store the service information locally or in a data repository, for example, the UDR.

The second network device 120 may 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.

The service context may include an identification of the IoT service, for example, a service ID, a service name, etc. Alternatively, or in addition, the service context may include an address of a server provisioning the IoT service, for example, an address of a computing system hosting the IoT service. Alternatively, or in addition, the service context may include a scope of a coverage of the IoT service, for example, involved cells for some local services.

Subsequently, in some example embodiments, the service context may 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 may transmit a request indicating the change and the second network device 120 may update the service context of the IoT device 140 accordingly.

In some example embodiments, the second network device 120 may authenticate the IoT service based on subscription information or local policy. For example, the second network device 120 may check the authorization certificate of the IoT service.

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

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 may perform device-service mapping. The device-service mapping may be performed based on the service context or the service information. For example, if the unique identification (UID) of the IoT device 140 is included in the range or the list of the identifications of the target IoT devices, the second network device 120 may determine that the IoT service is subscribed by the IoT device 140. In some example embodiments, the second network device 120 may further perform authentication of the IoT device 140 with the network entity 150. For example, a list of IoT devices, e.g., UIDs, may be checked by the network entity 150. If the UID of the IoT device 140 is included in the list of authorized IoT devices, authentication of the IoT device 140 is successful.

The second network device 120 determines 335 the configuration information regarding the IoT service, which is also referred to as service configuration information. The configuration information may include any suitable parameters of an operation associated with the IoT service. In some example embodiments, the operation may include a query to the IoT device 140 issued from the IoT service. Through the query, the IoT service may request data from the IoT device 140. For example, if the IoT device 140 comprises a sensor, the IoT service may request the IoT device 140 to report its sensing data.

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

Alternatively, or in addition, if the query is triggered periodically, the query parameters may include configuration of the periodic query. The configuration may include a period of the query, and/or a time offset of the query. Based on the configuration, a time occasion for transmitting the query command can be determined.

It is to be understood that although some example embodiments are described with respect to the query, it is an example without any limitation. The aspects described with respect to the query are applicable to other operation associated with the IoT service.

The above example embodiments are described with respect to an individual IoT device. It is to be understood that more than one IoT device may be attached to the first network device 110. Accordingly, the query may be associated with one or more IoT devices including the IoT device 140. In other words, the IoT service may request data from the one or more IoT devices and the configuration information is applicable to the query to the one or more IoT devices.

To determine the configuration information, in some example embodiments, the second network device 120 may communicate with the network entity 150 to obtain the configuration information from the network entity 150. Alternatively, or in addition, in some example embodiments, the service context may include the configuration information and the second network device 120 may retrieve the configuration information from the service context. For example, if the registration request for the IoT service may include the configuration information, when creating the service context, the second network device 120 may incorporate the configuration information into the service context.

In some example embodiments, the second network device 120 may further create 340 a device context of the IoT device 140. The de vice context is used to record any suitable content related to the IoT device 140.

In some example embodiments, the device context may include a UID of the IoT device 140. Alternatively, or in addition, the device context may include identifications of one or more IoT services subscribed by the IoT device 140. It is to be understood that service subscription can be independent to device and/or server deployment. and it is possible that one certain IoT device can be registered to more than one services. Therefore, the device context may include IDs of a plurality of IoT services.

Alternatively, or in addition, the device context may include a device type of the IoT device 140. Alternatively, or in addition, the device context may include a location of the IoT device 140. The location may be a geographic location of the IoT device 140, which may be represented by coordinates. The location may have any suitable precision.

Alternatively, or in addition, the device context may include an association relationship of the IoT device 140 with another entity in the communication system, for example, a base station, or UE, etc. For example, the device context may include an identification of a cell to which the IoT device 140 is attached, for example, a cell ID. For another example, the device context may include an identification of a terminal device with which the IoT device 140 is associated, for example, an ID of the UE with which the IoT device 140 is associated.

Alternatively, or in addition, the device context may include one or more parameters related to power supply of the IoT device 140. For example, the device context may indicate whether the IoT device 140 has a power supply or battery, whether energy can be harvested by the IoT device 140, whether the IoT device 140 has a sleep cycle, etc.

Alternatively, or in addition, the device context may include capability information of the IoT device 140. For example, the device context may indicate an operating frequency, maximum response distance, etc.

Given that that IoT device 140 subscribes the IoT service, the second network device 120 may associate the IoT device 140 with the IoT service. For example, the second network device 120 may build binding information between the service context of the IoT service and the device context of the IoT device 140 and store it. In this way, if there is any change to the service context, the device context can be updated accordingly.

In addition, in some example embodiments, in response to the registration of the IoT device, the service context may be updated to include the UID of the IoT device 140 subscribing the IoT service.

Continuing with the signaling chart 300, the second network device 120 provides 345 the configuration information to the first network device 110 to which the IoT device 140 is attached. The configuration information may be provided to the first network device 110 directly or via another network entity.

The first network device 110 receives the configuration information and creates (350) a device context of the IoT device 140 based on the configuration information. For example, if a previous version of the device context has been created, the first network device 110 may incorporate the configuration information into the previous version to update the contents of the device context. For another example, the first network device 110 may generate contents of the device context at least based on the configuration information.

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

In other words, in such example embodiments, the contents of the device context of the IoT device 140 can be transferred and inherited from an upstream entity to a downstream entity.

In some example embodiments, if there is a change in a status of the IoT device 140, the device context may be updated based on the change. The status of the IoT device 140 may include but not limited to the location of the IoT device 140, a subscription status (such as, which service is subscribed by the IoT device 140) , an association with one or more terminal devices. For example, if the association relationship between the IoT device 140 and terminal devices is changed, the device context may be updated to include the ID of a new terminal device with which the IoT device 140 is associated.

After the device context is created based on the configuration information, the first network device 110 may perform an operation associated with the IoT service according to the device context. In some example embodiments, the query to the IoT device 140 from the IoT service may be performed based on the device context. Such example embodiments will be described below with reference to FIG. 6.

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

As can be seen from the example procedure described above, the one or more NFs may manage IoT service, including at least service registration, service authentication and service initialization and maintenance. For example, the IoT service may be authenticated based on subscription information or local policy, for example by checking the authorization certificate. For another example, IoT service context may be maintained (for example, be created, stored and updated) based on the registration request from the 3^rd party AF. For a further example, IoT device registration event may be subscribed and/or unsubscribed from a network function (e.g., AMF or SMF) . Moreover, binding information between the IoT service context and the subscribed IoT device (s) can be built and stored.

In another aspect, the one or more NFs may manage IoT device, including at least device registration, device authentication and device context initialization and maintenance. For example, new device registration may be detected based on device-initiated procedure and notify the subscribed NF. For another example, the device context may be maintained (for example, created, stored and updated) , if the authentication of the IoT device is finished successfully, for example the UID of the IoT device is included in the list of authorized IoT device (s) . For a further example, the device context may be transferred to the target RAN in case of mobility.

An example procedure for IoT management is described with reference to FIG. 3. Some more example embodiments are described below.

Example signaling chart in the case of general NFs

As mentioned above, in some example embodiments, the IoT management functionalities may be implemented by one or more general NFs. FIG. 4 illustrates a signaling chart 400 for IoT management using general NFs according to some example embodiments of the present disclosure. The signaling chart 400 may be implemented in the communication environment 200A and involve the IoT device 240, UE 230, gNB 210, AMF 260, SMF 222, UDR 223, NEF 221, and AF 250. However, it is to be understood that the signaling chart 400 may involves more entities or less entities, and the number of entities illustrated in FIG. 4 is only for the purpose of illustration without suggesting any limitations.

In general, the signaling chart 400 comprises 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 to the communication system with certain service parameters. For example, a new Nnef_service request or an existing Nnef_service request may be used to initiate the service registration procedure 450.

As shown in FIG. 4, the AF 250 may transmit (402) to the NEF 221 a request for registering an IoT service, which is also referred to as service request. The service request may be used to invoke the NEF 221 to create service parameters for the IoT service. The request may include service information regarding the IoT service, for example, a type of target IoT devices, a range or list of identifications for target IoT devices. The request may further include an address of the AF application, subscription information regarding IoT device registration, etc. For example, the subscription information may include the range or the list of identifications of the target IoT devices subscribing the IoT service.

In response to the request, the NEF 221 may identify (404) the service and store the service information in the UDR 223. The NEF 221 may store any other suitable information in the UDR 223, for example, descriptions, parameters of the IoT service, and IoT service information (e.g., Type of service, service UID, etc…) etc.

In the example as shown in FIG. 4, the NEF 221 may create (406) a service context of the IoT service. The explanation of the service context is the same as or similar to that described above with reference to FIG. 3, and thus description thereof is not repeated here. Alternatively, in some example embodiments, the service context may be created in the unified data management (UDM) . In such example embodiments, the NEF 221 may forward the received request to the UDM (not shown in FIG. 4) .

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

Through the above service registration procedure 450, the IoT service is registered in the core network. The service context of the IoT service can be maintained in the core network.

During the device registration procedure 460, an IoT device attachment procedure may be performed (412) among the gNB 210, the UE 230 and the IoT device 240. After the attachment procedure is finished successfully, the IoT device 240 is attached to the gNB 210 and is associated with the UE 230. Then, the UE 230 may initiate the registration of the IoT device 240. As shown in FIG. 4, the UE 230 may transmit (414) an IoT device registration request to the AMF 260. For example, the UE 230 may initiate the device registration procedure by transmitting a device registration request.

The registration request may include device information regarding the IoT device 240. The device information may include the UID of the IoT device 240 and any other information or parameter related to the IoT device 240. The registration request may further include an ID of a Protocol Data Unit (PDU) session, a data network name (DNN) , a single network slice selection assistance information (S-NSSAI) , which can help identifying the IoT device 240. In some example embodiments, a Non-Access Stratum (NAS) signaling may be used to carry the registration request. In addition, the registration request or the device information may include an ID of the terminal device with which the IoT device 240 is associated.

The AMF 260 may 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 may be included in a Nsmf_service request. Other information, such as the PDU session ID, DDN and S-NSSAI may also be forwarded to the SMF 222.

Upon receiving the device information, the SMF 222 may detect an IoT device registration event. Accordingly, the SMF 22 may associate the ID of the UE 230 and the UID of the IoT device 240. In other words, the SMF 222 may bind the reported UE ID and the carried-on IoT device UID.

Then, the SMF 222 may notify the new registered UID to the NEF 221 which subscribed this event. As shown in FIG. 4, the SMF 222 may transmit (418) a notification of the registration of the IoT device 240. The notification may include the UID of the IoT device 240 and any other suitable information related to the IoT device 240. In an example, the notification may be included in a Nsmf_EventExposure service message.

The NEF 221 may perform (420) device-service mapping. In other words, the NEF 221 may determine one or more IoT service subscribed by the IoT device 240. The mapping may be performed based on the service information stored in the UDR 223 or the service context created (406) during the service registration procedure. If the UID of the IoT device 240 is included in the service information or the service context as one identification of the range or the list of identifications of target IoT devices, and/or the ID of the IoT service is included in the device information, the NEF 221 may associate the IoT device 240 with the IoT service. The NEF 221 may further perform a device authentication of the IoT device 240 with the AF 250. For example, a list of the IoT device (s) , e.g., comprising UIDs, may be checked by the AF 250. If the UID of the IoT device 240 is included in the list of the authorized IoT device (s) , the device authentication of the IoT device 240 is successful.

In some example embodiments, after the IoT device 240 has been registered, the NEF 221 may request (422) from the AF 250 for configuration information regarding the IoT device, for example, service configuration parameters, and receive the requested configuration information. The configuration information is similar to that described above with reference to FIG. 3 and thus description thereof is not repeated here. Alternatively, or in addition, in some example embodiments, the NEF 221 may request the configuration information from the AF 250 after the service response is transmitted (408) , or the NEF 221 may include a request for the configuration information within the service response.

The configuration information may be transferred (424) from the NEF 221 to the SMF 222. In some example embodiments, the configuration information may be transferred via a Policy Control function (PCF, not shown in FIG. 4) . The device authentication result of the new registered IoT device 240 may be also informed to the SMF 222 in terms of the UID of the IoT device 240. The configuration information may be carried in an Nnef service or Npcf/Nsmf service message.

If the UID of the IoT device 240 is included, the SMF 222 may derives the corresponding UE based on the stored binding information of UE IDs and UIDs of IoT devices. In this example, the SMF 222 determines that the IoT device 240 is associated with the UE 230. The SMF 222 may create (426) a device context of the IoT device 240. The explanation of the device context is the same or similar to that described above with reference to FIG. 3 and thus description thereof is not repeated here.

The SMF 222 may inform the serving AMF for the associated UE about the received indication of the IoT device 240 and the configuration information. In this example, the SMF 222 may transmit (428) the configuration information to the AMF 260. The configuration information may be carried in a Nsmf_service message.

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

Then, the AMF 260 may transmit (432) the configuration information to the gNB 210. For example, the AMF 260 may transmit the device registration response including the configuration information to the gNB 210 through 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.

While the IoT device 240 is registered in the core network and authenticated by the AF 250, the gNB 210 may create (434) the device context of the IoT device 240. For example, the device context may be created at least based on the configuration information. The context device may be created further based on device information of the IoT device 240, for example, which may be provided to the gNB 210 during the IoT device attachment procedure (412) . For example, the device context may be first created based on the device information obtained during the IoT device attachment procedure (412) and then updated based on the configuration information.

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

In some example embodiments, the SMF 222 may provide contents of the device context created (426) at the SMF 222 to the gNB 210 via the AMF 260. The gNB 210 may create its own device context based on the provided contents. In other words, the device context may be transferred and inherited from the SMF 222 to the gNB 210.

As can be seen, the device context may be transferred and inherited from the core network to the RAN.

In some example embodiments, the UE initiates the transmission (414) of the registration request is not the same that in the device attachment procedure (412) . Accordingly, the gNB 210 may update the device context with the new relationship between the IoT device 240 and the UE with which the IoT device 240 is associated.

In some example embodiments, the gNB 210 may provide (436) the configuration information to the UE 230 with which the IoT device 240 is associated. For example, the configuration information may be transmitted to the UE 230 through a radio resource control (RRC) reconfiguration signaling.

In the example embodiments described with reference to FIG. 4, the IoT management can be enhanced by using some general NFs.

Example signaling chart in the case of dedicated NF

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

FIG. 5 illustrates a signaling chart for IoT management using the dedicated network function according to some example embodiments of the present disclosure. The signaling chart 500 may be implemented in the communication environment 200B and involve the IoT device 240, UE 230, gNB 210, AMF 260, PMF 220, and AF 250. However, it is to be understood that the signaling chart 500 may involves more entities or less entities, and the number of entities illustrated in FIG. 3 is only for the purpose of illustration without suggesting any limitations.

In general, the signaling chart 500 comprises a service registration procedure 550 and a device registration procedure 560. During the service registration procedure 550, the AF 250 initiates a new IoT service creation procedure to the communication system with certain service parameters. For example, a Npmf_ServiceParameter_Create request may be used to initiate the service registration procedure 550.

As shown in FIG. 5, the AF 250 may transmit (502) to the PMF 220 a request for registering an IoT service, which is also referred to as service request. The service request may be used to invoke the PMF 220 to create service parameters for the IoT service. The request may include service information regarding the IoT service, for example, a type of target IoT devices, UIDs of the target IoT devices, or a range or list of identifications of target IoT devices. The request may further include an ID of the AF application, subscription information regarding IoT device registration, etc. For example, the subscription information may include UIDs of the target IoT devices subscribing the IoT service.

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

The PMF 220 may create (504) a service context of the IoT service. The explanation of the service context is the same as or similar to that described above with reference to FIG. 3, and thus description thereof is not repeated here. Alternatively, in some example embodiments, the service context may be created in the unified data management (UDM) . In such example embodiments, the PMF 220 may forward the received request to the UDM (not shown in FIG. 4) .

The PMF 220 then may transmit (506) a service response to the service request to the AF 250. For the successful created IoT service, the PMF 220 may subscribe (508) an IoT device registration event in the core network. In this way, when an IoT device registration event is detected by the core network (e.g., the AMF 260) , the event will be notified to the PMF 220, as described below.

Through the above procedure 550, the IoT service is registered in the core network. The service context of the IoT service can be maintained in the core network.

During the device registration procedure 560, an IoT device attachment procedure may be performed (510) among the gNB 210, the UE 230 and the IoT device 240. After the attachment procedure is finished successfully, the IoT device 240 is attached to the gNB 210 and is associated with the UE 230. Then, the UE 230 may initiate the registration of the IoT device 240. As shown in FIG. 5, the UE 230 may transmit (512) an IoT device registration request to the AMF 260. For example, the UE 230 may initiate the device registration procedure by transmitting a device registration request.

The registration request may include device information regarding the IoT device 240. The device information may include the UID of the IoT device 240 and any other information or parameter related to the IoT device 240. The registration request may further include an ID of a PDU session, a DNN, an S-NSSAI, which can help identifying the IoT device 240. In some example embodiments, a NAS signaling may be used to carry the registration request.

Upon receiving registration request, the AMF 260 may detect an IoT device registration event. Accordingly, the AMF 260 may associate the ID of the UE 230 and the UID of the IoT device 240. In other words, the AMF 260 may bind the reported UE ID and the carried-on IoT device UID.

Then, the AMF 260 may notify the new registered UID to the PMF 220 which subscribed this event. As shown in FIG. 5, the AMF 260 may transmit (514) a notification of the registration of the IoT device 240. The notification may include the UID of the IoT device 240 and any other suitable information related to the IoT device 240. In an example, the notification may be included in a Npmf_service message.

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

The PMF 220 may further perform a device authentication of the IoT device 240 with the AF 250. For example, a list of the IoT device (s) may be checked by the AF 250. If the UID of the IoT device 240 is included in the list of the authorized IoT device (s) , the device authentication of the IoT device 240 is successful.

In some example embodiments, after the IoT device 240 has been registered, the PMF 220 may request (518) from the AF 250 for configuration information regarding the IoT device, for example, service configuration parameters. The configuration information is similar to that described above with reference to FIG. 3 and thus description thereof is not repeated here. Alternatively, or in addition, in some example embodiments, the PMF 220 may request the configuration information from the AF 250 after the service response is transmitted (506) , or the PMF 220 may include a request for the configuration information within the service response.

The PMF 220 may create (520) a device context of the IoT device 240. The explanation of the device context is the same as or similar to that described above with reference to FIG. 3 and thus description thereof is not repeated here.

The PMF 220 may inform the serving AMF for the associated UE about the IoT device 240 and the configuration information. In this example, the PMF 220 may transmit (522) the configuration information to the AMF 260. The configuration information may be carried in a Npmf_service message.

Upon receiving the configuration information, the AMF 260 may create (524) a device context of the IoT device 240. The device context is similar to that describe d above with reference to FIG. 3 and thus description thereof is not repeated here. The deice context may be created based on the configuration information. For example, the configuration information may be incorporated into the device context. In some example embodiments, the PMF 220 may provide contents of the device context created (520) at the PMF 220 to the AMF 260. The AMF 260 may create its own device context based on the provided contents. In other words, the device context may be transferred and inherited from the PMF 220 to the AMF 260.

Then, the AMF 260 may transmit (526) the configuration information to the gNB 210. For example, the AMF 260 may transmit the device registration response including the configuration information to the gNB 210 through 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.

While the IoT device 240 is registered in the core network and authenticated by the AF 250, the gNB 210 may create (528) the device context of the IoT device 240. For example, the device context may be created at least based on the configuration information. The context device may be created further based on device information of the IoT device 240, for example, which may be provided to the gNB 210 during the IoT device attachment procedure (510) . For example, the device context may be first created based on the device information obtained during the IoT device attachment procedure (510) and then updated based on the configuration information.

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

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

In some example embodiments, the UE initiates the transmission (512) of the registration request is not the same that in the device attachment procedure (510) . Accordingly, the gNB 210 may update the device context with the new relationship between the IoT device 240 and the UE with which the IoT device 240 is associated.

In some example embodiments, the gNB 210 may provide (530) the configuration information to the UE 230 with which the IoT device 240 is associated. For example, the configuration information may be transmitted to the UE 230 through an RRC reconfiguration signaling.

The advantage of introducing a new NF is that the operation and signaling associated with ambient IoT can be grouped together. The AIoT features can be evolved independently to other features as much as possible, and the impact to the functionalities of the existing NF are minimal.

In these example embodiments, the PMF 220 undertakes the functionalities distributed in the NEF 221, the UDR 223 and the SMF 222 as shown in FIG. 4. Their operation, signaling initiation and termination are all included in the PMF 220. However, it is to be noted that in some example embodiments, the signaling interaction between the AF 250 and PMF 220 (for example, the acts 502 and 506) may need to be forwarded through the NEF, which is a provision of the core network from a security perspective.

Example signaling chart for query

As briefly mentioned above, in some example embodiments, the query to the IoT device 140 from the IoT service may be performed based on the device context of the IoT device 140. Reference is now made to FIG. 6. FIG. 6 illustrates a signaling chart 600 for performing the query according to some example embodiments of the present disclosure. The signaling chart 600 involves the first network device 110, the terminal device 130, the IoT device 140 and the network entity 150. However, it is to be understood that the signaling chart 600 may involves more devices or less devices, and the number of devices illustrated in FIG. 6 is only for the purpose of illustration without suggesting any limitations.

In some example embodiments, the query may be triggered periodically. The procedure 650 shows an example of the periodic query. In this example embodiments, the configuration information may include a query command, which is also referred to as a second query command.

The first network device 110 may determine a time occasion for initiating the query based on the configuration information. For example, the time occasion may be determined based on the period and time offset of the query. At the determined time occasion, the first network device 110 may transmit the second query command to the IoT device 140 directly or via the terminal device 130 with which the IoT device 140 is associated. For example, if the first network device 110 is located within the maximum response distance of the IoT device 140 and the IoT device is not associated with any terminal device, the query command may be transmitted directly to the IoT device 140.

In the example of FIG. 6, the first network device 110 may transmit (602) the second query command to the terminal device 130 with which the IoT device 140 is associated. The terminal device 130 may forward (604) the second query command to the IoT device 140.

In response to the second query command, the IoT device 140 may transmit (606) data report to the terminal device 130, which may then forward (608) the data report to the first network device 110. Alternatively, the IoT device 140 may transmit the data report to the first network device 110 directly. The first network device 110 further forward (610) the data report to the network entity 150. In this way, the application can get its desired data. The periodic query action is the initiative of the RAN without participation of the AF.

As mentioned above, in some example embodiments, the query may be associated with a plurality of IoT devices attached to the first network device 110, including the IoT device 140. In this case, the first network device 110 may determine respective device contexts of the plurality of IoT devices from all the device contexts maintained by the first network device 110. Based on the respective device contexts, the first network device 110 may perform the query to each of the plurality of IoT devices, as similarly to the procedure 650.

In some example embodiments, the query may be triggered by an event. The procedure 660 shows an example of the event triggered query. In this example embodiments, triggered by an event, the network entity 150 may transmit (612) a query command to the first network device 110, which is also referred to as a first query command.

The first network device 110 may transmit the first query command to the IoT device 140 directly, or via the terminal device 130 with which the IoT device 140 is associated. In the example of FIG. 6, the first network device 110 may transmit (614) the first query command to the terminal device 130 with which the IoT device 140 is associated. The terminal device 130 may forward (616) the first query command to the IoT device 140.

In response to the first query command, the IoT device 140 may transmit (618) data report to the terminal device 130, which may then forward (620) the data report to the first network device 110. Alternatively, the IoT device 140 may transmit the data report to the first network device 110 directly. The first network device 110 further forward (622) the data report to the network entity 150. In this way, the application can get its desired data.

As mentioned above, in some example embodiments, the query may be associated with a plurality of IoT devices attached to the first network device 110, including the IoT device 140. Alternatively, or in addition, the query may be from a plurality of IoT services, which means that these IoT services need data from the same IoT device.

Given that, in some example embodiments, the first query command may include identifications of one or more IoT services comprising the IoT service, or UIDs of one or more IoT devices comprising the IoT device 140. In such example embodiments, the first network device 110 may determine respective device contexts of the one or more IoT devices from all the device contexts maintained by the first network device 110. Based on the respective device contexts, the first network device 110 may perform the query to each of the one or more of IoT devices, as similarly to the procedure 660. If more than one IoT service requests data from the same IoT device, for example, from the IoT device 140, the data from the IoT device 140 may be distributed to each of these IoT services by the network entity 150.

Through the above description, the network device in the CN implements core network functionalities to expose query capability to the 3rd party AF and allow the AF to request data with certain requirements to the communication system. Both the event triggered query (for example, immediate query) and the periodic query can be supported. Moreover, a query request can interpret be to query parameters, and the query parameters can be transferred to the RAN. The network device in the RAN implements functionalities to store the query parameters and to perform the query accordingly.

In the 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 (for example, obtained during attachment procedure) . In this way, the RAN can find the IoT device quicky and accurately. Therefore, the query can be executed efficiently.

Example Methods

FIG. 7 shows a flowchart of an example method 700 implemented at a first network device in accordance with some example embodiments of the present disclosure. For the purpose of discussion, the method 700 will be described from the perspective of the first network device 110 in FIG. 1.

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

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

In some example embodiments, the first network device 110 may receive, from the second network device 120, contents related to the device context. The device context is created based on the contents and the configuration information.

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

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

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.

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 the case the query is triggered periodically, or a configuration of the query in the case the query is triggered periodically.

In some example embodiments, the first network device 110 may perform the query based on the device context of the IoT device.

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

In some example embodiments, the first query command comprises at least one: identifications of one or more IoT services comprising the IoT service, or unique identifications of one or more IoT devices comprising the IoT device.

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

FIG. 8 shows a flowchart of an example method 800 implemented at a second network device in accordance with some example embodiments of the present disclosure. For the purpose of discussion, the method 800 will be described from the perspective of the second network device 120 in FIG. 1. In some example embodiments, the method 700 may be implemented at one or more of the NEF, AMF, SMF and UDR. In some example embodiments, the method 700 may be implemented at the PMF.

At block 810, the second network device 120 determines an IoT service subscribed by an IoT device.

At block 820, the second network device 120 determines configuration information regarding the IoT service.

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

In some example embodiments, the second network device 120 may receive, from a first network entity, a request for registering the IoT service, the second request comprising service information regarding the IoT service; register the IoT service based on the service information; and create a service context of the IoT service based on the service information.

In some example embodiments, the service context comprises at least one of: an identification of the IoT service, an address of a server provisioning the IoT service, a scope of a coverage of the IoT service, unique identifications of one or more IoT devices subscribing the IoT service, or the configuration information.

In some example embodiments, the second network device 120 may subscribe, to a second network entity, an IoT registration event for the IoT service; and receive, from the second network entity, a notification of registration of the IoT device.

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

In some example embodiments, the second network device 120 may provide contents of the device context to the first network device 110.

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

In some example embodiments, in response to registration of the IoT device, the second network device 120 may perform an authentication of the IoT device with a first network entity.

In some example embodiments, the configuration information is received from a first network entity.

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

In some example embodiments, the configuration information comprises 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 in the case the query is triggered periodically, or a configuration of the query in the case the query is triggered periodically.

Example Apparatus, Device and Medium

In some example embodiments, a first apparatus capable of performing any of the method 700 (for example, the first network device 110 in FIG. 1) may comprise means for performing the respective operations of the method 700. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module. The first apparatus may be implemented as or included in the first network device 110 in FIG. 1.

In some example embodiments, the first apparatus comprises means for receiving, from a second apparatus, configuration information regarding an Internet of Things, IoT, service subscribed by to 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.

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

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

In some example embodiments, the one or more parameters compri se 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 the case the query is triggered periodically, or a configuration of the query in the case the query is triggered periodically.

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

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

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 transmitting, at the time occasion, a second query command to the IoT device directly, or via a terminal device with which the IoT device is associated.

In some example embodiments, the first apparatus further comprises means for performing other operations in some example embodiments of the method 700 or the first network device 110. In some example embodiments, the means comprises at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the performance of the first apparatus.

In some example embodiments, a second apparatus capable of performing any of the method 800 (for example, the second network device 120 in FIG. 1) may comprise means for performing the respective operations of the method 800. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module. The second apparatus may be implemented as or included in the second network device 120 in FIG. 1.

In some example embodiments, the second apparatus comprises means for determining an Internet of Things, IoT, service subscribed by an IoT device; means for determining configuration information regarding the IoT service; and means for providing the configuration information to a first apparatus to which the IoT device is attached.

In some example embodiments, the second apparatus comprises means for receiving, from a first network entity, a request for registering the IoT service, the second request comprising service information regarding 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.

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

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

In some example embodiments, the second apparatus comprises means for providing contents of the device context to the first apparatus.

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

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

FIG. 9 is a simplified block diagram of a device 900 that is suitable for implementing example embodiments of the present disclosure. The device 900 may be provided to implement a communication device, for example, the first network device 110, the terminal device 130 or the second device 120 as shown in FIG. 1. As shown, the device 900 includes one or more processors 910, one or more memories 920 coupled to the processor 910, and one or more communication modules 940 coupled to the processor 910.

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

The processor 910 may be of any type suitable to the local technical network and may include one or more of the following: general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on multicore processor architecture, as non-limiting examples. The device 900 may have multiple processors, such as an application specific integrated circuit chip that is slaved in time to a clock which synchronizes the main processor.

The memory 920 may include one or more non-volatile memories and one or more volatile memories. Examples of the non-volatile memories include, but are not limited to, a Read Only Memory (ROM) 924, an electrically programmable read only memory (EPROM) , a flash memory, a hard disk, a compact disc (CD) , a digital video disk (DVD) , an optical disk, a laser disk, and other magnetic storage and/or optical storage. Examples of the volatile memories include, but are not limited to, a random access memory (RAM) 922 and other volatile memories that will not last in the power-down duration.

A computer program 930 includes computer executable instructions that are executed by the associated processor 910. The instructions of the program 930 may include instructions for performing operations/acts of some example embodiments of the present disclosure. The program 930 may be stored in the memory, e.g., the ROM 924. The processor 910 may perform any suitable actions and processing by loading the program 930 into the RAM 922.

The example embodiments of the present disclosure may be implemented by means of the program 930 so that the device 900 may perform any process of the disclosure as discussed with reference to FIG. 3 to FIG. 8. The example embodiments of the present disclosure may also be implemented by hardware or by a combination of software and hardware.

In some example embodiments, the program 930 may be tangibly contained in a computer readable medium which may be included in the device 900 (such as in the memory 920) or other storage devices that are accessible by the device 900. The device 900 may load the program 930 from the computer readable medium to the RAM 922 for execution. In some example embodiments, the computer readable medium may include any types of non-transitory storage medium, such as ROM, EPROM, a flash memory, a hard disk, CD, DVD, and the like. The term “non-transitory, ” as used herein, is a limitation of the medium itself (i.e., tangible, not a signal) as opposed to a limitation on data storage persistency (e.g., RAM vs. ROM) .

FIG. 10 shows an example of the computer readable medium 1000 which may be in form of CD, DVD or other optical storage disk. The computer readable medium 1000 has the program 930 stored thereon.

Generally, various embodiments of the present disclosure may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device. While various aspects of embodiments of the present disclosure are illustrated and described as block diagrams, flowcharts, or using some other pictorial representations, it is to be understood that the block, apparatus, system, technique or method described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.

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, being executed in a device on a target physical or virtual processor, to carry out any of the methods as described above. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, or the like that perform particular tasks or implement particular abstract data types. The functionality of the program modules may be combined or split between program modules as desired in various embodiments. Machine-executable instructions for program modules may be executed within a local or distributed device. In a distributed device, program modules may be located in both local and remote storage media.

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

In the context of the present disclosure, the computer program code or related data may be carried by any suitable carrier to enable the device, apparatus or processor to perform various processes and operations as described above. Examples of the carrier include a signal, computer readable medium, and the like.

The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable medium may include but not limited to an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More spe cific 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.

Further, while operations are depicted in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In certain circumstances, multitasking and parallel processing may be advantageous. Likewise, while several specific implementation details are contained in the above discussions, these should not be construed as limitations on the scope of the present disclosure, but rather as descriptions of features that may be specific to particular embodiments. Unless explicitly stated, certain features that are described in the context of separate embodiments may also be implemented in combination in a single embodiment. Conversely, unless explicitly stated, various features that are described in the context of a single embodiment may also be implemented in a plurality of embodiments separately or in any suitable sub-combination.

Although the present disclosure has been described in languages 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 above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.

Claims

A first network device comprising:

at least one processor; and

at least one memory storing instructions that, when executed by the at least one processor, cause the first network device at least to perform:

receiving, from a second network device, configuration information regarding an Internet of Things, IoT, service subscribed 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.
The first network device of claim 1, wherein the first network device is caused to perform:

receiving, from the second network device, contents related to the device context, and

wherein the device context is created based on the contents and the configuration information.
The first network device of claim 1, wherein the first network device is caused to perform:

updating the device context based on a change in a status of the IoT device.
The first network device of any of claims 1-3, wherein the device context comprises at least one of:

a unique identification of the IoT device,

identifications of one or more IoT services subscribed by the IoT device,

a device type of the IoT device,

a location of the IoT device,

an identification of a cell to which the IoT device is attached,

an identification of a terminal device with which the IoT device is associated,

one or more parameters related to power supply of the IoT device,

capability information of the IoT device, or

the configuration information.
The first network device of any of claims 1-4, 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.
The first network device of claim 5, wherein 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 the case the query is triggered periodically, or

a configuration of the query in the case the query is triggered periodically.
The first network device of any of claims 5-6, wherein the first network device is caused to perform:

performing the query based on the device context of the IoT device.
The first network device of claim 7, wherein the query is triggered by an event, and the first network device is caused to perform:

receiving, from a first network entity, a first query command to initiate the query; and

transmitting the first query command to the IoT device directly, or via the terminal device with which the IoT device is associated.
The first network device of claim 8, wherein the first query command comprises at least one:

identifications of one or more IoT services comprising the IoT service, or

unique identifications of one or more IoT devices comprising the IoT device.
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 occasion for initiating the query based on the configuration information; and

transmitting, at the time occasion, a second query command to the IoT device directly, or via a terminal device with which the IoT device is associated.
A second network device comprising:

at least one processor; and

at least one memory storing instructions that, when executed by the at least one processor, cause the second network device at least to perform:

determining an Internet of Things, IoT, service subscribed by an IoT device;

determining configuration information regarding the IoT service; and

providing the configuration information to a first network device to which the IoT device is attached.
The second network device of claim 11, wherein the second network device is caused to perform:

receiving, from a first network entity, a request for registering the IoT service, the second request comprising service information regarding the IoT service;

registering the IoT service based on the service information; and

creating a service context of the IoT service based on the service information.
The second network device of claim 12, wherein the service context comprises at least one of:

an identification of the IoT service,

an address of a server provisioning the IoT service,

a scope of a coverage of the IoT service,

unique identifications of one or more IoT devices subscribing the IoT service, or

the configuration information.
The second network device of any of claims 11-13, wherein the second network device is caused to perform:

subscribing, to a second network entity, an IoT registration event for the IoT service; and

receiving, from the second network entity, a notification of registration of the IoT device.
The second network device of any of claims 11-14, wherein the second network device is caused to perform:

in response to registration of the IoT device, creating a device context of the IoT device.
The second network device of claim 15, wherein the second network device is caused to perform:

providing contents of the device context to the first network device.
The second network device of any of claims 15-16, wherein the device context comprises at least one of:

a unique identification of the IoT device,

an identification of one or more IoT services subscribed by the IoT device,

a device type of the IoT device,

a location of the IoT device,

an identification of a cell to which the IoT device is attached,

an identification of a terminal device with which the IoT device is associated,

one or more parameters related to power supply of the IoT device, or

capability information of the IoT device.
The second network device of any of claims 11-17, wherein the second network device is caused to perform:

in response to registration of the IoT device, performing an authentication of the IoT device with a first network entity.
The second network device of any of claims 11-18, wherein the configuration information is received from a first network entity.
The second network device of any of claims 11-19, wherein the configuration information comprises one or more parameters of a query from the IoT service to request data from the IoT device.
The second network device of claim 20, wherein the configuration information comprises 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 in the case the query is triggered periodically, or

a configuration of the query in the case the query is triggered periodically.
A method comprising:

receiving, at a first network device from a second network device, configuration information regarding an Internet of Things, IoT, service subscribed by to 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.
A method comprising:

determining, at a second network device, an Internet of Things, IoT, service subscribed by an IoT device;

determining configuration information regarding the IoT service; and

providing the configuration information to a first network device to which the IoT device is attached.
A first apparatus comprising:

means for receiving, from a second apparatus, configuration information regarding an Internet of Things, IoT, service subscribed by to 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.
A second apparatus comprising:

means for determining an Internet of Things, IoT, service subscribed by an IoT device;

means for determining configuration information regarding the IoT service; and

means for providing the configuration information to a first apparatus to which the IoT device is attached.
A computer readable medium comprising instructions stored thereon for causing an apparatus at least to perform the method of claim 22 or the method of claim 23.