Ambient internet-of-things configuration method and apparatus, and terminal and network-side device

Abstract

The present application belongs to the technical field of communications. Disclosed are an ambient Internet-of-Things (AIoT) configuration method and apparatus, and a terminal and a network-side device. The AIoT configuration method in an embodiment of the present application comprises: a terminal executing a first operation, the first operation comprising at least one of the following: receiving a paging message from a network-side device, wherein the paging message carries a first cause value, and the first cause value is used for indicating that a paging cause is that the network-side device expects the terminal to act as an AIoT read-write device; and receiving first configuration information from the network-side device, wherein the first configuration information is configuration information related to the AIoT read-write device.

Description

Ambient Internet of Things configuration method and device, terminal and network side equipment

[0001] Cross-reference to Related Applications

[0002] The present application is based on the Chinese patent application No. 202410901939.9, filed on July 5, 2024, and claims the priority of the Chinese patent application No. 202410901939.9, the whole content of which is incorporated herein by reference. TECHNICAL FIELD

[0003] The present application relates to the field of communication technology, in particular to an Ambient Internet of Things configuration method and device, a terminal and a network side equipment. BACKGROUND

[0004] In related technologies, a terminal can communicate with an Ambient Internet of Things (AIoT) device (e.g., a Tag) as an AIoT Reader. Specifically, a network side equipment can control the terminal through air interface signaling, the terminal communicates with the AIoT device through AIoT communication, and the terminal sends the AIoT communication content to the network side equipment through the air interface. However, there is no corresponding solution in related technologies on how to configure the terminal as an AIoT Reader to perform AIoT communication. SUMMARY

[0005] Embodiments of the present application provide an Ambient Internet of Things configuration method and device, a terminal and a network side equipment, which can provide a way for the network side equipment to configure the terminal as an AIoT Reader to perform AIoT communication, and is beneficial to ensure the performance of AIoT communication.

[0006] In a first aspect, an Ambient Internet of Things configuration method is provided, the method comprising:

[0007] The terminal performs a first operation, the first operation comprising at least one of:

[0008] receiving a paging message from a network side equipment, the paging message carrying a first reason value, the first reason value indicating that the network side equipment expects the terminal to be an AIoT Reader;

[0009] receiving first configuration information from the network side equipment, the first configuration information being AIoT Reader related configuration information.

[0010] In a second aspect, an Ambient Internet of Things configuration device is provided, the device comprising:

[0011] The processing module is configured to perform a first operation, and the first operation comprises at least one of the following:

[0012] The network-side device receives a paging message from the terminal, and the paging message carries a first cause value, where the first cause value is used to indicate that a paging cause is that the network-side device expects the terminal to be an AIoT read-write device.

[0013] The network-side device receives first configuration information from the terminal, and the first configuration information is AIoT read-write device related configuration information.

[0014] In a third aspect, an AIoT configuration method is provided, and the method comprises the following steps:

[0015] The network-side device performs a second operation, and the second operation comprises at least one of the following:

[0016] The network-side device sends a paging message to the terminal, and the paging message carries a first cause value, where the first cause value is used to indicate that a paging cause is that the network-side device expects the terminal to be an AIoT read-write device.

[0017] The network-side device sends first configuration information to the terminal, and the first configuration information is AIoT read-write device related configuration information.

[0018] In a fourth aspect, an AIoT configuration apparatus is provided, and the apparatus comprises:

[0019] The processing module is configured to perform a second operation, and the second operation comprises at least one of the following:

[0020] The network-side device sends a paging message to the terminal, and the paging message carries a first cause value, where the first cause value is used to indicate that a paging cause is that the network-side device expects the terminal to be an AIoT read-write device.

[0021] The network-side device sends first configuration information to the terminal, and the first configuration information is AIoT read-write device related configuration information.

[0022] In a fifth aspect, an AIoT configuration apparatus is provided, and the apparatus is configured to perform the steps of the method according to the first aspect, or implement the steps of the method according to the third aspect.

[0023] In a sixth aspect, a terminal is provided, and the terminal comprises a processor and a memory, where the memory stores programs or instructions that can be run on the processor, and the programs or instructions are executed by the processor to implement the steps of the method according to the first aspect.

[0024] In a seventh aspect, a terminal is provided, comprising a processor and a communication interface, wherein the processor is configured to perform a first operation, the first operation comprising at least one of: receiving, from a network-side device, a paging message carrying a first cause value, the first cause value indicating that a paging cause is that the network-side device expects the terminal to be an AIoT read-write device; and receiving, from the network-side device, first configuration information, the first configuration information being AIoT read-write device related configuration information.

[0025] In an eighth aspect, a network-side device is provided, comprising a processor and a memory, the memory storing programs or instructions executable on the processor, the programs or instructions, when executed by the processor, implementing the steps of the method according to the third aspect.

[0026] In a ninth aspect, a network-side device is provided, comprising a processor and a communication interface, wherein the processor is configured to perform a second operation, the second operation comprising at least one of: sending, to a terminal, a paging message carrying a first cause value, the first cause value indicating that a paging cause is that the network-side device expects the terminal to be an AIoT read-write device; and sending, to the terminal, first configuration information, the first configuration information being AIoT read-write device related configuration information.

[0027] In a tenth aspect, a readable storage medium is provided, the readable storage medium storing programs or instructions, the programs or instructions, when executed by a processor, implementing the steps of the method according to the first aspect or implementing the steps of the method according to the third aspect.

[0028] In an eleventh aspect, a wireless communication system is provided, comprising a terminal and a network-side device, the terminal being configured to perform the steps of the AIoT configuration method according to the first aspect, and the network-side device being configured to perform the steps of the AIoT configuration method according to the third aspect.

[0029] In a twelfth aspect, a chip is provided, comprising a processor and a communication interface, the communication interface being coupled to the processor, and the processor being configured to run programs or instructions, implementing the steps of the method according to the first aspect or implementing the steps of the method according to the third aspect.

[0030] In a thirteenth aspect, a computer program / program product is provided, the computer program / program product being stored in a storage medium, the computer program / program product being executed by at least one processor to implement the steps of the method according to the first aspect or to implement the steps of the method according to the third aspect.

[0031] In the embodiments of the present application, the terminal can receive a paging message from the network side device, the paging message carrying a first cause value, the first cause value being used to indicate that the paging cause is that the network side device expects the terminal to be an AIoT read-write device, that is, the network side device can notify the terminal to be an AIoT read-write device for AIoT communication through the paging message, so that the terminal can be triggered to be an AIoT read-write device to assist AIoT communication in the case that the terminal is in the non-connected state, which expands the implementation architecture of AIoT communication and is beneficial to improving the efficiency of AIoT communication; and / or the terminal can receive first configuration information from the network side device, the first configuration information being AIoT read-write device related configuration information, that is, the network side device provides the terminal with related configuration information when the terminal is an AIoT read-write device, and then the terminal can perform AIoT communication based on the first configuration information, which is beneficial to ensuring the performance of the terminal as an AIoT read-write device for AIoT communication. BRIEF DESCRIPTION OF DRAWINGS

[0032] FIG. 1 is a block diagram of a wireless communication system to which embodiments of the present application can be applied;

[0033] FIG. 2a is a schematic diagram of an AIoT system according to an embodiment of the present application;

[0034] FIG. 2b is a schematic diagram of an AIoT system according to another embodiment of the present application;

[0035] FIG. 2c is a schematic diagram of an AIoT system according to another embodiment of the present application;

[0036] FIG. 3 is a flowchart of AIoT communication of a UE as an AIoT reader according to an embodiment of the present application;

[0037] FIG. 4 is a schematic diagram of the transition between RRC states according to an embodiment of the present application;

[0038] FIG. 5 is a flowchart of an environment IoT configuration method according to an embodiment of the present application;

[0039] FIG. 6 is a flowchart of another environment IoT configuration method according to an embodiment of the present application;

[0040] FIG. 7 is a flowchart of another environment IoT configuration method according to an embodiment of the present application;

[0041] FIG. 8 is a flowchart of another environment IoT configuration method according to an embodiment of the present application;

[0042] FIG. 9 is a flowchart of another environment IoT configuration method according to an embodiment of the present application;

[0043] FIG. 10 is a structural diagram of an environmental Internet of Things configuration apparatus according to an embodiment of the present application;

[0044] FIG. 11 is a structural diagram of another environmental Internet of Things configuration apparatus according to an embodiment of the present application;

[0045] FIG. 12 is a structural diagram of a communication device according to an embodiment of the present application;

[0046] FIG. 13 is a structural diagram of a terminal according to an embodiment of the present application;

[0047] FIG. 14 is a structural diagram of a network-side device according to an embodiment of the present application. DETAILED DESCRIPTION

[0048] The technical solutions in the embodiments of the present application will be clearly described below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only some of the embodiments of the present application, but not all of them. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art belong to the scope of protection of the present application.

[0049] The terms "first", "second", and the like in the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the terms used in this way can be interchanged under appropriate circumstances, so that the embodiments of the present application can be implemented in an order other than that illustrated or described herein, and the objects distinguished by "first", "second" are usually a category and do not limit the number of objects, for example, the first object can be one or more. In addition, "or" in the present application means at least one of the connected objects. For example, the protection scope of "A or B" at least covers three schemes, namely, scheme one: including A and not including B; scheme two: including B and not including A; scheme three: including A and B. In addition, the terms "A and / or B", "at least one of A and B", "at least one of A or B" also at least cover the above three schemes, respectively. The character " / " generally represents that the objects before and after are in an "or" relationship.

[0050] The term "indication" in the present application can be a direct indication (or explicit indication) or an indirect indication (or implicit indication). The direct indication can be understood as the sender explicitly informing the receiver of the specific information, the operation to be performed or the requested result, etc. in the sent indication. The indirect indication can be understood as the receiver determining the corresponding information according to the indication sent by the sender, or judging and determining the operation to be performed or the requested result according to the judgment result.

[0051] It is worth noting that the technology described in the embodiments of the present application is not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA) or other systems. The terms "system" and "network" in the embodiments of the present application are often used interchangeably, and the described technology can be used in the above-mentioned systems and radio technologies, as well as in other systems and radio technologies. The following description describes a New Radio (NR) system for example purposes, and NR terminology is used in most of the following description, but these technologies can also be applied to systems other than NR systems, such as 6th Generation (6G) communication systems. th

[0052] ​FIG. 1 shows a block diagram of a wireless communication system to which embodiments of the present application can be applied. The wireless communication system includes a terminal 11, a network-side device 12, and an AIoT device 13. The terminal 11 can also be referred to as a user equipment (UE). The terminal 11 can be a terminal-side device such as a mobile phone, a tablet personal computer, a laptop computer, a notebook computer, a personal digital assistant, a palmtop computer, a netbook, an ultra-mobile personal computer (UMPC), a mobile Internet device (MID), an augmented reality (AR) device, a virtual reality (VR) device, a robot, a wearable device, a flight vehicle, a vehicle user equipment (VUE), a shipboard device, a pedestrian user equipment (PUE), a smart home (a home device with a wireless communication function such as a refrigerator, a television, a washing machine, or furniture), a game console, a personal computer (PC), a kiosk, or a self-service machine. The wearable device includes a smart watch, a smart bracelet, a smart earphone, smart glasses, smart jewelry (a smart bracelet, a smart necklace, a smart ring, a smart necklace, a smart anklet, a smart necklace, etc.), a smart wristband, and smart clothing. The vehicle-mounted device can also be referred to as a vehicle-mounted terminal, a vehicle-mounted controller, a vehicle-mounted module, a vehicle-mounted component, a vehicle-mounted chip, or a vehicle-mounted unit. It should be noted that the specific type of the terminal 11 is not limited in the embodiments of the present application. It should be further noted that the terminal 11 can be a terminal with an AIoT read-write capability, or the terminal 11 can be a terminal with an AIoT read-write capability, or the terminal 11 can be a terminal supporting AIoT communication.

[0053] The network side device 12 can include an access network device or a core network device, wherein the access network device can also be referred to as a radio access network (RAN) device, a radio access network function or a radio access network unit. The access network device can include a base station (BS), a wireless local area network (WLAN) access point (AP) or a wireless fidelity (WiFi) node, etc. Among them, the base station can be referred to as a node B (NB), an evolved node B (eNB), a next generation node B (gNB), a new radio node B (NR node B), an access point, a relay base station (RBS), a serving base station (SBS), a base transceiver station (BTS), a radio base station, a radio transceiver, a basic service set (BSS), an extended service set (ESS), a home node B (HNB), a home evolved node B, a transmit / receive point (TRP), a non-terrestrial network (NTN) device (such as a satellite or a high altitude platform station, etc.) or some other suitable term in the art, as long as the same technical effect is achieved, the base station is not limited to a specific technical term. It needs to be explained that in the embodiments of the present application, only the base station in the NR system is taken as an example for introduction, and the specific type of the base station is not limited.

[0054] The core network device can also be referred to as a core network node, a core network function, or a core network network element, etc., which includes but is not limited to at least one of the following: a mobility management entity (MME), an access and mobility management function (AMF), a session management function (SMF), a user plane function (UPF), a policy control function (PCF), a policy and charging rules function (PCRF), an edge application server discovery function (EASDF), a unified data management (UDM), a unified data repository (UDR), a home subscriber server (HSS), a centralized network configuration (CNC), a network repository function (NRF), a network exposure function (NEF), a local NEF (or L-NEF), a binding support function (BSF), an application function (AF), a location management function (LMF), a gateway mobile location center (GMLC), a network data analytics function (NWDAF), a non-terrestrial network (NTN) device (such as a satellite or a high altitude platform station, etc.), and the like.It should be noted that, in the embodiments of the present application, only the core network device in the NR system is taken as an example for introduction, and the specific type of the core network device is not limited. If the name of the core network device mentioned in the embodiments of the present application changes in the subsequent protocol version (for example, 6G), it is also within the protection scope of the present application.

[0055] Optionally, the core network device can be implemented by one or more function modules in one device, or can be implemented by multiple devices together, and the embodiments of the present application do not make specific limitation thereto. It can be understood that the above function modules can be network elements in a hardware device, or software function modules running on a special hardware, or virtualized function modules instantiated on a platform (for example, a cloud platform) and the like.

[0056] The AIoT device 13 can also be referred to as an AIoT responding device. Exemplarily, the AIoT device 13 can be any device supporting backscatter communication technology or wireless radio frequency identification technology, and can include but is not limited to a tag or a terminal and the like. For example, the tag can be a radio frequency identification (RFID) tag.

[0057] For the convenience of understanding, some contents related to the embodiments of the present application are described as follows:

[0058] I. AIoT

[0059] As an IoT service composed of a large number of devices, the AIoT device has ultra-low complexity, ultra-low cost and ultra-low power consumption, and is powered by energy harvesting, and the device itself has no battery or only limited energy storage capacity, for example, using a capacitor.

[0060] In a wireless communication system, typically, the AIoT device collects energy from radio waves, which can come from a network device (for example, a base station) or a user equipment (UE).

[0061] 1. The AIoT device can include an AIoT device with the following characteristics:

[0062] i. The AIoT device with peak power consumption equal to or approximately equal to 1 μW has energy storage, and the device has no uplink and downlink signal amplification function. The uplink transmission of the AIoT device is backscattered on an externally provided carrier wave (CW, i.e., the above-mentioned radio wave).

[0063] ii. An AIoT device with peak power consumption less than or equal to several hundred μW, featuring energy storage and supporting uplink and / or downlink signal amplification. The uplink transmission of this AIoT device can be generated directly internally or through backscattering from an externally provided carrier source.

[0064] iii. An active device with energy storage, having active radio frequency components for transmission, and capable of independently generating signals.

[0065] 2. AIoT involves deployment scenarios with the following characteristics:

[0066] i. Topology 1

[0067] AIoT base stations and small base stations coexist at the same location. The base station acts as an AIoT read / write device, receiving AIoT service requests from the core network. The base station and AIoT devices communicate with each other, and the base station sends AIoT service responses back to the core network, as shown in Figure 2a.

[0068] ii. Topology II

[0069] AIoT base stations and large base stations coexist at the same location. The UE, as an intermediate node (AIoT read / write device), interacts with the core network to perform AIoT services. The base station controls the UE through air interface signaling, and the UE communicates with AIoT devices, as shown in Figure 2b.

[0070] iii. Topology 4

[0071] The UE, as an AIoT read / write device, directly communicates with AIoT devices, as shown in Figure 2c.

[0072] 3. The main business types of AIoT are: inventory and command issuance.

[0073] Inventory is the most basic and important business of AIoT, used to enable AIoT servers to learn about one or more known or unknown AIoT devices within the coverage area of ​​AIoT readers via the 3GPP network.

[0074] After recognizing that an AIoT device has been identified by the network, the AIoT server can issue commands to the device via the 3GPP network, which may include the commands shown in Table 1:

[0075] Table 1

[0076] 4、Based on the above service, the possible data transmission models of AIoT devices include: Device-terminated (DT), Device-originated-Device-terminated triggered (DO-DTT) based on Device-terminated transmission triggered, or Device-originated-Autonomous (DO-A). Among them, for the above DO-DTT, for example, asset identification, status reporting and tracking, the Reader collects data from the device by triggering the inventory program; for the above DO-A, for example, connecting a large number of various sensors, these sensors collect and actively report information about the environment, equipment and biology when necessary.

[0077] 5、For the solution of UE Reader (i.e. UE as Reader) selection in topology two, the network function (Network Function, NF) (such as AIoT function (AIoT Function, AIoTF)) selects the UE Reader suitable for the inventory service based on the capability of the inventoried AIoT device, the capability of the UE registered as the Reader, the location information, etc. Specifically, referring to FIG. 3, it can include the following steps:

[0078] Step 1, the UE performs a registration procedure. The UE transmits the AIoT Reader function (such as supported inventory frequency) to the AMF through a non-access layer (Non-access Stratum, NAS) message (such as a registration request message). The UE can also be referred to as an intermediate node UE.

[0079] Step 2, the AF sends the inventory request information to the AIoTF, including: inventory area information, AIoT device capability (such as supported inventory frequency), etc. The third party defined inventory area information indicates the area where the AIoT device is located.

[0080] Step 3, the AIoTF maps the third party defined information to the information defined in 3GPP. For example, the inventory area information is mapped to the cell identity (ID), which helps the AIoTF to select the AMF.

[0081] Step 4, the AIoTF obtains the information of the available UEs corresponding to the cell ID mapped in step 3 from the AMF. The UE information includes: UE ID, supported inventory frequency.

[0082] Step 5, AIoT F selects appropriate UE Reader to participate in the inventory process.

[0083] Step 6, inventory process is performed.

[0084] It should be noted that the present application mainly considers the scenario of topology two, how the UE is configured to become an AIoT Reader.

[0085] II. Radio Resource Control (RRC) state

[0086] Three different RRC states are defined for the UE in the NR system, i.e. RRC idle state (RRC_IDLE), RRC connected state (RRC_CONNECTED) and RRC inactive state or deactivation state (RRC_INACTIVE), the Next Generation Radio Access Network (NG-RAN) can realize the allocation and control of air interface resources by configuring the UE to enter different RRC states.

[0087] RRC_CONNECTED: the UE has an RRC connection with the NG-RAN, and can realize uplink and downlink data / signaling transmission, the access stratum (AS) context of the UE is stored in the NG-RAN and the UE, and the BS can directly realize the mobility management of the UE;

[0088] RRC_INACTIVE: the UE has no RRC connection with the NG-RAN, but the NG-RAN has a logical connection with the CN about the UE, the access stratum AS context of the UE is stored in the NG-RAN and the UE, and the UE controls the mobility (i.e. cell reselection, etc.) by itself;

[0089] RRC_IDLE: the UE has no RRC connection with the NG-RAN, and the NG-RAN has no logical connection with the CN about the UE, the NG-RAN does not store the access stratum AS context of the UE, and the UE controls the mobility (i.e. cell selection / reselection, etc.) by itself.

[0090] Among them, FIG. 4 is a schematic diagram of RRC state conversion provided by the embodiment of the present application.

[0091] III. Paging

[0092] As shown in FIG. 4, for the purpose of energy saving, when there is no service for the UE, the UE will enter the idle state or the inactive state, at this time, the specific area where the UE is located is not clear to the RAN and the CN, and if there is incoming service, the UE needs to be found first. The paging can enable the network to find the UE in RRC_INACTIVE and RRC_IDLE through a paging message, or can inform the UE that the system information has changed, etc.

[0093] The UE in RRC_IDLE listens to the paging message triggered by the core network (CN), and the UE in RRC_INACTIVE listens to the paging message triggered by the RAN and the CN.

[0094] The paging message is used to notify one or more UEs.

[0095] The environment Internet of Things configuration method provided by the embodiments of the present application will be described in detail in combination with the accompanying drawings, some embodiments and application scenarios.

[0096] Please refer to FIG. 5, which is a flowchart of an environment Internet of Things configuration method provided by the embodiments of the present application. The method can be executed by a terminal, as shown in FIG. 5, which includes the following steps:

[0097] In step 501, the terminal executes a first operation, which includes at least one of the following:

[0098] The terminal receives a paging message from a network side device, the paging message carrying a first cause value, the first cause value being used to indicate that the paging cause is that the network side device expects the terminal to be an AIoT read-write device;

[0099] The terminal receives first configuration information from the network side device, the first configuration information being AIoT read-write device related configuration information.

[0100] In an embodiment, the terminal receives a paging message from a network side device, for example, the terminal can receive the paging message from the network side device in a non-connected state, the paging message carrying a paging cause that the network side device expects the terminal to be an AIoT read-write device.

[0101] The non-connected state can include but is not limited to the deactivation state (INACTIVE) or the idle state (IDLE), etc. The deactivation state can be RRC_INACTIVE, and the idle state can be RRC_IDLE.

[0102] Exemplarily, the network-side device can determine the candidate terminal as the AIoT read-write device according to at least one of the capability of the terminal, the location information of the terminal, the RRC state of the terminal, the power of the terminal, the capability of the AIoT device, the location information of the AIoT device, the air interface link quality, and the AIoT link quality, and send a paging message to the candidate terminal, wherein the paging cause carried by the paging message is that the network-side device expects the terminal as the AIoT read-write device. The capability of the terminal can include whether the terminal is registered as an AIoT read-write device, whether the terminal has the capability as an AIoT read-write device, the AIoT service type supported by the terminal as an AIoT read-write device, the AIoT communication frequency supported by the terminal as an AIoT read-write device, and the like. The capability of the AIoT device can include the AIoT service type supported by the AIoT device, the AIoT communication frequency, and the like.

[0103] The first reason value carried by the paging message is used to indicate that the paging cause is that the network-side device expects the terminal as an AIoT read-write device. Exemplarily, the first reason value can be Reader (i.e., AIoTServiceAsReader) as an AIoT service.

[0104] Exemplarily, in the case of receiving the paging message, the terminal can respond to the paging message and communicate with the AIoT device as an AIoT read-write device in the connected state; or the terminal can decide whether to respond to the paging message or whether to perform AIoT communication as an AIoT read-write device according to its own situation, for example, the terminal can decide whether to respond to the paging message or whether to perform AIoT communication as an AIoT read-write device according to at least one of the capability information of the terminal, the current state information of the terminal, and the current air interface service performed by the terminal. For example, if the current uplink transmission traffic of the terminal is greater than a first threshold, the terminal decides not to respond to the paging message.

[0105] It should be noted that in the case where the terminal decides not to respond to the paging message, the terminal can also perform AIoT communication as an AIoT read-write device, for example, the terminal can receive an AIoT service request from an AIoT server or the like in the non-connected state and perform AIoT communication with the AIoT device as an AIoT read-write device in the non-connected state; or in the case where the terminal decides not to respond to the paging message, the terminal can not perform AIoT communication.

[0106] In the embodiment, when the terminal is in the non-connected state, the network side device can notify the terminal to perform AIoT communication as an AIoT read-write device through a paging message, so that the terminal in the non-connected state is triggered to perform AIoT communication as an AIoT read-write device, the architecture mode of AIoT communication implementation is expanded, and the efficiency of AIoT communication is improved.

[0107] In another embodiment, the terminal can receive first configuration information from the network side device, the first configuration information being AIoT read-write device related configuration information. For example, the terminal can receive the first configuration information from the network side device when the terminal is in the connected state.

[0108] For example, the first configuration information can include at least one of AIoT read-write device and AIoT device AIoT communication configuration information and AIoT read-write device and network side device AIoT interface message transmission configuration information.

[0109] For example, when the first configuration information is received, the terminal can directly accept the first configuration information, that is, the terminal assumes the function of the AIoT read-write device and performs AIoT communication based on the first configuration information. Alternatively, the terminal can determine whether to accept the first configuration information according to its own situation. For example, the terminal can determine whether to accept the first configuration information according to at least one of terminal capability information, terminal current state information, and terminal current air interface service. For example, if the current uplink transmission traffic of the terminal is greater than a first threshold, the terminal determines not to accept the first configuration information.

[0110] For example, the network side device can determine a candidate terminal as an AIoT read-write device according to at least one of terminal capability, terminal location information, terminal RRC state, AIoT device capability, AIoT device location information, air interface link quality, and AIoT link quality, and send the first configuration information to the candidate terminal.

[0111] In the embodiment, the terminal can receive first configuration information from the network side device, the first configuration information being AIoT read-write device related configuration information. That is, the network side device provides the terminal with related configuration information when the terminal is an AIoT read-write device. Furthermore, the terminal can perform AIoT communication based on the first configuration information when the terminal is an AIoT read-write device, which is beneficial to improve the performance of the terminal performing AIoT communication as an AIoT read-write device.

[0112] In yet another embodiment, the terminal receives a paging message from the network-side device, the paging message carrying a paging cause that the network-side device expects the terminal to be an AIoT read-write device, and receives first configuration information from the network-side device, the first configuration information being AIoT read-write device related configuration information. For example, the terminal can receive the paging message from the network-side device in a non-connected state, and receive the first configuration information from the network-side device in a case of switching from the non-connected state to a connected state, so that the terminal can be an AIoT read-write device and perform AIoT communication based on the first configuration information.

[0113] The paging message and the first configuration information can refer to the related descriptions in the foregoing embodiments, and will not be described herein.

[0114] Specifically, the embodiments do not limit the receiving order of the first configuration information and the paging message. For example, the terminal can receive the first configuration information in a connected state, and then switch from the connected state to a non-connected state and receive the paging message in the non-connected state; or the terminal can receive the paging message in a non-connected state, and then switch from the non-connected state to a connected state and receive the first configuration information in the connected state.

[0115] In the embodiments, the network-side device can notify the terminal to perform AIoT communication as an AIoT read-write device through the paging message when the terminal is in a non-connected state, and provide the terminal with related configuration information (i.e., the first configuration information) when the terminal is in a connected state, so as to not only trigger the terminal in a non-connected state to perform AIoT communication as an AIoT read-write device, but also enable the terminal to perform AIoT communication based on the configuration information obtained in the connected state, which is conducive to improving the performance of AIoT communication.

[0116] Optionally, the first configuration information includes second configuration information, and the second configuration information includes at least one of the following:

[0117] First resource information for indicating a resource for the AIoT read-write device to send a message to the AIoT device;

[0118] Second resource information for indicating a resource for the AIoT device to send a message to the AIoT read-write device;

[0119] Third resource information for indicating a resource for the AIoT read-write device to perform AIoT communication with the AIoT device;

[0120] The first indication information is used to indicate whether the AIoT read-write device needs to send a continuous wave (CW) for exciting the AIoT device to send a message.

[0121] The third configuration information is used to configure the AIoT read-write device and the network-side device to transmit an AIoT interface message.

[0122] Exemplarily, the first resource information can be used to indicate at least one of a time domain resource, a frequency domain resource, a code domain resource, or the like, of the AIoT read-write device sending a message to the AIoT device. The second resource information can be used to indicate at least one of a time domain resource, a frequency domain resource, a code domain resource, or the like, of the AIoT device sending a message to the AIoT read-write device. The third resource information can be used to indicate at least one of a time domain resource, a frequency domain resource, a code domain resource, or the like, of the AIoT read-write device and the AIoT device performing AIoT communication.

[0123] Exemplarily, the AIoT read-write device and the AIoT device performing AIoT communication can include at least one of the AIoT read-write device sending a message to the AIoT device and the AIoT device sending a message to the AIoT read-write device.

[0124] Exemplarily, the third configuration information can be used to configure at least one of a QoS flow, a bearer, and a resource, or the like, of the AIoT read-write device and the network-side device transmitting an AIoT interface message. For example, the third configuration information can include at least one of a latency budget of a QoS flow dedicated for AIoT communication, a priority, or the like; establishment or release configuration of a radio bearer dedicated for AIoT communication, or the like.

[0125] It should be noted that the message sent by the AIoT read-write device to the AIoT device can also be referred to as a reader-to-device (R2D) message. The message sent by the AIoT device to the AIoT read-write device can also be referred to as a device-to-reader (D2R) message.

[0126] Optionally, the first configuration information further includes fourth configuration information, and the fourth configuration information includes at least one of:

[0127] a valid time length of the second configuration information;

[0128] a valid area of the second configuration information.

[0129] In the embodiment, the valid time length of the second configuration information can be used to indicate a time period in which the second configuration information is valid. For example, if the first resource information is valid only in a first time period, the terminal releases the resource indicated by the first resource information when the first time period is exceeded.

[0130] The valid area of the second configuration information is used to indicate an area in which the second configuration information is valid. The valid area can include a cell, a geographic area, and the like. For example, if the network-side device configures the valid area of the first resource information as a first cell, the first resource information is valid when the terminal connects to the first cell. If the terminal reselects to a second cell, the terminal releases the resource indicated by the first resource information, and the terminal cannot continue to serve as an AIoT read-write device.

[0131] In some optional embodiments, the valid time length of each parameter item of the second configuration information can be the same, that is, each parameter item of the second configuration information corresponds to the same valid time length. For example, the first resource information, the second resource information, the third resource information, the first indication information, and the third configuration information all correspond to the same valid time length. Alternatively, each parameter item of the second configuration information can correspond to a different valid time length. For example, the first resource information corresponds to a first valid time length, the second resource information corresponds to a second valid time length, the third resource information corresponds to a third valid time length, the first indication information corresponds to a fourth valid time length, and the third configuration information corresponds to a fifth valid time length.

[0132] In some optional embodiments, the valid area of each parameter item of the second configuration information can be the same, that is, each parameter item of the second configuration information corresponds to the same valid area. For example, the first resource information, the second resource information, the third resource information, the first indication information, and the third configuration information all correspond to the same valid area. Alternatively, each parameter item of the second configuration information can correspond to a different valid area. For example, the first resource information corresponds to a first valid area, the second resource information corresponds to a second valid area, the third resource information corresponds to a third valid area, the first indication information corresponds to a fourth valid area, and the third configuration information corresponds to a fifth valid area.

[0133] The embodiment is advantageous in that at least one of the valid time length and the valid area of the second configuration information is configured, so that the AIoT communication of the non-connected terminal serving as an AIoT read-write device is more accurately and efficiently controlled.

[0134] Optionally, after the first configuration information is received from the network-side device, the method further includes:

[0135] The terminal sends first response information or second response information to the network-side device.

[0136] The first response information is used to indicate that the terminal successfully receives the first configuration information or the terminal is configured to be an AIoT read-write device, and the second response information is used to indicate that the terminal does not expect to be an AIoT read-write device or preference information of the terminal as an AIoT read-write device.

[0137] It can be understood that, in the case that the terminal is in the connected state, the terminal can send the first response information or the second response information to the network side device.

[0138] In the embodiment, in the case that the terminal sends the first response information to the network side device, it indicates that the terminal accepts the first configuration information or is willing to be an AIoT read-write device, and in this case, the terminal can perform AIoT communication with an AIoT device based on the first configuration information; in the case that the terminal sends the second response information to the network side device, it indicates that the terminal does not accept the first configuration information or is unwilling to be an AIoT read-write device, and in this case, the terminal can continue to use the configuration information used before receiving the first configuration information, that is, the terminal does not perform AIoT communication.

[0139] The preference information of the terminal as an AIoT read-write device can include, but is not limited to, at least one of a preferred communication frequency band of an AIoT interface of the terminal in the case of being an AIoT read-write device, a preferred RRC state, a preferred time, a preferred area, and the like. The preferred communication frequency band of the AIoT interface can be understood as that the terminal prefers to be an AIoT read-write device in the frequency band, the preferred RRC state can be understood as that the terminal prefers to be an AIoT read-write device in the RRC state, the preferred time can be understood as that the terminal prefers to be an AIoT read-write device in the time, and the preferred area can be understood as that the terminal prefers to be an AIoT read-write device in the area.

[0140] In the embodiment, the terminal receives the first configuration information from the network side device in the connected state, and sends the first response information or the second response information to the network side device to inform the network side device whether the terminal is configured as an AIoT read-write device, so as to facilitate to ensure consistency of understanding of the terminal and the network side device, and further facilitate to improve AIoT communication performance.

[0141] Optionally, the second response information includes at least one of the following:

[0142] time information used to indicate a time period in which the terminal expects to be an AIoT read-write device;

[0143] a communication frequency band of an AIoT interface preferred by the terminal in the case of being an AIoT read-write device;

[0144] The RRC state preferred by the terminal in the case of being an AIoT read-write device.

[0145] The RRC state can include, but is not limited to, at least one of a connected state, a deactivated state, and an idle state.

[0146] The communication frequency band of the AIoT interface can be understood as a communication frequency band used by the AIoT interface. For example, the communication frequency band of the AIoT interface can include at least one of a frequency band in which the AIoT interface transmits an R2D message and a frequency band in which the AIoT interface receives a D2R message.

[0147] In this embodiment, in the case that the terminal does not accept the first configuration information or does not want to become an AIoT read-write device, the terminal reports at least one of a time period, a communication frequency band, and an RRC state preferred by the terminal as an AIoT read-write device to the network side device, so that the network side device can more accurately configure the terminal as an AIoT read-write device based on the above preference information.

[0148] Optionally, the first configuration information is carried in an RRC reconfiguration (RRCReconfiguration) message or a system message; or the first response information is carried in an RRC reconfiguration complete (RRCReconfigurationComplete) message.

[0149] Alternatively, the second response information is carried in a user equipment assistance information (UE Assistance Information, UAI) message.

[0150] For example, the network side device sends an RRCReconfiguration message to the terminal, the RRCReconfiguration message carries the first configuration information, the terminal can send an RRCReconfigurationComplete message to the network side device in the case that the terminal accepts the first configuration information or wants to become an AIoT read-write device, the message carries the first response information, or the terminal can send a UAI message to the network side device in the case that the terminal does not accept the first configuration information or does not want to become an AIoT read-write device, the UAI message carries the second response information.

[0151] This embodiment multiplexes the existing messages for AIoT communication configuration, which is conducive to reducing the complexity of AIoT communication configuration.

[0152] Optionally, after receiving the first configuration information from the network side device, the method further includes:

[0153] The terminal performs AIoT communication with the AIoT device in the case of entering the deactivated state.

[0154] The terminal entering the deactivated state can be understood as the terminal being converted from the connected state to the deactivated state.

[0155] In this embodiment, the terminal can receive the first configuration information from the network side device in the connected state, and be converted from the connected state to the deactivated state, and perform AIoT communication with the AIoT device in the deactivated state, for example, perform AIoT communication with the AIoT device based on the first configuration information, that is, when the terminal acts as an AIoT device, only communicate with the AIoT device at the AIoT interface, and interrupt the communication of the Uu interface, which is beneficial to improve the performance of AIoT communication.

[0156] In some optional embodiments, the terminal can be released from the connected state to the deactivated state by the network in the case of receiving the AIoT service request and the first configuration information from the network side device, and perform AIoT communication with the AIoT device in the deactivated state, for example, can perform AIoT communication with the AIoT device based on the first configuration information in the deactivated state. Wherein, the AIoT service request is used to request the terminal to perform AIoT service. The AIoT service request and the first configuration information can be sent through the same message, or can be sent through different messages. In addition, this embodiment does not limit the sending order of the AIoT service request and the first configuration information, for example, the AIoT service request and the first configuration information can be sent at the same time, or the AIoT service request can be sent first, and the first configuration information can be sent later.

[0157] Optionally, the receiving the first configuration information from the network side device comprises:

[0158] receiving a first RRC release message from the network side device node, the first RRC release message carrying the first configuration information, and the first RRC release message being an RRC release message carrying suspend configuration (SuspendConfig).

[0159] In this embodiment, the terminal receives the RRC release (RRCRelease with suspend Config) message carrying SuspendConfig from the network side device, and the RRCRelease with suspend Config message carries the first configuration information, so that the terminal can not only enter the deactivated state based on the RRCRelease with suspend Config message, but also perform AIoT communication based on the first configuration information carried by the RRCRelease with suspend Config message, which not only saves signaling overhead, but also improves the efficiency of configuring the terminal to perform AIoT communication as an AIoT read-write device.

[0160] Optionally, after receiving the paging message from the network side device, the method further comprises:

[0161] The terminal determines whether to respond to the paging message according to the first information;

[0162] The first information comprises at least one of the following:

[0163] The capability information of the terminal, wherein the capability information is related to the capability of the terminal as an AIoT read-write device;

[0164] Whether the terminal is authenticated as an AIoT read-write device;

[0165] Whether the first frequency band and the second frequency band match, wherein the first frequency band is an AIoT communication frequency band broadcast by a serving cell of the terminal, and the second frequency band is an AIoT communication frequency band supported by the terminal as an AIoT read-write device;

[0166] Whether the terminal has valid target configuration information, wherein the target configuration information is used for AIoT communication of the terminal as an AIoT read-write device;

[0167] The power of the terminal;

[0168] The air interface service condition of the terminal.

[0169] The capability information of the terminal can comprise at least one of the following: an indication of whether the terminal has the capability of being an AIoT read-write device, a polling frequency supported by the terminal as an AIoT read-write device, a polling area supported by the terminal as an AIoT read-write device, and a polling time before the terminal as an AIoT read-write device.

[0170] For whether the terminal is authenticated as an AIoT read-write device, for example, if the terminal registers the capability of the terminal as an AIoT read-write device to the network side device, it indicates that the terminal is authenticated as an AIoT read-write device, and if the terminal does not register the capability of the terminal as an AIoT read-write device to the network side device, it indicates that the terminal is not authenticated as an AIoT read-write device.

[0171] For whether the first frequency band and the second frequency band match, for example, if there is an overlapping frequency band part in the first frequency band and the second frequency band, it is determined that the first frequency band and the second frequency band match, otherwise it is determined that the first frequency band and the second frequency band do not match.

[0172] For the power of the terminal, for example, the terminal can determine whether the power is sufficient for performing AIoT communication based on the power, and if the power is not sufficient, the terminal can determine not to respond to the paging message.

[0173] The air interface service condition of the terminal can include whether the terminal has air interface service to perform within a preset time.

[0174] For example, whether the terminal responds to the paging message can indicate whether the terminal expects to be an AIoT read-write device. For example, if the terminal does not respond to the paging message, it can indicate that the terminal does not expect to be an AIoT read-write device, and if the terminal responds to the paging message, it can indicate that the terminal expects to be an AIoT read-write device.

[0175] For example, the terminal can determine not to respond to the paging message when the first condition is met, and / or determine to respond to the paging message when the second condition is met.

[0176] The first condition can include any of the following:

[0177] The terminal does not have the capability to be an AIoT read-write device;

[0178] The terminal is not authenticated as an AIoT read-write device;

[0179] The first frequency band does not match the second frequency band;

[0180] The terminal does not have valid target configuration information;

[0181] The terminal does not have enough power to perform AIoT communication;

[0182] The terminal has air interface service to perform within a preset time.

[0183] The second condition can include at least one of the following:

[0184] The terminal has the capability to be an AIoT read-write device;

[0185] The terminal is authenticated as an AIoT read-write device;

[0186] The first frequency band matches the second frequency band;

[0187] The terminal has valid target configuration information;

[0188] The terminal has enough power to perform AIoT communication;

[0189] The terminal does not have air interface service to perform within a preset time.

[0190] In this embodiment, the terminal can determine whether to respond to the paging message according to the first information, which not only improves the flexibility of the terminal in deciding whether to be an AIoT read-write device, but also ensures the quality of AIoT communication.

[0191] Optionally, the method further comprises:

[0192] The terminal sends a first RRC establishment request (i.e., RRCSetupRequest) message or a first RRC resume request (i.e., RRCResumeRequest) message to the network side device.

[0193] The first RRC establishment request message carries a second cause value, and the second cause value is used to indicate that the terminal initiates connection establishment because the terminal expects to become an AIoT read-write device. The first RRC resume request message carries a third cause value, and the third cause value is used to indicate that the terminal initiates connection resumption because the terminal expects to become an AIoT read-write device.

[0194] It can be understood that in the case where the terminal responds to the paging message, the terminal can send a first RRC establishment request message or a first RRC resume request message to the network side device.

[0195] The present embodiment is exemplified as follows in different cases:

[0196] Case 1: If the terminal receives the above paging message in an idle state, the terminal can send a first RRC establishment request message to the network side device, and the first RRC establishment request message carries a second cause value, which is used to indicate that the terminal initiates connection establishment because the terminal expects to become an AIoT read-write device. In this way, the network side device can know that the terminal initiates connection establishment because the terminal expects to become an AIoT read-write device, which is conducive to quickly establishing a connection for the terminal, for example, the network side device can send an RRC establishment (i.e., RRCSetup) message to the terminal.

[0197] Exemplarily, the RRC layer of the terminal can set the establishmentCause to the second cause value, which is used to indicate that the terminal initiates connection establishment because the terminal expects to become an AIoT read-write device.

[0198] In case two, if the terminal receives the paging message in the deactivated state, the terminal can send a first RRC setup request message to the network side device, the first RRC setup request message carrying a second cause value, the second cause value indicating that the reason (i.e. establishmentCause) for the terminal to initiate connection establishment is that the terminal expects to become an AIoT read-write device, so that the network side device can know that the reason for the terminal to initiate connection establishment is that the terminal expects to become an AIoT read-write device, thereby facilitating the establishment of a connection for the terminal, for example, the network side device can send an RRC setup (i.e. RRCSetup) message to the terminal, or the terminal can send a first RRC resume request message to the network side device, the first RRC resume request message carrying a third cause value, the third cause value indicating that the reason (i.e. resumeCause) for the terminal to initiate connection recovery is that the terminal expects to become an AIoT read-write device, so that the network side device can know that the reason for the terminal to initiate connection recovery is that the terminal expects to become an AIoT read-write device, thereby facilitating the recovery of a connection for the terminal, for example, the network side device can send an RRC resume (i.e. RRCResume) message to the terminal.

[0199] Exemplarily, if the identification information of the terminal is the terminal identification indicated by the NAS layer, i.e. the paging message is a paging message sent by the core network (CN), in this case, the RRC layer of the terminal submits the second cause value to the NAS layer and sets the release cause to other; the NAS layer determines to initiate RRC connection establishment; the RRC layer of the terminal sets the establishmentCause to the second cause value, indicating that the reason for the terminal to initiate connection establishment is to expect to become a UE reader.

[0200] If the identification information of the terminal is the full Inactive-Radio Network Temporary Identity (fullI-RNTI) stored by the terminal, i.e. the paging message is a paging message sent by the RAN, in this case, the terminal is configured with a first access identifier, the first access identifier directly corresponding to the third cause value, wherein the mapping relationship between the first access identifier and the third cause value can be protocol predefined; the RRC layer of the terminal initiates RRC connection recovery and sets the resumeCause to the third cause value, indicating that the reason for the terminal to initiate connection recovery is to expect to become an AIoT read-write device.

[0201] It can be understood that in this embodiment, the non-connected state terminal performs AIoT communication with the AIoT device in the case of entering the RRC connected state, and can further receive an AIoT service request from the network side device and send an AIoT service response to the network side device through the RRC connection.

[0202] Optionally, the receiving of the first configuration information from the network side device comprises:

[0203] receiving a first RRC setup (i.e. RRCSetup) message or a first RRC resume (i.e. RRCResume) message from the network side device;

[0204] The first RRC setup message or the first RRC resume message carries the first configuration information.

[0205] In this embodiment, the first configuration information is carried by the first RRC setup message or the first RRC resume message, which not only saves signaling overhead, but also improves the efficiency of the terminal configured as an AIoT read-write device for AIoT communication.

[0206] Optionally, the method further comprises:

[0207] The terminal sends a second RRC setup request message or a second RRC resume request message to the network side device;

[0208] The second RRC setup request message or the second RRC resume request message carries second indication information, and the second indication information is used to indicate that the terminal does not expect to become an AIoT read-write device or preference information of the terminal as an AIoT read-write device.

[0209] In this embodiment, the terminal can send a second RRC setup request message or a second RRC resume request message to the network side device in the case of not expecting to become an AIoT read-write device, to inform the network side device that the terminal does not expect to become an AIoT read-write device or preference information of the terminal as an AIoT read-write device, which can avoid the network side device continuously paging the terminal and is beneficial to save resources. In addition, the network side device can also subsequently more accurately configure the terminal as an AIoT read-write device based on the above-mentioned preference information.

[0210] In some optional embodiments, in the case that the second RRC setup request message or the second RRC resume request message carries the preference information of the terminal as an AIoT read-write device, the terminal can subsequently page the terminal based on the above-mentioned preference information, and then the terminal can enter the connected state and receive the first configuration information, and as an AIoT read-write device, perform AIoT communication based on the above-mentioned first configuration information.

[0211] In some optional embodiments, the terminal can carry the second indication information in other messages, for example, the terminal can transmit the second indication information in a UAI message.

[0212] In some optional embodiments, the terminal can transmit the second indication information in a small data transmission (SDT) manner. For example, the terminal in the inactive state can transmit the second indication information in the SDT manner.

[0213] Optionally, the second indication information includes at least one of the following:

[0214] time information, used to indicate a time period during which the terminal expects to be an AIoT read-write device;

[0215] a communication frequency band of a preferred AIoT interface of the terminal in the case of being an AIoT read-write device;

[0216] a preferred RRC state of the terminal in the case of being an AIoT read-write device.

[0217] In the embodiment, the communication frequency band of the preferred AIoT interface and the preferred RRC state can be referred to the related description of the foregoing embodiments, which will not be described here.

[0218] Optionally, the second RRC setup request message or the second RRC resume request message is carried in MSG1 or MSGA of a random access procedure.

[0219] Optionally, the method further includes:

[0220] The terminal receives an RRC reject message or a second RRC release message or a third RRC release message from the network side device, and the third RRC release message is a release message carrying SuspendConfig.

[0221] For example, in the case that the terminal is in the idle state, the terminal can receive an RRC reject message from the network side device, in which case the terminal can remain in the idle state; in the case that the terminal is in the inactive state, the terminal can receive an RRC reject message or a second RRC release message or a third RRC release message from the network side device, wherein in the case of receiving the RRC reject message or the third RRC release message, the terminal can remain in the inactive state, and in the case of receiving the second RRC release message, the terminal can release resources and enter the idle state.

[0222] In the embodiment, in a case where the second indication information indicates that the terminal does not expect to become an AIoT read-write device or the terminal does not prefer to become an AIoT read-write device, the network-side device can send an RRC reject message, an RRC release message or a third RRC release message to the terminal, so that system resources can be saved, and the terminal can maintain the original RRC state.

[0223] Optionally, after receiving the paging message from the network-side device, the method further includes:

[0224] The terminal performs AIoT communication with the AIoT device in the non-connected state.

[0225] In the embodiment, the terminal can perform AIoT communication with the AIoT device in the non-connected state without responding to the paging message, so that the efficiency of IoT communication can be improved, and system resources can be saved.

[0226] It should be noted that in a case where the terminal does not respond to the paging message, the terminal can receive an AIoT service request from an AIoT server or a core network element, and perform AIoT communication with the AIoT device in the non-connected state.

[0227] In addition, in a case where the terminal also receives first configuration information from the network-side device, the terminal can receive the first configuration information from the network-side device before switching to the non-connected state, for example, the first configuration information can be carried in an RRC release message or an RRC release message carrying suspension configuration.

[0228] In some optional embodiments, in a case where the terminal completes the AIoT communication with the AIoT device, the terminal can send an RRC setup request message or an RRC resume request message to the network-side device, and in a case where the terminal enters the connected state, the terminal can send an AIoT service response to the network-side device; or the terminal can carry the AIoT service response in the RRC setup request message or the RRC resume request message, in which case the terminal does not need to send the AIoT service response to the network-side device in a case where the terminal enters the connected state.

[0229] Optionally, the method further includes:

[0230] In a case where the terminal completes the AIoT communication with the AIoT device, the terminal sends a third RRC resume request message to the network-side device.

[0231] In the embodiment, in a case where the terminal completes the AIoT communication with the AIoT device in the deactivated state, the terminal can send a third RRC resume request message to the network-side device, so that the air interface communication of the terminal can be quickly recovered.

[0232] Optionally, the third RRC resume request message comprises an AIoT service response, the AIoT service response being used for responding to the AIoT service request sent by the network side device.

[0233] Illustratively, the terminal can carry the AIoT service response in the third RRC resume request message in the manner of SDT.

[0234] In this embodiment, the terminal sends the AIoT service response to the network side device through the third RRC resume request message, which is conducive to saving signaling overhead.

[0235] Optionally, the method further comprises:

[0236] The terminal receives a second RRC resume message from the network side device;

[0237] In the case of resuming to the connected state, the terminal sends an AIoT service response to the network side device, the AIoT service response being used for responding to the AIoT service request sent by the network side device.

[0238] In this embodiment, the terminal sends the AIoT service response to the network side device in the case of resuming to the connected state, which is conducive to ensuring the reliability of AIoT service response transmission.

[0239] Please refer to FIG. 6, which is a flow chart of an environment Internet of Things configuration method provided by the embodiment of the present application, the method can be executed by a network side device, as shown in FIG. 6, comprising the following steps:

[0240] Step 601, the network side device executes a second operation, the second operation comprising at least one of the following:

[0241] Sending a paging message to the terminal, the paging message carrying a first cause value, the first cause value being used to indicate that the paging reason is that the network side device expects the terminal as an AIoT read-write device;

[0242] Sending first configuration information to the terminal, the first configuration information being environment Internet of Things AIoT read-write device related configuration information.

[0243] Optionally, the first configuration information comprises second configuration information, the second configuration information comprising at least one of the following:

[0244] First resource information, used to indicate the resource of the AIoT read-write device sending a message to the AIoT device;

[0245] Second resource information, used to indicate the resource of the AIoT device sending a message to the AIoT read-write device;

[0246] third resource information, used for indicating a resource for AIoT communication between the AIoT read-write device and the AIoT device;

[0247] first indication information, used for indicating whether the AIoT read-write device needs to send an excitation source carrier CW;

[0248] third configuration information, used for configuring the AIoT read-write device to transmit an AIoT interface message over the air.

[0249] Optionally, the first configuration information further includes fourth configuration information, and the fourth configuration information includes at least one of the following:

[0250] a valid time length of the second configuration information;

[0251] a valid area of the second configuration information.

[0252] Optionally, the method further includes:

[0253] receiving, by the network-side device, first response information or second response information from the terminal;

[0254] wherein the first response information is used for indicating that the terminal successfully receives the first configuration information or the terminal is configured to be an AIoT read-write device, and the second response information is used for indicating that the terminal does not expect to be an AIoT read-write device or preference information of the terminal as an AIoT read-write device.

[0255] Optionally, the second response information includes at least one of the following:

[0256] time information, used for indicating a time period during which the terminal expects to be an AIoT read-write device;

[0257] a communication frequency band of an AIoT interface preferred by the terminal in the case of being an AIoT read-write device;

[0258] an RRC state preferred by the terminal in the case of being an AIoT read-write device.

[0259] Optionally, the first configuration information is carried in a radio resource control (RRC) reconfiguration message or a system message.

[0260] or

[0261] the first response information is carried in an RRC reconfiguration complete message.

[0262] or

[0263] the second response information is carried in a user equipment assistance information (UAI) message.

[0264] Optionally, the sending the first configuration information to the terminal comprises:

[0265] sending a first RRC release message to the terminal, the first RRC release message comprising the first configuration information, the first RRC release message being an RRC release message carrying SuspendConfig.

[0266] Optionally, the method further comprises:

[0267] receiving, by the network-side device, a first RRC setup request message or a first RRC resume request message from the terminal;

[0268] wherein the first RRC setup request message carries a second cause value, the second cause value being used to indicate that the terminal initiates connection establishment because the terminal expects to become an AIoT read-write device, and the first RRC resume request message carries a third cause value, the third cause value being used to indicate that the terminal initiates connection resumption because the terminal expects to become an AIoT read-write device.

[0269] Optionally, the sending the first configuration information to the terminal comprises:

[0270] sending a first RRC setup message or a first RRC resume message to the terminal;

[0271] wherein the first RRC setup message or the first RRC resume message comprises the first configuration information.

[0272] Optionally, the method further comprises:

[0273] receiving, by the network-side device, a second RRC setup request message or a second RRC resume request message from the terminal;

[0274] wherein the second RRC setup request message or the second RRC resume request message carries second indication information, the second indication information being used to indicate that the terminal does not expect to become an AIoT read-write device or preference information of the terminal as an AIoT read-write device.

[0275] Optionally, the second indication information comprises at least one of the following:

[0276] time information used to indicate a time period during which the terminal expects to become an AIoT read-write device;

[0277] a communication frequency band of an AIoT interface preferred by the terminal in the case of the terminal as an AIoT read-write device;

[0278] an RRC state preferred by the terminal in the case of the terminal as an AIoT read-write device.

[0279] Optionally, the second RRC setup request message or the second RRC resume request message is carried by MSG1 or MSGA of a random access procedure.

[0280] Optionally, the method further comprises:

[0281] The network-side device sends an RRC reject message or a second RRC release message or a third RRC release message to the terminal, the third RRC release message being a release message carrying SuspendConfig.

[0282] Optionally, the method further comprises:

[0283] The network-side device receives a third RRC resume request message from the terminal.

[0284] Optionally, the third RRC resume request message comprises an AIoT service response, the AIoT service response being used to respond to an AIoT service request sent by the network-side device.

[0285] Optionally, the method further comprises:

[0286] The network-side device sends a second RRC resume message to the terminal.

[0287] The network-side device receives an AIoT service response from the terminal, the AIoT service response being used to respond to an AIoT service request sent by the network-side device.

[0288] It should be noted that the implementation manner of this embodiment can refer to the related description of the embodiment shown in FIG. 5, which will not be repeated here.

[0289] The embodiments of the present application are exemplified below in combination with examples:

[0290] Example 1: The main idea of this example is that the RAN node provides the RRC_CONNECTED UE with a configuration related to AIoT reader. The UE receives and uses the configuration according to its current situation, or still maintains the previous configuration, and informs the base station of its preference information for becoming an AIoT reader.

[0291] Referring to FIG. 7, the environment Internet of Things configuration method provided in this embodiment comprises the following steps:

[0292] Step 10. The RAN node determines a candidate UE as an AIoT reader according to the capability of the UE, the capability of the AIoT device, the location information of the UE, the RRC state of the UE, and the like.

[0293] Step 11. The RAN node sends an RRCReconfiguration message to the RRC_CONNECTED UE, where the first configuration information is carried. Wherein the first configuration information can refer to the related description of the foregoing embodiments, which will not be repeated here.

[0294] Step 12. The UE checks its own situation and determines whether to respond to the network configuration (i.e. the first configuration information described above), for example, the terminal can determine whether to respond to the network configuration according to the link quality of the air interface, the link quality of the AIoT interface, the power of the terminal, whether it has the willingness or ability to become an AIoT reader, etc.

[0295] Step 13a. The UE receives the network configuration and sends an RRCReconfigurationComplete message to the RAN node.

[0296] Step 13b. The UE continues to use the configuration before receiving the RRCReconfiguration message in the case of determining that it cannot implement the received first configuration information.

[0297] Step 14. The UE sends a UAI message to the RAN node, where the second response information is carried, which is used to indicate that the UE does not expect to become an AIoT reader. Wherein the second response information described above can refer to the related description of the foregoing embodiments, which will not be repeated here.

[0298] It should be noted that the above step 14 can be an optional step.

[0299] Example two: The main idea of this example is that the RAN provides the RRC_CONNECTED UE with configuration related to AIoT reader, and releases the UE to RRC_INACTIVE, so that the UE only focuses on the communication of the AIoT interface when it becomes an AIoT reader, and interrupts the communication of the Uu interface; when the UE completes the communication of the AIoT interface, it can initiate a connection recovery process to transmit the communication content of the AIoT interface and restore the Uu connection.

[0300] Referring to FIG. 8, the environment Internet of Things configuration method provided by the embodiment includes the following steps:

[0301] Step 20. The RRC_CONNECTED UE receives the AIoT service request sent by the RAN node.

[0302] Step 21. The RAN node sends an RRCRelease with suspend Config message to the RRC_CONNECTED UE, where the first configuration information is carried. Wherein the first configuration information can refer to the related description of the foregoing embodiments, which will not be repeated here.

[0303] It can be understood that the RRC_CONNECTED UE can enter RRC_INACTIVE in the case of receiving the RRCRelease with suspend Config message.

[0304] Step 22. Based on the first configuration information and the AIoT service request, the UE and the AIoT device communicate on the AIoT interface.

[0305] Step 23. The RRC_INACTIVE UE sends an RRCResumeRequest message to the RAN node.

[0306] Optionally, the UE can carry the AIoT service response in the RRCResumeRequest message by means of SDT, for responding to the AIoT service request.

[0307] Step 24. The RAN node sends an RRCResume message to the RRC_INACTIVE UE to resume the RRC connection.

[0308] Step 25. The UE enters RRC_CONNECTED and sends an RRCResumeComplete message to the RAN node.

[0309] Step 26. The UE sends the AIoT service response for responding to the AIoT service request.

[0310] It can be understood that in the case of transmitting the AIoT service response by means of SDT in step 23, this step 26 can not be performed.

[0311] Example Three: The main idea of this example is:

[0312] 1) The RAN / CN triggers the UE in RRC_INACTIVE / IDLE to enter RRC_CONNECTED by paging, and carries the paging cause value paging cause as AIoTServiceAsReader in the paging message, so as to realize that the non-connected state UE can be paged and enter the connected state as an AIoT reader; from the perspective of the UE, it knows that the reason for being paged is to assist the network to complete the AIoT service, and the UE can selectively enter the connected state and determine whether to assume the function of the AIoT reader according to the current situation.

[0313] 2) The UE decides whether to enter the connected state in response to the paging according to its current situation, for example, informs the RAN node of its maintained original RRC state and reason to avoid continuous paging by the network; or responds to the paging and sets a corresponding connection recovery / establishment reason value.

[0314] Referring to FIG. 9, the environment IoT configuration method provided by the embodiment includes the following steps:

[0315] Step 30. The RAN node determines a candidate UE as an AIoT reader according to the information of the UE in the coverage and the capability of the AIoT device, wherein the information of the UE can include the capability of the UE (i.e., whether the UE has the AIoT reader function or the UE is authenticated to be used for assisting AIoT communication), the location information of the UE, the RRC state of the UE, etc. The location information of the UE can be used to determine whether the AIoT device (e.g., the AIoT device that needs to be inventoried) is located in the moving area of the UE. If the candidate UE is in RRC_INACTIVE / IDLE, the following steps are performed.

[0316] Step 31. The RAN node sends a paging message to the candidate UE, wherein the paging message carries a first reason value, which can be one-to-one corresponding to the UE to be paged, indicating that the purpose of the network paging the UE is to expect the UE as an AIoT reader of the AIoT service. Specifically, the granularity of the AIoT service can be service level, such as AIoT reader for inventory or AIoT reader for command.

[0317] Step 32. Based on the first reason value, the UE can determine whether to respond to the network paging or perform AIoT communication according to the first information. Wherein the first information can refer to the related description of the foregoing embodiment, which is not repeated here.

[0318] I. In the case that the UE decides to respond to the paging, enter the connected state and perform AIoT communication as an AIoT reader, steps 33b to 34b can be performed:

[0319] Step 33b. The UE sends an RRCResumeRequest or RRCSetupRequest message to the RAN node, wherein the RRCSetupRequest message carries a second reason value and the RRCResumeRequest message carries a third reason value.

[0320] Specifically, for the two cases of RRC_IDLE UE and RRC_INACTIVE UE, please refer to the related description of the foregoing embodiment, which is not repeated here.

[0321] Step 34b. The RAN node sends an RRCResume or RRCSetup message to the UE, which carries the first configuration information. The first configuration information can refer to the related description of the foregoing embodiments, which will not be described here.

[0322] II. In the case where the UE decides not to respond to the paging and maintain the original state, steps 33a and 34a can be performed:

[0323] Step 33a. The UE sends an RRCResumeRequest or RRCSetupRequest message to the RAN node, which carries the second indication information indicating that the UE does not expect to become an AIoT reader.

[0324] The second indication information can refer to the related description of the foregoing embodiments, which will not be described here.

[0325] Step 34a. The RAN node sends an RRCResume with Suspend config or RRCReject message to the UE, which does not carry any information element.

[0326] It should be noted that the above steps 33a and 34a can be optional steps.

[0327] III. In the case where the UE decides to respond to the paging but does not enter the connected state and maintain the original state to perform AIoT communication, the UE uses the valid target configuration information in RRC_INACTIVE to perform AIoT communication. After obtaining the AIoT service response, the UE sends an RRCResumeRequest message to the RAN node.

[0328] Optionally, the UE can carry the AIoT service response in the RRCResumeRequest message in the form of SDT to respond to the AIoT service request of the network, or send the AIoT service response to the RAN node after completing the connection recovery process.

[0329] Through the embodiments of the present application, the network can control the candidate UE as the AIoT reader to enter the connected state, directly accept the configuration and transmission of the AIoT service from the network side, and ensure the communication of the AIoT interface; or control the candidate UE as the AIoT reader to enter the deactivated state, only maintain the communication of the AIoT interface, give a certain scheduling flexibility of the AIoT interface as the AIoT reader, or the network triggers the UE as the AIoT reader to perform the AIoT communication through paging, or the UE initiates random access to request configuration to perform the AIoT communication. Through the embodiments of the present application, the communication efficiency of the AIoT interface can be improved in the case that the network is busy in scheduling the AIoT interface as the AIoT reader, that is, the network can flexibly decentralize the function of the AIoT reader to a UE with the AIoT reader capability in its service range. In addition, the UE can decide whether to become the AIoT reader to assist the network to complete the AIoT service according to its own situation.

[0330] It should be noted that the execution subject of the environment Internet of Things configuration method provided in the embodiments of the present application can be an environment Internet of Things configuration device. In the embodiments of the present application, the environment Internet of Things configuration device is taken as an example to execute the environment Internet of Things configuration method, and the environment Internet of Things configuration device provided in the embodiments of the present application is described.

[0331] The embodiments of the present application provide an environment Internet of Things configuration device. As an example, the environment Internet of Things configuration device can be a communication device or a component in the communication device, such as a chip. The communication device can be a terminal, a network side device, a server, or the like. For example, the terminal can include but is not limited to the types of the terminal 11 listed above, the network side device can include but is not limited to the types of the network side device 12 listed above, and the embodiments of the present application are not limited specifically.

[0332] The environmental Internet of Things configuration apparatus includes a receiving module, a sending module and a processing module. The receiving module, the sending module and the processing module can be implemented by software or by hardware. When implemented by hardware, the processing module can be implemented by a processor, which can include a general-purpose processor, a special-purpose processor, a central processing unit (CPU), a microprocessor, a digital signal processor (DSP), an artificial intelligent (AI) processor, a graphics processing unit (GPU), an application specific integrated circuit (ASIC), a network processor (NP), a field programmable gate array (FPGA) or other programmable logic devices, a gate circuit, a transistor, a discrete hardware component, etc. The receiving module and the sending module can be implemented by a communication interface, which can include a transceiver, a pin, a circuit, a bus, a radio frequency unit, etc.

[0333] Specifically, referring to FIG. 10, when the environmental Internet of Things configuration apparatus is a terminal or a component in a terminal, the environmental Internet of Things configuration apparatus 1000 includes a processing module 1001 configured to perform a first operation, and the first operation includes at least one of the following:

[0334] receiving a paging message from a network-side device, the paging message carrying a first cause value, the first cause value being used to indicate that a paging cause is that the network-side device expects the terminal to be an AIoT read-write device;

[0335] receiving first configuration information from the network-side device, the first configuration information being environmental Internet of Things (AIoT) read-write device related configuration information.

[0336] Optionally, the first configuration information includes second configuration information, and the second configuration information includes at least one of the following:

[0337] first resource information used to indicate a resource for the AIoT read-write device to send a message to an AIoT device;

[0338] second resource information used to indicate a resource for the AIoT device to send a message to the AIoT read-write device;

[0339] third resource information used to indicate a resource for the AIoT read-write device to perform AIoT communication with the AIoT device;

[0340] The first indication information is used to indicate whether the AIoT read-write device needs to send a carrier wave (CW) of an excitation source, and the CW is used to excite the AIoT device to send a message.

[0341] The third configuration information is used to configure the AIoT read-write device and the network side device to transmit an AIoT interface message.

[0342] Optionally, the first configuration information further includes fourth configuration information, and the fourth configuration information includes at least one of the following:

[0343] The effective time length of the second configuration information;

[0344] The effective area of the second configuration information.

[0345] Optionally, the apparatus further includes:

[0346] The sending module is configured to send first response information or second response information to the network side device;

[0347] The first response information is used to indicate that the terminal successfully receives the first configuration information or the terminal is configured to be an AIoT read-write device, and the second response information is used to indicate that the terminal does not expect to be an AIoT read-write device or preference information of the terminal as an AIoT read-write device.

[0348] Optionally, the second response information includes at least one of the following:

[0349] Time information is used to indicate a time period in which the terminal expects to be an AIoT read-write device;

[0350] The communication frequency band of the AIoT interface preferred by the terminal as an AIoT read-write device;

[0351] The RRC state preferred by the terminal as an AIoT read-write device.

[0352] Optionally, the first configuration information is carried in a radio resource control (RRC) reconfiguration message or a system message.

[0353] Or,

[0354] The first response information is carried in an RRC reconfiguration completion message.

[0355] Or,

[0356] The second response information is carried in a user equipment assistance information (UAI) message.

[0357] Optionally, the processing module 1001 is further configured to perform AIoT communication with an AIoT device in a deactivated state.

[0358] Optionally, the receiving the first configuration information from the network side device comprises:

[0359] receiving a first RRC release message from a network side device node, the first RRC release message carrying the first configuration information, the first RRC release message being an RRC release message carrying suspend configuration SuspendConfig.

[0360] Optionally, the processing module 1001 is further configured to determine, according to the first information, whether to respond to the paging message.

[0361] The first information comprises at least one of the following:

[0362] capability information of the terminal, the capability information being capability information related to the terminal as an AIoT read-write device;

[0363] whether the terminal is authenticated as an AIoT read-write device;

[0364] whether a first frequency band and a second frequency band match, the first frequency band being an AIoT communication frequency band broadcast by a serving cell of the terminal, and the second frequency band being an AIoT communication frequency band supported by the terminal as an AIoT read-write device;

[0365] whether the terminal has valid target configuration information, the target configuration information being used for AIoT communication of the terminal as an AIoT read-write device;

[0366] a power level of the terminal;

[0367] an air interface service condition of the terminal.

[0368] Optionally, the apparatus further comprises:

[0369] a sending module configured to send a first RRC setup request message or a first RRC resume request message to the network side device;

[0370] The first RRC setup request message carries a second reason value, and the second reason value is used to indicate that the terminal initiates connection setup because the terminal expects to become an AIoT read-write device. The first RRC resume request message carries a third reason value, and the third reason value is used to indicate that the terminal initiates connection resume because the terminal expects to become an AIoT read-write device.

[0371] Optionally, the receiving the first configuration information from the network side device comprises:

[0372] receiving a first RRC setup message or a first RRC resume message from the network side device;

[0373] The first RRC setup message or the first RRC resume message carries the first configuration information.

[0374] Optionally, the apparatus further includes:

[0375] The sending module is configured to send a second RRC setup request message or a second RRC resume request message to the network-side device.

[0376] The second RRC setup request message or the second RRC resume request message carries second indication information, and the second indication information is used to indicate that the terminal does not expect to be an AIoT read-write device or preference information of the terminal as an AIoT read-write device.

[0377] Optionally, the second indication information includes at least one of the following:

[0378] Time information used to indicate a time period during which the terminal expects to be an AIoT read-write device;

[0379] A communication frequency band of an AIoT interface preferred by the terminal in the case of being an AIoT read-write device;

[0380] An RRC state preferred by the terminal in the case of being an AIoT read-write device.

[0381] Optionally, the second RRC setup request message or the second RRC resume request message is carried by MSG1 or MSGA of a random access procedure.

[0382] Optionally, the apparatus further includes:

[0383] The receiving module is configured to receive, from the network-side device, an RRC reject message or a second RRC release message or a third RRC release message, and the third RRC release message is a release message carrying SuspendConfig.

[0384] Optionally, the processing module is further configured to perform AIoT communication with an AIoT device in a non-connected state.

[0385] Optionally, the apparatus further includes:

[0386] The sending module is configured to send, to the network-side device, a third RRC resume request message in the case that the terminal completes AIoT communication with the AIoT device.

[0387] Optionally, the third RRC resume request message includes an AIoT service response, and the AIoT service response is used to respond to an AIoT service request sent by the network-side device.

[0388] Optionally, the apparatus further comprises:

[0389] a receiving module, configured to receive a second RRC resume message from the network side device;

[0390] The sending module is further configured to send an AIoT service response to the network side device in the case of resuming to the connected state, the AIoT service response being used to respond to the AIoT service request sent by the network side device.

[0391] The environment Internet of Things configuration apparatus provided by the embodiments of the present application can realize each process realized by the method embodiment of FIG. 5 and achieve the same technical effects. To avoid repetition, details are not described herein.

[0392] Referring to FIG. 11, when the environment Internet of Things configuration apparatus is a network side device or a component in a network side device, the environment Internet of Things configuration apparatus 1100 comprises a processing module 1101 configured to perform a second operation, the second operation comprising at least one of the following:

[0393] sending a paging message to a terminal, the paging message carrying a first cause value, the first cause value being used to indicate that a paging cause is that the network side device expects the terminal as an AIoT read-write device;

[0394] sending first configuration information to a terminal, the first configuration information being environment Internet of Things AIoT read-write device related configuration information.

[0395] Optionally, the first configuration information comprises second configuration information, and the second configuration information comprises at least one of the following:

[0396] first resource information, used to indicate a resource of sending a message by an AIoT read-write device to an AIoT device;

[0397] second resource information, used to indicate a resource of sending a message by an AIoT device to an AIoT read-write device;

[0398] third resource information, used to indicate a resource of AIoT communication between an AIoT read-write device and an AIoT device;

[0399] first indication information, used to indicate whether an AIoT read-write device needs to send a stimulus source carrier wave (CW);

[0400] third configuration information, used to configure an AIoT read-write device to transmit an AIoT interface message over the air.

[0401] Optionally, the first configuration information further comprises fourth configuration information, and the fourth configuration information comprises at least one of the following:

[0402] a validity duration of the second configuration information;

[0403] a valid area of the second configuration information.

[0404] Optionally, the apparatus further comprises:

[0405] a receiving module, configured to receive first response information or second response information from the terminal;

[0406] The first response information is used to indicate that the terminal successfully receives the first configuration information or the terminal is configured to be an AIoT read-write device, and the second response information is used to indicate that the terminal does not expect to be an AIoT read-write device or preference information of the terminal as an AIoT read-write device.

[0407] Optionally, the second response information comprises at least one of the following:

[0408] time information used to indicate a time period during which the terminal expects to be an AIoT read-write device;

[0409] a communication frequency band of an AIoT interface preferred by the terminal in the case of being an AIoT read-write device;

[0410] an RRC state preferred by the terminal in the case of being an AIoT read-write device.

[0411] Optionally, the first configuration information is carried in a radio resource control (RRC) reconfiguration message or a system message.

[0412] Or,

[0413] The first response information is carried in an RRC reconfiguration complete message.

[0414] Or,

[0415] The second response information is carried in a user equipment assistance information (UAI) message.

[0416] Optionally, the sending of the first configuration information to the terminal comprises:

[0417] sending a first RRC release message to the terminal, the first RRC release message comprising the first configuration information, and the first RRC release message being an RRC release message carrying suspend configuration (SuspendConfig).

[0418] Optionally, the apparatus further comprises:

[0419] a receiving module, configured to receive a first RRC setup request message or a first RRC resume request message from the terminal;

[0420] The first RRC setup request message carries a second cause value, and the second cause value is used to indicate that the terminal initiates connection establishment because the terminal expects to become an AIoT read-write device. The first RRC resume request message carries a third cause value, and the third cause value is used to indicate that the terminal initiates connection recovery because the terminal expects to become an AIoT read-write device.

[0421] Optionally, the sending the first configuration information to the terminal comprises:

[0422] sending the first RRC setup message or the first RRC resume message to the terminal.

[0423] The first RRC setup message or the first RRC resume message comprises the first configuration information.

[0424] Optionally, the apparatus further comprises:

[0425] The receiving module is configured to receive a second RRC setup request message or a second RRC resume request message from the terminal.

[0426] The second RRC setup request message or the second RRC resume request message carries second indication information, and the second indication information is used to indicate that the terminal does not expect to become an AIoT read-write device or preference information of the terminal as an AIoT read-write device.

[0427] Optionally, the second indication information comprises at least one of the following:

[0428] time information used to indicate a time period during which the terminal expects to become an AIoT read-write device;

[0429] a communication frequency band of an AIoT interface preferred by the terminal in the case of the terminal as an AIoT read-write device;

[0430] an RRC state preferred by the terminal in the case of the terminal as an AIoT read-write device.

[0431] Optionally, the second RRC setup request message or the second RRC resume request message is carried by MSG1 or MSGA of a random access procedure.

[0432] Optionally, the apparatus further comprises:

[0433] The sending module is configured to send an RRC reject message or a second RRC release message or a third RRC release message to the terminal, and the third RRC release message is a release message carrying SuspendConfig.

[0434] Optionally, the apparatus further comprises:

[0435] The receiving module is configured to receive a third RRC resume request message from the terminal.

[0436] Optionally, the third RRC resume request message comprises an AIoT service response, and the AIoT service response is used to respond to an AIoT service request sent by the network-side device.

[0437] Optionally, the apparatus further comprises:

[0438] The sending module is configured to send a second RRC resume message to the terminal.

[0439] The receiving module is further configured to receive an AIoT service response from the terminal, and the AIoT service response is used to respond to an AIoT service request sent by the network-side device.

[0440] The environment Internet of Things configuration apparatus provided in the embodiments of the present application can implement each process implemented by the method embodiment of Figure 6 and achieve the same technical effects. To avoid repetition, details are not described herein.

[0441] As shown in Figure 12, the embodiments of the present application further provide a communication device 1200, which comprises a processor 1201 and a memory 1202, and the memory 1202 stores programs or instructions executable on the processor 1201. For example, when the communication device 1200 is a terminal, the programs or instructions are executed by the processor 1201 to implement each step of the above-mentioned environment Internet of Things configuration method embodiments and achieve the same technical effects. When the communication device 1200 is a network-side device, the programs or instructions are executed by the processor 1201 to implement each step of the above-mentioned environment Internet of Things configuration method embodiments and achieve the same technical effects. To avoid repetition, details are not described herein.

[0442] The embodiments of the present application further provide a terminal, which comprises a processor and a communication interface, the communication interface is coupled to the processor, and the processor is configured to run programs or instructions to implement the steps in the method embodiment shown in Figure 5. The terminal embodiment corresponds to the above-mentioned terminal-side method embodiment, and each implementation process and implementation manner of the above-mentioned method embodiment can be applied to the terminal embodiment and achieve the same technical effects. The terminal can be the environment Internet of Things configuration apparatus shown in Figure 10. Specifically, Figure 13 is a hardware structure schematic diagram of a terminal for implementing the embodiments of the present application.

[0443] The terminal 1300 comprises, but is not limited to, at least part of components such as a radio frequency unit 1301, a network module 1302, an audio output unit 1303, an input unit 1304, a sensor 1305, a display unit 1306, a user input unit 1307, an interface unit 1308, a memory 1309, and a processor 1310.

[0444] Those skilled in the art can understand that the terminal 1300 can also include a power supply (such as a battery) for supplying power to each component, and the power supply can be logically connected to the processor 1310 through a power management system, so that the power management system can realize the functions of managing charging, discharging, and power consumption management. The terminal structure shown in FIG. 13 does not constitute a limitation on the terminal, and the terminal can include more or fewer components than those shown, or combine certain components, or different component arrangements, which will not be described here.

[0445] It should be understood that in the embodiments of the present application, the input unit 1304 can include a graphics processor 13041 and a microphone 13042. The graphics processor 13041 processes image data of a still picture or a video obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode. The display unit 1306 can include a display panel 13061, which can be configured in the form of a liquid crystal display, an organic light-emitting diode, etc. The user input unit 1307 includes at least one of a touch panel 13071 and other input devices 13072. The touch panel 13071 is also called a touch screen. The touch panel 13071 can include two parts of a touch detection device and a touch controller. The other input devices 13072 can include, but are not limited to, a physical keyboard, function keys (such as volume control keys, on-off keys, etc.), trackballs, mice, joysticks, which will not be described here.

[0446] In the embodiments of the present application, after the radio frequency unit 1301 receives the downlink data from the network side device, it can be transmitted to the processor 1310 for processing. In addition, the radio frequency unit 1301 can send uplink data to the network side device. Generally, the radio frequency unit 1301 includes, but is not limited to, an antenna, an amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, etc.

[0447] The memory 1309 can be used to store software programs or instructions and various data. The memory 1309 can mainly include a first storage area storing programs or instructions and a second storage area storing data, wherein the first storage area can store an operating system, application programs or instructions required by at least one function (such as a sound playing function, an image playing function, etc.), and the like. In addition, the memory 1309 can include a volatile memory or a non-volatile memory. The non-volatile memory can be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically EPROM (EEPROM), or a flash memory. The volatile memory can be a Random Access Memory (RAM), a Static RAM (SRAM), a Dynamic RAM (DRAM), a Synchronous DRAM (SDRAM), a Double Data Rate SDRAM (DDR SDRAM), an Enhanced SDRAM (ESDRAM), a Synch link DRAM (SLDRAM), and a Direct Rambus RAM (DRRAM). The memory 1309 in the embodiments of the present application includes but is not limited to these and any other suitable types of memory.

[0448] The processor 1310 can include one or more processing units; optionally, the processor 1310 integrates an application processor and a modem processor, wherein the application processor mainly processes operations related to an operating system, a user interface, and an application program, and the modem processor mainly processes wireless communication signals, such as a baseband processor. It can be understood that the above-mentioned modem processor can also not be integrated into the processor 1310.

[0449] The processor 1310 is configured to perform a first operation, and the first operation includes at least one of the following: receiving a paging message from a network side device, the paging message carrying a first cause value, the first cause value being used to indicate that a paging cause is that the network side device expects the terminal as an AIoT read-write device; receiving first configuration information from the network side device, the first configuration information being environment Internet of Things (AIoT) read-write device related configuration information.

[0450] It can be understood that the implementation process of each implementation mode mentioned in the embodiment can refer to the related description of the environment Internet of Things configuration method embodiment, and achieve the same or corresponding technical effects. To avoid repetition, it will not be repeated here.

[0451] The embodiment of the application further provides a network side device, comprising a processor and a communication interface, the communication interface and the processor are coupled, the processor is used to run programs or instructions, and the steps of the method embodiment shown in FIG. 6 are realized. The network side device embodiment corresponds to the network side device method embodiment described above. Each implementation process and implementation mode of the above method embodiment can be applied to the network side device embodiment, and the same technical effects can be achieved.

[0452] Specifically, the embodiment of the application further provides a network side device, which can be the environment Internet of Things configuration apparatus shown in FIG. 11. As shown in FIG. 14, the network side device 1400 comprises an antenna 1401, a radio frequency device 1402, a baseband device 1403, a processor 1404 and a memory 1405. The antenna 1401 is connected with the radio frequency device 1402. In the uplink direction, the radio frequency device 1402 receives information through the antenna 1401, and sends the received information to the baseband device 1403 for processing. In the downlink direction, the baseband device 1403 processes the information to be sent, and sends it to the radio frequency device 1402. The radio frequency device 1402 processes the received information and sends it out through the antenna 1401.

[0453] The method performed by the network side device in the above embodiment can be implemented in the baseband device 1403, which comprises a baseband processor.

[0454] The baseband device 1403 may, for example, comprise at least one baseband board, which is provided with a plurality of chips, as shown in FIG. 14. One of the chips is, for example, a baseband processor, which is connected with the memory 1405 through a bus interface to call the programs in the memory 1405 and execute the network device operations shown in the above method embodiment.

[0455] The network side device may, for example, further comprise a network interface 1406, which is, for example, a Common Public Radio Interface (CPRI).

[0456] Specifically, the network side device 1400 of the embodiment of the application further comprises instructions or programs stored in the memory 1405 and executable on the processor 1404. The processor 1404 calls the instructions or programs in the memory 1405 to execute the method performed by each module shown in FIG. 11, and achieves the same technical effects. To avoid repetition, it will not be repeated here.

[0457] The embodiment of the present application further provides a readable storage medium, and the readable storage medium stores a program or instructions, which are executed by a processor to implement each process of the environment Internet of Things configuration method embodiment and achieve the same technical effects. To avoid repetition, details are not described herein.

[0458] The processor is the processor in the terminal in the above embodiments. The readable storage medium includes a computer readable storage medium, such as a computer readable only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, etc. In some examples, the readable storage medium can be a non-transitory readable storage medium.

[0459] The embodiment of the present application further provides a chip, which includes a processor and a communication interface. The communication interface is coupled with the processor. The processor is used to run a program or instructions to implement each process of the environment Internet of Things configuration method embodiment and achieve the same technical effects. To avoid repetition, details are not described herein.

[0460] It should be understood that the chip mentioned in the embodiment of the present application can also be referred to as a system chip, a system chip, a chip system or a system on chip, etc.

[0461] The embodiment of the present application further provides a computer program / program product, which is stored in a storage medium. The computer program / program product is executed by at least one processor to implement each process of the environment Internet of Things configuration method embodiment and achieve the same technical effects. To avoid repetition, details are not described herein.

[0462] The embodiment of the present application further provides a wireless communication system, which includes a terminal and a network side device. The terminal can be used to execute the steps of the environment Internet of Things configuration method. The network side device can be used to execute the steps of the environment Internet of Things configuration method.

[0463] It should be noted that, in the present document, the terms "comprises", "comprising", or any other variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but can also include other elements not expressly listed or inherent to such process, method, article, or apparatus. An element proceeded by "comprises a", "comprising", or the like does not, without more constraints, preclude the existence of additional identical elements in the process, method, article, or apparatus that comprises the element. Furthermore, it is to be understood that the methods and apparatuses of the present application can be carried out by specific hardware, software, or a combination thereof, and that the scope of the application is not limited to the specific order of execution of the steps described in the examples. In addition, features described in relation to certain examples can be combined in other examples.

[0464] From the above description of the embodiments, it is clear that the above-mentioned method can be realized by means of a computer software product and a general hardware platform, of course, it can also be realized by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disc, optical disc, etc.), and includes a plurality of instructions for making the terminal or network side device execute the method described in each embodiment of the present application.

[0465] The embodiments of the present application are described above in combination with the drawings, but the present application is not limited to the above-mentioned specific embodiments, the above-mentioned specific embodiments are only illustrative, not restrictive, and those skilled in the art can make many forms of embodiments under the inspiration of the present application without departing from the scope of the present application and the scope protected by the claims.

Claims

1. A method for configuring an environmental Internet of Things, comprising: a terminal performing a first operation, the first operation comprising at least one of: receiving a paging message from a network side device, the paging message carrying a first cause value, the first cause value indicating that a paging cause is that the network side device expects the terminal to be an AIoT read-write device; receiving first configuration information from the network side device, the first configuration information being configuration information related to an AIoT read-write device of an environmental Internet of Things.

2. The method of claim 1, wherein, the first configuration information comprising second configuration information, the second configuration information comprising at least one of: first resource information indicating a resource for the AIoT read-write device to send a message to an AIoT device; second resource information indicating a resource for the AIoT device to send a message to the AIoT read-write device; third resource information indicating a resource for the AIoT read-write device to perform AIoT communication with the AIoT device; first indication information indicating whether the AIoT read-write device needs to send a carrier wave (CW) of an excitation source, the CW being used to excite the AIoT device to send a message; third configuration information used to configure the AIoT read-write device to transmit an AIoT interface message with the network side device.

3. The method of claim 2, wherein, the first configuration information further comprising fourth configuration information, the fourth configuration information comprising at least one of: a validity duration of the second configuration information; a validity area of the second configuration information.

4. The method of claim 1 or 2, wherein, after the receiving the first configuration information from the network side device, the method further comprising: the terminal sending first response information or second response information to the network side device; wherein the first response information is used to indicate that the terminal successfully receives the first configuration information or that the terminal is configured to be an AIoT read-write device, and the second response information is used to indicate that the terminal does not expect to be an AIoT read-write device or preference information of the terminal as an AIoT read-write device.

5. The method of claim 4, wherein, the second response information comprising at least one of: time information indicating a time period during which the terminal expects to be an AIoT read-write device; a communication frequency band of an AIoT interface preferred by the terminal as an AIoT read-write device; an RRC state preferred by the terminal as an AIoT read-write device.

6. The method of claim 4 or 5, wherein: the first configuration information is carried in a radio resource control (RRC) reconfiguration message or a system message; alternatively, the first response information is carried in an RRC reconfiguration complete message; alternatively, the second response information is carried in a user equipment assistance information (UAI) message.

7. The method of any one of claims 1 to 3, wherein, after the receiving the first configuration information from the network side device, the method further comprising: the terminal performing AIoT communication with an AIoT device in a deactivated state.

8. The method of claim 7, wherein, the receiving the first configuration information from the network side device comprises: receiving a first RRC release message from a network side device node, the first RRC release message carrying the first configuration information, the first RRC release message being an RRC release message carrying suspend configuration (SuspendConfig).

9. The method of any one of claims 1 to 3, wherein, after the receiving the paging message from the network side device, the method further comprising: The terminal determines whether to respond to the paging message according to the first information; The first information includes at least one of the following: The capability information of the terminal, which is the capability information related to the terminal as an AIoT read-write device; Whether the terminal is authenticated as an AIoT read-write device; Whether the first frequency band matches the second frequency band, the first frequency band being an AIoT communication frequency band broadcast by a serving cell of the terminal, and the second frequency band being an AIoT communication frequency band supported by the terminal as an AIoT read-write device; Whether the terminal has valid target configuration information, the target configuration information being used for the terminal to perform AIoT communication as an AIoT read-write device; The power of the terminal; The air interface traffic of the terminal.

10. The method of claim 1, 2, 3, or 9, wherein, The method further includes: The terminal sends a first RRC setup request message or a first RRC resume request message to the network side device; The first RRC setup request message carries a second cause value, and the second cause value indicates that the terminal initiates connection establishment because the terminal expects to become an AIoT read-write device, and the first RRC resume request message carries a third cause value, and the third cause value indicates that the terminal initiates connection recovery because the terminal expects to become an AIoT read-write device.

11. The method of claim 10, wherein, The first configuration information received from the network side device includes: The terminal receives a first RRC setup message or a first RRC resume message from the network side device; The first RRC setup message or the first RRC resume message carries the first configuration information.

12. The method of claim 1, 2, 3, or 9, wherein, The method further includes: The terminal sends a second RRC setup request message or a second RRC resume request message to the network side device; The second RRC setup request message or the second RRC resume request message carries second indication information, and the second indication information indicates that the terminal does not expect to become an AIoT read-write device or preference information of the terminal as an AIoT read-write device.

13. The method of claim 12, wherein, The second indication information includes at least one of the following: Time information, used to indicate a time period during which the terminal expects to become an AIoT read-write device; A communication frequency band of an AIoT interface preferred by the terminal as an AIoT read-write device; An RRC state preferred by the terminal as an AIoT read-write device.

14. The method of claim 12 or 13, wherein, The second RRC setup request message or the second RRC resume request message is carried by MSG1 or MSGA of a random access process.

15. The method of any one of claims 12 to 14, wherein, The method further includes: The terminal receives an RRC reject message or a second RRC release message or a third RRC release message from the network side device, and the third RRC release message is a release message carrying SuspendConfig.

16. The method of claim 1, 2, 3, or 9, wherein, After receiving the paging message from the network side device, the method further includes: The terminal performs AIoT communication with an AIoT device in an idle state.

17. The method of claim 7 or 8, wherein, The method further includes: In a case where the terminal completes AIoT communication with the AIoT device, the terminal sends a third RRC resume request message to the network side device.

18. The method of claim 17, wherein, The third RRC recovery request message includes an AIoT service response, and the AIoT service response is used to respond to the AIoT service request sent by the network side device.

19. The method of claim 17, wherein, The method further includes: The terminal receives a second RRC recovery message from the network side device; In the case of recovery to the connected state, the terminal sends an AIoT service response to the network side device, and the AIoT service response is used to respond to the AIoT service request sent by the network side device.

20. An environmental Internet of Things configuration method, comprising: The network side device performs a second operation, and the second operation includes at least one of the following: sending a paging message to the terminal, the paging message carrying a first cause value, and the first cause value being used to indicate that the paging reason is that the network side device expects the terminal to be an AIoT read-write device; sending first configuration information to the terminal, and the first configuration information being environmental Internet of Things (AIoT) read-write device related configuration information.

21. The method of claim 20, wherein, The first configuration information includes second configuration information, and the second configuration information includes at least one of the following: first resource information, used to indicate a resource of a message sent by an AIoT read-write device to an AIoT device; second resource information, used to indicate a resource of a message sent by an AIoT device to an AIoT read-write device; third resource information, used to indicate a resource of AIoT communication between an AIoT read-write device and an AIoT device; first indication information, used to indicate whether the AIoT read-write device needs to send a stimulating source carrier (CW); third configuration information, used to configure the AIoT read-write device to transmit an AIoT interface message over the air.

22. The method of claim 21, wherein, The first configuration information further includes fourth configuration information, and the fourth configuration information includes at least one of the following: a valid time length of the second configuration information; a valid area of the second configuration information.

23. The method of any one of claims 20-22, wherein, The method further includes: The network side device receives first response information or second response information from the terminal; The first response information is used to indicate that the terminal successfully receives the first configuration information or the terminal is configured to be an AIoT read-write device, and the second response information is used to indicate that the terminal does not expect to be an AIoT read-write device or preference information of the terminal as an AIoT read-write device.

24. The method of claim 23, wherein, The second response information includes at least one of the following: time information, used to indicate a time period during which the terminal expects to be an AIoT read-write device; a communication frequency band of an AIoT interface preferred by the terminal in the case of being an AIoT read-write device; an RRC state preferred by the terminal in the case of being an AIoT read-write device.

25. The method of claim 23 or 24, wherein: the first configuration information is carried in a radio resource control (RRC) reconfiguration message or a system message; alternatively, the first response information is carried in an RRC reconfiguration complete message; alternatively, the second response information is carried in a user equipment assistance information (UAI) message.

26. The method of any one of claims 20-22, wherein, The first configuration information is sent to the terminal, including: sending a first RRC release message to the terminal, the first RRC release message including the first configuration information, the first RRC release message being an RRC release message carrying SuspendConfig.

27. The method of any one of claims 20-22, wherein, The method further includes: receiving, by the network-side device, a first RRC setup request message or a first RRC resume request message from the terminal; wherein the first RRC setup request message carries a second cause value, the second cause value being used to indicate that the terminal initiates connection establishment because the terminal expects to become an AIoT read-write device, and the first RRC resume request message carries a third cause value, the third cause value being used to indicate that the terminal initiates connection resumption because the terminal expects to become an AIoT read-write device.

28. The method of claim 27, wherein, The first configuration information sent to the terminal includes: sending a first RRC setup message or a first RRC resume message to the terminal; wherein the first RRC setup message or the first RRC resume message includes the first configuration information.

29. The method of any one of claims 20-22, wherein, The method further includes: receiving, by the network-side device, a second RRC setup request message or a second RRC resume request message from the terminal; wherein the second RRC setup request message or the second RRC resume request message carries second indication information, the second indication information being used to indicate that the terminal does not expect to become an AIoT read-write device or preference information of the terminal as an AIoT read-write device.

30. The method of claim 29, wherein, The second indication information includes at least one of: time information used to indicate a time period during which the terminal expects to become an AIoT read-write device; a communication frequency band of an AIoT interface preferred by the terminal in the case of becoming an AIoT read-write device; an RRC state preferred by the terminal in the case of becoming an AIoT read-write device.

31. The method of claim 29 or 30, wherein, The second RRC setup request message or the second RRC resume request message is carried by MSG1 or MSGA of a random access procedure.

32. The method of any one of claims 29-31, wherein, The method further includes: sending, by the network-side device, an RRC reject message or a second RRC release message or a third RRC release message to the terminal, the third RRC release message being a release message carrying SuspendConfig.

33. The method of claim 26, wherein, The method further includes: receiving, by the network-side device, a third RRC resume request message from the terminal.

34. The method of claim 33, wherein, The third RRC resume request message includes an AIoT service response, the AIoT service response being used to respond to an AIoT service request sent by the network-side device.

35. The method of claim 34, wherein, The method further includes: sending, by the network-side device, a second RRC resume message to the terminal; receiving, by the network-side device, an AIoT service response from the terminal, the AIoT service response being used to respond to an AIoT service request sent by the network-side device.

36. An environmental Internet of Things configuration apparatus, comprising: a processing module configured to perform a first operation, the first operation including at least one of: receiving a paging message from a network-side device, the paging message carrying a first cause value, the first cause value being used to indicate that a paging cause is that the network-side device expects a terminal to become an AIoT read-write device; receive first configuration information from a network side device, the first configuration information being configuration information related to an environment Internet of Things (AIoT) read-write device.

37. The apparatus of claim 36, wherein, The first configuration information includes second configuration information, and the second configuration information includes at least one of the following: first resource information, used to indicate a resource for the AIoT read-write device to send a message to an AIoT device; second resource information, used to indicate a resource for the AIoT device to send a message to the AIoT read-write device; third resource information, used to indicate a resource for the AIoT read-write device to perform AIoT communication with the AIoT device; first indication information, used to indicate whether the AIoT read-write device needs to send a carrier (CW) of an excitation source, the CW being used to excite the AIoT device to send a message; third configuration information, used to configure the AIoT read-write device to transmit an AIoT interface message with the network side device.

38. The apparatus of claim 36 or 37, wherein, The apparatus further includes: a sending module, configured to send first response information or second response information to the network side device; wherein the first response information is used to indicate that the terminal successfully receives the first configuration information or that the terminal is configured to be an AIoT read-write device, and the second response information is used to indicate that the terminal does not expect to be an AIoT read-write device or preference information of the terminal as an AIoT read-write device.

39. The apparatus of claim 36 or 37, wherein, The processing module is further configured to perform AIoT communication with an AIoT device in a deactivated state.

40. The apparatus of claim 36 or 37, wherein, The processing module is further configured to determine whether to respond to the paging message according to first information. The first information includes at least one of the following: capability information of the terminal, the capability information being capability information related to the terminal as an AIoT read-write device; whether the terminal is authenticated as an AIoT read-write device; whether a first frequency band and a second frequency band match, the first frequency band being an AIoT communication frequency band broadcast by a serving cell of the terminal, and the second frequency band being an AIoT communication frequency band supported by the terminal as an AIoT read-write device; whether the terminal has valid target configuration information, the target configuration information being used for the terminal to perform AIoT communication as an AIoT read-write device; a power level of the terminal; and an air interface traffic condition of the terminal.

41. An environment Internet of Things (AIoT) configuration apparatus, comprising: a processing module, configured to perform a second operation, the second operation including at least one of the following: sending a paging message to a terminal, the paging message carrying a first cause value, the first cause value being used to indicate that a paging cause is that a network side device expects the terminal to be an AIoT read-write device; sending first configuration information to the terminal, the first configuration information being configuration information related to an environment Internet of Things (AIoT) read-write device.

42. The device of claim 41, wherein, The apparatus further includes: a receiving module, configured to receive first response information or second response information from the terminal; wherein the first response information is used to indicate that the terminal successfully receives the first configuration information or that the terminal is configured to be an AIoT read-write device, and the second response information is used to indicate that the terminal does not expect to be an AIoT read-write device or preference information of the terminal as an AIoT read-write device.

43. The device of claim 41, wherein, The apparatus further includes: a receiving module, configured to receive a first RRC setup request message or a first RRC resume request message from the terminal; wherein the first RRC setup request message carries a second cause value, and the second cause value is used to indicate that the terminal initiates connection establishment because the terminal expects to become an AIoT read-write device; and the first RRC resume request message carries a third cause value, and the third cause value is used to indicate that the terminal initiates connection resumption because the terminal expects to become an AIoT read-write device. 44.A terminal, comprising a processor and a memory, the memory storing programs or instructions executable on the processor, the programs or instructions being executed by the processor to implement the steps of the ambient Internet of Things configuration method according to any one of claims 1 to 19. 45.A network side device, comprising a processor and a memory, the memory storing programs or instructions executable on the processor, the programs or instructions being executed by the processor to implement the steps of the ambient Internet of Things configuration method according to any one of claims 20 to 35. 46.A readable storage medium, the readable storage medium storing programs or instructions, the programs or instructions being executed by a processor to implement the steps of the ambient Internet of Things configuration method according to any one of claims 1 to 19, or to implement the steps of the ambient Internet of Things configuration method according to any one of claims 20 to 35. 47.A computer program product, the computer program product being executed by at least one processor to implement the steps of the ambient Internet of Things configuration method according to any one of claims 1 to 19, or to implement the steps of the ambient Internet of Things configuration method according to any one of claims 20 to 35.

Images