Communication method and communication apparatus

Abstract

Provided in the present application are a communication method and a communication apparatus. The communication method comprises: when a first apparatus is not paged, or the first apparatus fails to access a second apparatus, or the data transmission between the first apparatus and the second apparatus fails, receiving first time information, wherein the first time information comprises a first duration during which the second apparatus does not send a first message. By means of the method, the success rate of a first apparatus receiving a first message sent by a second apparatus is improved.

Description

Communication methods and communication devices

[0001] This application claims priority to Chinese Patent Application No. 202411051022.0, filed on July 31, 2024, entitled "Communication Method and Communication Apparatus", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of communication technology, specifically to a communication method and a communication device. Background Technology

[0003] Radio frequency identification (RFID) technology is a non-contact automatic identification technology. An RFID system typically includes a reader and a tag. The reader can read information from the tag or write information that needs to be stored in the tag. The tag converts the wireless signals emitted by the reader into energy, which powers itself to operate.

[0004] With the development of communication technology, to save power consumption of terminal devices, it is proposed to introduce RFID technology into mobile communication network systems to realize passive Internet of Things (IoT), that is, network devices can act as readers, realizing the functions of readers. For example, there is the ambient internet of things (A-IoT) technology. A-IoT consists of reader devices (e.g., base stations) and passive, semi-passive, or active A-IoT terminals. A-IoT terminals are terminal devices in cellular network systems, and can also be understood as IoT terminals with extremely low power consumption and extremely low complexity. Main functions include inventory, positioning, sensing, and command; typical application scenarios include logistics, warehousing, industrial manufacturing, identity recognition, and environmental monitoring.

[0005] When IoT devices connect to read / write devices, they typically need to receive messages from the read / write devices. However, IoT devices do not know when the read / write devices will send messages, which reduces the success rate of IoT devices receiving messages from the read / write devices. Summary of the Invention

[0006] To address the aforementioned technical problems, this application provides a communication method and a communication device, in which the reading and writing device informs the IoT device of the time it will not send messages, which helps to improve the success rate of the IoT device receiving messages from the reading and writing device.

[0007] In a first aspect, a communication method is provided, which can be executed by a first device. Unless otherwise specified, the "first device" in this application can refer to the first device itself (e.g., an electronic tag, a radio frequency identification (RFID) tag, an ambient internet of things (AIoT) device, etc.), a component in the first device (e.g., a processor, a chip, or a chip system, etc.), or a logic module or software that can implement all or part of the functions of the first device.

[0008] The method includes: when the first device is not paged, or the first device fails to connect to the second device, or the data transmission between the first device and the second device fails, receiving first time information, wherein the first time information includes a first duration during which the second device does not send a first message.

[0009] Based on the above scheme, the first device learns the time when the second device does not send the first message, thereby improving the success rate of the first device receiving the first message sent by the second device.

[0010] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: communicating with the second device based on the first time information.

[0011] In conjunction with the first aspect, in some implementations of the first aspect, the first message is monitored or received after a first duration following the receipt of the first time information.

[0012] Based on the above scheme, the first device monitors or receives the first message after a first duration, which improves the success rate of the first device receiving the first message sent by the second device.

[0013] After receiving the first time information for a first duration, the second time information is received, the second time information including a second duration during which the second device does not send the first message.

[0014] Based on the above scheme, when the time for the next transmission of the first message is uncertain, the second device can instruct the second device not to transmit the first message at multiple times.

[0015] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: stopping monitoring or receiving the first message within a first duration after receiving the first time information.

[0016] Based on the above scheme, the first device stops monitoring or receiving the first message when the second device does not send the first message (or before sending the first message), thereby saving the energy consumption of the first device.

[0017] In conjunction with the first aspect, in some implementations of the first aspect, stopping monitoring or receiving the first message within a first duration after receiving the first time information includes: being in a dormant state within a first duration after receiving the first time information.

[0018] Based on the above scheme, the first device enters a sleep state when the second device does not send the first message (or before sending the first message), thereby saving the energy consumption of the first device.

[0019] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: starting a first timer with a duration of the first duration upon receiving the first time information; the first duration after receiving the first time information includes: after the first timer times out.

[0020] In conjunction with the first aspect, in some implementations of the first aspect, the first message includes a paging message or an access trigger message.

[0021] Based on the above scheme, the first device learns the time when the second device does not send paging messages or access trigger messages, thereby improving the success rate of the first device accessing the second device.

[0022] In conjunction with the first aspect, in some implementations of the first aspect, after a first duration following the receipt of the first time information, monitoring or receiving the first message is stopped based on the battery information of the first device.

[0023] The phrase "after the first duration of receiving the first time information" can be replaced with "after the first time period". The start time of this first time period is the moment when the first time information is received, and the end time is the moment after the first duration of receiving the first time information.

[0024] Based on the above scheme, if the power of the first device is still insufficient, the time to exit the sleep state can be delayed, thereby avoiding the power being exhausted when the second device is connected.

[0025] Secondly, a communication method is provided, which can be executed by a second device. Unless otherwise specified, the "second device" in this application can refer to the second device itself (e.g., a base station, a terminal, a relay node, an IAB node, etc.), a component in the second device (e.g., a processor, a chip, or a chip system, etc.), or a logic module or software that can implement all or part of the functions of the second device. The method includes: the second device sending a first message to a first device, the first message indicating an access type, the access type being one of at least two access types; and the second device enabling the first device to access the device according to the access type.

[0026] The method includes: sending first time information to a first device, the first time information including a first duration during which the second device does not send the first message; and not sending the first message within a first duration after sending the first time information.

[0027] In conjunction with the second aspect, in some implementations of the second aspect, before sending the first time information to the first device, the method further includes: determining that the first device satisfies a first condition, the first condition including any one of the following conditions: the first device is not paged, or the first device fails to access the second device, or data transmission between the first device and the second device fails.

[0028] In conjunction with the second aspect, in some implementations of the second aspect, the first message includes a paging message or an access trigger message.

[0029] In conjunction with the second aspect, in some implementations of the second aspect, the method further includes: sending the first message after a first duration following the transmission of the first time information.

[0030] In conjunction with the second aspect, in some implementations of the second aspect, the method further includes: after a first duration of sending the first time information, sending second time information, the second time information including a second duration during which the second device does not send the first message.

[0031] In conjunction with the second aspect, in some implementations of the second aspect, the method further includes: sending third time information before sending the first time information for a first duration, the third time information including a third duration during which the second device does not send the first message.

[0032] Thirdly, a communication device is provided, comprising: a processor coupled to a memory for storing a computer program, the processor for running the computer program, such that the communication device performs the method described in the first aspect and any possible implementation thereof.

[0033] Fourthly, a communication device is provided, comprising: a processor coupled to a memory for storing a computer program, the processor for running the computer program, such that the communication device performs the method described in the second aspect above and any possible implementation thereof.

[0034] Fifthly, a computer-readable storage medium is provided having a computer program stored thereon, which, when executed by a computer, causes the computer to perform the communication methods that can be implemented in the first aspect and any of the first aspect, or the second aspect and any of the second aspect.

[0035] In a sixth aspect, a computer program product containing instructions is provided, which, when run on a computer, causes the computer to perform the communication method that can be implemented in the first aspect and any of the first aspect, or the second aspect and any of the second aspect.

[0036] In a seventh aspect, a chip is provided, the chip including a processor and a data interface, the processor reading instructions stored in a memory through the data interface to execute the communication methods implemented in the first aspect and any of the first aspect, or the second aspect and any of the second aspect.

[0037] In conjunction with the seventh aspect, in one possible implementation, the processor is coupled to the memory via an interface.

[0038] In conjunction with the seventh aspect, in one possible implementation, the chip system further includes a memory in which computer programs or computer instructions are stored.

[0039] Eighthly, a communication system is provided, including a communication device of the third aspect and a communication device of the fourth aspect. Attached Figure Description

[0040] Figure 1 is a schematic diagram of a communication system applicable to an embodiment of this application.

[0041] Figure 2 is a schematic diagram of another communication system applicable to embodiments of this application.

[0042] Figure 3 is a schematic diagram of another communication system applicable to an embodiment of this application.

[0043] Figure 4 is a schematic diagram of another communication system applicable to embodiments of this application.

[0044] Figure 5 is a schematic diagram of an open radio access network (O-RAN) system applicable to embodiments of this application.

[0045] Figure 6 is a schematic diagram of another O-RAN system applicable to embodiments of this application.

[0046] Figure 7 is a schematic diagram of a random access procedure for a tag.

[0047] Figure 8 is a schematic flowchart of a communication method 800 provided in an embodiment of this application.

[0048] Figure 9 is a schematic flowchart of a communication method 900 provided in an embodiment of this application.

[0049] Figure 10 is a schematic diagram of a communication method provided in an embodiment of this application.

[0050] Figure 11 is a schematic flowchart of a communication method 1100 provided in an embodiment of this application.

[0051] Figure 12 is a schematic diagram of a communication method provided in an embodiment of this application.

[0052] Figure 13 is a schematic block diagram of a communication device 1300 provided in an embodiment of this application.

[0053] Figure 14 is a schematic block diagram of another communication device 1400 provided in an embodiment of this application.

[0054] Figure 15 is a schematic block diagram of the chip system 1500 provided in an embodiment of this application. Detailed Implementation

[0055] The technical solutions in this application will now be described with reference to the accompanying drawings.

[0056] The technical solutions provided in this application can be applied to various communication systems, such as: 5th generation (5G) or new radio (NR) systems, long term evolution (LTE) systems, LTE frequency division duplex (FDD) systems, LTE time division duplex (TDD) systems, wireless local area network (WLAN) systems, satellite communication systems, future communication systems, or integrated systems of multiple systems. The technical solutions provided in this application can also be applied to device-to-device (D2D) communication, vehicle-to-everything (V2X) communication, machine-to-machine (M2M) communication, machine-type communication (MTC), and Internet of Things (IoT) communication systems or other communication systems.

[0057] The technical solutions provided in this application can also be applied to non-terrestrial network (NTN) systems such as inter-satellite communication and satellite communication. As an example, a satellite communication system includes a satellite base station and terminal equipment. The satellite base station provides communication services to the terminal equipment. The satellite base station can also communicate with other base stations. A satellite can act as a base station or as a terminal device. Here, "satellite" can refer to unmanned aerial vehicles (UAVs), hot air balloons, low-Earth orbit (LEO) satellites, medium-Earth orbit (MEO) satellites, high-Earth orbit (HEO) satellites, etc. "Satellite" can also refer to non-terrestrial base stations or non-terrestrial equipment, etc.

[0058] In a communication system, a device can send signals to or receive signals from another device. These signals can include information, signaling, or data. The device can also be replaced by an entity, network entity, communication device, mobile device, network element, communication module, node, communication node, communication apparatus, etc. This disclosure uses a device as an example. For instance, a communication system can include at least one terminal device and at least one network device. The network device can send downlink signals to the terminal device, and / or the terminal device can send uplink signals to the network device. It is understood that the terminal device in this disclosure can be replaced by a first communication device, and the network device can be replaced by a second communication device, both performing the corresponding communication methods described in this disclosure. Alternatively, the corresponding communication methods in this disclosure can be applied between network devices or between terminal devices, without limitation herein.

[0059] The terminal device in this application embodiment can be a device or module that accesses the aforementioned communication system and has corresponding communication functions. The terminal device can include various devices with wireless communication capabilities, which can be used to connect people, objects, machines, etc. The terminal device can be widely applied in various scenarios, such as: cellular communication, D2D, V2X, peer-to-peer, M2M, MTC, IoT, virtual reality (VR), augmented reality (AR), industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, smart cities, drones, robots, remote sensing, passive sensing, positioning, navigation and tracking, autonomous delivery, etc. The terminal device can be a terminal in any of the above scenarios, such as an MTC terminal, an IoT terminal, etc. Terminal equipment can be user equipment (UE), terminal, fixed equipment, mobile station equipment or mobile equipment, subscriber unit, handheld device, vehicle-mounted equipment, wearable device, cellular phone, smartphone, session initiation protocol (SIP) phone, wireless data card, personal digital assistant (PDA), computer, tablet computer, laptop computer, wireless modem, handset, laptop computer, computer with wireless transceiver capability, smart book, vehicle, satellite, global positioning system (GPS) device, target tracking device, aircraft (e.g., drone, helicopter, multiple helicopters, four helicopters, or airplanes), ship, remote control device, smart home device, industrial equipment, transportation vehicle with wireless communication capability, communication module, or roadside unit with terminal function, all conforming to the 3rd generation partnership project (3GPP) standard. The terminal device (RSU) can be a unit or a device built into the aforementioned equipment (e.g., a communication module, modem, or chip in the aforementioned equipment), or other processing devices connected to a wireless modem. For ease of description, the terminal device will be described below as a terminal or UE.

[0060] It should be understood that in certain scenarios, a UE can also be used as a base station. For example, a UE can act as a scheduling entity, providing sidelink signaling between UEs in scenarios such as V2X, D2D, or end-to-end.

[0061] In this embodiment, the device for implementing the functions of the terminal device can be the terminal device itself, or it can be any device capable of supporting the terminal device in implementing those functions, such as a chip system. This device can be installed in or used in conjunction with the terminal device. In this embodiment, the chip system can be composed of chips or may include chips and other discrete components. This embodiment only uses the terminal device as an example to illustrate the device for implementing the functions of the terminal device, and does not constitute a limitation on the solution of this embodiment.

[0062] The network device in this application embodiment can be a device or module with corresponding communication functions. The network device can be a device used to communicate with terminal devices; it can also be called an access network device or a wireless access network device, such as a base station. In this application embodiment, the network device can refer to a radio access network (RAN) node (or device) that connects the terminal device to the wireless network. A base station can broadly encompass, or be replaced by, various names including: NodeB, evolved NodeB (eNB), next-generation NodeB (gNB), relay station, access point, transmitting and receiving point (TRP), transmitter point, master station, auxiliary station, motor slide retainer (MSR) node, home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. A base station can be a macro base station, micro base station, relay node, donor node, or a combination thereof. A base station can also refer to a communication module, modem, or chip installed within the aforementioned equipment or apparatus. A base station can also be a mobile switching center, a device that performs base station functions in D2D, V2X, and M2M communications, or a device that performs base station functions in future communication systems. A base station can support networks using the same or different access technologies. The embodiments of this application do not limit the specific technologies or device forms used in the network equipment.

[0063] Base stations can be fixed or mobile. For example, a helicopter or drone can be configured to act as a mobile base station, and one or more cells can move depending on the location of the mobile base station. In other examples, a helicopter or drone can be configured as a device to communicate with another base station.

[0064] In some deployments, the network devices mentioned in the embodiments of this application may be devices including CU, DU, or CU and DU, or devices with control plane CU nodes (central unit-control plane (CU-CP)) and user plane CU nodes (central unit-user plane (CU-UP)) and DU nodes. For example, the network devices may include gNB-CU-CP, gNB-CU-UP, and gNB-DU.

[0065] In some deployments, multiple RAN nodes collaborate to assist terminals in achieving wireless access, with different RAN nodes each implementing some of the base station's functions. For example, RAN nodes can be CUs, DUs, CU-CPs, CU-UPs, or RUs. CUs and DUs can be configured separately or included in the same network element, such as a BBU. RUs can be included in radio frequency equipment or radio frequency units, such as RRUs, AAUs, or RRHs.

[0066] In some deployments, the CU (Core Unit) is a logical node that carries the Radio Resource Control (RRC) layer, Service Data Adaptation Protocol (SDAP) layer, Packet Data Convergence Protocol (PDCP) layer, and other control functions of the access network equipment. The CU connects to network nodes such as the core network through interfaces, which may be E2 interfaces, etc. Optionally, the CU possesses some core network functions. The CU (e.g., the PDCP layer and higher layers) connects to the DU (e.g., the Radio Link Control (RLC) layer and lower layers) through interfaces, which may be F1 interfaces, etc. In some examples, these interfaces (e.g., the F1 interface) can provide control plane (C-Plane) and user plane (U-Plane) functions (e.g., interface management, system information management, UE context management, RRC message transmission, etc.). The F1 application protocol (F1AP) is the application protocol for the F1 interface, and in some examples, it defines the F1 signaling procedures. The F1 interface supports both the control plane (F1-C) and the user plane (F1-U).

[0067] In some deployments, the CU can be split into CU-CP and CU-UP. CU-CP is a logical node carrying the RRC layer and the control plane part of PDCP (PDCP-C) layer, used to implement the CU's control plane functions. CU-CP can interact with network elements in the core network used to implement control plane functions. These network elements in the core network can be access and mobility function network elements. CU-UP is a logical node carrying the SDAP layer and the user plane part of PDCP (PDCP-U) layer, used to implement the CU's user plane functions. CU-UP can interact with network elements in the core network used to implement user plane functions. The above CU and DU configurations are merely examples; the functions of CU and DU can be configured as needed. For example, CU or DU can be configured to have more protocol layer functions, or CU or DU can be configured to have only partial protocol layer processing functions. For example, some functions of the RLC layer and the functions of the protocol layer above the RLC layer can be placed in the CU, while the remaining functions of the RLC layer and the functions of the protocol layer below the RLC layer can be placed in the DU. Another example is that the functions of the CU or DU can be divided according to service type or other system requirements. For instance, based on latency, functions that need to meet low latency requirements can be placed in the DU, while functions that do not need to meet such latency requirements can be placed in the CU.

[0068] In some deployments, the DU (Distributed Unit) is a logical node that carries the RLC (Real-Time Control) layer, the medium access control (MAC) layer, the higher physical layer (Higher PHY) layer, and other functions. In some examples, the DU can control at least one RU (Remote Root). The DU connects to the RU through interfaces, which can be fronthaul interfaces. In some examples, the Higher PHY layer includes the PHY layer processing, such as forward error correction (FEC) encoding and decoding, scrambling, modulation, and demodulation.

[0069] In some deployments, the RU is a logical node that carries both lower physical layer (PHY) and radio frequency (RF) processing. In some examples, the RU can be a TRP, RRH, or other similar entity. In some examples, the Low-PHY includes portions of the PHY processing, such as Fast Fourier Transform (FFT), Inverse Fast Fourier Transform (IFFT), digital beamforming, and filtering. The RU communicates with one or more UEs via a radio link.

[0070] The DU and RU can be co-located or not. The DU and RU exchange control plane and user plane information via a fronthaul link through a lower-layer split-control, user, and synchronization (LLS-CUS) interface. LLS-CUS may include interfaces providing control and user planes respectively. In some examples, the control plane refers to real-time control between the DU and RU. The DU and RU exchange management information via a fronthaul link interface (such as an LLS-M interface), and the management plane (M-Plane) refers to non-real-time management operations between the DU and RU.

[0071] DU and RU can cooperate to implement the functions of the PHY layer. A DU can be connected to one or more RUs. The functions of DU and RU can be configured in various ways depending on the design. For example, a DU can be configured to implement baseband functions, and an RU can be configured to implement mid-RF functions. Another example is that a DU can be configured to implement higher-level functions in the PHY layer, and an RU can be configured to implement lower-level functions in the PHY layer, or to implement both lower-level and RF functions. Higher-level functions in the physical layer can include a portion of the physical layer's functions that are closer to the MAC layer, while lower-level functions in the physical layer can include another portion of the physical layer's functions that are closer to the mid-RF side.

[0072] In one possible design, the processing unit in the BBU used to implement baseband functions is called the baseband high (BBH) unit, and the processing unit in the RRU / AAU / RRH used to implement baseband functions is called the baseband low (BBL) unit.

[0073] In different systems, CU (or CU-CP and CU-UP), DU, or RU may have different names, but those skilled in the art will understand their meaning. For example, a radio access network can also be an open radio access network (O-RAN) architecture. In an O-RAN system, CU can also be called an open CU (open CU, O-CU), DU can also be called an open DU (open DU, O-DU), CU-CP can also be called an open CU-CP (O-CU-CP), CU-UP can also be called an open CU-UP (O-CU-UP), and RU can also be called an open RU (open RU, O-RU). Any of the units among CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented through software modules, hardware modules, or a combination of software modules and hardware modules.

[0074] In this embodiment, the device for implementing the functions of a network device can be a network device itself, or a device capable of supporting the network device in implementing those functions, such as a chip system, chip, circuit, or communication module (i.e., a communication module that performs communication functions). This device can be installed within the network device. In this embodiment, the chip system can be composed of chips, or it can include chips and other discrete devices. Furthermore, the device can be configured with program instructions for performing corresponding communication functions. This embodiment only uses a network device as an example to illustrate the device for implementing the functions of a network device, and does not limit the solution of this embodiment.

[0075] Network devices and terminal devices can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; and they can also be deployed in the air on airplanes, balloons, and satellites. This application does not limit the scenario in which the network devices and terminal devices are located. Furthermore, terminal devices and network devices can be hardware devices, software functions running on dedicated hardware, or software functions running on general-purpose hardware, such as virtualization functions instantiated on a platform (e.g., a cloud platform), or entities that include dedicated or general-purpose hardware devices and software functions. This application does not limit the specific form of the terminal devices and network devices.

[0076] First, a brief introduction to the communication system applicable to the embodiments of this application is given below.

[0077] Figure 1 is a schematic diagram of a communication system 100 applicable to an embodiment of this application. As shown in Figure 1, the communication system includes a network device 110 and an ambient Internet of Things (A-IoT) terminal 120. The network device 110 and the A-IoT terminal 120 communicate bidirectionally. The communication between the network device 110 and the A-IoT terminal 120 includes ambient Internet of Things data and / or signaling. That is, the network device 110 sends downlink data and / or signaling to the A-IoT terminal 120, and the A-IoT terminal 120 sends uplink data and / or signaling to the network device 110. Alternatively, it can be understood that the network device 110 and the A-IoT terminal 120 transmit uplink and downlink data and / or signaling.

[0078] Figure 2 is a schematic diagram of a communication system 200 applicable to an embodiment of this application. As shown in Figure 2, the communication system includes a network device 210, an intermediate node 220, and an A-IoT terminal 230. The network device 210 and the A-IoT terminal 230 communicate bidirectionally with the intermediate node 220. For example, the network device 210 communicates bidirectionally with the intermediate node 220, and then the intermediate node 220 communicates bidirectionally with the A-IoT terminal 120. That is, the network device 210 transmits uplink and downlink data and / or signaling between itself and the intermediate node 220, and the intermediate node 220 transmits uplink and downlink data and / or signaling between itself and the A-IoT terminal 120. In this embodiment, the intermediate node 220 can be a repeater, an integrated access backhaul (IAB) node, a UE, etc.

[0079] Figure 3 is a schematic diagram of a communication system 300 applicable to an embodiment of this application. As shown in Figures 3(a) and (b), the communication system includes a network device 310, an auxiliary node 320, and an A-IoT terminal 330. In Figure 3(a), the A-IoT terminal 330 sends data and / or signaling to the network device 310, the network device 310 sends data and / or signaling to the auxiliary node 320 via the Uu interface, and then the A-IoT terminal 330 receives data and / or signaling from the auxiliary node 320. In Figure 3(b), the A-IoT terminal 330 receives data and / or signaling sent by the network device 310 and sends data and / or signaling to the auxiliary node 320, and then the network device 310 receives data and / or signaling from the auxiliary node 320 via the Uu interface. In this embodiment of the application, the intermediate node of the auxiliary node 320 may be a repeater, an IAB node, a UE, etc.

[0080] Figure 4 is a schematic diagram of a communication system 400 applicable to an embodiment of this application. As shown in Figure 4, the communication system includes a terminal device 410 and an A-IoT terminal 420. The terminal device 410 and the A-IoT terminal 420 communicate bidirectionally. The communication between the terminal device 410 and the A-IoT terminal 420 includes environmental IoT data and / or signaling. That is, the terminal device 410 sends downlink data and / or signaling to the A-IoT terminal 420, and the A-IoT terminal 420 sends uplink data and / or signaling to the terminal device 410. Alternatively, it can be understood that the terminal device 410 and the A-IoT terminal 420 transmit uplink and downlink data and / or signaling.

[0081] Figures 1 to 4 are merely schematic diagrams. The communication system to which the embodiments of this application are applicable may also include other devices, such as core network devices, wireless relay devices and / or wireless backhaul devices, which are not shown in Figures 1 to 4.

[0082] The embodiments of this application can also be applied to open RAN (O-RAN) system architecture.

[0083] As shown in Figure 5, an O-RAN system can include core network (CN) equipment, access network (RAN) equipment, and user equipment (UE). Access network equipment communicates with core network equipment via a backhaul link and with UE via an air interface. For example, a BBU in the access network equipment communicates with core network equipment via a backhaul link, and an RU in the access network equipment communicates with UE via an air interface. The BBU communicates with at least one RU via a fronthaul link; the BBU and RU may or may not be co-located. The BBU includes at least one CU and at least one DU, and the CU and DU can communicate via at least one midhaul link.

[0084] Figure 5 is just a schematic diagram. The wireless communication system may also include other devices, which are not shown in Figure 5.

[0085] Figure 6 is a schematic diagram of the application framework involving the RIC module under the O-RAN architecture. As shown in Figure 6, the communication system includes a RAN intelligent controller (RIC). The RIC includes near-real-time RIC (near-RT RIC) and non-real-time RIC (non-RT RIC). The non-real-time RIC mainly processes non-real-time information, such as data that is not sensitive to latency, with latency in the order of seconds. The real-time RIC mainly processes near-real-time information, such as data that is relatively sensitive to latency, with latency in the order of tens of milliseconds.

[0086] The near real-time RIC and non-real-time RIC can also be set up as separate network elements. Optionally, the near real-time RIC and non-real-time RIC can also be part of other devices. For example, the near real-time RIC can be set in the RAN node (e.g., in CU, DU), while the non-real-time RIC can be set in the OAM, cloud server, core network device, or other network device.

[0087] To facilitate a better understanding of the technical solution of this application, some related technologies involved in the technical solution of this application are introduced.

[0088] 1. Passive Radio Frequency Identification (RFID):

[0089] An RFID system consists of an interrogator and tags, which communicate with each other without contact. The interrogator can read information from the tag or write information to the tag. The tag itself is simple, requiring excitation from the interrogator to transmit information; it converts the wireless signal emitted by the interrogator into energy to power itself. If RFID is applied to mobile communication systems, such as 5G systems, the base station can act as the interrogator, fulfilling its functions.

[0090] The primary application of RFID is identification, but it can also be used for data reading and writing. The tags have the following characteristics:

[0091] 1) The label design is simple, for example, the application layer and air interface signaling are combined into one design.

[0092] 2) The tag supports power consumption in the microwatt (μW) level or hundreds of microwatts level, but cannot support complex designs or complex measurements.

[0093] 3) When using multi-tag communication, time-division multiplexing is used, and multiple tags are read serially. It does not support the distinction between the frequency domain and the code domain, and its parallel performance is poor.

[0094] Figure 7 is a flowchart of the RFID process. As shown in Figure 7, the specific working process of RFID is as follows.

[0095] In S710, the reader sends a select signal to the tag. Correspondingly, the tag receives the select signal from the reader.

[0096] The select signaling is used to select one tag or a group of tags. Specifically, the reader uses the select signaling to cause tags that meet and / or do not meet the selection criteria to set the status of a specific session in the inventory flag.

[0097] For example, the inventory flag can have four independent sessions: session 0 (S0), session 1 (S1), session 2 (S2), and session 3 (S3). Each session can be in state A or state B. Specifically, the select signaling also carries the fields of inventory session, action, and mask. The select signaling sets the selected tag with the corresponding flag. Assuming that the inventorySession selects session S0 and action = 0, if the mask matches, the tag will set the flag of S0 to A, i.e., perform the initial flag setting.

[0098] Each flag corresponds to a session, and `inventorySession` specifies which session's flag should be set. The `action` parameter specifies how to set the flag; for example, `action = 1` or `action = 0`. When a tag receives a `select` signal, if the mask matches, it will set the flag corresponding to the session to A (action = 1) or B (action = 0). The `mask` is used to filter which tags are selected. For example, if a tag stores a complete 96-bit identifier, the `mask` can indicate that tags with the first 16 bits being 111…111 are selected. If the `mask` matches, the tag can further set its flag based on the `action` parameter and then listen for subsequent query commands.

[0099] Optionally, the above select signaling can also be paging signaling, used to page one or a group of tags.

[0100] In S720, the reader sends a query command to the tag. Correspondingly, the tag receives the query command from the reader.

[0101] The Query command carries the value of parameter Q, the session, and the inventory flag. Assuming the session is S0 and the inventory flag is A, when the tag's session matches the flag, a random value between 0 and 2 is generated based on parameter Q. Q A value between -1 and 1 is used as the initial value of the counter. The tag determines whether to immediately send a random number (RN) to the reader based on the value of the counter. For example, when counter = 0, the tag will send an RN to the reader (e.g., RN(16), where RN(16) is a 16-bit random number). When counter is not 0, the tag will not send an RN to the reader. If the reader does not receive an RN from the tag within a certain period of time, it will send a QueryRep command to the tag.

[0102] Specifically, there are two scenarios for the subsequent execution steps: scenario 1 and scenario 2.

[0103] Case 1: Counter = 0, specifically including S721.

[0104] S721, the tag sends a random number to the reader. Correspondingly, the reader receives the random number from the tag.

[0105] The random number (RN) can be a 16-bit random number or an 8-bit random number; this application does not limit this.

[0106] Case 2: Counter is an integer greater than or equal to 1, specifically including S722 and S723.

[0107] S722, the reader sends a QueryRep command to the tag. Correspondingly, the tag receives the QueryRep command from the reader.

[0108] The QueryRep command can be empty, meaning it may omit the value of parameter Q, session, and disk flag. The number of times the QueryRep command is sent is determined by the value of counter. Specifically, each time the tag receives a QueryRep command, counter = counter - 1. The tag continues until the value of counter reaches 0, at which point it sends an RN to the reader.

[0109] More specifically, the tag can calculate the selectable time slot range [0, 2] based on the value of the random parameter Q. Q -1], the label can be in [0, 2]Q A random value is selected from [-1] and assigned to counter. Each time the tag receives a QueryRep command, the counter's count is decremented by 1. When the counter's count reaches 0, S723 can be executed.

[0110] For example, each QueryRep command corresponds to the start or end of an access time slot. That is, each time a tag receives a QueryRep command, it signifies the end of the previous time slot and the start of the next time slot.

[0111] S723, the tag sends a random number to the reader. Correspondingly, the reader receives the random number from the tag.

[0112] When the counter count is 0, the tag sends a random number in its randomly selected access time slot.

[0113] In S730, the reader sends an acknowledged (ACK) message to the tag. Correspondingly, the tag receives the ACK message from the reader.

[0114] When a reader receives the aforementioned RN from a tag, if there is no collision (i.e., the reader receives only one RN from a tag), it will send an ACK message to the reader. This ACK message includes the received RN, indicating that the tag contention has been successfully resolved.

[0115] S740, the tag sends uplink data to the reader.

[0116] The upstream data can be the electronic product code (EPC).

[0117] S750, the reader sends the QueryRep command to the tag again. Correspondingly, the tag receives the QueryRep command from the reader.

[0118] S760, the tag will reverse the state of the disk storage flag.

[0119] After a tag receives a QueryRep command, indicating successful data transmission, it can reverse the state of the disk storage flag. For example, the state of session 0 can be set from state A to state B. Reversing the disk storage flag prevents tags that have already been disked from being disked again, because tags with flag A set in subsequent Query commands and flag B set will not respond to receiving the Query command.

[0120] The QueryRep command can be used to trigger tags that have not yet successfully connected to the reader. Specifically, the count value of tags whose counter value is not 0 is decremented by 1 until the counter value is 0. Then, steps S723 to S760 are repeated until all tags have successfully connected to the reader.

[0121] 2. A-IoT:

[0122] A-IoT devices in A-IoT technology include network devices and Type I terminal devices; or, in other words, A-IoT-based communication systems include network devices and Type I terminal devices. Type I terminal devices can be devices with A-IoT terminal device functionality. In this case, both readers and A-IoT terminal devices can be implemented based on cellular network infrastructure. In other words, both readers and A-IoT terminal devices can be devices within a cellular network. For example, the functionality of a reader can be implemented by network devices, such as base stations. A-IoT terminal devices can be implemented by terminals within a cellular network, such as ultra-low power, ultra-low complexity IoT terminals, i.e., Type I terminals. Network devices and Type I terminals can perform contactless data communication, thereby reading information from Type I terminals and / or writing information that needs to be stored into Type I terminals. A-IoT technology can be used to implement one or more of the following services: inventory, positioning, sensing, and command. Typical application scenarios for A-IoT technology include logistics, warehousing, industrial manufacturing, identity recognition, and environmental monitoring.

[0123] For example, inventory management involves using a reader (e.g., a base station or terminal device) to access A-IoT terminals (or A-IoT terminal devices) within its coverage area. Successfully connected devices need to send their unique identifier (which can be recognized by the network, such as the EPC in RFID) to the reader. Inventory management can also be called a count operation. It retrieves tag identification information; for example, the reader can use commands like Query and ACK to obtain tag identification information. To facilitate tag inventory, tags include four session identifiers, each corresponding to two inventory states: A and B. The inventory state is indicated by a sessInventoried flag. When a reader selects a tag, the selection command sent to it carries a session identifier, and the tag stores this session identifier. When the reader performs inventory management on a tag, the query command sent to it includes the session identifier, at which point the tag can flip its inventory state from A to B. If the reader sends a query command to perform inventory operations again, the tag will not respond to the reader because the inventory status of the tag is B, thus avoiding the same tag being inventoried multiple times in the same inventory cycle.

[0124] Positioning is the process of using location signals to pinpoint the location of an A-IoT terminal.

[0125] Sensing involves A-IoT terminals reporting sensor data to the base station, such as temperature data.

[0126] Commands can be operational instructions, such as read, write, kill, or lock. Read operations can read the EPC, tag identifier (TID), content stored in the tag's reserved area, or content stored in the user's storage area from the tag's memory. Write operations can perform write operations on the tag's storage area; for example, a network device (e.g., a base station) can send a downlink command and data to instruct the A-IoT terminal to write data to its own storage area. Kill operations can permanently disable the tag. Lock operations can lock the tag's information, preventing read or write operations on that tag. Alternatively, locking operations can also lock a storage area, preventing or disallowing read or write operations on that storage area; for example, a network device can send a downlink command to instruct the A-IoT terminal to lock the location at a specified address in the storage area, making the contents of that storage area immutable and / or unreadable.

[0127] Terminal devices in A-IoT can be divided into three categories: device A, device B, and device C.

[0128] 1) Device A (similar to a passive tag): It has no energy storage or some low capacitance energy storage, cannot generate independent signals, and uses backscattering to transmit signals.

[0129] 2) Device B (similar to a semi-passive tag): It has energy storage, such as capacitor energy storage, but cannot generate signals independently; it uses backscattering to transmit signals. The stored energy can amplify the reflected signal. Optionally, device B stores energy using a battery.

[0130] 3) Device C (similar to an active tag): It has energy storage, can generate signals independently, and has active radio frequency (RF) components for transmission.

[0131] The 3GPP meeting further defined the following three categories of A-IoT devices: device 1, device 2a, and device 2b.

[0132] 1) Device 1: Peak power consumption is approximately 1μW, with energy storage function, and initial sampling frequency offset (SFO) reaches 10. X At parts per million (ppm), it cannot amplify downlink (DL) or uplink (UL) signals. It requires an external carrier signal for backscatter communication to enable uplink transmission.

[0133] 2) Device 2a: Peak power consumption less than or equal to several hundred μW, with energy storage function, and initial sampling frequency offset up to 10. X ppm can amplify DL and / or UL signals. An external carrier signal is required for backscatter communication in order to perform uplink transmission.

[0134] 3) Device 2b: Peak power consumption less than or equal to several hundred μW, with energy storage function, and initial sampling frequency offset of 10. X ppm, capable of DL and / or UL signal amplification. The device can perform uplink transmission without relying on an externally provided carrier.

[0135] 3. Frequency calibration

[0136] Because the crystal oscillator accuracy of the device is very low, for example, SFO = 10^5 ppm, which means it will deviate by 1 ms every 10 ms, the device needs to be woken up to perform calibration based on the calibration signal / information / frame. Each time the device wakes up, it receives downlink signaling. Regardless of whether the downlink information is something it can successfully parse, the header is always the same. For example, the delimiter and calibration are the same in different downlink signaling or downlink signaling for different devices. Therefore, as long as the device receives a downlink message, regardless of whether it is a message it needs to parse or can parse, it can complete frequency calibration based on the message header / frame header (such as calibration and / or delimiter).

[0137] As mentioned earlier, when an IoT device connects to a reader / writer, it is usually necessary to monitor messages from the reader / writer. However, the IoT device does not know when the reader / writer will send a message.

[0138] In view of this, this application provides a communication method in which a read / write device indicates to an IoT device a time period during which it will not send messages, thereby improving the success rate of the IoT device receiving messages from the read / write device.

[0139] Before introducing the scheme of this application, the following points should be noted.

[0140] (1) In this application, “instruction” may include direct instruction, indirect instruction, explicit instruction, and implicit instruction. When describing a certain instruction information for the purpose of instructing A, it can be understood that the instruction information carries A, directly instructs A, or indirectly instructs A.

[0141] In this application, the information indicated by the instruction information is called the information to be instructed. In specific implementations, there are many ways to indicate the information to be instructed, such as, but not limited to, directly indicating the information to be instructed, such as the information to be instructed itself or its index. It can also indirectly indicate the information to be instructed by indicating other information, where there is a relationship between the other information and the information to be instructed. It can also indicate only a part of the information to be instructed, while the other parts are known or pre-agreed upon. For example, the instruction of specific information can be achieved by using a pre-agreed (e.g., protocol-defined) arrangement of various pieces of information, thereby reducing instruction overhead to some extent. Furthermore, the information to be instructed can be sent as a whole or divided into multiple sub-information pieces, and the sending period and / or timing of these sub-information pieces can be the same or different.

[0142] (2) In this application, "send" and "receive" indicate the direction of signal transmission. For example, "send information to XX" can be understood as the destination of the information being XX, which may include direct transmission via the air interface or indirect transmission via the air interface by other units or modules. "Receive information from YY" can be understood as the source of the information being YY, which may include direct reception from YY via the air interface or indirect reception from YY via the air interface by other units or modules. "Send" can also be understood as the "output" of the chip interface, and "receive" can also be understood as the "input" of the chip interface. In other words, sending and receiving can occur between devices, such as between network devices and terminal devices, or within a device, such as between components, modules, chips, software modules, or hardware modules within the device via a bus, wiring, or interface.

[0143] (3) In the various embodiments of this application, unless otherwise specified or logically conflicting, the terms and / or descriptions of different embodiments are consistent and can be referenced by each other. The technical features of different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0144] (4) In this application, "first" and "second" are used for descriptive convenience only to distinguish objects and are not intended to limit the scope of the embodiments of this application. They are not used to describe the order or sequence of features. It should be understood that the objects described in this way can be interchanged where appropriate so as to describe solutions other than those in the embodiments of this application.

[0145] (5) In this application, “predefined” may mean a standard protocol predefined, or it may mean that the devices have agreed or negotiated in advance.

[0146] (6) In this application, the words “exemplary,” “for example,” etc., are used to indicate examples, illustrations, or descriptions. Any embodiment or design described as an “example” in this application should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of the word “example” is intended to present the concept in a concrete manner. In the embodiments of this application, “of,” “corresponding, relevant,” and “corresponding” may sometimes be used interchangeably, and it should be noted that their intended meanings are consistent unless their distinction is emphasized.

[0147] The methods provided by the embodiments of this application are described in detail below with reference to the accompanying drawings. The embodiments provided by this application can be applied to the communication systems shown in the above figures, and are not limited thereto.

[0148] First, the execution entity in the embodiments of this application is described as follows:

[0149] In this embodiment of the application, as an example, the first device is a terminal device and the second device is a network device. Accordingly, the communication link between the first device and the second device can be an uplink or downlink communication link. The information received by the first device (e.g., first indication information or second indication information, etc.) can be downlink (DL) information / downlink signal / downlink signaling / downlink data, etc., and the information sent by the first device (e.g., first data or first identification information, etc., described below) can be uplink (UL) information / uplink signal / uplink signaling / uplink data, etc.

[0150] As another example, the first device and the second device can be different terminal devices. Accordingly, the communication link between the first device and the second device can be a communication link between terminal devices, such as a side link.

[0151] As another example, the first device can be an A-IoT device (the device can be an example of an implementation of a terminal device), and the second device can be a reader. Accordingly, the communication link between the first device and the second device can include a device-to-reader (DR or D2R) link and a reader-to-device (RD or R2D) link.

[0152] In the embodiments of this application, "uplink" can be replaced with "DR" or "D2R", and "downlink" can be replaced with "RD" or "R2D". For example, "uplink signaling" can be replaced with "D2R signaling".

[0153] Figure 8 is a schematic diagram of a communication method 800 provided in an embodiment of this application. For ease of description, Figure 8 illustrates the interaction between a first device and a second device as an example. The first device can be replaced by a terminal device, an A-IoT device, or a component of an A-IoT device (e.g., a chip, a chip system, a circuit, or a communication module), and the second device can be replaced by a component of a network device (e.g., a chip, a chip system, a circuit, or a communication module), and the second device has the function of a reader / writer. Furthermore, the steps described below as being performed by a single execution entity can also be divided into steps performed by multiple execution entities, which can be logically and / or physically separated. The method 800 shown in Figure 8 may include the following steps.

[0154] S801, the second device sends first time information to the first device, and correspondingly, the first device receives the first time information sent by the second device. The first time information includes a first duration during which the second device does not send the first message.

[0155] The first message includes all messages sent by the second device, or it includes paging messages and access trigger messages sent by the second device. The first device stopping monitoring or receiving messages sent by the second device includes: the first device stopping monitoring or receiving all messages sent by the second device, or the first device stopping monitoring or receiving paging messages and access trigger messages sent by the second device. Optionally, all messages can be all R2D messages sent by the second device, all physical reader-to-device channel (PRDCH) messages sent by the second device, or messages such as stop monitoring / receiving PRDCH / any R2D transmission sent by the second device. Optionally, paging messages include paging messages or select messages, used to paging, select, or trigger one or more devices, and access trigger messages include query messages or queryRep messages.

[0156] Optionally, the Paging message can be used to indicate that the first device accesses the reader. For example, when the reader is a base station / access network device, the Paging message can be used to indicate that the first device accesses the network; when the reader is a terminal device, the Paging message can be used to indicate that the first device accesses the terminal. Optionally, the first device can access the network through the terminal.

[0157] Optionally, the Paging message can also be used to trigger / instruct the first device to send uplink data, or to trigger / instruct / request the first device to perform any of the following services or processes: paging service, inventory service, command service (such as read, write, deactivate, lock, etc.), positioning service, and sensing service.

[0158] Optionally, a Paging message can also be called an (initial) trigger message. Paging messages can be triggered by A-IoT sensing core network nodes (such as AMF, or ambient IoT management function (A-IoT MF), ambient IoT function (AIoTF), etc.). For example, an A-IoT sensing core network node sends a first service request message or paging message to an A-IoT access network node, and the A-IoT access network node sends a Paging message based on the first service request message or paging message. The first service can be a service related to the application scenario, and can be at least one of the following: inventory service, command service, positioning service, sensing service, proximity determination, read service, write service, deactivation service, lock service, or security service (such as authentication, registration, etc.), or it can be a newly defined service type in the future; the specific naming is not limited. For example, an inventory service is when a reader accesses a terminal within its coverage area; a successfully accessed terminal can send its unique identifier to the reader. Location services can use location signals to pinpoint the location of a terminal. Sensing services can involve the terminal reporting sensor data, such as temperature data. Operation command services can execute operation command processes, such as write and lock processes. For example, a write process involves the reader sending instructions and data, instructing the terminal to write data into its memory. A lock process involves the reader sending a downlink command, causing the terminal to lock a specified address in the memory, making the contents of that memory area unchangeable and / or unreadable.

[0159] Optionally, the Paging message can also be called a inventory trigger / instruction / request message or a command trigger / instruction / request message. For example, an inventory trigger / instruction / request message is used to trigger / instruct / request the first device to perform an inventory, while a command trigger / instruction / request message is used to trigger / instruct / request the first device to perform a command.

[0160] Optionally, the Query message can also be called an Access round indication / trigger message, which is used to indicate / trigger at least one access opportunity, such as directly or indirectly indicating the total number of access opportunities, or to trigger the first access opportunity, or to trigger a new round of access, or to trigger the first device that failed to access / data transmission to re-access.

[0161] Optionally, the QueryRep message can also be called an access occasion indication / trigger message, which is used to indicate / trigger the next access occasion. It can also be understood as indicating / associating with the boundary (start or end) of an access occasion.

[0162] The aforementioned access opportunities can also be described as access timing, access time slots, etc. Each access opportunity may allow the first device to send access (request), and / or contention resolution, and / or data transmission, etc.

[0163] Optionally, the paging message may include identification information for selecting / filtering communication devices, such as device ID, mask, group identifier, temporary identifier, permanent identifier (e.g., not lost due to battery level below threshold / depletion), temporary identifier (e.g., only lasts for a period of time and may be lost due to battery level below threshold / depletion), access stratum (AS) ID, etc.

[0164] Optionally, the second device sending first time information to the first device includes: the second device sending first instruction information to the first device, the first instruction information including the first time information.

[0165] The first indication information may indicate that the second device will not send the first message within a first duration, or that the second device will send the first message after the first duration, or that the first indication information may not monitor or receive the first message sent by the second device within the first duration, or that the first indication information may monitor or receive the first message sent by the second device after the first duration. Optionally, the first indication information indicating that the first device may not receive the first message sent by the second device within the first duration includes: the first indication information indicating that the first device enters a sleep state or may enter a sleep state within the first duration. Optionally, the first indication information may indicate that the first device determines whether to enter a sleep state based on its own capabilities; for example, if the first device has sufficient power, it may not enter a sleep state.

[0166] Alternatively, the first indication information may indicate whether the first device is allowed to enter a sleep state. For example, when the first indication information includes first time information, it indicates that the first device is allowed to enter a sleep state; when the first indication information does not include first time information, it indicates that the first device is not allowed to enter a sleep state.

[0167] Optionally, the first indication information may be unscrambled (or without cyclic redundancy check (CRC) code) or may use a common scrambling sequence (or common CRC sequence) so that the device receiving the first indication information can parse the first indication information.

[0168] Optionally, the first instruction message may be sent via broadcast.

[0169] Optionally, the first indication information may use different field values ​​to indicate the type of the first message. For example, the value of the first field may indicate whether the first message is a paging message or an access trigger message. For instance, a value of 0 for the first field indicates that the first message is a paging message, and a value of 1 for the first field indicates that the first message is an access trigger message.

[0170] The first indication information can also serve as a filter for devices. That is, the first indication information may include the device identifier or the device group identifier (such as group number), service identifier, etc.

[0171] Optionally, the first indication information may also include identification information, similar to the mask information of a paging message. This identification information can be a group identifier or mask, etc., so that a subset of devices can be filtered in the first indication information, and only devices that meet the group identifier or mask need to respond to the first indication information. The first indication information indicates that the second device will not send a paging message for the group identifier or mask indicated by the first time information within the specified time period.

[0172] Optionally, the first indication information may further include service identification information to distinguish different service requests. Thus, the first indication information indicates that the first device will not send a first message carrying the included service identification within the time period indicated by the first time information, or that the first device will send a first message carrying the service identification after the time period indicated by the first time information. For example, the first indication information may also include a first session identifier (e.g., session ID = 0). This first indication information indicates that the second device will not send a paging message associated with the first session identifier (session ID = 0) within the time period indicated by the first time information, or that the first device will send a paging message carrying the first session identifier after the time period indicated by the first time information.

[0173] In one possible implementation, different service identification information can be understood as paging messages that trigger different service requests. For example, if the paging message carries the first session identifier of the first service, the first device can choose not to respond to the first session identifier corresponding to the first service, thereby avoiding repeated execution of the same first service and avoiding additional overhead. Specifically, after the first device receives the first service trigger message associated with the first session identifier (session ID = 0) and completes the service (the process related to the first service is successfully completed, such as the inventory service successfully reporting the device ID), according to the first indication information carrying the first session identifier, if the first device receives another first service trigger message associated with the first session identifier within a certain period of time, it will not execute it; if it receives another first service trigger message associated with the second session identifier (session ID ≠ 0) within a certain period of time, it will execute the first service corresponding to the second session identifier.

[0174] The business identification information is associated with the first business. This application does not limit the name of the business identification information. The business identification information can also be called session / transaction / event / task / service / process identification information.

[0175] Optionally, the first indication information may also include a group number, or a procedure number, or a frequency domain resource indication, etc., to indicate that a first message for triggering the associated group number, procedure number, or frequency domain resource will not be sent within the time indicated by the first time information, or the first device may send a first message for triggering the associated group number, procedure number, or frequency domain resource after the time indicated by the first time information.

[0176] The roles of group number, program number, and frequency domain resources are explained below:

[0177] The purpose of group numbering: During inventory or access processes, devices can be divided into different groups (e.g., randomly selecting one group; the total number of groups can be indicated in the paging message). Access trigger messages (e.g., Query / QueryRep messages) can indicate which group's devices are triggered to access; devices in other groups may not respond / participate. The first indication information can be indicated by the group number, signifying that no access trigger messages (or corresponding inventory rounds) for one or more groups have been triggered within a certain period. For example, the first indication information can be indicated by the group number, signifying that no access trigger messages for group M have been triggered within a certain period. Alternatively, the first indication information can be indicated by the group number, signifying that no access trigger messages for groups M, N, and Q have been triggered within a certain period.

[0178] The purpose of the entry sequence number is as follows: Devices can be divided into different processes (e.g., randomly selecting a process; the total number of processes can be indicated in the paging message). Access trigger messages (e.g., Query / QueryRep messages) can indicate which process's access was triggered, and other groups of devices can choose not to respond or participate. Similarly, the first indication information can be indicated by the entry sequence number to show that no access trigger messages for one or more processes have been triggered within a certain period. For example, the first indication information can be indicated by the entry sequence number to show that no access trigger messages for process 1 have been triggered within a certain period. Or, the first indication information can be indicated by the entry sequence number to show that no access trigger messages for processes 1, 2, and 3 have been triggered within a certain period.

[0179] The function of frequency domain resource indication: Each access trigger message can indicate the uplink and / or downlink frequency domains currently in the inventory. The first indication information indicates that the frequency domain resource (uplink or downlink, or D2R / R2D) corresponding to the frequency domain resource (uplink or downlink, or D2R / R2D) will not be initiated for a period of time or will be initiated after a period of time.

[0180] The following describes the method for sending the first instruction information / first-time information.

[0181] Optionally, the first indication information / first time information can be carried in the MAC CE or the MAC header, for example, as one or more fields of the MAC CE or the MAC header. The MAC can be replaced by any other access stratum (AS) protocol layer; for example, the AS is an AS layer defined for A-IoT.

[0182] Optionally, the physical layer of the first device can determine the first time information based on the message frame header (e.g., a preamble sequence) of the first indication information, where the preamble sequence of the first indication information corresponds to the first time information. Optionally, different sequences correspond to different time information.

[0183] It should be understood that the first device is one of the devices used by the second device for paging (which may be alternatively, optional).

[0184] Optionally, not all devices selected or paged by the second device need to receive the first instruction information / first time information.

[0185] For example, the first device that receives the first instruction information / first time information may be a device that satisfies a first condition, wherein the first condition includes any one of the following conditions: not being paged, or failure to access the second device, or failure of data transmission with the second device.

[0186] Here, "not paged" can be replaced with "not selected / not triggered," specifically meaning: no paging message received; or, a paging message received but the identification information carried in the paging message does not match, for example, the device ID of the first device does not match the mask information, such as the first 4 bits of the mask indicating that the first 4 bits are 0101, while the first device ID's first 4 bits are 1000, not 0101, indicating a mismatch; or, no paging message received within a preset time; or, a paging message received within a preset time but the identification information carried in the paging message does not match. The preset time can be pre-configured or indicated by the second device to the first device.

[0187] It should be understood that the first device determining that it has been paged / selected / triggered may include the first device matching the identification information carried in the paging message, such as the first device's device ID matching the mask information. For example, if the first 4 bits of the mask indicator are 0101, and the first 4 bits of the first device's device ID are 0101, then it indicates a match.

[0188] Optionally, the second device may send the first instruction information / first time information to all selected or paged devices, or it may send the first instruction information / first time information only to devices that meet the first condition described above.

[0189] It should be understood that the first device may, for a period of time, cease monitoring or receiving the first message sent by the second device, or enter a dormant state, based on the first instruction information / first time information.

[0190] Optionally, the first device being in a dormant state includes: the first device maintaining all or part of the temporarily stored information, or not maintaining the temporarily stored information.

[0191] Optionally, the first device being in a sleep state includes: the first device receiving / detecting / listening to a portion of specified information, such as wake-up information, which may be a specified sequence or frame header; or, the first device not receiving / detecting / listening to any information.

[0192] Optionally, the first device being in a sleep state includes: the first device starting and maintaining a timer (such as a low-power crystal oscillator) for timing; when the timer expires, the first device exits the sleep state; or, the first device starts monitoring or receiving a first message.

[0193] Optionally, the first device being in a dormant state includes: the first device not sending messages, i.e., shutting down the engine.

[0194] Optionally, the aforementioned sleep mode can include different levels of sleep, such as deep sleep and light sleep. The power consumption of the two sleep modes is different, and the functions they can perform are also different. It should be understood that the specific sleep mode used can be specified by the protocol or based on network instructions (such as instructions in paging messages, where instruction = 0 indicates deep sleep and instruction = 1 indicates light sleep).

[0195] Deep sleep and shallow sleep can be distinguished based on power consumption. For example, deep sleep can be understood as turning off all power-consuming modules, while shallow sleep can retain some modules. The following examples illustrate the distinction between deep sleep and shallow sleep, but this application does not limit it.

[0196] Optionally, shallow hibernation can maintain all or part of the temporarily stored information, while deep hibernation does not maintain the temporarily stored information.

[0197] Optionally, shallow sleep can receive / detect / listen to a portion of specified information, such as wake-up information, which can be a specified sequence or frame header. Deep sleep does not receive / detect / listen to any information.

[0198] Optionally, neither deep sleep nor shallow sleep can send messages, i.e., the engine can be shut down.

[0199] It should be understood that the aforementioned first duration is indicated directly or indirectly by the second device through the first time information.

[0200] Specifically, the first-time information can indicate the first duration. It should be understood that in this application, duration refers to a time length. Duration can be relative time, for example, the granularity of duration can be a frame, subframe, slot, or symbol, etc.; duration can also be absolute time, for example, the granularity of duration can be minutes, seconds, or milliseconds, etc.

[0201] Alternatively, the first-time information can also indicate a time period. It should be understood that a time period refers to a period of time that includes a start time, duration, and end time. If the first-time information indicates a time period, then the first-time information needs to indicate at least two of the start time, duration, and end time of that time period.

[0202] Alternatively, the first time information can indicate some transmission parameters, such as the number of bit repetitions, the preamble length, or the code rate. Thus, the first device can determine the time length corresponding to the first time information based on these parameters.

[0203] Alternatively, the second device may pre-configure and indicate a unit time T0 (which may be dynamically configured), and indicate the number of unit times T0 through the first time information. Optionally, the time interval between at least two downlink messages received by the first device may be set as the unit time T0. For example, if the first device receives two consecutive QueryRep messages, and receives other messages in between (such as unparseable messages), it may skip them, and the time between the two consecutive QueryRep messages may be determined as T0.

[0204] Alternatively, the initial time information can include a number 'a' and a unit 'b', where 'a' is the sleep time and 'b' is the time unit. For example, 'a' = 000 to 111 indicates 10, 20, 30, 50...500 respectively, 'b' = 0 corresponds to ms, and 'b' = 1 corresponds to s (or a default unit, such as ms). If the initial time information indicates 'a' = 000 and 'b' = 0, it means 10ms.

[0205] Alternatively, the initial information can include different indices, each corresponding to a different time. For example, index0 corresponds to 10ms, index1 to 20ms, index2 to 30ms, index3 to 100ms, and so on.

[0206] Alternatively, the first-time information can indicate the number of messages to be received. When the number of messages received by the first device reaches the indicated number, it exits the sleep state (for example, in the sleep state, the headers of some messages can be detected, and the number of messages to be received can be determined based on the number of message headers received).

[0207] Optionally, the first time information may include multiple durations, which correspond to the times when multiple second devices send the first message. For example, the first time information may include 10ms, 1000ms, and 3000ms, thereby indicating that the first paging message is sent at 10ms (or around 10ms), at 1000ms (or around 1000ms), and at 3000ms (or around 3000ms).

[0208] Optionally, after sending the first instruction information / first time information to the first device, the second device stops sending the first message to the first device.

[0209] S802, the second device does not send the first message after a first duration following the transmission of the first time information.

[0210] S803 (optional step): The first device stops monitoring or receives the first message from the second device within a first duration after receiving the first time information.

[0211] Alternatively, the first device may monitor or receive a first message from the second device during a first time period, wherein the start time of the first time period is the time when the first time information is received, and the end time of the first time period is the time after a first duration has elapsed since the first time information was received.

[0212] Optionally, after receiving the first time information, the first device can directly stop monitoring or receive the first message according to the time indicated by the first time information.

[0213] For example, a higher layer of the first device (any layer above the physical layer, such as the MAC layer) obtains the first-time information and then needs to instruct the physical layer to perform actions such as entering sleep mode, stopping monitoring, or receiving the first message.

[0214] For example, the physical layer of the first device obtains first-time information, such as preamble or postamble sequences parsed by the physical layer, which correspond to different time information and / or sleep indications. After the physical layer determines this, it needs to inform the higher layer to perform operations such as pausing business, suspending processes, or discarding / clearing saved temporary information, or instructing the higher layer to start sleep-related timers (the timers may also be maintained by the physical layer).

[0215] In one implementation, the first device can determine a first moment based on a first duration. For example, the first moment is the time elapsed after the first device receives the first time information.

[0216] Furthermore, the first device can determine a first time period. Optionally, the start time of the first time period is the time when the first time information is received, the duration of the first time period is equal to the first duration, and the end time of the first time period is the first time.

[0217] It should be understood that after receiving the first duration, the first device can directly stop monitoring or receive the first message sent by the second device according to that duration, or enter sleep mode.

[0218] For example, if the first duration is 10ms, then the first device will stop monitoring or receiving the first message sent by the second device within 10ms after receiving the first time information. Optionally, the first device will enter a sleep state within 10ms after receiving the first time information.

[0219] Optionally, the start time of the first time period can be determined based on the time when the first time information is received. For example, it can be the moment the first time information is received, or it can be a time after a certain period of time has elapsed since the first time information was received. For example, after the first device receives the first time information, it can include a processing time, such as processing the received message. Optionally, different time lengths may be used for different business scenarios or data types.

[0220] It should be understood that the first time period is the maximum sleep time of the first device after receiving the first time information. The maximum sleep time includes the time between the first device determining that it needs to sleep and the first device needing to receive the first message.

[0221] Alternatively, the first-time information indicates a time period; for example, the first-time information may include a third time period.

[0222] Based on this third time period, the first moment can be determined; for example, the first moment is the end moment of the third time period.

[0223] It should be understood that when the first time information includes a third time period, the first device can determine the first time period for stopping monitoring or receiving the first message sent by the second device based on the third time period.

[0224] Optionally, if the first time period is equal to the third time period, the first device can directly stop monitoring or receiving the first message sent by the second device during the third time period, or enter sleep mode.

[0225] For example, if the third time period begins 1 ms after the first device receives the first time information and lasts for 10 ms, then the first device will stop monitoring or receiving the first message sent by the second device within 10 ms after receiving the first time information. Optionally, the first device may enter a sleep state within 10 ms after receiving the first time information.

[0226] It should be understood that in the above scheme, the end time of the first time period is equal to the first moment.

[0227] Optionally, the end time of the first time period may not be equal to the first moment.

[0228] For example, considering that the first device may have frequency offset, for example, if the first time information indicates that the second device sends the first message to the first device 10ms later, the first device can wake up after the timer counts 10ms. However, the frequency offset will cause 11ms to pass in the actual time, and the first device will not be able to receive the downlink message after waking up.

[0229] To overcome this problem, the first device can wake up before the first duration ends.

[0230] Optionally, after the first device receives the first time information, it can determine a first time period for stopping monitoring or receiving the first message sent by the second device based on the first time information.

[0231] In one implementation, if the first time information indicates a first duration, the first device can determine a first time period based on the first duration.

[0232] Optionally, the start time of the first time period is the time when the first time information is received, the duration of the first time period is shorter than the first duration, and the end time of the first time period is earlier than the first time.

[0233] For example, if the first duration is 10ms, then after receiving the first time information, the first device will stop monitoring or receiving the first message sent by the second device within 9ms. Optionally, the first device will enter a sleep state within 9ms after receiving the first indication information.

[0234] It should be understood that the duration of the first time period is less than the first duration. The exact difference can be determined based on the frequency deviation of the first device. For example, if the frequency deviation of the first device is 10%, then the first device can start monitoring or receiving the first message sent by the second device 10% earlier, that is, the duration of the first time period is 90% of the first duration.

[0235] In another implementation, if the first time information indicates a third time period, then the first device can determine the first time period.

[0236] Optionally, the start time of the first time period is the same as the start time of the third time period, and the end time of the first time period is earlier than the first time period, or in other words, the duration of the first time period is shorter than the duration of the third time period.

[0237] For example, if the start time of the third time period is 1ms after the first device receives the first time information and the duration is 10ms, then the start time of the first time period is 1ms after the first device receives the first time information and the duration is 9ms.

[0238] It should be understood that the duration of the first time period is shorter than the duration of the third time period. The exact difference can be determined based on the frequency deviation of the first device. For example, if the frequency deviation of the first device is 10%, then the first device can start monitoring or receiving the first message sent by the second device 10% earlier, meaning that the duration of the first time period is 90% of the duration of the third time period.

[0239] Based on the above method, the first device can determine a first time period and stop monitoring or receiving a first message from the second device during the first time period.

[0240] Optionally, after determining the first time period, the first device may start a first timer to maintain the first time period. For example, if the duration of the first time period is 10ms, the first device may start a 10ms timer and stop monitoring or receiving the first message from the second device within 10ms. When the timer expires, the first device exits the sleep state, or the first device wakes up, or the first device starts monitoring or receiving the first message from the second device.

[0241] Optionally, after step S802 or step S803, method 800 further includes step S804. Step S804 has three optional implementation methods, including option 1, option 2 and option 3. This application does not limit which option is executed in step S804.

[0242] S804 (option 1): After a first duration following the receipt of the first time information, the first device begins to monitor or receive the first message sent by the second device.

[0243] Correspondingly, the second device sends a first message to the first device after a first duration following the transmission of the first time information.

[0244] Optionally, if step S803 is executed, the first device begins to monitor or receive the first message sent by the second device, including: the first device wakes up, or the first device exits the hibernation state.

[0245] Optionally, since the first device may have frequency offset, it cannot determine whether it missed the first message sent by the second device. Therefore, after waking up, the first device continuously monitors the first message sent by the second device. Optionally, after waking up, the first device continuously and periodically monitors the first message sent by the second device. Optionally, the period of periodic monitoring is pre-configured, for example, predefined; or, the period is indicated to the first device by the second device.

[0246] Optionally, the first device consumes power when monitoring the first message. When the power drops to a preset threshold, the first device can stop monitoring the first message and resume monitoring the first message when the power is fully charged.

[0247] S804 (option 2): After executing step S803, if the first device cannot be woken up / cannot enter the working state (ON) after the first time information is received for a first duration, then continue to stop monitoring or receiving the first message.

[0248] Optionally, the second device sends a first message to the first device after a first duration following receiving the first time information.

[0249] Optionally, after receiving the first time information for a first duration, the second device continues to stop sending the first message to the first device.

[0250] The inability of the first device to be woken up / enter the working state includes: the first device's power level is insufficient to meet the requirements for waking up / entering the working state; or, the first device malfunctions, thus making it impossible to wake up / enter the working state.

[0251] It should be understood that after a first period of time following the receipt of the first time information, the first device may not yet be fully charged, or the first device may not yet have reached the required charge level; in such cases, the first device will continue to stop monitoring or receiving the first message. Optionally, the first device may begin monitoring or receiving the first message sent by the second device after its battery is fully charged.

[0252] Specifically, the first device continuing to stop monitoring or receiving the first message based on the power information includes: when the power of the first device is not fully charged, the first device continues to stop monitoring or receiving the first message.

[0253] Alternatively, the first device continuing to stop monitoring or receiving the first message based on power information includes: when the power of the first device has not reached a preset power level, the first device continues to stop monitoring or receiving the first message. The preset power level may be pre-configured or indicated to the first device by the network or the second device.

[0254] Optionally, the first device begins monitoring or receiving a first message sent by the second device when the battery is fully charged or reaches a preset charge level.

[0255] S804 (option 3): After a first duration following the transmission of the first time information, the second device sends second time information to the first device. Correspondingly, the first device receives the second time information sent by the second device after a first duration following the receipt of the first time information. The second time information includes a second duration during which the second device does not transmit the first message.

[0256] It should be understood that when the second device sends the first time information to the first device, it may not be able to accurately determine the time when the first device needs to sleep. Therefore, the second device may first instruct the first device to sleep for a shorter period of time, and then instruct it to sleep for a more accurate time after the first device wakes up. Optionally, the second duration may be shorter than the first duration.

[0257] Similar to the first time information, the second time information may also be included in the second indication information. The second indication information may also indicate that the second device will not send the first message within the second time period, or indicate that the second device will send the first message after the second time period, or indicate that the first device may not receive the first message sent by the second device within the second time period.

[0258] Similar to the first time information, the second duration can be indicated directly or indirectly through the second time information.

[0259] Specifically, the second time information can directly or indirectly indicate a duration or a time period, so that the first device can determine the second time period for stopping monitoring or receiving the first message sent by the second device based on the duration or time period indicated by the second time information.

[0260] For example, the second device instructs the first device to sleep for 5ms via a first instruction message. After 5ms, the second device then instructs the first device to sleep for another 3ms via a second instruction message. Optionally, after 3ms, the second device can instruct the first device to perform another sleep cycle.

[0261] For example, the second device instructs the first device to sleep for 5ms via the first instruction information. After 5ms, the second device instructs the first device to sleep for another 10ms via the second instruction information. Optionally, after 10ms, the second device can instruct the first device to sleep again.

[0262] The following description, using the method 900 shown in Figure 9 as an example and taking the first device as A-IoT device #1 and the second device as a network device, will illustrate the method 800 shown in Figure 8 above. It should be understood that method 900 is a specific implementation of method 800. In this method 900, if A-IoT device #1 is not paged and needs to monitor paging messages, and the network device will only send a paging message after a first duration (e.g., 10ms), then to save power for A-IoT device #1, the network device can instruct A-IoT device #1 to enter sleep mode within the next 10ms, thereby saving power.

[0263] S901, the network device sends a first indication message to the A-IoT device #1, the first indication message including first time information.

[0264] Among them, the first indication information indicates a duration of 10ms, the first indication information indicates that the network device will send a paging message after 10ms, or the first indication information indicates that the network device will not send a paging message within 10ms, or the first indication information indicates that A-IoT device #1 will enter a sleep state or can enter a sleep state within 10ms after receiving the first indication information, or the first indication information indicates that A-IoT device #1 will monitor the paging message after 10ms.

[0265] Optionally, the network device may send a first indication message to multiple A-IoT devices, including A-IoT device #1, indicating that the network device will send a paging message after 10ms, or the first indication message indicates that the network device will not send a paging message within 10ms.

[0266] For example, the network device simultaneously sends the first indication information to A-IoT device #1, A-IoT device #2, and A-IoT device #3, so that A-IoT device #1, A-IoT device #2, and A-IoT device #3 can all enter sleep mode after receiving the first indication information.

[0267] Optionally, the network device may send a first indication message to the A-IoT device #1 separately. The first indication message indicates that the network device will send a paging message after 10ms, or the first indication message indicates that the network device will not send a paging message within 10ms, or the first indication message indicates that the A-IoT device #1 will enter a sleep state or can enter a sleep state within 10ms after receiving the first indication message.

[0268] For example, the network device sends a first indication message to A-IoT devices #1, #2, and #3 respectively, and the timing of sending the first indication message to A-IoT devices #1, #2, and #3 can be different. As shown in Figure 10, A-IoT devices #1, #2, and #3 are all in a charging state and wake up at different times to monitor paging messages. In this case, the network device can send indication messages to different A-IoT devices when they wake up, instructing them to enter a sleep state.

[0269] As shown in Figure 10, if A-IoT device #1 wakes up first, the network device instructs A-IoT device #1 to sleep for 10ms; 5ms after A-IoT device #1 wakes up, A-IoT device #2 wakes up, and the network device instructs A-IoT device #2 to sleep for 5ms; 3ms after A-IoT device #2 wakes up, A-IoT device #3 wakes up, and the network device instructs A-IoT device #3 to sleep for 2ms.

[0270] S902, network devices do not send paging messages within 10ms.

[0271] S903, after receiving the first instruction information, A-IoT device #1 enters a sleep state that lasts for 10ms.

[0272] Alternatively, to overcome frequency offset, A-IoT device #1 can also wake up earlier, for example, by entering a sleep state that lasts for 9ms.

[0273] Optionally, after receiving the first indication information, A-IoT device #1 can start a 10ms timer and stop monitoring or receiving the first message from the second device within 10ms.

[0274] Optionally, after step S903, method 900 further includes step S904, which has three optional implementations, including option 1, option 2 and option 3. This application does not limit which option is executed in step S904.

[0275] S904 (option 1): After 10ms, A-IoT device #1 exits sleep mode and begins monitoring or receiving paging messages sent by network devices.

[0276] S904 (option 2): If the battery level of A-IoT device #1 is not full or has not reached the preset battery level (e.g., 80%) after 10ms, then A-IoT device #1 will continue to stop monitoring or receiving paging messages.

[0277] Optionally, A-IoT device #1 begins monitoring or receiving paging messages sent by network devices when it is fully charged or reaches a preset power level.

[0278] S904 (option 3): If the network device cannot send a paging message to A-IoT device #1 after 10ms, the network device will instruct A-IoT device #1 to enter sleep mode again.

[0279] The network device then instructs A-IoT device #1 to sleep for another 3ms via a second instruction. Optionally, after 3ms, the network device can instruct A-IoT device #1 to enter sleep mode again.

[0280] The following description, using the method 1100 shown in Figure 11 as an example and taking the first device as A-IoT device #1 and the second device as a network device, will illustrate the method 800 shown in Figure 8 above. It should be understood that method 1100 is a specific implementation of method 800. In this method 1100, if A-IoT device #1 fails to access the network device or fails to transmit data with the network device, and the network device only sends an access trigger message after a first duration (e.g., 10ms), then to save power for A-IoT device #1, the network device can instruct A-IoT device #1 to enter sleep mode within the next 10ms, thereby saving power.

[0281] S1101, the network device sends a first indication message to the A-IoT device #1, the first indication message including first time information.

[0282] Among them, the first time information indicates a duration of 10ms, the first indication information indicates that the network device will send the access trigger message after 10ms, or the first indication information indicates that the network device will not send the access trigger message within 10ms, or the first indication information indicates that A-IoT device #1 will enter a sleep state or can enter a sleep state within 10ms after receiving the first indication information.

[0283] In the first implementation, the network device can send a first indication message to multiple A-IoT devices, including A-IoT device #1. The first indication message indicates that the network device will send an access trigger message after 10ms, or the first indication message indicates that the network device will not send an access trigger message within 10ms.

[0284] For example, the network device simultaneously sends the first indication information to A-IoT device #1, A-IoT device #2, and A-IoT device #3, so that A-IoT device #1, A-IoT device #2, and A-IoT device #3 can all enter sleep mode after receiving the first indication information.

[0285] In the second implementation, the network device can send a first indication message to the A-IoT device #1 separately. The first indication message indicates that the network device will send the access trigger message after 10ms, or the first indication message indicates that the network device will not send the access trigger message within 10ms, or the first indication message indicates that the A-IoT device #1 will enter a sleep state or can enter a sleep state within 10ms after receiving the first indication message, or the first indication message indicates that the A-IoT device #1 will monitor the access trigger message after 10ms.

[0286] For example, after A-IoT devices #1, #2, and #3 fail to connect or transmit data, the network device sends indication information to these devices respectively. As shown in Figure 12, A-IoT devices #1, #2, and #3 fail to connect or transmit data at different times (hereinafter referred to as data transmission failure). In this case, the network device can send indication information to each A-IoT device when it fails to connect or transmit data, instructing the different A-IoT devices to enter a sleep state.

[0287] As shown in Figure 12, if A-IoT device #2 fails to transmit data first, the network device instructs A-IoT device #1 to sleep for 15ms; 5ms after A-IoT device #2 fails to transmit data, A-IoT device #3 fails to transmit data, so the network device instructs A-IoT device #3 to sleep for 12ms; 2ms after A-IoT device #3 fails to transmit data, A-IoT device #1 fails to transmit data, so the network device instructs A-IoT device #1 to sleep for 10ms.

[0288] In the third implementation, if A-IoT device #1 fails to access or transmit data, while A-IoT device #2 successfully transmits data, then A-IoT device #1 needs to monitor the access trigger message, and A-IoT device #2 needs to monitor the paging message. The network device can then send indication information to the two devices respectively, instructing them to sleep for different periods of time.

[0289] For example, the network device sends a first indication message to A-IoT device #1 (the first indication message can be referred to the description of the second implementation above), and the network device sends another indication message to A-IoT device #2, indicating that the network device will send a paging message after 20ms, or indicating that the network device will not send a paging message within 20ms, or indicating that A-IoT device #2 will enter a sleep state or can enter a sleep state within 20ms after receiving the third indication message.

[0290] Optionally, the first indication information may use different field values ​​to indicate the type of the first message. For example, the value of the first field may indicate whether the first message is a paging message or an access trigger message. For instance, a value of 0 for the first field indicates that the first message is a paging message, and a value of 1 for the first field indicates that the first message is an access trigger message.

[0291] S1102, the network device does not send an access trigger message within 10ms.

[0292] S1103, after receiving the first instruction information, A-IoT device #1 enters a sleep state that lasts for 10ms.

[0293] Alternatively, to overcome frequency offset, A-IoT device #1 can also wake up earlier, for example, by entering a sleep state that lasts for 9ms.

[0294] Optionally, after receiving the first indication information, A-IoT device #1 can start a 10ms timer and stop monitoring or receiving the first message from the second device within 10ms.

[0295] Optionally, after step S1103, method 1100 further includes step S1104, which has three optional implementation methods, including option 1, option 2 and option 3. This application does not limit which option is executed in step S1104.

[0296] S1104 (option 1): After 10ms, A-IoT device #1 exits sleep mode and begins monitoring or receiving access trigger messages sent by network devices.

[0297] S1104 (option 2): If the battery level of A-IoT device #1 is not full or has not reached the preset battery level (e.g., 80%) after 10ms, then A-IoT device #1 will continue to stop monitoring or receiving access trigger messages.

[0298] Optionally, A-IoT device #1 begins monitoring or receiving access trigger messages sent by network devices when the battery is fully charged or reaches a preset charge level.

[0299] S1104 (option 3): If the network device cannot send an access trigger message to A-IoT device #1 after 10ms, the network device will again instruct A-IoT device #1 to enter sleep mode.

[0300] The network device then instructs A-IoT device #1 to sleep for another 3ms via a second instruction. Optionally, after 3ms, the network device can instruct A-IoT device #1 to enter sleep mode again.

[0301] The following describes another communication method 1300 provided in the embodiments of this application. Method 1300 is applicable to the case where the second device is a base station and the second device can be composed of CU and DU.

[0302] It should be noted that the technical solutions of communication method 1300 described below can be referenced to the technical solutions of communication method 800 described above. In other words, all the technical solutions of communication method 800 described above are applicable to communication method 1300 described below, and this application will not repeat them here. The following only describes the differences between communication method 1300 and communication method 800 described above.

[0303] Method 1300 may include at least the following steps:

[0304] Optionally, in S1301, the CU in the second device receives prior information sent by the RIC, which includes the charging time and charging power of different devices.

[0305] Optionally, in S1302, the CU in the second device determines, based on prior information, which devices have not yet connected or successfully transmitted data, and / or determines which devices to send the first message to first.

[0306] It should be understood that the sequence number of each process does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0307] It should also be understood that, in the various embodiments of this application, unless otherwise specified or in case of logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced by each other, and the technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships.

[0308] It should also be understood that in some of the above embodiments, exemplary descriptions are mainly based on devices in existing network architectures (such as A-IoT devices or core network elements). It should be understood that the specific form of the device is not limited in the embodiments of this application. For example, any device that can achieve the same function in the future is applicable to the embodiments of this application.

[0309] It is understood that the methods and operations implemented by devices (such as A-IoT devices or core network elements) in the above-described method embodiments can also be implemented by components (such as chips or circuits).

[0310] Those skilled in the art will recognize that, based on the units and algorithm steps described in conjunction with the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is implemented in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0311] The communication device provided in this application is described in detail below with reference to Figures 13 to 15. It should be understood that the description of the device embodiments corresponds to the description of the method embodiments. Therefore, for details not described in detail, please refer to the method embodiments above; for brevity, some details will not be repeated.

[0312] This application embodiment can divide the transmitting or receiving device into functional modules according to the above method examples. For example, each function can be divided into its own functional modules, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware or as a software functional module. It should be noted that the module division in this application embodiment is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods. The following description uses the division of functional modules according to each function as an example.

[0313] Figure 13 is a schematic block diagram of a communication device 1300 provided in an embodiment of this application. The device 1300 includes a transceiver module 1310 and a processing module 1320. The transceiver module 1310 can implement corresponding communication functions, and the processing module 1320 is used for data processing. In other words, the transceiver module 1310 is used to perform operations related to receiving and sending, and the processing module 1320 is used to perform other operations besides receiving and sending. The transceiver module 1310 can also be referred to as a communication interface or a communication unit.

[0314] Optionally, the device 1300 may further include a storage module 1330, which can be used to store instructions and / or data. The processing module 1320 can read the instructions and / or data in the storage module to enable the device to perform the operation of the device in the aforementioned method embodiments.

[0315] In one design, the device 1300 may correspond to the first device in the above method embodiment.

[0316] The device 1300 can implement the steps or processes corresponding to those performed by the first device in the above method embodiments. The transceiver module 1300 can be used to perform transceiver-related operations of the first device in the above method embodiments, and the processing module 1300 can be used to perform processing-related operations of the first device in the above method embodiments.

[0317] In one possible implementation, the transceiver module 1310 is used to receive the first indication information. The processing module 1320 is used to determine a first time period based on the first indication information.

[0318] When the device 1300 is used to execute the method in FIG8, the transceiver module 1310 can be used to execute the step of sending and receiving information in the method, such as S801. The processing module 1320 can be used to execute the processing step in the method, such as S802.

[0319] It should be understood that the specific process of each unit performing the above-mentioned corresponding steps has been described in detail in the above method embodiments, and will not be repeated here for the sake of brevity.

[0320] In another design, the device 1300 may correspond to the second device in the above method embodiment, or to a component of the second device (such as a chip).

[0321] The device 1300 can implement the steps or processes corresponding to those performed by the second device in the above method embodiments. The transceiver module 1310 can be used to perform transceiver-related operations of the second device in the above method embodiments, and the processing module 1320 can be used to perform processing-related operations of the second device in the above method embodiments.

[0322] In one possible implementation, the transceiver module 1310 sends the first instruction information.

[0323] When the device 1300 is used to execute the method in FIG8, the transceiver module 1310 can be used to execute the step of sending and receiving information in the method, such as S801. The processing module 1320 can be used to execute the processing step in the method.

[0324] It should be understood that the specific process of each unit performing the above-mentioned corresponding steps has been described in detail in the above method embodiments, and will not be repeated here for the sake of brevity.

[0325] It should also be understood that the device 1300 here is embodied in the form of a functional module. The term "module" here can refer to an application-specific integrated circuit (ASIC), electronic circuitry, a processor (e.g., a shared processor, a proprietary processor, or a group processor, etc.) and memory for executing one or more software or firmware programs, integrated logic circuitry, and / or other suitable components supporting the described functions. In an alternative example, those skilled in the art will understand that device 1300 may be specifically the first device in the above embodiments, used to execute the various processes and / or steps corresponding to the first device in the above method embodiments; or, device 1300 may be specifically the second device in the above embodiments, used to execute the various processes and / or steps corresponding to the second device in the above method embodiments. To avoid repetition, further details are omitted here.

[0326] The apparatus 1300 of each of the above-described schemes has the function of implementing the corresponding steps performed by the devices (such as the first apparatus and the second apparatus) in the above-described methods. This function can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above-described functions; for example, the transceiver module can be replaced by a transceiver (for example, the transmitting unit in the transceiver module can be replaced by a transmitter, and the receiving unit in the transceiver module can be replaced by a receiver), and other units, such as processing modules, can be replaced by processors, which respectively execute the transceiver operations and related processing operations in each method embodiment.

[0327] In addition, the transceiver module 1310 can also be a transceiver circuit (for example, it may include a receiving circuit and a transmitting circuit), and the processing module 1320 can be a processing circuit.

[0328] Figure 14 is a schematic diagram of another communication device 1400 provided in an embodiment of this application. The device 1400 includes a processor 1410, which is used to execute computer programs or instructions stored in a memory 1420, or to read data / signaling stored in the memory 1420, to perform the methods in the above-described method embodiments. Optionally, there may be one or more processors 1410.

[0329] Optionally, as shown in FIG14, the device 1400 further includes a memory 1420 for storing computer programs or instructions and / or data. The memory 1420 may be integrated with the processor 1410 or may be disposed separately. Optionally, there may be one or more memories 1420.

[0330] Optionally, as shown in FIG14, the device 1400 further includes a transceiver 1430 for receiving and / or transmitting signals. For example, a processor 1410 is used to control the transceiver 1430 to receive and / or transmit signals.

[0331] As one option, the device 1400 is used to implement the operations performed by the first device in the various method embodiments described above.

[0332] As an alternative, the device 1400 is used to perform the operations performed by the second device in the various method embodiments described above.

[0333] It should be understood that the processor mentioned in the embodiments of this application can be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor can be a microprocessor or any conventional processor.

[0334] It should also be understood that the memory mentioned in the embodiments of this application can be volatile memory and / or non-volatile memory. Non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM). For example, RAM can be used as an external cache. By way of example and not limitation, RAM includes the following forms: static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM).

[0335] It should be noted that when the processor is a general-purpose processor, DSP, ASIC, FPGA, or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component, the memory (storage module) can be integrated into the processor.

[0336] It should also be noted that the memory described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0337] Figure 15 is a schematic diagram of a chip system 1500 provided in an embodiment of this application. The chip system 1500 (or may also be called a processing system) includes logic circuitry 1510 and an input / output interface 1520.

[0338] The logic circuit 1510 can be a processing circuit in the chip system 1500. The logic circuit 1510 can be coupled to a memory unit, calling instructions from the memory unit, enabling the chip system 1500 to implement the methods and functions of the embodiments of this application. The input / output interface 1520 can be an input / output circuit in the chip system 1500, outputting processed information from the chip system 1500, or inputting data or signaling information to be processed into the chip system 1500 for processing.

[0339] As one approach, the chip system 1500 is used to implement the operations performed by the first device and the second device in the various method embodiments described above.

[0340] For example, logic circuit 1510 is used to implement the processing-related operations performed by the first device and the second device in the above method embodiment; input / output interface 1520 is used to implement the sending and / or receiving-related operations performed by the first device and the second device in the above method embodiment.

[0341] This application also provides a computer-readable storage medium storing computer instructions for implementing the methods executed by the first core network element and the communication device in the above-described method embodiments.

[0342] For example, when the computer program is executed by the computer, it enables the computer to implement the methods performed by the first device and the second device in the various embodiments of the above methods.

[0343] This application also provides a computer program product comprising instructions which, when executed by a computer, implement the methods performed by the first device and the second device in the above-described method embodiments.

[0344] This application also provides a communication system, including the aforementioned first device and second device.

[0345] The explanations and beneficial effects of the relevant contents in any of the devices provided above can be found in the corresponding method embodiments provided above, and will not be repeated here.

[0346] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection of apparatus or units may be electrical, mechanical, or other forms.

[0347] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0348] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0349] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0350] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0351] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0352] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0353] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A communication method applied to a first device, characterized in that, comprising: receiving first time information when the first device is not paged, or the first device fails to access a second device, or data transmission between the first device and the second device fails, the first time information comprising a first duration in which the second device does not transmit a first message.

2. The method of claim 1, wherein, The method further comprises: communicating with the second device according to the first time information.

3. The method according to claim 1 or 2, characterized in that, The method further comprises: monitoring or receiving the first message after the first duration of receiving the first time information.

4. The method according to claim 1 or 2, characterized in that, The method further comprises: receiving second time information after the first duration of receiving the first time information, the second time information comprising a second duration in which the second device does not transmit the first message.

5. The method according to any one of claims 1 to 4, characterized in that, The method further comprises: stopping monitoring or receiving the first message within the first duration of receiving the first time information.

6. The method of claim 5, wherein, The stopping monitoring or receiving the first message within the first duration of receiving the first time information comprises: being in a sleep state within the first duration of receiving the first time information.

7. The method according to any one of claims 3 to 6, characterized in that, The method further comprises: starting a first timer with a duration of the first duration when the first time information is received; the first duration of receiving the first time information comprises after the first timer expires.

8. The method according to any one of claims 1 to 7, characterized in that, The first message comprises a paging message or an access trigger message. 9.A communication method applied to a second device, the method comprising: comprising: transmitting first time information to a first device, the first time information comprising a first duration in which the second device does not transmit a first message; not transmitting the first message within the first duration of transmitting the first time information.

10. The method of claim 9, wherein, Before transmitting the first time information to the first device, the method further comprises: determining that the first device satisfies a first condition, the first condition comprising any one of the following conditions: the first device is not paged, or the first device fails to access the second device, or data transmission between the first device and the second device fails.

11. The method according to claim 9 or 10, characterized in that, The first message comprises a paging message or an access trigger message.

12. The method according to any one of claims 9 to 11, characterized in that, The method further comprises: transmitting the first message after the first duration of transmitting the first time information.

13. The method according to any one of claims 9 to 11, characterized in that, The method further comprises: transmitting second time information after the first duration of transmitting the first time information, the second time information comprising a second duration in which the second device does not transmit the first message.

14. The method according to any one of claims 9 to 11, characterized in that, The method further comprises: transmitting third time information before the first duration of transmitting the first time information, the third time information comprising a third duration in which the second device does not transmit the first message.

15. A communications device, characterized by The communication device is configured to perform the method of any one of claims 1-8 or 9-14.

16. A communications device, characterized by The communication device comprises at least one processor and at least one memory, the at least one memory is configured to store computer programs or instructions, and the at least one processor is configured to execute the computer programs or instructions in the memory, so that the method of any one of claims 1-8 is performed, or so that the method of any one of claims 9-14 is performed.

17. A computer-readable storage medium, characterized in that, The computer program or instructions are stored on a computer readable storage medium, and when the computer program or instructions are run on a computer, the method of any one of claims 1-8 is performed, or the method of any one of claims 9-14 is performed.

18. A computer program product, characterised in that, The computer program product, when run on a computer, causes the method of any one of claims 1-8 to be performed, or the method of any one of claims 9-14 to be performed.

Images