Access failure processing method and apparatus

Abstract

Provided in the embodiments of the present application are an access failure processing method and apparatus, the method comprising: a first device receiving first information from a second device, determining a first time-frequency resource on the basis of the first information, and sending a second Msg1 to the second device on the first time-frequency resource, wherein before sending the second Msg1 to the second device, the first device sends a first Msg1 to the second device, but fails to receive a first Msg2 fed back by the second device; and / or, before sending the second Msg1 to the second device, the first device sends the first Msg1 to the second device, and receives the first Msg2 fed back by the second device, but the first device fails to send a first Msg3 to the second device; and / or, before sending the second Msg1 to the second device, the first device sends the first Msg1 to the second device, receives the first Msg2 fed back by the second device, and sends the first Msg3 to the second device, but fails to receive feedback information from the second device or receives feedback information from the second device, which is an NACK.

Description

Methods and apparatus for handling access failures Technical Field

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

[0002] From the early days of 2G (second generation) to 4G (fourth generation) systems, cellular mobile communication systems primarily served mobile phones, i.e., mobile terminal devices held by people. 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 device terminals have been supported and implemented in actual network deployments and service applications, such as eMTC (enhanced Machine-Type Communication) terminal devices, NB-IoT (Narrow Band Internet of Things) terminal devices, and RedCap (Reduced Capability) terminal devices. With the increasing diversity of IoT terminal device types, cellular mobile systems have gained increasingly stronger capabilities in providing services and offering services to vertical industries.

[0003] However, among the massive number of IoT devices, the area of ​​large-scale and lower-cost IoT terminal devices remains a gap in cellular mobile communication systems. In order to provide more robust, reliable, and complete IoT application solutions, how to support lower-cost IoT terminal devices in 3GPP (3rd Generation Partnership Project) cellular mobile systems has become an urgent problem to be solved.

[0004] 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. Summary of the Invention

[0005] The inventors discovered that RFID (Radio Frequency Identification) systems are a solution for the large-scale and lower-cost Internet of Things (IoT) terminal devices. RFID systems have a wide range of 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 easier to apply to various scenarios such as item management and tracking. Although RFID tags are inexpensive, the deployment and usage costs of RFID systems are higher compared to 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 for RFID systems.

[0006] 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.

[0007] As a new type of IoT terminal in 5G (fifth generation) systems, tag-based terminal devices (Ambient IoT devices, or A-IoT devices for short) face severe cost constraints. Their hardware capabilities are significantly weaker than those of ordinary smartphones and other IoT devices supported by existing cellular mobile communication systems. For example, tag-based terminal devices may lack a stable power supply (e.g., using ambient energy harvesting instead of conventional batteries), have narrower bandwidth, limited accuracy of their internal crystal oscillators due to cost constraints, and limited signal processing capabilities.

[0008] Due to the limited capabilities of A-IoT devices, the probability of resource collisions or access resolution failures during random access is higher than that of ordinary mobile devices in NR. Therefore, resolving random access failures in A-IoT devices is a pressing issue that needs to be addressed.

[0009] To address at least one of the above-mentioned problems or other similar issues, embodiments of this application provide a method and apparatus for handling access failures.

[0010] According to one aspect of the embodiments of this application, a method for handling access failure is provided, applied to a first device, wherein the method includes:

[0011] The first device receives first information from the second device (reader), determines a first time-frequency resource based on the first information, and sends a second message 1 (Msg1) to the second device on the first time-frequency resource.

[0012] in,

[0013] Before sending the second Msg1 to the second device, the first device sent the first Msg1 to the second device and did not receive a first message 2 (Msg2) from the second device. The first Msg2 is a response to the first Msg1; and / or,

[0014] Before sending the second Msg1 to the second device, the first device sent the first Msg1 to the second device and received the first Msg2 in response from the second device. The first device did not send the first message 3 (Msg3) to the second device; the first Msg3 was a response to the first Msg2; and / or,

[0015] Before sending the second Msg1 to the second device, the first device sent the first Msg1 to the second device, received the first Msg2 from the second device, sent the first Msg3 to the second device, and did not receive any feedback from the second device or received a NACK from the second device.

[0016] According to another aspect of the embodiments of this application, an access failure processing apparatus is provided, configured in a first device, the apparatus comprising:

[0017] The receiving unit receives the first information from the second device (reader);

[0018] The processing unit determines the first time-frequency resource based on the first information;

[0019] The sending unit sends a second message 1 (Msg1) to the second device on the first time-frequency resource;

[0020] in,

[0021] Before sending the second Msg1 to the second device, the sending unit sent the first Msg1 to the second device. The receiving unit did not receive the first message 2 (Msg2) from the second device. The first Msg2 is a response to the first Msg1; and / or,

[0022] Before sending the second Msg1 to the second device, the sending unit sent the first Msg1 to the second device. The receiving unit received the first Msg2 from the second device. The sending unit did not send the first message 3 (Msg3) to the second device. The first Msg3 is a response to the first Msg2; and / or,

[0023] Before sending the second Msg1 to the second device, the sending unit sent the first Msg1 to the second device. The receiving unit received the first Msg2 from the second device. The sending unit sent the first Msg3 to the second device. The receiving unit did not receive any feedback information from the second device or the feedback information received from the second device was NACK.

[0024] According to another aspect of the embodiments of this application, a method for handling access failure is provided, applied to a second device (reader), the method comprising:

[0025] The second device sends a first message to the first device and receives a second Msg1 from the first device on the first time-frequency resource;

[0026] in,

[0027] Before the second device receives the second Msg1 from the first device, the first device sends a first Msg1 to the second device, and the second device either does not receive the first Msg1 or receives the first Msg1 but does not send a first Msg2; and / or,

[0028] Before the second device receives the second Msg1 from the first device, the second device receives the first Msg1 from the first device and sends the first Msg2 back to the first device. The second device does not receive the first Msg3 from the first device, and the first Msg3 is a response to the first Msg2; and / or,

[0029] Before the second device receives the second Msg1 from the first device, the second device receives the first Msg1 from the first device and sends a first Msg2 back to the first device, and receives the first Msg3 from the first device, but does not send any feedback information to the first device or sends a NACK feedback information to the first device.

[0030] According to another aspect of the embodiments of this application, an access failure processing apparatus is provided, configured in a second device, the apparatus comprising:

[0031] A sending unit that sends first information to the first device;

[0032] The receiving unit receives a second Msg1 from the first device on a first time-frequency resource;

[0033] in,

[0034] Before the receiving unit receives the second Msg1 from the first device, the first device sends a first Msg1 to the second device; the receiving unit either does not receive the first Msg1 or the sending unit does not send a first Msg2 after receiving the first Msg1; and / or,

[0035] Before the receiving unit receives the second Msg1 from the first device, it receives the first Msg1 from the first device, and the sending unit sends the first Msg2 back to the first device. The receiving unit does not receive the first Msg3 from the first device, and the first Msg3 is a response to the first Msg2; and / or,

[0036] Before the receiving unit receives the second Msg1 from the first device, it receives the first Msg1 from the first device, and the sending unit feeds back the first Msg2 to the first device, and the receiving unit receives the first Msg3 from the first device. The sending unit either does not send feedback information to the first device or sends feedback information to the first device as NACK.

[0037] One of the beneficial effects of this application's embodiments is that, according to this application's embodiments, a specific definition of A-IoT device access failure is given, and corresponding solutions are provided for different access failure processes, thereby increasing the probability of A-IoT devices accessing the network and improving the efficiency of the A-IoT system.

[0038] 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.

[0039] 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.

[0040] 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

[0041] 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.

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

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

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

[0045] Figure 4 is a schematic diagram of the general frame structure of the slotted-ALOHA random access procedure in A-IoT.

[0046] Figure 5 is a schematic diagram of the random access process in Ambient IoT;

[0047] Figure 6 is a schematic diagram of the distribution of time-frequency resources in Ambient IoT;

[0048] Figure 7 is a schematic diagram of a method for handling access failure according to an embodiment of this application;

[0049] Figure 8 is a schematic diagram of an example where the first time reference point is the end point of the time domain resource of the first Msg1 sent by the first device;

[0050] Figure 9 is a schematic diagram of an example where the first time reference point is the end point of the time-domain resource of the last Msg1 in a time slot.

[0051] Figure 10 is a schematic diagram of an example where the first time reference point is the end point of the time domain resource where the random access trigger information is located in a time slot;

[0052] Figure 11 is a schematic diagram of an example where the first time reference point is the end point of the time domain resource of the last Msg2 in a time slot;

[0053] Figure 12 is a schematic diagram of an example where the first time reference point is the end point of the aforementioned first time domain resource;

[0054] Figure 13 is a schematic diagram of an example where the first time reference point is the end point of the aforementioned first time domain resource;

[0055] Figure 14 is a schematic diagram of an example of the first device reselecting time-domain resources based on the A-IoT paging message;

[0056] Figure 15 is a schematic diagram of another example of the first device reselecting time-domain resources based on the A-IoT paging message;

[0057] Figure 16 is a schematic diagram of an example of the first device reselecting time-domain resources based on Msg0;

[0058] Figure 17 is a schematic diagram of an example of the first device reselecting time-domain resources based on Msg2;

[0059] Figure 18 is a schematic diagram of an example of the first and second information;

[0060] Figure 19 is a schematic diagram of another example of the first and second information;

[0061] Figure 20 is another schematic diagram of the access failure handling method according to an embodiment of this application;

[0062] Figure 21 is a schematic diagram of an access failure handling device according to an embodiment of this application;

[0063] Figure 22 is another schematic diagram of the access failure handling device according to an embodiment of this application;

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

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

[0066] 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.

[0067] 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.

[0068] In the embodiments of this application, the singular forms "a," "the," etc., including the plural forms, should be broadly interpreted 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.

[0069] 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.

[0070] 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.

[0071] 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.

[0072] Base stations can include, but are not limited to, devices such as NodeBs (or NBs), evolved NodeBs (eNodeBs or eNBs), and 5G base stations (gNBs), IAB hosts (Donors), etc. They can also include Remote Radio Heads (RRHs), Remote Radio Units (RRUs), relays or low-power nodes (e.g., femeto, pico, etc.), reders, 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 geographic 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.

[0073] 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.

[0074] Terminal devices may include, but are not limited to, the following devices: cellular phones, personal digital assistants (PDAs), wireless modems, wireless communication devices, handheld devices, machine-type communication devices, laptops, cordless phones, smartphones, smartwatches, digital cameras, tags, devices attached to or associated with items (e.g., for item management), etc.

[0075] 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.

[0076] 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.

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

[0078] Figure 1 is a schematic diagram of a communication system according to an embodiment of this application, showing the case where the base station communicates directly with the AIoT device; Figure 2 is another schematic diagram of a communication system according to an embodiment of this application, showing the case where the base station communicates with the AIoT device through an intermediate node; Figure 3 is yet another schematic diagram of a communication system according to an embodiment of this application, showing the case where the base station communicates with the AIoT device with the assistance of an assisting node. Figures 1 to 3 schematically illustrate the cases using terminal devices and network devices as examples.

[0079] 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.

[0080] In this embodiment, the intermediate node can be a terminal device, a UE, or a network node, such as a relay, an IAB node, or a repeater, and this application is not limited thereto. The intermediate node has the function of communicating with the network device in Figure 2, and at least has the ability to send signals to and / or receive signals from the AIoT device. The auxiliary node can be a terminal device, a UE, or a network node, such as a relay, an IAB node, or a repeater, and this application is not limited thereto. The auxiliary node has the function of communicating with the network device in Figure 3, and at least has the ability to send signals to and / or receive signals from the AIoT device. The signals sent to and received from the AIoT device as described herein conform to the specifications and descriptions of AIoT devices in communication standard protocols.

[0081] 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.

[0082] 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.

[0083] This application's embodiments address access failures in DO-DTT (Device Originated-device-terminated triggered, i.e., downlink-triggered uplink sessions) scenarios, but are not limited to this.

[0084] Currently, in the event of D2R (Device to Reader) data transmission failure or contention-based random access failure, the device supports re-access. Here, "Device" refers, for example, to the aforementioned tag-type terminal device (Ambient IoT device), and "Reader" refers, for example, to the aforementioned network device (BS), intermediate node, or assisting node.

[0085] The inventors discovered that discussions prior to the existing standards did not address how to define D2R data transmission failure and contention resolution failure (or access failure), nor did they address how devices should re-access and how to determine the time-frequency resources for re-access.

[0086] This application addresses at least one of the aforementioned problems or other similar issues. The embodiments of this application are described below with reference to the accompanying drawings and specific details.

[0087] Figure 4 is a schematic diagram of the general frame structure of the slotted-ALOHA random access procedure for A-IoT. As shown in Figure 4, the A-IoT paging message triggers or corresponds to one or more slots, and one slot can contain one or more access occasions. The device can complete random access in one or more slots.

[0088] Figure 5 is a schematic diagram of the random access process in Ambient IoT. As shown in Figure 5, the process includes:

[0089] 510: The reader sends a paging message or msg0 (called message 0) or a trigger message to the device;

[0090] 520: The device sends msg1 (called message 1) to the reader, which includes ID (identifier) ​​related information;

[0091] 530: The reader sends msg2 (called message 2) to the device, which is a response to msg1;

[0092] 540: The device sends msg3 (called message 3) or D2R data transmission to the reader.

[0093] In the example in Figure 5, msg2 may be a response to msg1, or it may contain commands issued by the reader to the device.

[0094] Figure 6 is a schematic diagram of the distribution of time-frequency resources in Ambient IoT. As shown in Figure 6, an inventory round can contain multiple slots, and a slot contains multiple time-frequency resources (or occasions) for Msg1 / Msg2 / Msg3. Msg0, also known as an R2D message or a Random Access (RA) trigger message, is used to trigger random access by devices in the Msg1 occasion. Msg0 can be sent by a reader within a slot or between slots. Furthermore, Msg0 may contain RA trigger information and / or time-frequency resource information for Msg1 / Msg2 / Msg3.

[0095] First aspect of the embodiments

[0096] This application provides a method for handling access failures, described from the perspective of a first device. The first device, for example, is the device shown in Figure 5, which can be a tag-type terminal device. In this application embodiment, the second device, for example, is the reader shown in Figure 5, which can be a network device, terminal device, relay device, etc., with A-IoT capabilities, such as the network device shown in Figure 1, the intermediate node shown in Figure 2, or the auxiliary node shown in Figure 3, etc.

[0097] Figure 7 is a schematic diagram of an access failure handling method according to an embodiment of this application. As shown in Figure 7, the method includes:

[0098] 710: The first device receives first information from the second device, determines a first time-frequency resource based on the first information, and sends a second Msg1 to the second device on the first time-frequency resource.

[0099] The operation described in 710 above is an operation performed after an access failure has occurred. An access failure here includes, but is not limited to, at least one of the following situations:

[0100] Scenario 1: Before sending the second Msg1 to the second device, the first device sent the first Msg1 to the second device, but did not receive the first Msg2 (which is a response to the first Msg1) from the second device.

[0101] Scenario 2: Before sending the second Msg1 to the second device, the first device sent the first Msg1 to the second device and received the first Msg2 from the second device. However, the first device did not send the first Msg3 to the second device (the first Msg3 is a response to the first Msg2).

[0102] Scenario 3: Before sending the second Msg1 to the second device, the first device sent the first Msg1 to the second device, received the first Msg2 from the second device, and sent the first Msg3 to the second device. However, no feedback information was received from the second device, or the feedback information received from the second device was NACK (Negative-Acknowledgement).

[0103] It is worth noting that Figure 7 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 7 above.

[0104] According to the above embodiments, in the event of an access failure, i.e., when situations 1 to 3 occur, the first device performs a re-access. For example, it determines the time-frequency resource (referred to as the first time-frequency resource) for sending Msg1 (referred to as the second Msg1) based on the first information from the second device, and sends the second Msg1 to the second device on the first time-frequency resource. Thus, a specific definition of A-IoT device access failure is given, and corresponding solutions are provided for different access failure processes, thereby increasing the probability of A-IoT devices accessing the network and improving the efficiency of the A-IoT system.

[0105] In this embodiment, if the first device experiences an access failure during random access (CFRA or CBRA), the first device will attempt to re-access, i.e., it will reselect resources for transmitting Msg1 and / or Msg3 and / or D2R data, and then transmit Msg1 and / or Msg3 and / or D2R data. Here, random access by the first device refers to the first device transmitting Msg1 and / or receiving Msg2 and / or transmitting Msg3 and / or D2R data; furthermore, access failure refers to the aforementioned situation 1, 2, or 3.

[0106] In the embodiments of this application, for ease of explanation, Msg1, Msg2, and Msg3 that undergo random access are referred to as the first Msg1, the first Msg2, and the first Msg3, and Msg1, Msg2, and Msg3 that undergo re-access are referred to as the second Msg1, the second Msg2, and the second Msg3.

[0107] In some embodiments, the above situation 1 may include, for example, the first device not receiving the first Msg2 within the range of [T1, T2] after the first time reference point, or the first device not receiving the first Msg2 within the time period T3 after the first time reference point.

[0108] In the above embodiments, T1 can be the minimum value of the transmission delay plus the processing time, that is, the processing time after Msg1 is correctly received by the second device and the processing time for the second device to generate Msg2 before sending Msg2; T2 can be the maximum time range for the first device to receive Msg2, that is, the maximum time range from when the first device sends Msg1 to when it can receive Msg2. If the time exceeds T2, the first device will not receive Msg2; T3 can be the maximum time range for the first device to receive Msg2, that is, if the time exceeds T3, the first device will no longer receive Msg2.

[0109] In the above embodiments, T1, T2 and T3 may be default values ​​predefined in the standard, and / or time intervals specified in the protocol, and / or values ​​indicated or configured by the second device to the first device.

[0110] For predefined default values ​​in the standard, for example, T1 could be specified as N seconds, milliseconds, or microseconds, or T2 could be N symbols, time slots, subframes, or frames at a subcarrier spacing (SCS) of 15kHz, or R2D slice duration or D2R slice duration, or other newly defined time units, etc. Furthermore, the values ​​of T1, T2, and T3 can also be related to information such as device type and / or use case type.

[0111] The time interval specified in the protocol can be, for example, T1 is T D2R_min T2 and / or T3 are T D2R_max T D2R_min and T D2R_maxThese can be predefined default values ​​in the standard, or values ​​indicated or configured to the first device by the second device. Furthermore, the values ​​of T1, T2, and T3 can also be related to information such as message type, device type, and / or use case type.

[0112] The above T D2R_min and T D2R_max For example, it could be a time interval defined in a standard, such as T. D2R_min This refers to the minimum time between a D2R transmission and the corresponding R2D transmission following it; T D2R_max It refers to the maximum time between the D2R transmission and the corresponding R2D transmission following it.

[0113] The values ​​indicated or configured by the second device to the first device could be, for example, a table specifying the values ​​of T1, T2, and T3, which could also be related to information such as device type and / or use case type. The first device receives the corresponding index value from the table indicated or configured by the second device to determine the values ​​of T1, T2, and T3. Alternatively, the first device receives indication or configuration information from the second device, which indicates the values ​​of T1 and / or T2 and / or T3. The units of these values ​​could be N seconds, milliseconds, or microseconds, or N symbols, time slots, subframes, or frames under a certain reference subcarrier interval, or N R2D chip durations, or time in other defined time units.

[0114] In the above embodiments, the first device does not receive the first Msg2. For example, the first device may not receive any Msg2, or the first device may not receive the Msg2 (first Msg2) corresponding to the Msg1 (first Msg1) sent by the first device. The corresponding Msg2 refers to the device ID information contained therein that is consistent with the device ID information in the aforementioned Msg1 (first Msg1).

[0115] In the above embodiments, the first time reference point can be at least one of the following:

[0116] The start or end point of the time domain resource of the first Msg1 sent by the first device;

[0117] The start or end point of a time-domain resource in a time slot, specifically a Msg1 (e.g., the last Msg1).

[0118] The start or end point of the time domain resource where the trigger information is randomly accessed in a time slot. The trigger information can be an A-IoT paging message, or Msg0, etc.

[0119] The start or end point of a Msg2 time-domain resource in a time slot, for example, the start or end point of the last Msg2 time-domain resource in the time slot.

[0120] In the above embodiments, a time slot refers to the time domain range in which the random access procedure corresponding to the access failure occurs, such as the time domain range in which the time domain resource (or timing) of the first Msg1 is located.

[0121] Figure 8 is a schematic diagram of an example where the first time reference point is the end point of the time domain resource of the first Msg1 sent by the first device.

[0122] As shown in Figure 8(a), device 1 (the first device) sends Msg1 (first Msg1), and does not receive Msg2 (first Msg2) for Msg1 within the range of [T1, T2] after the end point of the time domain resource of Msg1; as shown in Figure 8(b), device 1 (the first device) sends Msg1 (first Msg1), and does not receive Msg2 (first Msg2) for Msg1 within the range of T3 after the end point of the time domain resource of Msg1.

[0123] Figure 9 is a schematic diagram of an example where the first time reference point is the end point of the time-domain resource of the last Msg1 in a time slot.

[0124] As shown in Figure 9(a), device 1 (the first device) sends Msg1 (first Msg1), and within the time slot where Msg1 is located, no Msg2 (first Msg2) is received for that Msg1 within the range of [T1, T2] after the end point of the time domain resource of the last Msg1 in the time domain; as shown in Figure 9(b), device 1 (the first device) sends Msg1 (first Msg1), and within the time slot where Msg1 is located, no Msg2 (first Msg2) is received for that Msg1 within the range of T3 after the end point of the time domain resource of the last Msg1 in the time domain.

[0125] Figure 10 is a schematic diagram of an example where the first time reference point is the end point of the time domain resource where the random access trigger information is located in a time slot. The trigger information can be an A-IoT paging message or Msg0.

[0126] As shown in Figure 10(a), device 1 (the first device) sends Msg1 (first Msg1), using the end point of the time domain resource where the paging message is located as the first time reference point. Within T3 time after the first time reference point, no Msg2 (first Msg2) for Msg1 is received. As shown in Figure 10(b), device 1 (the first device) sends Msg1 (first Msg1), using the end point of the time domain resource where Msg0 is located as the first time reference point. Within T3 time after the first time reference point, no Msg2 (first Msg2) for Msg1 is received.

[0127] In the example of Figure 10, taking the example that the first device did not receive Msg2 (first Msg2) corresponding to the above Msg1 (first Msg1) within T3 time after the first time reference point, this application is not limited to this. The example of Figure 10 can also be extended to the range of [T1, T2], similar to the examples of Figure 8 and Figure 9, which will not be repeated here.

[0128] Figure 11 is a schematic diagram of an example where the first time reference point is the end point of the time domain resource of the last Msg2 in a time slot.

[0129] As shown in Figure 11, device 1 (first device) sends Msg1 (first Msg1), taking the end point of the time domain resource of the last Msg2 in the time slot where Msg1 is located as the first time reference point. No Msg2 (first Msg2) for Msg1 is received within T3 time after the first time reference point.

[0130] In the example of Figure 11, taking the example that the first device did not receive Msg2 (first Msg2) corresponding to the above Msg1 (first Msg1) within T3 time after the first time reference point, this application is not limited to this. The example of Figure 101 can also be extended to the range of [T1, T2], similar to the examples of Figure 8 and Figure 9, which will not be repeated here.

[0131] In some embodiments, situation 2 described above may include, for example, the first device receiving the first Msg2 on the first time domain resource; however, the first device does not send the first Msg3 within the range of [T1, T2] after the first time reference point or within the time period T3 after the first time reference point.

[0132] In the above implementation, the first Msg2 received by the first device is the Msg2 corresponding to the first Msg1 it sent, that is, the device ID information contained in the first Msg2 is consistent with the device ID information in the first Msg1 it sent.

[0133] In the above embodiments, T1, T2, and T3 can be predefined default values ​​in the standard, and / or time intervals specified in the protocol, and / or values ​​indicated or configured by the second device to the first device. The details of T1, T2, and T3 have already been explained above and will not be repeated here.

[0134] In the above embodiments, the first time reference point can be at least one of the following:

[0135] The starting or ending point of the aforementioned first time-domain resource (i.e., the time-domain resource carrying the first Msg2);

[0136] The start or end point of a time-domain resource of a Msg2 (e.g., the last Msg2) in a time slot;

[0137] The start or end point of the time domain resource of the first Msg1 sent by the first device;

[0138] The start or end point of a time-domain resource in a time slot, specifically a Msg1 (e.g., the last Msg1).

[0139] The start or end point of the time domain resource where the random access trigger information is located in a time slot. The trigger information can be an A-IoT paging message or Msg0.

[0140] In the above embodiments, a time slot refers to the time domain range in which the random access procedure corresponding to the access failure occurs, such as the time domain range in which the time domain resource (or timing) of the first Msg1 is located.

[0141] Figure 12 is a schematic diagram of an example where the first time reference point is the end point of the aforementioned first time domain resource.

[0142] As shown in Figure 12, device 1 (first device) sends Msg1 (first Msg1) and receives Msg2 (first Msg2). However, the first device does not send Msg3 (first Msg3) within time T3 after the end point of the time domain resource carrying first Msg2.

[0143] The example in Figure 12 only takes the first time reference point as the end point of the first time domain resource. For other cases of the first time reference point, please refer to the examples in Figures 8 to 11, which will not be repeated here.

[0144] In some embodiments, situation 3 above may include, for example, the following: the first device sends a first Msg3 on a first time domain resource and does not receive feedback information from the second device within the range of [T1, T2] after the first time reference point; or, the first device does not receive feedback information from the second device within the time range of T3 after the first time reference point; or, the feedback information received by the first device from the second device within the range of [T1, T2] after the first time reference point is NACK; or, the feedback information received by the first device from the second device within the time range of T3 after the first time reference point is NACK.

[0145] In the above implementation, the first Msg2 received by the first device is the same as the first Msg1 it sent, that is, the device ID information contained in the first Msg2 is consistent with the device ID information in the first Msg1 it sent. Furthermore, the first Msg3 sent by the first device is the same as the first Msg2 it received. For example, the first Msg3 is a response to the first Msg2 or D2R data replying to the command in the first Msg2, etc.

[0146] In the above embodiments, T1, T2, and T3 can be predefined default values ​​in the standard, and / or time intervals specified in the protocol, and / or values ​​indicated or configured by the second device to the first device. The details of T1, T2, and T3 have already been explained above and will not be repeated here.

[0147] In the above embodiments, the first time reference point can be at least one of the following:

[0148] The starting or ending point of the aforementioned first time-domain resource (i.e., the time-domain resource carrying the first Msg3);

[0149] The start or end point of a time-domain resource of a Msg3 (e.g., the last Msg3) in a time slot;

[0150] The start or end point of a time-domain resource of a Msg2 (e.g., the last Msg2, or the Msg2 corresponding to the first Msg1) in a time slot;

[0151] The first device receives the start or end point of the time domain resource of the first Msg2;

[0152] The start or end point of the time domain resource of the first Msg1 sent by the first device;

[0153] The start or end point of a time-domain resource in a time slot, specifically a Msg1 (e.g., the last Msg1).

[0154] The start or end point of the time domain resource where the trigger information is randomly accessed in a time slot. This trigger information can be, for example, an A-IoT paging message or Msg0.

[0155] In the above embodiments, a time slot refers to the time domain range in which the random access procedure corresponding to the access failure occurs, such as the time domain range in which the time domain resource (or timing) of the first Msg1 is located.

[0156] Figure 13 is a schematic diagram of an example where the first time reference point is the end point of the aforementioned first time domain resource.

[0157] As shown in Figure 13, device 1 (the first device) sends Msg1 (first Msg1), receives Msg2 (first Msg2) corresponding to the first Msg1, and sends Msg3 (first Msg3) corresponding to the first Msg2. No feedback information is received from the second device within time T3 after the end point of the time domain resource carrying the first Msg3.

[0158] The example in Figure 13 only takes the first time reference point as the end point of the first time domain resource. For other cases of the first time reference point, please refer to the examples in Figures 8 to 11, which will not be repeated here.

[0159] In the above embodiments, the feedback information from the second device may be received after the first device sends Msg3 (first Msg3) or D2R data transmission, and is used to indicate that the second device has accurately received the aforementioned Msg3 (first Msg3) or D2R data transmission.

[0160] In the above embodiments, the feedback information from the second device is NACK. For example, it can be the corresponding NACK feedback information received from the second device after the first device sends Msg3 (first Msg3) or D2R data transmission, which is used to indicate that the second device has not received or has not accurately received the aforementioned Msg3 (first Msg3) or D2R data transmission.

[0161] The above examples illustrate several scenarios of access failure, 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 individually, or one or more of the above embodiments can be combined.

[0162] According to the above embodiments, the time limit for access failure can prevent A-IoT devices from receiving and / or listening for a long time, resulting in excessive power consumption, and can ensure the time for A-IoT devices and readers to process signals, ensuring that signals can be sent and received under normal circumstances.

[0163] In some embodiments, the first device may also receive a second Msg2 corresponding to the second Msg1 and / or send a second Msg3 or send D2R data based on the first information described above.

[0164] The following provides an exemplary description of the specific implementation of the first information.

[0165] In the embodiments of this application, the first information can be carried by higher layer signaling or by physical layer signaling.

[0166] In some embodiments, the first information is at least one of the following: A-IoT paging message, message 0 (Msg0), Msg2, used by the first device to determine the R2D transmission or message of the aforementioned first time-frequency resource.

[0167] Taking the first message as an example, the first device can reselect the time slot and the transmission timing of sending the second Msg1 (first time domain resource) according to the A-IoT paging message in order to perform re-access.

[0168] For example, the first device can re-access in a time slot following the time slot where the random access failure occurred within the current inventory round. For example, the first device can reselect a time slot based on the paging message of the current inventory round and select the resource to send Msg1 (second Msg1) in the selected time slot.

[0169] Figure 14 is a schematic diagram of an example of a first device reselecting time-domain resources based on an A-IoT paging message.

[0170] As shown in Figure 14, if an access failure occurs in the first time slot within the current inventory round, the first device can choose to send the resources of the second Msg1 in the second time slot within the current inventory round for re-access.

[0171] In the above example, for contention-based random access (RA), the first device can determine the resources for sending the second Msg1 based on the paging message or R2D messages such as Msg0, in order to perform re-access. For example, the first device can determine the resources for sending the second Msg1 according to a predefined method or according to the instructions or configuration information of the second device.

[0172] In the example above, for contention-free random access (RA), the first device can determine the resources used to send the second Msg1 based on the device ID in subsequent R2D messages such as Msg0, for re-access. For example, the first device can determine the resources used to send the second Msg1 according to a predefined method or according to the instructions or configuration information of the second device.

[0173] For example, the first device can also reselect a time slot based on the A-IoT paging message (e.g., subsequent A-IoT paging message) of a certain inventory round after the current inventory round where a random access failure occurs, and select the resource to send Msg1 (second Msg1) in the selected time slot.

[0174] For example, if a random access failure occurs in the last time slot of an inventory round, the first device can re-access in other inventory rounds following that inventory round; or, for another example, if a random access failure occurs in any time slot of an inventory round, the first device can re-access in other inventory rounds following that inventory round.

[0175] Figure 15 is a schematic diagram of another example of the first device reselecting time-domain resources based on the A-IoT paging message.

[0176] As shown in Figure 15, if an access failure occurs in the first time slot of the current inventory round, the first device can choose to send the resources of the second Msg1 in a certain time slot of the next inventory round to re-access.

[0177] In the above example, for contention-based random access (RA), the first device can determine the resources for sending the second Msg1 based on the paging message or R2D message such as Msg0, in order to perform re-access. For example, the first device can determine the resources for sending the second Msg1 according to a predefined method or according to the instructions or configuration information of the second device.

[0178] In the above example, for contention-free random access (RA), the first device can determine the resources used to send the second Msg1 based on the device ID in subsequent paging messages or R2D messages such as Msg0, in order to perform re-access. For example, the first device can determine the resources used to send the second Msg1 according to a predefined method or according to the instructions or configuration information of the second device.

[0179] Taking Msg0 as an example, the first device can reselect the time slot and the transmission timing (first time domain resource) for sending the second Msg1 based on Msg0 (or R2D message, RA trigger message, etc.) to perform re-access.

[0180] For example, if a random access failure occurs in a time slot of an inventory round, and the first device receives another Msg0 message after that time slot, it will attempt to re-access the device in the time slot where Msg0 was located.

[0181] The aforementioned Msg0 or R2D message can be a Msg0 or R2D message in the current inventory round, or it can be a Msg0 or R2D message in another inventory round.

[0182] Figure 16 is a schematic diagram of an example of the first device reselecting time-domain resources based on Msg0.

[0183] As shown in Figure 16, if an access failure occurs in the first time slot within the current inventory round, the first device can select the resources used to send the second Msg1 in the second time slot within the current inventory round for re-access.

[0184] In the above example, for contention-based random access (RA), the first device can determine the resources for sending the second Msg1 based on the paging message or R2D message such as Msg0, in order to perform re-access. For example, the first device can determine the resources for sending the second Msg1 according to a predefined method or according to the instructions or configuration information of the second device.

[0185] In the above example, for contention-free random access (RA), the first device can determine the resources used to send the second Msg1 based on the device ID in subsequent paging messages or R2D messages such as Msg0, in order to perform re-access. For example, the first device can determine the resources used to send the second Msg1 according to a predefined method or according to the instructions or configuration information of the second device.

[0186] Taking Msg2 as an example, the first device can reselect the time slot and the transmission timing (first time domain resource) for sending the second Msg1 and / or the second Msg3 based on Msg2 to perform re-access.

[0187] For example, if a random access failure occurs in a time slot of an inventory round, the first device will receive the corresponding Msg2 (first Msg2) in that time slot and then re-access the device, sending the second Msg3 or D2R data transmission.

[0188] The aforementioned second Msg2 can be Msg2 carrying a device identifier (random identifier) ​​corresponding to the second Msg1 sent by the first device.

[0189] Figure 17 is a schematic diagram of an example of the first device reselecting time-domain resources based on Msg2.

[0190] As shown in Figure 17(a), an access failure occurred in the first time slot within the current inventory round. This access failure could be due to the first device not sending Msg1, or the first device sending Msg1 but the second device not receiving it correctly, resulting in the first device not receiving Msg2. The first device can, within the current time slot within the current inventory round, after receiving the corresponding first Msg2, select resources for sending the second Msg1, the second Msg3, or D2R data transmission based on the first Msg2 to complete the re-access.

[0191] As shown in Figure 17(b), an access failure occurred in the first time slot within the current inventory round. This access failure occurred because the first device received Msg2 but did not send the corresponding Msg3, or the first device sent Msg3 but the second device did not receive it correctly, resulting in the first device not receiving the corresponding feedback. The first device can, within the current time slot within the current inventory round, after receiving the corresponding first Msg2, select resources for sending the second Msg1, the second Msg3, or D2R data transmission based on the first Msg2 to complete the re-access.

[0192] Taking the first information as an example of other R2D messages or R2D transmissions, such as R2D messages or R2D transmissions specifically used to trigger the first device to re-access and determine re-access resources (first time-frequency resources), the first device can re-select time slots and transmission timing (time domain resources) for sending the second Msg1 and / or the second Msg3 based on the R2D message or R2D transmission to re-access.

[0193] In the above embodiments, the first information may be re-access trigger information, that is, indication information from the second device to instruct the first device to re-access, and / or time-frequency resource information for re-access, etc. For example, after receiving the first information, the first device performs re-access based on the first information and sends a second Msg1 and / or a second Msg3. The first information may or may not include device identification information.

[0194] The following examples illustrate the implementation of the first information in cases 1 to 3 of the aforementioned access failure.

[0195] Taking the aforementioned scenario 1 as an example, if the first device does not receive the first Msg2 after sending the first Msg1, the first device can determine the resources for sending the second Msg1 based on the A-IoT paging message or Msg0 or other R2D messages or transmissions, so as to re-access.

[0196] Taking the aforementioned scenario 2 as an example, after the first device sends the first Msg1, it receives the corresponding first Msg2 but does not send the corresponding first Msg3. The first device can determine the resources for sending the second Msg1 based on the A-IoT paging message, Msg0, or other R2D messages or transmissions to enable re-access; or, the first device can determine the resources for sending the second Msg3 based on the A-IoT paging message, Msg0, or other R2D messages or transmissions to enable re-access.

[0197] Taking scenario 3 above as an example, after sending the first Msg1, the first device receives the corresponding first Msg2 and sends the corresponding first Msg3. It does not receive any feedback information from the second device, or the feedback information received from the second device is NACK. The first device can determine the resources for sending the second Msg1 based on the A-IoT paging message, Msg0, or other R2D messages or transmissions to re-access; or, the first device can determine the resources for sending the second Msg3 based on the A-IoT paging message, Msg0, or other R2D messages or transmissions to re-access.

[0198] In some embodiments, the first information includes at least one of the following: random access trigger indication information, random access time-frequency resource information, and device identification information of the first device. That is, the first device makes corresponding indications through the indication method of the trigger information, the indication method of the re-access time-frequency resources, and / or the device identification information.

[0199] In the above embodiments, the indication method for trigger information can be to indicate whether the first device should re-access using 1 bit of information. For example, a bit of "0" indicates that the first device should not re-access, and a bit of "1" indicates that the first device should re-access. Alternatively, the first device can be instructed to re-access based on the message type. For example, the R2D message carries the message type code or index corresponding to the re-access trigger information, indicating that the R2D message is re-access trigger information, and the first device should re-access after receiving the R2D message. Re-access can also be implicitly triggered. For example, the R2D message contains resource information for re-access, and the first device should re-access after receiving the R2D message.

[0200] In the above embodiments, the indication method for re-accessed time and frequency resources is described.

[0201] For time-domain resources, the time-domain resource information for the first device to re-access, i.e., the time-domain resource information for the first device to send the second Msg1 and / or the second Msg3, includes at least one of the following:

[0202] The start or start offset of the time-domain resource; the start or start offset of the time-domain resource may be indicated by the first information or may be pre-defined by the standard.

[0203] The duration or time offset of a time-domain resource; the duration of the time-domain resource may be indicated by the first information or may be pre-defined by the standard.

[0204] The end of the time-domain resource; the end of the time-domain resource may be indicated by the first information or may be pre-defined by the standard.

[0205] The period of the time-domain resource; the period of the time-domain resource can be indicated by the first information or it can be pre-defined by the standard.

[0206] This application does not limit the unit of the time-domain resource information (referred to as the time-domain resource time unit). For example, the time-domain resource time unit can be a chip duration or length of D2R transmission, where a chip is the duration of a codeword after the information bits of the D2R transmission are modulated. After OOK (On-Off Keying) modulation, the duration of a low level of a chip "0" or a high level of a chip "1" is a chip duration or length. Alternatively, the time-domain resource time unit can be absolute time, such as T seconds, milliseconds, or microseconds. Alternatively, the time-domain resource time unit can be a frame, subframe, time slot, symbol, etc. defined by the NR system. Alternatively, the time-domain resource time unit can be a time unit newly defined by the ambient IoT system.

[0207] In the above embodiments, the start of the time domain resource refers to the time offset from the second time reference point by T_start. T_start can be a predefined value or a value indicated or configured by the second device. The time unit of T_start can be any of the aforementioned, which will not be elaborated here.

[0208] The second reference point can be, for example, the start or end point of the time domain resource of the first information, the start or end point of the time domain resource of the second information, the start or end point of the time domain resource of the paging message, the start or end point of the time domain resource of Msg0, or the start or end point of the time domain resource of Msg2.

[0209] In the above embodiments, the end of the time domain resource refers to the time offset T_end after the third time reference point. T_end can be a predefined value or a value configured after the second device instruction. The time unit of T_end can be any of the aforementioned ones, which will not be elaborated here.

[0210] The third reference point can be the starting point of the aforementioned time-domain resource, the starting or ending point of the time-domain resource of the first information, the starting or ending point of the time-domain resource of the second information, the starting or ending point of the time-domain resource of the paging message, the starting or ending point of the time-domain resource of Msg0, or the starting or ending point of the time-domain resource of Msg2.

[0211] For frequency domain resources, the frequency domain resource information for re-access by the first device, i.e., the frequency domain resource information for the first device to send the second Msg1 and / or the second Msg3, includes at least one of the following:

[0212] The start of the frequency domain resource; the start of the frequency domain resource can be determined in a standard predefined manner or by a method indicated or configured by a second device.

[0213] The frequency offset of the frequency domain resource; the frequency offset of the frequency domain resource can be determined in a standard predefined manner, or it can be determined by a second device instruction or configuration.

[0214] The size of the frequency domain resource or the transmission bandwidth of the D2R signal; the size of the frequency domain resource or the transmission bandwidth of the D2R signal can be determined in a standard predefined manner, or it can be determined by a second device instruction or configuration.

[0215] The transmission center frequency of the D2R signal; the transmission center frequency of the D2R signal can be determined in a standard predefined manner, or it can be determined by the indication or configuration of the second device.

[0216] The size of the protection band; the size of the protection band can be determined in a standard predefined manner or by a method indicated or configured by a second device.

[0217] The bandwidth number, bandwidth ID, channel ID, frequency domain resource unit ID, or frequency domain resource unit index can be determined in a standard predefined manner or by a method indicated or configured by a second device.

[0218] The specific implementation methods of the first information have been described above by way of example, 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.

[0219] In some embodiments, the first device may also receive second information sent by the second device, and determine, based on the second information, to send the second Msg1 to the second device on the first time-frequency resource.

[0220] In the above embodiments, in some possible implementations, the first device receives first information from the second device. This first information is used to trigger the first device to re-access, and it is also used to determine the time-frequency resources for re-access (i.e., the time-frequency resources for sending the second Msg1 and / or the second Msg3). In other words, the first information is used both to trigger the first device to re-access and to indicate the time-frequency resources for re-access. The implementation of this first information has already been described above and will not be repeated here.

[0221] In the above embodiments, in some other possible implementations, the first device receives first information and second information from the second device. The first information is used to determine the time-frequency resources for re-access (i.e., the time-frequency resources for sending the second Msg1 and / or the second Msg3), and the second information is used to trigger the first device to perform re-access. That is, the first device prepares to perform re-access after receiving the second information. In other words, the first information is used to indicate resources, and the second information is used to trigger re-access.

[0222] In the above embodiments, the second information may be information specifically used to trigger re-access. For example, the second information may be an A-IoT paging message or Msg0 or Msg2 or R2D message or R2D transmission specifically used to indicate the resources used for re-access (different from the A-IoT paging message or Msg0 or Msg2 or R2D message or R2D transmission in the normal random access process). After receiving the first information, the first device determines the resources used for re-access. Here, the first information may be the first information in the aforementioned embodiments, but this application is not limited to this. The first information may also be an A-IoT paging message or Msg0 or Msg2 or R2D message or R2D transmission specifically used to indicate the resources used for re-access (different from the A-IoT paging message or Msg0 or Msg2 or R2D message or R2D transmission in the normal random access process).

[0223] Figure 18 is a schematic diagram of an example of the first and second information. In the example of Figure 18, the second information is information specifically used to trigger reconnection, and the first information is a paging message.

[0224] Figure 19 is a schematic diagram of another example of the first and second information. In the example of Figure 19, the second information is information specifically used to trigger reconnection, and the first information is Msg0.

[0225] The above are just examples. The first and second information can also be combined in other ways. For example, the second information can be used to trigger reconnection while the first information is Msg2, etc.

[0226] 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.

[0227] As can be seen from the above embodiments, according to the embodiments of this application, a specific definition of A-IoT device access failure is given, and corresponding solutions are given for different access failure processes, thereby increasing the probability of A-IoT devices accessing the network and improving the efficiency of the A-IoT system.

[0228] Second aspect of the embodiments

[0229] This application provides a method for handling access failures, described from the perspective of a second device. The second device can be the aforementioned network device, intermediate node, or auxiliary node. The embodiments of the second aspect can be combined with the embodiments of the first aspect, and the contents that are the same as those in the embodiments of the first aspect will not be repeated.

[0230] Figure 20 is a schematic diagram of an access failure handling method according to an embodiment of this application. As shown in Figure 20, the method includes:

[0231] 2010: The second device sends the first information to the first device and receives the second Msg1 from the first device on the first time-frequency resource.

[0232] The above-mentioned operation in 2010 was performed after an access failure occurred. This access failure includes, but is not limited to, at least one of the following situations:

[0233] Case 1: Before the second device receives the second Msg1 from the first device, the first device sends the first Msg1 to the second device. The second device either does not receive the first Msg1 or does not send the first Msg2 after receiving the first Msg1.

[0234] Scenario 2: Before the second device receives the second Msg1 from the first device, the second device receives the first Msg1 from the first device and sends the first Msg2 back to the first device. The second device does not receive the first Msg3 from the first device. The first Msg3 is a response to the first Msg2.

[0235] Case 3: Before the second device receives the second Msg1 from the first device, the second device receives the first Msg1 from the first device and sends the first Msg2 back to the first device, and receives the first Msg3 from the first device, but does not send any feedback information to the first device or sends a NACK feedback information to the first device.

[0236] It is worth noting that Figure 20 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 20 above.

[0237] In some embodiments, the second device may also send a second Msg2 corresponding to the second Msg1 to the first device, and / or receive a second Msg3 or D2R data sent by the first device.

[0238] In some embodiments, the first information is at least one of the following: A-IoT paging message, Msg0, Msg2, used by the first device to determine the R2D transmission or message of the first time-frequency resource.

[0239] In some embodiments, the first information includes at least one of the following: random access trigger indication information, random access time and frequency resource information, and device identifier related information of the first device.

[0240] In some embodiments, the first information is carried by higher-layer signaling and / or physical-layer signaling.

[0241] In some embodiments, the second device may also send a second message to the first device, the first device determining, based on the second message, to send a second Msg1 to the second device on a first time-frequency resource.

[0242] The specific implementation methods for the first and second information have been described in the embodiments of the first aspect, and their contents are incorporated herein by reference, and will not be repeated here.

[0243] 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.

[0244] As can be seen from the above embodiments, according to the embodiments of this application, a specific definition of A-IoT device access failure is given, and corresponding solutions are given for different access failure processes, thereby increasing the probability of A-IoT devices accessing the network and improving the efficiency of the A-IoT system.

[0245] Third aspect of the embodiments

[0246] This application provides a processing device for access failure. This device may be, for example, a first device, or one or more components or parts configured within the first device. The first device may be, for example, a tag-type terminal device; details identical to those in the first aspect of the embodiment will not be repeated.

[0247] Figure 21 is a schematic diagram of an access failure processing device according to an embodiment of this application. As shown in Figure 21, the signal receiving device 2100 of this embodiment includes a receiving unit 2110, a transmitting unit 2120, and a processing unit 2130.

[0248] The receiving unit 2110 receives the first information from the second device, the processing unit 2130 determines the first time-frequency resource based on the first information, and the sending unit 2120 sends the second Msg1 to the second device on the first time-frequency resource.

[0249] in,

[0250] Before sending the second Msg1 to the second device, the sending unit 2120 sent the first Msg1 to the second device. The receiving unit 2110 did not receive the first Msg2 from the second device. The first Msg2 is a response to the first Msg1; and / or,

[0251] Before sending the second Msg1 to the second device, the sending unit 2120 sent the first Msg1 to the second device. The receiving unit 2110 received the first Msg2 from the second device. The sending unit 2120 did not send the first Msg3 to the second device; the first Msg3 is a response to the first Msg2. And / or,

[0252] Before sending the second Msg1 to the second device, the sending unit 2120 sends the first Msg1 to the second device. The receiving unit 2110 receives the first Msg2 from the second device. The sending unit 2120 sends the first Msg3 to the second device. The receiving unit 2110 does not receive any feedback information from the second device or receives a NACK from the second device.

[0253] In some embodiments, before sending the second Msg1 to the second device, the sending unit 2120 sends the first Msg1 to the second device. The receiving unit 2110 does not receive the first Msg2 from the second device. The first Msg2 is a response to the first Msg1, including:

[0254] The receiving unit 2110 does not receive the first Msg2 within the range of [T1, T2] after the first time reference point; or, the receiving unit 2110 does not receive the first Msg2 within the time T3 after the first time reference point.

[0255] In the above embodiments, the first time reference point can be at least one of the following:

[0256] The start or end point of the time domain resource of the first Msg1 sent by the sending unit 2120;

[0257] The start or end point of a time-domain resource of Msg1 in a time slot;

[0258] The start or end point of the time domain resource where the random access trigger information is located in a time slot;

[0259] The start or end point of a time-domain resource of Msg2 in a time slot.

[0260] In other embodiments, before sending the second Msg1 to the second device, the sending unit 2120 sends the first Msg1 to the second device. The receiving unit 2110 receives the first Msg2 from the second device. The sending unit 2120 does not send the first Msg3 to the second device. The first Msg3 is a response to the first Msg2, including:

[0261] The receiving unit 2110 receives the first Msg2 on the first time domain resource;

[0262] The receiving unit 2110 does not send the first Msg3 within the range of [T1, T2] after the first time reference point or within the time period T3 after the first time reference point.

[0263] In the above embodiments, the first time reference point can be at least one of the following:

[0264] The starting or ending point of the first time domain resource;

[0265] The start or end point of a time-domain resource of Msg2 in a time slot;

[0266] The start or end point of the time domain resource of the first Msg1 sent by the sending unit 2120;

[0267] The start or end point of a time-domain resource of Msg1 in a time slot;

[0268] The start or end point of the time domain resource where the random access trigger information is located in a time slot.

[0269] In some other embodiments, before sending the second Msg1 to the second device, the sending unit 2120 sends the first Msg1 to the second device, the receiving unit 2110 receives the first Msg2 from the second device, the sending unit 2120 sends the first Msg3 to the second device, and the receiving unit 2110 does not receive any feedback information from the second device or receives a NACK from the second device, including:

[0270] The sending unit 2120 sends a first Msg3 on the first time domain resource; the receiving unit 2110 does not receive feedback information from the second device within the range of [T1, T2] after the first time reference point; or, the receiving unit 2110 does not receive feedback information from the second device within the time range of T3 after the first time reference point; or, the feedback information received by the receiving unit 2110 from the second device within the range of [T1, T2] after the first time reference point is NACK; or, the feedback information received by the receiving unit 2110 from the second device within the time range of T3 after the first time reference point is NACK.

[0271] In the above embodiments, the first time reference point can be at least one of the following:

[0272] The starting or ending point of the first time domain resource;

[0273] The start or end point of a time-domain resource of Msg3 in a time slot;

[0274] The start or end point of a time-domain resource of Msg2 in a time slot;

[0275] The receiving unit 2110 receives the start or end point of the time domain resource of the first Msg2;

[0276] The start or end point of the time domain resource of the first Msg1 sent by the sending unit 2120;

[0277] The start or end point of a time-domain resource of Msg1 in a time slot;

[0278] The start or end point of the time domain resource where the random access trigger information is located in a time slot.

[0279] In some embodiments, the receiving unit 2110 may also receive the second Msg2 corresponding to the second Msg1 according to the first information.

[0280] In some embodiments, the transmitting unit 2120 may also transmit a second Msg3 or transmit D2R data.

[0281] In some embodiments, the first information is at least one of the following: an A-IoT paging message, message 0 (Msg0), message 2, used by the first device to determine an R2D transmission or message for a first time-frequency resource.

[0282] In some embodiments, the first information includes at least one of the following: random access trigger indication information, random access time and frequency resource information, and device identifier related information of the first device.

[0283] In some embodiments, the first information is carried by higher-layer signaling and / or physical-layer signaling.

[0284] In some embodiments, the receiving unit 2110 may also receive second information sent by the second device, and the processing unit 2130 determines to send a second Msg1 to the second device on the first time-frequency resource based on the second information.

[0285] In the embodiments of this application, T1, T2, and T3 may be default values ​​predefined in the standard, and / or time intervals specified in the protocol, and / or values ​​indicated or configured by the second device to the first device.

[0286] 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.

[0287] 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 access failure processing device 2100 may also include other components or modules, and for details regarding these components or modules, please refer to related technologies.

[0288] Furthermore, for simplicity, Figure 21 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.

[0289] As can be seen from the above embodiments, according to the embodiments of this application, a specific definition of A-IoT device access failure is given, and corresponding solutions are given for different access failure processes, thereby increasing the probability of A-IoT devices accessing the network and improving the efficiency of the A-IoT system.

[0290] Fourth aspect of the embodiment

[0291] This application provides a processing device for access failure. This device may be, for example, a second device, or one or more components or parts configured on the second device. The second device may be the aforementioned network device, intermediate node, or auxiliary node. Contents identical to those in the embodiments of the first to third aspects will not be repeated.

[0292] Figure 22 is another schematic diagram of an access failure processing device according to an embodiment of this application. As shown in Figure 22, the access failure processing device 2200 includes a sending unit 2210 and a receiving unit 2220.

[0293] The sending unit 2210 sends first information to the first device, and the receiving unit 2220 receives the second Msg1 from the first device on the first time-frequency resource;

[0294] in,

[0295] Before receiving unit 2220 receives the second Msg1 from the first device, the first device sends the first Msg1 to the second device, and receiving unit 2220 does not receive the first Msg1, or receiving unit 2220 receives the first Msg1 but sending unit 2210 does not send the first Msg2; and / or,

[0296] Before receiving unit 2220 receives the second Msg1 from the first device, receiving unit 2220 receives the first Msg1 from the first device, and sending unit 2210 sends the first Msg2 back to the first device. Receiving unit 2220 does not receive the first Msg3 from the first device; the first Msg3 is a response to the first Msg2. And / or,

[0297] Before receiving unit 2220 receives the second Msg1 from the first device, receiving unit 2220 receives the first Msg1 from the first device, and sending unit 2210 sends the first Msg2 to the first device, and receiving unit 2220 receives the first Msg3 from the first device, and sending unit 2210 does not send feedback information to the first device or the feedback information sent by sending unit 2210 to the first device is NACK.

[0298] In some embodiments, the sending unit 2210 sends a second Msg2 corresponding to the second Msg1 to the first device, and / or the receiving unit 2220 receives the second Msg3 or D2R data sent by the first device.

[0299] In some embodiments, the first information is at least one of the following: A-IoT paging message, Msg0, Msg2, used by the first device to determine the R2D transmission or message of the first time-frequency resource.

[0300] In some embodiments, the first information includes at least one of the following: random access trigger indication information, random access time and frequency resource information, and device identifier related information of the first device.

[0301] In some embodiments, the first information is carried by higher-layer signaling and / or physical-layer signaling.

[0302] In some embodiments, the sending unit 2210 sends second information to the first device, and the first device determines to send a second Msg1 to the second device on the first time-frequency resource based on the second information.

[0303] In some embodiments, as shown in FIG22, the device 2200 further includes a processing unit 2230.

[0304] The processing unit 2230 is used to control the operation of the transmitting unit 2210 and the receiving unit 2220.

[0305] 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.

[0306] 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 access failure processing device 2200 may also include other components or modules, and for details regarding these components or modules, please refer to related technologies.

[0307] Furthermore, for simplicity, Figure 22 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.

[0308] As can be seen from the above embodiments, according to the embodiments of this application, a specific definition of A-IoT device access failure is given, and corresponding solutions are given for different access failure processes, thereby increasing the probability of A-IoT devices accessing the network and improving the efficiency of the A-IoT system.

[0309] Fifth aspect of the embodiment

[0310] 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.

[0311] 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.

[0312] The relevant content regarding the first and second devices has been described in the embodiments of the first to fourth aspects, and its content is incorporated herein by reference and will not be repeated here.

[0313] This application also provides a terminal device, but the application is not limited to this and may also include other devices.

[0314] Figure 23 is a schematic diagram of a terminal device according to an embodiment of this application. As shown in Figure 23, the terminal device 2300 may include a processor 2310 and a memory 2320; for example, the memory 2320 stores data and programs and is coupled to the processor 2310. 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.

[0315] For example, processor 2310 may be configured to execute a program to implement the method described in the embodiments of the first or second aspect.

[0316] As shown in Figure 23, the terminal device 2300 may further include a communication module 2330; it may or may not have a power supply. It is worth noting that the terminal device 2300 is not necessarily required to include all the components shown in Figure 23; these components are not essential. Furthermore, the terminal device 2300 may also include components not shown in Figure 23, which can be referred to in the prior art.

[0317] This application also provides a network device, such as a base station, but this application is not limited to this and may also include other network devices.

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

[0319] For example, processor 2410 may be configured to execute a program to implement the method described in the embodiments of the second aspect.

[0320] In addition, as shown in Figure 24, network device 2400 may also include transceiver 2440 and antenna 2450, 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 2400 does not necessarily include all the components shown in Figure 24; furthermore, network device 2400 may also include components not shown in Figure 24, which can be referred to in the prior art.

[0321] This application also provides a computer program, wherein when the program is executed in a terminal device, the program causes the terminal device to perform the method described in the embodiments of the first or second aspect.

[0322] This application also provides a storage medium storing a computer program, wherein the computer program causes a terminal device to perform the methods described in the embodiments of the first or second aspect.

[0323] This application also provides a computer program, wherein when the program is executed in a network device, the program causes the network device to perform the method described in the second aspect of the embodiment.

[0324] This application also provides a storage medium storing a computer program, wherein the computer program causes a network device to perform the method described in the second aspect of the embodiment.

[0325] 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.

[0326] 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.

[0327] 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.

[0328] 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.

[0329] 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.

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

[0331] 1. A method for handling access failures, applied to a first device, wherein the method includes:

[0332] The first device receives first information from the second device (reader), determines a first time-frequency resource based on the first information, and sends a second message 1 (Msg1) to the second device on the first time-frequency resource.

[0333] in,

[0334] Before sending the second Msg1 to the second device, the first device sent the first Msg1 to the second device and did not receive a first message 2 (Msg2) from the second device. The first Msg2 is a response to the first Msg1; and / or,

[0335] Before sending the second Msg1 to the second device, the first device sent the first Msg1 to the second device and received the first Msg2 in response from the second device. The first device did not send the first message 3 (Msg3) to the second device; the first Msg3 was a response to the first Msg2; and / or,

[0336] Before sending the second Msg1 to the second device, the first device sent the first Msg1 to the second device, received the first Msg2 from the second device, sent the first Msg3 to the second device, and did not receive any feedback from the second device or received a NACK from the second device.

[0337] 2. A method for handling access failures, applied to a second device (reader), wherein the method includes:

[0338] The second device sends a first message to the first device and receives a second Msg1 from the first device on the first time-frequency resource.

[0339] in,

[0340] Before the second device receives the second Msg1 from the first device, the first device sends a first Msg1 to the second device, and the second device either does not receive the first Msg1 or receives the first Msg1 but does not send a first Msg2; and / or,

[0341] Before the second device receives the second Msg1 from the first device, the second device receives the first Msg1 from the first device and sends the first Msg2 back to the first device. The second device does not receive the first Msg3 from the first device, and the first Msg3 is a response to the first Msg2; and / or,

[0342] Before the second device receives the second Msg1 from the first device, the second device receives the first Msg1 from the first device and sends a first Msg2 back to the first device, and receives the first Msg3 from the first device, but does not send any feedback information to the first device or sends a NACK feedback information to the first device.

[0343] 3. A terminal device comprising a memory and a processor, the memory storing a computer program and the processor being configured to execute the computer program to implement the method as described in Appendix 1 or Appendix 2.

[0344] 4. A network device comprising a memory and a processor, the memory storing a computer program and the processor being configured to execute the computer program to implement the method as described in Appendix 2.

[0345] 5. A computer program product comprising at least a computer program that, when executed by a processor, causes a terminal device to perform the method as described in Appendix 1 or Appendix 2.

[0346] 6. A computer program product comprising at least a computer program that, when executed by a processor, causes a network device to perform the method as described in Appendix 2.

Claims

1. A processing apparatus for access failure, configured in a first device, wherein, The device includes: a receiving unit, a processing unit, and a transmitting unit. The receiving unit receives first information from the second device (reader), the processing unit determines a first time-frequency resource based on the first information, and the sending unit sends a second message 1 (Msg1) to the second device on the first time-frequency resource. in, Before sending the second Msg1 to the second device, the sending unit sent the first Msg1 to the second device. The receiving unit did not receive the first message 2 (Msg2) from the second device. The first Msg2 is a response to the first Msg1; and / or, Before sending the second Msg1 to the second device, the sending unit sent the first Msg1 to the second device. The receiving unit received the first Msg2 from the second device. The sending unit did not send the first message 3 (Msg3) to the second device. The first Msg3 is a response to the first Msg2; and / or, Before sending the second Msg1 to the second device, the sending unit sent the first Msg1 to the second device. The receiving unit received the first Msg2 from the second device. The sending unit sent the first Msg3 to the second device. The receiving unit did not receive any feedback information from the second device or the feedback information received from the second device was NACK.

2. The apparatus according to claim 1, wherein, Before sending the second Msg1 to the second device, the sending unit sent the first Msg1 to the second device. The receiving unit did not receive the first Msg2 from the second device. The first Msg2 is a response to the first Msg1, including: The receiving unit did not receive the first Msg2 within the range [T1, T2] after the first time reference point; or... The receiving unit did not receive the first Msg2 within T3 time after the first time reference point.

3. The apparatus according to claim 2, wherein, The first time reference point is at least one of the following: The starting point or ending point of the time domain resource of the first Msg1 sent by the sending unit; The start or end point of a time-domain resource of Msg1 in a time slot; The start or end point of the time domain resource where the random access trigger information is located in a time slot; The start or end point of a time-domain resource of Msg2 in a time slot.

4. The apparatus according to claim 1, wherein, Before sending the second Msg1 to the second device, the sending unit sent the first Msg1 to the second device. The receiving unit received the first Msg2 from the second device. The sending unit did not send the first Msg3 to the second device. The first Msg3 is a response to the first Msg2, including: The receiving unit receives the first Msg2 on the first time domain resource; The receiving unit did not send the first Msg3 within the range of [T1, T2] after the first time reference point or within the time period T3 after the first time reference point.

5. The apparatus according to claim 4, wherein, The first time reference point is at least one of the following: The start or end point of the first time-domain resource; The start or end point of a time-domain resource of Msg2 in a time slot; The starting point or ending point of the time domain resource of the first Msg1 sent by the sending unit; The start or end point of a time-domain resource of Msg1 in a time slot; The start or end point of the time domain resource where the random access trigger information is located in a time slot.

6. The apparatus according to claim 1, wherein, Before sending the second Msg1 to the second device, the sending unit sends the first Msg1 to the second device. The receiving unit receives the first Msg2 from the second device. The sending unit sends the first Msg3 to the second device. The receiving unit either does not receive any feedback from the second device or receives a NACK from the second device, including: The sending unit sends the first Msg3 on the first time domain resource; The receiving unit does not receive feedback information from the second device within the range [T1, T2] after the first time reference point; or, the receiving unit does not receive feedback information from the second device within the time range T3 after the first time reference point; or, the feedback information received by the receiving unit from the second device within the range [T1, T2] after the first time reference point is NACK; or, the feedback information received by the receiving unit from the second device within the time range T3 after the first time reference point is NACK.

7. The apparatus according to claim 6, wherein, The first time reference point is at least one of the following: The start or end point of the first time-domain resource; The start or end point of a time-domain resource of Msg3 in a time slot; The start or end point of a time-domain resource of Msg2 in a time slot; The receiving unit receives the start or end point of the time-domain resources of the first Msg2; The starting point or ending point of the time domain resource of the first Msg1 sent by the sending unit; The start or end point of a time-domain resource of Msg1 in a time slot; The start or end point of the time domain resource where the random access trigger information is located in a time slot.

8. The apparatus according to claim 1, wherein, The receiving unit receives the second Msg2 corresponding to the second Msg1 according to the first information, and / or the sending unit sends the second Msg3 or sends D2R data according to the first information.

9. The apparatus according to claim 1, wherein, The first information is at least one of the following: A-IoT paging message, message 0 (Msg0), Msg2, used by the first device to determine the R2D transmission or message of the first time-frequency resource.

10. The apparatus according to claim 1, wherein, The first information includes at least one of the following: random access trigger indication information, random access time and frequency resource information, and device identifier related information of the first device.

11. The apparatus according to claim 1, wherein, The first information is carried by higher-layer signaling and / or physical-layer signaling.

12. The apparatus according to claim 1, wherein, The receiving unit receives the second information sent by the second device, and the processing unit determines, based on the second information, to send the second Msg1 to the second device on the first time-frequency resource.

13. The apparatus according to claim 2, wherein, T1, T2, and T3 are predefined default values ​​in the standard, and / or time intervals specified in the protocol, and / or values ​​indicated or configured by the second device to the first device.

14. A processing apparatus for access failure, configured in a second device (reader), wherein, The device includes: a transmitting unit and a receiving unit. The transmitting unit sends first information to the first device, and the receiving unit receives the second Msg1 from the first device on the first time-frequency resource. in, Before the receiving unit receives the second Msg1 from the first device, the first device sends a first Msg1 to the second device, and the receiving unit either does not receive the first Msg1 or, after receiving the first Msg1, does not send a first Msg2; and / or, Before the receiving unit receives the second Msg1 from the first device, the receiving unit receives the first Msg1 from the first device, and the sending unit sends the first Msg2 back to the first device. The receiving unit does not receive the first Msg3 from the first device, and the first Msg3 is a response to the first Msg2; and / or, Before the receiving unit receives the second Msg1 from the first device, the receiving unit receives the first Msg1 from the first device, and the sending unit feeds back the first Msg2 to the first device, and the receiving unit receives the first Msg3 from the first device, and the sending unit does not send feedback information to the first device or sends feedback information to the first device as NACK.

15. The apparatus according to claim 14, wherein, The sending unit sends a second Msg2 corresponding to the second Msg1 to the first device, and / or the receiving unit receives the second Msg3 or D2R data sent by the first device.

16. The apparatus according to claim 14, wherein, The first information is at least one of the following: A-IoT paging message, Msg0, Msg2, used by the first device to determine the R2D transmission or message of the first time-frequency resource.

17. The apparatus according to claim 14, wherein, The first information includes at least one of the following: random access trigger indication information, random access time and frequency resource information, and device identifier related information of the first device.

18. The apparatus according to claim 14, wherein, The first information is carried by higher-layer signaling and / or physical-layer signaling.

19. The apparatus according to claim 14, wherein, The sending unit sends second information to the first device, and the first device determines, based on the second information, to send the second Msg1 to the second device on the first time-frequency resource.

20. A communication system, comprising: First equipment and second equipment. The second device sends the first information to the first device; The first device receives first information from the second device, determines a first time-frequency resource based on the first information, and sends a second Msg1 to the second device on the first time-frequency resource; in, Before sending the second Msg1 to the second device, the first device sent the first Msg1 to the second device and did not receive a first message 2 (Msg2) from the second device. The first Msg2 is a response to the first Msg1; and / or, Before sending the second Msg1 to the second device, the first device sent the first Msg1 to the second device and received the first Msg2 from the second device. The first device did not send the first message 3 (Msg3) to the second device. The first Msg3 is a response to the first Msg2. And / or, Before sending the second Msg1 to the second device, the first device sent the first Msg1 to the second device, received the first Msg2 from the second device, sent the first Msg3 to the second device, and did not receive any feedback from the second device or received a NACK from the second device.

Images