Communication methods, terminals, network devices and storage medium

Abstract

The present disclosure relates to communication methods, terminals, network devices and a storage medium. A communication method comprises: when configured as an intermediate node of an ambient Internet of Things (A-IOT) system, a terminal remains in a radio resource control (RRC) connected state. In the method of the present disclosure, when a terminal is configured as an A-IOT intermediate node, the terminal remains in an RRC connected state, so as to be capable of forwarding A-IOT data in a timely manner, thereby ensuring A-IOT communication performance.

Description

Communication method, terminal, network device and storage medium TECHNICAL FIELD

[0001] The present disclosure relates to the technical field of communication, and in particular to a communication method, a terminal, a network device and a storage medium. BACKGROUND

[0002] Ambient Internet of Things (Ambient-IoT or A-IoT) technology is an Internet of Things technology that supports power acquisition from the environment or energy acquisition from the environment, or is also called a passive Internet of Things. A-IOT can obtain energy by collecting radio waves, light, motion, heat or any other suitable power source in the environment, and the complexity, cost and maintenance cost of the device are lower, which is conducive to improving network performance and sustainability.

[0003] SUMMARY

[0004] When there is no receipt transceiving on the User to Network interface-Universal (Uu) between the terminal and the network device, the terminal can enter a Radio Resource Control (RRC) idle state (RRC_IDLE), but in the topology structure supported by A-IOT, the terminal needs to forward A-IOT data in some scenarios.

[0005] Embodiments of the present disclosure provide a communication method, a terminal, a network device and a storage medium.

[0006] In a first aspect, embodiments of the present disclosure provide a communication method, executed by a terminal, comprising:

[0007] In a case where the terminal is configured as an intermediate node of an Ambient Internet of Things (A-IoT) system, the terminal is kept in a Radio Resource Control (RRC) connected state (RRC_CONNECTED).

[0008] In a second aspect, embodiments of the present disclosure provide a communication method, executed by a network device, comprising:

[0009] Sending configuration information to a terminal, the configuration information being used for configuring the terminal as an intermediate node of an Ambient Internet of Things (A-IoT) system, wherein in a case where the terminal is configured as the intermediate node, the terminal is in an RRC connected state.

[0010] In a third aspect, embodiments of the present disclosure provide a terminal, comprising:

[0011] A processing module, configured to, in a case where the terminal is configured as an intermediate node of an Ambient Internet of Things (A-IoT) system, keep the terminal in a Radio Resource Control (RRC) connected state.

[0012] In a fourth aspect, an embodiment of the present disclosure provides a network device, comprising:

[0013] a transceiver configured to send configuration information to a terminal, the configuration information being used to configure the terminal as an intermediate node of an ambient Internet of Things (A-IOT) system, wherein the terminal is in an RRC connected state when the terminal is configured as the intermediate node.

[0014] In a fifth aspect, an embodiment of the present disclosure provides a terminal, comprising:

[0015] one or more processors;

[0016] The terminal is configured to implement the method of the first aspect.

[0017] In a sixth aspect, an embodiment of the present disclosure provides a network device, comprising:

[0018] one or more processors;

[0019] The network device is configured to implement the method of the second aspect.

[0020] In a seventh aspect, an embodiment of the present disclosure provides a communication system, comprising a terminal and a network device, wherein:

[0021] The terminal is configured to implement the method of the first aspect;

[0022] The network device is configured to implement the method of the second aspect.

[0023] In an eighth aspect, an embodiment of the present disclosure provides a storage medium, the storage medium storing instructions, wherein:

[0024] When the instructions run on a communication device, the communication device is caused to perform the method of the first aspect or the second aspect.

[0025] In a ninth aspect, an embodiment of the present disclosure provides a program product, wherein:

[0026] When the program product is executed by a communication device, the communication device is caused to perform the method of the first aspect or the second aspect.

[0027] In an embodiment of the present disclosure, when the terminal is configured as an intermediate node of an A-IOT, the terminal is kept in an RRC connected state, so that A-IOT data can be forwarded in time and the communication performance of the A-IOT is ensured. BRIEF DESCRIPTION OF DRAWINGS

[0028] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure, the following describes the drawings required for the embodiments, and the following drawings are only some embodiments of the present disclosure, and do not specifically limit the protection scope of the present disclosure.

[0029] FIGS. 1a-1g are one exemplary schematic diagram of an architecture of a communication system according to embodiments of the present disclosure;

[0030] FIG. 2 is an exemplary interactive schematic diagram of a method according to embodiments of the present disclosure;

[0031] FIGS. 3a-3b are exemplary flowcharts of a method according to embodiments of the present disclosure;

[0032] FIGS. 4a-4b are exemplary flowcharts of a method according to embodiments of the present disclosure;

[0033] FIG. 5a is a structural schematic diagram of a terminal according to embodiments of the present disclosure;

[0034] FIG. 5b is a structural schematic diagram of a communication device according to embodiments of the present disclosure;

[0035] FIG. 6a is a schematic diagram of a communication device according to embodiments of the present disclosure;

[0036] FIG. 6b is a schematic diagram of a communication device according to embodiments of the present disclosure. DETAILED DESCRIPTION

[0037] The embodiments of the present disclosure provide a communication method, a terminal, a network device and a storage medium.

[0038] In a first aspect, the embodiments of the present disclosure provide a communication method, executed by a terminal, comprising:

[0039] In a case where the terminal is configured as an intermediate node of an ambient Internet of Things (A-IOT) system, the terminal is kept in a radio resource control (RRC) connected state.

[0040] In the above embodiments, when the terminal is configured as an intermediate node of an A-IOT, the terminal is kept in an RRC connected state regardless of whether there is data transmission and reception on a Uu interface, so that A-IOT data can be forwarded in time and the communication performance of the A-IOT is ensured.

[0041] In combination with the embodiments of the first aspect, in some embodiments, the method further comprises:

[0042] receiving configuration information sent by the network device, the configuration information being used to configure the terminal as an intermediate node.

[0043] In combination with the embodiments of the first aspect, in some embodiments, the terminal is not configured with a first timer or is configured with the first timer.

[0044] With reference to the embodiments of the first aspect, in some embodiments, the terminal is not configured with the first timer when the terminal is configured as the intermediate node; wherein the first timer is configured when the terminal is not configured as the intermediate node.

[0045] With reference to the embodiments of the first aspect, in some embodiments, the terminal is configured with the first timer.

[0046] With reference to the embodiments of the first aspect, in some embodiments, the first timer is started or restarted when the terminal receives or transmits the A-IOT information; for example, the first timer is started or restarted when the first Media Access Control (MAC) entity of the terminal 101 receives or transmits the A-IOT information. Wherein the terminal is in the RRC connected state during the running of the first timer, and the first MAC entity is used for communication with the A-IOT device.

[0047] With reference to the embodiments of the first aspect, in some embodiments, the receiving or transmitting the A-IOT information comprises at least one of:

[0048] receiving the first command sent by the A-IOT device, such as the first MAC entity of the terminal 101 receiving the first command sent by the A-IOT device;

[0049] transmitting the second command to the A-IOT device, such as the first MAC entity of the terminal 101 transmitting the second command to the A-IOT device;

[0050] transmitting a Continuous Wave (CW) to the A-IOT device, such as the first MAC entity of the terminal transmitting the CW to the A-IOT device.

[0051] With reference to the embodiments of the first aspect, in some embodiments, the method further comprises:

[0052] when the first timer is configured, the terminal does not start the first timer, such as the second MAC entity of the terminal does not start the first timer; wherein the first timer is started when the terminal is not configured as the intermediate node, and the second MAC entity is used for communication with the network device.

[0053] With reference to the embodiments of the first aspect, in some embodiments, when the terminal is configured with the first timer, the method further comprises:

[0054] when the first timer expires, the RRC layer of the terminal controls the terminal to remain in the RRC connected state and does not enter the RRC idle state;

[0055] Alternatively, the method further comprises:

[0056] When the terminal is not configured as an intermediate node, the terminal enters an RRC idle state after the first timer expires.

[0057] In some embodiments of the first aspect, the method further comprises:

[0058] The MAC layer (e.g., the second MAC entity) of the terminal receives the indication information from the higher layer, and determines the state of the first timer according to the indication information from the higher layer. The terminal is configured with the first timer.

[0059] In some embodiments of the first aspect, the indication information is used to indicate that the first timer is stopped, and determining the state of the first timer according to the indication information comprises:

[0060] The MAC layer (e.g., the second MAC entity) stops running the first timer when receiving the indication information sent by the RRC layer, or starts the first timer when not receiving the indication information.

[0061] In some embodiments of the first aspect, the indication information is used to indicate that the first timer is not started, and determining the state of the first timer according to the indication information comprises:

[0062] The MAC layer (e.g., the second MAC entity) does not start the first timer when receiving the indication information sent by the RRC layer, or starts the first timer when not receiving the indication information.

[0063] In some embodiments of the first aspect, the indication information is used to indicate that the first timer is started, and determining the state of the first timer according to the indication information comprises:

[0064] The MAC layer (e.g., the second MAC entity) starts the first timer when receiving the indication information sent by the RRC layer, or

[0065] The MAC layer does not start the first timer when not receiving the indication information.

[0066] In some embodiments of the first aspect, the indication information comprises at least one of:

[0067] receiving the stop indication information;

[0068] receiving the non-start indication information;

[0069] not receiving the start indication information.

[0070] In some embodiments of the first aspect, determining the state of the first timer comprises:

[0071] stopping running the first timer; or

[0072] not starting the first timer.

[0073] In some embodiments of the first aspect, the indication information comprises at least one of:

[0074] no stop indication information is received;

[0075] no non-start indication information is received;

[0076] start indication information is received.

[0077] In some embodiments of the first aspect, determining the state of the first timer comprises:

[0078] starting the first timer.

[0079] In some embodiments of the first aspect, the method further comprises:

[0080] receiving A-IOT data or signaling sent by the network device;

[0081] sending A-IOT data or signaling to the A-IOT device.

[0082] In a second aspect, the embodiments of the present disclosure provide a communication method, executed by a network device, comprising:

[0083] sending configuration information to a terminal, the configuration information being used to configure the terminal as an intermediate node of an ambient Internet of Things (A-IOT) system, wherein the terminal is in an RRC connected state when the terminal is configured as the intermediate node.

[0084] In some embodiments of the second aspect, the terminal is configured or not configured with the first timer.

[0085] In some embodiments of the second aspect, the method further comprises:

[0086] when the terminal is configured as the intermediate node, not configuring the terminal with the first timer, wherein the first timer is configured when the terminal is not configured as the intermediate node.

[0087] In some embodiments of the second aspect, the method further comprises:

[0088] configuring the terminal with the first timer.

[0089] In some embodiments of the second aspect, the first timer is started or restarted when the terminal receives or sends A-IOT information, wherein the terminal is in the RRC connected state during running of the first timer.

[0090] In combination with the embodiments of the second aspect, in some embodiments, the A-IOT information comprises at least one of:

[0091] a first command sent by the A-IOT device to the terminal;

[0092] a second command sent by the terminal to the A-IOT device;

[0093] a continuous electromagnetic wave (CW) sent by the terminal to the A-IOT device.

[0094] In combination with the embodiments of the second aspect, in some embodiments, the first timer is not started when the terminal is configured as an intermediate node, in a case that the first timer is configured, wherein the first timer is started when the terminal is not configured as the intermediate node.

[0095] In combination with the embodiments of the second aspect, in some embodiments, a state of the first timer is determined by a MAC layer of the terminal according to indication information of a higher layer whether to start or not, and the second MAC entity is used for communication with the network device.

[0096] In combination with the embodiments of the second aspect, in some embodiments, the method further comprises:

[0097] sending A-IOT data or signaling to the terminal.

[0098] In a third aspect, the embodiments of the present disclosure provide a terminal, comprising:

[0099] a processing module, configured to keep in a radio resource control (RRC) connected state in a case that the terminal is configured as an intermediate node of an ambient Internet of Things (A-IOT) system.

[0100] In a fourth aspect, the embodiments of the present disclosure provide a network device, comprising:

[0101] a transceiver module, configured to send configuration information to a terminal, the configuration information being used for configuring the terminal as an intermediate node of an ambient Internet of Things (A-IOT) system, wherein the terminal is in an RRC connected state in a case that the terminal is configured as the intermediate node.

[0102] In a fifth aspect, the embodiments of the present disclosure provide a terminal, comprising:

[0103] one or more processors;

[0104] wherein the terminal is configured to implement the method of the first aspect.

[0105] In a sixth aspect, the embodiments of the present disclosure provide a network device, comprising:

[0106] one or more processors;

[0107] The network device is configured to implement the method of the second aspect.

[0108] In a seventh aspect, the embodiments of the present disclosure provide a communication system, comprising a terminal and a network device, wherein,

[0109] The terminal is configured to implement the method of the first aspect.

[0110] The network device is configured to implement the method of the second aspect.

[0111] In an eighth aspect, the embodiments of the present disclosure provide a storage medium, wherein the storage medium stores instructions.

[0112] When the instructions run on a communication device, the communication device executes the method of the first aspect or the second aspect.

[0113] In a ninth aspect, the embodiments of the present disclosure provide a program product, wherein

[0114] When the program product is executed by a communication device, the communication device executes the method of the first aspect or the second aspect.

[0115] In a tenth aspect, the embodiments of the present disclosure provide a computer program, which, when running on a computer, causes the computer to execute the method described in the first aspect, the second aspect, or the optional implementation manner of the third aspect.

[0116] In an eleventh aspect, the embodiments of the present disclosure provide a chip or a chip system. The chip or the chip system comprises processing circuitry configured to execute the method described in the first aspect, the second aspect, or the optional implementation manner of the third aspect.

[0117] It can be understood that the terminal, the device, the communication system, the storage medium, the program product, the computer program, the chip or the chip system are all used to execute the method proposed in the embodiments of the present disclosure. Therefore, the beneficial effects that can be achieved are referred to the beneficial effects in the corresponding method, which will not be described here.

[0118] The embodiments of the present disclosure are not exhaustive, but only illustrate some embodiments, and are not specific limitations on the protection scope of the present disclosure. In the case of no contradiction, each step in an embodiment can be implemented as an independent embodiment, and the steps can be combined arbitrarily, for example, the scheme after removing some steps in an embodiment can also be implemented as an independent embodiment, and the order of the steps in an embodiment can be exchanged arbitrarily, in addition, the optional implementation manners in an embodiment can be combined arbitrarily; in addition, the embodiments can be combined arbitrarily, for example, the steps of different embodiments or the optional implementation manners of other embodiments can be combined arbitrarily, and an embodiment can be combined with the optional implementation manners of other embodiments.

[0119] In each embodiment of the present disclosure, the terms and / or descriptions between the embodiments are consistent if there is no special description and logical conflict, and can be referred to each other, and the technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0120] The terms used in the embodiments of the present disclosure are only for the purpose of describing specific embodiments and are not used as limitations of the present disclosure.

[0121] In the embodiments of the present disclosure, unless otherwise specified, the elements expressed in singular form, such as "one", "one", "the", "the above", "the", "the above", "this", etc. can represent "one and only one", and can also represent "one or more", "at least one", etc. For example, in the case of using articles such as "a", "an", "the" in English, the noun after the article can be understood as singular expression, and can also be understood as plural expression.

[0122] In the embodiments of the present disclosure, "plurality" refers to two or more.

[0123] In some embodiments, the terms "at least one of", "one or more", "a plurality of", "multiple", and the like can be replaced with each other.

[0124] In some embodiments, the writing manner of "at least one of A, B", "A and / or B", "A in one case and B in another case", "A in response to one case and B in response to another case", and the like can include the following technical solutions according to the case: in some embodiments, A (A is executed regardless of B); in some embodiments, B (B is executed regardless of A); in some embodiments, A and B are selected to be executed (A and B are selectively executed); in some embodiments, A and B (A and B are executed). When there are more branches such as A, B, C, etc., it is similar to the above.

[0125] In some embodiments, the writing manner of "A or B" and the like can include the following technical solutions according to the case: in some embodiments, A (A is executed regardless of B); in some embodiments, B (B is executed regardless of A); in some embodiments, A and B are selected to be executed (A and B are selectively executed). When there are more branches such as A, B, C, etc., it is similar to the above.

[0126] The prefix words of "first", "second" and the like in the embodiments of the present disclosure are merely used to distinguish different description objects, and do not constitute limitation on the position, order, priority, quantity or content of the description objects. The description objects are described in the claims or embodiments in the context of the description, and should not be construed as redundant limitation because of the use of the prefix words. For example, the description object is "field", and the ordinal words before "field" in "first field" and "second field" do not limit the position or order between "fields", and "first" and "second" do not limit whether the "fields" modified by them are in the same message or not, nor limit the order of "first field" and "second field". For another example, the description object is "level", and the ordinal words before "level" in "first level" and "second level" do not limit the priority between "levels". For another example, the quantity of the description object is not limited by the ordinal words, and can be one or more. For example, "first device", wherein the quantity of "device" can be one or more. In addition, the objects modified by different prefix words can be the same or different, for example, the description object is "device", and "first device" and "second device" can be the same device or different devices, and their types can be the same or different; for another example, the description object is "information", and "first information" and "second information" can be the same information or different information, and their contents can be the same or different.

[0127] In some embodiments, "including A", "containing A", "for indicating A", "carrying A" can be interpreted as directly carrying A, or indirectly indicating A.

[0128] In some embodiments, the terms of "in response to", "in response to determining", "in the case of", "when", "when", "if", "if" and the like can be replaced with each other.

[0129] In some embodiments, the terms of "greater than", "greater than or equal to", "not less than", "more than", "more than or equal to", "not less than", "higher than", "higher than or equal to", "not lower than", "above" and the like can be replaced with each other, and the terms of "less than", "less than or equal to", "not greater than", "less than", "less than or equal to", "not more than", "lower than", "lower than or equal to", "not higher than", "below" and the like can be replaced with each other.

[0130] In some embodiments, the apparatuses and devices can be interpreted as entities, and can also be interpreted as virtual, whose names are not limited to the names described in the embodiments, and in some cases can also be understood as "equipment", "device", "circuit", "network element", "node", "function", "unit", "section", "system", "network", "chip", "chip system", "entity", "subject", etc.

[0131] In some embodiments, "network" can be interpreted as an apparatus contained in the network, such as a network device, an access network device, a core network device, etc.

[0132] In some embodiments, "access network device (AN device)" can also be referred to as "radio access network device (RAN device)", "base station (BS)", "radio base station", "fixed station", and in some embodiments can also be understood as "node", "access point", "transmission point (TP)", "reception point (RP)", "transmission / reception point (TRP)", "panel", "antenna panel", "antenna array", "cell", "macro cell", "small cell", "femto cell", "pico cell", "sector", "cell group", "serving cell", "carrier", "component carrier", "bandwidth part (BWP)", etc.

[0133] In some embodiments, a "terminal" or "terminal device" can be referred to as a "user equipment" (UE), a "user terminal," a "mobile station" (MS), a "mobile terminal" (MT), a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, and / or the like.

[0134] In some embodiments, data, information, and / or the like can be obtained in compliance with laws and regulations of a country in which a location is situated.

[0135] In some embodiments, data, information, and / or the like can be obtained after consent of a user is obtained.

[0136] Further, each element, each row, or each column in a table of embodiments of the present disclosure can be implemented as an independent embodiment, and a combination of any element, any row, or any column can be implemented as an independent embodiment.

[0137] FIG. 1a is an architecture schematic diagram of a communication system according to an embodiment of the present disclosure, and FIGS. 1b-1f are topological structure schematic diagrams of the communication system according to an embodiment of the present disclosure.

[0138] As shown in FIG. 1a, the communication system 100 includes a terminal 101, a network device 102, and an A-IoT device 103. The communication system 100 can be an A-IoT communication system. Different topological structures or topological scenarios can be supported in the A-IoT communication system. For example:

[0139] Referring to FIG. 1b, the network device 102 and the A-IoT device 103 are directly connected to each other to perform A-IoT data or signaling transmission.

[0140] Referring to FIG. 1c, the terminal 101 acts as an intermediate node to forward data, for example, the A-IoT device 103 communicates with the terminal 101, and the terminal 101 can act as an intermediate node to forward A-IoT data or signaling to the network device 102. The intermediate node can also be a relay, a repeater, or an integrated access backhaul (IAB), etc.

[0141] Referring to FIGS. 1d and 1e, an assisting node 104 is provided in the system, and the A-IoT device 103 and the network device 102 directly perform A-IoT data or signaling reception or transmission in downlink (DL) or uplink (UL); then there is an assisting node 104 in the UL or DL, which is responsible for receiving or sending UL or receiving DL data. The assisting node 104 can be a relay, a repeater, an IAB, or a terminal 101.

[0142] Referring to FIG. 1f, the A-IoT device 103 and the terminal 101 directly perform DL and UL A-IoT data or signaling reception and transmission; the terminal 101 is responsible for collecting data and forwarding the collected data to the network side, such as the network device 102.

[0143] In some embodiments, the terminal 101 includes at least one of a user equipment (UE), a mobile phone, a wearable device, an Internet of Things device, a communication-capable automobile, a smart automobile, a tablet, a computer with wireless transceiver functionality, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical surgery, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, a wireless terminal device in a smart home, and the like, but is not limited thereto.

[0144] In some embodiments, the network device 102 can include at least one of an access network device and a core network device.

[0145] Optionally, the access network device is at least one of a node or device that accesses a terminal to a wireless network, and can include at least one of a base station in a 5G communication system, an evolved NodeB (eNB), a next generation eNB (ng-eNB), a next generation NodeB (gNB), a node B (NB), a home node B (HNB), a home evolved node B (HeNB), a wireless backhaul device, a radio network controller (RNC), a base station controller (BSC), a base transceiver station (BTS), a base band unit (BBU), a mobile switching center, a base station in a 6G communication system, an open base station (Open RAN), a cloud base station (Cloud RAN), a base station in other communication systems, an access node in a wireless fidelity (WiFi) system, and the like, but is not limited thereto.

[0146] Optionally, the access network device can be composed of a central unit (CU) and a distributed unit (DU), wherein the CU can also be referred to as a control unit. The CU-DU structure can split the protocol layers of the access network device, and the functions of part of the protocol layers are controlled by the CU, and the functions of the remaining part or all of the protocol layers are distributed in the DU and controlled by the CU. However, the present application is not limited to this.

[0147] Optionally, the core network device can be one device including one or more network elements, or can be multiple devices or device groups including all or part of the one or more network elements. The network element can be virtual or physical. The core network includes at least one of an evolved packet core (EPC), a 5G core network (5GCN), and a next-generation core (NGC), for example. Alternatively, the core network device refers to a network element with specific functions, such as an access management function (AMF) and a service management function (SMF).

[0148] In some embodiments, the A-IoT device 103 can also be referred to as an Ambient-IoT terminal or a passive device, or simply a device (Device). The A-IoT device 103 supports ambient power and is powered by energy harvesting, without a battery or with limited energy storage capability (for example, using a capacitor).

[0149] The A-IoT device 103 can have low memory, low processing power, low power, small data transmission, and mass deployment, and can be maintenance-free and have a long service life. For example, the service life of the A-IoT device 103 can be more than 10 years.

[0150] In some embodiments, the A-IoT device 103 has different power acquisition and storage capabilities according to different types and working modes. For example, the types of the A-IoT device 103 can include the following types:

[0151] Device 1 (Device1) or Device A: without energy storage, without independent signal generation or amplification function, the Device 1 can communicate in the backscattering mode.

[0152] Device 2a (Device2a) or Device B: with energy storage capability, without independent signal generation function, Device2a can communicate in a backscattering manner, and the stored energy can be used for signal amplification.

[0153] Device 2b (Device2b) or Device C: with energy storage capability, can independently generate signals, such as radio frequency (RF) components with active signal transmission.

[0154] In some embodiments, in order to support the data transmission of A-IoT devices 103, one or more of the following functions need to be supported in the network or communication system 100:

[0155] Energy source (Energy Source, ES) function: provide energy for A-IoT devices 103, which can be used for device 2a and device 2b;

[0156] Downlink transmission (Downlink Transmission, DT) function: trigger the uplink transmission of A-IoT devices 103 by sending indication information.

[0157] Continuous wave (Continuous Wave, CW) excitation function: provide electromagnetic waves required for backscattering for A-IoT devices 103, which can be used for device 1 and device 2a to realize uplink transmission through backscattering CW. CW is actually also an ES, and A-IoT devices 103 can receive CW and store energy.

[0158] Uplink receiver (Uplink Receiver, UR) function: receive the uplink information backscattered by A-IoT devices 103, or receive the uplink information actively transmitted by A-IoT devices 103.

[0159] Among them, the above functions can be realized by network devices 102, terminals 101 or repeaters, etc., for example, the terminal 101 can send CW. Among the above multiple functions, one device can realize multiple functions or all functions involved; or through multiple devices, each device realizes one function, and the network can coordinate the behavior of different devices.

[0160] In some embodiments, the communication between the A-IoT device 103 and the network device 102, such as the communication based on the two topologies of FIG. 1b or FIG. 1c, can use spectrum resources in three forms: In-Band, Guard Band, and Stand-alone. Among them, In-band is to use normal NR communication DL and / or UL spectrum resources, such as using the DL / UL communication (FIG. 1b) spectrum resources of the base station and other UEs, or the DL / UL communication (FIG. 1c) spectrum resources between the UE and the base station. Guard-band is to use the spectrum resources of the guard band of the normal NR communication DL and / or UL spectrum, and Stand alone is to use the spectrum resources unrelated to the NR communication.

[0161] In some embodiments, the number of devices or nodes in FIGS. 1a-1f is only illustrative, and in actual applications, each device or node can adopt multiple.

[0162] In some embodiments, the technical solutions of the present disclosure can be applied to the Open RAN architecture, at which time the interfaces between the access network devices or within the access network devices involved in the embodiments of the present disclosure can become internal interfaces of the Open RAN, and the processes and information interactions between these internal interfaces can be realized through software or programs.

[0163] It can be understood that the communication system described in the embodiments of the present disclosure is for more clearly illustrating the technical solutions of the embodiments of the present disclosure, and does not constitute a limitation on the technical solutions provided by the embodiments of the present disclosure. It can be known by those skilled in the art that, with the evolution of system architecture and the appearance of new business scenarios, the technical solutions provided by the embodiments of the present disclosure are also applicable to similar technical problems.

[0164] The following embodiments of the present disclosure can be applied to the communication system 100 shown in FIGS. 1a-1f, or part of the subject, but are not limited thereto.

[0165] The subjects shown in FIGS. 1a-1f are examples, and the communication system can include all or part of the subjects in FIGS. 1a-1f, or other subjects other than FIGS. 1a-1f. The number and form of each subject is arbitrary, the connection relationship between each subject is exemplary, each subject can be connected or not connected, and the connection can be in any way, can be direct connection or indirect connection, can be wired connection or wireless connection.

[0166] Embodiments of the present disclosure can be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G new radio (NR), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Future generation radio access (FX), Global System for Mobile communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (Bluetooth (registered trademark)), Public Land Mobile Network (PLMN) network, Device-to-Device (D2D) system, Machine to Machine (M2M) system, Internet of Things (IoT) system, Vehicle-to-Everything (V2X), system using other communication processing methods, next-generation system expanded based thereon, and the like. Further, a plurality of systems can be applied in combination (for example, combination of LTE or LTE-A and 5G, and the like).

[0167] Traditional Internet of Things (IoT) devices are usually powered by batteries with limited life. With the popularity of IoT networks and the large number of IoT devices, the problems of battery maintenance, battery recycling, battery replacement and the like of traditional IoT devices are increasingly serious. The batteries that cannot be successfully recycled will also have harmful effects on ecology and the environment. Based on this, environmentally friendly and safe battery-free communication has emerged. Battery-free communication can improve network performance and sustainability, expand application scenarios, and significantly reduce device size and cost.

[0168] To meet the growing demand in vertical domains, existing Low Power Wide Area (LPWA) technologies such as Machine Type Communication (MTC), Narrow Band Internet of Things (NB-IoT), Reduced Capability (RedCap), etc. can achieve low cost, low power consumption and large-scale connectivity. However, the following needs cannot be met: first, devices driven by traditional batteries are not suitable, for example, in extreme environmental conditions (e.g. high voltage, extremely high / low temperature, humid environment); second, maintenance-free devices are needed (e.g. without replacing the traditional batteries of the device); finally, ultra-low complexity, very small device size or form factor (e.g. thickness of mm), longer life cycle, etc. are needed. IoT that supports environmental power or environmental energy supply can meet the above needs.

[0169] Low-power IoT communication chips such as Bluetooth Low Energy (BLE), Long Range Radio (LoRa) or NB-IoT have a transmit-receive power consumption of tens of milliwatts or even hundreds of milliwatts. In combination with the description of the foregoing embodiments, the energy harvested from the environment is only in the order of microwatts. The energy harvested from the environment can drive the perception nodes such as A-IoT devices 103 to perform data transmission and wireless communication. Wireless communication technology is needed to reduce the communication energy consumption to tens of microwatts or even below ten microwatts.

[0170] Backscatter Communications is a modulation and transmission technology with extremely low power consumption based on the principle of backscattering of radio frequency signals, and is a means to realize the Internet of Everything. In backscatter communications, since part of the radio frequency signal such as electromagnetic wave will be reflected when reaching the surface of an object, the passive node such as A-IoT device 103 as a sending node adjusts the matching between the receiving antenna and the impedance according to the information to be sent, enhances the reflection of the incident radio frequency signal, and modulates the sensing data obtained by itself onto the reflected signal to complete the sending of data. Compared with other communication technologies, backscatter communications does not require complex radio frequency structure, reduces the use of power amplifiers, high-precision crystal oscillators, duplexers, high-precision filters and other devices, and also does not require complex baseband processing, so it can simplify the terminal design and greatly reduce the cost of terminal nodes.

[0171] In a wireless radio frequency identification (RFID) system applying backscatter communications, as shown in FIG. 1g, a receiver sends a radio frequency excitation signal to activate a passive node. The receiver can be a RFID reader, which can correspond to a network device 102, an intermediate node such as a terminal 101 or an auxiliary node 104 in the A-IoT system; the passive node can be a RFID electronic tag, which can correspond to an A-IoT device 103 in the A-IoT system. The electronic tag modulates its own information onto the radio frequency signal using backscatter communications, and the reader receives the reflected signal of the passive electronic tag and demodulates it to realize information transmission. The communication process of RFID has the following disadvantages: the wireless signal will experience double path fading, the path loss is large, the effective communication distance is short, and therefore the coverage distance is small; single channel transmission is required; the tag needs to be strictly aligned; there is no power control, etc. It is necessary to integrate 3GPP communication technology to improve the wireless communication performance of RFID technology in the passive Internet of Things.

[0172] In the RFID communication system, from the use of the function, divided into three types of command of Select, Inventory and Access. Among them: Select command includes: Select command and Challenge command. Inventory command includes: Query command, Query Adjust command, Query Rep command, ACK command, NAK command. Access command includes: Req_RN command, Read command, Write command, Kill command, Lock command; optionally, also can include: Access command, BlockWrite command, BlockErase command.

[0173] Among them, the command application instance in Inventory and Access can include:

[0174] (1) after the tag receives the valid Query command, each tag that meets the set standard is selected to generate a random number. Each tag with a random number of zero will produce a response, such as sending back a temporary password RN16, RN16 is a 16-bit random number, and transfer to the Reply state; other tags can change some attributes and flags, exit the group of tags with zero, which is conducive to reducing repeated identification.

[0175] (2) after the tag receives the valid QueryAdjust command, each tag respectively generates a new random number, and the other behaviors are the same as Query command.

[0176] (3) after the tag receives the valid QueryRep command, the original random number of each tag in the tag group is reduced by one, and the other behaviors are the same as Query command.

[0177] (4) only the single tag can receive the valid ACK command, after receiving, according to the Electronic Product Code (EPC) communication protocol, the content in the EPC area is sent back. Among them, ACK command can use the above RN16 or Handle, Handle is a 16-bit random number temporarily representing the identity of the tag.

[0178] (5) after the tag receives the valid NAK command, the tag in the Ready state and the Killed state keeps the original state, and the tag in other states all transfer to the Arbitrate state.

[0179] For the A-IoT device 103, it needs to collect the radio wave transmitted by the network node to obtain energy to drive itself to work. Therefore, before obtaining energy, the A-IoT device 103 is usually in the "shutdown" state or off-network state. Therefore, the communication system needs to support a data communication mode with shorter transmission duration, lower memory consumption, and more convenient terminal management to complete the data communication process as soon as possible, such as the above-mentioned backscatter technology.

[0180] In the A-IoT system, in the topological scenarios corresponding to FIG. 1a or FIG. 1c, the terminal 101 can act as an intermediate node or a Reader and forward the A-IOT data transmission and sending operation. However, in the related protocol, the terminal 101 can enter the RRC_IDLE state when there is no data transmission and reception on the Uu interface, such as entering the RRC_IDLE state when the data inactivity timer defined or configured by the configuration expires. The terminal 101 in the RRC_IDLE state will affect the A-IOT communication process.

[0181] FIG. 2 is an interaction diagram of a communication method according to an embodiment of the present disclosure. As shown in FIG. 2, the embodiment of the present disclosure relates to a communication method, and the method comprises:

[0182] In step S2101, the network device 102 sends configuration information to the terminal 101.

[0183] In some embodiments, the network device 102 can be a base station (BS), for example. The terminal 101 can be a UE, for example.

[0184] In some embodiments, the configuration information is used to configure the terminal 101 as an intermediate node or a Reader of the A-IOT system. In combination with FIG. 1a or 1c, when the terminal 101 acts as an intermediate node or a Reader, it can forward A-IOT data or signaling.

[0185] In some embodiments, the network device 102 and the terminal 101 can perform Uu interface communication.

[0186] In some embodiments, the terminal 101 receives the configuration information.

[0187] Optionally, regardless of whether there is data transmission on the Uu interface, the terminal 101 can refer to the behavior of step S2102 after receiving the configuration information.

[0188] In step S2102, the terminal 101 remains in the RRC connected state.

[0189] In some embodiments, the terminal 101 needs to be kept in the RRC connected state when the terminal 101 is configured as an intermediate node of the ambient Internet of Things (A-IOT) system, for example, the terminal 101 is kept in the RRC connected state during the period when the terminal 101 is configured as an intermediate node.

[0190] In some embodiments, the terminal 101 can be configured or not configured with a first timer by the network device 102. The first timer may, for example, include a data inactivity timer dataInactivityTimer. In the following embodiments, the dataInactivityTimer is taken as an example.

[0191] In a first implementation, the terminal 101 is not configured with the data inactivity timer when the terminal 101 is configured as an intermediate node.

[0192] In this implementation, the data inactivity timer dataInactivityTimer is configured when the terminal 101 is not configured as an intermediate node.

[0193] In this implementation, the information element (IE) of the data inactivity timer dataInactivityTimer is configured differently from the configuration related to the terminal 101 as an intermediate node. In other words, the IE of the data inactivity timer dataInactivityTimer can only be configured when the terminal 101 is not configured as an intermediate node. Thus, in this implementation, when the terminal 101 forwards data or signaling of A-IOT as an intermediate node, the terminal 101 will not enter the RRC idle state due to the influence of the data inactivity timer dataInactivityTimer, and can be kept in the RRC connected state.

[0194] In a second implementation, the terminal 101 is configured with the data inactivity timer dataInactivityTimer, but the operation rules or control of the inactivity timer are different from the related protocol.

[0195] In this implementation, the following examples can be referred to for description:

[0196] In a first example, the method can further include starting or restarting the data inactivity timer when the terminal 101 receives or transmits A-IOT information, for example, starting or restarting the data inactivity timer when the first MAC entity of the terminal 101 receives or transmits A-IOT information.

[0197] Wherein, the terminal 101 is in RRC connected state during the running of the data inactivity timer. In the implementation of step S2102, the terminal 101 can keep the data inactivity timer running by restarting the timer, so as to keep in the RRC connected state.

[0198] In this example, the first MAC entity is used for communication with the A-IOT device 103, which can also be referred to as an IOT MAC entity. For the terminal 101 supporting A-IOT, the MAC layer of the terminal 101 can include a first MAC entity for communication with the A-IOT device 103, and a second MAC entity for communication with the network device 102. The second MAC entity can communicate with the upper layer (such as the RRC layer) of the terminal 101.

[0199] In this example, receiving or transmitting A-IOT information includes at least one of the following:

[0200] The terminal 101 receives the first command sent by the A-IOT device 103, such as the first MAC entity receiving the first command.

[0201] The terminal 101 sends a second command to the A-IOT device 103, such as the first MAC entity receiving the second command.

[0202] The terminal 101 sends a continuous electromagnetic wave (CW) to the A-IOT device 103.

[0203] Wherein, the A-IOT information can include A-IOT data or signaling. The first command is, for example, a Device to Reader (D2R) command, i.e., a command sent by the A-IOT device 103 to the terminal 101. The second command is, for example, a R2D command, i.e., a command sent by the terminal 101 to the A-IOT device 103. The CW can be used in backscattering communication and can be provided by the terminal 101 or other devices for the A-IOT device 103.

[0204] In this example, when the above conditions are met, the terminal 101 can restart the data inactivity timer, so as to keep in the RRC connected state and not enter the RRC idle state due to the expiration of the timer.

[0205] In this example, for the data inactivity monitoring function:

[0206] When in the RRC connected state, the terminal 101 (UE) can be configured with the data inactivity monitoring function by the RRC. The RRC controls the data inactivity operation by configuring the timer dataInactivityTimer.

[0207] When the dataInactivityTimer is configured, the terminal 101 shall:

[0208] 1> if any MAC entity receives a MAC Service Data Unit (SDU) of a Dedicated Transmission Channel (DTCH) logical channel, a Dedicated Control Channel (DCCH) logical channel, a common control channel (CCCH) logical channel or a multicast MTCH logical channel; or

[0209] 1> if any MAC entity transmits a MAC SDU of a DTCH logical channel or a DCCH logical channel; or

[0210] 1> if any IOT MAC entity transmits a R2D message or receives a D2R message:

[0211] 2> start or restart the dataInactivityTimer.

[0212] 1> if the dataInactivityTimer expires:

[0213] 2> indicate the expiration of the dataInactivityTimer to upper layers.

[0214] In the second example, the method can further include: when the terminal 101 is configured as an intermediate node, and in the case where the first timer is configured, the terminal 101 does not start the data inactivity timer, for example, the MAC layer of the terminal 101 does not start the timer, or the second MAC entity does not start the timer.

[0215] Wherein, the data inactivity timer is started when the terminal 101 is not configured as an intermediate node, and the second MAC entity is used for communication with the network device 102.

[0216] In the example, in the implementation process of step S2102, when the terminal 101 is configured as an intermediate node and is configured with the dataInactivityTimer, the MAC layer, such as the second MAC entity, can not start or cannot start the running of the timer, so that the terminal 101 is not affected by the timer and remains in the RRC connected state.

[0217] In this example, the terminal 101 starts the dataInactivityTimer only if it is not configured as an intermediate node or a Reader; if it is configured as an intermediate node or a Reader, the MAC layer of the terminal 101 cannot start the dataInactivityTimer.

[0218] In this example, for the data inactivity monitoring function:

[0219] When in RRC connected state, the terminal 101 (UE) can be configured by RRC with the data inactivity monitoring function. The RRC controls the data inactivity operation by configuring the timer dataInactivityTimer.

[0220] When the dataInactivityTimer is configured, the terminal 101 shall:

[0221] 1> if any MAC entity receives a MAC SDU on a DTCH logical channel, a DCCH logical channel, a CCCH logical channel or a multicast MTCH logical channel, and the UE is not configured as a UE Reader; or

[0222] 1> if any MAC entity transmits a MAC SDU on a DTCH logical channel or a DCCH logical channel, and the UE is not configured as a UE Reader:

[0223] 2> start or restart the dataInactivityTimer.

[0224] 1> if the dataInactivityTimer expires:

[0225] 2> indicate to the upper layers that the dataInactivityTimer has expired.

[0226] In other examples, the status of the first timer can also be determined according to the indication information of the upper layer.

[0227] Optionally, the indication information comprises at least one of:

[0228] receiving a stop indication information; receiving a do not start indication information; not receiving a start indication information.

[0229] Optionally, determining the status of the first timer comprises: stopping running the first timer; or, not starting the first timer.

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

[0231] The stop indication information is not received; the non-start indication information is not received; and the start indication information is received.

[0232] Optionally, determining the state of the first timer comprises starting the first timer.

[0233] For example, the following third and fourth examples can be referred to:

[0234] In the third example, the method can further comprise: the MAC layer of the terminal 101 receiving indication information from a high layer of the terminal, and determining the state of the data inactivity timer according to the indication information. Wherein, the terminal is configured with the first timer. Wherein, the terminal 101 can receive the indication information from the high layer RRC layer through the second MAC entity.

[0235] In this example, if the indication information is used to indicate to stop running the data inactivity timer, i.e., the indication information is a stop indication, then:

[0236] When the MAC layer of the terminal 101, such as the second MAC entity, receives the indication information sent by the RRC layer of the terminal 101, the running of the data inactivity timer is stopped. Wherein, if the DataInactivityTimer is running, and the second MAC entity of the terminal 101 receives the indication information (or stop indication) from the high layer (RRC), the running of the timer can be stopped; if the DataInactivityTimer has not yet run, and the second MAC entity of the terminal 101 receives the stop indication from the high layer, the MAC of the terminal 101 cannot start the DataInactivityTimer. Thus, the terminal 101 can not be limited by the timer and remain in the RRC connected state during the implementation of step S2102. Wherein, the above stop indication can be sent in the A-IOT communication scenario.

[0237] Alternatively, when the second MAC entity does not receive the indication information, the data inactivity timer is started. Wherein, the second MAC entity can normally run the DataInactivityTimer when it does not receive the indication information, and the terminal 101 can enter the RRC idle state at an appropriate time. Wherein, when the terminal 101 does not need to forward A-IOT data, the RRC layer can not send the above stop indication.

[0238] In this example, for the data inactivity monitoring function:

[0239] When in RRC CONNECTED state, the terminal 101 (UE) can be configured by RRC with data inactivity monitoring function. The RRC controls the data inactivity operation by configuring a timer dataInactivityTimer.

[0240] When dataInactivityTimer is configured, the terminal 101 shall:

[0241] 1> if any MAC entity receives a MAC SDU on a DTCH logical channel, a DCCH logical channel, a CCCH logical channel or a multicast MTCH logical channel and has not received a dataInactivityTimer stop indication from upper layers; or

[0242] 1> if any MAC entity transmits a MAC SDU on a DTCH logical channel or a DCCH logical channel and has not received a dataInactivityTimer stop indication from upper layers:

[0243] 2> start or restart the dataInactivityTimer.

[0244] 1> if any MAC entity receives a dataInactivityTimer stop indication from upper layers;

[0245] 2> stop the dataInactivityTimer, if running.

[0246] 1> if the dataInactivityTimer expires:

[0247] 2> indicate the expiry of the dataInactivityTimer to upper layers.

[0248] In a fourth example, the method can further include: determining, by the MAC layer of the terminal 101, the state of the data inactivity timer according to the indication information of the upper layers.

[0249] In this example, if the indication information is used to indicate not to start the data inactivity timer, i.e. the indication information is a not start indication, then:

[0250] When the MAC layer, such as the second MAC entity, receives the indication information sent by the RRC layer, the data inactivity timer is not started or cannot be started. For example, if the MAC layer receives an indication that the timer DataInactivityTimer is not started, the MAC of the terminal 101 cannot start the timer DataInactivityTimer at this time. Thus, the terminal 101 can not be limited by the timer and remain in the RRC connected state during the implementation of step S2102. The above-mentioned not-starting indication can be sent in the A-IOT communication scenario.

[0251] Alternatively, when the second MAC entity does not receive the indication information, the data inactivity timer is started. For example, if the MAC layer does not receive an indication that the timer DataInactivityTimer is not started, the timer DataInactivityTimer can be started at this time, and the terminal 101 can enter the RRC idle state at an appropriate time. Where the terminal 101 does not need to forward A-IOT data, the RRC layer can not send the above-mentioned not-starting indication.

[0252] In this example, if the indication information is used to indicate that the data inactivity timer is started, i.e., the indication information is a start indication, then:

[0253] When the MAC layer, such as the second MAC entity, receives the indication information sent by the RRC layer, the data inactivity timer is started. Where if the MAC layer receives an indication that the timer DataInactivityTimer is started, the timer DataInactivityTimer can be started at this time, and the terminal 101 can enter the RRC idle state at an appropriate time. Where the terminal 101 does not need to forward A-IOT data, the RRC layer can send the above-mentioned start indication.

[0254] Alternatively, when the second MAC entity does not receive the indication information, the data inactivity timer is not started or cannot be started. Where if the MAC layer does not receive an indication that the timer DataInactivityTimer is started, the MAC of the terminal 101 cannot start the timer DataInactivityTimer at this time. If the timer is not started, the terminal 101 can not be limited by the timer and remain in the RRC connected state during the implementation of step S2102. Where the above-mentioned start indication can not be sent in the A-IOT communication scenario.

[0255] In this example, for the data inactivity monitoring function:

[0256] When in RRC connected state, the terminal 101 (UE) can be configured by RRC with data inactivity monitoring function. The RRC controls the data inactivity operation by configuring a timer dataInactivityTimer.

[0257] When dataInactivityTimer is configured, the terminal 101 shall:

[0258] 1> if any MAC entity receives a MAC SDU on a DTCH logical channel, a DCCH logical channel, a CCCH logical channel or a multicast MTCH logical channel and has not received an indication from upper layers not to start the dataInactivityTimer:

[0259] 1> if any MAC entity transmits a MAC SDU on a DTCH logical channel or a DCCH logical channel and has not received an indication from upper layers not to start the dataInactivityTimer:

[0260] 2> start or restart the dataInactivityTimer.

[0261] 1> if the dataInactivityTimer expires:

[0262] 2> indicate the expiry of the dataInactivityTimer to upper layers.

[0263] In the fifth example, during the implementation of step S2102, it can include: when the data inactivity timer expires, the RRC layer of the terminal 101 controls the terminal to remain in the RRC connected state and not enter the RRC idle state.

[0264] Wherein, the data inactivity timer DataInactivityTimer expires, i.e. ends or expires.

[0265] In this example, the MAC layer, such as the second MAC entity, can normally run the DataInactivityTimer and can report the expiry of the timer to the RRC layer. The RRC layer of the terminal 101 can be used to control whether the terminal 101 enters the RRC idle state. In this example, even if the timer expires, when the terminal 101 is configured as an intermediate node, the RRC layer can keep the terminal 101 in the RRC connected state and ignore the expiry indication reported by the MAC layer.

[0266] Alternatively, the method comprises: when the terminal 101 is not configured as an intermediate node, the terminal 101 enters the RRC idle state after the data inactivity timer expires.

[0267] In this example, if the terminal 101 is not configured as an intermediate node or Reader, it can enter the idle state after the timer DataInactivityTimer expires; otherwise, even if the timer DataInactivityTimer expires, the terminal 101 will not enter the idle state.

[0268] In this example, for UE actions when DataInactivityTimer expires:

[0269] When receiving DataInactiviyTimer expires from lower layers in the RRC connected state, the terminal 101 (UE) should:

[0270] 1> If the terminal 101 is not configured as a UE Reader,

[0271] 2> Perform the operation of entering the RRC idle state, and release the reason as “RRC connection failure”.

[0272] Step S2103, the network device 102 sends A-IOT data or signaling to the terminal 101.

[0273] In some embodiments, the terminal 101 can receive A-IOT data or signaling sent by the network device 102 as an intermediate node.

[0274] Step S2104, the terminal 101 sends A-IOT data or signaling to the A-IOT device 103.

[0275] In some embodiments, the terminal 101 can forward A-IOT data or signaling to the A-IOT device 103 as an intermediate node.

[0276] In some embodiments, the names of information, etc. are not limited to the names described in the embodiments, and the terms “signal”, “message”, “signaling”, “report”, “configuration”, “indication”, “instruction”, “command”, “channel”, “parameter”, “domain”, “field”, etc. can be replaced with each other.

[0277] In some embodiments, “acquire”, “obtain”, “get”, “receive”, “transmit”, “bidirectionally transmit”, “send and / or receive” can be replaced by each other, which can be interpreted as receiving from other subjects, acquiring from protocols, acquiring from higher layers, obtaining by self-processing, implementing autonomously, and various meanings.

[0278] In some embodiments, the terms “send”, “transmit”, “report”, “issue”, “transmit”, “bidirectionally transmit”, “send and / or receive” can be replaced by each other.

[0279] In some embodiments, the terms “radio”, “wireless”, “radio access network (RAN)”, “access network (AN)”, “RAN-based” and the like can be replaced by each other.

[0280] In some embodiments, the terms “time”, “time point”, “time point”, “time position” and the like can be replaced by each other, and the terms “time length”, “time period”, “time window”, “window”, “time” and the like can be replaced by each other.

[0281] In some embodiments, the terms “certain”, “preseted”, “preset”, “set”, “indicated”, “certain”, “arbitrary”, “first” and the like can be replaced by each other, and “certain A”, “preset A”, “preset A”, “set A”, “indicated A”, “certain A”, “arbitrary A”, “first A” can be interpreted as A specified in advance in protocols and the like, or A obtained by setting, configuring, or indicating, or A specified as certain A, certain A, arbitrary A, or first A, but not limited thereto.

[0282] The method related to the embodiments of the present disclosure can include at least one of steps S2101-S2104.

[0283] In some embodiments, step S2101 is optional, and in different embodiments, one or more steps can be replaced.

[0284] In some embodiments, step S2102 or S2103 is optional, and in different embodiments, one or more steps can be replaced.

[0285] In some embodiments, other optional implementations described before or after the corresponding description of FIG. 2 can be referred to.

[0286] In the embodiments of the present disclosure, the terminal 101 can remain in the RRC_CONNECTED state regardless of whether the Uu port transmits data when the terminal 101 is configured as an intermediate node or a reader, so that the terminal 101 normally performs the role of the reader and completes the ambient IOT task.

[0287] FIG. 3a is a flow diagram illustrating a communication method according to an embodiment of the present disclosure. As shown in FIG. 3a, the present embodiment relates to a communication method, which is performed by the terminal 101, and the above method comprises the following steps:

[0288] In step S3101, configuration information is received.

[0289] In some embodiments, the implementation of step S3101 can refer to the implementation of step S2101 in FIG. 2, which will not be repeated here.

[0290] In step S3102, the terminal remains in the RRC_CONNECTED state.

[0291] In some embodiments, the implementation of step S3102 can refer to the implementation of step S2102 in FIG. 2, which will not be repeated here.

[0292] In step S3103, A-IOT data or signaling transmitted by the network device 102 is received.

[0293] In some embodiments, the implementation of step S3103 can refer to the implementation of step S2103 in FIG. 2, which will not be repeated here.

[0294] In step S3104, A-IOT data or signaling is transmitted to the A-IOT device 103.

[0295] In some embodiments, the implementation of step S3104 can refer to the implementation of step S2104 in FIG. 2, which will not be repeated here.

[0296] The method related to the embodiments of the present disclosure can include at least one of steps S3101-S3104.

[0297] In some embodiments, other optional implementations can be described before or after the description corresponding to FIG. 3a.

[0298] FIG. 3b is a flow diagram illustrating a communication method according to an embodiment of the present disclosure. As shown in FIG. 3b, the present embodiment relates to a communication method, which is performed by the terminal 101, and the above method comprises the following steps:

[0299] In step S3201, the terminal remains in the RRC_CONNECTED state when the terminal is configured as an intermediate node of an A-IOT system.

[0300] In some embodiments, the implementation of step S3201 can refer to the implementation of step S2102 in FIG. 2, which will not be repeated here.

[0301] In some embodiments, other optional implementations can be referred to before or after the description corresponding to FIG. 3b.

[0302] FIG. 4a is a flow diagram illustrating a communication method according to an embodiment of the present disclosure. As shown in FIG. 4a, the embodiment of the present disclosure relates to a communication method, which is performed by the network device 102, and the above method comprises:

[0303] In step S4101, configuration information is sent.

[0304] In some embodiments, the implementation of step S4101 can refer to the implementation of step S2101 in FIG. 2, which will not be repeated here.

[0305] In step S4102, A-IOT data or signaling is sent.

[0306] In some embodiments, the implementation of step S4102 can refer to the implementation of step S2103 in FIG. 2, which will not be repeated here.

[0307] The method related to the embodiment of the present disclosure can comprise at least one of steps S4101-S4102.

[0308] In some embodiments, other optional implementations can be referred to before or after the description corresponding to FIG. 4a.

[0309] FIG. 4b is a flow diagram illustrating a communication method according to an embodiment of the present disclosure. As shown in FIG. 4b, the embodiment of the present disclosure relates to a communication method, which is performed by the network device 102, and the above method comprises:

[0310] In step S4201, configuration information is sent.

[0311] In some embodiments, the implementation of step S4201 can refer to the implementation of step S2101 in FIG. 2, which will not be repeated here.

[0312] In some embodiments, other optional implementations can be referred to before or after the description corresponding to FIG. 4b.

[0313] In the embodiment of the present disclosure, when the UE is configured as a reader, it can remain in the RRC_CONNECTED state regardless of whether the Uu port transmits data, so that the UE normally performs the role of the reader and completes the ambient IOT task. In order to facilitate the understanding of the embodiment of the present disclosure, some examples are listed below:

[0314] Embodiment 1:

[0315] IE DataInactivityTimer and UEreader related configuration are not configured simultaneously, or IE DataInactivityTimer can be configured only when UE is not configured as UEreader.

[0316] In this embodiment, -DataInactivityTimer and UEreader are not configured simultaneously.

[0317] Embodiment 2:

[0318] Embodiment 2 can include the following multiple options:

[0319] Option 1:

[0320] If IOT MAC receives D2R command or sends R2D command, restart the timer DataInactivityTimer. Or

[0321] If IOT MAC receives D2R command or sends R2D command or sends CW, restart the timer DataInactivityTimer.

[0322] For data inactivity monitoring function:

[0323] When in RRC connected state, UE can be configured with data inactivity monitoring function by RRC. RRC controls data inactivity operation by configuring timer dataInactivityTimer.

[0324] When dataInactivityTimer is configured, UE shall:

[0325] 1> if any MAC entity receives a MAC SDU for a DTCH logical channel, a DCCH logical channel, a CCCH logical channel or a multicast MTCH logical channel; or

[0326] 1> if any MAC entity transmits a MAC SDU for a DTCH logical channel or a DCCH logical channel; or

[0327] 1> if any IOT MAC entity transmits R2D message or receives D2R message:

[0328] 2> start or restart the dataInactivityTimer.

[0329] 1> if the dataInactivityTimer expires:

[0330] 2> indicate to upper layers that the dataInactivityTimer has expired.

[0331] Option 2:

[0332] If the UE is not configured as a UE reader, the timer DataInactivityTimer can be started at this point, if configured as a UE reader, the UE's MAC cannot start the timer DataInactivityTimer at this point.

[0333] For data inactivity monitoring function:

[0334] When in RRC connected state, the UE can be configured by RRC with the data inactivity monitoring function. RRC controls the data inactivity operation by configuring the timer dataInactivityTimer.

[0335] When dataInactivityTimer is configured, the UE shall:

[0336] 1> if any MAC entity receives a MAC SDU for a DTCH logical channel, a DCCH logical channel, a CCCH logical channel or a multicast MTCH logical channel, and the UE is not configured as a UE Reader; or

[0337] 1> if any MAC entity transmits a MAC SDU for a DTCH logical channel or a DCCH logical channel, and the UE is not configured as a UE Reader:

[0338] 2> start or restart the dataInactivityTimer.

[0339] 1> if the dataInactivityTimer expires:

[0340] 2> indicate to upper layers that the dataInactivityTimer has expired.

[0341] Option 3:

[0342] If the UE receives a dataInactivityTimer stop indication from upper layers (RRC), the UE shall stop the timer dataInactivityTimer, if running.

[0343] The timer dataInactivityTimer can only be started if the MAC does not receive a dataInactivityTimer stop indication. If the MAC receives a dataInactivityTimer stop indication, the UE's MAC cannot start the timer dataInactivityTimer.

[0344] For the data inactivity monitoring function:

[0345] When in RRC CONNECTED state, the UE can be configured by RRC with the data inactivity monitoring function. RRC controls the data inactivity operation by configuring the timer dataInactivityTimer.

[0346] When dataInactivityTimer is configured, the UE shall:

[0347] 1> if any MAC entity receives a MAC SDU on a DTCH logical channel, DCCH logical channel, CCCH logical channel or multicast MTCH logical channel and has not received a dataInactivityTimer stop indication from upper layers; or

[0348] 1> if any MAC entity transmits a MAC SDU on a DTCH logical channel or DCCH logical channel and has not received a dataInactivityTimer stop indication from upper layers:

[0349] 2> start or restart dataInactivityTimer.

[0350] 1> if any MAC entity receives a dataInactivityTimer stop indication from upper layers;

[0351] 2> stop dataInactivityTimer, if running.

[0352] 1> if dataInactivityTimer expires:

[0353] 2> indicate dataInactivityTimer expiry to upper layers.

[0354] Option 4:

[0355] If the MAC does not receive a timer DataInactivityTimer not start indication, the timer DataInactivityTimer can be started at this time, if the MAC receives a timer DataInactivityTimer not start indication, the UE's MAC cannot start the timer DataInactivityTimer. Or

[0356] If the MAC receives a timer DataInactivityTimer start indication, the timer DataInactivityTimer can be started at this time, if the MAC does not receive a timer DataInactivityTime start indication, the UE's MAC cannot start the timer DataInactivityTimer.

[0357] For data inactivity monitoring function:

[0358] When in RRC connected state, the UE can be configured with data inactivity monitoring function by RRC. RRC controls the data inactivity operation by configuring the timer dataInactivityTimer.

[0359] When dataInactivityTimer is configured, the UE shall:

[0360] 1> if any MAC entity receives a MAC SDU for a DTCH logical channel, a DCCH logical channel, a CCCH logical channel or a multicast MTCH logical channel and does not receive a dataInactivityTimer not start indication from upper layers; or

[0361] 1> if any MAC entity transmits a MAC SDU for a DTCH logical channel or a DCCH logical channel and does not receive a dataInactivityTimer not start indication from upper layers:

[0362] 2> start or restart the dataInactivityTimer.

[0363] 1> if the dataInactivityTimer expires:

[0364] 2> indicate to upper layers that the dataInactivityTimer has expired.

[0365] In this embodiment, the rule for starting or restarting the DataInactivityTimer is increased, for example, the DataInactivityTimer is restarted when there is R2D transmission or D2R reception in the IOT MAC. Alternatively, the DataInactivityTimer is started only when there is no UE reader configured or a high layer indication that the timer DataInactivityTimer can be started or cannot be started.

[0366] Embodiment 3

[0367] If the UE is not configured as a reader, the UE can enter the idle state after the timer DataInactivityTimer expires, otherwise the UE cannot enter the idle state after the timer DataInactivityTimer expires.

[0368] UE actions when the DataInactivityTimer expires:

[0369] When the DataInactivityTimer expires is received from the lower layers in the RRC connected state, the UE shall:

[0370] 1> if the UE is not configured as a UE Reader,

[0371] 2> perform the actions to enter the RRC idle state with release cause "RRC connection failure".

[0372] In the embodiments of the present disclosure, it is illustrated how the UE reader controls the timer DataInactivityTimer to control whether the UE can enter the idle state.

[0373] The embodiments of the present disclosure also propose a device for implementing any of the above methods, for example, a device comprising units or modules for implementing each step performed by the terminal in any of the above methods. For another example, another device is proposed, comprising units or modules for implementing each step performed by the network equipment (such as access network equipment, core network function node, core network equipment, etc.) in any of the above methods.

[0374] It should be understood that the division of each unit or module in the above apparatus is only a logical function division, and all or part of them can be integrated into a physical entity or physically separated in actual implementation. In addition, the units or modules in the apparatus can be implemented in the form of processor calling software: for example, the apparatus includes a processor, the processor is connected with a memory, the memory stores instructions, and the processor calls the instructions stored in the memory to realize any of the above methods or realize the functions of each unit or module of the above apparatus, wherein the processor is a general processor such as a central processing unit (CPU) or a microprocessor, and the memory is a memory in the apparatus or a memory outside the apparatus. Alternatively, the units or modules in the apparatus can be implemented in the form of hardware circuit, and the functions of part or all of the units or modules can be realized by the design of hardware circuit. The above hardware circuit can be understood as one or more processors; for example, in one implementation, the above hardware circuit is an application-specific integrated circuit (ASIC), and the functions of part or all of the units or modules are realized by the design of the logical relationship of elements in the circuit; for another example, in another implementation, the above hardware circuit is a programmable logic device (PLD), and a field programmable gate array (FPGA) is taken as an example, which can include a large number of logic gate circuits, and the connection relationship between the logic gate circuits is configured by a configuration file, so as to realize the functions of part or all of the units or modules. All units or modules of the above apparatus can be all implemented in the form of processor calling software, or all implemented in the form of hardware circuit, or part implemented in the form of processor calling software and the remaining part implemented in the form of hardware circuit.

[0375] In the embodiments of the present disclosure, the processor is a circuit with signal processing capability. In one implementation, the processor can be a circuit with instruction reading and running capability, such as a central processing unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), a digital signal processor (DSP), or the like. In another implementation, the processor can implement certain functions through a logical relationship of hardware circuits, and the logical relationship of the hardware circuits is fixed or reconfigurable. For example, the processor is a hardware circuit implemented by an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In the reconfigurable hardware circuit, the processor loads a configuration document to implement the configuration of the hardware circuit. It can be understood that the processor loads instructions to implement the functions of the above part or all units or modules. In addition, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a neural network processing unit (NPU), a tensor processing unit (TPU), a deep learning processing unit (DPU), and the like.

[0376] FIG. 5a is a structural schematic diagram of a terminal according to an embodiment of the present disclosure. As shown in FIG. 5a, the terminal 5100 can include at least one of a transceiver module 5101, a processing module 5102, and the like. In some embodiments, the processing module 5102 is configured to maintain a radio resource control (RRC) connected state when the terminal is configured as an intermediate node of an ambient Internet of Things (A-IoT) system.

[0377] Optionally, the transceiver module 5101 is configured to perform at least one of the communication steps, such as transmitting and / or receiving, performed by the terminal 101 in any of the above methods, which will not be described herein. Optionally, the processing module 5102 is configured to perform at least one of the other steps performed by the terminal 101 in any of the above methods, which will not be described herein.

[0378] FIG. 5b is a structural schematic diagram of a network device according to an embodiment of the present disclosure. As shown in FIG. 5b, the network device 5200 can include at least one of a transceiver module 5201, a processing module 5202, and the like. In some embodiments, the transceiver module 5201 is configured to send configuration information to a terminal, where the configuration information is used to configure the terminal as an intermediate node of an ambient Internet of Things (A-IoT) system, and the terminal is in an RRC connected state when the terminal is configured as the intermediate node.

[0379] Optionally, the transceiver module 5201 is configured to perform at least one of the communication steps, such as sending and / or receiving, performed by the network device in any of the above methods, which will not be repeated here. Optionally, the processing module 5202 is configured to perform at least one of the other steps performed by the network device 102 in any of the above methods, which will not be repeated here.

[0380] In some embodiments, the transceiver module can include a sending module and / or a receiving module, which can be separate or integrated together. Optionally, the transceiver module can be mutually replaced with a transceiver.

[0381] In some embodiments, the processing module can be a module or can include multiple sub-modules. Optionally, the multiple sub-modules perform all or part of the steps required to be performed by the processing module. Optionally, the processing module can be mutually replaced with a processor.

[0382] FIG. 6a is a structural schematic diagram of a communication device 6100 according to an embodiment of the present disclosure. The communication device 6100 can be a network device (such as an access network device, a core network device, etc.), a terminal (such as a user equipment, etc.), a chip, a chip system, or a processor supporting the network device to implement any of the above methods, or a chip, a chip system, or a processor supporting the terminal to implement any of the above methods. The communication device 6100 can be used to implement the methods described in the above method embodiments, and specific implementation can be referred to the descriptions in the above method embodiments.

[0383] As shown in FIG. 6a, the communication device 6100 includes one or more processors 6101. The processor 6101 can be a general-purpose processor or a special-purpose processor, etc., such as a baseband processor or a central processing unit. The baseband processor can be configured to process communication protocols and communication data, and the central processing unit can be configured to control a communication device (such as a base station, a baseband chip, a terminal device, a terminal device chip, a DU or a CU, etc.), execute a program, and process data of the program. Optionally, the communication device 6100 is configured to implement any of the above methods. Optionally, the one or more processors 6101 are configured to invoke instructions to cause the communication device 6100 to implement any of the above methods.

[0384] In some embodiments, the communication device 6100 further includes one or more transceivers 6102. When the communication device 6100 includes one or more transceivers 6102, the transceiver 6102 performs at least one of the communication steps of sending and / or receiving in the above-described methods, and the processor 6101 performs at least one of the other steps. In alternative embodiments, the transceiver can include a receiver and / or a transmitter, which can be separate or integrated together. Alternatively, the terms transceiver, transceiving unit, transceiver, transceiving circuit, interface circuit, interface, etc. can be replaced by each other, the terms transmitter, transmitting unit, transmitter, transmitting circuit, etc. can be replaced by each other, and the terms receiver, receiving unit, receiver, receiving circuit, etc. can be replaced by each other.

[0385] In some embodiments, the communication device 6100 further includes one or more memories 6103 for storing data. Alternatively, all or part of the memory 6103 can also be outside the communication device 6100. In alternative embodiments, the communication device 6100 can include one or more interface circuits 6104. Alternatively, the interface circuit 6104 is connected with the memory 6103, and the interface circuit 6104 can be used to receive data from the memory 6103 or other devices, and can be used to send data to the memory 6103 or other devices. For example, the interface circuit 6104 can read the data stored in the memory 6103 and send the data to the processor 6101.

[0386] The communication device 6100 described in the above embodiments can be a network device or a terminal, but the scope of the communication device 6100 described in the present disclosure is not limited thereto, and the structure of the communication device 6100 can not be limited by Figure 6a. The communication device can be a standalone device or can be part of a larger device. For example, the communication device can be: 1) a standalone integrated circuit (IC), or a chip, or a chip system or subsystem; (2) a set of one or more ICs, which can optionally include storage components for storing data, programs; (3) an ASIC, such as a Modem; (4) a module that can be embedded in other devices; (5) a receiver, a terminal device, a smart terminal device, a cellular phone, a wireless device, a handset, a mobile unit, a vehicle-mounted device, a network device, a cloud device, an artificial intelligence device, etc.; (6) others, etc.

[0387] Figure 6b is a structural schematic diagram of a chip 6200 according to an embodiment of the present disclosure. For the case where the communication device 6100 is a chip or a chip system, the structural schematic diagram of the chip 6200 shown in Figure 6b can be referred to, but is not limited thereto.

[0388] The chip 6200 includes one or more processors 6201. The chip 6200 is configured to execute any of the above methods.

[0389] In some embodiments, chip 6200 further includes one or more interface circuits 6202. Optionally, the terms interface circuit, interface, transceiver pin, and the like can be substituted for one another. In some embodiments, chip 6200 further includes one or more memories 6203 for storing data. Optionally, all or part of memory 6203 can be external to chip 6200. Optionally, interface circuit 6202 is connected to memory 6203, and interface circuit 6202 can be used to receive data from memory 6203 or other devices, and interface circuit 6202 can be used to send data to memory 6203 or other devices. For example, interface circuit 6202 can read data stored in memory 6203 and send the data to processor 6201.

[0390] In some embodiments, interface circuit 6202 performs at least one of the communication steps of sending and / or receiving in the above-described methods. The performance of the communication steps of sending and / or receiving in the above-described methods by interface circuit 6202 means, for example, that interface circuit 6202 performs data interaction between processor 6201, chip 6200, memory 6203, or transceiver devices. In some embodiments, processor 6201 performs at least one of the other steps.

[0391] The modules and / or devices described in each of the embodiments of the virtual device, the physical device, the chip, and the like can be combined or separated according to circumstances. Optionally, part or all of the steps can also be performed by multiple modules and / or devices in cooperation, which is not limited here.

[0392] The disclosure also proposes a storage medium, and the above-mentioned storage medium stores instructions, when the above-mentioned instructions run on communication device 6100, the communication device 6100 performs any one of the above methods. Optionally, the above-mentioned storage medium is an electronic storage medium. Optionally, the above-mentioned storage medium is a computer readable storage medium, but is not limited to this, and it can also be a storage medium readable by other devices. Optionally, the above-mentioned storage medium can be a non-transitory storage medium, but is not limited to this, and it can also be a transitory storage medium.

[0393] The disclosure also proposes a program product, and the above-mentioned program product is executed by communication device 6100, so that communication device 6100 performs any one of the above methods. Optionally, the above-mentioned program product is a computer program product.

[0394] The disclosure also proposes a computer program, when it runs on a computer, the computer executes any one of the above methods. Industrial applicability

[0395] When the terminal is configured as an intermediate node of A-IOT, the terminal remains in the RRC connected state, so as to forward A-IOT data in time and ensure the communication performance of A-IOT.

Claims

1. A communication method, performed by a terminal, the method comprising: maintaining in a radio resource control (RRC) connected state, in a case that the terminal is configured as an intermediate node in an ambient Internet of Things (A-IoT) system.

2. The method of claim 1, wherein, The method further comprises: receiving configuration information transmitted by a network device, the configuration information being used for configuring the terminal as the intermediate node. 3.The method of claim 1 or 2, wherein: the terminal is not configured with a first timer or is configured with the first timer.

4. The method of claim 3, wherein, The method further comprises: starting or restarting the first timer when the terminal receives or transmits A-IoT information, wherein the terminal is in the RRC connected state during running of the first timer.

5. The method of claim 4, wherein, The receiving or transmitting A-IoT information comprises at least one of: receiving a first command transmitted by the A-IoT device; transmitting a second command to the A-IoT device; transmitting a continuous wave (CW) to the A-IoT device.

6. The method of claim 3, wherein, The method further comprises: in a case that the terminal is configured with the first timer, the terminal does not start the first timer.

7. The method of claim 3, wherein, In a case that the terminal is configured with the first timer, further comprising: when the first timer expires, an RRC layer of the terminal controls the terminal to maintain in the RRC connected state and not to enter an RRC idle state; or, the method further comprises: in a case that the terminal is not configured as the intermediate node, the terminal enters the RRC idle state after the first timer expires.

8. The method of claim 3, wherein, The method further comprises: a MAC layer of the terminal receives indication information from a higher layer of the terminal, and determines a state of the first timer according to the indication information, wherein the terminal is configured with the first timer. 9.The method of claim 8, wherein: the indication information is used to indicate to stop running the first timer, and the determining the state of the first timer according to the indication information comprises: stopping running the first timer when the MAC layer receives the indication information transmitted by the RRC layer, or starting the first timer when the MAC layer does not receive the indication information. 10.The method of claim 8, wherein: the indication information is used to indicate not to start the first timer, and the determining the state of the first timer according to the indication information comprises: not starting the first timer when the MAC layer receives the indication information transmitted by the RRC layer, or starting the first timer when the MAC layer does not receive the indication information. 11.The method of claim 8, wherein: the indication information is used to indicate to start the first timer, and the determining the state of the first timer according to the indication information comprises: starting the first timer when the MAC layer receives the indication information transmitted by the RRC layer, or not starting the first timer when the MAC layer does not receive the indication information. The method further comprises:

12. The method of any one of claims 1 to 11, wherein, receiving A-IoT data or signaling transmitted by a network device; transmitting the A-IoT data or signaling to an A-IoT device. ​ 13.A communication method, performed by a network device, the method comprising: sending, to a terminal, configuration information for configuring the terminal as an intermediate node of an ambient Internet of Things (A-IoT) system, wherein the terminal is in an RRC connected state if the terminal is configured as the intermediate node.

14. The method of claim 13, wherein, The method further comprises: configuring or not configuring a first timer for the terminal. 15.The method of claim 14, wherein, the first timer is started or restarted when the terminal receives or transmits A-IoT information, wherein the terminal is in an RRC connected state during the running of the first timer.

16. The method of claim 15, wherein, The A-IoT information comprises at least one of: a first command sent by an A-IoT device to the terminal; a second command sent by the terminal to the A-IoT device; a continuous wave (CW) sent by the terminal to the A-IoT device. 17.The method of claim 14, wherein, the first timer is not started when the terminal is configured as the intermediate node if the first timer is configured. 18.The method of claim 14, wherein, a status of the first timer is determined by a MAC layer of the terminal according to an indication from a higher layer.

19. The method of any one of claims 13 to 18, wherein, The method further comprises: sending A-IoT data or signaling to the terminal. 20.A terminal comprising: a processing module configured to maintain in an RRC connected state if the terminal is configured as an intermediate node of an ambient Internet of Things (A-IoT) system. 21.A network device comprising: a transceiving module configured to send, to a terminal, configuration information for configuring the terminal as an intermediate node of an ambient Internet of Things (A-IoT) system, wherein the terminal is in an RRC connected state if the terminal is configured as the intermediate node. 22.A terminal comprising: one or more processors; wherein the terminal is configured to implement the method of any of claims 1-12. 23.A network device comprising: one or more processors; wherein the network device is configured to implement the method of any of claims 13-19. 24.A communication system comprising a terminal and a network device, wherein: the terminal is configured to implement the method of any of claims 1-12; the network device is configured to implement the method of any of claims 13-19. 25.A storage medium having stored instructions, wherein: when the instructions are run on a communication device, the communication device is caused to perform the method of any of claims 1-12, or any of claims 13-19. 26.A program product, wherein: when the program product is executed by a communication device, the communication device is caused to perform the method of any of claims 1-12, or any of claims 13-19.

Images