Signal transmission method, apparatus and system

Abstract

Provided in the embodiments of the present application are a signal transmission method, apparatus and system. The method comprises: a first device receiving, on a zeroth resource, message 0 (msg0) sent by a second device, wherein message 0 is at least used for instructing or triggering the first device to implement random access, or instructing the first device to send message 1 (msg1); the first device sending, on a first resource, message 1 (msg1) to the second device, wherein message 1 is at least used for responding to message 0; the first device receiving, on a second resource, message 2 (msg2) sent by the second device, wherein message 2 is at least used for responding to message 1, and the first device sends message 1 on the first resource at least by means of backscattering a first waveform.

Description

Signal transmission methods, devices and systems Technical Field

[0001] The embodiments of this application relate to the field of communication technology. Background Technology

[0002] From the early days of 2G to 4G, cellular mobile communication systems primarily served mobile phones—human-held mobile terminal devices. With the rapid development of mobile internet and the Internet of Things (IoT), from the later stages of 4G to the present, the evolution of cellular mobile communication technology has considered and supported increasingly diverse IoT application scenarios. Correspondingly, more types of IoT devices have been supported and implemented in actual network deployments and service applications, such as eMTC (enhanced Machine-Type Communication) devices, NB-IoT (Narrow Band Internet of Things) devices, and RedCap (Reduced Capability) devices. With the increasing diversity of IoT terminal devices, cellular mobile systems have gained increasingly stronger capabilities in providing services and offering services to vertical industries.

[0003] Digital mobile communication has evolved through 2G, 3G, 4G, and now 5G, effectively meeting people's needs in voice communication, digital mobile communication, and mobile broadband networking. However, with social and economic development, the demand for Internet of Things (IoT) communication is gradually emerging. To meet the needs of IoT communication, 3GPP (3rd Generation Partnership Project) has defined a series of IoT technology standards, including MTC, NB-IoT, and RedCap.

[0004] While existing IoT technology standards have met the requirements of low cost, low power consumption, and massive connectivity for IoT terminal devices, there are still many scenarios where IoT communication needs cannot be met using these standards. These include extreme working environments that hinder the maintenance of IoT terminal devices, and the need for extremely small size and low cost terminal devices. How 3GPP can support these IoT terminal device requirements within cellular systems is a problem that needs to be addressed.

[0005] It should be noted that the above introduction to the technical background is only for the purpose of providing a clear and complete explanation of the technical solutions of this application and facilitating understanding by those skilled in the art. It should not be assumed that these technical solutions are known to those skilled in the art simply because they have been described in the background section of this application.

[0006] Summary of the Invention

[0007] The inventors discovered that RFID (Radio Frequency Identification) technology is a widely used communication technology that can identify specific targets and read / write related data in a non-contact manner. The advantages of RFID systems include low tag cost and small size, making them frequently used in various applications such as logistics information collection, retail, libraries, and identity verification. One disadvantage of RFID systems is the limited information reading range (based on the wireless signal communication range) of RFID tags. Using manual handheld tag readers can result in high labor costs, which may be the main expense. Using dedicated RFID gateways to read and manage RFID tags requires significant deployment costs. Furthermore, the simple logical architecture of RFID systems makes it difficult to effectively coordinate with interference in radio wave transmission, resulting in generally low system capacity and spectrum utilization efficiency.

[0008] Compared to RFID systems, 3GPP's 5G systems support tag-based terminal devices, allowing for the reuse of existing base stations and leveraging existing cellular networks to support industry applications based on this type of terminal, thereby effectively reducing deployment and usage costs. 3GPP's 5G systems can provide reliable authentication, network coordination, and accurate and stable terminal device management mechanisms, and can also optimize the network to improve system capacity and spectrum utilization efficiency.

[0009] As a new type of IoT terminal in 5G systems, tagged IoT devices are severely limited by cost. Their capabilities are significantly weaker than those of ordinary smartphones and other IoT devices supported by existing cellular mobile communication systems. For example, tagged IoT devices have extremely limited stored energy and cannot reuse existing 5G mechanisms for communication between terminal and network devices. Therefore, how to efficiently utilize the stored energy of tagged IoT devices to communicate with network devices is a problem that needs to be solved.

[0010] Furthermore, due to cost constraints, tag-based terminal devices have extremely limited energy storage, typically using a capacitor to store energy, which is then consumed during communication. Therefore, a key challenge is how to ensure performance while conserving energy and communicating with network devices (e.g., where and when to receive / send data) under these energy-constrained conditions.

[0011] To address at least one of the above-mentioned problems, embodiments of this application provide a signal transmission method, apparatus, and system.

[0012] According to one aspect of the embodiments of this application, a signal transmission method is provided, applied to a first device, the method comprising:

[0013] The first device receives message 0 (msg0) sent by the second device on the zeroth resource. Message 0 is used at least to instruct or trigger the first device to implement random access, or to instruct the first device to send message 1 (msg1).

[0014] The first device sends message 1 (msg1) to the second device on the first resource, the message 1 being used at least in response to message 0;

[0015] The first device receives message 2 (msg2) sent by the second device on the second resource, the message 2 being used at least in response to message 1;

[0016] The first device sends message 1 on the first resource by backscattering the first waveform.

[0017] According to another aspect of the embodiments of this application, a signal transmission device is provided, configured in a first device, the device comprising:

[0018] The receiving unit receives message 0 (msg0) sent by the second device on the zeroth resource. Message 0 is used at least to instruct or trigger the first device to implement random access, or to instruct the first device to send message 1 (msg1).

[0019] A sending unit that sends message 1 (msg1) to the second device on a first resource, the message 1 being used at least in response to message 0;

[0020] The receiving unit receives message 2 (msg2) sent by the second device on the second resource, and message 2 is used at least in response to message 1;

[0021] The sending unit transmits message 1 on the first resource by backscattering the first waveform at least once.

[0022] According to another aspect of the embodiments of this application, a signal transmission method is provided, applied to a second device, the method comprising:

[0023] The second device sends message 0 to the first device, which is at least used to instruct or trigger the first device to implement random access, or to instruct the first device to send message 1 (msg1);

[0024] The second device receives message 1 from one or more of the first devices, the message 1 being used at least in response to message 0;

[0025] The second device sends one or more messages 2 on one or more second resources, wherein the one or more messages 2 are at least used in response to the one or more messages 1;

[0026] The first device transmits message 1 on the first resource by backscattering the first waveform at least once.

[0027] According to another aspect of the embodiments of this application, a signal transmission device is provided, configured in a second device, the device comprising:

[0028] A sending unit sends message 0 to a first device, the message 0 being used at least to instruct or trigger the first device to implement random access, or to instruct the first device to send message 1 (msg1);

[0029] A receiving unit receives message 1 from one or more of the first devices, the message 1 being used at least in response to message 0;

[0030] The sending unit also sends one or more messages 2 on one or more second resources, the one or more messages 2 being used at least in response to the one or more messages 1;

[0031] The first device transmits message 1 on the first resource by backscattering the first waveform at least once.

[0032] According to another aspect of the embodiments of this application, a communication system is provided, including the first device and the second device of the foregoing embodiments.

[0033] One of the beneficial effects of this application embodiment is that: the first device transmits message 1 on the first resource at least by backscattering the first waveform, thereby effectively saving the energy consumption of the first device, such as eliminating the need for uplink carrier signal generation circuitry, etc., enabling the first device to maintain communication with the second device even when using a low-cost energy storage device. Furthermore, even if the first device samples a low-cost clock source to generate a low-precision clock, the first device can still maintain communication with the network device.

[0034] Specific embodiments of this application are disclosed in detail with reference to the following description and accompanying drawings, indicating how the principles of this application can be adopted. It should be understood that the embodiments of this application are not limited in scope. Within the spirit and scope of the appended claims, embodiments of this application include many changes, modifications, and equivalents.

[0035] Features described and / or illustrated for one embodiment may be used in the same or similar manner in one or more other embodiments, combined with features in other embodiments, or substituted for features in other embodiments.

[0036] It should be emphasized that the term "including / comprises" as used herein refers to the presence of a feature, whole, step, or component, but does not exclude the presence or addition of one or more other features, wholes, steps, or components. Attached Figure Description

[0037] The elements and features described in one drawing or embodiment of this application may be combined with elements and features shown in one or more other drawings or embodiments. Furthermore, in the drawings, similar reference numerals denote corresponding parts in several drawings and can be used to indicate corresponding parts used in more than one embodiment.

[0038] Figure 1 is a schematic diagram of a communication system according to an embodiment of this application;

[0039] Figure 2 is another schematic diagram of the communication system according to an embodiment of this application;

[0040] Figure 3 is another schematic diagram of the communication system according to an embodiment of this application;

[0041] Figure 4 is a schematic diagram of a signal transmission method according to an embodiment of this application;

[0042] Figure 5 is a schematic diagram of an example of a time point associated with message 0;

[0043] Figure 6 is a schematic diagram of another example of a time point related to message 0;

[0044] Figure 7 is a schematic diagram of another example of a time point related to message 0;

[0045] Figure 8 is a schematic diagram of an example of a time point related to message 1;

[0046] Figure 9 is a schematic diagram of an example of a time point and message 2;

[0047] Figure 10 is a schematic diagram of another example of a time point and message 2 related;

[0048] Figure 11 is a schematic diagram of an example of one or more time points related to message 0;

[0049] Figure 12 is a schematic diagram of another example of one or more time points related to message 0;

[0050] Figure 13 is a schematic diagram of another example of more than one time point and message 0;

[0051] Figure 14 is a schematic diagram of an example of one or more time points related to message 1;

[0052] Figure 15 is a schematic diagram of an example of one or more time points related to message 2;

[0053] Figure 16 is a schematic diagram of another example of a time point and message 2 related to more than one time point;

[0054] Figure 17 is a schematic diagram of a signal transmission method according to an embodiment of this application;

[0055] Figure 18 is a schematic diagram of a signal transmission device according to an embodiment of this application;

[0056] Figure 19 is a schematic diagram of a signal transmission device according to an embodiment of this application;

[0057] Figure 20 is a schematic diagram of information interaction between the first device and the second device according to an embodiment of this application;

[0058] Figure 21 is a schematic diagram of a terminal device according to an embodiment of this application;

[0059] Figure 22 is a schematic diagram of a network device according to an embodiment of this application. Detailed Implementation

[0060] Referring to the accompanying drawings, the foregoing and other features of this application will become apparent from the following description. Specific embodiments of this application are specifically disclosed in the description and drawings, illustrating partial implementations in which the principles of this application may be employed. It should be understood that this application is not limited to the described embodiments; rather, it includes all modifications, variations, and equivalents falling within the scope of the appended claims.

[0061] In the embodiments of this application, the terms "first," "second," etc., are used to distinguish different elements by name, but do not indicate the spatial arrangement or chronological order of these elements, and these elements should not be limited by these terms. The term "and / or" includes any one or more of the terms listed in association and all combinations thereof. The terms "comprising," "including," "having," etc., refer to the presence of the stated features, elements, components, or assemblies, but do not exclude the presence or addition of one or more other features, elements, components, or assemblies.

[0062] In the embodiments of this application, the singular forms "a," "the," etc., including the plural forms, should be broadly understood as "a kind" or "a class" rather than limited to the meaning of "an." Furthermore, the term "the" should be understood to include both the singular and plural forms, unless the context explicitly indicates otherwise. Additionally, the term "according to" should be understood as "at least partially based on…," and the term "based on" should be understood as "at least partially based on…," unless the context explicitly indicates otherwise.

[0063] In the embodiments of this application, the term "communication network" or "wireless communication network" may refer to a network that conforms to any of the following communication standards, such as Long Term Evolution (LTE), LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), Ambient IoT, etc.

[0064] Furthermore, communication between devices in a communication system can be carried out according to communication protocols at any stage, including but not limited to the following communication protocols: 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G and 5G, New Radio (NR), future 6G, etc., and / or other currently known or future communication protocols.

[0065] In this application embodiment, the term "network device" refers, for example, to a device in a communication system that connects a terminal device to a communication network and provides services to that terminal device. Network devices may include, but are not limited to, devices such as: base stations (BS), access points (AP), transmission reception points (TRP), broadcast transmitters, mobile management entities (MME), gateways, servers, radio network controllers (RNC), base station controllers (BSC), etc. Furthermore, network devices may also include readers or interrogators used for AIoT, but this application is not limited to these devices.

[0066] In the above embodiments, base stations may include, but are not limited to: Node B (NodeB or NB), evolved Node B (eNodeB or eNB), and 5G base stations (gNB), IAB hosts (Donor), etc. They may also include Remote Radio Heads (RRHs), Remote Radio Units (RRUs), relays, or low-power nodes (e.g., femeto, pico, etc.), readers, or interrogators. The term "base station" can include some or all of their functions, and each base station can provide communication coverage to a specific geographical area. The term "cell" can refer to a base station and / or its coverage area, depending on the context in which the term is used.

[0067] In the embodiments of this application, the terms "User Equipment" (UE) or "Terminal Equipment" (TE) refer, for example, to a device that accesses a communication network and receives network services through a network device. A terminal device can be fixed or mobile, and may also be referred to as a mobile station (MS), terminal, subscriber station (SS), access terminal (AT), tag, etc.

[0068] In the above embodiments, the terminal device may include, but is not limited to, the following devices: cellular phone, personal digital assistant (PDA), wireless modem, wireless communication device, handheld device, machine communication device, laptop computer, cordless phone, smartphone, smartwatch, digital camera, tag, device attached to or related to an item (e.g., for item management), etc.

[0069] For example, in scenarios such as the Internet of Things (IoT), terminal devices can also be machines or devices for monitoring or measurement, including but not limited to: machine-type communication (MTC) terminals, vehicle communication terminals, device-to-device (D2D) terminals, machine-to-machine (M2M) terminals, ambient IoT devices, etc.

[0070] Furthermore, the terms "network side" or "network equipment side" refer to one side of the network, which can be a base station or include one or more network devices as described above. The terms "user side," "terminal side," or "terminal equipment side" refer to the side of the user or terminal, which can be a UE or include one or more terminal devices as described above. Unless otherwise specified, "equipment" can refer to either network equipment or terminal equipment.

[0071] RFID systems are solutions for the large-scale, low-cost Internet of Things (IoT) terminal devices. RFID systems have wide applications. The advantages of RFID systems include low tag cost and low price. RFID tags are small, with fewer restrictions on the size and material of the items they can be used with, making them easy to apply to various item management and tracking scenarios. Although RFID tags are inexpensive, the deployment and usage costs of RFID systems are higher than wide-area commercial networks. In terms of deployment, RFID systems are typically deployed locally, with dedicated networks, making it difficult to effectively amortize deployment costs. In terms of usage, if a manual handheld tag reader solution is used, labor costs may become the main operating expense and are difficult to reduce; if dedicated RFID ports or gateways are used for reading and management, deployment costs will increase significantly. Furthermore, the simple logical architecture of RFID systems and loose wireless resource management, such as the difficulty in effectively coordinating interference in radio wave transmission, generally result in lower system capacity and spectrum utilization efficiency.

[0072] Compared to existing RFID systems, leveraging existing commercial mobile cellular networks (such as LTE and 5G NR systems) to support industry applications requiring tag-based IoT devices can effectively reduce deployment costs, thereby lowering the barrier to entry for this type of IoT device deployment. Furthermore, existing commercial mobile cellular networks (such as LTE and 5G NR systems) offer significantly better network security and wireless resource management than existing RFID systems. Taking 5G systems as an example, 5G can provide high-security authentication, network coordination, and accurate and stable terminal device management mechanisms, effectively reducing labor costs and thus lowering the overall cost of using this type of IoT. It can also optimize the network to improve system capacity and spectrum utilization efficiency. This reduction in deployment and usage costs can effectively promote the application of tag-based IoT devices in business management and industrial manufacturing, accelerate the digitalization process of related industries, improve production efficiency, and ultimately contribute more effectively to social development.

[0073] As a new type of IoT terminal in 5G systems, tagged IoT devices are severely constrained by cost. Their hardware capabilities are significantly weaker than traditional terminal devices, such as smartphones and other IoT devices supported by existing cellular mobile communication systems. For example, tagged IoT devices have extremely limited stored energy, and the existing mechanisms for communication between terminal and network devices in 5G systems cannot be reused. How to efficiently utilize the stored energy of tagged IoT devices to communicate with network devices is a problem that needs to be solved.

[0074] The following examples illustrate the scenarios of embodiments of this application, but this application is not limited thereto.

[0075] Figure 1 is a schematic diagram of a communication system according to an embodiment of this application, Figure 2 is another schematic diagram of a communication system according to an embodiment of this application, and Figure 3 is yet another schematic diagram of a communication system according to an embodiment of this application. Figures 1 to 3 schematically illustrate the situation using terminal devices and network devices as examples.

[0076] As shown in Figure 1, network devices can communicate directly with AIoT devices, sending signals directly to or receiving signals directly from AIoT devices. As shown in Figure 2, network devices can also use intermediate nodes to send signals to or receive signals from AIoT devices. As shown in Figure 3, network devices can also send signals to or receive signals from AIoT devices with the assistance of assisting nodes.

[0077] Intermediate nodes can be terminal devices, UEs, or network nodes, such as relays, IAB nodes, repeaters, etc., and this application is not limited to these. Intermediate nodes have the function of communicating with the network devices in Figure 2, and at least have the ability to send signals to AIoT devices and / or receive signals from AIoT devices. Auxiliary nodes can be terminal devices, UEs, or network nodes, such as relays, IAB nodes, repeaters, etc., and this application is not limited to these. Auxiliary nodes have the function of communicating with the network devices in Figure 3, and at least have the ability to send signals to AIoT devices and / or receive signals from AIoT devices. The signals sent to and received from AIoT devices as described here conform to the specifications and descriptions of AIoT devices in communication standard protocols.

[0078] In the embodiments of this application, the network device sending signals / information / configurations to the AIoT device, or the AIoT device receiving signals / information / configurations from the network device, can be done in several ways: the network device directly sends the signal to the AIoT device, which then receives it; the network device sends the signal to the AIoT device via an intermediate node, which then receives it; the network device sends the signal to the AIoT device with the assistance of an auxiliary node, which then receives it; or the network device sends the signal to the AIoT device through other methods, which then receives it. Unless otherwise specified, this application is not limited to these methods.

[0079] In the embodiments of this application, the AIoT device sending signals / information to the network device or the network device receiving signals / information from the AIoT device can be done in various ways: the AIoT device sends the signal and the network device receives it directly; the AIoT device sends the signal and the network device receives it via an intermediate node; the AIoT device sends the signal and the network device receives it with the help of an auxiliary node; or the AIoT device sends the signal and the network device receives it through other methods. Unless otherwise specified, this application is not limited to these methods.

[0080] Due to cost constraints, tag-based terminal devices have extremely limited energy storage, typically using a capacitor to store energy. However, this stored energy is consumed during communication. Therefore, finding a way for tag-based terminal devices to communicate with network devices (e.g., where and when to receive / send data) while conserving energy and maintaining adequate performance is a problem that needs to be solved.

[0081] This application is made to address at least one of the above-mentioned problems or other similar problems. The embodiments of this application will be described below with reference to the accompanying drawings and specific implementation methods.

[0082] In the embodiments of this application, unless otherwise specified, expressions such as "in the case of," "if," and "when" have the same meaning and can be interchanged; the tag-type terminal device is also called "first device" or "terminal device," and the network device is also called "second device." It can be the network device in the examples of Figures 1 to 3, the intermediate node in the example of Figure 2, or the auxiliary node in the example of Figure 3. For example, it can be a reader or interrogator, etc.

[0083] In the embodiments of this application, uplink / downlink signal transmission and reception can be performed between the first device and the second device. Downlink can also be an R2D link (reader-to-device link) or an R2T link (reader-to-tag link), etc., while uplink can also be a D2R link (device-to-reader link) or a T2R link (tag-to-reader link), etc. This application is not limited to these.

[0084] First aspect of the embodiments

[0085] This application provides a signal transmission method, which will be described from the perspective of a first device.

[0086] Figure 4 is a schematic diagram of a signal transmission method according to an embodiment of this application. As shown in Figure 4, the method includes:

[0087] 410: The first device receives message 0 (msg0) sent by the second device on the zeroth resource, message 0 being used at least to instruct or trigger the first device to implement random access, or to instruct the first device to send message 1 (msg1);

[0088] 420: The first device sends message 1 (msg1) to the second device on the first resource. Message 1 is used at least in response to message 0. The first device sends message 1 on the first resource at least by backscattering the first waveform.

[0089] 430: The first device receives message 2 (msg2) sent by the second device on the second resource. Message 2 is used at least in response to message 1.

[0090] It is worth noting that Figure 4 above is only an illustrative description of the embodiments of this application, but this application is not limited thereto. For example, the execution order between various operations can be appropriately adjusted, and other operations can be added or some operations can be removed. Those skilled in the art can make appropriate modifications based on the above content, and are not limited to the description in Figure 4 above.

[0091] In the embodiments of this application, the first device is, for example, a tag-type terminal device in the scenarios shown in Figures 1 to 3, which may be referred to as "others". The second device is, for example, a network device in the scenarios shown in Figures 1 to 3, an intermediate node in the scenario shown in Figure 2, or an auxiliary node in the scenario shown in Figure 3, which may also be referred to as "others". For ease of explanation, this application uses a tag-type terminal device as the first device and a network device as the second device as an example for description.

[0092] According to the above embodiments, the first device transmits message 1 on the first resource at least by backscattering the first waveform. This effectively saves the energy consumption of the first device, enabling it to maintain communication with the second device even when using a low-cost energy storage device. Furthermore, even if the first device samples a low-cost clock source to generate a low-precision clock, it can still maintain communication with the network device.

[0093] In the embodiments of this application, the first waveform can be a continuous waveform (CW), a carrier waveform (CW), a backscattered / backscattering waveform, an uplink waveform, etc., and this application is not limited thereto.

[0094] In some embodiments, the first waveform received by the first device may originate from the second device. This application is not limited thereto; the first waveform may also originate from other devices controlled by the second device.

[0095] In one example, the first device transmits message 1 on the first resource by backscattering a first waveform. The first device modulates the information to be sent to the second device onto the first waveform by adjusting its backscatter circuit, and then backscatters the modulated first waveform.

[0096] In some embodiments, the first device receiving message 2 sent by the second device includes at least: the first device receiving a first signal from the second device at no later than a second time point. The first signal may or may not include message 2 in response to message 1 sent by the first device.

[0097] For example, the first device can receive the first signal earlier than the second time point. The advance time can be determined by the implementation algorithm of the first device, and this application does not impose any restrictions on this. As a result, the first device does not need a high-precision clock to align with the second time point, enabling the first device to receive message 2 even with a low-precision clock, thereby reducing the cost of the first device.

[0098] In the above embodiments, the first device may further determine whether the first signal is or includes message 2 in response to message 1 it sent.

[0099] For example, the first device determines whether the first signal is message 2 sent by the second device in response to message 1 it sent. The specific determination method will be explained later.

[0100] In some embodiments, the first signal is message 2 corresponding to message 1 sent by the first device, that is, the first signal is used to respond to message 1 sent by the first device, and the first device can stop receiving message 2; in other embodiments, the first signal is not message 2 corresponding to message 1 sent by the first device, that is, the first signal is not used to respond to message 1 sent by the first device, and the first device can continue to receive the next first signal. This implementation effectively saves energy consumption for the first device to receive message 2, enabling the first device to maintain communication with the second device even when using a low-cost energy storage device.

[0101] In the above embodiments, the second time point is at least the starting time point of the second resource in the time domain. This application is not limited to this; the second time point can also be other time-domain locations related to the second resource.

[0102] In some embodiments, the second device may configure the second time point through control information of Layer 1 (L1) or control information or data of higher layers. This application is not limited to this. For example, the second time point may also be predefined, such as in a standard protocol.

[0103] In some possible implementations, the second time point includes a time point that is associated with at least one of the aforementioned messages 0, 1, and 2.

[0104] In the above implementation, the first device receives the first signal no later than the time point and determines whether the first signal is message 2 sent by the second device in response to message 1 it sent.

[0105] In some embodiments, the first signal is message 2 corresponding to message 1 sent by the first device. The first device stops receiving message 2 and then performs subsequent random access actions, such as sending the identifier of the terminal device to the second device, etc.

[0106] In some embodiments, if the first signal is not the message 2 corresponding to message 1 sent by the first device, the first device may continue to receive message 2 or stop receiving message 2, for example, by re-receiving message 0 or sending a report of failure to receive message 2 to the second device, etc.

[0107] In the above implementation, the point in time related to message 0 means that the point in time is related to the zeroth resource carrying message 0, or that the point in time is related to the information carried by message 0.

[0108] In one example, this point in time is associated with the zeroth resource carrying message 0. For example, this point in time is separated from the start or end position of the zeroth resource by a certain time interval (referred to as the first time).

[0109] Figure 5 is a schematic diagram of an example of a time point associated with message 0, showing the time interval T between this time point and the end position of the zeroth resource.

[0110] As shown in Figure 5, a time point t2 is separated from the end position t1 of the zeroth resource carrying message 0 by a time interval T. The first device can determine the time point t2 based on the end position t1 of the zeroth resource carrying message 0 and the time T, and receive the first signal no later than the time point t2 (that is, at or before the time point t2).

[0111] In the above example, the first time (e.g., time T) can be configured by the second device or it can be predefined. This application does not restrict its specific value.

[0112] The above are just examples, and this application is not limited to them. The relationship between a point in time and the zeroth resource carrying message 0 may also include other situations.

[0113] In another example, this point in time is related to the information carried by message 0, for example, message 0 carries the position information of this point in time on the timeline.

[0114] Figure 6 is a schematic diagram of another example of a time point associated with message 0, showing how message 0 carries the location information of that time point on the timeline.

[0115] As shown in Figure 6, the position information of this point in time on the time axis is t2, and message 0 carries this position information t2. After receiving message 0, the first device can obtain the position information t2 and receive the first signal no later than time t2 (that is, at or before time t2).

[0116] In another example, this point in time is related to the information carried by message 0. For example, message 0 carries configuration information of a first resource (a resource used by the first device to send message 1). This configuration information includes at least the position information of the first resource on the timeline. The point in time is separated from the start or end position of the first resource by a certain time interval (called the first time).

[0117] Figure 7 is a schematic diagram of another example of a time point related to message 0, showing the situation where message 0 carries the configuration information of the first resource.

[0118] As shown in Figure 7, message 0 carries the configuration information of the first resource, including the position information of the first resource on the time axis, such as the end position t1 of the first resource on the time axis, and the time interval T between the time point t2 and the end position t1. After receiving message 0, the first device can obtain the configuration information of the first resource, and then obtain the position information t1. Based on the time T, it can determine the time point t2 and receive the first signal no later than the time point t2 (that is, at or before the time point t2).

[0119] In the above example, the first time (e.g., time T) can be configured by the second device or it can be predefined. This application does not restrict its specific value.

[0120] The above are just examples; this application is not limited to these. The relationship between a point in time and the information carried by message 0 may also include other situations.

[0121] In the above implementation, the point in time related to message 1 means that the point in time is related to the first resource carrying message 1.

[0122] In one example, the point in time is associated with the first resource carrying message 1. For example, the point in time is separated from the start or end position of the first resource (the resource used by the first device to send message 1) by a certain time interval (referred to as the first time).

[0123] Figure 8 is a schematic diagram of an example of a time point associated with message 1, showing the time interval T between this time point and the end position of the first resource carrying message 1.

[0124] As shown in Figure 8, a time interval T is defined between a time point t2 and the end position t1 of the first resource carrying message 1. After sending message 1, the first device can determine the time point t2 based on this time T and receive the first signal no later than time point t2 (i.e., at or before time point t2).

[0125] In the above example, the first time (e.g., time T) can be configured by the second device or it can be predefined. This application does not restrict its specific value.

[0126] The above are just examples, and this application is not limited to them. The relationship between a point in time and the first resource carrying message 1 may also include other situations.

[0127] In the above implementation, the point in time related to message 2 means that the point in time is related to the second resource carrying message 2, or that the point in time is related to the information carried by message 2. Message 2 can be one of more than one message 2 sent by the second device, such as the first one, or the second resource carrying the message can be located before the second resource carrying message 2 in the time domain, referred to as the first msg2, or it can be any other message 2. The first msg2 will be used as an example for explanation below.

[0128] In one example, this point in time is related to the second resource carrying message 2 (first msg2). For example, this point in time is separated from the start or end position of the second resource carrying first msg2 by a certain time interval (referred to as the first time).

[0129] Figure 9 is a schematic diagram of an example of a time point related to message 2, showing the time interval T between this time point and the end position of the second resource carrying the first msg2.

[0130] As shown in Figure 9, a time interval T is defined between a time point t2 and the end position t1 of the second resource carrying the first msg2. After receiving the first msg2, the first device can determine the time point t2 based on the time T. If the first msg2 is not a response to its sent message 1, the first device receives the first signal no later than the time point t2 (i.e., at or before the time point t2).

[0131] In the above example, the first time (e.g., time T) can be configured by the second device or it can be predefined. This application does not restrict its specific value.

[0132] The above are just examples, and this application is not limited to them. The relationship between a point in time and the second resource carrying message 2 may also include other situations.

[0133] In another example, the point in time is related to the information carried by message 2 (first msg2), for example, the first msg2 carries the position information of the point in time on the timeline.

[0134] Figure 10 is a schematic diagram of another example of a time point associated with message 2, showing the case where the first msg2 carries the position information of that time point on the time axis.

[0135] As shown in Figure 10, the position information of this point in time on the time axis is t2, and the first msg2 carries this position information t2. After receiving the first msg2, the first device can obtain the position information t2. If the first msg2 is not a response to the message 1 it sent, the first device receives the first signal no later than the time point t2 (that is, at or before the time point t2).

[0136] The above are just examples, and this application is not limited to them. The relationship between a point in time and the information carried by message 2 may also include other situations.

[0137] In some other possible implementations, the second time point includes more than one time point that is related to at least one of the aforementioned messages 0, 1, and 2.

[0138] In the above implementation, the first device receives the first signal no later than one time point and determines whether the first signal is message 2 sent by the second device in response to message 1 it sent.

[0139] In some embodiments, the first signal is message 2 corresponding to message 1 sent by the first device. The first device stops receiving message 2 and then performs subsequent random access actions, such as sending the identifier of the terminal device to the second device, etc.

[0140] In some embodiments, if the first signal is not the message 2 corresponding to message 1 sent by the first device, the first device may continue to receive message 2, for example, continue to receive the first signal at the next time point until it receives the message 2 corresponding to message 1 sent by the first device, at which point the first device stops receiving message 2.

[0141] In some embodiments, if the first signal received by the first device at all times is not the message 2 corresponding to the message 1 it sent, the first device may stop receiving message 2, and subsequent actions may include re-receiving message 0 or sending a report to the second device that the message 2 was not received, etc.

[0142] In the above implementation, "more than one time point related to message 0" means that "more than one time point" is related to the zeroth resource carrying message 0, or that "more than one time point" is related to the information carried by message 0.

[0143] In one example, the one or more time points are related to the zeroth resource carrying message 0. For example, the one or more time points are separated from the start or end position of the zeroth resource by one or more time periods (referred to as the first time).

[0144] Figure 11 is a schematic diagram of an example of one or more time points associated with message 0, showing the case where the time points are separated from the end position of the zeroth resource carrying message 0 by time intervals T1 and T2, respectively.

[0145] As shown in Figure 11, one or more time points t2-1 and t2-2 are separated from the end position t1 of the zeroth resource carrying message 0 by time intervals T1 and T2, respectively. The first device can determine one or more time points t2-1 and t2-2 based on the end position of the zeroth resource carrying message 0 and the time intervals T1 and T2, and receive a first signal no later than time point t2-1. If the first signal is not a response to its sent message 1, it can continue to receive the first signal no later than time point t2-2. The behavior of the first device can be found in other descriptions in this document and will not be repeated here.

[0146] In the above example, the more than one first time (e.g., time T1 and time T2) can be configured by the second device or predefined, and this application does not restrict its specific value.

[0147] The above are just examples, and this application is not limited to them. The relationship between one or more time points and the zeroth resource carrying message 0 may also include other situations.

[0148] In another example, the one or more time points are related to the information carried by message 0, for example, message 0 carries the position information of the one or more time points on the timeline.

[0149] Figure 12 is a schematic diagram of another example of one or more time points associated with message 0, showing the case where message 0 carries the location information of one or more time points on the timeline.

[0150] As shown in Figure 12, the location information of the one or more time points on the time axis is t2-1 and t2-2, and message 0 carries this location information t2-1 and t2-2. After receiving message 0, the first device can obtain the location information t2-1 and t2-2, and receive the first signal no later than time point t2-1. If the first signal is not a response to its sent message 1, it can receive the first signal no later than time point t2-2. The behavior of the first device can be referred to in other descriptions in this document, and will not be repeated here.

[0151] In another example, the one or more time points are related to the information carried by message 0. For example, message 0 carries configuration information for one or more first resources (resources used by the first device to send message 1) and one or more second resources (resources used by the second device to send message 2). The configuration information includes the position information of the first and second resources on the time axis (the configuration information may also include other information, which is not limited in this application). The first resource and the second resource correspond one-to-one.

[0152] In the example above, the first device obtains the time-domain location of the second resource corresponding to message 2, which is used by it to send message 1, using the first resource. The first device then receives the first signal at that time-domain location. Therefore, the first device does not need to receive the first signal at more than one time point, thus saving energy.

[0153] In another example, the one or more time points are related to the information carried by message 0. For example, message 0 carries configuration information of one or more first resources (resources used by the first device to send message 1). The configuration information includes the position information of the first resource on the time axis (the configuration information may also include other information, which is not limited in this application). The one or more time points and the start or end position of the first resource are separated by one or more time periods (referred to as the first time).

[0154] Figure 13 is a schematic diagram of another example of a time point and message 0, showing that message 0 carries configuration information for more than one first resource.

[0155] As shown in Figure 13, message 0 carries configuration information for one or more first resources. This configuration information includes the position information of the one or more first resources on the timeline, such as the end position t1 of the one or more first resources on the timeline, and the time points t2-1 and t2-2 are separated from the end position t1 by time intervals T1 and T2, respectively. After receiving message 0, the first device can obtain the configuration information of the one or more first resources, and thus obtain the position information t1. Based on time T1 and T2, it determines the time points t2-1 and t2-2, and receives the first signal no later than time point t2-1. If the first signal is not a response to its sent message 1, the first device can continue to receive the first signal no later than time point t2-2. The behavior of the first device can be referred to in other descriptions in this document, and will not be repeated here.

[0156] In the above example, the more than one first time can be configured by the second device or predefined. It is understood that message 0 can also carry other information, and this application does not impose any restrictions on this.

[0157] The above are just examples; this application is not limited to these. The relationship between one or more time points and the information carried by message 0 may also include other situations.

[0158] In the examples above, the first resource carrying message 1 (i.e., the resource used by the first device to send message 1) can be the first, the last, or any one of the more than one first resources mentioned above; this application does not impose any restrictions on this. Furthermore, which of the more than one first resources the first device uses to send message 1 can be predefined, configured by the second device, or randomly selected by the first device; this application does not impose any restrictions on this.

[0159] In the above implementation, the more than one time point related to message 1 means that the more than one time point is related to the first resource carrying message 1.

[0160] In one example, the one or more time points are related to the first resource carrying message 1. For example, the one or more time points are separated from the start or end position of the first resource by one or more time periods (referred to as the first time).

[0161] Figure 14 is a schematic diagram of an example of one or more time points related to message 1, showing the case where the one or more time points are separated from the end position of one or more first resources by time intervals T1 and T2, respectively.

[0162] As shown in Figure 14, more than one time point t2-1 and t2-2 are separated from the end position t1 of more than one first resource by time intervals T1 and T2, respectively. The first device can determine the time points t2-1 and t2-2 based on the end position of the resource (first resource) used to send message 1 and the time intervals T1 and T2, and receive the first signal no later than time point t2-1. If the first signal is not a response to the message 1 it sent, the first device can continue to receive the first signal no later than time point t2-2. For further description of the behavior of the first device, please refer to other descriptions in this document.

[0163] In the above example, the more than one first time (e.g., time T1 and time T2) can be configured by the second device or predefined, and this application does not restrict its specific value.

[0164] The above are just examples, and this application is not limited to them. The relationship between one or more time points and the first resource carrying message 1 may also include other situations.

[0165] In the above implementation, "more than one time point related to message 2" means that the more than one time point is related to the second resource carrying message 2, or that the more than one time point is related to the information carried by message 2. Here, message 2 can be one of more than one message 2 sent by the second device, such as the first one, or the second resource carrying the message may be located before the second resource carrying message 2 in the time domain, referred to as the first msg2. This application is not limited to this; message 2 can also be other messages 2 among more than one message 2 sent by the second device. The following explanation uses the first msg2 as an example.

[0166] In one example, the one or more time points are related to the second resource carrying message 2 (first msg2). For example, the one or more time points are separated from the start or end position of the second resource carrying the first msg2 by one or more time periods (referred to as the first time).

[0167] Figure 15 is a schematic diagram of an example of one or more time points related to message 2, showing the time interval T between the one or more time points and the end position of the second resource carrying the first msg2.

[0168] As shown in Figure 15, one or more time points t2-1 and t2-2 are separated from the end position t1 of the second resource carrying the first msg2 by time intervals T1 and T2, respectively. The first device can determine the time points t2-1 and t2-2 based on the end position t1 and the times T1 and T2. If the first msg2 is a response to its sent message 1, the first device will no longer receive the first signal; otherwise, the first device will receive the first signal no later than time point t2-1. If the first signal is also not a response to its sent message 1, the first device can continue to receive the first signal no later than time point t2-2. The behavior of the first device can be referred to other embodiments in this document, and will not be repeated here.

[0169] In the above example, the more than one first time can be configured by the second device or it can be predefined. This application does not restrict its specific value.

[0170] The above are merely illustrative examples, and this application is not limited to them. The relationship between one or more time points and the second resource carrying message 2 may also include other situations.

[0171] In another example, the more than one time point is related to the information carried by message 2 (first msg2), for example, the first msg2 carries the position information of the more than one time point on the time axis.

[0172] Figure 16 is a schematic diagram of another example of a time point associated with message 2, showing the case where the first msg2 carries the position information of more than one time point on the time axis.

[0173] As shown in Figure 16, the position information of the one or more time points on the time axis is t2-1 and t2-2, and the first msg2 carries this position information t2-1 and t2-2. After receiving the first msg2, the first device can obtain the position information t2-1 and t2-2. If the first msg2 is a response to its sent message 1, the first device will no longer receive the first signal; otherwise, the first device will receive the first signal no later than time point t2-1. If the first signal is not a response to its sent message 1, the first device will continue to receive the first signal no later than time point t2-2. The behavior of the first device can be referred to other embodiments in this document, which will not be repeated here.

[0174] The above are just examples, and this application is not limited to them. The relationship between more than one time point and the information carried by message 2 may also include other situations.

[0175] In the above implementation, "more than one time point related to message 1 and message 2" means that some of the more than one time points are related to message 1, and other of the more than one time points are related to message 2. Here, message 2 can be one of more than one message 2 sent by the second device, such as the first one, or a second resource carrying the message that precedes the second resource carrying message 2 in the time domain, referred to as the first msg2, or other message 2. The following explanation uses the first msg2 as an example.

[0176] In the above example, some of the more than one time points are related to message 1. For example, some of the time points are related to the first resource where the first device sends message 1. The specific association method is similar to that described above and will not be repeated here.

[0177] In the above example, another part of the more than one time point is related to message 2 (first msg2). For example, the other part of the time point is related to the second resource carrying the first msg2, or the other part of the time point is related to the information carried by the first msg2. The specific association method is similar to that described above, and will not be repeated here.

[0178] The above embodiments are merely illustrative examples illustrating that "a portion of the more than one time points is related to message 1" and "another portion of the more than one time points is related to message 2 (first msg2)". However, this application is not limited thereto, and appropriate modifications can be made based on the above embodiments. For example, the above embodiments can be used individually, or one or more of the above embodiments can be combined.

[0179] In the above implementation, "more than one time point related to message 0 and message 2" means that some of the more than one time points are related to message 0, and other of the more than one time points are related to message 2. Here, message 2 can be one of more than one message 2 sent by the second device, such as the first one, or a second resource carrying the message that is located before the second resource carrying message 2 in the time domain, referred to as the first msg2, or other message 2. The following explanation uses the first msg2 as an example.

[0180] In the above example, some of the multiple time points are related to message 0. For example, these time points may be related to the zeroth resource carrying message 0, the configuration information of the first resource carrying message 0, or the configuration information of the second resource carrying message 0. The specific association methods are similar to those described above and will not be repeated here.

[0181] In the above example, another portion of the multiple time points is related to message 2 (first msg2). For example, this other portion of the time points is related to the second resource carrying the first msg2; or, this other portion of the time points is related to the information carried by the first msg2. The specific association methods are similar to those described above and will not be repeated here.

[0182] The above embodiments are merely illustrative examples illustrating that "a portion of the more than one time points is related to message 0" and "another portion of the more than one time points is related to message 2 (first msg2)". However, this application is not limited thereto, and appropriate modifications can be made based on the above embodiments. For example, the above embodiments can be used alone, or one or more of the above embodiments can be combined.

[0183] In this embodiment of the application, message 0 is a message sent by the second device to the first device. This message 0 is at least used to instruct or trigger the first device to implement random access, or in other words, to instruct the first device to send message 1.

[0184] In some embodiments, message 0 includes relevant information about the first resource. For example, message 0 indicates the first resource, and this application does not limit the specific indication method. Thus, the first device can determine the first resource based on message 0 and then send the aforementioned message 1 on the first resource. Furthermore, message 0 may also include other information, and this application does not limit this.

[0185] In the above embodiments, message 0 can be carried by the zeroth resource. However, this application is not limited to this; the zeroth resource can also carry other messages.

[0186] In the above embodiments, when the first device receives message 0, it can trigger a random access procedure and send message 1 on the first resource. Message 1 is used to respond to message 0. This application is not limited to this. Message 1 can also be used for other purposes or functions.

[0187] In this embodiment of the application, message 1 is a message sent by the first device to the second device, and message 1 is used at least in response to message 0 sent by the second device.

[0188] In some embodiments, message 1 includes an identifier of the first device, which can be a temporary identifier or a permanent identifier, and this application does not impose any limitation on this. Thus, by receiving message 1, the second device can know which first devices responded to message 0, or which first devices requested the second resource or message 2.

[0189] In other embodiments, message 1 includes request information from the first device for the second resource. Thus, by receiving message 1, the second device can understand which second resources the first device is requesting.

[0190] In the above embodiments, the request information may, for example, include the temporal location of the second resource desired by the first device. Furthermore, the request information may also include other information, which this application does not limit.

[0191] The above are just examples; message 1 may also include other information, and this application does not impose any restrictions on this.

[0192] In the above embodiments, message 1 can be carried by the first resource. However, this application is not limited to this, and the first resource can also carry other messages.

[0193] In this embodiment of the application, message 2 is a message sent by the second device to the first device, and is used at least in response to message 1 sent by the first device.

[0194] In some embodiments, message 2 includes an identifier of the first device, thereby allowing the first device to determine whether message 2 is a response to message 1 it sent, i.e., whether message 2 was sent to itself. Furthermore, message 2 may also include other information, which is not limited in this application.

[0195] In the above embodiments, message 2 may include the identifiers of one or more first devices, and the first device may determine whether message 2 is a response to message 1 sent by the one or more first device identifiers.

[0196] For example, message 2 may contain only an identifier of the first device. The first device determines whether message 2 is a response to its message 1 by comparing this identifier with the identifier of the first device in message 1 it sent. That is, if the identifier is the same as the identifier included in message 1 sent by the first device (i.e., the first device's own identifier), the first device determines that message 2 is a response to its message 1.

[0197] For example, message 2 includes one or more identifiers of the first device. The first device determines whether message 2 is a response to message 1 by determining whether the identifier in message 1 it sent is included in one or more of the identifiers of the first device. That is, if the identifier included in message 1 (i.e., the first device's own identifier) ​​is included in one or more of the identifiers of the first device included in message 2, the first device determines that message 2 is a response to message 1 it sent.

[0198] In the example above, if the first device determines that message 2 is a response to message 1 it sent, the first device can stop receiving other messages 2, thereby further saving energy.

[0199] In the example above, if the first device determines that message 2 is not a response to message 1 it sent, the first device can continue to receive the next message 2 in order to obtain a response to message 1 it sent.

[0200] In the above example, if the first device determines that all received messages 2 are not responses to its sent message 1, the first device may stop receiving messages 2, resume receiving messages 0, or send a report to the second device indicating a failure to receive messages 2. Therefore, the second device can take appropriate action based on the report from the first device, and this application does not limit the content of the second device's appropriate actions.

[0201] In the above embodiments, message 2 can be carried by a second resource. However, this application is not limited to this; the second resource can also carry other messages.

[0202] In some embodiments, message 1 is related to message 0. For example, message 0 is used to trigger or instruct the first device to send message 1, or message 1 is used to respond to message 0, and so on. The first device can determine whether message 1 needs to be generated, and / or whether message 1 should be sent, and / or how message 1 should be sent, such as where, when, and how to send message 1, based on the receipt of message 0. Furthermore, the first device can also make the above judgments in conjunction with other information, which is not limited in this application.

[0203] In some embodiments, message 2 is related to message 1; for example, message 2 is used to respond to message 1, etc. The second device can determine whether message 2 needs to be generated, and / or whether message 2 should be sent, and / or how message 2 should be sent, such as where, when, and how it should be sent, based on the receipt of message 1. Furthermore, the second device can also make the above judgments in conjunction with other information, and this application does not impose any limitations on this.

[0204] In some embodiments, the first signal is a signal and / or information sent by the second device to the first device. It may carry the aforementioned message 0 and / or message 2. In addition, it may also carry other information, such as scheduling information or control information for scheduling or controlling the transmission of uplink signals or information, and / or indication information for indicating the transmission of downlink signals or information, and / or data information sent by the second device to the first device, etc.

[0205] The above embodiments are merely illustrative examples of embodiments of this application, but this application is not limited thereto, and appropriate modifications can be made based on the above embodiments. For example, the above embodiments can be used alone, or one or more of the above embodiments can be combined.

[0206] According to the above embodiments, the energy consumption of the first device can be effectively saved, enabling the first device to maintain communication with the second device (e.g., a network device, an intermediate node, or an auxiliary node) even when using a low-cost energy storage device. Furthermore, even if the first device samples a low-cost clock source to generate a low-precision clock, the first device can still maintain communication with the network device.

[0207] Second aspect of the embodiments

[0208] This application provides a signal transmission method, described from the perspective of a second device. The second aspect of the embodiment can be implemented in conjunction with or separately from the first aspect of the embodiment; content identical to that in the first aspect of the embodiment will not be repeated.

[0209] Figure 17 is a schematic diagram of a signal transmission method according to an embodiment of this application. As shown in Figure 17, the method includes:

[0210] 1710: The second device sends message 0 to the first device, message 0 being used at least to instruct or trigger the first device to implement random access, or to instruct the first device to send message 1 (msg1);

[0211] 1720: The second device receives message 1 from one or more first devices, message 1 being used at least in response to message 0, and the first device sending message 1 on the first resource at least by backscattering the first waveform;

[0212] 1730: The second device sends one or more messages 2 on one or more second resources, the one or more messages 2 being used at least in response to the aforementioned one or more messages 1.

[0213] It is worth noting that Figure 17 above is only an illustrative description of the embodiments of this application, but this application is not limited thereto. For example, the execution order between various operations can be appropriately adjusted, and other operations can be added or some operations can be removed. Those skilled in the art can make appropriate modifications based on the above content, and are not limited to the description in Figure 17 above.

[0214] In some embodiments, one or more messages 2 are sent at least via TDM (time-division multiplexing), but this application is not limited thereto, and the one or more messages 2 may also be sent via other means.

[0215] In some embodiments, one or more messages 2 include a first message 2 (first msg2) and a second message 2 (second msg2), and the second resource carrying the first msg2 and the second resource carrying the second msg2 do not overlap in the time domain, as shown in Figures 9 to 16.

[0216] In some embodiments, the second resource carrying the first msg2 is located before the second resource carrying the second msg2 in the time domain.

[0217] In some embodiments, there is no second resource between the second resource carrying the first msg2 and the second resource carrying the second msg2.

[0218] In some embodiments, the second resource carrying the first msg2 and the second resource carrying the second msg2 have a zero resource carrying message 0 or a first resource carrying message 1.

[0219] The above embodiments are merely illustrative examples of embodiments of this application, but this application is not limited thereto, and appropriate modifications can be made based on the above embodiments. For example, the above embodiments can be used alone, or one or more of the above embodiments can be combined.

[0220] In the embodiments of this application, the relevant content of message 0, message 1, message 2 and the second time point has been described in the embodiments of the first aspect, and its content is incorporated here and will not be repeated here.

[0221] According to the above embodiments, the energy consumption of the first device can be effectively saved, enabling the first device to maintain communication with the second device (e.g., a network device, an intermediate node, or an auxiliary node) even when using a low-cost energy storage device. Furthermore, even if the first device samples a low-cost clock source to generate a low-precision clock, the first device can still maintain communication with the network device.

[0222] Third aspect of the embodiments

[0223] This application provides a signal transmission device. This device may be, for example, a tag-type terminal device (referred to as the first device), or one or more components or parts configured on the tag-type terminal device. Contents identical to those in the first and second aspects of the embodiments will not be repeated.

[0224] Figure 18 is a schematic diagram of a signal transmission device according to an embodiment of the present application. As shown in Figure 18, the signal transmission device 1800 according to an embodiment of the present application includes a receiving unit 1810 and a transmitting unit 1820.

[0225] The receiving unit 1810 receives message 0 (msg0) sent by the second device on the zeroth resource. Message 0 is used at least to instruct or trigger the first device to implement random access, or to instruct the first device to send message 1 (msg1).

[0226] The sending unit 1820 sends message 1 (msg1) to the second device on the first resource. Message 1 is used at least in response to message 0.

[0227] The receiving unit 1810 receives message 2 (msg2) sent by the second device on the second resource. Message 2 is used at least in response to message 1.

[0228] The transmitting unit 1820 transmits message 1 on the first resource at least by backscattering the first waveform.

[0229] In some embodiments, the receiving unit 1810 receives message 2 (msg2) sent by the second device, which includes at least:

[0230] The receiving unit 1810 receives the first signal from the second device no later than the second time point.

[0231] In some embodiments, as shown in FIG18, the device 1800 further includes a processing unit 1830, which determines whether the first signal is message 2 for responding to message 1.

[0232] In the above embodiments, the second time point is at least the starting time point of the second resource in the time domain.

[0233] In some possible implementations, the second time point includes a time point that is associated with at least one of message 0, message 1, and message 2.

[0234] For example, the point in time being associated with message 0 means that the point in time is associated with the zeroth resource carrying message 0, or that the point in time is associated with the information carried by message 0.

[0235] The point in time is related to the zeroth resource carrying message 0, for example, it includes at least: the point in time is separated from the start or end position of the zeroth resource by a first time interval, the first time being configured or predefined by the second device.

[0236] The time point is related to the information carried by message 0, for example, it includes at least: message 0 carries at least the position information of the time point on the time axis; or, message 0 carries at least the configuration information of the first resource, the configuration information including at least the position information of the first resource on the time axis, the time point and the start or end position of the first resource are separated by a first time interval, the first time interval is configured by the second device or predefined.

[0237] For example, the point in time that is related to message 1 means that the point in time is related to the first resource that carries message 1.

[0238] The point in time is related to the first resource carrying message 1, for example, it includes at least: the point in time is separated from the start or end position of the first resource by a first time interval, which is configured or predefined by the second device.

[0239] For example, the point in time being related to message 2 means that the point in time is related to the second resource carrying message 2, or that the point in time is related to the information carried by message 2. Here, message 2 is, for example, the first of more than one message 2 sent by the second device, or the second resource carrying the message is located in the time domain before the second resource carrying message 2, and is referred to as the first msg2. This application is not limited to this.

[0240] The time point is related to the second resource carrying message 2, for example, it includes at least: the time point is separated from the start or end position of the second resource carrying the first message 2 by a first time interval, which is configured or predefined by the second device.

[0241] The information carried by message 2 at a given time point is related to the information carried by the message, such as at least the position information of the first message 2 on the timeline.

[0242] In some other possible implementations, the second time point includes more than one time point that is associated with at least one of message 0, message 1, and message 2.

[0243] For example, "more than one time point is related to message 0" means that: "more than one time point is related to the zeroth resource carrying message 0"; or, "more than one time point is related to the information carried by message 0".

[0244] The one or more time points are related to the zeroth resource carrying message 0, for example, at least including: the one or more time points are separated from the start position or end position of the zeroth resource by one or more first time points, the one or more first time points being configured or predefined by the second device.

[0245] The one or more time points are related to the information carried by message 0, for example, at least including: message 0 carries the position information of the one or more time points on the time axis; or, message 0 carries the configuration information of one or more first resources and one or more second resources, the configuration information including the position information of the first resources and second resources on the time axis, the first resources and second resources corresponding one to one; or, message 0 carries the configuration information of one or more first resources, the configuration information including the position information of the first resources on the time axis, the one or more time points and the start position or end position of the first resources are respectively separated by one or more first times, the one or more first times being configured by the second device or predefined.

[0246] In the example above, the first resource carrying message 1 is the first, last, or any one of the above-mentioned first resources.

[0247] For example, "more than one time point is related to message 1" means that "more than one time point is related to the first resource that carries message 1".

[0248] The one or more time points are related to the first resource carrying message 1, for example, at least including: the one or more time points are separated from the start position or end position of the first resource by one or more first time intervals, and the one or more first time intervals are configured by the second device or predefined.

[0249] For example, "more than one time point related to message 2" means that: more than one time point is related to the second resource carrying message 2, or that more than one time point is related to the information carried by message 2. Here, message 2 is, for example, the first of more than one message 2 sent by the second device, or the second resource carrying the message is located in the time domain before the second resource carrying message 2, and is referred to as the first msg2. This application is not limited to this.

[0250] The one or more time points are related to the second resource carrying message 2, for example, at least including: the one or more time points are separated from the start position or end position of the second resource carrying the first message 2 by one or more first time points, and the one or more first time points are configured or predefined by the second device.

[0251] The information carried by message 2 is related to one or more time points, such as at least the first msg2 carrying the position information of one or more time points on the time axis.

[0252] For example, "more than one time point is related to message 1 and message 2" means that some of the time points are related to message 1, and other time points are related to message 2.

[0253] In some examples, one part of the time point relates to a first resource where the first device sends message 1, and the other part relates to a second resource carrying message 2;

[0254] In other examples, one part of the time point relates to the first resource from which the first device sends message 1, and the other part relates to the information carried by message 2.

[0255] For example, "more than one time point is related to message 0 and message 2" means that some of the time points are related to message 0, and other time points are related to message 2.

[0256] In some examples, one part of the time point relates to the zeroth resource carrying message 0, and the other part relates to the second resource carrying message 2;

[0257] In some examples, one part of the time point relates to the zeroth resource carrying message 0, while the other part relates to the information carried by message 2;

[0258] In some examples, one part of the time point relates to the configuration information of the first resource carrying message 0, while the other part relates to the second resource carrying message 2;

[0259] In some examples, one part of the time point relates to the first resource configuration information carried in message 0, while the other part relates to the information carried in message 2;

[0260] In some examples, one part of the time point relates to the second resource configuration information carried in message 0, while the other part relates to the second resource carrying message 2;

[0261] In some examples, one part of the time point relates to the second resource configuration information carried in message 0, while the other part relates to the information carried in message 2.

[0262] In some embodiments, message 0 includes at least information related to the first resource.

[0263] In some embodiments, message 1 includes at least the identifier of the first device and / or the first device's request information for the second resource. This request information may include, for example, at least the temporal location of the second resource desired by the first device.

[0264] In some embodiments, message 2 includes at least the identifier of the first device.

[0265] In some examples, message 2 includes at least one or more identifiers of a first device, which the first device uses to determine whether message 2 is a response to message 1 it sent.

[0266] For example, message 2 includes only an identifier of the first device, and this identifier is the same as the identifier included in message 1 sent by the first device. The first device determines that message 2 is a response to message 1 it sent.

[0267] For example, message 2 includes the identifier of one or more first devices, and the identifier included in message 1 sent by the first device is contained in the identifier of one or more first devices included in message 2, and the first device determines that message 2 is a response to message 1 sent by it.

[0268] In some embodiments, if the first device determines that message 2 is a response to message 1 it sent, the first device stops receiving other messages 2.

[0269] In some embodiments, if the first device determines that message 2 is not a response to message 1 it sent, the first device continues to receive the next message 2.

[0270] In some embodiments, if the first device determines that all messages 2 are not a response to its sent message 1, the first device stops receiving messages 2 and / or resumes receiving messages 0 and / or sends a message 2 reception failure report to the second device.

[0271] In some embodiments, the processing unit 1830 determines, at least based on the receipt of message 0, whether message 1 needs to be generated and / or sent, and / or how message 1 should be sent.

[0272] In some embodiments, the second device determines, at least based on the receipt of message 1, whether message 2 needs to be generated and / or sent, and / or how message 2 should be sent.

[0273] In some embodiments, message 0 and / or message 2 are carried by a first signal, which also carries at least one of the following:

[0274] Scheduling or control information used to schedule or control the transmission of uplink signals or information;

[0275] Indication information used to indicate the transmission of downlink signals or information;

[0276] Data information sent from the second device to the first device.

[0277] The above embodiments are merely illustrative examples of embodiments of this application, but this application is not limited thereto, and appropriate modifications can be made based on the above embodiments. For example, the above embodiments can be used alone, or one or more of the above embodiments can be combined.

[0278] It is worth noting that the above description only covers the components or modules relevant to this application, but this application is not limited thereto. The signal transmission device 1800 may also include other components or modules, and for details regarding these components or modules, please refer to related technologies.

[0279] Furthermore, for simplicity, Figure 18 only illustrates the connection relationships or signal flow between the various components or modules, but those skilled in the art should understand that various related technologies such as bus connections can be used. The aforementioned components or modules can be implemented using hardware facilities such as processors, memory, transmitters, and receivers; this application does not limit this implementation.

[0280] According to the above embodiments, the energy consumption of the first device can be effectively saved, enabling the first device to maintain communication with the second device (e.g., a network device, an intermediate node, or an auxiliary node) even when using a low-cost energy storage device. Furthermore, even if the first device samples a low-cost clock source to generate a low-precision clock, the first device can still maintain communication with the network device.

[0281] Fourth aspect of the embodiment

[0282] This application provides a signal transmission device. This device may be, for example, a network device, an intermediate node, or an auxiliary node, referred to as a second device, or it may be one or more components or parts configured in a network device, intermediate node, or auxiliary node. Contents identical to those in the embodiments of the first to third aspects will not be repeated.

[0283] Figure 19 is another schematic diagram of a signal transmission device according to an embodiment of this application. As shown in Figure 19, the signal transmission device 1900 includes a transmitting unit 1910 and a receiving unit 1920.

[0284] The sending unit 1910 sends message 0 to the first device. Message 0 is used at least to instruct or trigger the first device to implement random access, or to instruct the first device to send message 1 (msg1).

[0285] The receiving unit 1920 receives message 1 from one or more first devices, where message 1 is used at least in response to message 0;

[0286] Sending unit 1910 sends one or more messages 2 on one or more second resources, and one or more messages 2 are used at least in response to one or more messages 1;

[0287] The first device sends message 1 on the first resource by backscattering the first waveform.

[0288] In some embodiments, more than one message 2 is sent at least in TDM (time-division multiplexing) mode.

[0289] In some embodiments, one or more messages 2 include a first message 2 and a second message 2; the second resource carrying the first message 2 and the second resource carrying the second message 2 do not overlap in the time domain.

[0290] For example, the second resource carrying the first message 2 is located before the second resource carrying the second message 2 in the time domain; and / or, there is no second resource between the second resource carrying the first message 2 and the second resource carrying the second message 2; and / or, there is a zero resource carrying message 0 or a first resource carrying message 1 between the second resource carrying the first message 2 and the second resource carrying the second message 2.

[0291] In some embodiments, as shown in FIG19, the device 1900 further includes a processing unit 1930, which is used to generate the aforementioned message 0 and / or generate the aforementioned message 2 based on the received aforementioned message 1, but this application is not limited thereto.

[0292] The above embodiments are merely illustrative examples of embodiments of this application, but this application is not limited thereto, and appropriate modifications can be made based on the above embodiments. For example, the above embodiments can be used alone, or one or more of the above embodiments can be combined.

[0293] It is worth noting that the above description only covers the components or modules relevant to this application, but this application is not limited thereto. The signal transmitting device 1900 may also include other components or modules, and for details regarding these components or modules, please refer to related technologies.

[0294] Furthermore, for simplicity, Figure 19 only illustrates the connection relationships or signal flow between the various components or modules, but those skilled in the art should understand that various related technologies such as bus connections can be used. The aforementioned components or modules can be implemented using hardware facilities such as processors, memory, transmitters, and receivers; this application does not limit this implementation.

[0295] According to the above embodiments, the energy consumption of the first device can be effectively saved, enabling the first device to maintain communication with the second device (e.g., a network device, an intermediate node, or an auxiliary node) even when using a low-cost energy storage device. Furthermore, even if the first device samples a low-cost clock source to generate a low-precision clock, the first device can still maintain communication with the network device.

[0296] Fifth aspect of the embodiment

[0297] This application also provides a communication system, which can be referred to in Figures 1 to 3. The contents that are the same as those in the embodiments of the first to fourth aspects will not be repeated.

[0298] In some embodiments, the communication system 100 may include at least a first device and a second device. The first device may be, for example, a tag-type terminal device in the scenarios of Figures 1 to 3, and the second device may be, for example, a network device in the scenarios of Figures 1 to 3, an intermediate node in the scenario of Figure 2, or an auxiliary node in the scenario of Figure 3.

[0299] Figure 20 is a schematic diagram of information interaction between the first device and the second device. As shown in Figure 20, the interaction process includes:

[0300] 2010: The second device sends message 0 to the first device. Message 0 is used at least to instruct or trigger the first device to implement random access or to instruct the first device to send message 1 (msg1). The first device receives message 0 on the zeroth resource.

[0301] 2020: A first device sends message 1 (msg1) to a second device on a first resource. Message 1 is used at least in response to message 0. The second device receives message 1 sent from one or more first devices. The first device sends message 1 on the first resource at least by backscattering a first waveform.

[0302] 2030: The second device sends one or more messages 2 on one or more second resources, the one or more messages 2 being used at least in response to the aforementioned one or more messages 1, and the first device receives the message 2 on the second resource.

[0303] The behavior of the first and second devices, as well as the relevant content of messages 0, 1, and 2, have been described in the embodiments of the first aspect, and their content is incorporated herein by reference and will not be repeated here.

[0304] This application also provides a terminal device, which may be a tag-type terminal device of the foregoing embodiments, an intermediate node of the foregoing embodiments, or an auxiliary node of the foregoing embodiments. However, this application is not limited to these and may also be other devices.

[0305] Figure 21 is a schematic diagram of a terminal device according to an embodiment of this application. As shown in Figure 21, the terminal device 2100 may include a processor 2110 and a memory 2120; for example, the memory 2120 stores data and programs and is coupled to the processor 2110. It is worth noting that this figure is exemplary; other types of structures may also be used to supplement or replace this structure to implement telecommunications functions or other functions.

[0306] For example, if the terminal device is a tag-type terminal device as described above, the processor 2110 can be configured to execute a program to implement the signal transmission method as described in the first aspect embodiment. For example, the processor 2110 can be configured to perform the following control:

[0307] Receive message 0 (msg0) sent by the second device on the zeroth resource. Message 0 is used at least to instruct or trigger the terminal device to implement random access, or to instruct the terminal device to send message 1 (msg1).

[0308] Send message 1 (msg1) to the second device on the first resource. Message 1 is used at least in response to message 0.

[0309] Receive message 2 (msg2) sent by the second device on the second resource. Message 2 is used at least in response to message 1.

[0310] The processor 2110 can be configured to send message 1 on the first resource at least by backscattering the first waveform.

[0311] For example, if the terminal device is the aforementioned intermediate or auxiliary node, the processor 2110 can be configured to execute a program to implement the signal transmission method as described in the second aspect of the embodiment. For example, the processor 2110 can be configured to perform the following control:

[0312] Send message 0 to the first device, message 0 being used at least to instruct or trigger the first device to implement random access, or to instruct the first device to send message 1 (msg1);

[0313] Receive message 1 from one or more first devices, where message 1 is used at least in response to message 0;

[0314] Send one or more messages 2 on one or more second resources, where one or more messages 2 are used at least in response to one or more messages 1;

[0315] The first device sends message 1 on the first resource by backscattering the first waveform.

[0316] As shown in Figure 21, the terminal device 2100 may further include a communication module 2130; it may or may not have a power supply. It is worth noting that the terminal device 2100 is not necessarily required to include all the components shown in Figure 21; these components are not essential. Furthermore, the terminal device 2100 may also include components not shown in Figure 21, which can be found in existing technologies.

[0317] This application also provides a network device, which can be the network device described in the foregoing embodiments, such as a base station, but this application is not limited to this and can also be other network devices.

[0318] Figure 22 is a schematic diagram of the network device configuration according to an embodiment of this application. As shown in Figure 22, the network device 2200 may include: a processor 2210 (e.g., a central processing unit CPU) and a memory 2220; the memory 2220 is coupled to the processor 2210. The memory 2220 can store various types of data; in addition, it also stores an information processing program 2230, and executes the program 2230 under the control of the processor 2210.

[0319] For example, processor 2210 can be configured to execute a program to implement the signal transmission method as described in the second aspect embodiment. For example, processor 2210 can be configured to perform the following control:

[0320] Send message 0 to the first device, message 0 being used at least to instruct or trigger the first device to implement random access, or to instruct the first device to send message 1 (msg1);

[0321] Receive message 1 from one or more first devices, where message 1 is used at least in response to message 0;

[0322] Send one or more messages 2 on one or more second resources, where one or more messages 2 are used at least in response to one or more messages 1;

[0323] The first device sends message 1 on the first resource by backscattering the first waveform.

[0324] In addition, as shown in Figure 22, network device 2200 may also include: transceiver 2240 and antenna 2250, etc.; the functions of the above components are similar to those in the prior art, and will not be described in detail here. It is worth noting that network device 2200 does not necessarily have to include all the components shown in Figure 22; in addition, network device 2200 may also include components not shown in Figure 22, which can be referred to in the prior art.

[0325] This application also provides a computer program, wherein when the program is executed in a tag-type terminal device, the program causes the tag-type terminal device to perform the signal transmission method described in the first aspect of the embodiment.

[0326] This application also provides a storage medium storing a computer program, wherein the computer program causes a tag-type terminal device to perform the signal transmission method described in the first aspect of the embodiment.

[0327] This application also provides a computer program in which, when executed in a network device, intermediate node, or auxiliary node, the program causes the network device, intermediate node, or auxiliary node to perform the signal transmission method described in the second aspect of the embodiment.

[0328] This application also provides a storage medium storing a computer program, wherein the computer program causes a network device, intermediate node, or auxiliary node to perform the signal transmission method described in the second aspect of the embodiment.

[0329] The apparatus and methods described above in this application can be implemented in hardware or in combination with software. This application relates to a computer-readable program that, when executed by a logic component, enables the logic component to implement the apparatus or components described above, or to implement the various methods or steps described above. This application also relates to storage media for storing the above programs, such as hard disks, magnetic disks, optical disks, DVDs, flash memory, etc.

[0330] The methods / apparatus described in conjunction with the embodiments of this application can be directly embodied in hardware, software modules executed by a processor, or a combination of both. For example, one or more and / or combinations of one or more functional block diagrams shown in the figures can correspond to various software modules in a computer program flow, or to various hardware modules. These software modules can correspond to the various steps shown in the figures, respectively. These hardware modules can be implemented, for example, using a field-programmable gate array (FPGA) to embed these software modules.

[0331] The software module can reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art. A storage medium can be coupled to the processor, enabling the processor to read information from and write information to the storage medium; or the storage medium can be an integral part of the processor. The processor and storage medium can reside in an ASIC. The software module can be stored in the memory of a mobile terminal or in a memory card that can be inserted into the mobile terminal. For example, if the device (such as a mobile terminal) uses a high-capacity MEGA-SIM card or a high-capacity flash memory device, the software module can be stored in the MEGA-SIM card or the high-capacity flash memory device.

[0332] One or more and / or one or more combinations of functional blocks described in the accompanying drawings can be implemented as a general-purpose processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, or any suitable combination thereof for performing the functions described herein. One or more and / or one or more combinations of functional blocks described in the accompanying drawings can also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in communication with a DSP, or any other such configuration.

[0333] The present application has been described above with reference to specific embodiments. However, those skilled in the art should understand that these descriptions are exemplary and not intended to limit the scope of protection of the present application. Those skilled in the art can make various modifications and variations to the present application based on its spirit and principles, and these modifications and variations are also within the scope of the present application.

[0334] Regarding the implementation methods including the above embodiments, the following notes are also disclosed:

[0335] 1. A signal transmission method applied to a first device, the method comprising:

[0336] The first device receives message 0 sent by the second device on the zeroth resource, the message 0 being used at least to instruct or trigger the first device to implement random access, or to instruct the first device to send message 1;

[0337] The first device sends message 1 to the second device on the first resource, the message 1 being used at least in response to message 0;

[0338] The first device receives message 2 sent by the second device on the second resource, the message 2 being used at least in response to message 1;

[0339] The first device transmits message 1 on the first resource by backscattering the first waveform at least once.

[0340] 2. According to the method described in Appendix 1, wherein,

[0341] The message 1 includes at least the identifier of the first device and / or the first device's request information for the second resource.

[0342] 3. According to the method described in Appendix 1, wherein,

[0343] The message 2 includes at least the identifier of the first device.

[0344] 4. According to the method described in Appendix 3, wherein,

[0345] The message 2 includes at least one or more identifiers of a first device, which determines whether the message 2 is a response to the message 1 it sent by the first device through the identifiers of the one or more first devices.

[0346] 5. According to the method described in Appendix 4, wherein,

[0347] Message 2 includes only an identifier of the first device, and this identifier is the same as the identifier included in message 1 sent by the first device. The first device determines that message 2 is a response to message 1 it sent; or,

[0348] The message 2 includes the identifier of one or more first devices, and the identifier included in the message 1 sent by the first device is included in the identifier of one or more first devices included in the message 2, and the first device determines that the message 2 is a response to the message 1 it sent.

[0349] 6. According to the method described in Appendix 1, wherein,

[0350] The first device determines, at least based on the receipt of message 0, whether it needs to generate and / or send message 1, and / or how to send message 1.

[0351] The second device determines, at least based on the receipt of message 1, whether it needs to generate and / or send message 2, and / or how to send message 2.

[0352] 7. According to the method described in Appendix 1, wherein,

[0353] Message 0 and / or Message 2 are carried by a first signal, which also carries at least one of the following:

[0354] Scheduling or control information used to schedule or control the transmission of uplink signals or information;

[0355] Indication information used to indicate the transmission of downlink signals or information;

[0356] The data information sent by the second device to the first device.

[0357] 8. A signal transmission method applied to a second device, the method comprising:

[0358] The second device sends message 0 to the first device, the message 0 being used at least to instruct or trigger the first device to implement random access, or to instruct the first device to send message 1;

[0359] The second device receives message 1 from one or more of the first devices, the message 1 being used at least in response to message 0;

[0360] The second device sends one or more messages 2 on one or more second resources, wherein the one or more messages 2 are at least used in response to the one or more messages 1;

[0361] The first device transmits message 1 on the first resource by backscattering the first waveform at least once.

[0362] 9. According to the method described in Appendix 8, wherein,

[0363] The more than one message 2 includes a first message 2 and a second message 2;

[0364] The second resource carrying the first message 2 and the second resource carrying the second message 2 do not overlap in the time domain.

[0365] 10. The method according to Appendix 9, wherein,

[0366] The second resource carrying the first message 2 is located in the time domain before the second resource carrying the second message 2; and / or,

[0367] There is no second resource between the second resource carrying the first message 2 and the second resource carrying the second message 2; and / or,

[0368] Between the second resource carrying the first message 2 and the second resource carrying the second message 2, there is a zeroth resource carrying the message 0 or a first resource carrying the message 1.

Claims

1. A signal transmission device, configured in a first device, comprising a receiving unit and a transmitting unit, wherein: The receiving unit receives message 0 sent by the second device on the zero resource. Message 0 is at least used to instruct or trigger the first device to implement random access, or to instruct the first device to send message 1. The sending unit sends message 1 to the second device on the first resource, and message 1 is at least used to respond to message 0; The receiving unit receives message 2 sent by the second device on the second resource, and message 2 is at least used to respond to message 1; The sending unit transmits message 1 on the first resource by backscattering the first waveform at least once.

2. The apparatus according to claim 1, wherein, The device also includes a processing unit; The receiving unit receives a first signal from the second device no later than the second time point; The processing unit determines whether the first signal is message 2 used in response to message 1.

3. The apparatus according to claim 2, wherein, The second time point is at least the starting time point of the second resource in the time domain.

4. The apparatus according to claim 2, wherein, The second time point includes a time point that is associated with at least one of message 0, message 1, and message 2.

5. The apparatus according to claim 4, wherein, The specified point in time is related to the zeroth resource carrying the message 0; and / or, The specific time point is related to the information carried by message 0; And / or, The point in time is associated with the first resource carrying the message 1; And / or, The aforementioned point in time is related to the second resource carrying the message 2; And / or, The specified point in time is related to the information carried by message 2.

6. The apparatus according to claim 5, wherein, The point in time associated with the zeroth resource carrying the message 0 includes at least: The time interval between the point in time and the start or end position of the zeroth resource is a first time, wherein the first time is configured by the second device or is predefined. The point in time is related to the information carried by message 0, and includes at least: Message 0 carries at least the position information of the one time point on the time axis; or, The message 0 carries at least the configuration information of the first resource, which includes at least the position information of the first resource on the time axis. The time interval between the time point and the start or end position of the first resource is a first time, which is configured or predefined by the second device.

7. The apparatus according to claim 5, wherein, The point in time associated with the first resource carrying message 1 includes at least: The time point is spaced from the start or end position of the first resource by a first time interval, where the first time interval is configured or predefined by the second device.

8. The apparatus according to claim 5, wherein, The point in time associated with the second resource carrying the message 2 includes at least: The time interval between the point in time and the start or end position of the second resource is a first time, wherein the first time is configured or predefined by the second device; The point in time is related to the information carried by message 2, and includes at least: The message 2 contains at least the location information of the point in time on the timeline.

9. The apparatus according to claim 2, wherein, The second time point includes one or more time points, which are related to at least one of message 0, message 1, and message 2.

10. The apparatus according to claim 9, wherein, The one or more time points are related to the zeroth resource carrying the message 0; and / or, The one or more time points mentioned above are related to the information carried by message 0; and / or, The one or more time points are related to the first resource carrying the message 1; and / or The one or more time points mentioned are related to the second resource carrying the message 2; And / or, The one or more time points mentioned are related to the information carried by message 2.

11. The apparatus according to claim 10, wherein, The one or more time points associated with the zeroth resource carrying the message 0 include at least: The one or more time points are each separated from the start or end position of the zeroth resource by one or more first time points, wherein the one or more first time points are configured by the second device or are predefined. The one or more time points mentioned are related to the information carried by message 0, including at least: Message 0 carries at least the position information of one or more time points on the timeline; or... The message 0 carries at least one configuration of the first resource and one or more of the second resources. The configuration information includes at least the position information of the first resource and the second resource on the time axis, wherein the first resource and the second resource correspond one-to-one; or, The message 0 carries at least one configuration information of the first resource, the configuration information including at least the position information of the first resource on the time axis, and the one or more time points and the start position or end position of the first resource are respectively separated by one or more first time intervals, the first time intervals being configured by the second device or predefined.

12. The apparatus according to claim 11, wherein, The first resource carrying the message 1 is the first, the last, or any one of the more than one first resources.

13. The apparatus according to claim 10, wherein, The one or more time points associated with the first resource carrying the message 1 include at least: The one or more time points are each spaced at more than one first time interval from the start or end position of the first resource, and the first time interval is configured or predefined by the second device.

14. The apparatus according to claim 10, wherein, One or more of the time points are associated with the second resource carrying the message 2, including at least: The one or more time points are each spaced from the start or end position of the second resource by one or more first time intervals, wherein the first time interval is configured by the second device or is predefined. The one or more time points related to the information carried by message 2 include at least: The message 2 carries at least one location information of a point in time on the timeline.

15. The apparatus according to claim 1, wherein, The message 0 includes at least the relevant information about the first resource.

16. The apparatus according to claim 1, wherein, The message 1 includes at least the identifier of the first device and / or the first device's request information for the second resource.

17. The apparatus according to claim 1, wherein, The message 2 includes at least the identifier of the first device.

18. The apparatus according to claim 17, wherein, The message 2 includes at least one or more identifiers of a first device, which determines whether the message 2 is a response to the message 1 it sent by using the identifiers of the one or more first devices.

19. The apparatus according to claim 18, wherein, If the first device determines that message 2 is a response to message 1 it sent, the first device stops receiving other messages 2; or, If the first device determines that message 2 is not a response to message 1 it sent, the first device continues to receive the next message 2; or, If the first device determines that none of the messages 2 are a response to the message 1 it sent, the first device stops receiving messages 2 and / or resumes receiving messages 0 and / or sends a message 2 reception failure report to the second device.

20. A signal transmission device, configured in a second device, comprising a transmitting unit and a receiving unit, wherein: The sending unit sends message 0 to the first device, and message 0 is used at least to instruct or trigger the first device to implement random access, or to instruct the first device to send message 1; The receiving unit receives message 1 from one or more of the first devices, and the message 1 is at least used to respond to message 0; The sending unit sends one or more messages 2 on one or more second resources, and the one or more messages 2 are at least used to respond to the one or more messages 1; The first device transmits message 1 on the first resource by backscattering the first waveform at least once.

Images