Scheduling method for amp IoT device, and apparatus, device and medium

Abstract

The present application belongs to the field of wireless communications. Disclosed are a scheduling method for an AMP IoT device, and an apparatus, a device and a medium. The method comprises: sending first signaling, wherein the first signaling is used for scheduling or triggering AMP IoT device transmission, and the first signaling carries first indication information and / or second indication information, the first indication information indicating device information of the AMP IoT device scheduled or triggered by the first signaling, and the second indication information indicating an AMP IoT transmission mode scheduled or triggered by the first signaling. The present application supports that flexible scheduling and accurate scheduling of AMP IoT devices are implemented by means of first signaling.

Description

AMP IoT device scheduling methods, devices, equipment and media Technical Field

[0001] This application relates to the field of wireless communication, and in particular to a scheduling method, apparatus, device, and medium for AMP IoT devices. Background Technology

[0002] If the communication system supports the coexistence of different AMP IoT devices, and even the coexistence of AMP IoT devices and traditional UEs, then how the network should selectively schedule different AMP IoT devices in such a complex hybrid deployment communication scenario is a problem that needs to be solved.

[0003] Summary of the Invention

[0004] This application provides a scheduling method, apparatus, device, and medium for AMP IoT devices, the technical solution of which includes at least:

[0005] According to one aspect of the embodiments of this application, a scheduling method for an AMP IoT device is provided, the method comprising:

[0006] Send a first signaling message, which is used to schedule or trigger AMP IoT device transmission. The first signaling message carries first indication information and / or second indication information. The first indication information indicates the device information of the AMP IoT device scheduled or triggered by the first signaling message, and the second indication information indicates the AMP IoT transmission mode scheduled or triggered by the first signaling message.

[0007] According to another aspect of the embodiments of this application, a scheduling method for an AMP IoT device is provided, the method comprising:

[0008] Receive a first signaling message, which is used to schedule or trigger AMP IoT device transmission. The first signaling message carries a first indication information and / or a second indication information. The first indication information indicates the device information of the AMP IoT device scheduled or triggered by the first signaling message, and the second indication information indicates the AMP IoT transmission mode scheduled or triggered by the first signaling message.

[0009] According to one aspect of the embodiments of this application, a communication device is provided, the device comprising:

[0010] The sending module is used to send a first signaling message, which is used to schedule or trigger the transmission of AMP IoT devices. The first signaling message carries first indication information and / or second indication information. The first indication information indicates the device information of the AMP IoT device scheduled or triggered by the first signaling message, and the second indication information indicates the AMP IoT transmission mode scheduled or triggered by the first signaling message.

[0011] According to another aspect of the embodiments of this application, a communication device is provided, the device comprising:

[0012] The receiving module is configured to receive a first signaling message, which is used to schedule or trigger AMP IoT device transmission. The first signaling message carries first indication information and / or second indication information. The first indication information indicates the device information of the AMP IoT device scheduled or triggered by the first signaling message, and the second indication information indicates the AMP IoT transmission mode scheduled or triggered by the first signaling message.

[0013] According to one aspect of the embodiments of this application, a communication device is provided, the communication device comprising: a processor; a transceiver connected to the processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to load and execute the executable instructions to implement the scheduling method of AMP IoT devices as described in the foregoing aspects.

[0014] According to another aspect of the embodiments of this application, a communication device is provided, the communication device comprising: a receiver; the communication device is configured to implement the scheduling method for AMP IoT devices as described in the foregoing aspects.

[0015] According to one aspect of the embodiments of this application, a computer-readable storage medium is provided, which stores at least one program that is loaded and executed by a processor to implement the scheduling method for AMP IoT devices as described in the foregoing aspects.

[0016] According to one aspect of the embodiments of this application, a computer program product or computer program is provided, the computer program product or computer program including computer instructions stored in a computer-readable storage medium, a processor obtaining the computer instructions from the computer-readable storage medium, and the processor executing the computer instructions to implement the scheduling method of AMP IoT devices as described in the above aspects.

[0017] According to one aspect of the embodiments of this application, a chip is provided, the chip including a programmable logic circuit and / or at least a program, the chip being used to implement the scheduling method of AMP IoT devices as described in the above aspects based on the programmable logic circuit and / or the at least a program.

[0018] The technical solutions provided in this application embodiment may include the following beneficial effects:

[0019] Since the first signaling can indicate the device information and / or transmission method of the AMP IoT device, and different AMP IoT devices can be distinguished by device information and transmission method, the receiver of the first signaling can determine whether it has been scheduled or triggered based on the indication information carried by the first signaling, thereby realizing precise and flexible scheduling of AMP IoT devices. Attached Figure Description

[0020] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0021] Figure 1 shows a schematic diagram of a wireless communication system provided in an exemplary embodiment of this application;

[0022] Figure 2 illustrates a schematic diagram of a communication-free system provided in an exemplary embodiment of this application;

[0023] Figure 3 shows a schematic diagram of radio frequency energy harvesting provided in an exemplary embodiment of this application;

[0024] Figure 4 shows a schematic diagram of a backscatter communication process provided in an exemplary embodiment of this application;

[0025] Figure 5 shows a schematic diagram of resistive load modulation provided in an exemplary embodiment of this application;

[0026] Figure 6 shows a schematic diagram of a topology provided in an exemplary embodiment of this application;

[0027] Figure 7 shows a schematic diagram of a topology provided in an exemplary embodiment of this application;

[0028] Figure 8 shows a schematic diagram of an encoding method provided in an exemplary embodiment of this application;

[0029] Figure 9 shows a flowchart of a scheduling method provided in an exemplary embodiment of this application;

[0030] Figure 10 shows a flowchart of a scheduling method provided in an exemplary embodiment of this application;

[0031] Figure 11 shows a schematic diagram of a scheduling method provided in an exemplary embodiment of this application;

[0032] Figure 12 shows a schematic diagram of a scheduling method provided in an exemplary embodiment of this application;

[0033] Figure 13 shows a schematic diagram of a scheduling method provided in an exemplary embodiment of this application;

[0034] Figure 14 shows a schematic diagram of a scheduling method provided in an exemplary embodiment of this application;

[0035] Figure 15 shows a schematic diagram of a scheduling method provided in an exemplary embodiment of this application;

[0036] Figure 16 shows a schematic diagram of a scheduling method provided in an exemplary embodiment of this application;

[0037] Figure 17 shows a schematic diagram of a scheduling method provided in an exemplary embodiment of this application;

[0038] Figure 18 shows a schematic diagram of a scheduling method provided in an exemplary embodiment of this application;

[0039] Figure 19 shows a schematic diagram of a scheduling method provided in an exemplary embodiment of this application;

[0040] Figure 20 shows a flowchart of a scheduling method provided in an exemplary embodiment of this application;

[0041] Figure 21 shows a structural block diagram of a communication device provided in an exemplary embodiment of this application;

[0042] Figure 22 shows a structural block diagram of a communication device provided in an exemplary embodiment of this application;

[0043] Figure 23 shows a schematic diagram of the structure of a communication device provided in an exemplary embodiment of this application;

[0044] Figure 24 shows a schematic diagram of the structure of a communication device provided in an exemplary embodiment of this application. Detailed Implementation

[0045] To make the objectives, technical solutions, and advantages of this application clearer, the embodiments of this application will be further described in detail below with reference to the accompanying drawings. Exemplary embodiments will be described in detail here, examples of which are illustrated in the accompanying drawings. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0046] The terminology used in this application is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. The singular forms “a,” “the,” and “the” used in this application and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used herein refers to and includes any or all possible combinations of one or more of the associated listed items.

[0047] It should be understood that although the terms first, second, third, etc., may be used in this application to describe various information, this information should not be limited to these terms. These terms are only used to distinguish information of the same type from one another. For example, without departing from the scope of this application, first information may also be referred to as second information, and similarly, second information may also be referred to as first information. Depending on the context, the word "if" as used herein can be interpreted as "when," "when," or "in response to determination." In this specification, when expressing the meaning of Boolean Values, it is expressed that "0" represents "first meaning" and "1" represents "second meaning." Without loss of generality, those skilled in the art will understand that the meanings they represent can be interchanged, that is, "1" represents "first meaning" and "0" represents "second meaning."

[0048] The technical solutions described in some embodiments of this application can be applied to various communication systems, such as: Wireless Local Area Networks (WLAN) systems, Wireless Fidelity (Wi-Fi) systems, New Radio (NR) systems, subsequent evolution systems of NR systems, 5th Generation (5G) systems, Advanced 5th Generation (5G-A) systems, Beyond 5th Generation (B5G) systems, 6G systems, subsequent evolution systems of 6G systems, Long Term Evolution (LTE) systems, Advanced Long Term Evolution (LTE-A) systems, LTE-Based Access to Unlicensed Spectrum (LTE-U) systems, NR-Based Access to Unlicensed Spectrum (NR-U) systems, cellular Internet of Things (IoT) systems, and Global System for Mobile Communications (GSM). Communication systems include GSM (Global System for Mobile Communications), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), General Packet Radio Service (GPRS), Terrestrial Networks (TN), Non-Terrestrial Networks (NTN), Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX), Global Positioning System (GPS), and Radio Frequency Identification (RFID).Among them, 5G systems and their subsequent evolution systems can adopt a non-standalone (NSA) network architecture or a standalone (SA) network architecture.

[0049] Figure 1 shows a schematic diagram of a wireless communication system 100 provided in an exemplary embodiment of this application. The wireless communication system 100 includes terminal devices with terminal devices, or terminal devices with network devices, or stations (STAs) with stations, which are not limited in this application.

[0050] The network equipment in this application supports wireless communication functions, including but not limited to: base stations (BS), node Bs (NBs), evolved node Bs (eNBs), next-generation node Bs (gNBs), radio network controllers (RNCs), base station controllers (BSCs), base transceiver stations (BTSs), home evolved node Bs or home node Bs (HNBs), baseband units (BBUs), remote radio units (RRUs), distributed units (DUs), wireless relay nodes, wireless backhaul nodes, transmission points (TPs), transmission and reception points (TRPs), antenna panels, routers, readers, etc.

[0051] The terminal equipment in this application, also known as user equipment (UE), includes, but is not limited to: mobile phones, tablets, e-book readers, laptops, desktop computers, televisions, virtual reality (VR) devices, augmented reality (AR) devices, mixed reality (MR) devices, extended reality (XR) devices, remote terminals, set-top boxes, vehicle communication equipment, handheld devices, wearable devices, wireless devices in industrial control, wireless devices in self-driving, wireless devices in remote medical care, wireless devices in smart grids, wireless devices in transportation safety, wireless devices in smart cities, wireless devices in smart homes (such as smart cameras, smart remote controls, smart water and electricity meters, etc.), wireless communication chips, application-specific integrated circuits (ASICs), systems-on-chips (SoCs), Internet of Things (IoT) nodes, and vehicle-to-everything (V2X) networks. Vehicles (IoV) nodes, sensors, etc., can also be computing devices with wireless communication capabilities or other processing devices connected to a wireless modem.

[0052] Figure 1(a) shows an example of a wireless communication system 100 including network device 110 and terminal device 120.

[0053] In some embodiments, both network device 110 and terminal device 120 support the 3rd Generation Partnership Project (3GPP) protocol, but are not limited to the 3GPP protocol.

[0054] In this application, STA can include Access Point STA (AP STA) and / or Non-Access Point STA (non-AP STA). An AP STA can be simply referred to as an AP. Communication between STAs can be between an AP and a non-AP STA, between two non-AP STAs, or between a STA and a peer STA. A peer STA refers to the device communicating with the STA; a peer STA can be an AP or a non-AP STA.

[0055] Figure 1(b) shows an example of a wireless communication system 100 including an AP 130 and a non-AP STA 140.

[0056] In some embodiments, AP 130 is a device deployed in a WLAN / Wi-Fi system to provide wireless communication functionality for STAs. AP 130 provides wireless access services and acts as a bridge between wired and wireless networks. AP 130 can be a terminal device or network device with a WLAN / Wi-Fi chip. Non-AP STA 140 can be a terminal device with a WLAN / Wi-Fi chip.

[0057] In some embodiments, the AP 130 supports the Institute of Electrical and Electronics Engineers (IEEE) 802.11 family of standard protocols, such as 802.11bp, 802.11be, 802.11ax, 802.11ac, 802.11n, 802.11g, 802.11b, and 802.11a, among other current and future WLAN standards. The AP 130 can also be used in network environments that support next-generation WLAN systems / next-generation Wi-Fi communications.

[0058] In some embodiments, the non-AP STA 140 supports standard protocols of the IEEE 802.11 family, such as 802.11bp, 802.11be, 802.11ax, 802.11ac, 802.11n, 802.11g, 802.11b, and 802.11a, among other current and future WLAN standards. The non-AP STA 140 can also be used in network environments that support next-generation WLAN systems / next-generation Wi-Fi communication.

[0059] In this embodiment, the next-generation WLAN system is an evolution of the 802.11be system and is backward compatible with the 802.11be system. Next-generation Wi-Fi communication refers to any new generation of Wi-Fi communication after Wi-Fi 7 based on the IEEE 802.11be standard, such as Ultra High Reliability (UHR) communication.

[0060] It's understandable that the role of a STA in wireless communication is not absolute. For example, when phone A is connected to a router, phone A is a non-AP STA, but when phone A acts as a hotspot for phone B, phone A acts as an AP.

[0061] In some embodiments, both AP 130 and non-AP STA 140 support the IEEE 802.11 protocol, but are not limited to the IEEE 802.11 protocol.

[0062] In some embodiments, there are one or more links between AP 130 and non-AP STA 140.

[0063] In some embodiments, AP 130 and non-AP STA 140 support multi-band communication. For example, they can communicate simultaneously in at least one of the frequency bands such as 2.4 GHz, 5 GHz, 6 GHz, 45 GHz, and 60 GHz. Alternatively, they can communicate simultaneously on different channels within the same frequency band or on different channels in different frequency bands. Multi-band communication can improve the throughput and / or reliability of communication between devices. Such a device supporting multi-band communication can be considered to have multi-link operation (MLO) capability and is commonly referred to as a multi-band device or multi-link device (MLD), sometimes also called a multi-band entity or multi-link entity. An MLD can be an AP device or a non-AP STA device. If an MLD is an AP device, it contains one or more APs; if an MLD is a non-AP STA device, it contains one or more non-AP STAs. Multiple links can be formed between APs in an AP MLD and STAs in a STA MLD, and communication can occur between APs in an AP MLD and STAs in a STA MLD through the corresponding links.

[0064] In some embodiments, the frequency bands supported by the wireless communication system 100 include, but are not limited to: millimeter wave (mmWave) bands (such as 45GHz, 60GHz, etc., which belong to the 30-300GHz range) and low-frequency bands. Among them, low-frequency bands include Sub-7GHz bands (such as 2.4GHz, 5GHz, 6GHz, etc., which belong to the 1-7.25GHz range).

[0065] • Regarding zero-power devices:

[0066] With the development of communication technology and the expansion of communication needs, the demand for low-power communication equipment is becoming increasingly urgent. Therefore, zero-power communication technology is introduced to reduce power consumption on the UE side. Zero-power communication technology can also be referred to as at least one of the following: ultra-low-power communication technology, low-power communication technology, etc. Communication equipment used to implement zero-power communication technology can be called zero-power device, and zero-power device can also be referred to as at least one of the following: ultra-low-power device, low-power device, etc.

[0067] Specifically, from the perspective of energy source and usage, zero-power devices can be divided into the following three types:

[0068] (1) Passive Devices: Passive devices do not require an internal battery. When a passive device approaches a network device (such as a reader in an RFID system), it is within the near-field range formed by the antenna radiation of the network device. Therefore, the passive device's antenna generates an induced current through electromagnetic induction, which drives the low-power chip circuitry of the passive device. This enables demodulation of the forward link signal and modulation of the backward link signal. For backscatter links, passive devices can use backscatter or extremely low-power active transmission methods to transmit signals. Since passive devices do not require an internal battery to drive either the forward or backward link, they can be considered truly zero-power devices.

[0069] Besides not needing batteries, passive devices also have very simple RF and baseband circuits. For example, they do not require low-noise amplifiers (LNAs), power amplifiers (PAs), crystal oscillators, analog-to-digital converters (ADCs), etc., which makes passive devices have many advantages such as small size, light weight, very low price, and long service life.

[0070] In addition to electromagnetic induction, passive devices can also support other energy harvesting methods. By harvesting energy from the environment (such as radio frequency energy, light energy, heat energy, kinetic energy, mechanical energy, etc.), they can obtain energy for the drive circuit to achieve communication.

[0071] (2) Semi-passive devices; semi-passive devices do not have conventional batteries installed. They collect environmental energy such as radio wave energy, solar energy, light energy, thermal energy, kinetic energy, and mechanical energy through an energy harvesting module, and store the collected energy in an energy storage unit (such as a capacitor). After obtaining energy, the energy storage unit can drive the low-power chip circuit of the semi-passive device. This enables the demodulation of forward link signals and the modulation of backward link signals. For backscatter links, semi-passive devices can use backscatter or low-power active transmission methods to transmit signals.

[0072] Semi-passive devices do not require built-in batteries to drive either the forward or reverse link. Although they use energy stored in capacitors during operation, this energy comes from ambient energy harvested by the energy harvesting module. Therefore, semi-passive devices can be considered true zero-power devices. Semi-passive devices inherit many advantages of passive devices, such as small size, light weight, very low price, and long service life.

[0073] (3) Active devices; Active devices can have built-in batteries. The batteries drive the low-power chip circuits of the active devices, enabling demodulation of forward link signals and modulation of backward link signals. The reverse link signal transmission of active devices can be achieved without consuming the power of the active devices themselves, through backscattering. Alternatively, the active devices can achieve reverse link transmission through low-power active transmission. Although they have built-in batteries, these active devices have extremely low power consumption and complexity, so the battery capacity can be set within a small range, thus achieving lower cost and size. The built-in batteries of active devices can also serve as energy storage units to store the environmental energy collected by the energy harvesting module, thereby making the maintenance cycle of active devices longer, or even maintenance-free.

[0074] Active devices utilize built-in batteries for power, increasing communication distance and improving communication reliability. Therefore, active devices are used in scenarios with relatively high requirements for communication distance and read latency.

[0075] Specifically, from the perspective of transmitter type, zero-power devices can be divided into the following three types:

[0076] (1) Devices equipped with a backscatter module use the backscattering method described above for uplink transmission. These devices do not have an active transmitter for active transmission; they only have a transmitter with a backscatter module. Therefore, when performing uplink transmission, other devices are required to provide a carrier wave, and these devices achieve uplink transmission by performing backscattering based on the carrier wave.

[0077] (2) Devices equipped with active transmitters use active transmitters with active transmission capabilities for uplink transmission. Therefore, such devices can send uplink data using their own active transmitters without requiring an external carrier. Suitable active transmitters for this type of device include, for example, low-power Amplitude Shift Keying (ASK) transmitters and low-power Frequency Shift Keying (FSK) transmitters. Based on current implementations, such transmitters can reduce the overall power consumption of the device to 400–600 μW when transmitting a 100 microwatt (μW) signal.

[0078] (3) Devices that simultaneously possess a backscatter module and an active transmitter support both backscatter and active transmission. Such devices can determine whether to use backscatter or an active transmitter for transmission based on different situations (such as different power levels, different available environmental energy, etc.) or on the scheduling of network devices.

[0079] • About Cellular Passive Internet of Things:

[0080] Cellular IoT is booming, and 3GPP has standardized some IoT technologies, but many IoT communication needs in various scenarios remain unmet, such as:

[0081] • Harsh communication environment;

[0082] Some IoT scenarios may face extreme environments such as high temperatures, extremely low temperatures, high humidity, high pressure, high radiation, or high-speed movement. Examples include ultra-high-voltage substations, high-speed train track monitoring, environmental monitoring in frigid regions, and industrial production lines. In these scenarios, existing IoT terminals will be unable to function due to the limitations of conventional power supplies. Furthermore, extreme working environments are also detrimental to IoT maintenance, such as battery replacement.

[0083] • The need for extremely small terminal form factors;

[0084] In certain IoT communication scenarios, such as food traceability, commodity distribution, and smart wearables, terminals require extremely small sizes for convenient use in these environments. For example, IoT terminals used for commodity management in the distribution process typically use electronic tags, embedded in very small packages. Furthermore, lightweight wearable devices can enhance the user experience while meeting user needs.

[0085] • The need for extremely low-cost IoT communication.

[0086] Numerous IoT communication scenarios require IoT terminals to be sufficiently inexpensive to enhance their competitiveness compared to other alternative technologies. For example, in logistics or warehousing scenarios, to facilitate the management of large quantities of goods in circulation, IoT terminals can be attached to each item, enabling precise management of the entire logistics process and lifecycle through communication between the terminal and the logistics network. These scenarios necessitate that IoT terminals be priced competitively.

[0087] Therefore, to cover these unmet communication needs, cellular IoT also requires the development of ultra-low-cost, extremely small-sized, battery-free, and maintenance-free IoT, and zero-power IoT can precisely meet this requirement. In standardization discussions, zero-power IoT can also be called Ambient Power Enabled IoT, or simply AMP IoT / Ambient IoT / A-IoT / AMP, etc., and some technical documents also refer to it as Passive IoT.

[0088] Zero-power IoT devices, also known as ambient energy IoT devices or passive IoT devices, are abbreviated as AMP IoT devices / Ambient IoT devices / A-IoT devices / AMP devices. The energy required for AMP IoT devices to operate comes from energy harvesting from the environment, such as radio frequency energy, radiation energy, light energy, heat energy, kinetic energy, and mechanical energy. AMP IoT devices that harvest radio frequency energy to power themselves may require other devices to provide them with radio frequency power signals. AMP IoT devices may have no energy storage capacity or very limited energy storage capacity, such as using a capacitor with a capacitance of only tens of microfarads (μF).

[0089] Based on 3GPP's discussion of Ambient IoT application scenarios, Ambient IoT can be applied to at least the following four types of scenarios: 1. Object recognition, such as logistics, production line product management, and supply chain management; 2. Environmental monitoring, such as monitoring temperature, humidity, and harmful gases in the working environment and natural environment; 3. Positioning, such as indoor positioning, smart object finding, and production line item positioning; 4. Smart control, such as smart control of various electrical appliances in smart homes (turning on and off air conditioners, adjusting temperature), and smart control of various facilities in agricultural greenhouses (automatic irrigation, fertilization).

[0090] The 3GPP RAN research report broadly categorizes AMP IoT devices into three types, each with corresponding complexity and communication capabilities: Device A: Lacking energy storage capacity and unable to transmit independent signals; it uses backscattering transmission. Device B: Possesses energy storage capacity, also unable to transmit independent signals, but uses backscattering transmission and can amplify the backscattered signal using stored energy. Device C: Possesses energy storage capacity and can transmit independent signals, possessing active transmission capability. Device A has the lowest complexity and power consumption, as low as 1 microwatt (μW), but its communication distance is limited, typically only a few meters. Device A requires a carrier signal from the network device for backscattering transmission. Device C typically has a large-capacity capacitor to store energy from the environment, supporting power consumption of several hundred microwatts, and can support active signal transmission with a longer communication distance. Because Device C can transmit actively, it does not require a carrier signal from the network device. Device B's complexity and power consumption fall between those of Device A and Device C.

[0091] The overall goal of the Ambient IoT Devices research project in 3GPP is to study a unified air interface design, minimizing differences (if necessary), to achieve support for at least the following two types of AMP IoT devices:

[0092] Type i: Peak power consumption of approximately 1μW, with energy storage capability, up to 10 x The initial sampling frequency offset (SFO) in ppm (parts per million) is not amplified for either downlink or uplink transmissions in AMP IoT devices. Uplink transmission in AMP IoT devices is achieved through backscattering on an externally provided carrier. Here, x is greater than 0.

[0093] Type ii: Peak power consumption less than several hundred microwatts, with energy storage capacity, up to 10 x The initial sampling frequency offset in ppm can be amplified for downlink and / or uplink transmissions of AMP IoT devices. Uplink transmissions of AMP IoT devices can be generated internally (i.e., actively transmitted) or achieved through backscattering on an externally provided carrier. Here, x is greater than 0.

[0094] Type i devices have lower peak power consumption than Type ii devices. Type i devices use backscatter communication for uplink transmission, a compromise between Device A and Device B in the RAN study report (possessing energy storage capability but unable to amplify the signal). Type ii devices have higher peak power consumption and can use either active transmission or backscatter communication for uplink transmission. When using active transmission, Type ii devices are similar to Device C in the RAN study report; when using backscatter communication, they are similar to Device B.

[0095] In addition, 3GPP R19 also discusses several service types that AMP IoT devices may participate in, each with corresponding service characteristics:

[0096] • Device-Originated (DO) services: For AMP IoT devices, this refers to services in which the AMP IoT device sends signaling / data to network devices and / or intermediate nodes. These can be initiated by the AMP IoT device itself or triggered by a specific event. Examples include Ambient IoT data reporting, data transmission, and signaling transmission.

[0097] • Device-Terminated (DT) Service: For AMP IoT devices, this refers to the service where network devices and / or intermediate nodes send signaling / data to the AMP IoT device. For example, a network device sends control signaling to an AMP IoT device, and the AMP IoT device executes the corresponding operation.

[0098] • Device-Originated Autonomous (DO-A) Service: For AMP IoT devices, this refers to the service where the AMP IoT device autonomously initiates the sending of signaling / data to network devices and / or intermediate nodes, and is a type of DO service. For example, an AMP IoT device sends alarm information to network devices and / or intermediate nodes.

[0099] • Device-Terminated Triggered (DO-DTT): Services initiated and terminated by the AMP IoT device itself, triggered by network devices and / or intermediate nodes. Typical examples include asset inventory and sensor sensing services. For instance, triggering the AMP IoT device to report its own identifier (ID) information or sensor data.

[0100] IEEE has also launched a research project on Ambient IoT Devices, broadly categorizing AMP IoT devices into two types, each with corresponding complexity and communication capabilities: 1) Ambient-only IoT Devices: These operate using ambient energy, have little or no energy storage, and employ backscattering or active transmission methods, consuming less than 1 milliwatt (mW). Coverage range reaches 30 meters indoors and 100 meters outdoors. 2) Ambient-assisted IoT Devices: Similar to existing 802.11 devices, these reuse existing physical layer designs, operate using ambient energy, and have energy storage capabilities. Coverage range reaches 30 meters indoors and 200 meters outdoors.

[0101] Figure 2 illustrates a wireless communication system 200 provided in an exemplary embodiment of this application, including a network device 210 and an AMP IoT device 220. The network device 210 may be a base station, access point (AP), reader, or other device providing wireless communication functionality as shown in Figure 1. The AMP IoT device 220 may be a zero-power device or an Ambient IoT device. The network device 210 transmits wireless power signals and / or downlink communication signals to the AMP IoT device 220, and receives backscattered signals and / or signals actively transmitted by the AMP IoT device 220. The AMP IoT device 220 may also be replaced with a zero-power device.

[0102] In this application, for ease of description, downlink transmission and uplink transmission are distinguished from the perspective of the AMP IoT device 220. Signals transmitted by the AMP IoT device 220 are referred to as uplink signals, and data transmitted by the AMP IoT device 220 are referred to as uplink data. Signals transmitted to the AMP IoT device 220 are referred to as downlink signals, and data transmitted to the AMP IoT device 220 are referred to as downlink data. The receiver of uplink transmission can be an AP, a non-AP STA, a network device, a terminal device, or an intermediate node; the sender of downlink transmission can be an AP, a non-AP STA, a network device, a terminal device, or an intermediate node. Based on the transmission methods described above, uplink signals / uplink data can be actively transmitted by the AMP IoT device 220, or they can be backscattered by the AMP IoT device 220 based on an external carrier.

[0103] AMP IoT device 220 includes an energy harvesting module 321. Optionally, in addition to the energy harvesting module 321, AMP IoT device 220 may also include one or more of the following: a backscatter communication module 322, a logic processing module 323, a sensor module 324, and a memory (not shown in the figure). For example, the logic processing module 323 includes a low-power computing module. It should be understood that the modules included in the AMP IoT device 220 shown in Figure 2 are merely an example and not a limitation.

[0104] For example, the energy harvesting module 321 can harvest ambient energy, such as radio frequency energy, light energy, kinetic energy, mechanical energy, solar energy, and radiation energy, to power the various modules of the AMP IoT device 220. If the ambient energy harvested by the AMP IoT device 220 is radio frequency energy, the signal used to provide the radio frequency energy can be called the power supply signal.

[0105] In some embodiments, radio frequency (RF) power is harvested based on ambient radio frequency (RF) signals; that is, the power supply signal is an ambient RF signal. Ambient RF signals include, for example, RF signals from other communication systems, broadcast signals, etc. In this case, the power harvesting method of the AMP IoT device 220 can be considered passive. Here, "other communication systems" refers to communication systems that do not include the AMP IoT device. In this case, the power supply signal can employ physical layer technologies supported by other communication systems; for example, the power supply signal can be an OFDM signal.

[0106] In some embodiments, radio frequency (RF) power harvesting is based on in-band radio frequency (IRF) signals, meaning the power supply signal is an IRF signal. The IRF signal may include, for example, a signal transmitted using time-frequency resources within the communication system containing the AMP IoT device. Such a power supply signal helps ensure energy harvesting efficiency and reliability. In this case, the power supply signal can employ physical layer technologies supported by the AMP IoT device 220; for example, the power supply signal may be a simple waveform obtained through simple modulation.

[0107] After acquiring power, the AMP IoT device 220 can receive signals from the AP / non-AP STA 210 via its receiver, reflect signals back to the AP / non-AP STA 210 via its backscatter communication module 322, or transmit signals back to the AP / non-AP STA 210 via its transmitter (not shown in the figure). The data reflected or transmitted by the AMP IoT device 220 can be its own stored data (such as identification or pre-written information, such as the production date, brand, and manufacturer of a product). The sensor module 324 can include various sensors, and the AMP IoT device 220 can report the data collected by these sensors based on a low-power mechanism. The memory is used to store basic information (such as item identification) or to acquire sensor data such as ambient temperature and humidity.

[0108] The AMP IoT device 220 can use the logic processing module 323 to perform simple operations such as signal demodulation, decoding, encoding, and modulation. The hardware design can be very simple, making the AMP IoT device 220 very low in cost and small in size.

[0109] Figure 3 illustrates the principle of radio frequency power harvesting (RF Power Harvesting) performed by the power harvesting module 321. RF power harvesting is based on the principle of electromagnetic induction. The RF module, through electromagnetic induction and connected in parallel with a capacitor C and a load resistor RL, harvests electromagnetic wave energy from space to obtain the energy needed to drive the AMP IoT device, such as powering the low-power demodulation module, modulation module, sensors, and memory access. Based on this, AMP IoT devices can operate without traditional batteries.

[0110] In backscatter communication, the backscattered signal can be modulated or not. Figure 4 shows the schematic diagram of backscatter communication with modulation. The transmit (TX) module 111 of the AP / non-AP STA 210 uses an amplifier (AMP) 112 to transmit a wireless signal carrier 131. The AMP IoT device 220 receives and modulates the wireless signal carrier 131, uses a logic processing module 323 to load the information to be transmitted, and uses an energy harvesting module 321 to harvest radio frequency energy. The AMP IoT device 220 uses an antenna 316 to radiate the modulated reflected signal 132. This information transmission process is called backscatter communication. The receive (RX) module 113 of the AP / non-AP STA 210 uses an LNA 114 to receive the modulated reflected signal 132. Backscatter and load modulation functions are inseparable. Load modulation adjusts and controls the circuit parameters of the oscillation circuit of the AMP IoT device 220 according to the data flow rhythm, causing parameters such as the impedance of the AMP IoT device 220 to change accordingly, thus completing the modulation process.

[0111] Load modulation techniques mainly include resistive load modulation and capacitive load modulation. Figure 5 shows the schematic diagram of resistive load modulation. In resistive load modulation, the load resistance R... L A third resistor R3 is connected in parallel. A switch S, controlled by binary encoding, is used to turn the circuit on or off. The switching of the third resistor R3 causes a change in the voltage across the circuit. The load resistor R... L It is connected in parallel with the first capacitor C1, and the load resistor R L The first inductor L1 is connected in series with the second resistor R2, and the second resistor R2 is connected in series with the first inductor L1. The first inductor L1 is coupled to the second inductor L2, and the second inductor L2 is connected in series with the second capacitor C2. For example, ASK modulation can be implemented, that is, signal modulation and transmission are achieved by adjusting the amplitude of the backscattered signal of the terminal device. Similarly, in capacitive load modulation, the circuit resonant frequency can be changed by switching the capacitor on and off, achieving FSK modulation, that is, signal modulation and transmission are achieved by adjusting the operating frequency of the backscattered signal of the terminal device.

[0112] The AMP IoT device 220 can use load modulation to modulate the incoming wave signal, thus realizing the backscatter communication process.

[0113] Therefore, the AMP IoT device 220 has the following significant advantages: (1) it does not need to actively transmit signals, thus eliminating the need for complex RF links such as PAs and RF filters; (2) it does not need to actively generate high-frequency signals, thus eliminating the need for high-frequency crystal oscillators; and (3) with the help of backscatter communication, signal transmission does not consume its own energy. Overall, compared with other terminal devices, the AMP IoT device has many advantages such as no need for conventional batteries, no maintenance, small size, low complexity, low cost, and long life cycle, supporting its wide application in various industries, such as logistics, object recognition, smart warehousing, smart agriculture, energy and power, industrial internet, smart wearables, smart homes, smart control, environmental monitoring, and positioning.

[0114] In addition to the advantages mentioned above, AMP IoT devices also suffer from poor time synchronization accuracy. On the one hand, to reduce device complexity and power consumption, AMP IoT devices typically use extremely simple clock circuits as the system clock, making it difficult for such simple circuits to provide high-precision time synchronization. On the other hand, limited by their simple structure and low complexity, AMP IoT devices struggle to support Orthogonal Frequency Division Multiplexing (OFDM) technology. AMP IoT devices can usually only transmit and receive signals with simple waveforms, and to maintain low power consumption and low complexity, their signal sampling rate is relatively low, typically between 2 and 3 MHz, resulting in poor synchronization accuracy of the sampling clock.

[0115] Generally, the synchronization error of the time synchronization and sampling clock in the simplest AMP IoT device may be between 1% and 10% (corresponding to 10,000 ppm to 100,000 ppm), while the synchronization error of the time synchronization and sampling clock in a slightly more advanced AMP IoT device may be less than 1% (corresponding to less than 10,000 ppm). Taking a 10% synchronization error in the sampling clock as an example, when sending uplink data, each symbol sent by the AMP IoT device may result in a 10% error in the symbol length (the shortest actual symbol length is 0.9 or the longest is 1.1). Therefore, when sending a string of symbols, this will lead to a more significant accumulation of time errors; for example, sending 200 symbols will result in a deviation of 20 symbols.

[0116] AMP IoT devices with different time synchronization accuracies may support different multiplexing methods. For example, those with very poor clock capabilities (such as SFO=10) 5AMP IoT devices with low clock speeds (SFO < 10 ppm) face challenges in maintaining time synchronization. Using Code Division Multiplexing (CDM) among multiple devices leads to poor transmission performance. Therefore, AMP IoT devices with poor clock speeds struggle to support CDM. Conversely, devices with better clock speeds (e.g., SFO < 10 ppm)... 4 AMP IoT devices with a resolution of ppm can well support CDM.

[0117] Similarly, due to limitations in complexity and power consumption, AMP IoT devices typically lack crystal oscillators or use oscillators with very low precision, making their frequencies highly susceptible to drift and resulting in Carrier Frequency Offset (CFO). CFO can lead to demodulation errors and Doppler shift, preventing receiver filters from accurately filtering the target bandwidth and degrading signal demodulation performance. Therefore, AMP IoT devices with different oscillator precisions will have varying receiving and transmitting performance, and may also support different multiplexing methods.

[0118] Regarding topology:

[0119] The communication between the network device 210 and the AMP IoT device 220 can be direct or indirect.

[0120] For direct communication, refer to the topology shown in Figure 6. Network device 210 and AMP IoT device 220 communicate bidirectionally. Network device 210 can directly send data and / or signaling to AMP IoT device 220, and AMP IoT device 220 can also directly send data and / or signaling to network device 210. Furthermore, the network device sending data and / or signaling to AMP IoT device 220 and the network device receiving data and / or signaling from AMP IoT device 220 may be different.

[0121] For indirect communication, refer to the topology shown in Figure 7. Network device 210 and AMP IoT device 220 communicate through intermediate node 230. Intermediate node 230 transmits data and / or signaling between network device 210 and AMP IoT device 220. Intermediate node can be at least one of the following: relay, integrated access backhaul (IAB) node, UE, repeater, etc.

[0122] Regarding encoding methods:

[0123] The AMP IoT device 220 may support various encoding methods. Based on the simplicity of the encoding methods, this application roughly divides them into two categories. The first category of encoding methods is relatively simple, including: Not Return to Zero (NRZ) encoding, Manchester encoding, Unipolar Return to Zero (URZ) encoding, Differential Binary Phase (DBP) encoding, Miller encoding, differential encoding, Bi-Phase Space Coding (FM0), Pulse Interval Encoding (PIE), Polar Codes, and repetition encoding. The second type of encoding method is more complex, such as error correction codes, including: Forward Error Correction (FEC) coding, Low Density Parity Check Code (LDPC), convolutional codes, BCH codes (Bose-Chaudhuri Hocquenghem codes), Turbo codes, and RS codes (Reed Solomon codes).

[0124] Figure 8 illustrates several encoding methods that AMP IoT devices can use.

[0125] NRZ encoding: A high level represents a binary "1", and a low level represents a binary "0". Figure 8 shows a schematic diagram of the level of the binary data "101100101001011" using NRZ encoding.

[0126] Manchester encoding, also known as split-phase encoding, represents binary values ​​by changes in level (rising or falling) over half a bit period. A negative transition over half a bit period represents a binary "1", and a positive transition over half a bit period represents a binary "0". Manchester encoding, when using carrier load modulation or backscatter modulation, is commonly used for data transmission from AMP IoT devices to network devices because it facilitates the detection of data transmission errors. This is because Manchester encoding does not allow a "no change" state within the bit length. When multiple AMP IoT devices simultaneously transmit data bits with different values, the received rising and falling edges cancel each other out, resulting in a continuous carrier signal throughout the entire bit length. Since this state is not allowed, network devices can use this error to determine the specific location of a collision. Figure 8 shows a schematic diagram of the level of the Manchester-encoded binary data "101100101001011".

[0127] URZ encoding: A high level during the first half of the bit cycle represents a binary "1", while a low level signal throughout the entire bit cycle represents a binary "1". Figure 8 shows a schematic diagram of the level of the binary data "101100101001011" using URZ encoding.

[0128] DBP encoding: Any edge in half a bit cycle represents a binary "0", and no edge represents a binary "1". Furthermore, the level is inverted at the beginning of each bit cycle. Therefore, the bit clock is relatively easy for the receiver to reconstruct. Figure 8 shows a schematic diagram of the level of binary data "101100101001011" encoded using DBP.

[0129] Miller encoding: Any edge within half a bit cycle represents a binary "1", while a constant level in the next bit cycle represents a binary "0". The level alternation at the beginning of a bit cycle makes it relatively easy for the receiver to reconstruct the bit clock. Figure 8 shows a schematic diagram of the level of the Miller-encoded binary data "101100101001011".

[0130] Differential coding: Each binary "1" to be transmitted causes a change in signal level, while for a binary "0", the signal level remains unchanged.

[0131] Regarding modulation methods:

[0132] Due to its simple structure and low complexity, AMP IoT devices support relatively simple modulation methods, such as one or more of the following: On-Off Keying (OOK) modulation, Multi-Carrier OOK (MC-OOK) modulation, Phase Shift Keying (PSK) modulation, Binary Phase Shift Keying (BPSK) modulation, and Binary Frequency Shift Keying (BFSK) modulation.

[0133] As discussed above, different AMP IoT devices may differ in one or more of the following aspects: device type, device capabilities, device structure, encoding method, modulation method, transmission method, multiplexing method, waveform, service characteristics, topology, etc. If the communication system supports the coexistence of different AMP IoT devices, and even supports the coexistence of AMP IoT devices and traditional UEs (such as terminal device 120 as shown in Figure 1), then how the network should strategically schedule different AMP IoT devices in such a complex hybrid deployment communication scenario is a problem that needs to be solved.

[0134] To this end, this application provides a scheduling method for AMP IoT devices, which supports precise and flexible scheduling of AMP IoT devices, thereby improving communication efficiency and reliability within the system.

[0135] Figure 9 illustrates a flowchart of a scheduling method for an AMP IoT device provided in an exemplary embodiment of this application. The method includes at least some of the following steps:

[0136] Step 920: Send a first signaling message. The first signaling message is used to schedule or trigger the transmission of AMP IoT devices. The first signaling message carries first indication information and / or second indication information. The first indication information indicates the device information of the AMP IoT device scheduled or triggered by the first signaling message, and the second indication information indicates the AMP IoT transmission method scheduled or triggered by the first signaling message.

[0137] The AMP IoT device in this application can be understood as a device whose energy comes from ambient energy, or as a device that supports operating by harvesting ambient energy, such as the zero-power device and / or AMP IoT device mentioned above. Ambient energy includes one or more of the following: radio frequency energy, light energy, kinetic energy, mechanical energy, solar energy, radiation energy, etc. For example, ambient energy harvesting can be achieved by the energy harvesting module 321 shown in Figure 2. Of course, the energy harvesting module can also be called by other names, such as a harvesting module, energy collection module, etc., and this application does not limit its name.

[0138] AMP IoT transmission methods include at least one of the following: transmission methods when AMP IoT devices perform uplink transmission, transmission methods when AMP IoT devices perform downlink transmission, and transmission methods supported by AMP IoT technology as agreed in the communication protocol.

[0139] In some embodiments, in a first signaling message, the first indication information and the second indication information are indicated separately, that is, the device information of the AMP IoT device and the AMP IoT transmission method are indicated by the two indication information respectively.

[0140] In some embodiments, in a first signaling message, the first indication information and the second indication information are combined, that is, the device information of the AMP IoT device and the AMP IoT transmission method are uniformly indicated by a single indication information. For example, the first signaling message carries third indication information, which is used to indicate both the device information of the AMP IoT device scheduled or triggered by the first signaling message and the AMP IoT transmission method scheduled or triggered by the first signaling message.

[0141] Since AMP IoT devices are aware of their own device information and / or supported transmission methods (e.g., device information and supported transmission methods are stored in the AMP IoT device or pre-written into it), upon receiving the first signaling, the AMP IoT device can determine whether to transmit based on the first signaling by judging whether its own device information and / or supported transmission methods belong to the device information and AMP IoT transmission method indicated by the first signaling. In other words, the AMP IoT device can determine whether to transmit based on the first signaling by judging whether it is an AMP IoT device scheduled or triggered by the first signaling.

[0142] In some embodiments, the first signaling is used to schedule or trigger transmission by one AMP IoT device, or to schedule or trigger transmission by multiple AMP IoT devices. Optionally, the multiple AMP IoT devices scheduled or triggered by the first signaling are the same, for example, they have the same device information and / or support the same transmission method. Optionally, the multiple AMP IoT devices scheduled or triggered by the first signaling are different, for example, they have different device information and / or support different transmission methods.

[0143] In some embodiments, the first signaling can schedule or trigger downlink transmission of the AMP IoT device, or it can schedule or trigger uplink transmission of the AMP IoT device. In this application, uplink transmission refers to transmission where the sender is an AMP IoT device, and downlink transmission refers to transmission where the receiver is an AMP IoT device. If the first signaling schedules or triggers downlink transmission of the AMP IoT device, it means that the first signaling schedules or triggers the AMP IoT device to receive downlink signals / downlink data. If the first signaling schedules or triggers uplink transmission of the AMP IoT device, it means that the first signaling schedules or triggers the AMP IoT device to send uplink signals / uplink data. If the first signaling schedules or triggers multiple AMP IoT devices, it can schedule or trigger uplink transmission of some AMP IoT devices and downlink transmission of others; or, schedule or trigger downlink transmission of all AMP IoT devices; or, schedule or trigger uplink transmission of all AMP IoT devices.

[0144] The sender of the first signaling, i.e. the executor of step 920, can be the network device 110 shown in Figure 1, or the terminal device 120 shown in Figure 1, or the AP 130 shown in Figure 1, or the non-AP STA 140 shown in Figure 1, or the network device 210 shown in Figure 2, or the intermediate node 230 shown in Figure 7.

[0145] In summary, the method provided in this application supports scheduling one or more AMP IoT devices by sending a first signaling message. Since the first signaling message can indicate the device information and / or transmission method of the AMP IoT device, and different AMP IoT devices, as well as AMP IoT devices and traditional UEs, can be distinguished by device information and transmission method, the receiver of the first signaling message can determine whether it has been scheduled or triggered based on the indication information carried by the first signaling message, thereby achieving precise and flexible scheduling of AMP IoT devices.

[0146] Figure 10 illustrates a flowchart of a scheduling method for an AMP IoT device provided in an exemplary embodiment of this application. The method is executed by the AMP IoT device and includes at least some of the following steps:

[0147] Step 1020: Receive the first signaling, which is used to schedule or trigger the transmission of AMP IoT devices. The first signaling carries first indication information and / or second indication information. The first indication information indicates the device information of the AMP IoT device scheduled or triggered by the first signaling, and the second indication information indicates the AMP IoT transmission method scheduled or triggered by the first signaling.

[0148] The recipient of the first signaling, i.e., the executor of step 1020, is the AMP IoT device. An AMP IoT device can be understood as a device whose energy comes from ambient energy, or as a device that supports operating by collecting ambient energy, such as the zero-power devices and / or AMP IoT devices mentioned above. Ambient energy includes one or more of the following: radio frequency energy, light energy, kinetic energy, mechanical energy, solar energy, radiation energy, etc. For example, ambient energy collection can be achieved through the energy collection module 321 shown in Figure 2. Of course, the energy collection module can also be called by other names, such as a collection module, energy harvesting module, etc., and this application does not limit its name.

[0149] AMP IoT transmission methods include at least one of the following: transmission methods when AMP IoT devices perform uplink transmission, transmission methods when AMP IoT devices perform downlink transmission, and transmission methods supported by AMP IoT technology as agreed in the communication protocol.

[0150] In some embodiments, in a first signaling message, the first indication information and the second indication information are indicated separately, that is, the device information of the AMP IoT device and the AMP IoT transmission method are indicated by the two indication information respectively.

[0151] In some embodiments, in a first signaling message, the first indication information and the second indication information are combined, that is, the device information of the AMP IoT device and the AMP IoT transmission method are uniformly indicated by a single indication information. For example, the first signaling message carries third indication information, which is used to indicate both the device information of the AMP IoT device scheduled or triggered by the first signaling message and the AMP IoT transmission method scheduled or triggered by the first signaling message.

[0152] Since AMP IoT devices are aware of their own device information and / or supported transmission methods (e.g., device information and supported transmission methods are stored in the AMP IoT device or pre-written into it), upon receiving the first signaling, the AMP IoT device can determine whether to transmit based on the first signaling by judging whether its own device information and / or supported transmission methods belong to the device information and AMP IoT transmission method indicated by the first signaling. In other words, the AMP IoT device can determine whether to transmit based on the first signaling by judging whether it is an AMP IoT device scheduled or triggered by the first signaling.

[0153] In some embodiments, the first signaling is used to schedule or trigger transmission by one AMP IoT device, or to schedule or trigger transmission by multiple AMP IoT devices. Optionally, the multiple AMP IoT devices scheduled or triggered by the first signaling are the same, for example, they have the same device information and / or support the same transmission method. Optionally, the multiple AMP IoT devices scheduled or triggered by the first signaling are different, for example, they have different device information and / or support different transmission methods.

[0154] In some embodiments, the first signaling can schedule or trigger downlink transmission of the AMP IoT device, or it can schedule or trigger uplink transmission of the AMP IoT device. In this application, uplink transmission refers to transmission where the sender is an AMP IoT device, and downlink transmission refers to transmission where the receiver is an AMP IoT device. If the first signaling schedules or triggers downlink transmission of the AMP IoT device, it means that the first signaling schedules or triggers the AMP IoT device to receive downlink signals / downlink data. If the first signaling schedules or triggers uplink transmission of the AMP IoT device, it means that the first signaling schedules or triggers the AMP IoT device to send uplink signals / uplink data. If the first signaling schedules or triggers multiple AMP IoT devices, it can schedule or trigger uplink transmission of some AMP IoT devices and downlink transmission of others; or, schedule or trigger downlink transmission of all AMP IoT devices; or, schedule or trigger uplink transmission of all AMP IoT devices.

[0155] In summary, the method provided in this application supports determining whether an AMP IoT device has been scheduled or triggered by receiving a first signaling message. Since the first signaling message can indicate the device information and / or transmission method of the AMP IoT device, and different AMP IoT devices, as well as AMP IoT devices and traditional UEs, can be distinguished by device information and transmission method, the receiver of the first signaling message can determine whether it has been scheduled or triggered based on the indication information carried by the first signaling message, thereby achieving precise and flexible scheduling of AMP IoT devices.

[0156] Furthermore, considering the device information that AMP IoT devices may possess and the transmission methods they may support, this application also provides a detailed design for the device information and transmission methods.

[0157] In some embodiments, the device information of the AMP IoT device includes: the device type of the AMP IoT device, and / or, the device capabilities of the AMP IoT device.

[0158] • AMP IoT devices can be of one or more of the following types: passive device, semi-passive device, active device, device with backscatter module, device with active transmitter, device with both backscatter module and active transmitter, Device A, Device B, Device C, Type i, Type ii, AMP-only IoT Device, AMP-Assisted IoT Device, etc. Please refer to the previous text for a description of each type; it will not be repeated here.

[0159] • The device capabilities of an AMP IoT device may include at least one or more of the following: transmission capability, energy storage capability, synchronization capability, modulation capability, coding capability, service capability (such as supported service types), supported MCS, multiplexing transmission capability, multiple access transmission capability, radio frequency capability (such as supported bandwidth), etc.

[0160] Transmission capability can be categorized into three types: active transmission only, backscatter only, and both active transmission and backscatter. Energy storage capability can refer to the ability to store energy, or it can be categorized by the amount of energy that can be stored; for example, based on the capacitance, AMP IoT devices with smaller capacitance have lower energy storage capabilities. Synchronization capability can refer to the ability to synchronize time and / or frequency, or it can be categorized by synchronization accuracy; for example, AMP IoT devices with lower synchronization accuracy have lower synchronization capabilities. Modulation capability can refer to whether a specific modulation method is supported, or it can be categorized by the number of supported modulation methods. Coding capability can refer to whether a specific coding method is supported, or it can be categorized by the number of supported coding methods. Multiplexing transmission capability can refer to whether a specific multiplexing method is supported, or it can be categorized by the number of supported multiplexing methods. Multiple access transmission capability can refer to whether a specific multiple access method is supported, or it can be categorized by the number of supported multiple access methods.

[0161] In some embodiments, the AMP IoT transmission method includes one or more of the following parameters: transmission resources for AMP IoT transmission, multiplexing method used for AMP IoT transmission, multiple access method used for AMP IoT transmission, waveform used for AMP IoT transmission, encoding method for AMP IoT transmission, modulation method for AMP IoT transmission, topology of AMP IoT transmission, and service type of AMP IoT transmission.

[0162] Therefore, when the first signaling carries indication information about the device type, it is possible to selectively schedule or trigger AMP IoT devices of the target device type to transmit. When the first signaling carries indication information about the device capabilities, it is possible to selectively schedule or trigger AMP IoT devices with the target device capabilities to transmit.

[0163] • The transmission resources of AMP IoT transmission include one or more of the following resources: time domain resources, frequency domain resources, spatial domain resources, and code domain resources.

[0164] In some embodiments, the second indication information may indicate the time-domain resources of AMP IoT transmission through one or more of the following information: the start position of the time-domain resources, the end position of the time-domain resources, the number of time-domain units, and the duration.

[0165] The time-domain unit includes one or more of the following: frame, subframe, slot, mini-slot, sub-slot, symbol, symbol group, and time-domain unit based on other time-domain units. The unit of duration can be microsecond (μs) or millisecond (ms), etc.

[0166] Optionally, the second indication information indicates the time-domain resources of the AMP IoT transmission through the Start and Length Indicator Value (SLIV).

[0167] Optionally, the second indication information indicates the time-domain resources of the AMP IoT transmission through a start symbol (S) and an allocation length (L).

[0168] In some embodiments, the second indication information may indicate the frequency domain resources of AMP IoT transmission through one or more of the following information: the start position of the frequency domain resources, the end position of the frequency domain resources, the number of frequency domain units, and the center frequency.

[0169] The frequency domain unit includes, for example, one or more of the following: carrier, subband, subchannel, subcarrier, physical resource block (PRB), bandwidth part (BWP), and at least one of other frequency domain units.

[0170] Optionally, the second indication information indicates the frequency domain resources transmitted by the AMP IoT through the number or index of the frequency domain unit, such as the channel number, sub-band number, PRB index, etc.

[0171] Optionally, the second indication information indicates the frequency domain resources of AMP IoT transmission through the size of the frequency domain unit, such as channel bandwidth, BWP size, sub-channel bandwidth, etc.

[0172] Optionally, the second indication information indicates the frequency domain resources of the AMP IoT transmission via a bitmap.

[0173] In some embodiments, the second indication information may indicate the spatial resources of AMP IoT transmission through one or more of the following information: antenna port index or number, number of antenna ports, number of layers, layer number or layer index, rank, beam, etc.

[0174] In some embodiments, the second indication information may indicate the code domain resources of AMP IoT transmission through one or more of the following information: the number of codewords, the index / number of the codewords, and the code rate.

[0175] Therefore, when the first signaling carries indication information about transmission resources, it is possible to selectively schedule or trigger AMP IoT devices to use the target transmission resources for transmission.

[0176] The multiplexing methods used in AMP IoT transmission include one or more of the following: Frequency Division Multiplexing (FDM), Time Division Multiplexing (TDM), and Code Division Multiplexing (CDM).

[0177] Therefore, when the first signaling carries indication information about the multiplexing method, it is possible to selectively schedule or trigger AMP IoT devices using the target multiplexing method to transmit.

[0178] • The multiple access methods used in AMP IoT transmission include one or more of the following: Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), and Code Division Multiple Access (CDMA).

[0179] Therefore, when the first signaling carries indication information about the multiple access method, it is possible to selectively schedule or trigger AMP IoT devices using the target multiple access method to transmit.

[0180] The waveforms used for AMP IoT transmission include one or more of the following: ASK waveform, OOK waveform, MC-OOK waveform, FSK waveform, PSK waveform, BPSK waveform, and BFSK waveform.

[0181] Therefore, when the first signaling carries indication information about the waveform, it is possible to selectively schedule or trigger AMP IoT devices using the target waveform to transmit.

[0182] The modulation methods for AMP IoT transmission include one or more of the following: ASK modulation, OOK modulation, MC-OOK modulation, FSK modulation, PSK modulation, BPSK modulation, and BFSK modulation.

[0183] The encoding methods used in AMP IoT transmission include one or more of the following: NRZ encoding, Manchester encoding, URZ encoding, DBP encoding, Miller encoding, differential encoding, FMO encoding, PIE encoding, repetition encoding, Polar codes, LDPC, convolutional codes, BCH codes, Turbo codes, RS codes, FEC codes, etc. Further, referring to the preceding descriptions, these encoding methods can be divided into two categories based on their simplicity: Category I encoding methods and Category II encoding methods. Of course, they can also be divided into two, three, or more categories according to other methods, depending on the actual needs.

[0184] Therefore, when the first signaling carries indication information about the encoding method, it is possible to selectively schedule or trigger AMP IoT devices using the target encoding method to transmit.

[0185] The topology of AMP IoT transmission includes one or more of the following: direct communication and indirect communication.

[0186] Therefore, when the first signaling carries indication information about the topology, it is possible to selectively schedule or trigger AMP IoT devices using the target topology for transmission.

[0187] • The service types transmitted by AMP IoT include one or more of the following: DO service, DT service, DO-A service, and DO-DTT service.

[0188] Therefore, when the first signaling carries indication information about the service type, it is possible to selectively schedule or trigger AMP IoT devices of the target service type to transmit.

[0189] Based on the embodiments shown in Figures 9 and 10, and in conjunction with the above-mentioned device information and transmission methods, this application also provides a detailed design for how the first signaling should schedule or trigger the transmission of AMP IoT devices under different circumstances.

[0190] Scenario 1: The first signaling schedules or triggers the transmission of multiple AMP IoT devices, and these multiple AMP IoT devices belong to the same type of AMP IoT device or use the same AMP IoT transmission method.

[0191] The first signaling can schedule uplink and / or downlink transmissions of multiple AMP IoT devices in a single instance, or the first signaling can trigger uplink and / or downlink transmissions of multiple AMP IoT devices in a single instance.

[0192] The first signaling message may carry only the first indication information, only the second indication information, or both the first and second indication information. Alternatively, the first signaling message may carry a third indication information, which is used to indicate both the device information of the AMP IoT device scheduled or triggered by the first signaling message and the AMP IoT transmission method scheduled or triggered by the first signaling message.

[0193] Therefore, this application supports carrying device type and / or device capability and / or transmission method indication information in the first signaling to precisely schedule a specific AMP IoT device for transmission. Especially in AMP IoT scenarios with mixed deployments of multiple device types, capabilities, and transmission methods, scheduling one AMP IoT device at a time via the first signaling can meet targeted business needs and improve transmission reliability. Furthermore, if the first signaling schedules multiple AMP IoT devices for uplink transmission, the uplink receiver may need to expend energy and time distinguishing which AMP IoT device sent the uplink transmission, leading to wasted power and transmission latency. It may even cause reception errors due to incorrect identification of the AMP IoT devices. Therefore, scheduling one AMP IoT device at a time via the first signaling ensures consistent understanding of device information and transmission methods between the receiving and receiving parties, reducing sending and receiving complexity and simplifying the behavior of the uplink receiving side.

[0194] (1) When the first signaling carries at least the first instruction information:

[0195] For example, the first indication information indicates the device type of the target AMP IoT device. The AMP IoT device that receives the first signaling can determine whether it is scheduled or triggered by the first signaling based on its own device type. Suppose that AMP IoT device 1 receives the first signaling. If the device type of AMP IoT device 1 is the same as the device type indicated by the first indication information, or if the device type indicated by the first indication information includes the device type of AMP IoT device 1 (for example, suppose the first indication information indicates two or more device types, and the device type of AMP IoT device 1 belongs to one of them), then it means that AMP IoT device 1 is the AMP IoT device scheduled or triggered by the first signaling.

[0196] For example, the first indication information indicates the device capabilities of the target AMP IoT device. An AMP IoT device that receives the first signaling can determine whether it is scheduled or triggered by the first signaling based on its own device capabilities. For instance, if AMP IoT device 1 receives the first signaling, and its device capabilities are the same as those indicated by the first indication information, or if the device capabilities indicated by the first indication information include those of AMP IoT device 1 (e.g., if the first indication information indicates two or more device capabilities, and AMP IoT device 1's device capabilities belong to one of them), then AMP IoT device 1 is the AMP IoT device scheduled or triggered by the first signaling.

[0197] For example, the first indication information indicates the device type and capabilities of the target AMP IoT device. The AMP IoT device receiving the first signaling determines whether it is scheduled or triggered by the first signaling based on its own device type and capabilities. For instance, only AMP IoT devices that simultaneously satisfy the device type and capabilities indicated by the first indication information are the target AMP IoT devices scheduled or triggered by the first signaling. Assuming both AMP IoT device 1 and AMP IoT device 2 receive the first signaling, if the device type indicated by the first indication information includes the device type of AMP IoT device 1, and the device capabilities indicated by the first indication information include the device capabilities of AMP IoT device 1, then AMP IoT device 1 is the AMP IoT device scheduled or triggered by the first signaling. If the device type of AMP IoT device 2 is different from the device type indicated by the first indication information, and / or the device capabilities of AMP IoT device 2 are different from the device capabilities indicated by the first indication information, then AMP IoT device 2 is not the AMP IoT device scheduled or triggered by the first signaling, and therefore, AMP IoT device 2 does not need to transmit according to the first signaling.

[0198] (2) When the first signaling carries at least the second instruction information:

[0199] For example, the second indication information indicates the target transmission resource. An AMP IoT device that receives the first signaling can determine whether it has been scheduled or triggered by the first signaling based on its own configured transmission resources. Assuming AMP IoT device 1 receives the first signaling, if the transmission resource configured for AMP IoT device 1 is the same as the target transmission resource indicated by the first indication information, or if the target transmission resource indicated by the first indication information includes the transmission resource configured for AMP IoT device 1, then AMP IoT device 1 is an AMP IoT device scheduled or triggered by the first signaling.

[0200] For example, the second indication information indicates the target multiplexing method. An AMP IoT device that receives the first signaling can determine whether it is scheduled or triggered by the first signaling based on the multiplexing methods it supports. For instance, if AMP IoT device 1 receives the first signaling, and the multiplexing method it supports is the same as the target multiplexing method indicated by the first indication information, or if the target multiplexing method indicated by the first indication information includes multiplexing methods supported by AMP IoT device 1 (for example, if the first indication information indicates two or more multiplexing methods, and AMP IoT device 1's multiplexing method belongs to one of them), then it indicates that AMP IoT device 1 is an AMP IoT device scheduled or triggered by the first signaling.

[0201] For example, the second indication information indicates the target multiple access method. An AMP IoT device that receives the first signaling can determine whether it has been scheduled or triggered by the first signaling based on the multiple access methods it supports. For instance, if AMP IoT device 1 receives the first signaling, and the multiple access method supported by AMP IoT device 1 is the same as the target multiple access method indicated by the first indication information, or if the target multiple access method indicated by the first indication information includes multiple access methods supported by AMP IoT device 1 (for example, assuming the first indication information indicates two or more multiple access methods, and AMP IoT device 1's multiple access method belongs to one of them), then it indicates that AMP IoT device 1 is an AMP IoT device scheduled or triggered by the first signaling.

[0202] For example, the second indication information indicates the target waveform. The AMP IoT device that receives the first signaling can determine whether it is scheduled or triggered by the first signaling based on the waveforms it supports. Assuming AMP IoT device 1 receives the first signaling, if the waveform supported by AMP IoT device 1 is the same as the target waveform indicated by the first indication information, or if the target waveform indicated by the first indication information includes waveforms supported by AMP IoT device 1 (for example, assuming the first indication information indicates two or more waveforms, and the waveform of AMP IoT device 1 belongs to one of them), then it indicates that AMP IoT device 1 is an AMP IoT device scheduled or triggered by the first signaling.

[0203] For example, the second indication information indicates the target encoding method. An AMP IoT device that receives the first signaling can determine whether it has been scheduled or triggered by the first signaling based on the encoding methods it supports. For instance, if AMP IoT device 1 receives the first signaling, and the encoding method it supports is the same as the target encoding method indicated by the first indication information, or if the target encoding method indicated by the first indication information includes encoding methods supported by AMP IoT device 1 (for example, if the first indication information indicates two or more encoding methods, and AMP IoT device 1's encoding method belongs to one of them), then it indicates that AMP IoT device 1 is an AMP IoT device scheduled or triggered by the first signaling.

[0204] For example, the second indication information indicates the target modulation method. An AMP IoT device that receives the first signaling can determine whether it has been scheduled or triggered by the first signaling based on the modulation methods it supports. For instance, if AMP IoT device 1 receives the first signaling, and the modulation method it supports is the same as the target modulation method indicated by the first indication information, or if the target modulation method indicated by the first indication information includes the modulation methods supported by AMP IoT device 1 (for example, assuming the first indication information indicates two or more modulation methods, and AMP IoT device 1's modulation method belongs to one of them), then it indicates that AMP IoT device 1 is an AMP IoT device scheduled or triggered by the first signaling.

[0205] For example, if the second indication information indicates multiple of the following: target transmission resources, target multiplexing mode, target multiple access mode, target waveform, target coding mode, and target modulation mode, then the AMP IoT device that simultaneously satisfies all the transmission modes indicated by the second indication information is the target AMP IoT device scheduled or triggered by the first signaling. Taking the second indication information indicating the target multiplexing mode, target waveform, target coding mode, and target modulation mode as an example, assuming AMP IoT device 1 receives the first signaling, if the waveform, coding mode, and modulation mode supported by AMP IoT device 1 are the same as the target waveform, target coding mode, and target modulation mode indicated by the second indication information, but the multiplexing mode supported by AMP IoT device 1 is different from the target multiplexing mode indicated by the second indication information, then AMP IoT device 1 is not the AMP IoT device scheduled or triggered by the first signaling, and AMP IoT device 1 does not need to transmit according to the first signaling.

[0206] (3) The first signaling is also used to instruct scheduling resources for multiple AMP IoT devices:

[0207] In some embodiments, the first signaling may carry indication information of scheduling resources in addition to scheduling or triggering multiple AMP IoT devices to transmit. The scheduling resources may be a common scheduling resource corresponding to one type of AMP IoT device, or the scheduling resources may include individual scheduling resources corresponding to each AMP IoT device within the AMP IoT device ecosystem.

[0208] Optionally, the first signaling indicates a unified scheduling resource for multiple AMP IoT devices, or indicates a common scheduling resource for multiple AMP IoT devices. This resource indication scheme can save indication bits. These multiple AMP IoT devices perform uplink and / or downlink transmissions within the unified / common scheduling resource.

[0209] Optionally, the first signaling instruction indicates the scheduling resources separately for each of the multiple AMP IoT devices. In other words, the transmission resources are indicated individually for each AMP IoT device. This resource indication scheme offers high flexibility and reduces the probability of transmission conflicts between the various AMP IoT devices.

[0210] In some embodiments, scheduling resources include one or more of the following: time-domain resources, frequency-domain resources, spatial-domain resources, and code-domain resources.

[0211] In some embodiments, the first signaling may indicate the scheduling resources through one or more of the following information: the start position of the time-domain resource, the end position of the time-domain resource, the number of time-domain units, the duration, the start position of the frequency-domain resource, the end position of the frequency-domain resource, the number of frequency-domain units, the center frequency, the index or number of the antenna port, the number of antenna ports, the number of layers, the layer number or layer index, the rank, the beam, the number of codewords, the index / number of the codewords, and the code rate.

[0212] The device information indicated by the first indication information and / or the AMP IoT transmission method indicated by the second indication information are used by the AMP IoT device to determine whether it is scheduled or triggered by the first signaling.

[0213] The above content will now be explained with specific examples. #S1, #S2, and #S3 below are all different first signaling instructions used to implement different scheduling or triggering processes.

[0214] Figure 11 illustrates a schematic diagram of a scheduling method for AMP IoT devices provided in an exemplary embodiment of this application. It is assumed that multiple types of AMP IoT devices are currently deployed in a mixed manner, including AMP IoT devices of type i and AMP IoT devices of type ii.

[0215] The network device can carry only type i indication information in the first signaling #S1 and only type ii indication information in the first signaling #S2. That is, the network device triggers only type i AMP IoT devices to transmit in one trigger and only type ii AMP IoT devices to transmit in another trigger. Alternatively, the network device schedules only type i AMP IoT devices to transmit in one scheduling and only type ii AMP IoT devices to transmit in another scheduling.

[0216] Optionally, the first signaling also indicates a scheduling resource, scheduling or triggering the AMP IoT device to transmit on the corresponding resource. For example, the first signaling #S1 indicates resource #R1 for an AMP IoT device of type i, and the AMP IoT device of type i sends and receives signals on resource #R1 based on the scheduling or triggering of the first signaling #S1; the first signaling #S2 indicates resource #R2 for an AMP IoT device of type ii, and the AMP IoT device of type ii sends and receives signals on resource #R2 based on the scheduling or triggering of the first signaling #S2.

[0217] Optionally, resource #R1 is exactly the same as resource #R2.

[0218] Optionally, resources #R1 and #R2 may differ in one or more of the following domains: time domain, frequency domain, spatial domain, and code domain. For example, they may differ in the location of the frequency domain resources, the number of frequency domain cells, the location of the time domain resources, and the number of time domain cells. They may also differ in the number of channels, channel bandwidth, channel numbering, and channel center frequency. Furthermore, they may differ in the number of codewords and their index numbers. Finally, they may differ in the number of beams.

[0219] Figure 11 provides an example of precisely scheduling or triggering AMP IoT devices based on device type. Especially in scenarios where multiple AMP IoT device types are deployed, the first signaling can schedule or trigger transmission for only one target device type of AMP IoT device at a time. Furthermore, it supports scheduling available resources for AMP IoT devices. Multiple AMP IoT devices can be assigned shared scheduling resources, saving instruction bits and simplifying resource allocation. Alternatively, individual scheduling resources can be assigned to each AMP IoT device separately, improving the flexibility of resource allocation and reducing transmission conflicts.

[0220] Figure 12 illustrates a schematic diagram of an AMP IoT device scheduling method provided in an exemplary embodiment of this application. It is assumed that AMP IoT devices with multiple capabilities are currently deployed, such as capability 1 devices, capability 2 devices, and capability 3 devices. Of course, it is also possible to deploy only two types of AMP IoT devices, or four or more types of AMP IoT devices.

[0221] Taking the following examples: Device 1 is an AMP IoT device that only has active transmission capability; Device 2 is an AMP IoT device that only has backscatter capability; and Device 3 is an AMP IoT device that has both active transmission capability and backscatter capability.

[0222] Network devices can schedule or trigger transmission only for devices with capability 1 via the first signaling #S1. For example, the first signaling #S1 may only carry indication information for device capability 1 (only having active transmission capability). Network devices can schedule or trigger transmission only for devices with capability 2 via the first signaling #S2. For example, the first signaling #S2 may only carry indication information for device capability 2 (only having backscatter capability). Network devices can schedule or trigger transmission only for devices with capability 3 via the first signaling #S3. For example, the first signaling #S3 may only carry indication information for device capability 3 (having both active transmission and backscatter capabilities). In other words, the network device triggers transmission only for devices with capability 1 in the first trigger, only for devices with capability 2 in the second trigger, and only for devices with capability 3 in the third trigger. Alternatively, the network device schedules transmission only for devices with capability 1 in the first scheduling, only for devices with capability 2 in the second scheduling, and only for devices with capability 3 in the third scheduling.

[0223] Optionally, the first signaling also indicates a scheduling resource, scheduling or triggering the AMP IoT device to transmit on the corresponding resource. For example, the first signaling #S1 indicates resource #R1 for capability 1 device, and capability 1 device sends and receives signals on resource #R1 based on the scheduling or triggering of the first signaling #S1; the first signaling #S2 indicates resource #R2 for capability 2 device, and capability 2 device sends and receives signals on resource #R2 based on the scheduling or triggering of the first signaling #S2; the first signaling #S3 indicates resource #R3 for capability 3 device, and capability 3 device sends and receives signals on resource #R3 based on the scheduling or triggering of the first signaling #S3.

[0224] Optionally, resources #R1, #R2, and #R3 are completely identical.

[0225] Optionally, resources #R1, #R2, and #R3 may differ in one or more of the following domains: time domain, frequency domain, spatial domain, and code domain.

[0226] Figure 12 provides an example of precisely scheduling or triggering AMP IoT devices based on their capabilities. Especially in scenarios where AMP IoT devices with diverse capabilities are deployed, the first signaling can schedule or trigger transmission for only one type of AMP IoT device with a single target capability. Furthermore, it supports scheduling available resources for AMP IoT devices. Multiple AMP IoT devices can be assigned shared scheduling resources, saving instruction bits and simplifying resource allocation. Alternatively, individual scheduling resources can be assigned to each AMP IoT device, increasing the flexibility of resource allocation and reducing transmission conflicts.

[0227] Figure 13 illustrates a schematic diagram of an AMP IoT device scheduling method provided in an exemplary embodiment of this application. It is assumed that AMP IoT devices employing multiple AMP IoT transmission methods are currently deployed in a mixed manner, such as AMP IoT devices supporting OOK modulation, AMP IoT devices supporting BPSK modulation, and AMP IoT devices supporting FSK modulation. Similarly, it could include AMP IoT devices supporting OOK waveforms, AMP IoT devices supporting BPSK waveforms, AMP IoT devices supporting FSK waveforms, and AMP IoT devices supporting ASK waveforms. Of course, it is also possible to deploy only two types of AMP IoT devices, or four or more types of AMP IoT devices.

[0228] Network devices can schedule or trigger transmission only for AMP IoT devices supporting OOK modulation via the first signaling #S1, for example, the first signaling #S1 only carries indication information for OOK modulation. Network devices can schedule or trigger transmission only for AMP IoT devices supporting BPSK modulation via the first signaling #S2, for example, the first signaling #S2 only carries indication information for BPSK modulation. Network devices can schedule or trigger transmission only for AMP IoT devices supporting FSK modulation via the first signaling #S3, for example, the first signaling #S3 only carries indication information for FSK modulation. That is, in the first trigger, the network device only triggers transmission for AMP IoT devices supporting OOK modulation; in the second trigger, it only triggers transmission for AMP IoT devices supporting BPSK modulation; and in the third trigger, it only triggers transmission for AMP IoT devices supporting FSK modulation. Alternatively, in the first scheduling, the network device only schedules transmission for AMP IoT devices supporting OOK modulation; in the second scheduling, it only schedules transmission for AMP IoT devices supporting BPSK modulation; and in the third scheduling, it only schedules transmission for AMP IoT devices supporting FSK modulation.

[0229] Optionally, the first signaling also indicates a scheduling resource, scheduling or triggering the AMP IoT device to transmit on the corresponding resource. For example, the first signaling #S1 indicates resource #R1 for an AMP IoT device supporting OOK modulation, and the AMP IoT device supporting OOK modulation transmits and receives signals on resource #R1 based on the scheduling or triggering of the first signaling #S1; the first signaling #S2 indicates resource #R2 for an AMP IoT device supporting BPSK modulation, and the AMP IoT device supporting BPSK modulation transmits and receives signals on resource #R2 based on the scheduling or triggering of the first signaling #S2; the first signaling #S3 indicates resource #R3 for an AMP IoT device supporting FSK modulation, and the AMP IoT device supporting FSK modulation transmits and receives signals on resource #R3 based on the scheduling or triggering of the first signaling #S3.

[0230] Optionally, resources #R1, #R2, and #R3 are completely identical.

[0231] Optionally, resources #R1, #R2, and #R3 may differ in one or more of the following domains: time domain, frequency domain, spatial domain, and code domain.

[0232] Figure 13 provides an example of precisely scheduling or triggering AMP IoT devices based on modulation schemes or waveforms. Especially in AMP IoT scenarios where multiple modulation schemes or waveforms are deployed, the first signaling can schedule or trigger only one AMP IoT device with a target modulation scheme or waveform for uplink and / or downlink transmission at a time. If an AMP IoT device performs uplink transmission based on the first signaling, the receiver does not need to spend time and energy trying different modulation schemes or waveforms during reception, saving power and reducing transmission latency. Furthermore, it supports scheduling available resources for AMP IoT devices. Multiple AMP IoT devices can be assigned common scheduling resources, saving instruction bits and simplifying resource allocation. Alternatively, individual scheduling resources can be assigned to each AMP IoT device, improving the flexibility of resource allocation and reducing transmission conflicts.

[0233] Figure 14 illustrates a schematic diagram of an AMP IoT device scheduling method provided in an exemplary embodiment of this application. It is assumed that AMP IoT devices employing multiple AMP IoT transmission methods are currently deployed in a hybrid manner, such as AMP IoT devices supporting CDM, AMP IoT devices supporting FDM, and AMP IoT devices supporting TDM. Of course, it is also possible to deploy only two types of AMP IoT devices, or four or more types of AMP IoT devices.

[0234] Network devices can schedule or trigger transmissions only for AMP IoT devices supporting CDM using the first signaling #S1, for example, the first signaling #S1 may only carry CDM indication information. Network devices can schedule or trigger transmissions only for AMP IoT devices supporting FDM using the first signaling #S2, for example, the first signaling #S2 may only carry FDM indication information. Network devices can schedule or trigger transmissions only for AMP IoT devices supporting TDM using the first signaling #S3, for example, the first signaling #S3 may only carry TDM indication information. In other words, the network device triggers transmissions only for AMP IoT devices supporting CDM in the first trigger, only for AMP IoT devices supporting FDM in the second trigger, and only for AMP IoT devices supporting TDM in the third trigger. Alternatively, the network device schedules transmissions only for AMP IoT devices supporting CDM in the first scheduling, only for AMP IoT devices supporting FDM in the second scheduling, and only for AMP IoT devices supporting TDM in the third scheduling.

[0235] Optionally, the first signaling also indicates a scheduling resource, scheduling or triggering the AMP IoT device to transmit on the corresponding resource. For example, the first signaling #S1 indicates resource #R1 for an AMP IoT device that supports CDM, and the AMP IoT device that supports CDM sends and receives signals on resource #R1 based on the scheduling or triggering of the first signaling #S1; the first signaling #S2 indicates resource #R2 for an AMP IoT device that supports FDM, and the AMP IoT device that supports FDM sends and receives signals on resource #R2 based on the scheduling or triggering of the first signaling #S2; the first signaling #S3 indicates resource #R3 for an AMP IoT device that supports TDM, and the AMP IoT device that supports TDM sends and receives signals on resource #R3 based on the scheduling or triggering of the first signaling #S3.

[0236] Optionally, resources #R1, #R2, and #R3 are completely identical.

[0237] Optionally, resources #R1, #R2, and #R3 may differ in one or more of the following domains: time domain, frequency domain, spatial domain, and code domain.

[0238] Figure 14 provides an example of precisely scheduling or triggering AMP IoT devices based on multiplexing methods. Especially in AMP IoT scenarios with multiple multiplexing methods deployed in combination, the first signaling can schedule or trigger only one AMP IoT device with a specific target multiplexing method for uplink and / or downlink transmission in a single instance. Furthermore, it supports scheduling available resources for AMP IoT devices. Multiple AMP IoT devices can be assigned common scheduling resources, saving instruction bits and simplifying resource allocation. Alternatively, individual scheduling resources can be assigned to each AMP IoT device separately, improving the flexibility of resource allocation and reducing transmission conflicts.

[0239] Scenario 2: The first signaling schedules or triggers the transmission of multiple AMP IoT devices, and these multiple AMP IoT devices belong to various AMP IoT devices or use various AMP IoT transmission methods.

[0240] The first signaling can schedule uplink and / or downlink transmissions of multiple AMP IoT devices in a single instance, or the first signaling can trigger uplink and / or downlink transmissions of multiple AMP IoT devices in a single instance.

[0241] The first signaling message may carry only the first indication information, only the second indication information, or both the first and second indication information. Alternatively, the first signaling message may carry a third indication information, which is used to indicate both the device information of the AMP IoT device scheduled or triggered by the first signaling message and the AMP IoT transmission method scheduled or triggered by the first signaling message.

[0242] (1) When the first signaling carries at least the first instruction information:

[0243] For example, the first indication information indicates multiple target device types. An AMP IoT device that receives the first signaling can determine whether it is scheduled or triggered by the first signaling based on its own device type. Assuming that AMP IoT device 1 receives the first signaling, if the multiple target device types indicated by the first indication information include the device type of AMP IoT device 1, it means that AMP IoT device 1 is an AMP IoT device scheduled or triggered by the first signaling.

[0244] For example, the first indication information indicates multiple target device capabilities. An AMP IoT device that receives the first signaling can determine whether it has been scheduled or triggered by the first signaling based on its own device capabilities. Assuming AMP IoT device 1 receives the first signaling, if the multiple target device capabilities indicated by the first indication information include the device capabilities of AMP IoT device 1, then AMP IoT device 1 is an AMP IoT device scheduled or triggered by the first signaling.

[0245] For example, the first indication information indicates multiple target device types and multiple target device capabilities. An AMP IoT device receiving the first signaling determines whether it is scheduled or triggered by the first signaling based on its own device type and / or device capabilities. For instance, an AMP IoT device that only meets the target device type, or only meets the target device capability, or meets both the target device type and target device capability, is considered an AMP IoT device scheduled or triggered by the first signaling. Assuming both AMP IoT device 1 and AMP IoT device 2 receive the first signaling, if the target device type indicated by the first indication information includes the device type of AMP IoT device 1, then AMP IoT device 1 is an AMP IoT device scheduled or triggered by the first signaling. If the target device capability indicated by the first indication information includes the device capability of AMP IoT device 2, then AMP IoT device 2 is an AMP IoT device scheduled or triggered by the first signaling.

[0246] (2) When the first signaling carries at least the second instruction information:

[0247] For example, the second indication information indicates multiple target transmission resources. An AMP IoT device that receives the first signaling can determine whether it has been scheduled or triggered by the first signaling based on its own configured transmission resources. Assuming AMP IoT device 1 receives the first signaling, if the multiple target transmission resources indicated by the first indication information include the transmission resources configured for AMP IoT device 1, then AMP IoT device 1 is an AMP IoT device scheduled or triggered by the first signaling.

[0248] For example, the second indication information indicates the target multiplexing method. An AMP IoT device that receives the first signaling can determine whether it has been scheduled or triggered by the first signaling based on the multiplexing methods it supports. Assuming AMP IoT device 1 receives the first signaling, if the multiple target multiplexing methods indicated by the first indication information include multiplexing methods supported by AMP IoT device 1, then AMP IoT device 1 is an AMP IoT device scheduled or triggered by the first signaling.

[0249] For example, the second indication information indicates the target multiple access method. An AMP IoT device that receives the first signaling can determine whether it has been scheduled or triggered by the first signaling based on the multiple access methods it supports. Assuming AMP IoT device 1 receives the first signaling, if the multiple target multiple access methods indicated by the first indication information include the multiple access methods supported by AMP IoT device 1, then AMP IoT device 1 is an AMP IoT device scheduled or triggered by the first signaling.

[0250] For example, the second indication information indicates the target waveform. An AMP IoT device that receives the first signaling can determine whether it has been scheduled or triggered by the first signaling based on the waveforms it supports. Assuming AMP IoT device 1 receives the first signaling, if the multiple target waveforms indicated by the first indication information include waveforms supported by AMP IoT device 1, then AMP IoT device 1 is an AMP IoT device scheduled or triggered by the first signaling.

[0251] For example, the second indication information indicates the target encoding method. An AMP IoT device that receives the first signaling can determine whether it has been scheduled or triggered by the first signaling based on the encoding methods it supports. Assuming AMP IoT device 1 receives the first signaling, if the multiple target encoding methods indicated by the first indication information include encoding methods supported by AMP IoT device 1, then AMP IoT device 1 is an AMP IoT device scheduled or triggered by the first signaling.

[0252] For example, the second indication information indicates the target modulation scheme. An AMP IoT device that receives the first signaling can determine whether it has been scheduled or triggered by the first signaling based on the modulation schemes it supports. Assuming AMP IoT device 1 receives the first signaling, if the multiple target modulation schemes indicated by the first indication information include modulation schemes supported by AMP IoT device 1, then AMP IoT device 1 is an AMP IoT device scheduled or triggered by the first signaling.

[0253] For example, if the second indication information indicates multiple of the target transmission resources, target multiplexing mode, target multiple access mode, target waveform, target coding mode, and target modulation mode, then any AMP IoT device that satisfies at least some of the transmission modes indicated by the second indication information is the target AMP IoT device scheduled or triggered by the first signaling.

[0254] (3) The first signaling is also used to instruct scheduling resources for multiple AMP IoT devices:

[0255] In some embodiments, the first signaling may carry indication information of scheduling resources in addition to scheduling or triggering multiple AMP IoT devices to transmit. The scheduling resources may be common scheduling resources corresponding to multiple AMP IoT devices, or may include scheduling resources corresponding to each AMP IoT device individually, or may include scheduling resources corresponding to each type of AMP IoT device individually.

[0256] In some embodiments, the scheduling resources include one or more of the following: scheduling resources corresponding to each device type of AMP IoT device; scheduling resources corresponding to each device capability of AMP IoT device; scheduling resources corresponding to each transmission resource of AMP IoT transmission; scheduling resources corresponding to each multiplexing method used in each AMP IoT transmission; scheduling resources corresponding to each multiple access method used in each AMP IoT transmission; scheduling resources corresponding to each waveform used in each AMP IoT transmission; and scheduling resources corresponding to each encoding method used in each AMP IoT transmission.

[0257] Optionally, the first signaling indicates a unified / common scheduling resource to multiple AMP IoT devices. This resource indication scheme can save indication bits. These multiple AMP IoT devices perform uplink and / or downlink transmissions within the unified / common scheduling resource.

[0258] Optionally, the first signaling indicates scheduling resources to multiple AMP IoT devices separately. That is, the scheduling resources are indicated individually for each AMP IoT device; in other words, the indication of scheduling resources is specific to each AMP IoT device. This resource indication scheme offers high flexibility and reduces the probability of transmission conflicts between AMP IoT devices, but it requires a larger number of indication bits.

[0259] For example, the first signaling simultaneously schedules AMP IoT devices of both device capability 1 and device capability 2. Device capability 1 includes three AMP IoT devices (#D1, #D2, #D3), and device capability 2 includes two AMP IoT devices (#D4, #D5). The first signaling indicates resource A for #D1, resource B for #D2, resource C for #D3, resource D for #D4, and resource E for #D5. Each AMP IoT device transmits and receives signals in its corresponding resource. Optionally, resources A, B, C, D, and E are all different; however, it is possible for some resources to be the same or overlap.

[0260] Optionally, the first signaling indicates scheduling resources separately for each of the various AMP IoT devices. In other words, the scheduling resources are indicated individually for each AMP IoT device, meaning the indication of scheduling resources is targeted at the AMP IoT device group. This resource indication scheme offers high flexibility while requiring fewer indication bits.

[0261] For example, the first signaling simultaneously schedules AMP IoT devices with both device capability 1 and device capability 2. The first signaling instructs resource A and resource B for the AMP IoT devices with device capability 1 and device capability 2, respectively. The AMP IoT devices with device capability 1 include 3 AMP IoT devices, all of which can transmit and receive signals in resource A. The AMP IoT devices with device capability 2 include 4 AMP IoT devices, all of which can transmit and receive signals in resource B. Optionally, resources A and resources B are different from each other; however, it is possible that some resources are the same or overlap.

[0262] The device information indicated by the first indication information and / or the AMP IoT transmission method indicated by the second indication information are used by the AMP IoT device to determine whether it is scheduled or triggered by the first signaling.

[0263] The above content will now be explained with specific examples. #S1, #S2, and #S3 below are all different first signaling instructions used to implement different scheduling or triggering processes.

[0264] Figure 15 illustrates a schematic diagram of a scheduling method for AMP IoT devices provided in an exemplary embodiment of this application. It is assumed that multiple types of AMP IoT devices are currently deployed in a mixed manner, including AMP IoT devices of type i and AMP IoT devices of type ii.

[0265] The network device can carry indication information for type i and type ii in the first signaling #S1. That is, the network device can trigger both type i and type ii AMP IoT devices to transmit simultaneously in a single trigger. Or, the network device can schedule both type i and type ii AMP IoT devices to transmit simultaneously in a single scheduling.

[0266] Optionally, the first signaling also carries indication information of the transmission resources, scheduling or triggering AMP IoT devices to transmit on the corresponding resources.

[0267] Figure 15(1) shows the case where the same resources are indicated for AMP IoT devices of type i and type ii.

[0268] Figure 15(2) illustrates the case where different resources are indicated for AMP IoT devices of type i and type ii. The first signaling #S1 indicates resource #R1 for AMP IoT devices of type i, and AMP IoT devices of type i transmit and receive signals on resource #R1 based on the scheduling or triggering of the first signaling #S1; the first signaling #S1 indicates resource #R2 for AMP IoT devices of type ii, and AMP IoT devices of type ii transmit and receive signals on resource #R2 based on the scheduling or triggering of the first signaling #S1.

[0269] Optionally, resources #R1 and #R2 may differ in one or more of the following domains: time domain, frequency domain, spatial domain, and code domain.

[0270] Figure 15 provides an example of precisely scheduling or triggering AMP IoT devices based on device type. The first signaling can schedule or trigger multiple AMP IoT devices of different types in a single instance, improving scheduling efficiency and reducing the number of first signaling transmissions to minimize resource consumption. Furthermore, it supports scheduling available resources for AMP IoT devices. Multiple AMP IoT devices can be assigned shared scheduling resources, saving instruction bits and simplifying resource allocation. Alternatively, each AMP IoT device can be assigned individual scheduling resources, increasing the flexibility of resource allocation and reducing transmission conflicts.

[0271] Figure 16 illustrates a schematic diagram of an AMP IoT device scheduling method provided in an exemplary embodiment of this application. It is assumed that AMP IoT devices with multiple capabilities are currently deployed, such as capability 1 devices, capability 2 devices, and capability 3 devices. Of course, it is also possible to deploy only two types of AMP IoT devices, or four or more types of AMP IoT devices.

[0272] Taking the following examples: Device 1 is an AMP IoT device that only has active transmission capability; Device 2 is an AMP IoT device that only has backscatter capability; and Device 3 is an AMP IoT device that has both active transmission capability and backscatter capability.

[0273] Network devices can schedule or trigger transmission for capability 1, capability 2, and capability 3 devices via the first signaling #S1. For example, the first signaling #S1 carries indication information for device capability 1 (only possessing active transmission capability), device capability 2 (only possessing backscatter capability), and device capability 3 (possessing both active transmission and backscatter capabilities). In other words, the network device triggers transmission for capability 1, capability 2, and capability 3 devices in a single trigger. Or, the network device schedules transmission for capability 1, capability 2, and capability 3 devices in a single scheduling operation.

[0274] Optionally, the first signaling also indicates a scheduling resource, scheduling or triggering the AMP IoT device to transmit on the corresponding resource. For example, the first signaling #S1 indicates resource #R1 for a capability 1 device, and the capability 1 device sends and receives signals on resource #R1 based on the scheduling or triggering of the first signaling #S1; the first signaling #S1 indicates resource #R2 for a capability 2 device, and the capability 2 device sends and receives signals on resource #R2 based on the scheduling or triggering of the first signaling #S1; the first signaling #S1 indicates resource #R3 for a capability 3 device, and the capability 3 device sends and receives signals on resource #R3 based on the scheduling or triggering of the first signaling #S1.

[0275] Optionally, resources #R1, #R2, and #R3 are completely identical, as shown in Figure 16(1).

[0276] Optionally, resources #R1, #R2, and #R3 may differ in one or more of the following domains: time domain, frequency domain, spatial domain, and code domain. Figure 16(2) shows the case where they differ in the time domain, Figure 16(3) shows the case where they differ in the frequency domain, and Figure 16(4) shows the case where they differ in both the time and frequency domains.

[0277] Figure 16 provides an example of precisely scheduling or triggering AMP IoT devices based on their capabilities. The first signaling can schedule or trigger multiple AMP IoT devices with different capabilities in a single instance, improving scheduling efficiency and reducing the number of first signaling transmissions to minimize resource consumption. Furthermore, it supports scheduling available resources for AMP IoT devices. Multiple AMP IoT devices can be assigned shared scheduling resources, saving instruction bits and simplifying resource allocation. Alternatively, each AMP IoT device can be assigned individual scheduling resources, increasing the flexibility of resource allocation and reducing transmission conflicts.

[0278] Figure 17 illustrates a schematic diagram of an AMP IoT device scheduling method provided in an exemplary embodiment of this application. It is assumed that AMP IoT devices employing multiple AMP IoT transmission methods are currently deployed in a mixed manner, such as AMP IoT devices supporting OOK modulation, AMP IoT devices supporting BPSK modulation, and AMP IoT devices supporting FSK modulation. Similarly, it could include AMP IoT devices supporting OOK waveforms, AMP IoT devices supporting BPSK waveforms, AMP IoT devices supporting FSK waveforms, and AMP IoT devices supporting ASK waveforms. Of course, it is also possible to deploy only two types of AMP IoT devices, or four or more types of AMP IoT devices.

[0279] In Figures 17(1), (2), and (3), the network device can schedule or trigger AMP IoT devices that support OOK modulation, BPSK modulation, and FSK modulation to transmit data via the first signaling #S1. For example, the first signaling #S1 carries indication information for OOK modulation, BPSK modulation, and FSK modulation. That is, the network device triggers AMP IoT devices that support OOK modulation, BPSK modulation, and FSK modulation to transmit data in a single trigger. Or, the network device schedules AMP IoT devices that support OOK modulation, BPSK modulation, and FSK modulation in a single scheduling process.

[0280] Optionally, the first signaling also indicates scheduling resources, scheduling or triggering AMP IoT devices to transmit on the corresponding resources. For example, the first signaling #S1 indicates resource #R1 for AMP IoT devices supporting OOK modulation, and the AMP IoT devices supporting OOK modulation transmit and receive signals on resource #R1 based on the scheduling or triggering of the first signaling #S1; the first signaling #S1 indicates resource #R2 for AMP IoT devices supporting BPSK modulation, and the AMP IoT devices supporting BPSK modulation transmit and receive signals on resource #R2 based on the scheduling or triggering of the first signaling #S1; the first signaling #S1 indicates resource #R3 for AMP IoT devices supporting FSK modulation, and the AMP IoT devices supporting FSK modulation transmit and receive signals on resource #R3 based on the scheduling or triggering of the first signaling #S1.

[0281] In Figure 17(4), the network device can schedule or trigger AMP IoT devices that support OOK modulation and BPSK modulation to transmit via the first signaling #S1. For example, the first signaling #S1 carries indication information for OOK modulation and BPSK modulation. The network device can schedule or trigger AMP IoT devices that support FSK modulation to transmit via the first signaling #S2. For example, the first signaling #S2 carries only indication information for FSK modulation.

[0282] In other words, the network device triggers AMP IoT devices supporting OOK and BPSK modulation to transmit in the first trigger, and only triggers AMP IoT devices supporting FSK modulation to transmit in the second trigger. Alternatively, the network device schedules AMP IoT devices supporting OOK and BPSK modulation to transmit in the first scheduling, and only schedules AMP IoT devices supporting FSK modulation to transmit in the second scheduling.

[0283] Optionally, the first signaling also indicates scheduling resources, scheduling or triggering AMP IoT devices to transmit on the corresponding resources. For example, the first signaling #S1 indicates resource #R1 for AMP IoT devices supporting OOK modulation, and the AMP IoT devices supporting OOK modulation transmit and receive signals on resource #R1 based on the scheduling or triggering of the first signaling #S1; the first signaling #S1 indicates resource #R2 for AMP IoT devices supporting BPSK modulation, and the AMP IoT devices supporting BPSK modulation transmit and receive signals on resource #R2 based on the scheduling or triggering of the first signaling #S1; the first signaling #S2 indicates resource #R3 for AMP IoT devices supporting FSK modulation, and the AMP IoT devices supporting FSK modulation transmit and receive signals on resource #R3 based on the scheduling or triggering of the first signaling #S2.

[0284] Optionally, resources #R1, #R2, and #R3 are completely identical.

[0285] Optionally, resources #R1, #R2, and #R3 may differ in one or more of the following domains: time domain, frequency domain, spatial domain, and code domain.

[0286] Figure 17(1) shows the different cases in the time domain, Figure 17(2) shows the different cases in the frequency domain, Figure 17(3) shows the different cases in both the time and frequency domains, and Figure 17(4) shows the different cases in both the time and frequency domains.

[0287] Figure 17 provides an example of precisely scheduling or triggering AMP IoT devices based on modulation schemes or waveforms. The first signaling can schedule or trigger multiple AMP IoT devices supporting different modulation schemes or waveforms in a single operation, improving scheduling efficiency and reducing the number of first signaling transmissions to minimize resource consumption. Furthermore, it supports scheduling available resources for AMP IoT devices. Multiple AMP IoT devices can be assigned shared scheduling resources, saving instruction bits and simplifying resource allocation. Alternatively, each AMP IoT device can be assigned individual scheduling resources, increasing the flexibility of resource allocation and reducing transmission conflicts.

[0288] Figure 18 illustrates a schematic diagram of an AMP IoT device scheduling method provided in an exemplary embodiment of this application. It is assumed that AMP IoT devices employing multiple AMP IoT transmission methods are currently deployed in a hybrid manner, such as AMP IoT devices supporting CDM, AMP IoT devices supporting FDM, and AMP IoT devices supporting TDM. Of course, it is also possible to deploy only two types of AMP IoT devices, or four or more types of AMP IoT devices.

[0289] In Figures 18(1), (2), and (3), the network device can schedule or trigger AMP IoT devices supporting CDM, FDM, and TDM to transmit data via the first signaling #S1. For example, the first signaling #S1 carries indication information for CDM, FDM, and TDM. That is, the network device triggers AMP IoT devices supporting CDM, FDM, and TDM to transmit data in a single trigger. Or, the network device schedules AMP IoT devices supporting CDM, FDM, and TDM in a single scheduling process.

[0290] Optionally, the first signaling also indicates a scheduling resource, scheduling or triggering the AMP IoT device to transmit on the corresponding resource. For example, the first signaling #S1 indicates resource #R1 for an AMP IoT device supporting CDM, and the AMP IoT device supporting CDM transmits and receives signals on resource #R1 based on the scheduling or triggering of the first signaling #S1; the first signaling #S1 indicates resource #R2 for an AMP IoT device supporting FDM, and the AMP IoT device supporting FDM transmits and receives signals on resource #R2 based on the scheduling or triggering of the first signaling #S1; the first signaling #S1 indicates resource #R3 for an AMP IoT device supporting TDM, and the AMP IoT device supporting TDM transmits and receives signals on resource #R3 based on the scheduling or triggering of the first signaling #S1.

[0291] In Figure 18(4), the network device can schedule or trigger AMP IoT devices that support CDM and FDM to transmit via the first signaling #S1. For example, the first signaling #S1 carries indication information for CDM and FDM. The network device can schedule or trigger AMP IoT devices that support TDM to transmit via the first signaling #S2. For example, the first signaling #S2 carries indication information for TDM only.

[0292] In other words, the network device triggers AMP IoT devices that support CDM and FDM for transmission in the first trigger, and only triggers AMP IoT devices that support TDM for transmission in the second trigger. Or, the network device schedules AMP IoT devices that support CDM and FDM for transmission in the first scheduling, and only schedules AMP IoT devices that support TDM for transmission in the second scheduling.

[0293] Optionally, the first signaling also indicates a scheduling resource, scheduling or triggering the AMP IoT device to transmit on the corresponding resource. For example, the first signaling #S1 indicates resource #R1 for an AMP IoT device that supports CDM, and the AMP IoT device that supports CDM sends and receives signals on resource #R1 based on the scheduling or triggering of the first signaling #S1; the first signaling #S1 indicates resource #R2 for an AMP IoT device that supports FDM, and the AMP IoT device that supports FDM sends and receives signals on resource #R2 based on the scheduling or triggering of the first signaling #S1; the first signaling #S2 indicates resource #R3 for an AMP IoT device that supports TDM, and the AMP IoT device that supports TDM sends and receives signals on resource #R3 based on the scheduling or triggering of the first signaling #S2.

[0294] Optionally, resources #R1, #R2, and #R3 are completely identical.

[0295] Optionally, resources #R1, #R2, and #R3 may differ in one or more of the following domains: time domain, frequency domain, spatial domain, and code domain. Figure 18(1) shows the case where they differ in the time domain, Figure 18(2) shows the case where they differ in the frequency domain, Figure 18(3) shows the case where they differ in both the time and frequency domains, and Figure 18(4) shows the case where they differ in both the time and frequency domains.

[0296] Figure 18 provides an example of precisely scheduling or triggering AMP IoT devices based on multiplexing methods. The first signaling can schedule or trigger multiple AMP IoT devices supporting different multiplexing methods in a single instance, improving scheduling efficiency and reducing the number of first signaling transmissions to reduce resource consumption. Furthermore, it supports scheduling available resources for AMP IoT devices. Multiple AMP IoT devices can be assigned common scheduling resources, saving instruction bits and simplifying resource allocation. Alternatively, each AMP IoT device can be assigned individual scheduling resources, improving the flexibility of resource allocation and reducing transmission conflicts.

[0297] Figure 19 illustrates a schematic diagram of an AMP IoT device scheduling method provided in an exemplary embodiment of this application. It is assumed that the current deployment includes a mix of AMP IoT devices with various capabilities and AMP IoT devices employing various AMP IoT transmission methods, such as capability 2 (backscatter capability only), capability 3 (active transmission and backscatter capabilities), CDM-supporting AMP IoT devices, FDM-supporting AMP IoT devices, OOK waveform-supporting AMP IoT devices, and ASK modulation-supporting AMP IoT devices. Of course, it is also possible to deploy only two types of AMP IoT devices, or four or more types of AMP IoT devices.

[0298] Network devices can schedule or trigger capability 2 devices, AMP IoT devices that support CDM and FDM to transmit data through the first signaling #S1. For example, the first signaling #S1 carries indication information for capability 2, CDM and FDM.

[0299] Network devices can schedule or trigger capability 3 devices, AMP IoT devices that support OOK waveforms, and AMP IoT devices that support ASK modulation through the first signaling #S2. For example, the first signaling #S2 carries indication information for capability 3, OOK waveform, and ASK modulation.

[0300] Optionally, the first signaling also instructs on scheduling resources, scheduling or triggering AMP IoT devices to transmit on the corresponding resources. The resources corresponding to AMP IoT devices with different capabilities and AMP IoT devices using different AMP IoT transmission methods may be the same or different.

[0301] Figure 19 provides an example of precisely scheduling or triggering AMP IoT devices based on device information and transmission methods. The first signaling can schedule or trigger multiple AMP IoT devices with different device information and supporting different transmission methods in a single instance, improving scheduling efficiency and reducing the number of first signaling transmissions to reduce resource consumption. Furthermore, it supports scheduling available resources for AMP IoT devices. Multiple AMP IoT devices can be assigned common scheduling resources, saving instruction bits and simplifying the allocation of scheduling resources. Alternatively, each AMP IoT device can be assigned individual scheduling resources, improving the flexibility of scheduling resource allocation and reducing transmission conflicts.

[0302] Scenario 3: The first signaling schedules or triggers a transmission of an AMP IoT device.

[0303] The first signaling message can schedule uplink and / or downlink transmissions of an AMP IoT device in a single instance, or the first signaling message can trigger uplink and / or downlink transmissions of an AMP IoT device in a single instance.

[0304] The first signaling message may carry only the first indication information, only the second indication information, or both the first and second indication information. Alternatively, the first signaling message may carry a third indication information, which is used to indicate both the device information of the AMP IoT device scheduled or triggered by the first signaling message and the AMP IoT transmission method scheduled or triggered by the first signaling message.

[0305] Upon receiving the first signaling message, the AMP IoT device can determine whether it has been scheduled or triggered by the first signaling message based on its own device information and / or supported transmission methods. The determination principle is similar to that in case one, and will not be elaborated here.

[0306] Optionally, the first signaling also carries indication information of the transmission resources, scheduling or triggering AMP IoT devices to transmit on the corresponding resources.

[0307] Figure 20 illustrates a flowchart of a scheduling method for an AMP IoT device provided in an exemplary embodiment of this application. The method is executed by a first AMP IoT device and includes at least some of the following steps:

[0308] Step 2020: Receive the first signaling, which is used to schedule or trigger the transmission of the AMP IoT device. The first signaling carries first indication information and / or second indication information.

[0309] The first indication information indicates the device information of the AMP IoT device that is scheduled or triggered by the first signaling, and the second indication information indicates the AMP IoT transmission method that is scheduled or triggered by the first signaling.

[0310] For related information, please refer to steps 1020, Case 1, Case 2, and Case 3 above.

[0311] Step 2040: Determine whether the device itself is scheduled or triggered by the first signaling based on its own device information and / or supported AMP IoT transmission methods.

[0312] In other words, based on the first signaling, as well as its own device information and / or supported AMP IoT transmission methods, it determines whether to transmit according to the scheduling or triggering of the first signaling.

[0313] In some embodiments, if the device information indicated by the first signaling includes the device information of the first AMP IoT device, the first signaling schedules or triggers the first AMP IoT device; or if the device information indicated by the first signaling does not include the device information of the first AMP IoT device, the first signaling does not schedule or trigger the first AMP IoT device.

[0314] In some embodiments, the device information indicated by the first signaling includes the device information of the first AMP IoT device, including one or more of the following: the device type indicated by the first signaling includes the device type of the first AMP IoT device; the device capability indicated by the first signaling includes the device capability of the first AMP IoT device.

[0315] For example, when the first signaling carries first indication information, and the device information indicated by the first indication information includes the device information of the first AMP IoT device, the first AMP IoT device performs transmission based on the scheduling or triggering of the first signaling. That is, when the device information of the first AMP IoT device is the same as the device information indicated by the first signaling, or when the device information indicated by the first signaling includes the device information of the first AMP IoT device, the first AMP IoT device considers itself to be scheduled or triggered by the first signaling, and the first AMP IoT device performs uplink and / or downlink transmission according to the scheduling or triggering of the first signaling.

[0316] For example, when the first signaling carries first indication information, and the device capabilities indicated by the first indication information include the device capabilities of the first AMP IoT device, the first AMP IoT device performs transmission based on the scheduling or triggering of the first signaling. That is, when the device capabilities of the first AMP IoT device are the same as the device capabilities indicated by the first signaling, or when the device capabilities indicated by the first signaling include the device capabilities of the first AMP IoT device, the first AMP IoT device considers itself to be scheduled or triggered by the first signaling, and the first AMP IoT device performs uplink and / or downlink transmission according to the scheduling or triggering of the first signaling.

[0317] In some embodiments, the device information indicated by the first signaling does not include the device information of the first AMP IoT device, including one or more of the following: the device type indicated by the first signaling does not include the device type of the first AMP IoT device; the device capability indicated by the first signaling does not include the device capability of the first AMP IoT device.

[0318] For example, if the first signaling carries first indication information, and the device information indicated by the first indication information does not include the device information of the first AMP IoT device, the first AMP IoT device will not transmit based on the scheduling or triggering of the first signaling. That is, if the device information of the first AMP IoT device is different from the device information indicated by the first signaling, or if the device information indicated by the first signaling does not include the device information of the first AMP IoT device (i.e., the device information of the first AMP IoT device is not part of the device information indicated by the first signaling), the first AMP IoT device considers itself not to be scheduled or triggered by the first signaling, and the first AMP IoT device will not transmit according to the scheduling or triggering of the first signaling.

[0319] For example, if the first signaling carries first indication information, and the device capabilities indicated by the first indication information do not include the device capabilities of the first AMP IoT device, the first AMP IoT device will not perform transmission based on the scheduling or triggering of the first signaling. That is, if the device capabilities of the first AMP IoT device are different from the device capabilities indicated by the first signaling, or if the device capabilities indicated by the first signaling do not include the device capabilities of the first AMP IoT device (i.e., the device capabilities of the first AMP IoT device are not part of the device capabilities indicated by the first signaling), the first AMP IoT device considers itself not to be scheduled or triggered by the first signaling, and the first AMP IoT device will not perform uplink and / or downlink transmissions according to the scheduling or triggering of the first signaling.

[0320] In some embodiments, if the AMP IoT transmission method indicated by the first signaling includes a transmission method supported by the first AMP IoT device, the first signaling schedules or triggers the first AMP IoT device; or if the AMP IoT transmission method indicated by the first signaling does not include a transmission method supported by the first AMP IoT device, the first signaling does not schedule or trigger the first AMP IoT device.

[0321] In some embodiments, the AMP IoT transmission method indicated by the first signaling includes the transmission method supported by the first AMP IoT device, including one or more of the following: the transmission resources of the AMP IoT transmission indicated by the first signaling include the transmission resources configured for the first AMP IoT device; the multiplexing method used in the AMP IoT transmission indicated by the first signaling includes the multiplexing method supported by the first AMP IoT device; the multiple access method used in the AMP IoT transmission indicated by the first signaling includes the multiple access method supported by the first AMP IoT device; the waveform used in the AMP IoT transmission indicated by the first signaling includes the waveform supported by the first AMP IoT device; and the encoding method used in the AMP IoT transmission indicated by the first signaling includes the encoding method supported by the first AMP IoT device.

[0322] For example, when the first signaling carries second indication information, and the transmission resources indicated by the second indication information include the transmission resources configured for the first AMP IoT device, the first AMP IoT device performs transmission based on the scheduling or triggering of the first signaling. That is, when the transmission resources configured for the first AMP IoT device are the same as the transmission resources indicated by the first signaling, or when the transmission resources indicated by the first signaling include the transmission resources configured for the first AMP IoT device, the first AMP IoT device considers itself to be scheduled or triggered by the first signaling, and the first AMP IoT device performs uplink and / or downlink transmission according to the scheduling or triggering of the first signaling.

[0323] For example, when the first signaling carries second indication information, and the multiplexing method indicated by the second indication information includes a multiplexing method supported by the first AMP IoT device, the first AMP IoT device performs transmission based on the scheduling or triggering of the first signaling. That is, when the multiplexing method supported by the first AMP IoT device is the same as the multiplexing method indicated by the first signaling, or when the multiplexing method indicated by the first signaling includes a multiplexing method supported by the first AMP IoT device, the first AMP IoT device considers itself to be scheduled or triggered by the first signaling, and the first AMP IoT device performs uplink and / or downlink transmission according to the scheduling or triggering of the first signaling.

[0324] For example, when the first signaling carries second indication information, and the multi-access method indicated by the second indication information includes a multi-access method supported by the first AMP IoT device, the first AMP IoT device performs transmission based on the scheduling or triggering of the first signaling. That is, when the multi-access method supported by the first AMP IoT device is the same as the multi-access method indicated by the first signaling, or when the multi-access method indicated by the first signaling includes a multi-access method supported by the first AMP IoT device, the first AMP IoT device considers itself to be scheduled or triggered by the first signaling, and the first AMP IoT device performs uplink and / or downlink transmission according to the scheduling or triggering of the first signaling.

[0325] For example, when the first signaling carries second indication information, and the waveform indicated by the second indication information includes a waveform supported by the first AMP IoT device, the first AMP IoT device performs transmission based on the scheduling or triggering of the first signaling. That is, when the waveform supported by the first AMP IoT device is the same as the waveform indicated by the first signaling, or when the waveform indicated by the first signaling includes a waveform supported by the first AMP IoT device, the first AMP IoT device considers itself to be scheduled or triggered by the first signaling, and the first AMP IoT device performs uplink and / or downlink transmission according to the scheduling or triggering of the first signaling.

[0326] For example, when the first signaling carries second indication information, and the modulation scheme indicated by the second indication information includes a modulation scheme supported by the first AMP IoT device, the first AMP IoT device performs transmission based on the scheduling or triggering of the first signaling. That is, when the modulation scheme supported by the first AMP IoT device is the same as the modulation scheme indicated by the first signaling, or when the modulation scheme indicated by the first signaling includes a modulation scheme supported by the first AMP IoT device, the first AMP IoT device considers itself to be scheduled or triggered by the first signaling, and the first AMP IoT device performs uplink and / or downlink transmission according to the scheduling or triggering of the first signaling.

[0327] For example, when the first signaling carries second indication information, and the encoding method indicated by the second indication information includes an encoding method supported by the first AMP IoT device, the first AMP IoT device performs transmission based on the scheduling or triggering of the first signaling. That is, when the encoding method supported by the first AMP IoT device is the same as the encoding method indicated by the first signaling, or when the encoding method indicated by the first signaling includes an encoding method supported by the first AMP IoT device, the first AMP IoT device considers itself to be scheduled or triggered by the first signaling, and the first AMP IoT device performs uplink and / or downlink transmission according to the scheduling or triggering of the first signaling.

[0328] In some embodiments, the AMP IoT transmission method indicated by the first signaling does not include the transmission methods supported by the first AMP IoT device, including one or more of the following: the transmission resources of the AMP IoT transmission indicated by the first signaling do not include the transmission resources configured for the first AMP IoT device; the multiplexing method used in the AMP IoT transmission indicated by the first signaling does not include the multiplexing method supported by the first AMP IoT device; the multiple access method used in the AMP IoT transmission indicated by the first signaling does not include the multiple access method supported by the first AMP IoT device; the waveform used in the AMP IoT transmission indicated by the first signaling does not include the waveform supported by the first AMP IoT device; the encoding method used in the AMP IoT transmission indicated by the first signaling does not include the encoding method supported by the first AMP IoT device.

[0329] For example, if the first signaling carries second indication information, and the transmission resources indicated by the second indication information do not include the transmission resources configured for the first AMP IoT device, the first AMP IoT device will not perform transmission based on the scheduling or triggering of the first signaling. That is, if the transmission resources configured for the first AMP IoT device are different from the transmission resources indicated by the first signaling, or if the transmission resources indicated by the first signaling do not include the transmission resources configured for the first AMP IoT device, the first AMP IoT device considers itself not to be scheduled or triggered by the first signaling, and therefore will not perform transmission according to the scheduling or triggering of the first signaling.

[0330] For example, if the first signaling carries second indication information, and the multiplexing method indicated by the second indication information does not include the multiplexing method supported by the first AMP IoT device, the first AMP IoT device will not transmit based on the scheduling or triggering of the first signaling. That is, if the multiplexing method supported by the first AMP IoT device is different from the multiplexing method indicated by the first signaling, or if the multiplexing method indicated by the first signaling does not include the multiplexing method supported by the first AMP IoT device, the first AMP IoT device considers itself not to be scheduled or triggered by the first signaling, and the first AMP IoT device will not transmit according to the scheduling or triggering of the first signaling.

[0331] For example, if the first signaling carries second indication information, and the multi-access method indicated by the second indication information does not include the multi-access methods supported by the first AMP IoT device, the first AMP IoT device will not transmit based on the scheduling or triggering of the first signaling. That is, if the multi-access method supported by the first AMP IoT device is different from the multi-access method indicated by the first signaling, or if the multi-access method indicated by the first signaling does not include the multi-access methods supported by the first AMP IoT device, the first AMP IoT device considers itself not to be scheduled or triggered by the first signaling, and the first AMP IoT device will not transmit according to the scheduling or triggering of the first signaling.

[0332] For example, if the first signaling carries second indication information, and the waveform indicated by the second indication information does not include waveforms supported by the first AMP IoT device, the first AMP IoT device will not transmit based on the scheduling or triggering of the first signaling. That is, if the waveform supported by the first AMP IoT device is different from the waveform indicated by the first signaling, or if the waveform indicated by the first signaling does not include waveforms supported by the first AMP IoT device, the first AMP IoT device considers itself not to be scheduled or triggered by the first signaling, and the first AMP IoT device will not transmit according to the scheduling or triggering of the first signaling.

[0333] For example, if the first signaling carries second indication information, and the modulation scheme indicated by the second indication information does not include a modulation scheme supported by the first AMP IoT device, the first AMP IoT device will not transmit based on the scheduling or triggering of the first signaling. That is, if the modulation scheme supported by the first AMP IoT device differs from the modulation scheme indicated by the first signaling, or if the modulation scheme indicated by the first signaling does not include a modulation scheme supported by the first AMP IoT device, the first AMP IoT device considers itself not to be scheduled or triggered by the first signaling, and therefore will not transmit according to the scheduling or triggering of the first signaling.

[0334] For example, if the first signaling carries second indication information, and the encoding method indicated by the second indication information does not include encoding methods supported by the first AMP IoT device, the first AMP IoT device will not transmit based on the scheduling or triggering of the first signaling. That is, if the encoding method supported by the first AMP IoT device differs from the encoding method indicated by the first signaling, or if the encoding method indicated by the first signaling does not include encoding methods supported by the first AMP IoT device, the first AMP IoT device considers itself not to be scheduled or triggered by the first signaling, and therefore will not transmit according to the scheduling or triggering of the first signaling.

[0335] Step 2060: Based on the first signaling scheduling or triggering, perform downlink transmission and / or uplink transmission.

[0336] In some embodiments, the first signaling also indicates the scheduling resources corresponding to the scheduled / triggered AMP IoT device. The scheduling resources corresponding to different AMP IoT devices are completely different, may overlap, or may be exactly the same.

[0337] Optionally, the first signaling indicates a unified / common scheduling resource to all AMP IoT devices in this scheduling or triggering. Alternatively, the first signaling indicates separate scheduling resources to different AMP IoT devices in this scheduling or triggering.

[0338] If the first AMP IoT device believes that it has been scheduled or triggered by the first signaling, and the first signaling also carries indication information of transmission resources, then the first AMP IoT device will use the transmission resources indicated by the first signaling to perform downlink transmission and / or uplink transmission.

[0339] In some embodiments, a network device may schedule or trigger a first AMP IoT device to send signals and / or data to itself. For example, assuming the sender of the first signaling is network device #20, the first AMP IoT device schedules or triggers the first signaling to send uplink signals and / or uplink data to network device #20.

[0340] In some embodiments, a network device may schedule or trigger a first AMP IoT device to send signals and / or data to other devices. For example, assuming the sender of the first signaling is network device #20, the first AMP IoT device schedules or triggers, based on the first signaling, to send uplink signals and / or uplink data to network device #40.

[0341] In some embodiments, a network device may schedule or trigger a first AMP IoT device to receive signals and / or data sent by itself. For example, assuming that the sender of the first signaling is network device #20, the first AMP IoT device schedules or triggers based on the first signaling to receive downlink signals and / or downlink data sent by network device #20.

[0342] In some embodiments, a network device may schedule or trigger a first AMP IoT device to receive signals and / or data sent by other devices. For example, assuming the sender of the first signaling is network device #20, the first AMP IoT device may schedule or trigger based on the first signaling to receive downlink signals and / or downlink data sent by network device #40.

[0343] In summary, the method provided in this application allows AMP IoT devices to determine whether they are scheduled or triggered by the first signaling based on their own device information and / or supported transmission methods. Furthermore, the first signaling can carry various indication information, facilitating flexible and precise scheduling of AMP IoT devices. Moreover, the first signaling can also indicate scheduling resources. Indicating common scheduling resources to multiple AMP IoT devices helps save resource overhead and reduce the number of bits required for indication; indicating scheduling resources to different AMP IoT devices separately provides higher scheduling flexibility and transmission reliability, reduces conflicts and interference between AMP IoT devices of different types, capabilities, and using different transmission methods, and simplifies network-side reception.

[0344] Figure 21 shows a structural block diagram of a communication device provided in an exemplary embodiment of this application. The device can be implemented as a network device as described above, or as part of a network device as described above, or as an AP as described above, or as part of an AP as described above, or as a terminal device as described above, or as part of a terminal device as described above, or as a non-AP STA as described above, or as part of a non-AP STA as described above, or as an intermediate node as described above, or as part of an intermediate node as described above.

[0345] Optionally, the device is a wireless communication device / wireless device that supports the 802.11 protocol. Optionally, the device is a wireless communication device / wireless device that supports the 3GPP protocol.

[0346] The device includes a transmitting module 2110. Optionally, the device may also include a processing module 2130 and / or a receiving module 2150.

[0347] The sending module 2110 is used to send a first signaling message, which is used to schedule or trigger the transmission of AMP IoT devices. The first signaling message carries first indication information and / or second indication information. The first indication information indicates the device information of the AMP IoT device scheduled or triggered by the first signaling message, and the second indication information indicates the AMP IoT transmission mode scheduled or triggered by the first signaling message.

[0348] In some embodiments, the device information of the AMP IoT device includes one or more of the following: the device type of the AMP IoT device, and the device capabilities of the AMP IoT device;

[0349] In some embodiments, the AMP IoT transmission method includes one or more of the following parameters: transmission resources for AMP IoT transmission, multiplexing method used for AMP IoT transmission, multiple access method used for AMP IoT transmission, waveform used for AMP IoT transmission, and encoding method for AMP IoT transmission.

[0350] In some embodiments, the device information indicated by the first indication information and / or the AMP IoT transmission mode indicated by the second indication information are used by the AMP IoT device to determine whether it is scheduled or triggered by the first signaling.

[0351] In some embodiments, the first signaling schedules or triggers an AMP IoT device to transmit.

[0352] In some embodiments, the first indication information indicates device information of an AMP IoT device, the device information of an AMP IoT device including: a device type of an AMP IoT device, or a device capability of an AMP IoT device.

[0353] In some embodiments, the second indication information indicates an AMP IoT transmission method, which includes: a transmission resource for AMP IoT transmission, or a multiplexing method used in AMP IoT transmission, or a multiple access method used in AMP IoT transmission, or a waveform used in AMP IoT transmission, or an encoding method used in AMP IoT transmission.

[0354] In some embodiments, the first signaling also carries indication information of scheduling resources; wherein the scheduling resources are common scheduling resources corresponding to the AMP IoT device, or the scheduling resources include scheduling resources corresponding to each AMP IoT device in the AMP IoT device.

[0355] In some embodiments, the first signaling schedules or triggers multiple AMP IoT devices to transmit.

[0356] In some embodiments, the first indication information indicates device information of multiple AMP IoT devices, the device information of multiple AMP IoT devices including: device types of multiple AMP IoT devices; or, device capabilities of multiple AMP IoT devices; or, device types and device capabilities of at least one AMP IoT device.

[0357] In some embodiments, the second indication information indicates multiple AMP IoT transmission methods, which include one or more of the following: at least one AMP IoT transmission resource, at least one AMP IoT transmission multiplexing method, at least one AMP IoT transmission multiple access method, at least one AMP IoT transmission waveform, and at least one AMP IoT transmission encoding method.

[0358] In some embodiments, the first signaling also carries indication information of scheduling resources; wherein the scheduling resources are common scheduling resources corresponding to the multiple AMP IoT devices, or the scheduling resources include scheduling resources corresponding to each AMP IoT device in the multiple AMP IoT devices, or the scheduling resources include scheduling resources corresponding to each AMP IoT device in the multiple AMP IoT devices.

[0359] In some embodiments, the scheduling resources include scheduling resources corresponding to each of the multiple AMP IoT devices, including one or more of the following: the scheduling resources include scheduling resources corresponding to the device type of each AMP IoT device; the scheduling resources include scheduling resources corresponding to the device capabilities of each AMP IoT device; the scheduling resources include scheduling resources corresponding to the transmission resources of each AMP IoT transmission; the scheduling resources include scheduling resources corresponding to the multiplexing method used in each AMP IoT transmission; the scheduling resources include scheduling resources corresponding to the multiple access method used in each AMP IoT transmission; the scheduling resources include scheduling resources corresponding to the waveform used in each AMP IoT transmission; and the scheduling resources include scheduling resources corresponding to the encoding method used in each AMP IoT transmission.

[0360] In some embodiments, the scheduling resources include one or more of the following: time-domain resources, frequency-domain resources, spatial-domain resources, and code-domain resources.

[0361] In some embodiments, the processing module 2130 is used to determine whether it carries first indication information and / or second indication information.

[0362] In some embodiments, the processing module 2130 is used to determine which one or more AMP IoT devices to schedule or trigger.

[0363] In some embodiments, the receiving module 2150 is used to receive uplink transmissions scheduled or triggered by the AMP IoT device based on the first signaling.

[0364] In summary, the apparatus provided in this application supports scheduling one or more AMP IoT devices by sending a first signaling message. Since the first signaling message can indicate the device information and / or transmission method of the AMP IoT device, and different AMP IoT devices, as well as AMP IoT devices and traditional UEs, can be distinguished by device information and transmission method, the receiver of the first signaling message can determine whether it has been scheduled or triggered based on the indication information carried by the first signaling message, thereby achieving precise and flexible scheduling of AMP IoT devices.

[0365] Figure 22 shows a structural block diagram of a communication device provided in an exemplary embodiment of this application, which can be implemented as the AMP IoT device described above, or as part of the AMP IoT device described above.

[0366] Optionally, the device is a wireless communication device / wireless device that supports the 802.11 protocol. Optionally, the device is a wireless communication device / wireless device that supports the 3GPP protocol.

[0367] The device includes a receiving module 2210. Optionally, the device may also include a processing module 2230 and / or a transmitting module 2250.

[0368] The receiving module 2210 is used to receive a first signaling, which is used to schedule or trigger the transmission of AMP IoT devices. The first signaling carries first indication information and / or second indication information. The first indication information indicates the device information of the AMP IoT device scheduled or triggered by the first signaling, and the second indication information indicates the AMP IoT transmission mode scheduled or triggered by the first signaling.

[0369] In some embodiments, the device information of the AMP IoT device includes one or more of the following: the device type of the AMP IoT device, the device capabilities of the AMP IoT device; the AMP IoT transmission method includes one or more of the following parameters: the transmission resources of the AMP IoT transmission, the multiplexing method used in the AMP IoT transmission, the multiple access method used in the AMP IoT transmission, the waveform used in the AMP IoT transmission, and the encoding method of the AMP IoT transmission.

[0370] In some embodiments, the processing module 2230 is configured to determine whether the first AMP IoT device is scheduled or triggered by the first signaling based on the device information of the first AMP IoT device and / or the transmission method supported by the first AMP IoT device.

[0371] In some embodiments, if the device information indicated by the first signaling includes the device information of the first AMP IoT device, the first signaling schedules or triggers the first AMP IoT device; or if the device information indicated by the first signaling does not include the device information of the first AMP IoT device, the first signaling does not schedule or trigger the first AMP IoT device.

[0372] In some embodiments, the device information indicated by the first signaling includes the device information of the first AMP IoT device, including one or more of the following: the device type indicated by the first signaling includes the device type of the first AMP IoT device; the device capability indicated by the first signaling includes the device capability of the first AMP IoT device; the device information indicated by the first signaling does not include the device information of the first AMP IoT device, including one or more of the following: the device type indicated by the first signaling does not include the device type of the first AMP IoT device; the device capability indicated by the first signaling does not include the device capability of the first AMP IoT device.

[0373] In some embodiments, if the AMP IoT transmission method indicated by the first signaling includes a transmission method supported by the first AMP IoT device, the first signaling schedules or triggers the first AMP IoT device; or, if the AMP IoT transmission method indicated by the first signaling does not include a transmission method supported by the first AMP IoT device, the first signaling does not schedule or trigger the first AMP IoT device.

[0374] In some embodiments, the AMP IoT transmission method indicated by the first signaling includes transmission methods supported by the first AMP IoT device, including one or more of the following: the transmission resources of the AMP IoT transmission indicated by the first signaling include the transmission resources configured for the first AMP IoT device; the multiplexing method used in the AMP IoT transmission indicated by the first signaling includes the multiplexing method supported by the first AMP IoT device; the multiplexing method used in the AMP IoT transmission indicated by the first signaling includes the multiplexing method supported by the first AMP IoT device; the waveform used in the AMP IoT transmission indicated by the first signaling includes the waveform supported by the first AMP IoT device; the encoding method used in the AMP IoT transmission indicated by the first signaling includes the encoding method supported by the first AMP IoT device. The AMP IoT transmission method indicated by the first signaling does not include transmission methods supported by the first AMP IoT device, including one or more of the following: the transmission resources of the AMP IoT transmission indicated by the first signaling do not include the transmission resources configured for the first AMP IoT device; the multiplexing method used in the AMP IoT transmission indicated by the first signaling does not include the multiplexing method supported by the first AMP IoT device; the multiplexing method used in the AMP IoT transmission indicated by the first signaling does not include the multiplexing method supported by the first AMP IoT device; the waveform used in the AMP IoT transmission indicated by the first signaling does not include the waveform supported by the first AMP IoT device. The waveforms supported by the IoT device; the encoding method used by the AMP IoT transmission indicated by the first signaling does not include the encoding method supported by the first AMP IoT device.

[0375] In some embodiments, the first signaling schedules or triggers an AMP IoT device to transmit.

[0376] In some embodiments, the first indication information indicates device information of an AMP IoT device, the device information of an AMP IoT device including: a device type of an AMP IoT device, or a device capability of an AMP IoT device.

[0377] In some embodiments, the second indication information indicates an AMP IoT transmission method, which includes: a transmission resource for AMP IoT transmission, or a multiplexing method used in AMP IoT transmission, or a multiple access method used in AMP IoT transmission, or a waveform used in AMP IoT transmission, or an encoding method used in AMP IoT transmission.

[0378] In some embodiments, the first signaling also carries indication information of scheduling resources; wherein the scheduling resources are common scheduling resources corresponding to the AMP IoT device, or the scheduling resources include scheduling resources corresponding to each AMP IoT device in the AMP IoT device.

[0379] In some embodiments, the first signaling schedules or triggers multiple AMP IoT devices to transmit.

[0380] In some embodiments, the first indication information indicates device information of multiple AMP IoT devices, the device information of multiple AMP IoT devices including: device types of multiple AMP IoT devices; or, device capabilities of multiple AMP IoT devices; or, device types and device capabilities of at least one AMP IoT device.

[0381] In some embodiments, the second indication information indicates multiple AMP IoT transmission methods, which include one or more of the following: at least one AMP IoT transmission resource, at least one AMP IoT transmission multiplexing method, at least one AMP IoT transmission multiple access method, at least one AMP IoT transmission waveform, and at least one AMP IoT transmission encoding method.

[0382] In some embodiments, the first signaling also carries indication information of scheduling resources; wherein the scheduling resources are common scheduling resources corresponding to the multiple AMP IoT devices, or the scheduling resources include scheduling resources corresponding to each AMP IoT device in the multiple AMP IoT devices, or the scheduling resources include scheduling resources corresponding to each AMP IoT device in the multiple AMP IoT devices.

[0383] In some embodiments, the scheduling resources include scheduling resources corresponding to each of the multiple AMP IoT devices, including one or more of the following: the scheduling resources include scheduling resources corresponding to the device type of each AMP IoT device; the scheduling resources include scheduling resources corresponding to the device capabilities of each AMP IoT device; the scheduling resources include scheduling resources corresponding to the transmission resources of each AMP IoT transmission; the scheduling resources include scheduling resources corresponding to the multiplexing method used in each AMP IoT transmission; the scheduling resources include scheduling resources corresponding to the multiple access method used in each AMP IoT transmission; the scheduling resources include scheduling resources corresponding to the waveform used in each AMP IoT transmission; and the scheduling resources include scheduling resources corresponding to the encoding method used in each AMP IoT transmission.

[0384] In some embodiments, the scheduling resources include one or more of the following: time-domain resources, frequency-domain resources, spatial-domain resources, and code-domain resources.

[0385] In some embodiments, the transmitting module 2250 is used to transmit signals / data. Optionally, the transmitting module 2250 transmits signals / data using an active transmission method. Optionally, the transmitting module 2250 transmits signals / data using a backscattering method.

[0386] In some embodiments, the processing module 2230 is used for energy harvesting.

[0387] In some embodiments, the energy used by the receiving module 2210 and / or the transmitting module 2250 is the energy collected by the processing module 2230.

[0388] In summary, the apparatus provided in this application supports determining whether an AMP IoT device has been scheduled or triggered by receiving a first signaling message. Since the first signaling message can indicate the device information and / or transmission method of the AMP IoT device, and different AMP IoT devices, as well as between AMP IoT devices and traditional UEs, can be distinguished by device information and transmission method, the receiver of the first signaling message can determine whether it has been scheduled or triggered based on the indication information carried by the first signaling message, thereby achieving precise and flexible scheduling of AMP IoT devices.

[0389] It should be noted that the apparatus provided in the above embodiments is only illustrated by the division of the above functional modules. In practical applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the communication device can be divided into different functional modules to complete all or part of the functions described above. In addition, the apparatus and method embodiments provided in the above embodiments belong to the same concept.

[0390] Figure 23 shows a schematic diagram of the structure of a communication device 2300 provided in an exemplary embodiment of this application, including at least one of the following: a receiver 2301, a transmitter 2302, a processor 2303, a memory 2304, and a bus (not shown in the figure). The communication device 2300 is used to perform some or all of the steps performed by the network device, AP, terminal device, non-AP STA, or intermediate node described above. The receiver 2301 is used to implement the receiving function, and the transmitter 2302 is used to implement the transmitting function.

[0391] In some embodiments, receiver 2301 can be used to implement the functions and steps of receiving module 2150, and transmitter 2302 can be used to implement the functions and steps of sending module 2110.

[0392] Optionally, the receiver 2301 and transmitter 2302 can be implemented as a communication component, which can be a communication chip, and can be referred to as a transceiver. Optionally, the receiver 2301 and transmitter 2302 can be implemented as a wireless communication component and / or a wired communication component. Optionally, the wireless communication component includes a wireless communication chip and / or a radio frequency antenna. Optionally, the wired communication component includes a wired communication chip and / or a wired interface.

[0393] The processor 2303 includes one or more processing cores. The processor 2303 executes various functional applications and information processing by running software programs and modules. In some embodiments, the processor 2303 can be used to implement the functions and steps of the processing module 2130 described above. The memory 2304 can be used to store computer programs executed by the processor 2303, which executes the computer programs to implement the various steps in the above method embodiments.

[0394] In some embodiments, the memory 2304 may be connected to the processor 2303, the receiver 2301, and the transmitter 2302.

[0395] Furthermore, the memory 2304 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, including but not limited to: magnetic disks or optical disks, EEPROM (Electrically Erasable Programmable Read Only Memory), EPROM (Erasable Programmable Read Only Memory), SRAM (Static Random Access Memory), ROM (Read-Only Memory), magnetic storage, flash memory, and PROM (Programmable Read-Only Memory).

[0396] In some embodiments, the receiver 2301 independently receives signals / data, or the processor 2303 controls the receiver 2301 to receive signals / data, or the processor 2303 requests the receiver 2301 to receive signals / data, or the processor 2303 cooperates with the receiver 2301 to receive signals / data.

[0397] In some embodiments, the transmitter 2302 independently transmits signals / data, or the processor 2303 controls the transmitter 2302 to transmit signals / data, or the processor 2303 requests the transmitter 2302 to transmit signals / data, or the processor 2303 cooperates with the transmitter 2302 to transmit signals / data.

[0398] For details not described in this embodiment, please refer to the embodiments above, which will not be repeated here.

[0399] Figure 24 shows a schematic diagram of the structure of a communication device 2400 provided in an exemplary embodiment of this application, including at least one of the following: a receiver 2410, a transmitter 2420, a processor 2430, a memory 2440, and a bus (not shown in the figure). The communication device 2400 can be used to perform some or all of the steps performed by the AMP IoT device described above.

[0400] Receiver 2410 is used to implement the receiving function, and transmitter 2420 is used to implement the transmitting function.

[0401] In some embodiments, receiver 2410 and transmitter 2420 can be implemented as a communication component, which may be a communication chip, and may be referred to as a transceiver. Exemplarily, receiver 2410 and transmitter 2420 are implemented as a wireless communication component. Optionally, the wireless communication component includes a wireless communication chip and / or a radio frequency antenna (not shown in the figure).

[0402] In some embodiments, receiver 2410 can be used to implement the functions and steps of receiving module 2210 described above. Optionally, receiver 2410 can be implemented as a first receiver 2413 and a second receiver 2415. Optionally, the first receiver 2413 and the second receiver 2415 are two independently operating receivers, that is, receiver 2410 includes two mutually independent first receivers 2413 and second receivers 2415. Optionally, receiver 2410 can be implemented as a combined receiver of the first receiver 2413 and the second receiver 2415.

[0403] In some embodiments, the first receiver 2413 is implemented as a WUR (Wake-up Receiver), and may also be called LP-WUR (Low Power WUR), ULP-WUR (Ultra Low Power WUR), low power receiver, ultra-low power receiver, zero power receiver, auxiliary receiver, etc.

[0404] In some embodiments, the second receiver 2415 is implemented as a master receiver or a legacy receiver.

[0405] In some embodiments, transmitter 2420 can be used to implement the functions and steps of the transmitting module 2250 described above. Optionally, transmitter 2420 can be implemented as a first transmitter 2423 and / or a second transmitter 2425. Optionally, the first transmitter 2423 and the second transmitter 2425 are two transmitters that operate independently, that is, transmitter 2420 includes two mutually independent first transmitters 2423 and second transmitters 2425. Optionally, transmitter 2420 can be implemented as a combined transmitter of the first transmitter 2423 and the second transmitter 2425.

[0406] In some embodiments, the first transmitter 2423 is implemented as a backscatter transmitter, and the second transmitter 2425 is implemented as a main transmitter.

[0407] In some embodiments, the processor 2430 and the receiver 2410 may be implemented as a single module, or the processor 2430 may be implemented as part of the receiver 2410.

[0408] The processor 2430 includes one or more processing cores. The processor 2430 executes various functional applications and information processing by running software programs and modules. In some embodiments, the processor 2430 can be used to implement the functions and steps of the processing module 2230 described above.

[0409] The memory 2440 can be used to store a computer program executed by the processor 2430, which is used to execute the computer program to implement the various steps in the above method embodiments.

[0410] In some embodiments, the memory 2440 may be connected to the processor 2430, the receiver 2410, and the transmitter 2420. Furthermore, the memory 2440 may be implemented by any type of volatile or non-volatile storage device or a combination thereof, including but not limited to: magnetic disks or optical disks, EEPROM, EPROM, SRAM, ROM, magnetic storage, flash memory, and PROM.

[0411] In some embodiments, the receiver 2410 independently receives signals / data, or the processor 2430 controls the receiver 2410 to receive signals / data, or the processor 2430 requests the receiver 2410 to receive signals / data, or the processor 2430 cooperates with the receiver 2410 to receive signals / data.

[0412] In some embodiments, the transmitter 2420 independently transmits signals / data, or the processor 2430 controls the transmitter 2420 to transmit signals / data, or the processor 2430 requests the transmitter 2420 to transmit signals / data, or the processor 2430 cooperates with the transmitter 2420 to transmit signals / data.

[0413] For details not described in this embodiment, please refer to the embodiments above, which will not be repeated here.

[0414] In one exemplary embodiment of this application, a chip is also provided, the chip including programmable logic circuits and / or program instructions, which, when the chip is run on a communication device, is used to implement the scheduling method of the AMP IoT device provided in the above-described method embodiments.

[0415] In some embodiments, the chip includes a transmitting module 2110. Optionally, the chip further includes a processing module 2130 and / or a receiving module 2150. Optionally, each module can be implemented as a circuit structure. Related details can be found above and will not be repeated here.

[0416] In some embodiments, the chip includes a receiving module 2210. Optionally, the chip further includes a processing module 2230 and / or a transmitting module 2250. Optionally, each module can be implemented as a circuit structure. Related details can be found above and will not be repeated here.

[0417] In one exemplary embodiment of this application, a computer-readable storage medium is also provided, which stores at least one program that is loaded and executed by a processor to implement the scheduling method for AMP IoT devices provided in the above-described method embodiments.

[0418] In one exemplary embodiment of this application, a computer program product is also provided, which includes computer instructions stored in a computer-readable storage medium. A processor retrieves the computer instructions from the computer-readable storage medium and executes the computer instructions to implement the scheduling method for the AMP IoT device provided in the above-described method embodiments.

[0419] In one exemplary embodiment of this application, a computer program is also provided, the computer program including computer instructions, the computer instructions being stored in a computer-readable storage medium, a processor retrieving the computer instructions from the computer-readable storage medium, and the processor executing the computer instructions to implement the scheduling method for the AMP IoT device provided in the above-described method embodiments.

[0420] Those skilled in the art will understand that all or part of the steps of the above embodiments can be implemented by hardware or by a program instructing related hardware. The program can be stored in a computer-readable storage medium, such as a read-only memory, a disk, or an optical disk.

[0421] The above are merely optional embodiments of this application and are not intended to limit this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the protection scope of this application.

Claims

1. A scheduling method for AMP IoT devices, characterized in that, The method includes: Send a first signaling message, which is used to schedule or trigger the transmission of AMP IoT devices in the environment. The first signaling message carries a first indication information and / or a second indication information. The first indication information indicates the device information of the AMP IoT device scheduled or triggered by the first signaling message, and the second indication information indicates the AMP IoT transmission mode scheduled or triggered by the first signaling message.

2. The method according to claim 1, characterized in that, The device information of the AMP IoT device includes one or more of the following: the device type of the AMP IoT device, and the device capabilities of the AMP IoT device; The AMP IoT transmission method includes one or more of the following parameters: transmission resources for AMP IoT transmission, multiplexing method used in AMP IoT transmission, multiple access method used in AMP IoT transmission, waveform used in AMP IoT transmission, and encoding method used in AMP IoT transmission.

3. The method according to claim 1 or 2, characterized in that, The device information indicated by the first indication information and / or the AMP IoT transmission mode indicated by the second indication information are used by the AMP IoT device to determine whether it is scheduled or triggered by the first signaling.

4. The method according to any one of claims 1 to 3, characterized in that, The first signaling schedules or triggers an AMP IoT device to transmit data.

5. The method according to claim 4, characterized in that, The first indication information indicates device information of an AMP IoT device, which includes: device type of an AMP IoT device, or device capability of an AMP IoT device.

6. The method according to claim 4 or 5, characterized in that, The second indication information indicates an AMP IoT transmission method, which includes: a transmission resource for AMP IoT transmission, or a multiplexing method used in AMP IoT transmission, or a multiple access method used in AMP IoT transmission, or a waveform used in AMP IoT transmission, or an encoding method used in AMP IoT transmission.

7. The method according to any one of claims 4 to 6, characterized in that, The first signaling also carries indication information for scheduling resources; The scheduling resource is either a common scheduling resource corresponding to the AMP IoT device, or the scheduling resource includes the scheduling resources corresponding to each AMP IoT device in the AMP IoT device.

8. The method according to any one of claims 1 to 3, characterized in that, The first signaling schedules or triggers multiple AMP IoT devices to transmit data.

9. The method according to claim 8, characterized in that, The first indication information indicates device information for multiple AMP IoT devices, which includes: device types of multiple AMP IoT devices; or, device capabilities of multiple AMP IoT devices; or, device types and device capabilities of at least one AMP IoT device.

10. The method according to claim 8 or 9, characterized in that, The second indication information indicates multiple AMP IoT transmission methods, which include one or more of the following: at least one AMP IoT transmission resource, at least one AMP IoT transmission multiplexing method, at least one AMP IoT transmission multiple access method, at least one AMP IoT transmission waveform, and at least one AMP IoT transmission encoding method.

11. The method according to any one of claims 8 to 10, characterized in that, The first signaling also carries indication information for scheduling resources; Wherein, the scheduling resource is the common scheduling resource corresponding to the multiple AMP IoT devices, or the scheduling resource includes the scheduling resource corresponding to each AMP IoT device in the multiple AMP IoT devices, or the scheduling resource includes the scheduling resource corresponding to each type of AMP IoT device in the multiple AMP IoT devices.

12. The method according to claim 11, characterized in that, The scheduling resources include one or more of the following: scheduling resources corresponding to each device type of AMP IoT device; scheduling resources corresponding to each device capability of AMP IoT device; scheduling resources corresponding to each transmission resource of AMP IoT transmission; scheduling resources corresponding to each multiplexing method used in each AMP IoT transmission; scheduling resources corresponding to each multiple access method used in each AMP IoT transmission; scheduling resources corresponding to each waveform used in each AMP IoT transmission; and scheduling resources corresponding to each encoding method used in each AMP IoT transmission.

13. The method according to claim 7, 11, or 12, characterized in that, The scheduling resources include one or more of the following: time domain resources, frequency domain resources, spatial domain resources, and code domain resources.

14. A scheduling method for AMP IoT devices, characterized in that, The method is executed by a first AMP IoT device, and the method includes: Receive a first signaling message, which is used to schedule or trigger the transmission of an AMP IoT device in the environment. The first signaling message carries a first indication information and / or a second indication information. The first indication information indicates the device information of the AMP IoT device scheduled or triggered by the first signaling message, and the second indication information indicates the AMP IoT transmission mode scheduled or triggered by the first signaling message.

15. The method according to claim 14, characterized in that, The device information of the AMP IoT device includes one or more of the following: the device type of the AMP IoT device, and the device capabilities of the AMP IoT device; The AMP IoT transmission method includes one or more of the following parameters: the transmission resources for AMP IoT transmission, and the transmission method used by AMP IoT transmission. Multiplexing method, multiple access method used in AMP IoT transmission, waveform used in AMP IoT transmission, encoding method used in AMP IoT transmission.

16. The method according to claim 14 or 15, characterized in that, The method further includes: Based on the device information of the first AMP IoT device and / or the transmission methods supported by the first AMP IoT device, determine whether the first AMP IoT device is scheduled or triggered by the first signaling.

17. The method according to claim 16, characterized in that, If the device information indicated by the first signaling includes the device information of the first AMP IoT device, the first signaling schedules or triggers the first AMP IoT device. or, If the device information indicated by the first signaling does not include the device information of the first AMP IoT device, the first signaling will not schedule or trigger the first AMP IoT device.

18. The method according to claim 17, characterized in that, The device information indicated by the first signaling includes the device information of the first AMP IoT device, including one or more of the following: the device type indicated by the first signaling includes the device type of the first AMP IoT device, and the device capability indicated by the first signaling includes the device capability of the first AMP IoT device; The situation where the device information indicated by the first signaling does not include the device information of the first AMP IoT device includes one or more of the following: the device type indicated by the first signaling does not include the device type of the first AMP IoT device, and the device capability indicated by the first signaling does not include the device capability of the first AMP IoT device.

19. The method according to any one of claims 14 to 18, characterized in that, If the AMP IoT transmission method indicated by the first signaling includes a transmission method supported by the first AMP IoT device, the first signaling schedules or triggers the first AMP IoT device; or, If the AMP IoT transmission method indicated by the first signaling does not include the transmission method supported by the first AMP IoT device, the first signaling will not schedule or trigger the first AMP IoT device.

20. The method according to claim 19, characterized in that, The AMP IoT transmission method indicated by the first signaling includes the transmission methods supported by the first AMP IoT device, including one or more of the following: the transmission resources of the AMP IoT transmission indicated by the first signaling include the transmission resources configured for the first AMP IoT device; the multiplexing method used by the AMP IoT transmission indicated by the first signaling includes the multiplexing methods supported by the first AMP IoT device; the multiple access method used by the AMP IoT transmission indicated by the first signaling includes the multiple access methods supported by the first AMP IoT device; the waveform used by the AMP IoT transmission indicated by the first signaling includes the waveforms supported by the first AMP IoT device; and the encoding method used by the AMP IoT transmission indicated by the first signaling includes the encoding methods supported by the first AMP IoT device. The case where the AMP IoT transmission method indicated by the first signaling does not include the transmission methods supported by the first AMP IoT device includes one or more of the following: the transmission resources of the AMP IoT transmission indicated by the first signaling do not include the transmission resources configured for the first AMP IoT device; the multiplexing method used in the AMP IoT transmission indicated by the first signaling does not include the multiplexing method supported by the first AMP IoT device; the multiple access method used in the AMP IoT transmission indicated by the first signaling does not include the multiple access method supported by the first AMP IoT device; the waveform used in the AMP IoT transmission indicated by the first signaling does not include the waveform supported by the first AMP IoT device; and the encoding method used in the AMP IoT transmission indicated by the first signaling does not include the encoding method supported by the first AMP IoT device.

21. The method according to any one of claims 14 to 20, characterized in that, The first signaling schedules or triggers an AMP IoT device to transmit data.

22. The method according to claim 21, characterized in that, The first indication information indicates device information of an AMP IoT device, which includes: device type of an AMP IoT device, or device capability of an AMP IoT device.

23. The method according to claim 21 or 22, characterized in that, The second indication information indicates an AMP IoT transmission method, which includes: a transmission resource for AMP IoT transmission, or a multiplexing method used in AMP IoT transmission, or a multiple access method used in AMP IoT transmission, or a waveform used in AMP IoT transmission, or an encoding method used in AMP IoT transmission.

24. The method according to any one of claims 21 to 23, characterized in that, The first signaling also carries indication information for scheduling resources; The scheduling resource is either a common scheduling resource corresponding to the AMP IoT device, or the scheduling resource includes the scheduling resources corresponding to each AMP IoT device in the AMP IoT device.

25. The method according to any one of claims 14 to 20, characterized in that, The first signaling schedules or triggers multiple AMP IoT devices to transmit data.

26. The method according to claim 25, characterized in that, The first indication information indicates device information for multiple AMP IoT devices, which includes: device types of multiple AMP IoT devices; or, device capabilities of multiple AMP IoT devices; or, device types and device capabilities of at least one AMP IoT device.

27. The method according to claim 25 or 26, characterized in that, The second indication information indicates multiple AMP IoT transmission methods, which include one or more of the following: at least one AMP IoT transmission resource, at least one AMP IoT transmission multiplexing method, at least one AMP IoT transmission multiple access method, at least one AMP IoT transmission waveform, and at least one AMP IoT transmission encoding method.

28. The method according to any one of claims 25 to 27, characterized in that, The first signaling also carries indication information for scheduling resources; Wherein, the scheduling resource is the common scheduling resource corresponding to the multiple AMP IoT devices, or the scheduling resource includes the scheduling resource corresponding to each AMP IoT device in the multiple AMP IoT devices, or the scheduling resource includes the scheduling resource corresponding to each type of AMP IoT device in the multiple AMP IoT devices.

29. The method according to claim 28, characterized in that, The scheduling resources include scheduling resources corresponding to each of the various AMP IoT devices, including one or more of the following: scheduling resources corresponding to the device type of each AMP IoT device; scheduling resources corresponding to the device capabilities of each AMP IoT device; scheduling resources corresponding to the transmission resources of each AMP IoT transmission; scheduling resources corresponding to the multiplexing method used in each AMP IoT transmission; scheduling resources corresponding to the multiple access method used in each AMP IoT transmission; scheduling resources corresponding to the waveform used in each AMP IoT transmission; and scheduling resources corresponding to the encoding method used in each AMP IoT transmission.

30. The method according to claim 24, 28, or 29, characterized in that, The scheduling resources include one or more of the following: time domain resources, frequency domain resources, spatial domain resources, and code domain resources.

31. A communication device, characterized in that, The device includes: The sending module is used to send a first signaling message, which is used to schedule or trigger the transmission of an AMP IoT device in the environment. The first signaling message carries a first indication information and / or a second indication information. The first indication information indicates the device information of the AMP IoT device scheduled or triggered by the first signaling message, and the second indication information indicates the AMP IoT transmission mode scheduled or triggered by the first signaling message.

32. The apparatus according to claim 31, characterized in that, The device information of the AMP IoT device includes one or more of the following: the device type of the AMP IoT device, and the device capabilities of the AMP IoT device; The AMP IoT transmission method includes one or more of the following parameters: transmission resources for AMP IoT transmission, multiplexing method used in AMP IoT transmission, multiple access method used in AMP IoT transmission, waveform used in AMP IoT transmission, and encoding method used in AMP IoT transmission.

33. The apparatus according to claim 31 or 32, characterized in that, The device information indicated by the first indication information and / or the AMP IoT transmission mode indicated by the second indication information are used by the AMP IoT device to determine whether it is scheduled or triggered by the first signaling.

34. The apparatus according to any one of claims 31 to 33, characterized in that, The first signaling schedules or triggers an AMP IoT device to transmit data.

35. The apparatus according to claim 34, characterized in that, The first indication information indicates device information of an AMP IoT device, which includes: device type of an AMP IoT device, or device capability of an AMP IoT device.

36. The apparatus according to claim 34 or 35, characterized in that, The second indication information indicates an AMP IoT transmission method, which includes: a transmission resource for AMP IoT transmission, or a multiplexing method used in AMP IoT transmission, or a multiple access method used in AMP IoT transmission, or a waveform used in AMP IoT transmission, or an encoding method used in AMP IoT transmission.

37. The apparatus according to any one of claims 34 to 36, characterized in that, The first signaling also carries indication information for scheduling resources; The scheduling resource is either a common scheduling resource corresponding to the AMP IoT device, or the scheduling resource includes the scheduling resources corresponding to each AMP IoT device in the AMP IoT device.

38. The apparatus according to any one of claims 31 to 33, characterized in that, The first signaling schedules or triggers multiple AMP IoT devices to transmit data.

39. The apparatus according to claim 38, characterized in that, The first indication information indicates device information for multiple AMP IoT devices, which includes: device types of multiple AMP IoT devices; or, device capabilities of multiple AMP IoT devices; or, device types and device capabilities of at least one AMP IoT device.

40. The apparatus according to claim 38 or 39, characterized in that, The second indication information indicates multiple AMP IoT transmission methods, which include one or more of the following: at least one AMP IoT transmission resource, at least one AMP IoT transmission multiplexing method, at least one AMP IoT transmission multiple access method, at least one AMP IoT transmission waveform, and at least one AMP IoT transmission encoding method.

41. The apparatus according to any one of claims 38 to 40, characterized in that, The first signaling also carries indication information for scheduling resources; Wherein, the scheduling resource is the common scheduling resource corresponding to the multiple AMP IoT devices, or the scheduling resource includes the scheduling resource corresponding to each AMP IoT device in the multiple AMP IoT devices, or the scheduling resource includes the scheduling resource corresponding to each type of AMP IoT device in the multiple AMP IoT devices.

42. The apparatus according to claim 41, characterized in that, The scheduling resources include one or more of the following: scheduling resources corresponding to each device type of AMP IoT device; scheduling resources corresponding to each device capability of AMP IoT device; scheduling resources corresponding to each transmission resource of AMP IoT transmission; scheduling resources corresponding to each multiplexing method used in each AMP IoT transmission; scheduling resources corresponding to each multiple access method used in each AMP IoT transmission; scheduling resources corresponding to each waveform used in each AMP IoT transmission; and scheduling resources corresponding to each encoding method used in each AMP IoT transmission.

43. The apparatus according to claim 37, 41, or 42, characterized in that, The scheduling resources include one or more of the following: time domain resources, frequency domain resources, spatial domain resources, and code domain resources.

44. A communication device, characterized in that, The device includes: The receiving module is used to receive a first signaling, which is used to schedule or trigger the transmission of an AMP IoT device in the environment. The first signaling carries first indication information and / or second indication information. The first indication information indicates the device information of the AMP IoT device scheduled or triggered by the first signaling, and the second indication information indicates the AMP IoT transmission mode scheduled or triggered by the first signaling.

45. The apparatus according to claim 44, characterized in that, The device information of the AMP IoT device includes one or more of the following: the device type of the AMP IoT device, and the device capabilities of the AMP IoT device; The AMP IoT transmission method includes one or more of the following parameters: transmission resources for AMP IoT transmission, multiplexing method used in AMP IoT transmission, multiple access method used in AMP IoT transmission, waveform used in AMP IoT transmission, and encoding method used in AMP IoT transmission.

46. ​​The apparatus according to claim 44 or 45, characterized in that, The device further includes: The processing module is used to determine whether the first AMP IoT device is scheduled or triggered by the first signaling based on the device information of the first AMP IoT device and / or the transmission method supported by the first AMP IoT device.

47. The apparatus according to claim 46, characterized in that, If the device information indicated by the first signaling includes the device information of the first AMP IoT device, the first signaling schedules or triggers the first AMP IoT device. or, If the device information indicated by the first signaling does not include the device information of the first AMP IoT device, the first signaling will not schedule or trigger the first AMP IoT device.

48. The apparatus according to claim 47, characterized in that, The device information indicated by the first signaling includes the device information of the first AMP IoT device, including one or more of the following: the device type indicated by the first signaling includes the device type of the first AMP IoT device, and the device capability indicated by the first signaling includes the device capability of the first AMP IoT device; The situation where the device information indicated by the first signaling does not include the device information of the first AMP IoT device includes one or more of the following: the device type indicated by the first signaling does not include the device type of the first AMP IoT device, and the device capability indicated by the first signaling does not include the device capability of the first AMP IoT device.

49. The apparatus according to any one of claims 44 to 48, characterized in that, If the AMP IoT transmission method indicated by the first signaling includes a transmission method supported by the first AMP IoT device, the first signaling schedules or triggers the first AMP IoT device; or, If the AMP IoT transmission method indicated by the first signaling does not include the transmission method supported by the first AMP IoT device, the first signaling will not schedule or trigger the first AMP IoT device.

50. The apparatus according to claim 49, characterized in that, The AMP IoT transmission method indicated by the first signaling includes the transmission methods supported by the first AMP IoT device, including one or more of the following: the transmission resources of the AMP IoT transmission indicated by the first signaling include the transmission resources configured for the first AMP IoT device; the multiplexing method used by the AMP IoT transmission indicated by the first signaling includes the multiplexing methods supported by the first AMP IoT device; the multiple access method used by the AMP IoT transmission indicated by the first signaling includes the multiple access methods supported by the first AMP IoT device; the waveform used by the AMP IoT transmission indicated by the first signaling includes the waveforms supported by the first AMP IoT device; and the encoding method used by the AMP IoT transmission indicated by the first signaling includes the encoding methods supported by the first AMP IoT device. The case where the AMP IoT transmission method indicated by the first signaling does not include the transmission methods supported by the first AMP IoT device includes one or more of the following: the transmission resources of the AMP IoT transmission indicated by the first signaling do not include the transmission resources configured for the first AMP IoT device; the multiplexing method used in the AMP IoT transmission indicated by the first signaling does not include the multiplexing method supported by the first AMP IoT device; the multiple access method used in the AMP IoT transmission indicated by the first signaling does not include the multiple access method supported by the first AMP IoT device; the waveform used in the AMP IoT transmission indicated by the first signaling does not include the waveform supported by the first AMP IoT device; and the encoding method used in the AMP IoT transmission indicated by the first signaling does not include the encoding method supported by the first AMP IoT device.

51. The apparatus according to any one of claims 44 to 50, characterized in that, The first signaling schedules or triggers an AMP IoT device to transmit data.

52. The apparatus according to claim 51, characterized in that, The first indication information indicates device information of an AMP IoT device, which includes: device type of an AMP IoT device, or device capability of an AMP IoT device.

53. The apparatus according to claim 51 or 52, characterized in that, The second indication information indicates an AMP IoT transmission method, which includes: a transmission resource for AMP IoT transmission, or a multiplexing method used in AMP IoT transmission, or a multiple access method used in AMP IoT transmission, or a waveform used in AMP IoT transmission, or an encoding method used in AMP IoT transmission.

54. The apparatus according to any one of claims 51 to 53, characterized in that, The first signaling also carries indication information for scheduling resources; The scheduling resource is either a common scheduling resource corresponding to the AMP IoT device, or the scheduling resource includes the scheduling resources corresponding to each AMP IoT device in the AMP IoT device.

55. The apparatus according to any one of claims 44 to 50, characterized in that, The first signaling schedules or triggers multiple AMP IoT devices to transmit data.

56. The apparatus according to claim 55, characterized in that, The first indication information indicates device information for multiple AMP IoT devices, which includes: device types of multiple AMP IoT devices; or, device capabilities of multiple AMP IoT devices; or, device types and device capabilities of at least one AMP IoT device.

57. The apparatus according to claim 55 or 56, characterized in that, The second indication information indicates multiple AMP IoT transmission methods, which include one or more of the following: at least one AMP IoT transmission resource, at least one AMP IoT transmission multiplexing method, at least one AMP IoT transmission multiple access method, at least one AMP IoT transmission waveform, and at least one AMP IoT transmission encoding method.

58. The apparatus according to any one of claims 55 to 57, characterized in that, The first signaling also carries indication information for scheduling resources; Wherein, the scheduling resource is the common scheduling resource corresponding to the multiple AMP IoT devices, or the scheduling resource includes the scheduling resource corresponding to each AMP IoT device in the multiple AMP IoT devices, or the scheduling resource includes the scheduling resource corresponding to each type of AMP IoT device in the multiple AMP IoT devices.

59. The apparatus according to claim 58, characterized in that, The scheduling resources include scheduling resources corresponding to each of the various AMP IoT devices, including one or more of the following: scheduling resources corresponding to the device type of each AMP IoT device; scheduling resources corresponding to the device capabilities of each AMP IoT device; scheduling resources corresponding to the transmission resources of each AMP IoT transmission; scheduling resources corresponding to the multiplexing method used in each AMP IoT transmission; scheduling resources corresponding to the multiple access method used in each AMP IoT transmission; scheduling resources corresponding to the waveform used in each AMP IoT transmission; and scheduling resources corresponding to the encoding method used in each AMP IoT transmission.

60. The apparatus according to claim 54, 58, or 59, characterized in that, The scheduling resources include one or more of the following: time domain resources, frequency domain resources, spatial domain resources, and code domain resources.

61. A communication device, characterized in that, The communication device includes: a processor; a transceiver connected to the processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to load and execute the executable instructions to implement the scheduling method for an AMP IoT device as described in any one of claims 1 to 13.

62. A communication device, characterized in that, The communication device includes: a receiver; the communication device is configured to perform the scheduling method for AMP IoT devices as described in any one of claims 14 to 30.

63. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores at least one program, which is loaded and executed by a processor to implement the scheduling method for an AMP IoT device as described in any one of claims 1 to 13, or the scheduling method for an AMP IoT device as described in any one of claims 14 to 30.

64. A computer program product or computer program, characterized in that, The computer program product or the computer program includes computer instructions stored in a computer-readable storage medium, a processor retrieves the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions to implement the scheduling method for an AMP IoT device as claimed in any one of claims 1 to 13, or the scheduling method for an AMP IoT device as claimed in any one of claims 14 to 30.

65. A chip, characterized in that, The chip includes a programmable logic circuit and / or at least a program, and the chip is used to implement the scheduling method of the AMP IoT device as described in any one of claims 1 to 13, or the scheduling method of the AMP IoT device as described in any one of claims 14 to 30, based on the programmable logic circuit and / or the at least a program.

Images