Method executed by device, and device

Abstract

According to the present disclosure, provided are a method executed by means of a device, and a device. The method is characterized by comprising: receiving a reader-to-device (R2D) timing acquisition signal (R-TAS), wherein the R-TAS is composed of a start-indicator part (SIP) and a clock-acquisition part (CAP), the R-TAS is used for indicating the start of a physical R2D channel (PRDCH), and the PRDCH immediately follows the R-TAS; and receiving the PRDCH, wherein a transport block (TB) size carried by the PRDCH is determined to be a value indicated by a higher layer.

Description

Methods performed by the device and the device Technical Field

[0001] This disclosure relates to a method and apparatus performed by a device in a wireless communication system. Background Technology

[0002] In wireless communication systems, different communication nodes (or simply nodes) can exchange information (such as voice or data). Examples of communication nodes can include terminal nodes and network nodes. A terminal node can refer to a mobile terminal, wireless terminal, terminal device, mobile device, mobile station (MS), user equipment (UE), or simply a device. A network node can include a base station, etc.

[0003] Examples of wireless communication systems can include systems standardized by 3GPP (3rd Generation Partnership Project), such as 4G systems or their evolutions based on LTE (Long-Term Evolution) radio access technology (e.g., the corresponding base station could be an eNB), and 5G systems or their evolutions based on NR (New Radio) radio access technology (e.g., the corresponding base station could be a gNB). In recent years, wireless communication technologies, including LTE and NR, have been widely used not only for communication between people (or between devices operated or controlled by people) but also for "machine-type communications" (MTC), which provides network access services to "things" or "machines," and, for example, to form an "Internet of Things" (IoT).

[0004] Wireless communication systems require continuous improvement in one or more aspects, such as improvements in some or all of the following: reliability, capacity, transmission rate, latency, interference immunity, efficiency (e.g., some or all of transmission efficiency, signaling efficiency, and energy efficiency), coverage, cost-effectiveness, and interoperability. Specifically, for example, one or more of the aspects may at least partially include some or all of the following: operation on licensed spectrum, operation on unlicensed spectrum, operation on paired spectrum, operation on unpaired spectrum, operation with shared spectrum channel access, operation without shared spectrum channel access, initial access, multiple access, random access, channel coding, line coding, physical layer channel and signal generation, transmission and reception, transmission and reception based on unicast, multicast, multicast and broadcast, physical layer control information and signaling flow (e.g., including synchronization flow, scheduling mechanism and feedback mechanism), frame structure, timing adjustment, timing relationship, transmission power control, signal measurement, higher-level control information and signaling flow, resource allocation and management, multi-carrier operation (e.g., including carrier aggregation). Aggregation and dual connectivity, multi-antenna transmission and reception, beam-based operation, priority-based operation, multi-point cooperation, relaying operation, mobility management, and in-device coexistence.

[0005] Prior art literature

[0006] Non-patent literature

[0007] Non-Patent Document 1: RP-170379, Revision of SI: Study on New Radio Access Technology, 3GPP TSG RAN Meeting #75

[0008] Non-Patent Document 2: RP-191971, Revised WID: New Radio Access Technology, 3GPP TSG RAN Meeting #85

[0009] Non-Patent Document 3: RP-234058, New SID: Study on solutions for Ambient IoT (Internet of Things) in NR, 3GPP TSG RAN Meeting #102

[0010] Non-patent document 4: RP-240826, Revised SID: Study on solutions for Ambient IoT (Internet of Things) in NR, 3GPP TSG RAN Meeting#103

[0011] Non-Patent Document 5: RP-243326, New Work Item: Solutions for Ambient IoT (Internet of Things) in NR, 3GPP TSG RAN Meeting #106 Summary of the Invention

[0012] To address at least some of the aforementioned problems, this disclosure provides a method and apparatus performed by a device that can at least partially improve the efficiency of a wireless communication system.

[0013] According to this disclosure, a method performed by a device is proposed, characterized by comprising: receiving a device R2D timing acquisition signal R-TAS from a reader, wherein the signal R-TAS consists of a start indicator portion SIP and a clock acquisition portion CAP, the signal R-TAS being used to indicate the start of a physical R2D channel PRDCH, the PRDCH immediately following the signal R-TAS; and receiving the PRDCH, wherein the size of the transport block TB carried by the PRDCH is determined to be a value indicated by a higher layer.

[0014] Furthermore, according to this disclosure, an apparatus is proposed, comprising: a processor; and a memory storing instructions, wherein the instructions, when executed by the processor, perform the methods described above. Attached Figure Description

[0015] The above and other features of this disclosure will become more apparent from the following detailed description taken in conjunction with the accompanying drawings, wherein:

[0016] Figure 1 shows a flowchart corresponding to a method performed by a device according to some embodiments of the present disclosure.

[0017] Figure 2 shows a flowchart corresponding to a method performed by a device according to some embodiments of the present disclosure.

[0018] Figure 3 shows a flowchart corresponding to a method performed by a device according to some embodiments of the present disclosure.

[0019] Figure 4 shows a block diagram of the device involved in this disclosure. Detailed Implementation

[0020] The present disclosure will now be described in detail with reference to the accompanying drawings and specific embodiments. It should be noted that the present disclosure should not be limited to the specific embodiments described below. Furthermore, for the sake of simplicity, detailed descriptions of well-known technologies not directly related to the present disclosure have been omitted to prevent confusion in understanding the present disclosure.

[0021] The following describes several implementations of this disclosure using the 3GPP 5G wireless communication system specification and its subsequent evolutions (e.g., 5G Advanced) as an example application environment. However, it should be noted that this disclosure is not limited to the following implementations, but is applicable to many other wireless communication systems, such as wireless communication systems after 5G, and 4G mobile communication systems before 5G such as LTE, LTE-Advanced, and LTE-Advanced Pro.

[0022] The terminology given in this disclosure may be used in different wireless communication systems, but a unified terminology is used in this disclosure. When applied to a specific system, it can be replaced with the terminology used in the corresponding system.

[0023] In this disclosure, "network node" may refer to a base station, or a core network node (e.g., 5G Core Network; or Evolved Packet Core), or other types of network nodes, wherein a core network node may include at least some or all of the following: AMF (Access and Mobility Management Function), UPF (User Plane Function), MME (Mobility Management Entity), S-GW (Serving Gateway), and AIoTF (A-IoT Function).

[0024] In this disclosure, "base station" can refer to a base station of any communication system, such as a base station including a 3G communication system (e.g., NodeB), a 4G communication system (e.g., eNB), and a 5G communication system (e.g., gNB).

[0025] In this disclosure, "base station" can refer to any form of base station, such as a femto base station, a pico base station, a micro base station, a macro base station, etc.

[0026] In this disclosure, unless otherwise specified, "communication node" may refer to a terminal node.

[0027] In this disclosure, unless otherwise specified, "terminal node" may refer to a device.

[0028] In this disclosure, "device" may refer to a mobile terminal, a wireless terminal, a terminal device, a mobile device, a mobile station (MS), or user equipment (UE).

[0029] In this disclosure, "network node" may refer to a base station, or a core network node (e.g., 5G Core Network; or Evolved Packet Core), or other types of network nodes, wherein the core network node may include at least part of some or all of the AMF (Access and Mobility Management Function), UPF (User Plane Function), MME (Mobility Management Entity), S-GW (Serving Gateway), and AIoTF (A-IoT Function).

[0030] It should be noted that in this disclosure, the two connected by "and", "or", or "and / or" may represent different ways of expressing the same meaning in different application scenarios, and there may be a relationship of inclusion between the two, which do not necessarily refer to completely different content.

[0031] Unless otherwise stated in this disclosure:

[0032] ● Any two of “predefine”, “predetermine”, and “preset” can be interchanged.

[0033] ● “Number” and “index” are interchangeable. For example, the number of an RB (resource block) can be called the index of that RB, and vice versa; also, “numbering an RB as 0” can be expressed as “indexing an RB as 0”.

[0034] ● Elements in a set (or array, list, sequence, etc.) can be assigned indices 0, 1, 2, ..., in the order they appear. For example, the set {t0, t1, ..., t2}... N-1 The elements t0, t1, ..., t in} N-1 These can correspond to indices 0, 1, ..., and N-1, respectively.

[0035] ● An element in a set (or array, list, sequence, etc.) can be represented by its index (e.g., the subscript of the element corresponding to it in the set, array, list, or sequence, etc.). For example, a RE (Resource Element) with index 0 can be called "RE 0".

[0036] ● The index corresponding to an object (e.g., a subcarrier, a time slot, a cyclic shift, etc.) (e.g., the index of the object in a set, an array, a list, or a sequence) can be used as the "identifier" (ID) of the object.

[0037] ● If no quantity is specified when referring to an object, the quantity of the object may be one or more. For example, in "transmit uplink transmission(s) on an uplink channel", the "transmission(s)" may correspond to one transmission or multiple transmissions.

[0038] ● Elements in a time series (or set, array, or list) can appear in chronological order. For example, in a time slot set {t0, t1, ..., t...}, the elements can appear sequentially. N-1 In the}, the time corresponding to time slot t0 is earlier than (or no later than) the time corresponding to time slot t1, the time corresponding to time slot t1 is earlier than (or no later than) the time corresponding to time slot t2, and so on.

[0039] ● "Subcarrier" can refer to a subcarrier in a waveform based on OFDM (Orthogonal Frequency Division Multiplexing).

[0040] ● Δf can be used to represent subcarrier spacing (SCS), for example, the subcarrier spacing determined or configured for a carrier or a BWP (Bandwidth part). For example, Δf = 15 kHz; Δf = 30 kHz; Δf = 60 kHz; Δf = 120 kHz.

[0041] ●μ can be used to represent the SCS configuration corresponding to a given SCS. For example, μ=0 corresponds to Δf=15 kHz, and vice versa; μ=1 corresponds to Δf=30 kHz, and vice versa; μ=2 corresponds to Δf=60 kHz, and vice versa; μ=3 corresponds to Δf=120 kHz, and vice versa. In some cases, Δf can be equal to 15.2. μ kilohertz.

[0042] ●Constant T c It can be defined as: T c =1 / (Δf) max ·N f ), where Δf max =480·10 3 Hertz, N f =4096.

[0043] ●The constant κ can be defined as: κ = T s / T c =64, where T s =1 / (Δf) ref ·N f,ref ), Δf ref =15·10 3 Hz, N f,ref =2048.

[0044] ● This can be used to represent the length of the "useful symbol time" of an OFDM symbol l with SCS configured as μ, i.e., excluding the cyclic prefix (CP). In some aspects, the... The value of can be independent of l; in this case, the value of can be... Recorded as For example, the It can be equal to seconds, wherein, the It can be equal to 2048·κ·2 -μ For example, the aforementioned It can be equal to seconds; for example, the aforementioned It can be equal to Seconds. In some respects, the stated It can be T c As a unit, accordingly, the It can be equal to the stated

[0045] ● This can be used to represent the total duration (i.e., including CP) of OFDM symbol l with SCS configured as μ. For example, the... It can be equal to seconds, wherein, the It can be equal to the duration of the CP of the OFDM symbol l. In some aspects, the... It can be represented as T c Multiples of, correspondingly, the It can be equal to In some respects, the stated The value can be determined at least in part based on the index (i.e., l) of the corresponding OFDM symbol l.

[0046] ● This can be used to represent, for example, the average OFDM symbol duration in a subframe when the SCS is configured as μ. For example, the... It can be equal to Second.

[0047] In some respects, a bit string (or bitmap, or bit sequence) of size (or “length”) of L bits (e.g., denoted as “b0, b1, ..., b...) L-1In the given text, the leftmost bit (b0) corresponds to the most significant bit (MSB), and correspondingly, the rightmost bit (b...) corresponds to the most significant bit (MSB). L-1 ) can correspond to the least significant bit (LSB). In some aspects, in the bit string "b0, b1, ..., b L-1 In the diagram, the leftmost bit (b0) corresponds to the least significant bit, and correspondingly, the rightmost bit (b...) corresponds to the least significant bit. L-1 () can correspond to the most significant bit.

[0048] In some respects, "bit padding" can refer to the operation of adding zero or one "padding bits" to the end of a bit sequence, where the value of each "padding bit" (if any) can be "0", and the bit padding can be called "zero-padding" accordingly; or, the value of each "padding bit" (if any) can be "1", and the bit padding can be called "one-padding".

[0049] In some respects, if the number of padding bits added in a bit stuffing operation is zero, the bit stuffing operation can be called a "type 0 bit stuffing operation"; otherwise, it can be called a "type 1 bit stuffing operation". In some respects, a type 0 bit stuffing operation can be equivalent to not performing any bit stuffing operation.

[0050] In some respects, an "operating band" can refer to an operating band with a duplex mode of FDD (Frequency Division Duplex), or an operating band with a duplex mode of TDD (Time Division Duplex), or an operating band defined in other ways.

[0051] In some respects, the uplink (UL) or downlink (DL) operating frequency band within an FDD operating frequency band can be referred to as an FDD operating sub-band. Specifically, for example, the FDD uplink operating frequency band can be referred to as a UL operating sub-band, and the FDD downlink operating frequency band can be referred to as a DL operating sub-band.

[0052] In some respects, channel coding can be replaced by FEC (Forward Error Correction), and vice versa.

[0053] In some respects, "Layer 1" and "physical layer" are interchangeable.

[0054] In some respects, "Layer 2" may contain zero or one or more sublayers, such as part or all of the MAC (Medium Access Control) layer, RLC (Radio Link Control) layer, PDCP (Packet Data Convergence Protocol) layer, SDAP (Service Data Adaptation Protocol) layer, and RRC (Radio Resource Control) layer.

[0055] In some respects, "higher layer(s)" can refer to one or more protocol layers or sublayers above a reference protocol layer or sublayer within a specific protocol stack (e.g., access stratum protocol stack). For example, if the reference protocol layer or sublayer is a physical layer, then "higher layer" can at least partially include some or all of the MAC layer, RLC layer, PDCP layer, SDAP layer, RRC layer, PC5-RRC layer, PC5-S layer, and NAS (Non-Access-Stratum) layer. In this disclosure, unless otherwise specified, the reference protocol layer or sublayer of a "higher layer" can be a physical layer. Where there is no risk of confusion, "higher layer" can also be referred to as "higher layer".

[0056] In some respects, "higher-layer data" can be data or signaling defined in higher-layer protocols, because from the perspective of the corresponding reference protocol layer or reference protocol sublayer, data or signaling defined in higher-layer protocols all belong to "data".

[0057] In some respects, "lower layer(s)" can refer to one or more protocol layers or sublayers below a reference protocol layer or sublayer within a specific protocol stack. For example, if the reference protocol layer or sublayer is an RRC layer, then "lower layer" can include part or all of the MAC layer and the physical layer; similarly, if the reference protocol layer or sublayer is a MAC layer, then "lower layer" can refer to the physical layer. In this disclosure, unless otherwise specified, the reference protocol layer or sublayer of a "lower layer" can be the MAC layer. Where there is no risk of confusion, "lower layer" can also be referred to as "lower layer".

[0058] In some respects, "signaling" can refer to physical layer control information, such as DCI (Downlink Control Information), UCI (Uplink Control Information), and SCI (Sidelink Control Information).

[0059] In some respects, "signaling" can refer to higher-level control information, such as MAC CE (Control Element) or RRC messages.

[0060] In some respects, a "parameter" can refer to a parameter of a physical layer.

[0061] In some respects, a "parameter" can refer to a higher-level parameter.

[0062] In this disclosure, unless otherwise specified, "parameter" may refer to a higher-level parameter.

[0063] In some respects, a "parameter" can refer to a predefined quantity. For example, the number of subcarriers in each RB can correspond to a predefined parameter.

[0064] In some respects, a "parameter" can refer to a "configured" parameter. For example, a parameter that satisfies one or more of the following conditions can be called a "configured" parameter:

[0065] ● The configuration information corresponding to the parameter (e.g., including the value of the parameter) can be provided by one protocol layer (e.g., RRC layer) in a communication node (e.g., a device) to another protocol layer (e.g., physical layer) in the same communication node.

[0066] ● The configuration information corresponding to the parameter (e.g., the value of the parameter) can be provided by a protocol layer (e.g., RRC layer) of a communication node (e.g., a base station) to the peer protocol layer of one or more other communication nodes (e.g., one or more devices).

[0067] ● The configuration information corresponding to the parameter (e.g., the value of the parameter) can be "pre-configured" in a specific storage location in a communication node (e.g., a device) or in another storage location that the communication node can access.

[0068] In some contexts, "configuration" can be replaced with "configuration or pre-configuration". For example, a configuration parameter can refer to a configuration or pre-configuration parameter. Similarly, configuration information can refer to configuration or pre-configuration information.

[0069] In some respects, parameters(s) used to identify (or characterize) a resource may include at least some or all of the following: one or more time-domain parameters, one or more frequency-domain parameters, one or more code-domain parameters, and one or more spatial-domain parameters. In some respects, parameters used to identify a resource may be referred to as parameters associated with said resource, and vice versa.

[0070] In some respects, "time resources" and "time domain resources" are interchangeable.

[0071] In some respects, "frequency resources" and "frequency domain resources" are interchangeable.

[0072] In some respects, "time-frequency resources" and "time-frequency domain resources" are interchangeable.

[0073] In some respects, the start time of an OFDM symbol (including CP) can refer to the start time of the CP of the OFDM symbol.

[0074] In some respects, the start time of an OFDM symbol (excluding CP) may refer to the start time of the useful symbol portion of the OFDM symbol.

[0075] In some respects, “RB” can refer to “PRB” (Physical Resource Block), or “CRB” (Common Resource Block), or “VRB” (Virtual Resource Block), or “IRB” (Interlaced Resource Block), or RB as defined in other ways.

[0076] In some respects, “carrier-wave frequency” (or “carrier frequency”) can refer to the radio frequency (RF) reference frequency.

[0077] In some respects, "carrier frequency" can be used to identify the location of a radio frequency (RF) channel.

[0078] In some respects, the “carrier frequency” can be identified by an ARFCN (Absolute Radio Frequency Channel Number), for example, the ARFCN can be an NR-ARFCN or an EARFCN (E-UTRAARFCN).

[0079] In some respects, where there is no risk of confusion, “carrier frequency” can be simply referred to as “frequency”.

[0080] In some respects, a cell with a radio frequency reference frequency f0 as its carrier frequency (e.g., a downlink carrier frequency) can be referred to as a "cell on said radio frequency reference frequency f0".

[0081] In some respects, a "transmission" can correspond to a transmission on a physical channel. For example, the physical channel can be a PDCCH (Physical Downlink Control Channel); or, for instance, the physical channel can be a PBCH (Physical Broadcast Channel).

[0082] In some respects, a "transmission" can correspond to the transmission of a physical signal. For example, the physical signal can be a PSS (Primary Synchronization Signal); or, for instance, the physical signal can be an SSS (Secondary Synchronization Signal).

[0083] In some respects, a “transmission” can correspond to the transmission of zero or more physical channels and zero or more physical signals multiplexed in the same resource. For example, an “SS / PBCH block” (or an “SSB”, or an “SS block”) can consist of a PSS, an SSS, and a PBCH multiplexed in the same time slot.

[0084] In some respects, where there is no risk of confusion, the name of a physical channel (or physical signal) used for transmission can be used to indicate the transmission of said physical channel (or physical signal). For example, "PDCCH" can mean "PDCCH transmission".

[0085] In some respects, where there is no risk of confusion, the name of a physical channel (or physical signal) used for reception can be used to indicate the reception of said physical channel (or physical signal). For example, "PDCCH" can mean "PDCCH reception".

[0086] In some respects, a DCI carried in a downlink transmission (e.g., PDCCH) that corresponds to a specific DCI format (e.g., denoted as DCI format X) can be referred to as "a DCI format X". For example, a DCI carried in a PDCCH that corresponds to DCI format 0_0 can be referred to as "a DCI format 0_0".

[0087] In Release 12 (or Rel-12), 3GPP specifications introduced a new UE category, "Category 0," for "Low Complexity UEs" to provide low-cost devices for MTC (Multi-Channel Computing). Compared to UE categories introduced before Rel-12, Category 0 UEs have simplified transmission and reception capabilities. For example, the transport block size (TBS) for user data transmission in Category 0 UEs is limited to no more than 1000 bits; also, the half-duplex FDD operation type B supported by Category 0 UEs has a longer "guard period" than the previous half-duplex FDD operation type A.

[0088] Starting with Rel-13, 3GPP specifications began supporting eMTC (enhanced MTC, also known as "LTE-MTC" or "LTE-M") to further reduce the cost of MTC devices and support wider coverage (e.g., this can manifest as higher coupling loss). The "Category M1" UE introduced in Rel-13 is a type of "BLUE" (bandwidth-reduced low complexity UE) that only supports 6 PRBs (Physical Resource Blocks) of channel bandwidth in both uplink and downlink. Subsequent 3GPP specifications introduced an enhanced UE category for BL UEs, "Category M2," to support larger PDSCH / PUSCH channel bandwidths. BL UEs have their own SIB1 (System Information Block 1), which differs from non-BL UEs.

[0089] 3GPPRel-13 also supports "UEs in Enhanced Coverage" (or "UEs in Coverage Enhancement," or simply "UEs in CE"), which requires enhanced coverage functionality to access a cell. For this purpose, Rel-13 introduces two enhanced coverage modes: CE mode A and CE mode B. For BLUEs, support for CE mode A is mandatory. Within a cell supporting enhanced coverage functionality, different CE levels can correspond to different configurations (e.g., PRACH resource configuration) and / or operations.

[0090] 3GPP Rel-13 also introduced NB-IoT (Narrow Band Internet of Things), which allows network services to be provided via E-UTRA (Evolved Universal Terrestrial Radio Access) with a channel bandwidth of 200kHz. NB-IoT uses a physical layer optimized for very low power consumption to provide access to network services; for example, this includes using a full carrier bandwidth of 180kHz, subcarrier spacing of 3.75kHz or 15kHz, and so on. In an NB-IoT carrier, subcarrier spacing of 3.75kHz and 15kHz can correspond to transmission bandwidth configurations of 48 subcarriers and 12 subcarriers, respectively.

[0091] NB-IoT removes many features from E-UTRA that are not relevant to the design goals of NB-IoT, such as inter-RAT mobility, handover, relaying, carrier aggregation, dual connectivity, side-to-side communication, and side-to-side discovery, thereby greatly reducing the complexity of the UE.

[0092] NB-IoT supports stand-alone operation, guard band operation, and in-band operation. In stand-alone operation, NB-IoT uses its own spectrum, such as the spectrum corresponding to one or more GSM (Global System for Mobile communications) carriers. In guard band operation, NB-IoT can use unused resource blocks (RB(s)) within the guard band of an E-UTRA carrier. In in-band operation, NB-IoT can use resource blocks (RB(s)) within a normal E-UTRA carrier.

[0093] NB-IoT supports two UE categories: Category NB1 and Category NB2. UEs supporting the latter must also support the former. Category NB2 supports larger maximum uplink TBS, maximum downlink TBS, and Layer 2 buffer size than Category NB1.

[0094] Both eMTC and NB-IoT can be considered as LPWA (low power, wide area) technologies, and their devices are characterized by low cost, long battery life, ubiquitous coverage, and high system capacity.

[0095] In recent years, automation and digitalization across various industries have opened up many new markets, creating a pressing need for new IoT technologies to support devices with lower complexity and / or power consumption (e.g., one or more orders of magnitude lower than existing 3GPP LPWA technologies such as eMTC and / or NB-IoT). This could include devices with very limited energy storage capacity and no rechargeable or manually replaceable batteries. Additionally, new IoT technologies need to support higher connection counts and / or device densities (e.g., one or more orders of magnitude higher than existing 3GPP LPWA technologies such as eMTC and / or NB-IoT). To this end, 3GPP launched a study item in Rel-19 called "Study on solutions for Ambient IoT (Internet of Things) in NR" to evaluate the feasibility of new IoT technologies (including corresponding wireless access technologies) known as "Ambient Power-enabled IoT" (or simply A-IoT).

[0096] In some aspects, A-IoT can support one or more deployment scenarios, such as some or all of "standalone deployment," "guard-band deployment," and "in-band deployment." For example, in standalone deployment, A-IoT can use its own spectrum (e.g., spectrum that does not overlap with the spectrum occupied by any NR or LTE carrier); in guard-band deployment, A-IoT can use unused resource blocks (RB(s)) in the guard band of an NR (or LTE) carrier; and in in-band deployment, A-IoT can use resource blocks (RB(s)) in an NR carrier. In some aspects, each deployment scenario can correspond to an A-IoT "operation mode," or, where there is no risk of confusion, simply "operation" or "mode," for example, "standalone deployment" corresponds to "standalone operation mode," "guard-band deployment" corresponds to "guard-band operation mode," and "in-band deployment" corresponds to "in-band operation mode." In some respects, for an A-IoT system, "deployment scenario" can be equated with "operation mode," and vice versa.

[0097] In some aspects, the deployment scenarios of an A-IoT system (e.g., denoted as...) It can be determined, at least in part, based on some or all of the following: predefined information, configuration information, and instruction information. For example, the... Each value can correspond to one of the following deployment scenarios, either partially or entirely: "Standalone deployment", "Protection band deployment", and "In-band deployment".

[0098] In some respects, an A-IoT system may include at least some or all of the following:

[0099] ● One or more devices. Here, "devices" can also be called "A-IoT devices", "A-IoT UEs", "A-IoT terminals", or "A-IoT transponders".

[0100] ● One or more “readers” (or “interrogators”), wherein a reader may be a base station (e.g., a 5G base station), or an “intermediate node” that can communicate bidirectionally with the base station(s) (e.g., via the LTE Uu interface; or, as another example, via the NRUu interface), or a communication node defined in other ways.

[0101] ● One or more "carrier-wave nodes" (or "CW nodes"), where a CW node can be used to transmit CW (carrier-wave, radio frequency carrier-wave, RF carrier-wave, RF CW). In some respects, a CW transmission can be considered as a transmission from one CW node to one or more devices, and correspondingly, it can also be called a "CW2D" (cw-node-to-device) transmission.

[0102] ● One or more core network nodes, for example, may include at least some or all of the following: one or more “AIoTF” (A-IoT Function) that can communicate via NAS layer signaling and devices (or, readers), and one or more AMFs that can communicate via NAS layer signaling and readers (or, devices).

[0103] In some respects, in an A-IoT system, a communication node can support more than one A-IoT function. For example, a communication node can be both a reader and a CW node.

[0104] In some aspects, in an A-IoT system, the protocol stack for the radio interface between devices and readers may include at least some or all of the following: the A-IoT physical layer and the A-IoT MAC layer. In this disclosure, unless otherwise specified, "physical layer" may refer to the A-IoT physical layer, and "MAC layer" may refer to the A-IoT MAC layer.

[0105] In some respects, an A-IoT system can at least partially support one or more of the following business types:

[0106] ● "Inventory". For example, this can be used at least in part to discover and obtain device IDs.

[0107] ● "Command". For example, this can be used at least in part to send operation instructions to the device, such as commands like "read", "write", and "disable".

[0108] In some respects, at the Access Stratum (AS), information related to services (e.g., “inventory counting” services; or “command” services) can be transmitted on the A-IoT wireless interface as data from higher layers (e.g., one or more higher layers with the MAC layer as the reference protocol layer or reference protocol sublayer; or one or more higher layers with an access layer protocol layer above the MAC layer as the reference protocol layer or reference protocol sublayer).

[0109] In some respects, AS can also be referred to as "AS layer".

[0110] In some respects, a device can be attached to a tag (or label) on an item.

[0111] In some respects, a “device ID” can be used to identify (e.g., uniquely identify) or associate (or map to) a device. In some respects, a device ID can be an integer (e.g., a 16-bit integer; or a 24-bit integer; or a 32-bit integer; or a 48-bit integer; or a 64-bit integer; or a 96-bit integer; or a 128-bit integer), or it can be defined in other ways.

[0112] In some aspects, a "device group ID" can be used to identify (e.g., uniquely identify) or associate (or map to) one or more devices in an A-IoT system, wherein the one or more devices can be considered to constitute a "device group". In some aspects, a device group ID can be an integer (e.g., a 16-bit integer; or a 24-bit integer; or a 32-bit integer; or a 48-bit integer; or a 64-bit integer; or a 96-bit integer; or a 128-bit integer), or can be defined in other ways.

[0113] In some respects, an ID used to identify or associate (or map to) all devices can be called a “broadcast ID”. In other respects, a broadcast ID can be a special device group ID (for example, a broadcast ID can be a device group ID where every bit is 1; or, for instance, a broadcast ID can be a device group ID where every bit is 0).

[0114] In some respects, an ID that can be associated with (or mapped to) one or more devices can be called a "Type 1 ID". For example, a Type 1 ID can be an AS ID, or it can be a device ID, or it can be a device group ID, or it can be a broadcast ID, or it can be defined in other ways. In some respects, a device can be associated with one or more Type 1 IDs.

[0115] In some respects, if a Type 1 ID carried in an R2D transmission is associated with a device, then the device may be referred to as a “target device” (or “destination device”) of the R2D transmission (or the Type 1 ID).

[0116] In some respects, if an R2D transmission does not carry any type 1 ID, the target device of the R2D transmission can be any device.

[0117] In some respects, a device's physical layer can determine whether a Type 1 ID is associated with the device.

[0118] In some respects, it can be determined by the physical layer of a device whether the device is a target device for R2D transmission.

[0119] In some respects, it can be determined by a higher layer of a device (e.g., the MAC layer; or a higher layer of the MAC layer) whether a Type 1 ID is associated with the device.

[0120] In some respects, it can be determined by a higher layer of a device (e.g., the MAC layer; or a higher layer of the MAC layer) whether the device is a target device for R2D transmission.

[0121] In some respects, an intermediate node can be a UE (e.g., an LTE UE; or NR UE) that supports a reader function (e.g., referred to as a "common reader function"). In other respects, an intermediate node can transfer data and / or signaling between base stations(s) and devices (e.g., via the NR Uu interface; or LTE Uu interface).

[0122] In some respects, an intermediate node can be called an "intermediate UE" (or simply IUE), or a "reader UE", or a "UE reader", or an "A-IoT-enabled UE".

[0123] In some respects, an intermediate node can be a network-controlled communication node. For example, a network node (e.g., a base station) can control the A-IoT radio resources(s) used by the intermediate node.

[0124] In some respects, a device can communicate bidirectionally directly with a reader(s) (e.g., via A-IoT radio access technology), where...

[0125] ●The bidirectional communication may include the transmission of some or all of the following: data and signaling.

[0126] ●The bidirectional communication may include receiving some or all of the following: data and signaling.

[0127] A transmission from the device to a reader (e.g., referred to as "Reader A") can be called a D2R (device-to-reader) transmission, and the corresponding link can be called a "D2R link". In some respects, without the risk of confusion, a D2R link can be called an A-IoT "uplink".

[0128] A transmission from a reader (e.g., referred to as "Reader B") to the device can be called an R2D (reader-to-device) transmission, and the corresponding link can be called an "R2D link". In some respects, without the risk of confusion, an R2D link can be called an A-IoT "downlink".

[0129] ● In some respects, reader A and reader B may be two different readers.

[0130] ● In some respects, reader A and reader B may be the same reader.

[0131] In some aspects, the operating bands supported by an A-IoT system may at least partially include FDD bands, such as NR operating band n8 (i.e., an FDD band with an uplink operating band of 880 MHz to 915 MHz and a downlink operating band of 925 MHz to 960 MHz). In some aspects, when an A-IoT system operates in an FDD band, R2D transmission may at least partially utilize the downlink spectrum of the FDD band, D2R transmission may at least partially utilize the uplink spectrum of the FDD band, and CW transmission may at least partially utilize the uplink spectrum of the FDD band.

[0132] In some aspects, an R2D transmission may at least partially include a physical channel (e.g., referred to as PRDCH, Physical Reader-to-Device Channel). In some aspects, the control information carried in the PRDCH (e.g., referred to as "Type 2 R2D Control Information") may at least partially include some or all of the following: physical layer R2D control information (e.g., referred to as "Type 2 Physical Layer R2D Control Information"), and higher layer (e.g., one or more higher layers with the physical layer as a reference protocol layer or reference protocol sublayer; specifically, including, for example, the MAC layer) R2D control information (e.g., referred to as "Type 2 Higher Layer R2D Control Information").

[0133] In some aspects, an R2D transport (or, more specifically, for example, a PRDCH in the R2D transport) can be used to carry a TB (transport block), the corresponding TBS (transport block size, TB size) of which can be represented as one or more bits, or as one or more bytes, or otherwise. In some aspects, each TB submitted to the physical layer can be a MAC PDU (Protocol Data Unit) of the MAC layer, or otherwise defined.

[0134] In some respects, an R2D transmission may at least partially include (or be associated with) an R2D timing acquisition signal (R-TAS), wherein,

[0135] ● In some respects, in the time domain, the R-TAS may immediately precede the PRDCH in the R2D transmission.

[0136] ● In some respects, the R-TAS can be used at least in part for some or all of the following: timing acquisition, indicating the start of the PRDCH (e.g., at the start of the time domain), and indicating the start of the R2D transmission (e.g., at the start of the time domain).

[0137] ● In some respects, the R-TAS may carry control information, for example, referred to as “Type 1 R2D control information”.

[0138] ● In some respects, the R-TAS may include at least part of the following: a start-indicator part (SIP) and a clock-acquisition part (CAP).

[0139] ● In some respects, in the time domain, the CAP may immediately follow the SIP.

[0140] ● In some respects, the SIP can be used at least in part to indicate (or provide) the start of the R2D transmission (e.g., the start in the time domain), wherein, for example, the corresponding indication information can be part of the Type 1 R2D control information.

[0141] ● In some respects, the SIP can be used at least in part to indicate (or provide) the start of the PRDCH (e.g., the start in the time domain), wherein, for example, the corresponding indication information can be part of the Type 1 R2D control information.

[0142] ● In some respects, the R-TAS may be part of the R2D transmission, and correspondingly, for example, the R2D transmission may begin at the R-TAS.

[0143] ● In some respects, the R-TAS may not be part of the R2D transmission; correspondingly, for example, the R2D transmission may refer to the PRDCH.

[0144] ● In some respects, the R-TAS may not be part of the PRDCH.

[0145] ● In some respects, the R-TAS can be referred to as an "R2D preamble".

[0146] ● In some aspects, the information carried in the R-TAS may be referred to as "R2D timing acquisition information". In some aspects, "R2D timing acquisition information" may refer to the information carried in the CAP in the R-TAS. In some aspects, "R2D timing acquisition information" may include part or all of the Type 1 R2D control information.

[0147] In this disclosure, unless otherwise specified, “R2D control information” may refer to some or all of the following: Type 1 R2D control information and Type 2 R2D control information.

[0148] In some respects, an R2D transmission may at least partially contain (or be associated with) an "R2D postamble" (R-POA), in which,

[0149] ● In some respects, in the time domain, the R-POA may immediately follow the PRDCH in the R2D transmission.

[0150] ● In some respects, the R-POA can be used at least in part to indicate the end of the R2D transmission (or, the PRDCH).

[0151] ● In some respects, the R-POA may not be part of the PRDCH.

[0152] ● In some respects, the R-POA may be part of the PRDCH.

[0153] In some respects, in R2D reception, the remainder of an R2D transmission (e.g., CAP, and PRDCH) is only received if a SIP of an R2D transmission is correctly received (or detected).

[0154] In some respects, in R2D reception, the remainder of an R2D transmission (e.g., PRDCH) is only received if the SIP and CAP of an R2D transmission are correctly received (or detected).

[0155] In some aspects, during R2D reception, at least in part, the following can be determined based on the R2D control information carried in an R2D transmission (e.g., Type 1 R2D control information, or Type 2 R2D control information): the end time of the R2D transmission and the time-domain position of the corresponding R-POA (e.g., including the start time). In some aspects, if a valid R-POA is not detected at the determined time-domain position of the R-POA, the R2D transmission is discarded.

[0156] In some aspects, a D2R transmission may at least partially include a physical channel (e.g., referred to as PDRCH, Physical Device-to-Reader Channel). In some aspects, the control information carried in the PDRCH (e.g., referred to as "Type 2 D2R Control Information") may at least partially include some or all of the following: physical layer D2R control information, and higher layer (e.g., one or more higher layers with the physical layer as a reference protocol layer or reference protocol sublayer) D2R control information.

[0157] In some aspects, a D2R transport (or, more specifically, for example, a PDRCH in the D2R transport) can be used to carry a TB, the corresponding TBS of which can be represented as several bits, or several bytes, or in other ways. In some aspects, each TB submitted to the physical layer can be a MAC PDU of the MAC layer, or can be defined in other ways.

[0158] In some respects, a D2R transmission may at least partially include (or be associated with) a D2R timing acquisition signal (D-TAS), wherein,

[0159] ● In some respects, in the time domain, the D-TAS may immediately precede the PDRCH in the D2R transmission.

[0160] ● In some aspects, the D-TAS can be used at least in part for some or all of the following: timing acquisition, indicating the start of the PDRCH (e.g., at the start of the time domain), and indicating the start of the D2R transmission (e.g., at the start of the time domain).

[0161] ● In some aspects, the control information carried in the D-TAS (e.g., referred to as "Type 1 D2R control information") may at least partially include physical layer D2R control information.

[0162] ● In some respects, the D-TAS may be part of the D2R transmission, and correspondingly, for example, the D2R transmission may begin at the D-TAS.

[0163] ● In some respects, the D-TAS may not be part of the D2R transmission; correspondingly, for example, the D2R transmission may refer to the PDRCH.

[0164] ● In some respects, the D-TAS may not be part of the PDRCH.

[0165] ● In some aspects, the D-TAS can be referred to as a "D2R preamble". In some aspects, the D2R preamble can correspond to an M-sequence. In some aspects, the D2R preamble can correspond to a Golay sequence.

[0166] ● In some aspects, the information carried in the D-TAS may be referred to as "D2R timing acquisition information". In some aspects, "D2R timing acquisition information" may include part or all of the type 1 D2R control information.

[0167] In this disclosure, unless otherwise specified, “D2R control information” may refer to some or all of the following: Type 1 D2R control information and Type 2 D2R control information.

[0168] In some respects, a D2R transmission may at least partially contain (or associate with) one or more "D2R midambles" (D-MIAs), where,

[0169] ● In some respects, the D-MIA can be used at least in part for some or all of the following: timing acquisition and channel estimation.

[0170] ● In some respects, the D-MIA may not be part of the PDRCH.

[0171] ● In some respects, the D-MIA may be part of the PDRCH.

[0172] ● In some aspects, the D-MIA may correspond to an M-sequence. In other aspects, the D-MIA may correspond to a Golay sequence.

[0173] In some respects, a D2R transmission may at least partially contain (or be associated with) a "D2R postamble" (D-POA).

[0174] ● In some respects, in the time domain, the D-POA may immediately follow the PDRCH in the D2R transmission.

[0175] ● In some respects, the D-POA can be used at least in part for some or all of the following: timing acquisition, channel estimation, and indicating the end of the D2R transmission (or the PDRCH).

[0176] ● In some respects, the D-POA may not be part of the PDRCH.

[0177] ● In some respects, the D-POA may be part of the PDRCH.

[0178] ● In some aspects, the D-POA may correspond to an M-sequence. In other aspects, the D-POA may correspond to a Golay sequence.

[0179] In some aspects, a device can be identified using an "Access Layer ID" (AS ID). For example, an AS ID can be assigned to a device in R2D control information carried in an R2D transmission, and the AS ID can be used to identify the device in one or more subsequent R2D and / or D2R transmissions. In some aspects, the AS ID can be used for some or all of the following: D2R scheduling and R2D reception. In some aspects, the length of an AS ID (e.g., 16 bits; or, for example, 8 bits) is less than the length of a device ID (e.g., 48 bits; or, for example, 32 bits; or, for example, 24 bits).

[0180] In some respects, the R2D control information carried in an R2D transmission may at least partially include "target (or destination) device information," for example, indicating devices(s) that need to respond to the R2D transmission, wherein each device that needs to respond to the R2D transmission may be referred to as a target device of the R2D transmission. For example, the target device information may at least partially include some or all of the following: one or more device IDs, one or more AS IDs, one or more device group IDs, and a broadcast ID. Specifically, for example, if a device (e.g., d0) successfully receives an R2D transmission, and the corresponding target device information satisfies one or more of the following, then device d0 may be a target device of the R2D transmission:

[0181] ● One of the one or more device IDs included in the target device information is the device ID of device d0.

[0182] ● One of the one or more AS IDs included in the target device information is the AS ID assigned to the device d0.

[0183] ● One of the one or more AS IDs included in the target device information is an AS ID assigned to the device d0 that has not expired.

[0184] ●One of the one or more device group IDs contained in the target device information corresponds to (or is associated with; or is mapped to) one or more devices including the device d0.

[0185] ●One of the one or more device group IDs contained in the target device information corresponds to (or is associated with; or is mapped to) one or more device IDs, including the device ID of device d0.

[0186] ●The target device information includes a "broadcast ID".

[0187] In some respects, the target device(s) of an R2D transmission can refer to the target device(s) of the higher-layer (e.g., one or more layers above the physical layer) messages carried by the R2D transmission.

[0188] In some respects, an R2D transmission can be used to trigger (or schedule) one or more D2R transmissions, wherein, for example, each D2R transmission can be sent by a distinct target device of the R2D transmission.

[0189] In some respects, an "A-IoT transmission" can refer to part or all of a transmission sent by a node in an A-IoT system (such as a reader, a device, or a CW node). For example, an A-IoT transmission can refer to an R2D transmission (or a part of it, such as a physical layer channel or physical layer signal), or a D2R transmission (or a part of it, such as a physical layer channel or physical layer signal), or a CW transmission.

[0190] In some aspects, the transmission bandwidth of an A-IoT transmission can be expressed in Hertz (Hz), kilohertz (kHz), megahertz (MHz), the number of subcarriers, the number of RBs, or other units.

[0191] In some aspects, a device may support energy harvesting technology, for example, by capturing and converting energy from its surrounding environment (e.g., radio waves therein) for power generation and / or storage. In some aspects, the antenna for communication and the antenna for radio frequency (RF) energy harvesting may be the same antenna or different antennas. In some aspects, a device supporting energy harvesting may be equipped with a rechargeable or manually replaceable battery, or may not be equipped with any such battery.

[0192] In some respects, a device can support backscattered transmission (or backscattering transmission), where, for example, the device can modulate the backscattered CW transmitted by a CW node to achieve a D2R transmission. Specifically, for example, the device can change the impedance or reflection coefficient of its antenna according to the information to be transmitted, thereby switching the backscattered signal between "high-voltage" and "low-voltage" states. For the device, the CW can be considered as "externally provided" (rather than generated internally by the device).

[0193] In some respects, the CW waveform used for backscattering can be some or all of the following:

[0194] ●CW waveform 1: Single-tone unmodulated sinusoid, or simply "one-single-tone" waveform.

[0195] ●CW waveform 2: A waveform consisting of two single tones (e.g., two unmodulated sine waves), or simply a "two-single-tone" waveform.

[0196] Compared to backscatter-based transmission, transmission generated internally by a device can be called "internally-generated transmission" (or "self-generated transmission," or "transmission based on independent signal generation"). For example, in an internally-generated transmission, steps such as digital baseband signal generation, digital-to-analog conversion, filtering, mixing, analog RF signal generation and amplification, and outputting the signal to the antenna can all be performed internally by the device.

[0197] In some respects, “backscatter-based transmission” and “endogenous transmission” can be considered as two different “types” or “transmission schemes” of D2R transmission.

[0198] In some respects, devices in an A-IoT system can be categorized into multiple categories (or, "types").

[0199] For example, a "Type 1" device can be characterized, at least in part, by some or all of the following:

[0200] ● Ultra-low peak power consumption (e.g., around 1μW; or, for example, no more than 10μW).

[0201] ● It has energy storage.

[0202] ● Receivers based on radio frequency envelope detectors (RF Envelope Detectors).

[0203] ●The initial SFO (sampling frequency offset) can be as high as (parts per million, percentage per million), where N SFO，1 It can be a fixed value (e.g., N) SFO，1 =4; for example, N SFO，1 =5), or it can vary within a certain range depending on certain conditions.

[0204] ● No signal amplification capability (e.g., neither R2D nor D2R signal amplification capability).

[0205] ●D2R transmission is based on backscattering.

[0206] In some respects, a Type 1 device may also be referred to as a "Category 1" device, or, where there is no risk of confusion, as a "Device 1".

[0207] For example, a "Type 2a" device can be characterized, at least in part, by some or all of the following:

[0208] ● Very low peak power consumption (e.g., no more than a few hundred μW; or around 100 μW; or no more than 1 mW; or no more than 10 mW).

[0209] ● It has energy storage.

[0210] ● Receivers based on radio frequency envelope detectors (RF Envelope Detectors).

[0211] ●Initial SFO Gundam Where N SFO,2AIt can be a fixed value (e.g., N) SFO,2A =4; for example, N SFO,2A =5), or it can vary within a certain range depending on certain conditions.

[0212] ● Has signal amplification capability (e.g., partial or complete R2D and D2R signal amplification capability).

[0213] ●D2R transmission is based on backscattering.

[0214] In some respects, a type 2a device may also be referred to as a “Category 2a” device, or, where there is no risk of confusion, as a “Device 2a”.

[0215] For example, a "Type 2b" device can be characterized, at least in part, by some or all of the following:

[0216] ● Very low peak power consumption (e.g., no more than a few hundred μW; or around 100 μW; or no more than 1 mW; or no more than 10 mW).

[0217] ● It has energy storage.

[0218] ●Initial SFO Gundam Where N SFO,2B It can be a fixed value (e.g., N) SFO，2B =4; for example, N SFO，2B =5), or it can vary within a certain range depending on certain conditions.

[0219] ● Has signal amplification capability (e.g., partial or complete R2D and D2R signal amplification capability).

[0220] ●D2R transmission is an intrinsic transmission.

[0221] In some respects, a Type 2b device may also be referred to as a "Category 2b" device, or, where there is no risk of confusion, a "Device 2b".

[0222] In some respects, an "R2D resource" can refer to a resource that can be used for R2D transmission and / or reception. For example, for a device, an R2D resource can be used for R2D reception; as for a reader, an R2D resource can be used for R2D transmission.

[0223] In some respects, a “D2R resource” can refer to a resource that can be used for D2R transmission and / or reception. For example, for a device, a D2R resource can be used for D2R transmission; for a reader, a D2R resource can be used for D2R reception.

[0224] In some respects, a “CW resource” can refer to a resource that can be used for CW transmission.

[0225] In some respects, an "A-IoT resource" can refer to an R2D resource, a D2R resource, or a CW resource.

[0226] In some respects, an A-IoT resource can be a time-domain resource, and accordingly, the A-IoT resource can correspond to (or be associated with) one or more time-domain parameters, or the A-IoT resource can be identified (or characterized) by the one or more time-domain parameters.

[0227] In some respects, an A-IoT resource can be a frequency domain resource, and correspondingly, the A-IoT resource can correspond to (or be associated with) one or more frequency domain parameters, or the A-IoT resource can be identified (or characterized) by the one or more frequency domain parameters.

[0228] In some respects, an A-IoT resource can be a time-frequency resource, and accordingly, the A-IoT resource can correspond to (or be associated with) one or more time-domain parameters and one or more frequency-domain parameters, or the A-IoT resource can be identified (or characterized) by the one or more time-domain parameters and the one or more frequency-domain parameters.

[0229] In some aspects, in the time domain, an A-IoT transmission can occupy one or more "chips," which can be time-domain resources corresponding to the respective A-IoT resources. For example, an R2D transmission can occupy one or more "R2D chips" (e.g., one or more consecutive R2D chips). Similarly, a D2R transmission can occupy one or more "D2R chips" (e.g., one or more consecutive D2R chips).

[0230] In some respects, each chip can have a corresponding "value". For example, a chip "1" can refer to a chip with a value of "1"; a chip "0" can refer to a chip with a value of "0"; a chip "+1" can refer to a chip with a value of "+1"; and a chip "-1" can refer to a chip with a value of "-1".

[0231] In some aspects, an A-IoT transmission (e.g., an R2D transmission; or a D2R transmission) can use OOK (On-Off Keying) modulation, whereby, for example, a chip "1" can correspond to a "high voltage" amplitude envelope, and a chip "0" can correspond to a "low voltage" amplitude envelope. In some aspects, in this case, a chip can be called an "OOK chip".

[0232] In some respects, an A-IoT transmission (e.g., an R2D transmission; or D2R transmission) can use BPSK (Binary phase-shift keying) modulation, whereby, for example, chip "1" (or, in this case, "+1") can correspond to a 0° phase envelope, and chip "0" (or, in this case, "-1") can correspond to a 180° phase envelope.

[0233] In some respects, a chip can correspond to a modulated symbol. For example, this can apply to some or all of the following: OOK, and BPSK.

[0234] In some respects, the duration of a chip (e.g., an R2D chip; or, as another example, a D2R chip) may be referred to as the "chip duration" (or "chip length"). In some respects, the chip durations corresponding to different parts of an R2D transmission may be equal or unequal. In some respects, the chip durations corresponding to different parts of a D2R transmission may be equal or unequal.

[0235] In some respects, chip duration (e.g., R2D chip duration; or D2R chip duration) can be expressed in seconds, milliseconds, microseconds, etc., or can be expressed as an integer multiple or fraction of the length of an OFDM symbol (or slot, or subframe, etc.), or can be expressed in other units.

[0236] In this disclosure, unless otherwise specified, the elements in a chip sequence (or chip set) may appear in chronological order, or the indices of the elements in the chip sequence (or chip set) may increase in chronological order.

[0237] In some respects, "chip padding" can refer to adding one or more "padding chips" to the end of a chip sequence, wherein the values ​​of the one or more "padding chips" can all be equal, for example, all of them being chip "0" (or chip "1", or chip "+1", or chip "-1"). A padding chip in an R2D transmission can be called an "R2D padding chip", and a padding chip in a D2R transmission can be called a "D2R padding chip".

[0238] In some respects, it is possible to have a length of The input bit sequence (e.g., denoted as) ) Perform "repetition number" for R b The "repetition" operation yields a result of length [length missing]. The output bit sequence, where,

[0239] ●In some respects, It can be a satisfaction Integers.

[0240] ●In some respects, R b It can be a condition that satisfies R b Integers ≥ 1.

[0241] ●In some respects, R b =1 can represent no repetition (correspondingly, the output bit sequence can be equal to the input bit sequence), R b =2 can represent one repetition, R b =3 can represent two repetitions, and so on.

[0242] ● In some respects, the repetition operation may refer to the sequential repetition of each input bit (e.g., this may be called "bit-level repetition"), for example, for R b =2, The output bit sequence can be

[0243] ● In some respects, the repetition operation can refer to repeating the entire input bit sequence (e.g., this could be called "block-level repetition"), for example, for R b =2, The output bit sequence can be

[0244] In some respects, in repetitive operations, the "number of repetitions" can refer to R.b -1 (instead of R) b Accordingly, a "repetition count" of 0 can indicate no repetition (correspondingly, the output bit sequence can be equal to the input bit sequence), a "repetition count" of 1 can indicate one repetition, a "repetition count" of 2 can indicate two repetitions, and so on.

[0245] In some respects, the “number of repetitions” in repetitive operations can refer to the “number of repetitions”.

[0246] In some respects, a "CRC (Cyclic Redundancy Check) operation" can be performed on an A-IoT transmission (e.g., an R2D transmission, or a portion thereof, such as its PRDCH; or a D2R transmission, or a portion thereof, such as its PDRCH), wherein the type of the CRC operation can be one or more predefined or configured types, and the CRC operation can be a CRC attachment operation performed on a bit sequence consisting of some or all of the information bits carried by the A-IoT transmission (or, another bit sequence obtained by performing, for example, bit stuffing on the bit sequence). For example, a "Type 0 CRC operation" can refer to not performing a CRC attachment on the A-IoT transmission; a "Type 1 CRC operation" can refer to performing a CRC attachment of length 6 on the A-IoT transmission; a "Type 2 CRC operation" can refer to performing a CRC attachment of length 16 on the A-IoT transmission; a "non-Type 0 CRC operation" can refer to performing either a "Type 1 CRC operation" or a "Type 2 CRC operation" on the A-IoT transmission; and a "non-Type 0 CRC operation" can refer to performing a CRC attachment of length greater than 0 on the A-IoT transmission. In some aspects, the output bit sequence generated by the CRC operation can be called the "second output bit sequence" of the A-IoT transmission, and correspondingly, the input bit sequence of the CRC operation can be called the "second input bit sequence" of the A-IoT transmission. In some aspects, if the CRC operation performed is a "Type 0 CRC operation," then the "second input bit sequence" and the "second output bit sequence" can be two identical bit sequences.

[0247] In some aspects, the "second input bit sequence" may be an output bit sequence resulting from bit stuffing a "first input bit sequence" of the A-IoT transmission. In some aspects, the "first input bit sequence" may include some or all of the following: all bits of the physical layer control information carried by the A-IoT transmission, and all bits of the TB carried by the A-IoT transmission. In some aspects, if the bit stuffing operation performed is a "type 0 bit stuffing operation," then the "first input bit sequence" and the "second input bit sequence" may be two identical bit sequences.

[0248] In some aspects, the "second input bit sequence" may consist of two subsequences, wherein, for example, the first subsequence may at least partially include all bits of the physical layer control information carried by the A-IoT transmission, and the second subsequence may at least partially include all or part of the following: all bits of the TB carried by the A-IoT transmission, and padding bits (bit(s)) (if any). In this disclosure, "CRC operation" may refer to a CRC operation performed on the "second input bit sequence," or it may refer to a CRC operation performed on the first subsequence of the "second input bit sequence," or it may refer to a CRC operation performed on the second subsequence of the "second input bit sequence." In some aspects, the CRC operation performed on the second subsequence of the "second input bit sequence" may be referred to as a CRC operation performed on the TB carried by the A-IoT transmission.

[0249] In some aspects, line coding can be applied to an A-IoT transmission (e.g., an R2D transmission, or its PRDCH; or a D2R transmission, or its PDRCH). For example, line coding can be applied to the "second output bit sequence" of the A-IoT transmission; or, for example, line coding can be applied to the output bit sequence (e.g., bit-level repetition; or, block-level repetition) generated after performing a repetition operation on the "second output bit sequence" as input (e.g., bit-level repetition; or, block-level repetition). Alternatively, line coding can be applied to the output bit sequence (e.g., the "fourth output bit sequence" of the A-IoT transmission) generated after performing channel coding; or, for example, line coding can be applied to the output bit sequence (e.g., the "fifth output bit sequence" of the A-IoT transmission) generated after performing a repetition operation (e.g., bit-level repetition; or, block-level repetition) on the "fourth output bit sequence" as input (e.g., the "fifth output bit sequence" of the A-IoT transmission). In some aspects, the channel-coded input bit sequence (e.g., referred to as the "fourth input bit sequence" of the A-IoT transmission) may be the "second output bit sequence". In some aspects, the "fourth input bit sequence" may be the "third output bit sequence".

[0250] In some respects, some or all of the bits in the "first input bit sequence", the "second input bit sequence", the "second output bit sequence", the "third output bit sequence", the "fourth input bit sequence", the "fourth output bit sequence", and the "fifth output bit sequence" may be referred to as "information bits".

[0251] Examples of line coding may include, at least in part, Manchester coding, where, for example, the codeword mapped to bit "0" could be the chip sequence "1,0"; or the codeword mapped to bit "1" could be the chip sequence "0,1"; or the codeword mapped to bit "0" could be the chip sequence "0,1"; or the codeword mapped to bit "1" could be the chip sequence "1,0".

[0252] In some respects, the chip duration of an R2D chip (e.g., denoted as...) It can be at least partially based on an associated "R2D chip duration factor" (e.g., denoted as...). ) Determined, among which, It can be a satisfaction Integers. For example, the... It can be equal to Where l can be the index of the OFDM symbol in which the R2D chip is located (e.g., the index of the OFDM symbol in a subframe; or the index of the OFDM symbol in a time slot), and μ can be the SCS configuration used by the corresponding R2D transmission. It can be a reference OFDM symbol length, for example, It can be equal to (or or In some respects, for different OFDM symbols, the stated The methods for determining these can be the same or different.

[0253] In some respects, the set of values ​​for the R2D chip duration factor can be denoted as: in, It can be a satisfaction integers, for example, The value can be one of 32, 28, 24, 20, 18, 16, 15, 14, 13, 12, 11, 10, 9, 8, 7, 6, 5, 4, 3, 2, and 1. In some respects, the set... It may include at least some or all of the following R2D chip duration factor values: 1, 2, 4, 6, 8, 12, 16, 24, and 32. In some respects, for The corresponding R2D chip duration can be denoted as: Accordingly, the set The corresponding set of R2D chip durations can be denoted as:

[0254] In some respects, the R-POA contained (or associated with) an R2D transmission may correspond to a specific chip sequence (e.g., referred to as the "R-POA chip sequence"). In some respects, the R-POA chip sequence may differ from any chip sequence fragment that may appear in the PRDCH carried by the R2D transmission.

[0255] In some respects, chip padding can be performed on an R2D transmission. For example, the purpose of chip padding may be to align the R2D transmission to the boundary of its latest occupied OFDM symbol. In some respects, the padded chip(s) can be considered part of the R2D transmission. In some respects, the padded chip can be considered not part of the R2D transmission, in which case the padded chip can be considered a padding chip "associated" with the R2D transmission.

[0256] In some respects, in the time domain, a D-MIA can be inserted every few D2R chips in the PDRCH of a D2R transmission.

[0257] In some respects, each D-MIA in a D2R transmission may correspond to a specific chip sequence (e.g., referred to as the "D-MIA chip sequence"). In some respects, the D-MIA chip sequence may differ from any chip sequence fragment that may appear in the PDRCH.

[0258] In some respects, a D-POA in a D2R transmission can correspond to a specific chip sequence (e.g., referred to as the "D-POA chip sequence"). In some respects, the D-POA chip sequence can differ from any chip sequence fragment that may appear in the PDRCH.

[0259] In some respects, the chip durations used by different parts of a D2R transmission (e.g., some or all of the following: D-TAS, PDRCH, D-MIA, and D-POA) may be the same or different.

[0260] In some respects, different parts of a D2R transmission (e.g., some or all of the following: D-TAS, PDRCH, D-MIA, and D-POA) can use the same chip duration.

[0261] In some respects, a small frequency shift (SFS) can be applied to a D2R transmission. For example, this can be manifested as the D2R transmission operating in the frequency domain relative to the carrier frequency (CW frequency, e.g., denoted as f). c This produces a frequency shift of amount f. a The frequency shift, where, for example, the f a It can reach tens of kilohertz; for example, the f a It can reach up to several hundred kilohertz; for example, the f a The maximum frequency can reach several megahertz. Specifically, for example, in the case that the D2R transmission is a double-sideband transmission, the center frequencies of the lower sideband and upper sideband of the D2R transmission can be f0 and f1, respectively. c One f a and f c +f a The transmission bandwidth of the D2R transmission (e.g., denoted as...) For example, it can be equal to the sum of the bandwidth of the lower sideband and the bandwidth of the upper sideband; or, for example, in the case that the D2R transmission is a single-sideband transmission, the transmission bandwidth of the D2R transmission... For example, it can be equal to the sideband where the D2R transmission is located (e.g., the lower sideband, with a corresponding center frequency of f). c -f a For example, the center frequency of the sideband above is f. c +f a The bandwidth of ). In some respects, the bandwidth of ) This can be referred to as a "D2R transmission bandwidth".

[0262] In some respects, a D2R transport (or the D2R resources used by the D2R transport) can be associated with an "SFS factor" (e.g., denoted as ). ), where, for example, the SFS factor It can be defined as in, This can represent the D2R chip duration used in the D2R transmission (or, the PDRCH in the D2R transmission). This can be the "bit duration" (or bit length) used in the D2R transmission (or the PDRCH in the D2R transmission), that is, the time length corresponding to one bit (e.g., one information bit). For example, the bit can be a bit in the "second output bit sequence" (or "third output bit sequence"; or "fourth output bit sequence"; or "fifth output bit sequence") of the D2R transmission; or, for example, the bit can be a bit in the input bit sequence when performing a repetitive operation on the D2R transmission (or the PDRCH transmission in the D2R transmission). The unit can be related to the The units are the same (for example, the same unit could be seconds, milliseconds, microseconds, nanoseconds, or other units). In some respects, the “bit duration” may also be referred to as “D2R bit duration”.

[0263] In some respects, the transmission bandwidth of a D2R transmission and the corresponding bit duration The relationship can be (For example, when the said The unit is seconds, and the stated (The unit is Hertz). Those skilled in the art will understand that when the... and / or the aforementioned When using other units, the above relationship can be adjusted accordingly. For example, when the above... The unit is seconds, and the stated When the unit is kilohertz, the... It can be equal to In some respects, the stated It can correspond to a predefined parameter (e.g., For example, In some aspects, such as when the D2R transmission is a double-sideband transmission, the... It can be equal to 4. In some aspects, such as when the D2R transmission is a single-sideband transmission, the... It can equal 2.

[0264] In some respects, for a given bit duration (Or, the corresponding transmission bandwidth) The duration of each D2R chip Each can correspond to a different (distinct) SFS factor. vice versa.

[0265] In some respects, the SFS factor (Or, the corresponding D2R chip duration) It can be used to identify the frequency shift f. a For example, for a given bit duration, any two different SFS factors (or corresponding D2R chip durations) can correspond to two different frequency shifts. Therefore, FDMA (Frequency Division Multiple Access) can be achieved by appropriately assigning different SFS factors (or corresponding D2R chip durations) to multiple different D2R transmissions (e.g., multiple D2R transmissions multiplexed on the same time resource; or multiple D2R transmissions that overlap in time).

[0266] In some respects, the size of the transport block (TBS) carried by a D2R transmission can be a "first TBS set" (e.g., denoted as ). One of the elements in ), correspondingly, for example, the TBS can be based on a set indicated in an R2D transmission that triggers (or schedules) the D2R transmission. The indices of the elements in the set are determined. In some respects, the set... It can be a predefined or configured collection.

[0267] In some aspects, within an A-IoT system, one or more protocol layers (e.g., the MAC layer) can support segmentation. For example, a higher-level response message triggered by a higher-level message received by a device (e.g., which may contain a "read" command) can be divided into multiple segments. Here, "higher-level" can refer to a protocol layer with the MAC layer (or an access layer protocol layer above the MAC layer) as its reference protocol layer. The segmentation operation can be performed at the MAC layer, and each segment of the higher-level response message can be carried in a different D2R transmission. Specifically, for example, if the higher-level response message is 2000 bits in size (e.g., sequentially numbered 0 to 1999), after being divided into three segments, bits 0 to 799 can be placed in the first segment (e.g., corresponding segment number 0), bits 800 to 1599 can be placed in the second segment (e.g., corresponding segment number 1), and bits 1600 to 1999 can be placed in the third segment (e.g., corresponding segment number 2). In some aspects, within the multiple segments,

[0268] ● In some respects, each segment may correspond to a MAC SDU (Service Data Unit) in the MAC PDU that carries the segment in the D2R transmission.

[0269] ●In some respects, different segments may be the same size or different sizes.

[0270] ● In some respects, all segments except the last one can be the same size.

[0271] ● In some respects, each segment can be carried in a different D2R transmission (e.g., the segment can be carried in a MAC PDU in the D2R transmission), for example, by a corresponding R2D transmission scheduler.

[0272] ●In some respects, not dividing the case into segments can be considered equivalent to dividing it into a single segment.

[0273] ● In some respects, the D2R control information (e.g., physical layer D2R control information, MAC layer D2R control information, or D2R control information from other layers) included in the D2R transmission carrying each segment may at least partially include a "first segmentation information" indication, indicating some or all of the following:

[0274] ■ Does it have segments?

[0275] ■Is the current paragraph the last paragraph?

[0276] ■ Are there any more paragraphs?

[0277] In some respects, a “device procedure” performed by a device (e.g., at the device’s physical layer; or, for example, at a higher layer) may include one or more steps, in which the device may send or receive a message. For example, a device may access an A-IoT system through an “A-IoT random access procedure.”

[0278] In some respects, a device procedure executed by the physical layer of a device can be called a physical layer procedure.

[0279] In some respects, a device procedure executed by a higher layer of the device (e.g., the MAC layer) can be referred to as a higher-layer (e.g., MAC layer) procedure.

[0280] In some respects, the A-IoT random access process can be triggered by a reader. For example, a Type 1 trigger message carried in an R2D transmission can be used to trigger access for a single device, or to trigger access for some or all of a group of devices, or to trigger access for all devices within the reader's coverage area (e.g., this could refer to all devices that can successfully receive the Type 1 trigger message).

[0281] In this disclosure, unless otherwise specified, “random access procedure” may refer to the A-IoT random access procedure.

[0282] In some respects, in the description of the random access procedure in this disclosure, “access” may be replaced with “random access” where applicable, and vice versa.

[0283] In some respects, the type of random access procedure (or the random access type of random access procedure) may include at least some or all of the following: contention-free access (CFA, or “contention-free random access”, CFRA) and contention-based access (CBA, or “contention-based random access”, CBRA).

[0284] In some respects, a target device(s) of an R2D transmission carrying a Type 1 trigger message can respond to the Type 1 trigger message at least in part by triggering a random access procedure.

[0285] In some aspects, in a first step of a random access procedure (e.g., CBRA), the device sends a "first A-IoT access message" (e.g., referred to as A-IoT Msg1, or, where there is no risk of confusion, Msg1), wherein the A-IoT Msg1 may be carried in a D2R transmission. In some aspects, the A-IoT Msg1 may contain a RID (random ID), wherein, for example, the RID may be a 16-bit integer, or may be defined in other ways. In some aspects, the RID may be randomly generated by the device (e.g., randomly selected from a range of values ​​for the RID), or may be determined in other ways.

[0286] In some aspects, during a second step of a random access procedure (e.g., CBRA), the device receives a "second A-IoT access message" (e.g., referred to as A-IoT Msg2, or, where there is no risk of confusion, Msg2), which may be carried in an R2D transmission. For example, the R2D transmission may carry one or more RARs (Random Access Responses), each of which may be used to respond to an A-IoT Msg1.

[0287] In some aspects, during a third step of a random access procedure (e.g., CBRA), the device sends a "third A-IoT access message" (e.g., referred to as A-IoT Msg3, or, where there is no risk of confusion, Msg3), wherein the A-IoT Msg3 may be carried in a D2R transmission, wherein the time-domain and / or frequency-domain resources of the D2R transmission may be determined by a corresponding RAR. In some aspects, the A-IoT Msg3 may contain the device ID of the device.

[0288] In some aspects, the device can receive an ACK (acknowledgment) for its A-IoT Msg3, where the ACK (e.g., referred to as "Msg3-ACK") can be carried in an R2D transmission. In other aspects, the device can consider the random access procedure to have been successful upon successfully receiving the Msg3-ACK.

[0289] In some respects, a Type 1 trigger message can be an "initial trigger message". In some respects, a Type 1 trigger message can be an A-IoT paging message. In some respects, an A-IoT paging message can be one or more initial trigger message types.

[0290] In some respects, within a given time period (e.g., a step in a device process; or, for example, a given protocol state of the device), the device may only perform D2R transmissions, and the type of message sent can only be one of a specific set of message types, which can be referred to as a "valid message type set". As a special case, the "valid message type set" may contain only one message type. For example, in the first step of the random access procedure, the "valid message type set" may contain only one message type, namely A-IoT Msg1.

[0291] In some respects, the "set of valid message types" corresponding to two different time periods (or two different steps in the same device process; or two steps in two different device processes) may be the same or different.

[0292] In some respects, within a given time period (e.g., a step in a device procedure; or, for a given protocol state of the device), the device may only perform R2D reception, and the type of the received message can only be one of a specific set of message types, which can be referred to as a "valid received message type set". As a special case, the "valid received message type set" may contain only one message type. For example, in the second step of the random access procedure, the "valid received message type set" may contain only one message type, namely A-IoT Msg2.

[0293] In some respects, the "set of valid received message types" corresponding to two different time periods (or two different steps in the same device process; or two steps in two different device processes) may be the same or different.

[0294] In some respects, an R2D transport (e.g., an R2D transport carrying a type 1 trigger message, or another R2D transport) may carry a "transaction ID". In some respects, the transaction ID can prevent a device from repeatedly triggering a random access procedure for the same transaction (e.g., a "stock count"). For example, after a random access procedure triggered by a type 1 trigger message with transaction ID 0 has successfully completed, the device may no longer respond to type 1 trigger messages with transaction ID 0 unless certain conditions are met (e.g., the device is powered on again after a power outage; or a corresponding timer times out; etc.).

[0295] In some aspects, in multi-reader scenarios, a device can sequentially receive R2D transmissions from different readers within a short period. In this case, the transaction ID can at least partially ensure the smooth operation of A-IoT services. For example, in some cases, different readers can avoid using the same transaction ID simultaneously. Furthermore, the transaction ID can be used to determine the characteristics of the R2D or D2R transmissions associated with a given transaction, thus allowing for a degree of differentiation between R2D or D2R transmissions associated with different transaction IDs.

[0296] Specifically, for example, for a given device, a transaction ID (e.g., denoted as...) Of all the A-IoT transmissions associated with a given network, a portion may belong to a first transmission set, and the remainder may belong to a second transmission set.

[0297] ● In some aspects, the first transmission set may include zero or one or more R2D transmissions (e.g., including one or more R2D transmissions each carrying an A-IoT paging message) and zero or one or more D2R transmissions.

[0298] ●In some aspects, the R2D control information carried in each of some or all of the R2D transmissions in the first transmission set (e.g., physical layer R2D control information; or, for example, higher layer R2D control information) includes information regarding the aforementioned... The R2D control information includes indication information. For example, the R2D control information includes an indication for the... The field.

[0299] ●In some aspects, the D2R control information carried in each of some or all of the D2R transmissions in the first transmission set (e.g., physical layer D2R control information; or, for example, higher layer D2R control information) includes information regarding the... The D2R control information includes indication information. For example, the D2R control information includes an indication for the... The field.

[0300] ● In some aspects, the second transmission set may include zero or one or more R2D transmissions (e.g., including one or more R2D transmissions carrying A-IoT Msg2 respectively; or, for example, including one or more R2D transmissions carrying one or more Msg3-Ack respectively) and zero or one or more D2R transmissions (e.g., including one or more D2R transmissions carrying A-IoT Msg1 respectively; or, for example, including one or more D2R transmissions carrying A-IoT Msg3 respectively).

[0301] ●In some aspects, the R2D control information carried in each of some or all of the R2D transmissions in the second transmission set (e.g., physical layer R2D control information; or, for example, higher layer R2D control information) includes the requirements for the aforementioned The R2D control information includes indication information. For example, the R2D control information includes an indication for the... The field.

[0302] ●In some respects, for each of some or all of the D2R transmissions in the second transmission set, the device may perform one or more of the following:

[0303] ■According to the above Determine the sequence used for the D2R preamble in the D2R transmission.

[0304] ■According to the above Determine the sequence used for the synchronization code in the D2R transmission.

[0305] ■According to the above Determine the sequence used for the D2R post-synchronization code in the D2R transmission.

[0306] ■Use the above The CRC of the PDRCH carried in the D2R transmission is scrambled.

[0307] ■Use the above The transport block corresponding to the PDRCH carried in the D2R transmission is scrambled (for example, scrambled before FEC is performed; or scrambled after FEC is performed).

[0308] In this disclosure, unless otherwise specified, "scrambling" can refer to the process of determining a scrambled bit sequence based on a bit sequence to be scrambled and a scrambling bit sequence, wherein, for example, for a bit b in the bit sequence to be scrambled and a bit a in the scrambling bit sequence, a corresponding scrambled bit with a value of (b+a)mod 2 can be generated. Specifically, for example, using a first bit sequence (a0, a1, ..., a... A-1 For a second bit sequence (b0, b1, ..., b...), ... B-1 Scrambling is performed to generate a third bit sequence. The process can refer to k = 0, 1, ..., B-1, It can be equal to in, It can be equal to k mod A, or it can be determined in other ways; the first bit sequence, the second bit sequence, and the third bit sequence are respectively the scrambling bit sequence, the bit sequence to be scrambled, and the scrambled bit sequence.

[0309] In this disclosure, unless otherwise specified, "device" may refer to an A-IoT device.

[0310] The following description, with reference to FIG1, illustrates a method performed by a device according to some embodiments of the present disclosure.

[0311] Figure 1 shows a flowchart corresponding to a method performed by a device according to some embodiments of the present disclosure.

[0312] As shown in Figure 1, in some embodiments of this disclosure, the steps performed by the device may include some or all of the following: step S101, step S102, step S103, step S104, and step S105.

[0313] Specifically, in step S101, a first higher layer indicates first information to one or more lower layers (e.g., denoted as...). Accordingly, in this step, the one or more lower layers receive the... In some respects, the first higher layer may be a MAC layer. In some respects, the one or more lower layers may at least partially include a physical layer.

[0314] In some respects, the stated It can be used, at least in part, for verification and / or filtering of R2D reception.

[0315] In some respects, the stated It may contain at least one or more of the following:

[0316] ●A collection of one or more Type 1 IDs (e.g., denoted as...) As a special case, the set A text may contain only one element; in this case, in some respects, it can be considered that the text contains only one element. It represents a set; in some respects, it can be considered that the... It refers to the element (not a set containing the element).

[0317] ●A collection of one or more message types (e.g., denoted as...) As a special case, the set A text may contain only one element; in this case, in some respects, it can be considered that the text contains only one element. It represents a set; in some respects, it can be considered that the... It refers to the element (not a set containing the element).

[0318] ● A transaction ID (e.g., denoted as...) ).

[0319] ● A “first receive length” (e.g., denoted as ) ).

[0320] In some respects, the stated It can be determined at least partially by the first higher layer.

[0321] In some respects, the stated It can be a set (or a subset thereof) of all Type 1 IDs associated with the device, or it can be a predefined or configured set, or it can be determined in other ways.

[0322] In some respects, the stated It can be the current (e.g., the device process being executed by the device or corresponding to one or more steps therein) "set of valid received message types", or it can be a predefined or configured set, or it can be determined in other ways.

[0323] In some respects, the stated It can be a current transaction ID (e.g., the device process being executed by the device or corresponding to one or more steps therein), or it can be a predefined or configured transaction ID, or it can be determined in other ways.

[0324] In some respects, the stated It can be a satisfaction Integers.

[0325] In some respects, the stated It can be at least in part based on the above The and the Some or all of them can be determined, or they can correspond to a predefined or configured parameter, or they can be determined in other ways.

[0326] Furthermore, in step S102, an R2D transmission is received (e.g., denoted as...). This can be part of, for example, receiving (or detecting) the stated... The SIP in the context of receiving (or detecting) the CAP in the context, and receiving (or detecting) the stated A PRDCH transmission (e.g., denoted as) The first part (e.g., denoted as) ).

[0327] In some respects, step S102 can be performed by the physical layer.

[0328] In some respects, the stated It may include only the above.

[0329] In some respects, the stated It may include at least part of the above. And a second part (e.g., denoted as) ).

[0330] In some respects, it can be at least partially based on the aforementioned Determine whether the above exists.

[0331] In some respects, the stated It may carry at least some or all of the following: physical layer R2D control information (e.g., type 2 physical layer R2D control information), a first MAC PDU, and a second MAC PDU.

[0332] In some respects, the physical layer R2D control information may at least partially contain indications of some or all of the following: a transaction ID (e.g., denoted as...). A collection of one or more type 1 IDs (e.g., denoted as...). ), and a message type (e.g., denoted as ).

[0333] In some respects, the stated Can be carried Information bits, wherein, in some respects, the It can be a satisfaction Integers.

[0334] In some respects, the stated A portion or all of an information bit can correspond to one or more of the following:

[0335] ●Some or all of the physical layer R2D control information.

[0336] ● A first higher-level payload, for example, at least partially comprising a portion of the first MAC PDU (e.g., a portion or all of the MAC header in the first MAC PDU) or all of it.

[0337] In some respects, the stated Can be carried Information bits, wherein, in some respects, the It can be a satisfaction Integers.

[0338] In some respects, the stated A portion or all of an information bit can correspond to one or more of the following:

[0339] ●Some or all of the physical layer R2D control information.

[0340] ● The second higher-level load, for example, includes at least part of the following: part of the first MAC PDU (e.g., part or all of the first MAC PDU excluding the first higher-level load; or, for example, the MAC SDU in the first MAC PDU) or all of the second MAC PDU.

[0341] In some respects, the stated It can be by Each chip (e.g., sequentially denoted by time sequence) ……,as well as Composed of, among which,

[0342] ●In some respects, the aforementioned It can be a satisfaction Integers.

[0343] ●In some respects, the aforementioned It can correspond to a predefined or configured parameter.

[0344] ●In some respects, the aforementioned It can be made from chips ……,as well as The information carried in indicates that, wherein, It can be a satisfaction Integers. For example, For example, For example, For example, For example, For example, For example, For example, In some respects, the stated This can correspond to a predefined or configured parameter. In some respects, the stated... It can be a satisfaction Integers. In some respects, the stated It can be a satisfaction An integer. In some respects, if the received... If an R-POA is detected before a chip, then perform some or all of the following: terminate PRDCH reception and discard the chip. (or, the aforementioned) ).

[0345] ●In some respects, if the aforementioned If an R-POA is detected before a chip, then perform some or all of the following: terminate PRDCH reception and discard the chip. (or, the aforementioned) ).

[0346] In some respects, the stated A chip can be obtained by Manchester encoding some or all of the following: Each information bit, and the The CRC corresponding to each information bit.

[0347] In some respects, the R2D transmission is sent. The reader (e.g., denoted as rdr0) can be a base station or an IUE.

[0348] In some respects, the R2D transmission It can be used to trigger a random access procedure. For example, the R2D transmission. It can carry a Type 1 trigger message. Specifically, for example, the Type 1 trigger message can be an A-IoT paging message.

[0349] In some respects, the R2D transmission It may not be used to trigger a random access procedure. For example, the R2D transmission. It can carry a higher-level "command".

[0350] Furthermore, in step S103, the physical layer indicates (or reports; or notifies) the second information (e.g., denoted as...) to one or more higher layers. Accordingly, in this step, the one or more higher layers receive the... In some respects, the one or more higher layers may at least partially include a MAC layer.

[0351] In some respects, the stated It can be determined by the physical layer, at least in part, according to the above. Sure.

[0352] In some respects, the stated It may include at least some or all of the following:

[0353] ●The

[0354] ●The Some or all of the information bits.

[0355] ● Some or all of the physical layer R2D control information, for example, includes some or all of the following: The and the

[0356] ●The first higher-level load.

[0357] ● Part or all of the first MAC PDU.

[0358] ● Part or all of the MAC header of the first MAC PDU.

[0359] Furthermore, in step S104, a second higher layer indicates third information to one or more lower layers (e.g., denoted as...). Accordingly, in this step, the one or more lower layers receive the... In some respects, the second higher layer may be a MAC layer. In some respects, the one or more lower layers may at least partially include a physical layer.

[0360] In some respects, the stated It can be determined by the second higher layer at least in part based on some or all of the following: and the

[0361] In some respects, the second higher layer can [the following] The bit string corresponding to part or all of the first MAC PDU (or the MAC header of the first MAC PDU) is determined to be part or all of the first MAC PDU (or the MAC header of the first MAC PDU), and part or all of the indication information in the first MAC PDU (or the MAC header of the first MAC PDU) is determined.

[0362] In some respects, the stated This can be indicated in the first MAC PDU (e.g., the MAC header of the first MAC PDU, or other parts of the first MAC PDU) rather than in the physical layer R2D control information.

[0363] In some respects, the stated This can be indicated in the first MAC PDU (e.g., the MAC header of the first MAC PDU, or other parts of the first MAC PDU) rather than in the physical layer R2D control information.

[0364] In some respects, the stated This can be indicated in the first MAC PDU (e.g., the MAC header of the first MAC PDU, or other parts of the first MAC PDU) rather than in the physical layer R2D control information.

[0365] In some respects, if the Type 1 R2D reception conditions are met, then the It contains an instruction for the first PRDCH receive operation.

[0366] In some respects, the Type 1 R2D receiving conditions may at least partially include a combination of one or more of the following in an AND or OR manner (e.g., a combination of one or more AND operations; or a combination of one or more OR operations; or an OR combination of the result of one or more AND operations with the result of another one or more AND operations; or an AND combination of the result of one or more OR operations with the result of another one or more OR operations; etc.):

[0367] ●The Greater than (or, greater than or equal to) the stated

[0368] ●The Greater than (or greater than or equal to) a predefined or configured value.

[0369] ●The The value is an undefined value.

[0370] ●The The value is a reserved value.

[0371] ●The equal to the

[0372] ●The There is one (or at least one) Type 1 ID associated with the device. As a special case, in the... In the case of containing only one type 1 ID, the The type 1 ID in the document is associated with the device.

[0373] ●The device is the One (or at least one) type 1 ID target device. As a special case, in the If the device contains only one type 1 ID, then the device is the The target device with this type 1 ID.

[0374] ●The There is one (or at least one) Type 1 ID in the above. In the middle. As a special case, in the stated In the case of containing only one type 1 ID, the The type 1 ID in this context is the one described. One of the elements. As another special case, in the... and stated In the case where each contains only one type 1 ID, the and stated The types 1 IDs contained in each are equal.

[0375] ●The There is one (or at least one) Type 1 ID in the above. In the middle. As a special case, in the stated In the case of containing only one type 1 ID, the The type 1 ID in this context is the one described. One of the elements. As another special case, in the... and stated In the case where each contains only one type 1 ID, the and stated The types 1 IDs contained in each are equal.

[0376] ●The It is an empty set.

[0377] ●The It is an empty set.

[0378] ●The It is a set One of the message types, wherein, in some respects, the set It can be the set In some respects, the set This can be the current (e.g., the set of valid received message types corresponding to a device process or one or more steps being executed by the device). As a special case, in the... In the case of only one message type, the equal to the This message type.

[0379] ●The It is one of the message types in a predefined or configured set of message types (e.g., called the "first exception received message type set").

[0380] ●The It is an undefined message type.

[0381] ●The It is a reserved message type.

[0382] In some respects, the first PRDCH receive operation may be one of the following:

[0383] ●Continue receiving PRDCH.

[0384] ●Receive the

[0385] ●Receive the The remaining part.

[0386] In some respects, if the type 2 R2D reception conditions are met, then the It contains instructions for receiving the second PRDCH.

[0387] In some respects, the type 2 R2D receiving conditions may at least partially include a combination of one or more of the following in an AND or OR manner (e.g., a combination of one or more AND operations; or a combination of one or more OR operations; or a combination of the result of one or more AND operations with the result of another one or more AND operations; or a combination of the result of one or more OR operations with the result of another one or more OR operations; etc.):

[0388] ●The Less than (or, less than or equal to) the stated

[0389] ●The Less than (or less than or equal to) a predefined or configured value.

[0390] ●The The value is an undefined value.

[0391] ●The The value is a reserved value.

[0392] ●The Not equal to the stated

[0393] ●The None of the Type 1 IDs are associated with the device. As a special case, in the... In the case of containing only one type 1 ID, the This type 1 ID is not associated with the device in question.

[0394] ●The device mentioned is not the one described. Any target device with a Type 1 ID. As a special case, in the... If the device contains only one Type 1 ID, then the device is not the one specified in the original text. The target device with this type 1 ID.

[0395] ●The and stated The intersection of these sets is the empty set. As a special case, in the... In the case of containing only one type 1 ID, the This type 1 ID is not mentioned. In the middle. As another special case, in the stated In the case of containing only one type 1 ID, the This type 1 ID is not mentioned. In the middle. As yet another special case, in the aforementioned and stated In the case where each contains only one type 1 ID, the and stated The types 1 IDs contained in them are not equal.

[0396] ●The Not equal to the set Any message type. As a special case, in the... In the case of only one message type, the Not equal to the stated This message type.

[0397] ●The It is an empty set.

[0398] ●The It is an empty set.

[0399] ●The It is one of the message types in a predefined or configured set of message types (e.g., called the "second exception receiving message type set").

[0400] ●The It is an undefined message type.

[0401] ●The It is a reserved message type.

[0402] In some respects, the second PRDCH receive operation can be one of the following:

[0403] ● Interrupt PRDCH reception.

[0404] ●Exit PRDCH reception.

[0405] ● Abandon the aforementioned Received.

[0406] ● Abandon the aforementioned The remaining portion of the reception.

[0407] In some respects, "satisfying the type 2 R2D reception condition" can be equivalent to "not satisfying the type 1 R2D reception condition". Accordingly, for example, if the type 1 R2D reception condition is not satisfied, then the type 2 R2D reception condition is satisfied; or if the type 2 R2D reception condition is satisfied, then the type 1 R2D reception condition is not satisfied.

[0408] In some respects, "satisfying the type 1 R2D reception condition" can be equivalent to "not satisfying the type 2 R2D reception condition". Accordingly, for example, if the type 2 R2D reception condition is not satisfied, then the type 1 R2D reception condition is satisfied; or if the type 1 R2D reception condition is satisfied, then the type 2 R2D reception condition is not satisfied.

[0409] In some respects, the stated The information may include some or all of the indication information from the first MAC PDU (e.g., the MAC header of the first MAC PDU), such as one or more of the following:

[0410] ● Information related to time resource allocation (e.g., denoted as...) For example, the It may include at least part of, or all of, the following: (or, the aforementioned) The end time of ) and the stated (or, the aforementioned) The number of chips.

[0411] ●Information related to transport block size (e.g., denoted as...) For example, the It may include at least part of the following: the size of the transport block corresponding to the first MAC PDU (e.g., denoted as...). ), and the size of the transport block corresponding to the second MAC PDU (e.g., denoted as ).

[0412] In addition, in step S105, one or more operations related to PRDCH reception are performed.

[0413] In some respects, step S105 can be performed by the physical layer.

[0414] In some respects, the one or more operations related to PRDCH reception can be determined at least in part based on some or all of the following: and the

[0415] In some respects, the one or more operations related to PRDCH reception may include at least in part one or more of the following:

[0416] ●According to the above The indication information in the middle determines the (or, the aforementioned) The corresponding information. For example, according to the... Determine the (or, the aforementioned) The end time of ( ). For example, according to the above... Determine the (or, the aforementioned) The number of chips. For example, the number of chips in the aforementioned... The size of the transport block corresponding to the first MAC PDU is determined. For example, the... The size of the transport block corresponding to the second MAC PDU is determined.

[0417] ●Execute the above The operation(s) indicated by the instruction information in the document. For example, if the... If the instruction for the first PRDCH receive operation is included, then the first PRDCH receive operation is executed. For example, if the... If the instruction for the second PRDCH receive operation is included, then the second PRDCH receive operation is executed.

[0418] ●If the Type 1 R2D reception condition is met, then the first PRDCH reception operation is performed.

[0419] ●If the type 2 R2D reception condition is met, then the second PRDCH reception operation is performed.

[0420] ●According to the above The system executes corresponding operations based on the indication information provided. For example, based on a first indication in the indication information, the first PRDCH receiving operation is executed. Similarly, based on a second indication in the indication information, the second PRDCH receiving operation is executed.

[0421] In some respects, when performing the first PRDCH receive operation, it is at least partially based on the following: The indication information in the document determines that the aforementioned (or, the aforementioned) The information is received by PRDCH, for example, as described above. (or, the aforementioned) The information may include at least part of, or all of, the following: (or, the aforementioned) The end time of the above (or, the aforementioned) The number of chips, the size of the transport block corresponding to the first MAC PDU, and the size of the transport block corresponding to the second MAC PDU.

[0422] In some respects, in a method according to some embodiments of the present disclosure shown in FIG1, "physical layer" may refer to the physical layer of the device.

[0423] In some respects, in a method according to some embodiments of the present disclosure shown in FIG1, "higher layer" may refer to a higher layer of the device.

[0424] In some aspects, some or all of the steps (or portions thereof) of a method according to some embodiments of the present disclosure shown in FIG1, which are performed by the physical layer, can constitute a physical layer process. For example, steps S101, S102, and S105 can constitute a physical layer process. As another example, steps S102, S103, S104, and S105 can constitute a physical layer process.

[0425] In some aspects, some or all of the steps (or portions thereof) of a method according to some embodiments of the present disclosure shown in FIG1, which are performed by a higher layer (e.g., a MAC layer), can constitute a higher-level (e.g., MAC layer) process. For example, steps S103 and S104 can constitute a higher-level (e.g., MAC layer) process.

[0426] In some aspects, in a method according to some embodiments of the present disclosure shown in FIG1, a second higher layer determines whether a Type 1 ID is associated with the device.

[0427] In some aspects, in a method according to some embodiments of the present disclosure shown in FIG1, the second higher layer determines whether there is one (or at least one) Type 1 ID associated with the device in a set of Type 1 IDs.

[0428] In some aspects, in a method according to some embodiments of the present disclosure shown in FIG1, a higher layer of the second higher layer determines whether a Type 1 ID is associated with the device (e.g., based on the Type 1 ID provided by the former to the latter) and indicates the determination result to the second higher layer.

[0429] In some aspects, in a method according to some embodiments of the present disclosure shown in FIG1, a higher layer of the second higher layer determines whether there is one (or at least one) Type 1 ID associated with the device in a set of Type 1 IDs (e.g., based on the set of Type 1 IDs provided by the former to the latter), and indicates the determination result to the second higher layer.

[0430] In some aspects, in a method according to some embodiments of the present disclosure shown in FIG1, "message type" may refer to a message type defined at the physical layer, or a message type defined at the MAC layer, or a message type defined at a higher layer than the MAC layer.

[0431] In some aspects, in a method according to some embodiments of the present disclosure shown in FIG1, the “MAC header” may be replaced by a “MAC subheader”.

[0432] In some aspects, in a method according to some embodiments of the present disclosure shown in FIG1, "MAC PDU" can be replaced with "MAC subPDU", and correspondingly, "first MAC subPDU" and "second MAC subPDU" can be contained in the same MAC PDU (i.e., the... It is contained in a MAC PDU.

[0433] Thus, as shown in Figure 1, this disclosure provides a method in which, during PRDCH reception, the physical layer first receives the first part of a MAC PDU carried in the PRDCH and provides this first part to the MAC layer (or even a higher layer than the MAC layer). The latter then determines whether to continue receiving the PRDCH based on the Type 1 ID, message type, etc., in the first part, and in conjunction with the current device process steps. On the one hand, this method simplifies the design of the physical layer by placing content related to higher-level services, such as the Type 1 ID and message type, at a higher layer, allowing it to evolve continuously without affecting the physical layer, thereby improving the design and operational efficiency of A-IoT communication. On the other hand, this method allows the device to consume very little energy on R2D transmissions it does not want to receive, thus maintaining the operation of the entire A-IoT system with extremely low power consumption.

[0434] The following description, in conjunction with FIG2, illustrates a method performed by a device according to some embodiments of the present disclosure.

[0435] Figure 2 shows a flowchart corresponding to a method performed by a device according to some embodiments of the present disclosure.

[0436] As shown in Figure 2, in some embodiments of this disclosure, the steps performed by the device may include some or all of the following: step S201 and step S202.

[0437] Specifically, in step S201, an R2D transmission is received (e.g., denoted as...). ).

[0438] In some respects, the R2D transmission is sent. The reader (e.g., denoted as rdr0) can be a base station or an IUE.

[0439] In some respects, the R2D transmission The message may carry a higher-level (e.g., a higher-level protocol layer with the MAC layer as the reference) R2D message (e.g., referred to as the "first R2D message"). For example, the first R2D message may correspond to a higher-level "command" (e.g., a "read" command).

[0440] In some respects, the first R2D message can be used to trigger (or schedule) a D2R transmission (e.g., denoted as...). ), wherein the D2R transmission It can be used to carry one of one or more segments of a higher-level (e.g., a higher-level protocol layer with the MAC layer as the reference protocol layer) D2R message (e.g., referred to as the "first D2R message"), wherein,

[0441] ● In some aspects, within the one or more segments (e.g., including the last segment of the first D2R message, or excluding the last segment of the first D2R message), the size of each segment may be equal to a "set of first D2R segment sizes" (e.g., denoted as...). One of the elements in ).

[0442] ● In some aspects, the size of all segments (e.g., including the last segment of the first D2R message, or excluding the last segment of the first D2R message) may be equal to the size of the set. The same element in.

[0443] ●In some respects, within the one or more segments, the size of two distinct segments can be equal to the set, respectively. Two distinct elements in the set, or both of them can be equal to the set. The same element in.

[0444] In some respects, the R2D transmission The R2D control information can be used, at least in part, to determine whether the first D2R message has been fully received by the rdr0. In some aspects, if the first D2R message has been fully received by the rdr0, the D2R transmission may not need to be sent. In some respects, if the first D2R message has been fully received by the rdr0, then the sent D2R transmission... It is possible to omit any segment of the first D2R message.

[0445] In some respects, the set It can be a predefined or configured collection.

[0446] In some respects, the set Each element in the set can correspond to a TBS that can be used for D2R transmission (e.g., the element can be determined based on the TBS). For example, the set Each element in can be based on the set One of the corresponding elements is determined.

[0447] In some respects, the set It can be transmitted at least in part according to the D2R. The size of the transport block carried in (i.e., TBS, for example denoted as ) The transport block is determined by (a number of bits), wherein, for example, the transport block may correspond to a MAC PDU, which may contain a segment of the first D2R message (e.g., denoted as...). In some respects, the aforementioned It can be transmitted in R2D The R2D control information carried in the system indicates this.

[0448] In some respects, the stated Size (e.g., denoted as) (bits) can be at least partially based on the above. Sure.

[0449] In some respects, for the set Each element in the set can be predefined or configured with a set of segment sizes. For example, the set... It can be for the A predefined or configured set of segment sizes.

[0450] In some aspects, the R2D control information may include a "first segment offset" indication (e.g., denoted as...). ), wherein, the It can be a satisfaction Integers.

[0451] In some respects, the stated This can represent the number of segments corresponding to the first D2R message that rdr0 has successfully received (e.g., the number of consecutive segments starting from the first segment, i.e., segment numbered 0). For example, This could mean that rdr0 has not yet successfully received any segment corresponding to the first D2R message; for example, This can indicate that rdr0 has successfully received the segment with number 0 corresponding to the first D2R message; for example, This could indicate that rdr0 has successfully received the segment numbered 0 and the segment numbered 1 corresponding to the first D2R message; etc.

[0452] In some aspects, the R2D control information may include a "second segment offset" indication (e.g., denoted as...). ), wherein, the It can be a satisfaction Integers.

[0453] In some respects, the stated It can be represented by a "first reference segment size" (e.g., denoted as...). The number of segments of the first D2R message that the rdr0 has successfully received, determined by the segment size (in bits).

[0454] In some respects, the stated It can correspond to a predefined or configured parameter.

[0455] In some respects, the stated It can be at least in part based on the above Determined. For example, the... It can be for the A predefined or configured reference segment size.

[0456] In some respects, the stated This can be indicated in the R2D control information (e.g., physical layer R2D control information; or, for example, higher layer R2D control information). For example, the It can be specified as a predefined or configured set (e.g., denoted as...). The index in ).

[0457] In some respects, the set It can be the set

[0458] In some respects, the set It can be at least in part based on the above Sure.

[0459] In some respects, the stated It can be the set and a predefined or configured value. For example, the It can be the set The smallest element in.

[0460] In some respects, the stated This can be determined, at least in part, based on the size of the transport block carried by the D2R transmission carrying the first segment (i.e., segment number 0) of the first D2R message. For example, the... It can be a reference segment size that is predefined or configured for the size of the transport block.

[0461] In addition, in step S202, one or more operations related to D2R segmentation are performed.

[0462] For example, determine the number of bits of the first D2R message that has been successfully received by the rdr0 (e.g., denoted as...). (bits), or with the above Relevant information. Specifically, for example, the stated It can be equal to what the device has already sent. Each segment (numbered sequentially as 0, 1, ..., and ...) The sum of the sizes of the individual (e.g., expressed in bits), where, as a special case, for The It can be equal to 0. For example, the aforementioned... It can satisfy one of the following conditions:

[0463] ●

[0464] ●

[0465] ●

[0466] For example, determining whether the first D2R message has been received completely (i.e., whether rdr0 has received all bits of the first D2R message completely, or whether rdr0 has received all segments of the first D2R message completely). Specifically, for example, if the Type 1 D2R segmentation condition is met, it means that the first D2R message has been received completely (or the first D2R message has been fully acknowledged); or if the Type 1 D2R segmentation condition is not met, it means that the first D2R message has not been received completely (or the first D2R message has not been fully acknowledged). In some aspects, the Type 1 D2R segmentation condition may at least partially include a combination of one or more of the following in an AND or OR manner (e.g., the result of combining one or more items in an AND manner is combined with the result of combining another one or more items in an AND manner in an OR manner; or, the result of combining one or more items in an OR manner is combined with the result of combining another one or more items in an OR manner in an AND manner; etc.):

[0467] ●The Equal to the size of the first D2R message (e.g., denoted as...) (bits).

[0468] ● equal to the

[0469] ● Greater than the

[0470] ● Greater than or equal to the

[0471] For example, determining whether to send (transmit) the specified message. Specifically, for example, if the first D2R message has already been received completely, then the [missing information] is not sent. For example, if the first D2R message has been received completely, then the following message is sent: And the It does not carry any segment of the first D2R message. For example, if the first D2R message has not yet been fully received, then the following is sent: And the The first segment carrying the first D2R message that has not yet been acknowledged.

[0472] For example, when sending the aforementioned In the case of determining the The content carried. Specifically, for example, if the first D2R message has been received completely, then the... The carried MAC PDU does not contain any higher-layer (i.e., higher-layer protocol layers referenced by the MAC layer) data. For example, if the first D2R message has been received completely, then the... It does not carry any MAC PDU. For example, if the first D2R message has not yet been fully received, then the... The start bit of the segment carried can be the bit indexed in the first D2R message. The bits (assuming the index of the first bit in the first D2R message is 0). For example, if the first D2R message has not yet been fully received, then the... The start bit of the segment carried can be the bit indexed in the first D2R message. The first bit in the first D2R message is indexed as 0.

[0473] In some respects, the method shown in FIG2, according to some embodiments of the present disclosure, is performed by the MAC layer of the device.

[0474] Thus, as shown in Figure 2, this disclosure provides a method in which the size of the indication information for segment retransmission is reduced by indicating the number of segments successfully received (e.g., the number of segments actually received; or, for example, the number of segments determined based on a reference segment size) in the R2D transmission of a segmented higher-level R2D message, thereby improving communication efficiency in the case of segmented higher-level D2R messages.

[0475] The following description, with reference to FIG3, illustrates a method performed by a device according to some embodiments of the present disclosure.

[0476] Figure 3 shows a flowchart corresponding to a method performed by a device according to some embodiments of the present disclosure.

[0477] As shown in Figure 3, in some embodiments of this disclosure, the steps performed by the device may include some or all of the following: step S301, step S302, step S303, and step S304.

[0478] Specifically, in step S301, a first D2R transmission is sent (e.g., denoted as...). ), wherein the D2R transmission It can carry an A-IoT Msg1 (for example, denoted as...) In some respects, the aforementioned A variable may contain at least a partial RID (e.g., denoted as RID). ).

[0479] Furthermore, in step S302, a first R2D transmission is received (e.g., denoted as...). ), wherein the R2D transmission The middle may at least partially contain a function for responding to the above. RAR (e.g., denoted as RAR) ).

[0480] In some respects, the stated It can be contained in a "RAR container", which in some respects can be a MAC CE, or a MAC subPDU, or a MAC subheader, or a container defined in other ways.

[0481] In some respects, the R2D transmission The carried MAC PDU can be a "Type 1 MAC PDU", wherein, in some respects, a Type 1 MAC PDU can at least partially contain one or more of the following:

[0482] ● One or more RAR containers.

[0483] ● One or more "Msg3-ACK containers".

[0484] Specifically, for example, the R2D transmission The carried MAC PDU may contain one or more RAR containers and zero or one or more Msg3-ACK containers, wherein one of the one or more RAR containers contains the

[0485] In some respects, a Msg3-ACK container can be a MAC CE, or a MAC subPDU, or a container defined in other ways.

[0486] In some respects, a RAR container may contain at least some or all of the following: a container type, a RAR, an RID, and an AS ID, wherein,

[0487] ● In some respects, the container type can be used to indicate that the container is a RAR container.

[0488] ● In some aspects, the RAR can be used at least partially to schedule a D2R transmission, wherein the D2R transmission can be used at least partially to carry an A-IoT Msg3, and the RAR can be used at least partially to determine some or all of the following: time-domain and / or frequency-domain resources of the D2R transmission, information related to the channel coding rate, and indication information related to D-MIA, etc. For example, the A device carrying A-IoT Msg3 (e.g., denoted as Msg3) can be used to schedule the device. D2R transmission (e.g., denoted as) ).

[0489] ● In some respects, the RID may be the RID contained in the A-IoT Msg1 responded to by the RAR (or the RAR container).

[0490] ● In some respects, the RID may be referred to as the RID associated with the RAR (or the RAR container).

[0491] ● In some respects, the RID can be used at least in part to identify the RAR (or the RAR container). For example, the device can determine which of the one or more RARs is the RAR based at least in part on some or all of the following: The and the D2R transmission The time-domain and / or frequency-domain resources occupied (e.g., referred to as access occupancy).

[0492] ●In some respects, as stated in the above The AS ID assigned to the device (e.g., denoted as) ) can be equal to the stated Or it may not be equal to the stated...

[0493] Furthermore, in step S303, a second D2R transmission is sent (i.e., the... ), wherein the D2R transmission It can carry an A-IoT Msg3 (i.e., the aforementioned) In some respects, the aforementioned The device ID (e.g., denoted as) may at least partially contain the device ID of the device. ).

[0494] In addition, in step S304, a second R2D transmission is received (e.g., denoted as...). For example, the R2D transmission It can carry the above The confirmation, that is, the The corresponding Msg3-ACK (e.g., denoted as) ).

[0495] In some respects, the R2D transmission The carried MAC PDU can be a Type 1 MAC PDU, and correspondingly, the MAC PDU can contain one or more Msg3-ACK containers, and zero or one or more RAR containers, wherein one of the one or more Msg3-ACK containers contains the...

[0496] In some respects, a Msg3-ACK container may at least partially contain one or all of the following: a container type and a Msg3-ACK, wherein, in some respects, the container type may be used to indicate that the container is a Msg3-ACK container.

[0497] In some respects, a Msg3-ACK may at least partially contain an "AID" (acknowledgement ID), where,

[0498] ● In some respects, the AID can be an integer.

[0499] ● In some aspects, the AID can be used at least partially to identify (or associate with) some or all of the following: the A-IoT Msg3 confirmed by the AID, the device that sent the A-IoT Msg3 confirmed by the AID, and the Msg3-ACK container containing the Msg3-ACK. For example, the The included AID (e.g., denoted as) ) can be used to identify (or associate) the aforementioned Alternatively, it can be used to identify (or associate) the device, or it can be used to identify

[0500] (Or, related) includes the above The Msg3-ACK container.

[0501] ● In some respects, the AID may be determined at least in part based on some or all of the following: the device ID in the A-IoT Msg3 confirmed by the Msg3-ACK, an AS ID (e.g., the AS ID assigned in the RAR used to schedule the A-IoT Msg3), and an RID (e.g., the RID contained in the corresponding A-IoT Msg1).

[0502] For example, the It can be determined, at least in part, based on some or all of the following: The and the Specifically, for example, the It can be determined based on one of the following:

[0503] ●

[0504] ●

[0505] ●

[0506] ●The It is the aforementioned A function. For example, the... It is the aforementioned The integer corresponding to one or more MSBs; for example, the... It is the aforementioned The integer corresponding to one or more LSBs; for example, the... Therefore, the above The output of a hash function is given as a parameter, where, for example, a hash function can be a function used to map input data of arbitrary length to output data of fixed length.

[0507] ●The It is the aforementioned and stated A function. For example, the... Therefore, the above and stated The output of a hash function with parameters.

[0508] In some respects, the method shown in FIG3, according to some embodiments of the present disclosure, is performed by the MAC layer of the device.

[0509] Thus, as shown in Figure 3, this disclosure provides a method in which RAR and acknowledgment of A-IoT Msg3 (Msg3-Ack) are multiplexed in the same MAC PDU format. This allows the reader to retransmit one or more A-IoT Msg2s while acknowledging one or more successfully received A-IoT Msg3s in the same R2D transmission, thereby shortening the total time for inventory counting and other tasks for a large number of devices and improving the communication efficiency of the A-IoT system.

[0510] Variations

[0511] The following uses Figure 4 to illustrate a device that can perform the method described in detail above as a variation of this disclosure.

[0512] Figure 4 is a block diagram illustrating the device involved in this disclosure.

[0513] As shown in Figure 4, the device NODE 40 includes a processor 401 and a memory 402. The processor 401 may include, for example, a microprocessor, a microcontroller, an embedded processor, etc. The memory 402 may include, for example, volatile memory (such as random access memory, RAM), a hard disk drive (HDD), non-volatile memory (such as flash memory), or other memory. Program instructions are stored on the memory 402. When executed by the processor 401, these instructions can perform the methods described in detail herein, executed by the device.

[0514] The embodiments of this disclosure can be implemented on a computer program product. More specifically, the computer program product is one that has a computer-readable medium on which computer program logic is encoded, which, when executed on a computing device, provides related operations to implement the above-described technical solutions of this disclosure. When executed on at least one processor of a computing system, the computer program logic causes the processor to perform the operations (methods) described in the embodiments of this disclosure. This configuration of the disclosure is typically provided as software, code, and / or other data structures set or encoded on a computer-readable medium such as an optical medium (e.g., CD-ROM), floppy disk, or hard disk, or other media such as firmware or microcode on one or more ROM, RAM, or PROM chips, or downloadable software images, shared databases, etc., in one or more modules. The software or firmware or such configuration can be installed on a computing device to cause one or more processors in the computing device to perform the technical solutions described in the embodiments of this disclosure.

[0515] Computer-executable instructions or programs running on a device according to this disclosure may be programs that enable a computer to perform the functions of embodiments of this disclosure by controlling a central processing unit (CPU). The program or information processed by the program may be temporarily stored in volatile memory (such as random access memory, RAM), hard disk drive (HDD), non-volatile memory (such as flash memory), or other memory systems.

[0516] Computer-executable instructions or programs for implementing the functions of the embodiments of this disclosure can be recorded on a computer-readable storage medium. The corresponding functions can be implemented by causing a computer system to read and execute the programs recorded on the recording medium. The term "computer system" herein can refer to a computer system embedded in the device, and may include an operating system or hardware (such as peripheral devices). "Computer-readable storage medium" can be a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a short-time dynamic program storage medium, or any other computer-readable recording medium.

[0517] Various features or functional modules of the devices used in the above embodiments can be implemented or executed by circuits (e.g., monolithic or multi-chip integrated circuits). Circuits designed to perform the functions described in this specification may include general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or any combination of the above devices. A general-purpose processor may be a microprocessor, or any existing processor, controller, microcontroller, or state machine. The circuits described above may be digital circuits or analog circuits. In cases where advancements in semiconductor technology have led to new integrated circuit technologies that replace existing integrated circuits, one or more embodiments of this disclosure may also be implemented using these new integrated circuit technologies.

[0518] It should be understood that the above embodiments of this disclosure can be implemented by software, hardware, or a combination of both. For example, the various components inside the base station and equipment in the above embodiments can be implemented by a variety of devices, including but not limited to: analog circuit devices, digital circuit devices, digital signal processing (DSP) circuits, programmable processors, application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), programmable logic devices (CPLDs), and so on.

[0519] The methods and related devices of this disclosure have been described above in conjunction with preferred embodiments. Those skilled in the art will understand that the methods shown above are merely exemplary, and the various embodiments described above can be combined with each other without contradiction. The methods of this disclosure are not limited to the steps and sequence shown above. The network nodes and devices shown above may include more modules, such as modules that can be developed or will be developed in the future for use in network nodes or terminal nodes, etc. The various identifiers shown above are merely exemplary and not limiting, and this disclosure is not limited to the specific information elements exemplified by these identifiers. Those skilled in the art can make many variations and modifications based on the teachings of the illustrated embodiments.

[0520] Those skilled in the art should understand that any set is a subset of itself; the empty set is a subset of any set; parts or all of a mathematical expression, mathematical equation, or mathematical inequality can be simplified, transformed, or rewritten to a certain extent, such as merging constant terms, swapping two addition terms, swapping two multiplication terms, changing the sign of a term and moving it from the left to the right of the equation or inequality, or changing the sign of a term and moving it from the right to the left of the equation or inequality, etc.; the mathematical expression, mathematical equation, or mathematical inequality before and after simplification, transformation, or rewriting can be considered equivalent.

[0521] Furthermore, this disclosure is not limited to the embodiments described above. Although various examples of the embodiments have been described, this disclosure is not limited thereto. For example, this disclosure can be applied to fixed or non-mobile electronic devices installed indoors or outdoors that can be used as communication nodes, such as audio and / or video equipment, kitchen equipment, cleaning equipment, air conditioners, office equipment, vending machines, and other household appliances.

[0522] As described above, embodiments of this disclosure have been described in detail with reference to the accompanying drawings. However, the specific structure is not limited to the above embodiments, and this disclosure also includes any design modifications that do not depart from the spirit of this disclosure. Furthermore, various modifications can be made to this disclosure within the scope of the claims, and embodiments obtained by appropriately combining the technical means disclosed in different embodiments are also included within the technical scope of this disclosure. In addition, components with the same effects described in the above embodiments can be substituted for each other.

Claims

A method performed by a device, characterized in that, include: The reader receives a device R2D timing acquisition signal R-TAS, wherein the R-TAS signal consists of a start indicator section (SIP) and a clock acquisition section (CAP), and the R-TAS signal is used to indicate the start of the physical R2D channel PRDCH, which immediately follows the R-TAS signal; and Receive the PRDCH, wherein the size of the transport block TB carried by the PRDCH is determined to be a value indicated by a higher layer. A device characterized in that, include: processor; as well as Memory, which stores instructions The instructions are executed by the processor according to the method described in claim 1.

Images