Communication method and apparatus, terminal, and network side device

Abstract

The present application relates to the technical field of wireless communications, and discloses a communication method and apparatus, a terminal and a network side device. The communication method of embodiments of the present application comprises: a terminal receives first configuration information sent by a network side device, wherein the first configuration information is used for configuring a first target gap for executing an AIoT operation, and comprises a gap parameter of the first target gap; and the terminal communicates with an AIoT device within the first target gap.

Description

Communication methods, devices, terminals and network-side equipment

[0001] Cross-reference to related applications

[0002] This application claims priority to Chinese Patent Application No. 202411177637.8, filed on August 26, 2024, entitled "Communication Method, Apparatus, Terminal and Network Side Device", the entire contents of which are incorporated herein by reference. Technical Field

[0003] This application belongs to the field of wireless communication technology, specifically relating to a communication method, apparatus, terminal, and network-side equipment. Background Technology

[0004] In related technologies, within the Ambient Powered Internet of Things (AIoT), a possible connection is shown in Figure 1. An AIoT base station (BS) and a large base station coexist, with indoor user equipment (UE) acting as an intermediary node. The BS controls the UE via air interface signaling. The UE sends Reader to Device (R2D) messages to the AIoT device. The AIoT device performs backscattering, i.e., transmits Device to Reader (D2R) messages to the UE. The UE then forwards the AIoT device's response to the BS via the air interface.

[0005] In the connection topology shown in Figure 1, the UE needs to communicate with the network through the 3GPP Air Interface (Uu interface or Uu) and also with AIoT devices through the AIoT radio interface. This means that the UE's operations in the AIoT radio interface and the 3GPP Air Interface may be parallel. When radio frequency multiplexing exists between the AIoT radio interface and the 3GPP Air Interface, conflicts may occur between the UE's operations in the AIoT radio interface and the 3GPP air interface, potentially leading to communication failure. Summary of the Invention

[0006] This application provides a communication method, apparatus, terminal, and network-side device that can resolve the conflict between the operation of the UE in the AIoT wireless interface and the operation in the 3GPP air interface.

[0007] In a first aspect, a communication method is provided, comprising: a terminal receiving first configuration information sent by a network-side device, wherein the first configuration information is used to configure a first target gap for performing AIoT operations, and the first configuration information includes gap parameters of the first target gap; the terminal communicating with an AIoT device within the first target gap.

[0008] In a second aspect, a communication method is provided, comprising: a network-side device sending first configuration information to a terminal, wherein the first configuration information instructs the terminal to communicate with an AIoT device within a first target gap, wherein the first configuration information is used to configure the first target gap for performing AIoT operations, and the first configuration information includes gap parameters of the first target gap.

[0009] Thirdly, a communication device is provided, comprising: a receiving module for receiving first configuration information sent by a network-side device, wherein the first configuration information is used to configure a first target gap for performing AIoT operations, and the first configuration information includes gap parameters of the first target gap; and a processing module for communicating with an AIoT device within the first target gap.

[0010] Fourthly, a communication device is provided, comprising: a transmitting module, configured to transmit first configuration information to a terminal, wherein the first configuration information instructs the terminal to communicate with an AIoT device within a first target gap, wherein the first configuration information is configured to configure the first target gap for performing AIoT operations, and the first configuration information includes gap parameters of the first target gap.

[0011] Fifthly, a communication device is provided, the device being configured to perform the steps of the method described in the first aspect, or to implement the steps of the method described in the second aspect.

[0012] In a sixth aspect, a terminal is provided, the terminal including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as described in the first aspect.

[0013] In a seventh aspect, a terminal is provided, including a processor and a communication interface, wherein the processor is configured to perform the steps of the method described in the first aspect, and the communication interface is configured to be coupled to the processor.

[0014] Eighthly, a network-side device is provided, the network-side device including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as described in the first aspect.

[0015] In a ninth aspect, a network-side device is provided, including a processor and a communication interface, wherein the processor is configured to perform the steps of the method described in the second aspect, and the communication interface is configured to be coupled to the processor.

[0016] In a tenth aspect, a readable storage medium is provided, on which a program or instructions are stored, which, when executed by a processor, implement the steps of the method described in the first aspect, or implement the steps of the method described in the second aspect.

[0017] Eleventhly, a communication system is provided, comprising: a terminal and a network-side device, wherein the terminal can be used to perform the steps of the method as described in the first aspect, and the network-side device can be used to perform the steps of the method as described in the second aspect.

[0018] In a twelfth aspect, a chip is provided, the chip including a processor and a communication interface coupled to the processor, the processor being configured to run programs or instructions to implement the method as described in the first aspect, or to implement the method as described in the second aspect.

[0019] In a thirteenth aspect, a computer program / program product is provided, which is stored in a storage medium and is executed by at least one processor to implement the method as described in the first aspect, or to implement the method as described in the second aspect.

[0020] In this embodiment, the terminal receives first configuration information sent by the network-side device. The first configuration information is used to configure a first target gap for performing AIoT operations. The first configuration information includes gap parameters of the first target gap. The terminal communicates with the AIoT device within the first target gap, thereby avoiding conflicts between the AIoT operations performed by the UE and the operations in the 3GPP air interface. Attached Figure Description

[0021] Figure 1 shows a block diagram of a wireless communication system that can be applied to an embodiment of this application;

[0022] Figure 2 shows a schematic diagram of an AIoT system topology;

[0023] Figure 3a shows a schematic diagram of an AIoT system deployment;

[0024] Figure 3b shows another schematic diagram of AIoT system deployment;

[0025] Figure 3c shows another schematic diagram of AIoT system deployment;

[0026] Figure 3d shows another schematic diagram of AIoT system deployment;

[0027] Figure 3e shows another schematic diagram of AIoT system deployment;

[0028] Figure 3f shows another schematic diagram of AIoT system deployment;

[0029] Figure 3g shows another schematic diagram of AIoT system deployment;

[0030] Figure 3h shows another schematic diagram of AIoT system deployment;

[0031] Figure 4a shows a schematic diagram of an RFID system;

[0032] Figure 4b shows a flowchart of querying and accessing a single tag in an RFID system;

[0033] Figure 4c shows a schematic diagram of commonly used control commands in RFID;

[0034] Figure 5 shows a flowchart of a communication method provided in an embodiment of this application;

[0035] Figure 6 shows another flowchart of the communication method provided in an embodiment of this application;

[0036] Figure 7 shows a flowchart of a communication method according to Embodiment 1 of this application;

[0037] Figure 8 shows a flowchart of a communication method according to Embodiment 2 of this application;

[0038] Figure 9 shows a schematic diagram of a communication device provided in an embodiment of this application;

[0039] Figure 10 shows another structural schematic diagram of the communication device provided in an embodiment of this application;

[0040] Figure 11 shows a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0041] Figure 12 shows a schematic diagram of the hardware structure of a terminal provided in an embodiment of this application;

[0042] Figure 13 shows a schematic diagram of the hardware structure of a network-side device provided in an embodiment of this application. Detailed Implementation

[0043] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.

[0044] The terms "first," "second," etc., used in this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same class, not limited in number; for example, the first object can be one or more. Furthermore, "or" in this application indicates at least one of the connected objects. For example, the scope of protection for "A or B" covers at least three scenarios: Scenario 1: including A but not B; Scenario 2: including B but not A; Scenario 3: including both A and B. In addition, the terms "A and / or B," "at least one of A and B," and "at least one of A or B" also cover at least the above three scenarios. The character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0045] The term "instruction" in this application can be either a direct instruction (or explicit instruction) or an indirect instruction (or implicit instruction). A direct instruction can be understood as one in which the sender explicitly informs the receiver of specific information, the operation to be performed, or the requested result, etc., in the instruction sent. An indirect instruction can be understood as one in which the receiver determines the corresponding information based on the instruction sent by the sender, or makes a judgment and determines the operation to be performed or the requested result, etc., based on the judgment result.

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

[0047] Figure 1 shows a block diagram of a wireless communication system applicable to an embodiment of this application. The wireless communication system includes a terminal 11, a network-side device 12, and an AIoT device 13. The terminal 11 can be a mobile phone, tablet computer, laptop computer, notebook computer, personal digital assistant (PDA), handheld computer, netbook, ultra-mobile personal computer (UMPC), mobile internet device (MID), augmented reality (AR), virtual reality (VR) device, robot, wearable device, flight vehicle, vehicle user equipment (VUE), shipboard equipment, pedestrian user equipment (PUE), smart home devices (home appliances with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), game consoles, personal computers (PCs), ATMs, or self-service machines, etc. Wearable devices include: smartwatches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart chains, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among these, in-vehicle devices can also be referred to as in-vehicle terminals, in-vehicle controllers, in-vehicle modules, in-vehicle components, in-vehicle chips, or in-vehicle units, etc. It should be noted that the specific type of terminal 11 is not limited in this application embodiment. Network-side equipment 12 may include access network equipment or core network equipment, wherein access network equipment may also be referred to as Radio Access Network (RAN) equipment, radio access network function, or radio access network unit. Access network equipment may include base stations, Wireless Local Area Network (WLAN) access points (AS), or Wireless Fidelity (WiFi) nodes, etc.The term "base station" can be referred to as Node B (NB), Evolved Node B (eNB), Next Generation Node B (gNB), New Radio Node B (NR Node B), Access Point, Relay Base Station (RBS), Serving Base Station (SBS), Base Transceiver Station (BTS), Radio Base Station, Radio Transceiver, Basic Service Set (BSS), Extended Service Set (ESS), Home Node B (HNB), Home Evolved Node B, Transmit / Receive Point (TRP), or any other suitable term in the relevant field, as long as the same technical effect is achieved. The term "base station" is not limited to any specific technical terminology. It should be noted that this application embodiment only uses a base station in an NR system as an example for description and does not limit the specific type of base station.

[0048] AIoT device 13 features ultra-low complexity and ultra-low power consumption. It is a device used to implement IoT services. Specifically, AIoT device 13 can be powered through energy harvesting; it may not have a battery or may have limited energy storage capacity (e.g., using a capacitor). This type of device has low overall power consumption, including low-power signal reception and low-power signal transmission. Due to its low overall power consumption, the energy for communication can be derived from the environment, such as wind power, kinetic energy, heat energy, or radio frequency (RF) signals. It can also be referred to as an Ambient IoT or Passive IoT device, or a response device.

[0049] AIoT devices 13 can be classified based on energy source, energy storage capability, and whether they are passive or active transmitters, encompassing various device types:

[0050] 1) Passive device (e.g., device 1). It does not have independent signal generation / amplification, i.e., backscatter transmission.

[0051] 2) Semi-passive devices (such as device 2a) also belong to the broad category of passive devices. They have energy storage but do not generate independent signals; they transmit signals via backscattering. The stored energy can be used to amplify the reflected signal.

[0052] 3) Active devices (such as device 2b) have energy storage and independent signal generation, i.e., they contain active radio frequency components for transmission.

[0053] The main data / service types of AIoT fall into the following two categories:

[0054] Device-terminated (DT) data: DT data is the data stream transmitted to the AIoT device;

[0055] Device-originating (DO) data: DO data is data originating from AIoT devices. DO data can be further categorized as follows:

[0056] DO-A (Device-originated–autonomous) refers to data that AIoT devices autonomously initiate to transmit. For example, they connect to a large number of various sensors that collect and proactively report information about the environment, devices, and organisms when necessary.

[0057] DO-DTT (Device-originated–device-terminated triggered) refers to data transmission initiated by AIoT devices through reader / writer devices such as base stations. Examples include asset identification, status reporting, and tracking. These are all DL-triggered reports, where the Reader collects data from the tag by triggering an inventory process. Since the data is generated / initiated within the AIoT device, this service should be considered as a DO service initiated by the tag through control commands on the Reader side.

[0058] In addition to the connection topology shown in Figure 1, Ambient IoT can also adopt the connection topology shown in Figure 2 (for ease of distinction, the connection topology shown in Figure 2 can be called connection topology, and the connection topology of Figure 1 can be called connection topology 2), that is, AIoT BS and small base stations coexist. The BS sends R2D messages to the AIoT device, and the AIoT device performs backscattering, that is, D2R message transmission to the BS.

[0059] Due to issues such as self-interference, the base station (BS), the user terminal (UE), and the assisting node or intermediate node can each be a separate base station (BS) or UE. For example, multiple readers can each perform either receiving or transmitting functions, thus supporting transmit-receive separation. Therefore, several deployment methods as shown in Table 1 can be considered.

[0060] Table 1.

[0061] In related technologies, for information transmission between the reader and the tag in Radio Frequency Identification (RFID), in inventory mode, as shown in Figure 4a, after the reader sends a query command, the tag responds by generating a 16-bit random number. The reader then sends this sequence to the tag via an ACK command, and the tag sends the relevant data to the reader.

[0062] Figure 4b illustrates the process of querying and accessing a single tag. As shown in Figure 4b, querying and accessing a single tag mainly includes the following steps:

[0063] Step 1: The reader sends a query, query adjustment, or query request;

[0064] Step 2, there are two possible results for the tag: 1) Slot = 0: Tag responds to RN16; 2) Slot is less than or greater than 0: No response.

[0065] Step 3, the reader confirms the tagging by sending an ACK with the same RN16;

[0066] Step 4, the tag has two possible results: 1) Valid RN16: the tag responds to {PC / XPC, EPC}; 2) Invalid RN16: no response;

[0067] Step 5: The reader sends a registration RN containing the same RN16;

[0068] Step 6, the tag has two possible results: 1) Valid RN16: the tag responds to {handle}; 2) Invalid RN16: no response.

[0069] Step 7, the reader accesses the tag. Each access command uses `handle` as a parameter.

[0070] Step 8, Tag Authentication Handle. If the handle is incorrect, you can respond according to the tag response command method in the relevant technology.

[0071] It should be noted that, for the above description, 1) CRC-16 is not shown in the transmission; 2) please refer to the command / response table for command details.

[0072] Figure 4c shows commonly used control commands in RFID, and their details are described in Table 2.

[0073] Table 2.

[0074] In related technologies, gaps primarily include measurement gaps. In Radio Resource Management (RRM) measurements, for inter-frequency measurements and inter-RAT (Inter-Radio Access Technology) measurements, because inter-frequency and inter-RAT serve different frequencies, it's impossible to simultaneously complete serving cell signal transmission and reception and inter-frequency measurements using the same RF chain. Therefore, when the terminal's RF chain is limited, a gap needs to be introduced for measurement. When measuring other cells within the gap, the inability to complete serving cell transmission and reception will reduce throughput.

[0075] In related technologies, a terminal can only be configured with one measurement gap pattern. Two types of measurement gaps are supported: per-UE and per-FR gap.

[0076] 1) In NR, the per-UE gap is applied to FR1 (E-UTRA and NR) and FR2 (NR) frequencies. Only one gap pattern can be configured per-UE.

[0077] 2) There are two independent per-FR gap patterns: FR1 gap and FR2 gap. Each FR can only be configured with one gap pattern.

[0078] In topology 2 shown in Figure 1, the UE Reader needs to communicate with the network via the 3GPP air interface and with AIoT devices via the AIoT radio interface. This means that the UE's operations in the AIoT radio interface and the 3GPP air interface may be parallel. However, when radio frequency multiplexing exists between the AIoT radio interface and the 3GPP air interface, the UE's operations in these two interfaces may not be able to be executed in parallel. To address this issue, this application provides a solution for performing AIoT operations based on a gap mechanism.

[0079] The communication scheme provided in this application will be described in detail below with reference to the accompanying drawings, through some embodiments and application scenarios.

[0080] Figure 5 illustrates a flowchart of a communication method for reporting channel state information according to an embodiment of this application. This method 500 can be executed by a terminal. In other words, the method can be executed by software or hardware installed on the terminal. As shown in Figure 5, the method may include the following steps.

[0081] S510, the terminal receives first configuration information sent by the network-side device, wherein the first configuration information is used to configure a first target gap for performing AIoT operations.

[0082] In this embodiment of the application, the first configuration information includes gap parameters of the first target gap (Gap). Through these gap parameters, the terminal can determine the first target gap.

[0083] The terminal in this application embodiment is a UE that supports Ambient IoT, namely, an Ambient IoT capable UE, which can also be called a UE Reader.

[0084] In the embodiments of this application, the first target gap is a gap used to perform AIoT operations, and in order to distinguish it from gaps for other purposes, it can also be called an AIoT gap.

[0085] In this embodiment of the application, the network-side device (e.g., a base station) configures a first target gap for the terminal, instructing the terminal to perform AIoT operations within the first target gap and communicate with the network-side device outside the first target gap.

[0086] In some embodiments, the gap parameters included in the first configuration information may include: gap type information, used to indicate the type of the configured first target gap, the gap type information including at least one of the following:

[0087] 1) Frequency band information associated with the first target gap; the frequency band information can indicate the frequency band associated with the first target gap.

[0088] Optionally, the frequency band information may include at least one of the following:

[0089] --First indication information, used to indicate that the first target gap is configured for at least one of the following: per frequency band, i.e., AIoT gap per Band; per carrier component (CC), i.e., AIoT gap per CC; per bandwidth part (BWP), i.e., AIoT gap per BWP; per frequency, i.e., AIoT gap per Frequency.

[0090] In some implementations, the first indication information may also indicate that the first target gap is configured for at least one of the following: all frequencies, a predetermined frequency range. For example, AIoT gap per UE: indicates that the first target gap applies to all frequencies (e.g., FR1 and FR2), or AIoT gap per FRx, e.g., FR1 and FR2; or indicates that the first target gap applies to a specific frequency range (indicates that it applies to FRx only).

[0091] --Second indication information, used to indicate at least one of the following associated with the first target gap: frequency band, carrier unit, BWP, frequency.

[0092] Through the above optional implementation methods, the terminal performs AIoT operations at a specific frequency. The AIoT gap can be applied only to that specific frequency, frequency band, carrier unit, or BWP, without affecting the transmission and reception of other frequencies on the air interface.

[0093] 2) Indication information for the first gap type, used to indicate that the configured first target gap is applied to the uplink of the Uu interface;

[0094] Where the first configuration information includes an indication of a first gap type, the first target gap is configured as the first gap type, and the terminal does not perform air interface (Uu) uplink transmission during the first target gap. The first gap type can also be referred to as a UL gap. Optionally, the UE can continue to perform Uu downlink reception. For example, in the absence of downlink conflicts, the UE simultaneously receives Uu downlink and AIoT D2R information. It can be understood that the terminal, acting as a UE Reader, sends AIoT R2D (Reader to Device) signals, occupying Uu uplink time. Furthermore, the time interval between D2R signal reception and R2D signal transmission is short, and a single first target gap can be used to perform both R2D signal transmission and D2R signal reception. Therefore, the UE performs AIoT operations during the first target gap, without affecting the terminal's downlink reception.

[0095] 3) Indication information of the second gap type, used to indicate that the configured first target gap is applied to the downlink of the Uu interface;

[0096] Where the first configuration information includes an indication of a second gap type, the first target gap is configured as the second gap type, and the terminal does not perform Uu downlink reception operation during the first target gap. The second gap type can also be called a DL gap. It can be understood that the terminal, acting as a UE Reader, receives AIoT D2R signals (Device to Reader), occupying the air interface Uu downlink time; therefore, the terminal performs AIoT operation during the first target gap.

[0097] 4) Indication information of the third gap type, used to indicate that the configured first target gap is applied to the uplink and downlink of the Uu interface.

[0098] Where the first configuration information includes an indication of a third gap type, the first target gap is configured as the third gap type, meaning the terminal does not perform uplink transmission and downlink reception of Uu during the first target gap. It is understood that for backscatter-based AIoT communication, the terminal's reception of D2R signals generally follows the transmission of R2D signals, and the time interval between D2R signal reception and R2D signal transmission is short. Therefore, a first target gap can be used to perform both R2D signal transmission and D2R signal reception. During this first target gap, the terminal may not perform uplink transmission and downlink reception of Uu.

[0099] It should be noted that the above gap type information can be combined. For example, multiple first target gaps of both first and second gap types can be configured simultaneously. The first target gap of the first gap type is used for transmitting AIoT R2D (Reader to Device) signals. The first target gap of the second gap type is used for receiving D2R signals. Another example is UL Gap per Band, which indicates the first gap type gap on a specific band, ensuring that the first target gap only affects the uplink and reduces its impact on other bands.

[0100] In some embodiments, the gap parameters included in the first configuration information may include a retention indication, which indicates that the UE is allowed to use a "keep solution" for collided AIoT gaps. That is, when the first target gap (AIoT Gap) conflicts with other AIoT gaps or other gaps, the terminal may not discard the conflicting gaps, but instead retain these gaps to perform AIoT operations or other operations, thereby maximizing the efficiency of gap utilization.

[0101] In some embodiments, the first configuration information includes at least one of the following gap parameters:

[0102] 1) Period, used to indicate the repetition period of the first target gap; for example, gap repetition period in (ms).

[0103] 2) Length (Gap Length), used to indicate the length of the first target gap; for example, in milliseconds (ms), or in seconds such as 1s, 10s, etc.

[0104] 3) Start time, used to indicate the start time of the first target gap;

[0105] 4) GapOffset, used to indicate the gap offset of the first target gap, wherein the first target gap adopts a gap pattern with a measurement gap repetition period (MGRP), that is, Value gap Offset is the gap offset of the gap pattern with MGRP;

[0106] 5) Priority, used to indicate the priority of the first target gap; the terminal can handle conflicts between the first target gap (AIoT Gap) and other AIoT gaps or other gaps according to the priority. For example, in the event of a gap conflict, the lower priority gap is discarded and the higher priority gap is retained.

[0107] 6) Gap ID, used to identify the first target gap;

[0108] 7) The third indication information is used to indicate whether the first target gap is a Network Controlled Small Gap (NCSG). Therefore, the third indication information can also be called NCSG indication information.

[0109] 8) The fourth indication information (Interrupt) is used to indicate whether the first target gap is interrupted. If the fourth indication information indicates that the first target gap is interrupted, it can be understood that there is no gap, but there will be an interruption, that is, No gap with Interrupt.

[0110] In some embodiments, considering the characteristics of AIoT operations performed by the terminal, the inventory process includes paging and access procedures for at least one AIoT device. Considering that the total inventory time may be too long, when performing access procedures sequentially for multiple AIoT devices, the terminal can use a periodic first target gap to intermittently perform the inventory, thereby balancing Uu operations and AIoT operations. Considering that the time for data transmission and reception for a specific AIoT device is not necessarily fixed, a non-periodic gap or a one-time gap can be used. Therefore, the first target gap can be at least one of the following gaps:

[0111] - A first gap, which is a periodic gap. In one implementation, the first gap can be used for processes such as AIoT paging, random access, or inventorying one or more AIoT devices. The first gap includes parameters such as period, length, and offset.

[0112] - A second gap, which is either a non-periodic gap or a one-time gap. One implementation method can be used for data transmission and reception of AIoT devices. The second gap includes parameters such as length and start time.

[0113] The first or second gap mentioned above includes the parameters of the AIoT gap provided by the first configuration information.

[0114] It should be noted that the first target gap can be a UL gap, a DL gap, an NCSG, or an interrupt. That is, the terminal may require a UL gap or a DL gap to perform AIoT operations, or it may require an NCSG, or it may not require a gap but have an interrupt. It is understood that the above situations depend on the UE's radio frequency sharing situation.

[0115] In some implementations, the terminal may also receive second configuration information configured by a network-side device, such as a base station, which is used to configure AIoT radio resources. These AIoT radio resources are used by the terminal and AIoT devices to perform AIoT operations.

[0116] In some implementations, the first configuration information and the second configuration information can be configured simultaneously. For example, the first configuration information and the second radio resource information can be configured simultaneously via Radio Resource Control (RRC) reconfiguration. It is understood that when a terminal is selected as a UE reader, at the start of AIoT service, the base station can configure the terminal with both the first and second configuration information. The base station may be aware of conflicts between AIoT radio resources and air interface resources, and thus configures the first configuration information for the UE simultaneously, thereby resolving the conflict between the terminal's air interface operation and AIoT operation.

[0117] In some implementations, the first configuration information and the second configuration information can also be configured separately. For example, the network-side device can configure the second configuration information for the terminal at the start of the AIoT service, and then configure the first configuration information for the terminal before the AIoT wireless resources and air interface resources may conflict, so as to avoid conflicts between the terminal's air interface operation and AIoT operation.

[0118] S512, the terminal communicates with the AIoT device within the first target gap.

[0119] In this embodiment, the terminal can determine the first target gap based on the first configuration information, and thus can perform AIoT operations within the first target gap, such as triggering the AIoT device to initiate data transmission.

[0120] In some embodiments, after S510, the method may further include: the terminal receiving third configuration information sent by the network-side device, wherein the third configuration information is used for one of the following: adding a second target gap for AIoT operation, modifying the configured first target gap, or releasing the configured first target gap. After the network-side device sends the first configuration information for the first target gap, the network-side device may also send third configuration information for configuring the addition of a second target gap for AIoT operation. For example, after receiving the first configuration information, due to changes in the terminal's air-to-air operation, new conflicts may arise between AIoT wireless resources and air interface resources. To address these conflicts, the network-side device can configure a second target gap for the terminal to resolve the conflicts. Alternatively, after the network-side device sends the first configuration information for the first target gap, the network-side device may send third configuration information for modifying the configured first target gap. For example, after receiving the first configuration information, due to changes in the type of AIoT operation or changes in the terminal's air-to-air operation, the conflicts between AIoT wireless resources and air interface resources may change. To adapt to these changes, the network-side device may send third configuration information for modifying the configured first target gap. Alternatively, after the network-side device sends the first configuration information for the first target gap, the network-side device may send the third configuration information for releasing the configured first target gap. For example, after receiving the first configuration information, if there is no conflict between AIoT wireless resources and air interface resources for some reason, the network-side device may send the third configuration information for releasing the configured first target gap in order to improve transmission efficiency.

[0121] The technical solution provided by the embodiments of this application enables the terminal in the connected state to both maintain the connected state for data transmission and reception and to perform AIoT services during the first target gap, thereby avoiding the conflict between air interface operation and AIoT operation.

[0122] In some embodiments, prior to S510, the method may further include: the terminal sending a first request message to the network-side device, wherein the first request message is used to request a third target gap for AIoT operation, and the first request message includes gap parameters of the third target gap. Alternatively, the first request message is used to indicate the terminal's target gap preference and related target gap configuration; that is, the first request message indicates that the terminal's target gap preference is the third target gap and the gap parameters of the third target gap. In these embodiments, the terminal can determine, based on AIoT resource allocation and UE capabilities, whether a gap, NCSG, or interruption is required when performing AIoT operation. In such cases, the terminal can send the first request message to the network-side device, and the network-side device (base station) configures the first target gap according to the first request message sent by the terminal.

[0123] In some embodiments, the first request message carries the following gap parameters: gap type information, used to indicate the type of the third target gap, the gap type information including at least one of the following:

[0124] 1) Frequency band information associated with the third target gap;

[0125] Optionally, this frequency band information can allow you to enable at least one of the following:

[0126] --The fifth indication information is used to indicate that the third target gap is configured for at least one of the following: per frequency band, i.e., AIoT gap per Band; per carrier component (CC), i.e., AIoT gap per CC; per bandwidth part (BWP), i.e., AIoT gap per BWP; per frequency, i.e., AIoT gap per Frequency.

[0127] In some implementations, the fifth indication information may also indicate that the third target gap is configured for at least one of the following: all frequencies, a predetermined frequency range. For example, AIoT gap per UE: indicates that the second target gap applies to all frequencies (e.g., FR1 and FR2), or AIoT gap per FRx, e.g., FR1 and FR2; or indicates that the third target gap applies to a specific frequency range (indicates that it applies to FRx only).

[0128] --Sixth indication information, used to indicate at least one of the following associated with the third target gap: frequency band, carrier unit, BWP, frequency.

[0129] 2) Indication information of the first gap type, used to indicate that the third target gap is applied to the uplink of the Uu interface;

[0130] For example, if uplink transmission on the Uu interface is not performed during the UL Gap, but downlink reception on the Uu interface is required, the terminal can carry indication information of the first gap type in the first request message, indicating that the terminal prefers the target gap of the first gap type.

[0131] 3) Indication information of the second gap type, used to indicate that the third target gap is applied to the downlink of Uu;

[0132] For example, when a terminal receives an AIoT D2R (Device to Reader) signal as a UE Reader, it only needs to occupy the downlink time of the air interface Uu. Therefore, the terminal can carry indication information of the second gap type in the first request message, indicating that the terminal prefers the target gap of the second gap type.

[0133] 4) Indication information for the third gap type, used to indicate that the third target gap is applied to the uplink and downlink of Uu.

[0134] For AIoT communication based on backscattering, the terminal's reception of D2R signals generally follows the transmission of R2D signals. The time interval between D2R signal reception and R2D signal transmission is short. The terminal may need to use a gap to perform R2D signal transmission and D2R signal reception. Therefore, the terminal can carry indication information of the third gap type in the first request message, indicating that the terminal prefers the target gap of the third gap type.

[0135] In some embodiments, the first request message includes the following gap parameter: a retention preference, which instructs the terminal to retain all conflicting third target gaps, or in other words, instructs the terminal to retain all conflicting requested third target gaps. That is, when target gaps conflict, the terminal prefers not to discard the conflicting target gaps, but rather to retain these gaps to perform AIoT operations or other operations, thereby maximizing the efficiency of gap utilization.

[0136] In some embodiments, the first request message may include at least one of the following gap parameters:

[0137] Period, used to indicate the repetition period of the requested third target gap;

[0138] Length, used to indicate the length of the requested third target gap; for example, in milliseconds (ms), or in seconds such as 1s, 10s, etc.

[0139] Start time, used to indicate the start time of the requested third target gap; that is, the start time of the target gap preferred by the terminal.

[0140] Offset, used to indicate the gap offset of the requested third target gap in MGRP gap mode;

[0141] Priority is used to indicate the priority of the requested third target gap; that is, the priority of the target gap preferred by the terminal.

[0142] Gap identifier, used to identify the requested third target gap;

[0143] The seventh indication information is used to indicate whether the requested third target gap is a small gap controlled by the network;

[0144] The eighth instruction is used to indicate whether the requested third target gap is interrupted.

[0145] In some embodiments, the interval parameters included in the first configuration information are at least partially the same as the gap parameters included in the first request message. For example, the period, length, and offset included in the first request message are the same as the period, length, and offset in the first configuration information; or, the seventh indication information included in the first request message is the same as the third indication information included in the first configuration information, for example, both indicating a small gap for network control; or the eighth indication information included in the first request message is the same as the fourth indication information in the first configuration information, for example, both indicating an interruption. That is, the network-side device can configure the first target gap according to the third target interval requested by the terminal to try to meet the needs of the terminal.

[0146] In some embodiments, for the example of the terminal receiving third configuration information sent by the network-side device, before the terminal receives the third configuration information sent by the network-side device, the method may further include: the terminal sending a second request message to the network-side device, wherein the second request message is used for one of the following: requesting the network-side device to modify the configured first target gap, requesting the network-side device to release the configured first target gap, modifying the requested third target gap (also referred to as target gap preference), or releasing the requested third target gap (i.e., releasing the requested target gap preference). In these embodiments, when the terminal has already received the first configuration information, the terminal may request the network-side device to modify the configured first target gap, or request the network-side device to release the configured first target gap, and then receive the third configuration information sent by the network-side device. When the terminal has already sent the first request message, the terminal may request the network-side device to modify the target gap preference requested by the terminal or release the target gap preference requested by the terminal, to adapt to the needs of the current scenario.

[0147] In practical applications, the UE reader may be deployed separately, that is, separately as a UE Reader that transmits R2D signals or a Reader that receives D2R signals. In some embodiments, the terminal is a terminal that transmits reader-to-AIoT device (R2D) signals. In this case, optionally, the gap type information included in the first configuration information or the first request message may include at least one of the following:

[0148] 1) Frequency band information associated with the gap; for example, the frequency band information associated with the first target gap or the frequency band information associated with the third target gap mentioned above.

[0149] 2) Indication information for the first gap type, used to indicate that the gap is applied to the uplink of the Uu interface. That is, when the terminal is a UE Reader responsible for transmitting R2D signals, the terminal can request a UL Gap, or the network-side equipment can configure a UL Gap for the terminal.

[0150] In some embodiments, the terminal is a terminal that receives AIoT device-to-reader (D2R) signals. In this case, optionally, the gap type information included in the first configuration information or the first request message may include at least one of the following:

[0151] 1) Frequency band information related to gaps;

[0152] 2) Second gap type indication information, used to indicate that the gap is applied to the downlink of the Uu interface. When the terminal is a UE Reader responsible for receiving D2R signals, the terminal can request a DL Gap, or the network-side device can configure a DL Gap for the terminal.

[0153] In some implementations, the gap parameter in the first configuration information or the first request message may include: a reader type, used to indicate the type of the terminal, wherein the type of the terminal includes one of the following:

[0154] A transmitter-reader, the transmitter-reader being used to transmit R2D signals;

[0155] A receiver / reader, wherein the receiver / reader is used to receive D2R signals;

[0156] A transmitter and receiver reader for transmitting R2D signals and receiving D2R signals.

[0157] The reader type mentioned above can indicate the type of the terminal, thereby assigning a target gap that matches the type of the terminal.

[0158] In some embodiments, after the terminal receives the first configuration information sent by the network-side device, the method further includes at least one of the following:

[0159] 1) During the first target gap, if the terminal has already sent an R2D signal to the AIoT device and is listening for a D2R signal, the terminal postpones the random access procedure, for example, by postponing the transmission of the random access preamble. In other words, if the terminal has already sent an R2D signal to the AIoT device and is listening for a D2R signal during the first target gap, and if the terminal needs to initiate a random access procedure at that time, it can postpone the random access procedure, for example, by initiating it after the first target gap ends, thereby avoiding conflicts between the random access procedure and AIoT operations.

[0160] 2) The terminal determines the next available Physical Random Access Channel (PRACH) opportunity based on the first target gap; that is, when determining the next available PRACH opportunity, the terminal considers the first target gap, for example, avoiding PRACH opportunities that overlap with the first target gap as the next available PRACH.

[0161] 3) During the first target gap, if the terminal sends a random access preamble, the terminal receives a random access response. That is, if the terminal has already initiated a random access procedure, the terminal continues to execute the random access procedure during the first target gap to avoid interruption of the random access procedure.

[0162] The conflict between the first target gap and the random access procedure can be resolved through the above embodiments.

[0163] Based on the same technical concept, this application also provides another communication method.

[0164] It should be noted that the following embodiments only describe the operation of the network-side device. For other matters not covered, please refer to the relevant description of method 500 above.

[0165] Figure 6 shows a schematic flowchart of a communication method provided in an embodiment of this application. This method 600 can be executed by a network-side device. In other words, the method can be executed by software or hardware installed on the network-side device. As shown in Figure 6, the method mainly includes the following steps.

[0166] S610, the network-side device sends first configuration information to the terminal, instructing the terminal to communicate with the AIoT device within the first target gap through the first configuration information, wherein the first configuration information is used to configure the first target gap for performing AIoT operations, and the first configuration information includes gap parameters of the first target gap.

[0167] The first configuration information is the same as the first configuration information in method 500. For details, please refer to the relevant description in method 500, which will not be repeated here.

[0168] In this embodiment, the network-side device sends first configuration information of the first target gap to the terminal, thereby configuring the first target gap for the terminal to perform AIoT operations. The terminal can communicate with AIoT devices within the first target gap and communicate with the network-side device outside the first target gap, thereby avoiding conflicts between the AIoT wireless interface and the 3GPP air interface.

[0169] In some embodiments, the network-side device may further send second configuration information to the terminal, wherein the second configuration is used to configure the radio resources for AIoT operation. In some optional embodiments, the network-side device may send the first configuration information and the second configuration information to the terminal simultaneously, that is, simultaneously configure the radio resources for AIoT operation and the first target gap for performing the AIoT operation. In other embodiments, the network-side device may also send the first configuration information and the second configuration information to the terminal separately, that is, separately configure the radio resources for AIoT operation and the first target gap for performing the AIoT operation.

[0170] In some embodiments, after S610, the method may further include: the network-side device sending third configuration information to the terminal, wherein the third configuration information is used for one of the following: adding a second target gap for AIoT operation, modifying the configured first target gap, or releasing the configured first target gap. The third configuration information is the same as the third configuration information in method 500, and can be found in the relevant description in method 500, which will not be repeated here.

[0171] In some embodiments, prior to S610, the method may further include: the network-side device receiving a first request message sent by the terminal, wherein the first request message is used to request a third target gap for AIoT operation, and the first request message includes gap parameters of the third target gap. That is, before configuring the first target gap for the terminal, the network-side device receives the first request message sent by the terminal, which indicates the terminal's preferred third target gap and related gap parameters. Based on the request in the first request message, the network-side device can then configure the first target gap for the terminal.

[0172] The first request message is the same as the first request message in method 500, and the details can be found in the relevant description in method 500, which will not be repeated here.

[0173] In some embodiments, the gap parameter in the first configuration information sent by the network-side device is at least partially the same as the gap parameter in the first request message. That is, the network-side device can configure the first target gap based on the terminal's request as much as possible.

[0174] In some embodiments, when the network-side device sends third configuration information to the terminal, before the network-side device sends the third configuration information to the terminal, the method may further include: the network-side device receiving a second request message sent by the terminal, wherein the second request message is used for one of the following: requesting the network-side device to modify the configured first target gap, requesting the network-side device to release the configured first target gap, modifying the requested third target gap, or releasing the requested third target gap. That is, the network-side device can send third configuration information based on the terminal's request to meet the terminal's needs. The second request message is the same as the second request message in method 500; for details, please refer to the relevant description in method 500, which will not be repeated here.

[0175] The technical solutions provided in the embodiments of this application are described below through specific examples.

[0176] Example 1

[0177] In this embodiment, the network-side device (e.g., a base station) configures an AIoT Gap for the UE. The AIoT Gap includes Gap types suitable for AIoT operation.

[0178] Figure 7 shows a signaling flowchart in an embodiment of this application. As shown in Figure 7, the communication method provided in this embodiment mainly includes the following steps.

[0179] S701, the UE receives first AIoT Gap configuration information sent by a network-side device (such as a base station). The first AIoT Gap configuration information is used to configure the AIoT Gap.

[0180] The AIoT Gap is used to perform AIoT operations. The first AIoT Gap configuration information includes at least one of the following AIoT Gap parameters:

[0181] (1) Gap type information.

[0182] Optionally, the AIoT gap includes at least one of the following gap types:

[0183] 1) Per UE; Indicates gap configuration that applies to all frequencies (e.g., FR1 and FR2).

[0184] 2) Per FRx, for example, FR1 or FR2; indicates the gap configuration that applies to FRx only.

[0185] 3) Per Band, per Carrier Component (CC), per BWP, or Per Frequency; indicates that the gap is applied to a specific frequency band, carrier component (CC), bandwidth portion (BWP), or frequency. It can be understood that if the UE performs AIoT operations at a specific frequency, the AIoT gap can be applied to that specific frequency, or frequency band, carrier component (CC), or bandwidth portion (BWP). This ensures that transmission and reception on other frequencies over the air interface are not affected.

[0186] Accordingly, the Gap type information can also indicate the Band, Carrier Unit, BWP, or Frequency associated with the AIoT Gap.

[0187] 4) First Gap Type Indication Information. This indicates that the AIoT Gap is applied to the Uu uplink (UL), therefore, this AIoT Gap can also be called the UL Gap. During this UL Gap, the terminal does not perform uplink transmission operations on the Uu interface. Optionally, the UE can continue to perform Uu downlink reception. For example, in the absence of downlink conflicts, the UE simultaneously receives Uu downlink and AIoT D2R information. It can be understood that the UE, acting as a UE Reader, sends AIoT R2D signals (Reader to Device), occupying Uu uplink time. Furthermore, the time interval between D2R signal reception and R2D signal transmission is short, and a UL Gap can be used to perform both R2D signal transmission and D2R signal reception. Therefore, the UE performs AIoT operations during the UL Gap, thus not affecting downlink reception.

[0188] 5) The second type of Gap indication information indicates that the AIoT Gap is applied to the Uu interface downlink (DL). Therefore, this AIoT Gap can also be called the DL Gap. During this DL Gap, the terminal does not perform downlink reception operations on the Uu interface. It can be understood that the UE, as a UE Reader, receives AIoT D2R signals (Device to Reader), occupying the downlink time of the air interface Uu interface. Therefore, the UE performs AIoT operations during the DL Gap.

[0189] 6) The third type of Gap indication information indicates that the AIoT Gap is applied to Uu uplink and downlink, meaning that the terminal does not perform uplink transmission and downlink reception on the Uu interface during this AIoT Gap. It can be understood that for backscatter-based AIoT communication, the UE's reception of D2R signals generally follows the transmission of R2D signals, with a short time interval between D2R signal reception and R2D signal transmission. Therefore, an AIoT Gap can be used to perform both R2D signal transmission and D2R signal reception. During this AIoT Gap, the UE can refrain from performing Uu uplink transmission and downlink reception.

[0190] (2) Period; e.g., gap repetition period in (ms)).

[0191] (3) Length. For example, in milliseconds (ms) or in seconds (1s, 10s, etc.).

[0192] (4) Start time; that is, the start time of the AIoT Gap.

[0193] (5) Offset GapOffset; Value gap Offset is the gap offset of the gap pattern with MGRP.

[0194] (6) Retention Instruction. This indicates that the UE is allowed to use a retention solution for collided AIoT gaps. That is, when an AIoT gap conflicts with another AIoT gap or other gaps, the UE can retain these gaps to perform AIoT operations or other operations instead of discarding the conflicting gaps, thereby maximizing the efficiency of gap utilization.

[0195] (7) Priority (Indicates the priority of this gap): The UE can handle conflicts between AIoT gaps and other gaps based on priority. In the event of an AIoT gap conflict, the lower priority gap is discarded, and the higher priority gap is retained.

[0196] (8) Gap identifier (Gap ID).

[0197] (9) NCSG indication information, used to indicate whether NCSG is enabled.

[0198] (10) Interrupt message, used to indicate whether an interrupt has occurred. If an interrupt is indicated, there is no gap, but an interrupt will occur.

[0199] It's worth noting that the above gap types can be combined. For example, DL gap and UL gap can be configured simultaneously. The UL gap is used for transmitting AIoT R2D (Reader to Device) signals, while the DL gap is used for receiving D2R signals. Another example is UL gap per band, which indicates a UL gap on a specific band, ensuring that the AIoT gap only affects the uplink and reduces its impact on other bands.

[0200] Furthermore, considering the characteristics of UE performing AIoT operations, the inventory process includes paging and access procedures for at least one AIoT device. Given that the total inventory time may be too long, when sequentially performing access procedures for multiple AIoT devices, the UE can use periodic gaps to perform inventory intermittently, thus balancing Uu operations and AIoT operations. Considering that the time for data transmission and reception for a specific AIoT device is not necessarily fixed, non-periodic gaps or one-time gaps can be used. The AIoT gap can be at least one of the following:

[0201] 1) The first gap is a periodic gap. In one implementation, it can be used in processes such as AIoT paging and random access, or in a round of inventory, or in the inventory of one or more AIoT devices. The first gap includes parameters such as period, length, and offset.

[0202] 2) A second gap, which is either a non-periodic gap or a one-time gap. In one implementation, this can be used for data transmission and reception of AIoT devices. The second gap includes parameters such as length and start time.

[0203] The first or second gap mentioned above includes the parameters of the AIoT gap provided by the AIoT gap configuration information.

[0204] It's worth noting that the AIoT gap can be a UL / DL gap, an NCSG, or an interrupt. That is, a UE may require a UL / DL gap to perform AIoT operations, require an NCSG, or not require a gap but may experience an interrupt. Understandably, these scenarios depend on the UE's shared radio frequency configuration.

[0205] Optionally, the UE can also receive AIoT radio resource configuration information configured by network-side devices such as base stations. The AIoT radio resources are used by the Reader and AIoT devices to perform AIoT operations.

[0206] Optionally, the AIoT Gap configuration information and the AIoT radio resources can be configured simultaneously or separately. For example, the AIoT Gap configuration information and the AIoT radio resources can be configured simultaneously via RRC Reconfiguration. It can be understood that the UE is selected as the UE reader. Upon the start of the AIoT service, the base station configures the AIoT Gap configuration information and the AIoT radio resources for the UE. The base station may be aware of conflicts between the AIoT radio resources and air interface resources, and therefore configures the AIoT Gap configuration information for the UE simultaneously, thereby resolving the conflict between the UE's air interface operations and AIoT operations.

[0207] S702: The UE performs AIoT operations during the configured AIoT Gap, communicating with AIoT devices, such as paging, random access, or data transmission.

[0208] S703: The UE receives second AIoT Gap configuration information sent by a network-side device (such as a base station). The AIoT Gap configuration information is used to add AIoT gaps for AIoT operation, or to modify or release configured AIoT gaps.

[0209] This embodiment enables connected UEs to both maintain data transmission and reception in the connected state and execute AIoT services during AIoT gaps, thereby avoiding conflicts between air interface operations and AIoT operations.

[0210] Example 2

[0211] In this embodiment, the UE Reader may need a gap, NCSG, or interruption when performing AIoT operations, depending on the AIoT resource allocation and UE capabilities. The UE can send AIoT Gap request information to the network-side device, and the network-side device (base station) configures the AIoT Gap according to the UE's AIoT Gap request information.

[0212] Figure 8 shows a flowchart of the communication method in this embodiment. As shown in Figure 8, the method mainly includes the following steps.

[0213] S801, the UE sends an AIoT Gap request message to a network-side device (such as a base station). The AIoT Gap request message is used to request the network-side device to configure an AIoT Gap for the UE. The AIoT Gap is used to perform AIoT operations.

[0214] The AIoT Gap request information includes at least one of the following AIoT Gap parameters (i.e., the target gap parameter preferred by the UE):

[0215] (1) Gap type information.

[0216] The optional AIoT gap includes at least one of the following gap types:

[0217] 1) Per UE; Indicates gap configuration that applies to all frequencies (e.g., FR1 and FR2).

[0218] 2) Per FRx, for example, FR1 or FR2; indicates the gap configuration that applies to FRx only.

[0219] 3) Per Band, Per Carrier Component (CC), Per BWP, Per Freq: These indicate where the AIoT gap is applied to a specific frequency band, carrier component (CC), bandwidth portion (BWP), or frequency. It can be understood that if the UE prefers to perform AIoT operations on a specific frequency, then the AIoT gap can be applied to that specific frequency, or frequency band, carrier component (CC), or bandwidth portion (BWP). Benefit: It does not affect the transmission and reception of other frequencies on the air interface.

[0220] Accordingly, the Gap type information may also include the Band, carrier unit, BWP, or frequency associated with the requested Gap.

[0221] 4) First Gap Type Indication Information. This indicates the UE's preference for applying the AIoT Gap to the Uu uplink UL. During the UL Gap, the UE does not perform air interface (Uu) uplink transmission. Optionally, the UE can continue to perform Uu downlink reception. For example, in the absence of downlink conflicts, the UE simultaneously receives Uu downlink and AIoT D2R information. It can be understood that the UE, acting as a UE Reader, sends AIoT R2D (Reader to Device) signals, occupying Uu uplink time. Furthermore, the time interval between D2R signal reception and R2D signal transmission is short, and one UL Gap can be used to perform both R2D signal transmission and D2R signal reception. Therefore, the UE prefers to perform AIoT operations during the UL Gap to avoid affecting downlink reception.

[0222] 5) Second Gap Type Indication Information. This indicates the UE's preference for applying the AIoT Gap to the Uu downlink DL. Specifically, the UE does not perform Uu downlink reception during the DL Gap. It can be understood that the UE, acting as a UE Reader, receives AIoT D2R signals (Device to Reader), occupying the air interface Uu downlink time; therefore, the UE performs AIoT operations during the DL Gap.

[0223] 6) The third type of Gap indication information indicates the UE's preference for applying an AIoT Gap to Uu uplink and downlink, meaning the UE prefers not to perform Uu uplink transmission and downlink reception during the Gap period. It can be understood that for backscatter-based AIoT communication, the UE's reception of D2R signals generally follows the transmission of R2D signals, with a short time interval between D2R signal reception and R2D signal transmission. Therefore, the UE can request a Gap to perform R2D signal transmission and D2R signal reception. During this Gap, the UE can choose not to perform Uu uplink transmission and downlink reception.

[0224] (2) Period; such as gap repetition period in (ms), which is the period of the target gap preferred by the UE.

[0225] (3) Gap Length. For example, in milliseconds (ms) or seconds (1s, 10s, etc.). That is, the length of the target gap preferred by the UE.

[0226] (4) Start time; that is, the start time of the AIoT gap preferred by the UE.

[0227] (5) GapOffset; Value gap Offset is the gap offset of the gap pattern with MGRP, that is, the offset of the AIoT gap preferred by the UE.

[0228] (6) Retention Instruction. Instructs the UE to use the retention scheme for conflicting AIoT gaps. That is, when an AIoT gap conflicts with another AIoT gap or other gaps, the UE can retain the conflicting gaps to perform AIoT operations or other operations instead of discarding them, thereby maximizing the efficiency of gap utilization.

[0229] (7) Priority (Indicates the priority of this gap), that is, the priority of the AIoT Gap preferred by the UE. The UE can handle conflicts between AIoT Gaps and other gaps based on priority. In the event of a gap conflict, the lower priority gap is discarded, and the higher priority gap is retained.

[0230] (8) Gap identifier (Gap ID).

[0231] (9) NCSG indication information, used to indicate whether NCSG (Network Controlled Small Gap) is preferred by the UE.

[0232] (10) Interrupt information, used to indicate whether there is an interruption. That is, there is no gap, but there will be an interruption, i.e., whether the UE prefers the target gap to be interrupted.

[0233] Optionally, before sending the AIoT Gap request information to the network device (such as a base station), the UE can obtain the AIoT radio resource configuration. For example, the UE receives the AIoT radio resource configuration configured by the base station, such as an RRC Reconfiguration message. Alternatively, the UE receives the AIoT radio resource configuration configured by the core network.

[0234] S802, the UE receives AIoT Gap configuration information sent by a network-side device (such as a base station). The AIoT Gap configuration information is used to configure the AIoT Gap. The AIoT Gap is used to perform AIoT operations. (Same as Embodiment 1)

[0235] The AIoT Gap configuration information contains AIoT gap parameters that are at least partially identical to those in the AIoT Gap request information. For example, the AIoT Gap Pattern configured by the network-side device for the UE is the same as the AIoT Gap Pattern requested by the UE. This ensures that the AIoT gap configured by the network-side device guarantees that the UE is capable of supporting it and meets the UE's needs.

[0236] In step S803, the UE sends a second AIoT Gap request message to a network-side device (such as a base station). The second AIoT Gap request message is used to request the network to modify or release the configured AIoT Gap.

[0237] Example 3

[0238] In this embodiment, for UE readers in a separate Reader deployment, the AIoT Gap request or configuration will be different for UE Readers that transmit R2D signals or Readers that receive D2R signals.

[0239] For example, in Figure 3e, two UE Readers, R1 and R2, communicate with the AIoT device. Wherein:

[0240] R1 is the UE Reader that transmits the R2D signal.

[0241] R2 is the UE Reader that receives D2R signals.

[0242] The communication method in this embodiment mainly includes the following steps:

[0243] Step 1: The UE sends an AIoT Gap request message to the network-side device (such as a base station). The AIoT Gap request message is used to request the network to configure an AIoT Gap for the UE. The AIoT Gap is used to perform AIoT operations.

[0244] The AIoT Gap request information includes at least one of the following AIoT Gap parameters (same as the parameter content of the AIoT Gap configuration information):

[0245] (1) Gap type information.

[0246] Optionally, the AIoT gap includes at least one of the following gap types:

[0247] 1) Per UE; Indicates gap configuration that applies to all frequencies (e.g., FR1 and FR2).

[0248] 2) Per FRx, for example, FR1 or FR2; indicates the gap configuration that applies to FRx only.

[0249] 3) Per Band, per Carrier Component (CC), per BWP, Per Frequency (Freq): These indicate that the gap is applied to a specific frequency band, carrier component (CC), bandwidth portion (BWP), or frequency. It can be understood that if the UE performs AIoT operations at a specific frequency, the AIoT gap requested by the UE can be applied to that specific frequency, or frequency band, carrier component (CC), or bandwidth portion (BWP), so as not to affect the transmission and reception of other frequencies on the air interface.

[0250] 4) First Gap type indication information, indicating that the requested AIoT Gap is applied to Uu uplink UL. During the UL Gap, no air interface (Uu) uplink transmission is performed. Optionally, the UE can continue to perform Uu downlink reception. For example, in the absence of downlink conflicts, the UE simultaneously receives Uu downlink and AIoT D2R information. It can be understood that the UE, acting as a UE Reader, sends AIoT R2D (Reader to Device) signals, occupying Uu uplink time. Furthermore, the time interval between D2R signal reception and R2D signal transmission is short, and one UL Gap can be used to perform both R2D signal transmission and D2R signal reception. Therefore, the UE performs AIoT operations during the UL Gap without affecting the UE's downlink reception.

[0251] When the UE is a UE Reader responsible for transmitting R2D signals, the UE requests a UL Gap.

[0252] 5) The second type of Gap indication information indicates that the requested AIoT Gap is applied to the Uu downlink DL. During the DL Gap, the UE does not perform Uu downlink reception operations. It can be understood that the UE, acting as a UE Reader, receives AIoT D2R signals (Device to Reader), occupying the air interface Uu downlink time; therefore, the UE performs AIoT operations during the DL Gap.

[0253] When the UE is a UE Reader responsible for receiving D2R signals, the UE requests a DL Gap.

[0254] 6) The third type of Gap indication information indicates that the requested AIoT Gap applies to both Uu uplink and downlink, meaning that the UE does not perform Uu uplink transmission and downlink reception during the Gap period. It can be understood that for backscatter-based AIoT communication, the UE's reception of D2R signals generally follows the transmission of R2D signals, with a short time interval between D2R signal reception and R2D signal transmission. Therefore, a single Gap can be used to perform both R2D signal transmission and D2R signal reception. During this Gap, the UE can refrain from performing Uu uplink transmission and downlink reception.

[0255] 7) Reader type, used to indicate the UE Reader type, including at least one of the following:

[0256] Transmission, that is, the UE is the UE Reader responsible for transmitting R2D signals.

[0257] Receiving, that is, the UE is the UE Reader responsible for receiving D2R signals.

[0258] Transmission and reception. That is, the UE is the UE Reader responsible for transmitting R2D signals and receiving D2R signals.

[0259] The Reader type is used to indicate the type of AIoT Gap requested by the UE, such as indicating whether the AIoT Gap is applied to Uu uplink, Uu downlink, or both Uu uplink and downlink.

[0260] (2) Period; e.g., gap repetition period in (ms)).

[0261] (3) Length. For example, in milliseconds (ms) or in seconds (1s, 10s, etc.).

[0262] (4) Start time; that is, the start time of the gap.

[0263] (5) Offset GapOffset; Value gap Offset is the gap offset of the gap pattern with MGRP.

[0264] (6) Retention Instruction. Instructs the UE to use the retention scheme for conflicting AIoT gaps. That is, when an AIoT gap conflicts with another AIoT gap or other gaps, the UE can retain the conflicting gaps to perform AIoT operations or other operations instead of discarding them, thereby maximizing the efficiency of gap utilization.

[0265] (7) Priority (Indicates the priority of this gap): The UE can handle conflicts between AIoT Gap and other gaps based on priority. In the event of a gap conflict, the lower priority gap is discarded, and the higher priority gap is retained.

[0266] (8) Gap identifier (Gap ID).

[0267] (9) NCSG indication information, used to indicate whether the request is NCSG (Network Controlled Small Gap).

[0268] (10) Interrupt message, used to indicate whether the request is an interrupt. If it is, there is no gap, but there will be an interrupt.

[0269] Step 2: The UE receives AIoT Gap configuration information sent by a network-side device (such as a base station). This AIoT Gap configuration information is used to configure the AIoT Gap, which is used to perform AIoT operations.

[0270] Similarly, in the AIoT Gap configuration information,

[0271] When the UE is a UE Reader responsible for transmitting R2D signals, the UE is configured with a UL Gap.

[0272] When the UE is a UE Reader responsible for receiving D2R signals, the UE is configured with a DL Gap.

[0273] The AIoT Gap configuration information contains the same AIoT Gap as the AIoT Gap request information. That is, the Gap Pattern configured by the network device for the UE is the same as the Gap Pattern requested by the UE. Benefit: The network-configured AIoT gap ensures that the UE is supported by the capability and that its needs are met.

[0274] Step 3: The UE sends a second AIoT Gap request message to the network-side device (such as a base station). This second AIoT Gap request message is used to request the network-side device to modify or release the configured AIoT Gap.

[0275] The technical solution provided in this application embodiment allows the network-side device (e.g., a base station) to configure an AIoT Gap for the UE. The UE performs AIoT operations within the AIoT Gap, avoiding conflicts between the AIoT wireless interface and operations in the 3GPP air interface. The UE Reader can request an AIoT Gap from the network based on AIoT resource allocation and UE capabilities. The network-side device (e.g., a base station) configures the AIoT Gap based on the UE's AIoT Gap request information, effectively negotiating the Gap requirements for executing AIoT tasks. In a separate Reader deployment, suitable AIoT Gaps, such as UL gap and DL gap, are configured for either the UE Reader transmitting R2D signals or the UE Reader receiving D2R signals.

[0276] This application provides a communication device. As an example, the communication device may be a communication equipment or a component within a communication equipment, such as a chip. The communication equipment may be a terminal, a network-side device, or a server, etc. Exemplarily, the terminal may include, but is not limited to, the type of terminal 11 listed above, and the network-side device may include, but is not limited to, the type of network-side device 12 listed above. This application does not impose specific limitations.

[0277] The communication device includes a receiving module, a transmitting module, and a processing module. These modules can be implemented in software or hardware. When implemented in hardware, the processing module can be implemented by a processor. For example, the processor can include general-purpose processors, special-purpose processors, such as a Central Processing Unit (CPU), microprocessor, Digital Signal Processor (DSP), Artificial Intelligence (AI) processor, Graphics Processing Unit (GPU), Application Specific Integrated Circuit (ASIC), Network Processor (NP), Field Programmable Gate Array (FPGA), or other programmable logic devices, gate circuits, transistors, discrete hardware components, etc. The receiving and transmitting modules can be implemented by a communication interface, which can include one or more of the following: transceiver, pins, circuits, bus, radio frequency unit, etc.

[0278] Specifically, referring to Figure 9, when the communication device is a terminal or a component in a terminal, the communication device 900 includes a receiving module 901, used to receive first configuration information sent by a network-side device, wherein the first configuration information is used to configure a first target gap for performing AIoT operations, and the first configuration information includes gap parameters of the first target gap; and a processing module 902, used to communicate with the AIoT device within the first target gap.

[0279] In one possible implementation, the first configuration information includes the following gap parameters:

[0280] Gap type information, used to indicate the type of the configured first target gap, the gap type information includes at least one of the following:

[0281] The frequency band information associated with the first target gap;

[0282] The first gap type indication information is used to indicate that the configured first target gap is applied to the uplink of the Uu interface;

[0283] The second gap type indication information is used to indicate that the configured first target gap is applied to the downlink of the Uu interface;

[0284] The third gap type indication information is used to indicate that the configured first target gap is applied to the uplink and downlink of the Uu interface.

[0285] In one possible implementation, the frequency band information includes at least one of the following:

[0286] First indication information is used to indicate that the first target gap is configured for at least one of the following: each frequency band, each carrier unit, each bandwidth portion (BWP), and each frequency;

[0287] The second indication information is used to indicate at least one of the following associated with the first target gap: frequency band, carrier unit, BWP, frequency.

[0288] In one possible implementation, the first indication information is further used to indicate that the first target gap is configured for at least one of the following: all frequencies, a predetermined frequency range.

[0289] In one possible implementation, the first configuration information includes the following gap parameters:

[0290] A reservation instruction is used to indicate that the terminal is permitted to use a reservation scheme for the conflicting first target gap.

[0291] In one possible implementation, the first configuration information includes at least one of the following gap parameters:

[0292] Period, used to indicate the repetition period of the first target gap;

[0293] Length, used to indicate the length of the first target gap;

[0294] Start time, used to indicate the start time of the first target gap;

[0295] Offset, used to indicate the gap offset of the first target gap, wherein the first target gap adopts a gap pattern with a measured gap repetition period (MGRP);

[0296] Priority, used to indicate the priority of the first target gap;

[0297] Gap marker, used to identify the first target gap;

[0298] The third indication information is used to indicate whether the first target gap is a small gap controlled by the network;

[0299] The fourth indication information is used to indicate whether the first target gap is interrupted.

[0300] In one possible implementation, the first target gap includes at least one of the following:

[0301] The first gap is a periodic gap;

[0302] The second gap is a non-periodic gap or a one-time gap.

[0303] In one possible implementation, the receiving module 901 receives first configuration information sent by the network-side device, including:

[0304] The device receives second configuration information and first configuration information sent by a network-side device, wherein the second configuration information is used to configure the wireless resources for AIoT operation.

[0305] In one possible implementation, the receiving module 901 is further configured to receive third configuration information sent by the network-side device, wherein the third configuration information is used for one of the following: adding a second target gap for AIoT operation, modifying the configured first target gap, or releasing the configured first target gap.

[0306] In one possible implementation, as shown in Figure 9, it further includes: a sending module 903, configured to send a first request message to the network-side device, wherein the first request message is used to request a third target gap for AIoT operation, and the first request message includes gap parameters of the third target gap.

[0307] In one possible implementation, the first request message carries the following gap parameter: gap type information, indicating the type of the third target gap, the gap type information including at least one of the following:

[0308] The frequency band information associated with the third target gap;

[0309] The first gap type indication information is used to indicate that the third target gap is applied to the uplink of the air interface Uu;

[0310] The second gap type indication information is used to indicate that the third target gap is applied to the downlink of Uu;

[0311] The third gap type indication information is used to indicate that the third target gap is applied to the uplink and downlink of Uu.

[0312] In one possible implementation, the frequency band information includes at least one of the following:

[0313] The fifth indication information is used to indicate that the requested third target gap is configured for at least one of the following: per frequency band, per carrier unit, per bandwidth portion (BWP), and per frequency;

[0314] The sixth indication information is used to indicate at least one of the following associated with the requested third target gap: frequency band, carrier unit, BWP, frequency.

[0315] In one possible implementation, the fifth indication information is also used to indicate that the requested third target gap is configured for at least one of the following: all frequencies, a predetermined frequency range.

[0316] In one possible implementation, the first request message includes the following gap parameter:

[0317] Preservation preference, used to instruct the terminal to retain the preference for all conflicting third target gaps.

[0318] In one possible implementation, the first request message includes at least one of the following gap parameters:

[0319] Period, used to indicate the repetition period of the requested third target gap;

[0320] Length, used to indicate the length of the requested third target gap;

[0321] Start time, used to indicate the start time of the requested third target gap;

[0322] Offset, used to indicate the gap offset of the requested third target gap in MGRP gap mode;

[0323] Priority, used to indicate the priority of the requested third target gap;

[0324] Gap identifier, used to identify the requested third target gap;

[0325] The seventh indication information is used to indicate whether the requested third target gap is a small gap controlled by the network;

[0326] The eighth instruction is used to indicate whether the requested third target gap is interrupted.

[0327] In one possible implementation, the interval parameter included in the first configuration information is at least partially the same as the gap parameter included in the first request message.

[0328] In one possible implementation, the system further includes a sending module 903, configured to send a second request message to the network-side device, wherein the second request message is used for one of the following: requesting the network-side device to modify the configured first target gap, requesting the network-side device to release the configured first target gap, modifying the requested third target gap, or releasing the requested third target gap.

[0329] In one possible implementation, the device is a terminal that transmits R2D signals from a reader to an AIoT device.

[0330] In one possible implementation, the gap parameter includes gap type information, which includes at least one of the following:

[0331] Frequency band information associated with gaps;

[0332] The first gap type indication information is used to indicate the gap applied to the uplink of the Uu interface.

[0333] In one possible implementation, the device is a terminal that receives AIoT device-to-reader (D2R) signals.

[0334] In one possible implementation, the gap parameter includes gap type information, which includes at least one of the following:

[0335] Frequency band information associated with gaps;

[0336] The second gap type indication information is used to indicate the gap applied to the downlink of the Uu interface.

[0337] In one possible implementation, the gap parameter includes:

[0338] Reader type, used to indicate the type of the terminal, which includes one of the following:

[0339] A transmitter-reader, the transmitter-reader being used to transmit R2D signals;

[0340] A receiver / reader, wherein the receiver / reader is used to receive D2R signals;

[0341] A transmitter and receiver reader for transmitting R2D signals and receiving D2R signals.

[0342] In one possible implementation, the processing module 902 is also used for at least one of the following:

[0343] Within the first target gap, while R2D signals have already been sent to the AIoT device and D2R signals are being monitored, the random access process is postponed;

[0344] The timing of the next available Physical Random Access Channel (PRACH) is determined based on the first target gap.

[0345] During the first target gap, a random access response is received after a random access preamble has been sent.

[0346] Referring to Figure 10, when the communication device is a network-side device or a component of a network-side device, the communication device 1000 includes a sending module 1001, which is used to send first configuration information to the terminal, and instruct the terminal to communicate with the AIoT device within the first target gap through the first configuration information. The first configuration information is used to configure the first target gap for performing AIoT operations, and the first configuration information includes gap parameters of the first target gap.

[0347] In one possible implementation, the sending module 1001 sends first configuration information to the terminal, including:

[0348] Send the second configuration information and the first configuration information to the terminal, wherein the second configuration information is used to configure the wireless resources for AIoT operation.

[0349] In one possible implementation, the sending module 1001 is further configured to send third configuration information to the terminal, wherein the third configuration information is used for one of the following: adding a second target gap for AIoT operation, modifying the configured first target gap, or releasing the configured first target gap.

[0350] In one possible implementation, as shown in Figure 10, it further includes: a receiving module 1002, configured to receive a first request message sent by the terminal, wherein the first request message is used to request a third target gap for AIoT operation, and the first request message includes a gap parameter of the third target gap.

[0351] In one possible implementation, as shown in FIG10, it further includes: a receiving module 1002, configured to receive a second request message sent by the terminal, wherein the second request message is used for one of the following: requesting the network-side device to modify the configured first target gap, requesting the network-side device to release the configured first target gap, modifying the requested third target gap, or releasing the requested third target gap.

[0352] The communication device provided in this application embodiment can implement the various processes implemented in the method embodiments of Figures 5 to 8 and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0353] As shown in Figure 11, this application embodiment also provides a communication device 1100, including a processor 1101 and a memory 1102. The memory 1102 stores a program or instructions that can run on the processor 1101. For example, when the communication device 1100 is a terminal, the program or instructions executed by the processor 1101 implement the various steps of the above-described communication method 500 embodiment and achieve the same technical effect. When the communication device 1100 is a network-side device, the program or instructions executed by the processor 1101 implement the various steps of the above-described communication method 600 embodiment and achieve the same technical effect. To avoid repetition, further details are omitted here.

[0354] This application also provides a terminal, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the steps in the method embodiment shown in FIG5. This terminal embodiment corresponds to the above-described terminal-side method embodiment, and all implementation processes and methods of the above-described method embodiments can be applied to this terminal embodiment and can achieve the same technical effect. The terminal can be the communication device shown in FIG9. Specifically, FIG11 is a schematic diagram of the hardware structure of a terminal implementing an embodiment of this application.

[0355] The terminal 1100 includes, but is not limited to, at least some of the following components: radio frequency unit 1101, network module 1102, audio output unit 1103, input unit 1104, sensor 1105, display unit 1106, user input unit 1107, interface unit 1108, memory 1109, and processor 1110.

[0356] Those skilled in the art will understand that terminal 1100 may also include a power supply (such as a battery) for powering various components. The power supply can be logically connected to processor 1110 through a power management system, thereby enabling functions such as charging, discharging, and power consumption management through the power management system. The terminal structure shown in Figure 11 does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown, or combine certain components, or have different component arrangements, which will not be elaborated here.

[0357] It should be understood that, in this embodiment, the input unit 1104 may include a graphics processor 11041 and a microphone 11042. The graphics processor 11041 processes image data of still images or videos obtained by an image capture device (such as a camera) in video capture mode or image capture mode. The display unit 1106 may include a display panel 11061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 1107 includes at least one of a touch panel 11071 and other input devices 11072. The touch panel 11071 is also called a touch screen. The touch panel 11071 may include a touch detection device and a touch controller. Other input devices 11072 may include, but are not limited to, physical keyboards, function keys (such as volume control buttons, power buttons, etc.), trackballs, mice, and joysticks, which will not be described in detail here.

[0358] In this embodiment, after receiving downlink data from the network-side device, the radio frequency unit 1101 can transmit it to the processor 1110 for processing; in addition, the radio frequency unit 1101 can send uplink data to the network-side device. Typically, the radio frequency unit 1101 includes, but is not limited to, antennas, amplifiers, transceivers, couplers, low-noise amplifiers, duplexers, etc.

[0359] The memory 1109 can be used to store software programs or instructions and various data. The memory 1109 may primarily include a first storage area for storing programs or instructions and a second storage area for storing data. The first storage area may store the operating system, application programs or instructions required for at least one function (such as sound playback function, image playback function, etc.). Furthermore, the memory 1109 may include volatile memory or non-volatile memory. The non-volatile memory may be read-only memory (ROM), programmable ROM, erasable programmable ROM, electrically erasable programmable ROM, or flash memory. The volatile memory can be random access memory (RA11), static random access memory (SRA11), dynamic random access memory (DRA11), synchronous dynamic random access memory (SDRA11), double data rate synchronous dynamic random access memory (DDRSDRA11), enhanced synchronous dynamic random access memory (ESDRA11), synchronous link dynamic random access memory (SLDRA11), and direct memory bus random access memory (DRRA11). The memory 1109 in this embodiment includes, but is not limited to, these and any other suitable types of memory.

[0360] Processor 1110 may include one or more processing units; optionally, processor 1110 integrates an application processor and a modem processor, wherein the application processor mainly handles operations involving the operating system, user interface, and applications, and the modem processor mainly handles wireless communication signals, such as a baseband processor. It is understood that the aforementioned modem processor may also not be integrated into processor 1110.

[0361] The radio frequency unit 1101 is used for:

[0362] Receive first configuration information sent by a network-side device, wherein the first configuration information is used to configure a first target gap for performing AIoT operations, and the first configuration information includes gap parameters of the first target gap;

[0363] The device receives first configuration information sent by a network-side device, wherein the first configuration information is used to configure a first target gap for performing AIoT operations, and the first configuration information includes gap parameters of the first target gap.

[0364] It is understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant description of method embodiment 500 and achieve the same or corresponding technical effects. To avoid repetition, it will not be described again here.

[0365] This application also provides a network-side device, including a processor and a communication interface. The communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the steps of the method embodiment shown in FIG6. This network-side device embodiment corresponds to the above-described network-side device method embodiment. All implementation processes and methods of the above-described method embodiments can be applied to this network-side device embodiment and can achieve the same technical effect.

[0366] Specifically, this application embodiment also provides a network-side device, which can be the communication device shown in FIG10. As shown in FIG12, the network-side device 1200 includes: an antenna 1201, a radio frequency device 1202, a baseband device 1203, a processor 1204, and a memory 1205. The antenna 1201 is connected to the radio frequency device 1202. In the uplink direction, the radio frequency device 1202 receives information through the antenna 1201 and sends the received information to the baseband device 1203 for processing. In the downlink direction, the baseband device 1203 processes the information to be transmitted and sends it to the radio frequency device 1202, which processes the received information and then transmits it through the antenna 1201.

[0367] The method executed by the network-side device in the above embodiments can be implemented in the baseband device 1203, which includes a baseband processor.

[0368] The baseband device 1203 may include at least one baseband board, on which multiple chips are disposed, as shown in FIG12. One of the chips is, for example, a baseband processor, which is connected to the memory 1205 via a bus interface to call the program in the memory 1205 and execute the network device operation shown in the above method embodiment.

[0369] The network-side device may also include a network interface 1206, such as a Common Public Radio Interface (CPRI).

[0370] Specifically, the network-side device 1200 in this application embodiment further includes: instructions or programs stored in memory 1205 and executable on processor 124. Processor 1204 calls the instructions or programs in memory 1205 to execute the methods executed by each module shown in FIG10 and achieve the same technical effect. To avoid repetition, it will not be described in detail here.

[0371] This application also provides a readable storage medium storing a program or instructions. When the program or instructions are executed by a processor, they implement the various processes of the above-described communication method 500 or 600 embodiments and achieve the same technical effect. To avoid repetition, they will not be described again here.

[0372] The processor mentioned above is the processor in the terminal described in the above embodiments. The readable storage medium includes computer-readable storage media, such as a computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk. In some examples, the readable storage medium may be a non-transient readable storage medium.

[0373] This application embodiment also provides a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run programs or instructions to implement the various processes of the above-described communication method 500 or 600 embodiments and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0374] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0375] This application also provides a computer program / program product, which is stored in a storage medium and executed by at least one processor to implement the various processes of the above-described communication method 500 or 600 embodiments, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0376] This application embodiment also provides a communication system, including: a terminal and a network-side device, wherein the terminal can be used to execute the steps of the communication method 500 as described above, and the network-side device can be used to execute the steps of the communication method 600 as described above.

[0377] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0378] From the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of computer software products plus necessary general-purpose hardware platforms, and of course, they can also be implemented by hardware. The computer software product is stored in a storage medium (such as RO11, RA11, magnetic disk, optical disk, etc.) and includes several instructions to cause the terminal or network-side device to execute the methods described in the various embodiments of this application.

[0379] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other implementations under the guidance of this application without departing from the spirit and scope of the claims. All of these implementations are within the protection scope of this application.

Claims

1. A communication method, comprising: The terminal receives first configuration information sent by the network-side device, wherein the first configuration information is used to configure a first target gap for performing IoT AIoT operations enabled by ambient energy, and the first configuration information includes gap parameters of the first target gap; The terminal communicates with the AIoT device within the first target gap.

2. The method according to claim 1, wherein, The first configuration information includes the following gap parameters: Gap type information, used to indicate the type of the configured first target gap, the gap type information includes at least one of the following: The frequency band information associated with the first target gap; The first gap type indication information is used to indicate that the configured first target gap is applied to the uplink of the Uu interface; The second gap type indication information is used to indicate that the configured first target gap is applied to the downlink of the Uu interface; The third gap type indication information is used to indicate that the configured first target gap is applied to the uplink and downlink of the Uu interface.

3. The method according to claim 2, wherein, The frequency band information includes at least one of the following: First indication information is used to indicate that the first target gap is configured for at least one of the following: each frequency band, each carrier unit, each bandwidth portion (BWP), and each frequency; The second indication information is used to indicate at least one of the following associated with the first target gap: frequency band, carrier unit, BWP, frequency.

4. The method according to claim 3, wherein, The first indication information is also used to indicate that the first target gap is configured for at least one of the following: all frequencies, a predetermined frequency range.

5. The method according to any one of claims 1 to 4, wherein, The first configuration information includes the following gap parameters: A reservation instruction is used to indicate that the terminal is permitted to use a reservation scheme for the conflicting first target gap.

6. The method according to any one of claims 1 to 5, wherein, The first configuration information includes at least one of the following gap parameters: Period, used to indicate the repetition period of the first target gap; Length, used to indicate the length of the first target gap; Start time, used to indicate the start time of the first target gap; Offset, used to indicate the gap offset of the first target gap, wherein the first target gap adopts a gap pattern with a measured gap repetition period (MGRP); Priority, used to indicate the priority of the first target gap; Gap marker, used to identify the first target gap; The third indication information is used to indicate whether the first target gap is a small gap controlled by the network; The fourth indication information is used to indicate whether the first target gap is interrupted.

7. The method according to any one of claims 1 to 6, wherein, The first target gap includes at least one of the following: The first gap is a periodic gap; The second gap is a non-periodic gap or a one-time gap.

8. The method according to any one of claims 1 to 7, wherein, The terminal receives first configuration information sent by the network-side device, including: The terminal receives second configuration information and first configuration information sent by the network-side device, wherein the second configuration information is used to configure the wireless resources for AIoT operation.

9. The method according to any one of claims 1 to 8, wherein, After the terminal receives the first configuration information sent by the network-side device, the method further includes: The terminal receives third configuration information sent by the network-side device, wherein the third configuration information is used for one of the following: adding a second target gap for AIoT operation, modifying the configured first target gap, or releasing the configured first target gap.

10. The method according to any one of claims 1 to 9, wherein, Before the terminal receives the first configuration information sent by the network-side device, the method further includes: The terminal sends a first request message to the network-side device, wherein the first request message is used to request a third target gap for AIoT operation, and the first request message includes the gap parameter of the third target gap.

11. The method according to claim 10, wherein, The first request message carries the following gap parameters: gap type information, used to indicate the type of the third target gap, the gap type information including at least one of the following: The frequency band information associated with the third target gap; The first gap type indication information is used to indicate that the third target gap is applied to the uplink of the Uu interface; The second gap type indication information is used to indicate that the third target gap is applied to the downlink of the Uu interface; The third gap type indication information is used to indicate that the third target gap is applied to the uplink and downlink of the Uu interface.

12. The method according to claim 11, wherein, The frequency band information includes at least one of the following: The fifth indication information is used to indicate that the requested third target gap is configured for at least one of the following: per frequency band, per carrier unit, per bandwidth portion (BWP), and per frequency; The sixth indication information is used to indicate at least one of the following associated with the requested third target gap: frequency band, carrier unit, BWP, frequency.

13. The method according to claim 12, wherein, The fifth indication information is also used to indicate that the requested third target gap is configured for at least one of the following: all frequencies, a predetermined frequency range.

14. The method according to any one of claims 10 to 13, wherein, The first request message includes the following gap parameters: Preservation preference, used to instruct the terminal to retain the preference for all conflicting third target gaps.

15. The method according to any one of claims 10 to 14, wherein, The first request message includes at least one of the following gap parameters: Period, used to indicate the repetition period of the requested third target gap; Length, used to indicate the length of the requested third target gap; Start time, used to indicate the start time of the requested third target gap; Offset, used to indicate the gap offset of the requested third target gap in MGRP gap mode; Priority, used to indicate the priority of the requested third target gap; Gap identifier, used to identify the requested third target gap; The seventh indication information is used to indicate whether the requested third target gap is a small gap controlled by the network; The eighth instruction is used to indicate whether the requested third target gap is interrupted.

16. The method according to any one of claims 10 to 15, wherein, The interval parameters included in the first configuration information are at least partially the same as the gap parameters included in the first request message.

17. The method according to any one of claims 9 to 16, wherein, Before the terminal receives the third configuration information sent by the network-side device, the method further includes: The terminal sends a second request message to the network-side device, wherein the second request message is used for one of the following: requesting the network-side device to modify the configured first target gap, requesting the network-side device to release the configured first target gap, modifying the requested third target gap, or releasing the requested third target gap.

18. The method according to any one of claims 1 to 17, wherein, The terminal is the terminal that transmits the reader / writer to the AIoT device R2D signal.

19. The method according to claim 18, wherein, The gap parameter includes gap type information, which includes at least one of the following: Frequency band information associated with gaps; The first gap type indication information is used to indicate the gap applied to the uplink of the Uu interface.

20. The method according to any one of claims 1 to 17, wherein, The terminal is a terminal that receives AIoT device-to-reader (D2R) signals.

21. The method according to claim 20, wherein, The gap parameter includes gap type information, which includes at least one of the following: Frequency band information associated with gaps; The second gap type indication information is used to indicate the gap applied to the downlink of the Uu interface.

22. The method according to any one of claims 18 to 21, wherein, The gap parameters include: Reader type, used to indicate the type of the terminal, which includes one of the following: A transmitter-reader, the transmitter-reader being used to transmit R2D signals; A receiver / reader, wherein the receiver / reader is used to receive D2R signals; A transmitter and receiver reader for transmitting R2D signals and receiving D2R signals.

23. The method according to any one of claims 1 to 22, wherein, After the terminal receives the first configuration information sent by the network-side device, the method further includes at least one of the following: During the first target gap, while the terminal has already sent an R2D signal to the AIoT device and is listening for a D2R signal, the terminal postpones the random access process. The terminal determines the timing of the next available Physical Random Access Channel (PRACH) based on the first target gap. During the first target gap, if the terminal sends a random access preamble, the terminal receives a random access response.

24. A communication method, comprising: The network-side device sends first configuration information to the terminal, instructing the terminal to communicate with the AIoT device within the first target gap. The first configuration information is used to configure the first target gap for performing AIoT operations, and includes gap parameters of the first target gap.

25. The method according to claim 24, wherein, The first configuration information includes the following gap parameters: Gap type information, used to indicate the type of the configured first target gap, the gap type information includes at least one of the following: The frequency band information associated with the first target gap; The first gap type indication information is used to indicate that the configured first target gap is applied to the uplink of the Uu interface; The second gap type indication information is used to indicate that the configured first target gap is applied to the downlink of the Uu interface; The third gap type indication information is used to indicate that the configured first target gap is applied to the uplink and downlink of the Uu interface.

26. The method according to claim 24 or 25, wherein, The network-side device sends first configuration information to the terminal, including: The network-side device sends second configuration information and first configuration information to the terminal, wherein the second configuration information is used to configure the wireless resources for AIoT operation.

27. The method according to any one of claims 24 to 26, wherein, After the network-side device sends the first configuration information to the terminal, the method further includes: The network-side device sends third configuration information to the terminal, wherein the third configuration information is used for one of the following: adding a second target gap for AIoT operation, modifying the configured first target gap, or releasing the configured first target gap.

28. The method according to any one of claims 24 to 27, wherein, Before the network-side device sends the first configuration information to the terminal, the method further includes: The network-side device receives a first request message sent by the terminal, wherein the first request message is used to request a third target gap for AIoT operation, and the first request message includes the gap parameter of the third target gap.

29. The method according to claim 27 or 28, wherein, Before the network-side device sends the third configuration information to the terminal, the method further includes: The network-side device receives a second request message sent by the terminal, wherein the second request message is used for one of the following: requesting the network-side device to modify the configured first target gap, requesting the network-side device to release the configured first target gap, modifying the requested third target gap, or releasing the requested third target gap.

30. A communication device, comprising: A receiving module is configured to receive first configuration information sent by a network-side device, wherein the first configuration information is used to configure a first target gap for performing AIoT operations, and the first configuration information includes gap parameters of the first target gap; The processing module is used to communicate with the AIoT device within the first target gap.

31. The apparatus according to claim 30, wherein, The receiving module receives first configuration information sent by the network-side device, including: The device receives second configuration information and first configuration information sent by a network-side device, wherein the second configuration information is used to configure the wireless resources for AIoT operation.

32. The apparatus according to claim 30 or 31, wherein, The receiving module is further configured to receive third configuration information sent by the network-side device, wherein the third configuration information is used for one of the following: adding a second target gap for AIoT operation, modifying the configured first target gap, or releasing the configured first target gap.

33. The apparatus according to any one of claims 30 to 32, wherein, Also includes: The sending module is configured to send a first request message to the network-side device, wherein the first request message is used to request a third target gap for AIoT operation, and the first request message includes a gap parameter of the third target gap.

34. The apparatus according to any one of claims 30 to 33, wherein, Also includes: The sending module is configured to send a second request message to the network-side device, wherein the second request message is used for one of the following: requesting the network-side device to modify the configured first target gap, requesting the network-side device to release the configured first target gap, modifying the requested third target gap, or releasing the requested third target gap.

35. The apparatus according to any one of claims 30 to 34, wherein, The processing module is also used for at least one of the following: Within the first target gap, while R2D signals have already been sent to the AIoT device and D2R signals are being monitored, the random access process is postponed; Determine the next available PRACH opportunity based on the first target gap; The receiving module is also configured to receive a random access response during the first target gap, provided that a random access preamble has been sent.

36. A communication device, comprising: The sending module is used to send first configuration information to the terminal, and instruct the terminal to communicate with the AIoT device within the first target gap through the first configuration information. The first configuration information is used to configure the first target gap for performing AIoT operations, and the first configuration information includes gap parameters of the first target gap.

37. The apparatus according to claim 36, wherein, The sending module sends first configuration information to the terminal, including: Send the second configuration information and the first configuration information to the terminal, wherein the second configuration information is used to configure the wireless resources for AIoT operation.

38. The apparatus according to claim 36 or 37, wherein, The sending module is further configured to send third configuration information to the terminal, wherein the third configuration information is used for one of the following: adding a second target gap for AIoT operation, modifying the configured first target gap, or releasing the configured first target gap.

39. The apparatus according to any one of claims 36 to 38, wherein, Also includes: A receiving module is configured to receive a first request message sent by the terminal, wherein the first request message is used to request a third target gap for AIoT operation, and the first request message includes a gap parameter of the third target gap.

40. The apparatus according to claim 38 or 39, wherein, Also includes: The receiving module is configured to receive a second request message sent by the terminal, wherein the second request message is used for one of the following: requesting the network-side device to modify the configured first target gap, requesting the network-side device to release the configured first target gap, modifying the requested third target gap, or releasing the requested third target gap.

41. A terminal comprising a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the communication method as claimed in any one of claims 1 to 23.

42. A network-side device, comprising a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the communication method as claimed in any one of claims 24 to 29.

43. A readable storage medium storing a program or instructions that, when executed by a processor, implement the steps of the communication method as claimed in any one of claims 1 to 23, or implement the steps of the communication method as claimed in any one of claims 24 to 29.

Images