Access method, terminal device, network device, and storage medium

Abstract

Embodiments of the present disclosure provide an access method, a terminal device, a network device, and a storage medium. The method comprises: a terminal device receiving a first indication message repeatedly sent by a network device, and, upon determining that preemptive access needs to be initiated via a preemption slot, sending a first request message within the preemption slot, wherein one preemption slot is included between two adjacent first indication messages; the terminal device receiving a first response message sent by the network device, wherein the first response message is used for indicating a first quantity; and the terminal device determining a second quantity not greater than the first quantity, counting first feedback slots on the basis of a received second indication message repeatedly sent by the network device, and, when a count value of the first feedback slots reaches the second quantity, sending access information to the network device.

Description

Access method, terminal device, network device and storage medium

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This disclosure claims priority to Chinese Patent Application No. 202410340962.5 filed in China on March 25, 2024, the entire contents of which are incorporated herein by reference. Technical Field

[0003] The present disclosure relates to the field of mobile communication technology, and in particular to an access method, terminal equipment, network equipment, and storage medium. Background Art

[0004] In the inventory and access process of radio frequency identification (RFID) in related technologies, a terminal device needs to wait until the count value of a timeslot counter decreases to 0 before initiating access to a network device in the corresponding feedback timeslot, such as performing an inventory reply or access process.

[0005] While waiting for its own feedback slot to arrive, a terminal device may encounter a situation where an urgent response or priority access attempt is required (especially for terminal devices with sensing / measurement capabilities). The terminal device access process in related technologies does not support access before the terminal device's own feedback slot arrives, and cannot effectively solve the above problem. Summary of the Invention

[0006] At least one embodiment of the present disclosure provides an access method, terminal device, network device, and storage medium, for solving the problem that related technologies do not support access before the terminal device's own feedback time slot arrives.

[0007] In order to solve the above technical problems, the present disclosure is implemented as follows:

[0008] In a first aspect, an embodiment of the present disclosure provides an access method, applied to a terminal device, the method comprising:

[0009] The terminal device receives the first indication message repeatedly sent by the network device, and when determining that preemptive access needs to be initiated through the preemptive time slot, sends a first request message within the preemptive time slot, wherein a preemptive time slot is included between two adjacent first indication messages;

[0010] The terminal device receives a first response message sent by the network device, wherein the first response message is used to indicate a first quantity;

[0011] The terminal device determines a second number that is not greater than the first number, and counts the first feedback time slots based on the second indication message repeatedly sent by the received network device, and sends access information to the network device when the count value of the first feedback time slot reaches the second number; wherein, one first feedback time slot is included between two adjacent second indication messages.

[0012] Optionally, the above method further includes:

[0013] The terminal device counts the second feedback time slot based on the received first indication message, and sends access information to the network device when the count value of the second feedback time slot reaches a third number, wherein a second feedback time slot is included between two adjacent first indication messages.

[0014] Optionally, the above method further includes:

[0015] The terminal device determines to start the first type of access process or the second type of access process according to the event information and / or process type information sent by the network device;

[0016] When the terminal device determines to start the first type of access process, it generates trigger event information according to the event information, and enters the step of receiving the first indication message repeatedly sent by the network device, and when it is determined that preemptive access needs to be initiated through the preemptive time slot, sending a first request message within the preemptive time slot;

[0017] Among them, the first type of access process supports terminal devices initiating preemptive access, and the second type of access process does not support terminal devices initiating preemptive access; the event information includes triggering event information of at least one triggering event that triggers preemptive access, and the triggering event information includes triggering conditions; the process type information is used to indicate the start of the first type of access process or the second type of access process.

[0018] Optionally, the trigger condition includes at least one of the following:

[0019] a threshold corresponding to an indicator of a triggering event, and a first logical relationship between the indicator and the threshold;

[0020] The upper and lower limits of the threshold corresponding to the indicator that triggers the event;

[0021] Memory indication information used to indicate a target location in the memory of a terminal device, a codeword used to compare with a target field in the target location, and a second logical relationship between the target field and the codeword.

[0022] Optionally, determining to start the first type of access process according to the event information and / or the process type information includes at least one of the following methods:

[0023] Mode 1: The terminal device receives a first configuration message and the start instruction sent by a network device, wherein the first configuration message carries the event information, and the start instruction carries process type information; if the process type information indicates starting the first type of access process, the terminal device determines to start the first type of access process; in the first mode, the triggering event information is generated based on the event information carried in the first configuration message;

[0024] Second mode: The terminal device receives the start instruction sent by the network device, and determines to start the first type of access process when the start instruction carries the event information; in the second mode, the triggering event information is generated according to the event information carried by the start instruction;

[0025] The third method: the terminal device receives the first configuration message and the startup instruction sent by the network device, wherein the first configuration message carries first event information, and the startup instruction carries second event information and / or process type information; when the startup instruction carries the second event information, it is determined to start the first type of access process, and at this time, the triggering event information is generated based on the second event information; when the startup instruction does not carry the second event information but carries the process type information indicating the start of the first type of access process, it is determined to start the first type of access process, and at this time, the triggering event information is generated based on the first event information.

[0026] Optionally, the above method further includes:

[0027] When the terminal device determines to start the second type of access process, it receives the first indication message repeatedly sent by the network device, counts the third feedback time slot based on the received first indication message, and sends access information to the network device after the count value of the third feedback time slot reaches a fourth number, and a third feedback time slot is included between two adjacent first indication messages.

[0028] Optionally, determining to start the second type of access process according to the event information and / or the process type information includes at least one of the following methods:

[0029] Fourth mode: The terminal device receives the first configuration message and the start instruction sent by the network device, wherein the first configuration message carries the event information, and the start instruction carries the process type information; if the process type information indicates to start the second type of access process, determining to start the second type of access process;

[0030] Fifth mode: The terminal device receives the start instruction sent by the network device, and determines to start the second type of access process when the start instruction does not carry the event information;

[0031] The sixth method: the terminal device receives the first configuration message and the startup instruction sent by the network device, wherein the first configuration message carries event information, and the startup instruction carries event information and / or carries process type information; when the startup instruction does not carry event information and the process type information indicates to start the second type of access process, it is determined to start the second type of access process.

[0032] Optionally, the trigger event information further includes: an event identifier of the trigger event.

[0033] Optionally, the first request message includes at least one of the following information:

[0034] A preset bit sequence used to indicate a first request message;

[0035] An event identifier of a target triggering event, where the target triggering event is all or part of the triggering event that triggers the terminal device to initiate preemptive access.

[0036] Optionally, the first response message includes indication information of the first quantity, or includes indication information of the first quantity and an event identifier of the target triggering event.

[0037] Optionally, the terminal device determines a second number that is not greater than the first number, including:

[0038] The terminal device determines the first quantity based on the indication information of the first quantity in the first response message; and generates a second quantity that is not greater than the first quantity.

[0039] Optionally, when the count value of the first feedback timeslot reaches the second number, sending access information to the network device includes:

[0040] Send temporary identity information of the terminal device;

[0041] Upon successfully receiving a confirmation response message sent by the network device carrying the temporary identity information of the terminal device, sending reporting information to the network device;

[0042] The reported information includes at least one of the following: terminal device identity information, event identifier and data of a target triggering event, where the target triggering event is all or part of the triggering event that triggers the terminal device to initiate preemptive access.

[0043] Optionally, in any of the following cases, returning to the step of the terminal device receiving the first indication message repeatedly sent by the network device, and sending the first request message in the preemption time slot when determining that preemptive access needs to be initiated by preempting the time slot:

[0044] After the terminal device sends the first request message, the first response message is not successfully received;

[0045] When the count value of the first feedback time slot reaches the second number, in the process of sending access information to the network device, the terminal device fails to successfully receive the confirmation response message carrying the temporary identity information of the terminal device sent by the network device after sending the temporary identity information of the terminal device, or receives the failure indication information carrying the temporary identity information of the terminal device sent by the network device after sending the reporting information.

[0046] Optionally, the trigger event information further includes: failure fallback time slot indication information; and the method further includes:

[0047] The terminal device determines a fifth number according to the failure fallback time slot indication information;

[0048] After returning the first indication message repeatedly sent by the network device to the terminal device, and determining that it is necessary to initiate preemptive access through the preemptive time slot, after the step of sending the first request message in the preemptive time slot, the terminal device waits for the fifth number of second feedback time slots, and then determines whether it is necessary to access through the preemptive time slot.

[0049] Optionally, the above method further includes:

[0050] After receiving the first response message, the terminal device saves the count value of the second feedback timeslot;

[0051] After the terminal device receives the first indication message repeatedly sent by the network device and, when determining that preemptive access needs to be initiated through the preemptive time slot, sends the first request message within the preemptive time slot, the terminal device continues to count the second feedback time slot based on the saved count value of the second feedback time slot, and sends access information to the network device after the count value of the second feedback time slot reaches the third number.

[0052] Optionally, determining that preemptive access needs to be initiated by seizing a time slot includes at least one of the following:

[0053] When any trigger event meets the trigger condition of the trigger event, it is determined that preemptive access needs to be initiated by preempting the time slot, and the trigger event is used as the target trigger event;

[0054] When at least two triggering events meet their respective triggering conditions, it is determined that preemptive access needs to be initiated by preempting a time slot, and all or part of the at least two triggering events are selected as target triggering events.

[0055] In a second aspect, an embodiment of the present disclosure provides an access method, applied to a network device, the method comprising:

[0056] The network device repeatedly sends the first indication message and, in a preemption time slot between two adjacent first indication messages, listens to a first request message sent by the terminal device for requesting preemptive access;

[0057] When the network device successfully receives the first request message within the preemption time slot, it stops sending the first indication message, sends a first response message, and repeatedly sends a second indication message, wherein the first response message is used to indicate the first quantity;

[0058] The network device monitors the access information sent by the terminal device in the first number of first feedback time slots, wherein one first feedback time slot is included between two adjacent second indication messages.

[0059] Optionally, the above method further includes:

[0060] The network device monitors the access information sent by the terminal device in a second feedback time slot, wherein the second feedback time slot is the remaining part between two adjacent first indication messages except the preemption time slot.

[0061] Optionally, the above method further includes:

[0062] The network device initiates a first type of access process and sends event information, wherein the first type of access process supports the terminal device to initiate preemptive access, and the event information includes triggering event information of at least one triggering event that triggers preemptive access, and the triggering event information includes a triggering condition;

[0063] After the network device starts the first type of access process, the network device repeatedly sends a first indication message and monitors a first request message sent by a terminal device in a preemption time slot between two adjacent first indication messages.

[0064] Optionally, the trigger condition includes at least one of the following:

[0065] a threshold corresponding to an indicator of a triggering event, and a first logical relationship between the indicator and the threshold;

[0066] The upper and lower limits of the threshold corresponding to the indicator that triggers the event;

[0067] Memory indication information used to indicate a target location in the memory of a terminal device, a codeword used to compare with a target field in the target location, and a second logical relationship between the target field and the codeword.

[0068] Optionally, the network device initiates the first type of access process and sends the event information in at least one of the following ways:

[0069] In a first manner, the network device sends a first configuration message and a start instruction for starting an access process, wherein the first configuration message carries the event information, and the start instruction carries process type information for instructing to start the first type of access process;

[0070] Second mode: the network device sends a start instruction for starting the access process, wherein the start instruction carries the event information;

[0071] The third method: the network device sends a first configuration message and a startup instruction for starting the access process, wherein the first configuration message carries first event information, and the startup instruction carries second event information and / or carries process type information for indicating the start of the first type of access process.

[0072] Optionally, the above method further includes:

[0073] The network device starts a second type of access process, repeatedly sends a first indication message, and monitors access information sent by the terminal device between two adjacent first indication messages, wherein the second type of access process does not support the terminal device initiating preemptive access.

[0074] Optionally, the network device initiates the second type of access process in at least one of the following ways:

[0075] Fourth mode: the network device sends a first configuration message and a start instruction for starting the access process, wherein the first configuration message carries the event information, and the start instruction carries process type information for indicating starting the second type of access process;

[0076] Fifth mode: the network device sends a start instruction for starting the access process, wherein the start instruction does not carry the event information;

[0077] The sixth method: the network device sends a first configuration message and a start instruction for starting an access process, wherein the first configuration message carries event information, the start instruction does not carry event information, and carries process type information for indicating the start of the second type of access process.

[0078] Optionally, the trigger event information further includes: an event identifier of the trigger event.

[0079] Optionally, the first request message includes at least one of the following information:

[0080] A preset bit sequence used to indicate a first request message;

[0081] An event identifier of a target triggering event, where the target triggering event is all or part of the triggering event that triggers the terminal device to initiate preemptive access.

[0082] Optionally, the first response message includes indication information of the first quantity, or includes indication information of the first quantity and an event identifier of the target triggering event.

[0083] Optionally, the network device monitors access information sent by the terminal device in the first feedback timeslot, including at least one of the following:

[0084] When the network device successfully receives the temporary identity information of the terminal device sent by the terminal device, it sends a confirmation response message carrying the temporary identity information of the terminal device and receives the reporting information sent by the terminal device;

[0085] The network device sends a confirmation response message carrying the temporary identity information of the terminal device when successfully receiving the temporary identity information of the terminal device sent by the terminal device, and sends a failure indication message carrying the temporary identity information of the terminal device when unsuccessfully receiving the reporting information sent by the terminal device;

[0086] The network device returns to the network device and repeatedly sends the first indication message after the first number of first feedback time slots have passed, and listens to the first request message for preemptive access sent by the terminal device in the preemption time slot between two adjacent first indication messages;

[0087] The reported information includes at least one of the following: terminal device identity information, event identifier of a target triggering event, and data. The target triggering event is all or part of the triggering event that triggers the terminal device to initiate preemptive access.

[0088] Optionally, the trigger event information also includes: failure fallback time slot indication information; the failure fallback time slot indication information is used for the terminal device to determine a fifth number, and the fifth number is the number of second feedback time slots that the terminal device needs to wait for before determining again whether to initiate preemptive access when the preemptive access fails.

[0089] In a third aspect, an embodiment of the present disclosure provides a terminal device, including:

[0090] A first transceiver module is configured to receive a first indication message repeatedly sent by a network device, and, if it is determined that preemptive access needs to be initiated through a preemptive time slot, send a first request message within the preemptive time slot, wherein one preemptive time slot is included between two adjacent first indication messages;

[0091] A first receiving module is configured to receive a first response message sent by the network device, wherein the first response message is used to indicate a first quantity;

[0092] A first access module is configured to determine a second number that is not greater than the first number, count first feedback time slots based on a received second indication message repeatedly sent by the network device, and send access information to the network device when the count value of the first feedback time slot reaches the second number; wherein one first feedback time slot is included between two adjacent second indication messages.

[0093] In a fourth aspect, an embodiment of the present disclosure provides a network device, including:

[0094] A first transceiver module is configured to repeatedly send a first indication message and, in a preemption time slot between two adjacent first indication messages, monitor a first request message sent by a terminal device for requesting preemptive access;

[0095] a first response module, configured to, upon successfully receiving the first request message within the preemption time slot, stop sending the first indication message, send a first response message, and repeatedly send a second indication message, wherein the first response message is used to indicate a first quantity;

[0096] The first monitoring module is used to monitor the access information sent by the terminal device in the first number of first feedback time slots, wherein one first feedback time slot is included between two adjacent second indication messages.

[0097] In a fifth aspect, an embodiment of the present disclosure provides a terminal device, comprising: a processor, a memory, and a program stored in the memory and executable on the processor, wherein the program, when executed by the processor, implements the steps of the method described in the first aspect.

[0098] In a sixth aspect, an embodiment of the present disclosure provides a network device comprising: a processor, a memory, and a program stored in the memory and executable on the processor, wherein the program, when executed by the processor, implements the steps of the method described in the second aspect.

[0099] In a seventh aspect, an embodiment of the present disclosure provides a computer-readable storage medium having a program stored thereon. When the program is executed by a processor, the steps of the method described in the first aspect or the second aspect are implemented.

[0100] In an eighth aspect, an embodiment of the present disclosure provides a computer program product, comprising computer instructions, which, when executed by a processor, implement the steps of the method described in the first aspect or the second aspect.

[0101] Compared to related technologies, the access method, terminal device, network device, and storage medium provided by the embodiments of the present disclosure enable a terminal device to initiate preemptive access using its first feedback timeslot, before its second feedback timeslot has not yet arrived, when preemptive access is required. This satisfies scenarios where the terminal device requires priority access. The embodiments of the present disclosure can improve the flexibility and efficiency of terminal device access. BRIEF DESCRIPTION OF THE DRAWINGS

[0102] Various other advantages and benefits will become apparent to those skilled in the art upon reading the detailed description of the preferred embodiment below. The accompanying drawings are for illustration purposes only and are not to be considered as limiting the present disclosure. The same reference symbols are used throughout the drawings to represent the same components. In the drawings:

[0103] FIG1 is a schematic diagram of an inventory and access process of RFID in the related art;

[0104] FIG2 is a schematic diagram of another inventory and access process of RFID in the related art;

[0105] FIG3 is a flow chart of an access method according to an embodiment of the present disclosure when applied to a terminal device side;

[0106] FIG4 is a flow chart of an access method according to an embodiment of the present disclosure when applied to a network device side;

[0107] FIG5 is a schematic diagram of a representation method of multiple events according to an embodiment of the present disclosure;

[0108] FIG6 is a schematic diagram of a preemptive time slot and a normal recovery time slot according to an embodiment of the present disclosure;

[0109] FIG7 is a second schematic diagram of a preemptive time slot and a normal recovery time slot according to an embodiment of the present disclosure;

[0110] FIG8 is a third schematic diagram of a preemptive time slot and a normal recovery time slot according to an embodiment of the present disclosure;

[0111] FIG9 is a schematic diagram of the transition of the terminal device state according to an embodiment of the present disclosure;

[0112] FIG10 is an example diagram of an access process provided by the present disclosure;

[0113] FIG11 is an example diagram of another access process provided by the present disclosure;

[0114] FIG12 is a schematic structural diagram of a terminal device according to an embodiment of the present disclosure;

[0115] FIG13 is a schematic structural diagram of a network device according to an embodiment of the present disclosure;

[0116] FIG14 is a schematic structural diagram of a terminal device according to another embodiment of the present disclosure;

[0117] FIG15 is a schematic structural diagram of a network device according to another embodiment of the present disclosure. DETAILED DESCRIPTION

[0118] Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although exemplary embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be limited by the embodiments set forth herein. Rather, these embodiments are provided to enable a more thorough understanding of the present disclosure and to fully convey the scope of the present disclosure to those skilled in the art.

[0119] The terms "first", "second", etc. in the specification and claims of the present disclosure are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present disclosure described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices. "And / or" in the specification and claims represents at least one of the connected objects.

[0120] The following description provides examples and does not limit the scope, applicability, or configuration set forth in the claims. The functions and arrangements of the elements discussed may be changed without departing from the scope of this disclosure. The various examples may appropriately omit, substitute, or add various procedures or components. For example, the described methods may be performed in an order different from that described, and various steps may be added, omitted, or combined. In addition, features described with reference to certain examples may be combined in other examples.

[0121] In this document, the terminal device can be an active or passive device such as a tag, or a terminal device equipped with a tag. The network device can be any reader / writer that provides communication services to the terminal device, specifically various base stations, relay devices, and user equipment (UE, such as a mobile phone). The access method refers to the method by which the network device triggers the terminal device to respond, which can also be called an inventory method, a paging method, etc.

[0122] In addition, in this article, "successfully receiving a message or information" means that the message or information is received and successfully decoded or verified, thereby obtaining the message or information. "Unsuccessfully receiving a message or information" means that the message or information is not received, or that the message or information is received but decoding fails.

[0123] In this document, each time slot generally refers to the time interval between related messages, that is, it is usually defined by the time interval between two messages. The duration of the same time slot can be the same or different.

[0124] To facilitate understanding of the relevant solutions in the embodiments of the present disclosure, some concepts or processes of related technologies are first explained.

[0125] The definition of mandatory instructions for RFID readers is shown in Table 1:

[0126] Table 1

[0127] An inventory and access process of RFID in related technology is shown in FIG1 , which includes the following steps.

[0128] Step 11: For powered-on tags, the reader selects the tag whose memory content matches the mask field through the Select command. The matching tag performs the corresponding operation on the SL flag or the flag of the selected session.

[0129] Step 12: The reader sends a query command. The tag whose SL and Session flag bits match generates a 16-bit random number (RN16) and selects the Q bit to fill in the time slot counter.

[0130] Step 13: The reader sends one or more repeated QueryRep commands. Upon receiving the QueryRep command, the tag decrements its slot counter by one. When the slot counter reaches 0, the tag backscatters RN16. Here, a feedback slot is included between adjacent repeated QueryRep commands. This document also refers to the feedback slot between adjacent repeated QueryRep commands as the second feedback slot, to distinguish it from the first feedback slot described below.

[0131] Step 14: After correctly receiving the RN16 reflected by the tag, the reader sends an Acknowledgement (ACK) instruction to the tag to confirm that there is no conflict in the tag access process.

[0132] Step 15: After receiving the ACK command, the tag chooses to reply with the Electronic Product Code (EPC) or a truncated EPC according to the Truncate field in the previous Select command.

[0133] Step 16: The reader sends the Req_RN command carrying RN16.

[0134] Step 17: After the tag confirms that RN16 in the Req_RN command matches, it randomly generates a new 16-bit random number called Handle and replies with Handle.

[0135] Step 18: The reader sends a read instruction containing a Handle.

[0136] Step 19: The tag responds with the corresponding data (Data).

[0137] From the perspective of reducing signaling overhead and lowering inventory and access delays, the data transmission in step 19 of Figure 1 can be transmitted together with the EPC in step 15, that is, the EPC and Data are transmitted in step 15. At this time, the process shown in Figure 1 can be converted into the process shown in Figure 2, including steps 21 to 25 as shown in Figure 2.

[0138] In the access process shown in Figure 1 or Figure 2, after the tag determines the number of feedback time slots based on the Q value in the Query instruction, it needs to wait until the corresponding number of feedback time slots before it can feedback identity information and / or data. In the process of waiting for its own feedback time slot to arrive, the tag can perform its own measurement and / or sensing and / or calculation process through the radio frequency (RF) and / or other energy supply in this process. In the process of the tag performing measurement and / or sensing and / or calculation, it may encounter a situation where it needs an urgent reply / attempt priority access before its own feedback time slot arrives (especially for tags with sensing / measurement capabilities). The relevant technology cannot effectively solve the above problems. In this regard, the embodiment of the present disclosure proposes an access method that can support terminal devices (for example, the tags mentioned above) to initiate access before their own feedback time slot arrives. In order to distinguish between the access initiated by the terminal device in its own feedback time slot and the access initiated by the terminal device before the arrival of its own feedback time slot, this article sometimes refers to the former as normal access, that is, the access initiated in the terminal device's own feedback time slot (the second feedback time slot); and the latter as preemptive access, that is, the access initiated before the arrival of the terminal device's own feedback time slot (the second feedback time slot).

[0139] FIG3 is a flow chart of an access method provided by an embodiment of the present disclosure when applied to a terminal device. As shown in FIG3 , the method includes:

[0140] In step 31, the terminal device receives the first indication message repeatedly sent by the network device, and when it is determined that preemptive access needs to be initiated through a preemptive time slot, sends a first request message within the preemptive time slot, wherein a preemptive time slot is included between two adjacent first indication messages.

[0141] Here, the terminal device can specifically be an active or passive device such as a tag, or a terminal device provided with a tag. The network device can be various readers and writers that provide communication services for the tag, specifically various base stations, relay devices, user equipment (UE, such as mobile phones), etc. The network device repeatedly sends the first indication message, and the time intervals between two adjacent first indication messages can be equal or unequal, which is not limited in the embodiment of the present disclosure. In addition, there is a preemption time slot between two adjacent first indication messages. When the terminal device determines that it needs to initiate preemptive access, it can send the first request message in the preemption time slot between two adjacent first indication messages to request preemptive access.

[0142] Optionally, the first indication message may be a message for counting the second feedback timeslot, such as the QueryRep command described above. For example, upon receiving a first indication message, the terminal device decrements the value of its own second feedback timeslot counter by one. When the counter reaches 0, the terminal device initiates normal access in the second feedback timeslot. Therefore, the interval between two consecutive first indication messages includes one preemption timeslot and one second feedback timeslot.

[0143] It should be noted that, if the terminal device receives a first response message after a first indication message, a preemption time slot and a second feedback time slot are included between the first indication message and the first response message.

[0144] Step 32: The terminal device receives a first response message sent by the network device, wherein the first response message is used to indicate a first quantity.

[0145] Here, after sending the first indication message to request for access preemption, the terminal device waits to receive a first response message sent by the network device, where the first response message is used to indicate the first quantity.

[0146] In step 33, the terminal device determines a second number that is not greater than the first number, and counts the first feedback time slot based on the second indication message repeatedly sent by the received network device, and sends access information to the network device when the count value of the first feedback time slot reaches the second number; wherein, a first feedback time slot is included between two adjacent second indication messages.

[0147] Here, after receiving the first response message, the terminal device determines a second number, which is less than or equal to the first number, and then receives the second indication message repeatedly sent by the network device, counts the first feedback time slot according to the second indication message, and sends access information to the network device in the first feedback time slot when the count value reaches the second number.

[0148] Specifically, a first feedback time slot is included between two adjacent second indication messages. After receiving a second indication message, the terminal device can count the first feedback time slot. The second indication message can be other instructions similar to the repeat query (QueryRep) instruction. For example, when using subtraction counting, a counter with an initial value of the second number can be set, so that each time a second indication message is received, the counter is decremented by one. When the counter is 0, it is considered that the count value of the first feedback time slot has reached the second number. For another example, when using addition counting, a counter with an initial value of 0 can be set, so that each time a second indication message is received, the counter is incremented by one. When the value of the counter is equal to the second number, it is considered that the count value of the first feedback time slot has reached the second number.

[0149] Through the above steps, the embodiment of the present disclosure can, when preemptive access is needed, initiate preemptive access through the first feedback time slot before its own second feedback time slot has not yet arrived, to meet the scenario where the terminal device needs priority access.

[0150] In the case of supporting terminal devices to preempt access, the embodiment of the present disclosure also supports terminal devices to access through the second feedback time slot. For example, the method shown in Figure 3 may also include the following steps:

[0151] In step 34, if the terminal device does not have a need to preempt access (e.g., the terminal device does not trigger any event), the terminal device may count the second feedback time slots based on the received first indication message, and, when the count value of the second feedback time slots reaches a third number, send access information to the network device, wherein one second feedback time slot is included between two adjacent first indication messages. The third number may be obtained by referring to step 12 or 22 above, for example, the terminal device generates a random number RN16 based on the received query instruction, and determines a third number based on the random number RN16.

[0152] In the disclosed embodiment, the interval between two adjacent first indication messages includes a preemption time slot and a second feedback time slot. The preemption time slot may precede the second feedback time slot, with no overlap between the two. Furthermore, the second feedback time slot is the remainder of the interval between two adjacent first indication messages, excluding the preemption time slot. The length of the preemption time slot may be a preset first fixed length.

[0153] In an embodiment of the present disclosure, the terminal device may determine in advance whether to start the first type of access process or the second type of access process based on the event information and / or process type information sent by the network device. The first type of access process supports the terminal device to initiate preemptive access, and the second type of access process does not support the terminal device to initiate preemptive access. In the case of determining to start the first type of access process, the terminal device executes the steps shown in Figure 3, that is, executes steps 31 to 34; in the case of determining to start the second type of access process, the terminal device receives the first indication message repeatedly sent by the network device, counts the third feedback time slot based on the received first indication message, and sends access information to the network device after the count value of the third feedback time slot reaches the fourth number. Here, a third feedback time slot is included between two adjacent first indication messages, and the fourth number can also be obtained by referring to steps 12 or 22 above.

[0154] In the embodiment of the present disclosure, the process type information is used to indicate the start of the first type access process or the second type access process. The event information includes at least one triggering event information of a triggering event that triggers preemptive access, and the triggering event information includes a triggering condition; specifically, the triggering condition includes at least one of the following:

[0155] (1) A threshold corresponding to an indicator of a triggering event, and a first logical relationship between the indicator and the threshold. The first logical relationship may be a magnitude relationship, such as one or more of greater than, equal to, and less than.

[0156] (2) The upper and lower limits of the threshold corresponding to the indicator that triggers the event.

[0157] (3) Memory indication information for indicating a target location in a memory of a terminal device, a codeword for comparison with a target field in the target location, and a second logical relationship between the target field and the codeword. The second logical relationship may be one or more of equal, not equal, complete match, and partial match.

[0158] In step 31 above, the terminal device determines that it needs to initiate preemptive access by seizing a time slot, including at least one of the following:

[0159] (1) When any trigger event meets the trigger condition of the trigger event, it is determined that a preemptive access needs to be initiated by preempting the time slot, and the trigger event is used as the target trigger event.

[0160] (2) When at least two triggering events meet their respective triggering conditions, it is determined that preemptive access needs to be initiated by preempting the time slot, and all or part of the at least two triggering events are selected as target triggering events.

[0161] In the embodiment of the present disclosure, the terminal device determines, based on the event information and / or the process type information, a manner of starting the first type of access process, which may include at least one of the following:

[0162] The first method: the terminal device receives the first configuration message and the startup instruction sent by the network device, wherein the first configuration message carries the event information and the startup instruction carries the process type information; when the process type information indicates to start the first type of access process, it is determined to start the first type of access process; in the first method, the trigger event information is generated based on the event information carried in the first configuration message.

[0163] Here, the first configuration message may be a message for configuring the terminal device to use resources and / or reply behavior, and specifically may be a system message or other message.

[0164] The second method: the terminal device receives the startup instruction sent by the network device, and determines to start the first type of access process when the startup instruction carries the event information; in the second method, the triggering event information is generated based on the event information carried by the startup instruction.

[0165] The third method: the terminal device receives the first configuration message and the startup instruction sent by the network device, wherein the first configuration message carries first event information, and the startup instruction carries second event information and / or process type information; when the startup instruction carries the second event information, it is determined to start the first type of access process, and at this time, the triggering event information is generated based on the second event information; when the startup instruction does not carry the second event information but carries the process type information indicating the start of the first type of access process, it is determined to start the first type of access process, and at this time, the triggering event information is generated based on the first event information.

[0166] Here, the start instruction may include a selection instruction and / or a query instruction.

[0167] The terminal device determines, based on the event information and / or the process type information, a manner of starting the second type of access process, which may include at least one of the following:

[0168] Fourth mode: The terminal device receives the first configuration message and the start instruction sent by the network device, wherein the first configuration message carries the event information, and the start instruction carries the process type information; if the process type information indicates to start the second type of access process, determining to start the second type of access process;

[0169] Fifth mode: The terminal device receives the start instruction sent by the network device, and determines to start the second type of access process when the start instruction does not carry the event information;

[0170] The sixth method: the terminal device receives the first configuration message and the startup instruction sent by the network device, wherein the first configuration message carries event information, and the startup instruction carries event information and / or carries process type information; when the startup instruction does not carry event information and the process type information indicates to start the second type of access process, it is determined to start the second type of access process.

[0171] In the disclosed embodiments, the trigger event information indicated by the event information sent by the network device may include an event identifier of the trigger event. For example, if the event information indicates only one trigger event, the trigger event information may not carry the event identifier of the trigger event, but may also carry the event identifier. If the event information indicates at least two trigger events, the trigger event information may carry the event identifiers of each trigger event.

[0172] The first request message sent by the terminal device in step 31 may carry at least one of the following information:

[0173] (1) A preset bit sequence used to indicate a first request message so that the network device can identify the first request message.

[0174] (2) An event identifier of a target trigger event, wherein the target trigger event is all or part of the trigger events that trigger the terminal device to initiate access preemption, so that the network device can be informed of the event that triggers the terminal device to preempt access. Specifically, there can be one or more target trigger events. For example, when the trigger conditions of multiple trigger events are met, all of the trigger events can be used as target trigger events, that is, there are multiple target trigger events. Of course, some of the trigger events can also be used as target trigger events. When sending the first request message, the event identifier of the target trigger event can be carried in the first request message.

[0175] The first response message sent by the network device in the above step 32 may include the indication information of the first quantity, or the first response message includes the indication information of the first quantity and the event identifier of the target triggering event.

[0176] Thus, in the above step 33, the terminal device can determine the first quantity according to the indication information of the first quantity in the first response message; and then generate a second quantity that is not greater than the first quantity. The indication information of the first quantity can be implemented in a variety of ways, for example, directly indicating the first quantity, or indicating a Q value, where the first quantity is 2 Q Similarly, there are many ways to generate the second number, for example, randomly generating an integer in the range of 0 to the first number as the second number, which is also not specifically limited in the embodiment of the present disclosure.

[0177] The following describes an implementation of the terminal device sending access information to the network device when the count value of the first feedback timeslot reaches the second number in step 31, which may specifically include:

[0178] (1) Sending temporary identity information of the terminal device, such as a random number RN16 generated by the terminal device;

[0179] (2) upon successfully receiving a confirmation response message from the network device carrying the temporary identity information of the terminal device, sending reporting information to the network device; wherein the reporting information includes at least one of the following: terminal device identity information, an event identifier of a target triggering event, and data, wherein the target triggering event is all or part of a triggering event that triggers the terminal device to initiate preemptive access. Here, the data may be inventory data, sensor data, or other data, which is not specifically limited in this disclosure. There may be one or more target triggering events.

[0180] In the process shown in FIG3 , there may be some abnormal situations. In these abnormal situations, the terminal device will return to step 31 and continue to perform steps 31-33. Specifically, the abnormal situation includes at least one of the following:

[0181] (1) After the terminal device sends the first request message, it fails to successfully receive the first response message.

[0182] (2) When the count value of the first feedback time slot reaches the second number, in the process of sending access information to the network device, the terminal device fails to successfully receive the confirmation response message carrying the temporary identity information of the terminal device sent by the network device after sending the temporary identity information of the terminal device, or receives the failure indication information carrying the temporary identity information of the terminal device sent by the network device after sending the reporting information.

[0183] After the terminal device returns to step 31, in order to avoid the terminal device from frequently initiating preemptive access, the trigger event information of the embodiment of the present disclosure also includes: failure fallback time slot indication information. In this way, the terminal device can determine a fifth number based on the failure fallback time slot indication information. Then, after returning to step 31, the terminal device determines whether it is necessary to access through the preemptive time slot after waiting for the second feedback time slot of the fifth number. The failure fallback time slot indication information can directly indicate the fifth number, or it can indicate information related to the fifth number, so that the terminal device can determine the fifth number based on the information, for example, indicating a failure fallback time slot interval, and the terminal device randomly selects a value from the interval or selects a value according to a certain rule as the fifth number. The embodiment of the present disclosure does not make specific restrictions on this.

[0184] Furthermore, in the process shown in FIG3 , before receiving the first response message sent by the network device, the terminal device counts the second feedback time slots based on the received first indication message. If the first response message is received, the terminal device may save the count value of the second feedback time slots. Subsequently, after the terminal device returns to step 31, it may continue to count the second feedback time slots based on the saved count value of the second feedback time slots and send access information to the network device after the count value of the second feedback time slots reaches the third number.

[0185] FIG4 is a flow chart of an access method provided by an embodiment of the present disclosure when applied to a network device. As shown in FIG4 , the method includes:

[0186] In step 41, the network device repeatedly sends a first indication message, and in a preemption time slot between two adjacent first indication messages, monitors a first request message sent by a terminal device for requesting preemptive access.

[0187] Here, the network device can be a reader / writer that provides communication services for the terminal device, specifically various base stations, relay devices, user equipment (UE, such as mobile phones), etc. The terminal device can specifically be an active or passive device such as a tag, or a terminal device provided with a tag. The network device repeatedly sends the first indication message, and the time interval between two adjacent first indication messages can be equal or unequal, which is not limited in the embodiment of the present disclosure. In addition, there is a preemption time slot between two adjacent first indication messages. The terminal device that needs to initiate preemptive access can send a first request message in the preemption time slot between two adjacent first indication messages to request preemptive access.

[0188] Optionally, the first indication message may be a message for counting the second feedback timeslot, such as the QueryRep command described above. For example, upon receiving a first indication message, the terminal device decrements the value of its own second feedback timeslot counter by one. When the counter reaches 0, the terminal device initiates normal access in the second feedback timeslot. Therefore, the interval between two consecutive first indication messages includes one preemption timeslot and one second feedback timeslot.

[0189] Step 42: When the network device successfully receives the first request message within the preempted time slot, it stops sending the first indication message, sends a first response message, and repeatedly sends a second indication message, wherein the first response message is used to indicate the first quantity.

[0190] Here, if the network device successfully receives the first request message within the preemption time slot, the network device stops sending the first indication message, sends a first response message indicating the first quantity, and repeats sending the second indication message. The second indication message may be a message used by the terminal device to count the first feedback time slots. For each second indication message received by the terminal device, the terminal device counts one first feedback time slot, for example, by decrementing the value of its own first feedback time slot counter by one. When the counter reaches 0, the terminal device initiates preemptive access in the first feedback time slot.

[0191] Step 43: The network device monitors the access information sent by the terminal device in the first number of first feedback time slots, wherein one first feedback time slot is included between two adjacent second indication messages.

[0192] Here, the network device monitors the access information sent by the terminal device in the first feedback time slot between two adjacent second indication messages, that is, monitors the preemptive access initiated by the terminal device.

[0193] Through the above steps, the embodiment of the present disclosure can support the terminal device to initiate preemptive access through the first feedback time slot, thereby meeting the terminal device's demand for priority access.

[0194] After the network device monitors the first number of first feedback time slots, the process may return to step 41 .

[0195] In the case where the network device of the embodiment of the present disclosure supports the terminal device to preempt access, it also supports the terminal device to access through the second feedback time slot. For example, the method shown in Figure 4 may also include the following steps (not shown in Figure 4):

[0196] Step 44: The network device monitors the access information sent by the terminal device in a second feedback time slot, wherein the second feedback time slot is the remaining portion between two adjacent first indication messages except the preemption time slot.

[0197] In the disclosed embodiment, before step 41, the network device initiates a first access procedure and sends event information. The first access procedure supports preemptive access initiated by a terminal device, and the event information includes triggering event information for at least one triggering event for preemptive access, wherein the triggering event information includes a triggering condition. After the network device initiates the first access procedure, step 41 is entered.

[0198] Here, the trigger condition includes at least one of the following:

[0199] (1) a threshold corresponding to an indicator of a triggering event, and a first logical relationship between the indicator and the threshold;

[0200] (2) The upper and lower limits of the threshold corresponding to the indicator that triggers the event;

[0201] (3) Memory indication information for indicating a target location in a memory of a terminal device, a codeword for comparison with a target field in the target location, and a second logical relationship between the target field and the codeword.

[0202] Specifically, the network device initiates the first type of access process and sends the event information in at least one of the following ways:

[0203] In a first manner, the network device sends a first configuration message and a start instruction for starting an access process, wherein the first configuration message carries the event information, and the start instruction carries process type information for instructing to start the first type of access process;

[0204] Second mode: the network device sends a start instruction for starting the access process, wherein the start instruction carries the event information;

[0205] The third method: the network device sends a first configuration message and a startup instruction for starting the access process, wherein the first configuration message carries first event information, and the startup instruction carries second event information and / or carries process type information for indicating the start of the first type of access process.

[0206] Here, the start instruction may include a selection instruction and / or a query instruction.

[0207] In the embodiment of the present disclosure, the network device may also initiate the second type of access process, and the initiation method includes at least one of the following:

[0208] Fourth mode: the network device sends a first configuration message and a start instruction for starting the access process, wherein the first configuration message carries the event information, and the start instruction carries process type information for indicating starting the second type of access process;

[0209] Fifth mode: the network device sends a start instruction for starting the access process, wherein the start instruction does not carry the event information;

[0210] The sixth method: the network device sends a first configuration message and a start instruction for starting an access process, wherein the first configuration message carries event information, the start instruction does not carry event information, and is used to indicate the process type information for starting the second type of access process.

[0211] In the embodiment of the present disclosure, the triggering event information further includes: an event identifier of the triggering event.

[0212] In step 42 above, the first request message received by the network device may include at least one of the following information:

[0213] (1) a preset bit sequence for indicating a first request message;

[0214] (2) An event identifier of a target triggering event, where the target triggering event is all or part of the triggering event that triggers the terminal device to initiate preemptive access.

[0215] In the above step 42, the first response message sent by the network device includes the indication information of the first quantity, or includes the indication information of the first quantity and the event identifier of the target triggering event.

[0216] In step 43, the network device monitors the access information sent by the terminal device in the first feedback time slot, including at least one of the following:

[0217] (1) When the network device successfully receives the temporary identity information of the terminal device sent by the terminal device, the network device sends a confirmation response message carrying the temporary identity information of the terminal device and receives the reporting information sent by the terminal device;

[0218] (2) when the network device successfully receives the temporary identity information of the terminal device sent by the terminal device, the network device sends a confirmation response message carrying the temporary identity information of the terminal device, and when the network device fails to successfully receive the reporting information sent by the terminal device, the network device sends a failure indication message carrying the temporary identity information of the terminal device;

[0219] (3) After the first number of first feedback time slots have passed, the network device returns to the network device and repeatedly sends the first indication message, and in the preemption time slot between two adjacent first indication messages, listens for a first request message sent by the terminal device for requesting preemptive access;

[0220] The reported information includes at least one of the following: terminal device identity information, event identifier of a target triggering event, and data. The target triggering event is all or part of the triggering event that triggers the terminal device to initiate preemptive access.

[0221] In addition, in an embodiment of the present disclosure, the trigger event information may further include failure fallback time slot indication information. The failure fallback time slot indication information is used for the terminal device to determine a fifth number, which is the number of second feedback time slots that the terminal device needs to wait before re-determining whether to initiate preemptive access if preemptive access fails.

[0222] In addition, after monitoring the first number of first feedback time slots, the network device returns to step 41, i.e., repeatedly sends the first indication message, and monitors the first request message for preemptive access sent by the terminal device in the preemption time slot between two adjacent first indication messages. It should be noted that the last first feedback time slot in the first number is between the first first indication message sent by the network device after returning to step 41 and the last second indication message sent before the first indication message.

[0223] The above describes the method of the embodiment of the present disclosure from the perspective of the terminal device and the network device. To better understand the above embodiment, the method of the embodiment of the present disclosure is further described below with reference to an example of an access process triggered by an event.

[0224] The steps of the event-triggered access process are as follows:

[0225] Step 1: The base station sends a command carrying event information and starts a round of access process (first type of access process).

[0226] Here, the event information includes an event identifier, a failure fallback time slot indication (here, the failure fallback time slot interval is used), and an event triggering condition. The event identifier is used to uniquely identify a triggering event; the failure fallback time slot interval indication is described in detail in step 6 below; the event triggering condition can be at least one of the following:

[0227] Mode a: Threshold + Threshold Indication

[0228] The "threshold" indicates the threshold that triggers the event; the "threshold indication" indicates when the logical relationship (for example, >, ≥, <, ≤, =, ≠, etc.) with the threshold is satisfied to trigger the event.

[0229] Method b: lower threshold + upper threshold

[0230] This method is used when the event trigger condition is that the result of measurement and / or sensing and / or calculation falls within a certain value range (from the lower threshold to the upper threshold).

[0231] Method c: memory starting position + length + special code word + identification indication

[0232] Among them, "memory starting position + length" identifies the memory starting position and length used by the terminal device for field matching; the terminal device compares the above fields with the special codeword in the "event information"; "identification indication" is used to indicate what logical relationship the field used for matching and the special codeword meet to trigger the event (for example: =, ≠, etc.).

[0233] It should be noted that the trigger conditions for different events may be expressed in different ways. A possible embodiment is shown in Figure 5, where different trigger conditions are expressed for multiple events. Furthermore, upon receiving event information, the device can generate trigger event information based on the "event identifier," "failure fallback time slot interval," and "event trigger condition," and write it to the memory area.

[0234] Here, the manner in which the base station sends the event information and starts the access process may be based on at least one of the following manners:

[0235] Method 1: The base station only carries event information in the first configuration message, and starts the access process through a selection instruction (Select, if device selection is required) and a query instruction (Query).

[0236] In this case, when the base station initiates an access procedure by issuing a Select (if device selection is required) or Query command, the Select / Query command must also include at least the procedure type information. The procedure type information indicates whether the subsequent procedure is an event-triggered access procedure (first-type access procedure) or a normal access procedure (second-type access procedure). For example, "1" indicates an event-triggered access procedure, while "0" indicates a normal access procedure.

[0237] Method 2: The base station carries event information in a select command (Select) or a query command (Query) and starts the access process at the same time.

[0238] In this case, if the base station wants to perform an event-triggered access process, the Select (if device selection is required) / Query command it sends must at least contain event information (see above for the payload of event information). If the Select / Query command does not contain event information, it indicates that a normal access process is being performed.

[0239] It should be noted that in this case, if an event-triggered access process requires terminal device selection (i.e., initiated by a Select command), the event information can be carried in the Select command, and the Query command does not need to carry the event information. If terminal device selection is not required (i.e., an access process is initiated by a Query command), the event information must be carried in the Query command. From the perspective of unifying the signaling payload in the above two cases, the event information can be carried in the Query command.

[0240] Method three: the base station carries event information through the first configuration message and the Select / Query instruction.

[0241] In this case, if this round is a normal access process or an event-triggered access process based on event information in the system broadcast, the Select / Query command must at least include a process type indication (see method 1). Otherwise, the Select / Query command issued by the base station must at least include event information (see method 2).

[0242] It should be noted that Method 3 is the case where Methods 1 and 2 are used simultaneously, with Method 2 taking precedence. Specifically, if the selection / query instruction contains event information, the terminal device prioritizes the subsequent access process according to the event identifier, event trigger conditions, and failure fallback time slot interval contained therein, while ignoring the event information broadcast by the system. If the selection / query instruction does not contain event information, the terminal device determines whether to proceed with the subsequent access process according to the event and corresponding trigger conditions broadcast by the system based on the process type information.

[0243] Step 2: The base station sends a clock signal (QueryRep). The clock signal (QueryRep) is equivalent to the first indication message mentioned above. The time between two consecutive QueryRep instructions is recorded as a terminal device feedback slot (if the preemptive access process is about to start after a QueryRep is sent, the time between the QueryRep and the preemption reply and initialization instruction (equivalent to the first response message mentioned above) is a terminal device feedback slot). The terminal device feedback slot here includes the preemption slot and the normal reply slot (equivalent to the second feedback slot mentioned above). The preemption slot is for the terminal device that triggered the event to feedback a preemption indication message (equivalent to the first request message mentioned above), and the composition of the normal reply slot can be further divided into three situations according to the terminal device response situation: no terminal device feedback RN16, conflicting RN16 feedback from multiple terminal devices, and a single terminal device replying EPC+data, as shown in Figures 6, 7 and 8 respectively. It can be seen that the length of the normal reply slot may be different in different situations.

[0244] Step 3: The terminal device determines whether an event is triggered, and the base station monitors the preemption indication message (equivalent to the first request message above) within the time window of the preemption time slot and measures the energy of the received signal during this period.

[0245] While waiting for the normal reply time slot selected based on the Q value in the Query command, the terminal device performs its own measurement, sensing, and / or computation processes as normal. The terminal device records the results of these processes and determines whether they meet at least one event trigger condition. If so, upon receiving the next matching QueryRep command, the terminal device immediately responds with a preemption indication message (equivalent to the first request message described above) in the preemption time slot of the subsequent terminal device feedback time slot, and then enters the Triggered State.

[0246] Here, the payload of the preemption indication message may adopt at least one of the following schemes:

[0247] Solution 1: Special sequence. For example, the bit sequence "10101" is used as the preemption indication message.

[0248] This solution is simple to implement, and the base station can still correctly decode when multiple terminal devices provide feedback simultaneously (similar to receiving a multipath signal).

[0249] Solution 2: Identification of target triggering events.

[0250] It should be noted that, when there are multiple (≥2) preemption triggering events for the same terminal device, the terminal device may select one based on a certain rule; or, it may randomly select one as the target triggering event.

[0251] This solution enables the base station to identify the event that triggers preemption in advance.

[0252] It should be noted that the indicators that can be used as the basis for triggering the terminal device to preempt the time slot may include at least one of the following: measured received signal energy / power, measured RSRP of the received signal, measured interference intensity, perceived ambient temperature, perceived ambient humidity, and results calculated based on the above data, etc.

[0253] The base station monitors the preempted time slot of each terminal device's feedback time slot, and the subsequent behavior can be divided into the following cases:

[0254] 1) If the preemption indication message (equivalent to the first request message above) is successfully received and decoded, the base station further estimates the number of terminal devices that triggered the event based on the energy of the signal, and after completing the normal reply time slot immediately following the preemption time slot in Figure 6, Figure 7 or Figure 8, sends a preemption reply and initialization instruction (equivalent to the first response message above) to start a round of preemptive access process. The payload contained in the instruction includes at least: the Q value of this round of preemption process, which is used to indicate the first number (the Q value in the preemption reply and initialization instruction is used for the triggered terminal device to randomly select a terminal device feedback time slot in this round of preemption access process, and the triggered terminal device only generates a first random number based on the Q value and pre-loads it into the time slot counter without generating a new RN16); if the preemption indication message adopts the second solution of step 2, the preemption reply and initialization instruction may further include the decoded event identifier that triggered the preemption.

[0255] 2) If the preemption indication message (equivalent to the first request message above) is not successfully received or decoded, the normal reply time slot is continued, and then the base station continues to send QueryRep; each time the terminal device receives a QueryRep, the time slot counter is reduced by one; if the value of the time slot counter is 0, access is initiated.

[0256] It should be noted that the preemptive access process is started by the base station sending a preemptive reply and initialization command, and ends when the base station sends a QueryRep command again.

[0257] Step 4: After receiving the matching preemption reply and initialization command (equivalent to the first response message above), the terminal device in the triggered state saves the value of the slot counter from the previous process and generates a second random number based on the Q value in the preemption reply and initialization command (equivalent to the first response message above). This number is used to count the preemption feedback slot (equivalent to the first feedback slot above) in the subsequent preemptive access process. For details on the preemption feedback slot, see Step 5.

[0258] Step 5: If the base station has started a round of preemptive access process (equivalent to the first type of access process mentioned above), the base station sends the preemptive clock signal QueryRep_Seize (equivalent to the second indication message mentioned above). The time between two consecutive QueryRep_Seize instructions is recorded as a preemptive feedback time slot (equivalent to the first feedback time slot mentioned above. The preemptive feedback time slot is similar to Figure 6-8 but does not include the preemptive time slot. The terminal device in the triggered state counts the preemptive feedback time slot after receiving each QueryRep_Seize. For example, the time slot count is decremented (minus one) based on the above-mentioned second random number. If it is reduced to 0, RN16 is immediately fed back. (The RN16 here is still generated based on the Query instruction that starts the dynamic priority access process triggered by this round of events).

[0259] It should be noted that if a QueryRep_Seize command is the last preemption clock signal issued in a preemption access process, the time between the QueryRep_Seize command and the next QueryRep command is a preemption feedback slot. In addition, commands in the preemption access process are only executed by triggered terminal devices.

[0260] Step 6: In the preemptive access process, if the base station can correctly receive and decode the RN16, it will send an ACK instruction. The triggered terminal device receives the ACK instruction containing the matching RN16 and feeds back the EPC and / or data.

[0261] Note: During the preemptive access process, if the base station cannot successfully receive or decode RN16, it does not need to send a special instruction to indicate the decoding failure, and the subsequent process can continue. However, if the base station does not receive any response within the time window for expected reception of EPC and / or data or it cannot successfully decode EPC and / or data, it needs to send a failure indication message. After receiving the failure indication message, the triggered terminal device that has fed back EPC and / or data will transition to the normal state. The terminal device that transitions from the triggered state to the normal state will reload the value of the original time slot counter saved in step 4 into the time slot counter and randomly generate a fallback time slot number (denoted as N here) based on the fallback time slot interval in the event information for fallback. The meaning of fallback is: the terminal device that transitions from the triggered state to the normal state will only determine whether the trigger condition of at least one event is met again after experiencing N normal reply time slots (equivalent to the second feedback time slot mentioned above) based on the QueryRep instruction. If a terminal device that has sent a report does not receive a failure indication, it will exit the current access process after receiving the next matching QueryRep (equivalent to the first indication message above) or QueryRep_Seize (equivalent to the second indication message above). For example, if a triggered terminal device that has fed back EPC and / or data does not receive a failure indication, it will exit the current access process after receiving the next matching QueryRep or QueryRep_Seize.

[0262] During the preemptive access process, the terminal device may transition from the triggered state to the normal state due to detecting at least one of the following conditions:

[0263] 1) After the terminal device feeds back the preemption indication message (equivalent to the first request message above), it does not receive a preemption reply and an initialization instruction (equivalent to the first response message above). In other words, the terminal device still receives a QueryRep instruction (equivalent to the second indication message above).

[0264] 2) After the triggered terminal device feeds back RN16 when the time slot count is 0, it does not receive an ACK command;

[0265] 3) After the triggered terminal device feeds back RN16 when the time slot count is 0, it receives an ACK instruction containing an unmatched RN16;

[0266] 4) The triggered terminal device that has fed back RN16 or EPC and / or data receives failure indication information.

[0267] In addition, after the triggered state terminal device transfers to the normal state based on at least one of the above situations, it will fall back based on the failure fallback time slot indication information in the event information.

[0268] It should be noted that if the terminal device time slot that is still in the fallback phase is reduced to 0 based on the QueryRep instruction counter, it will exit the fallback phase and attempt to reply in the next normal reply time slot (equivalent to the second feedback time slot above).

[0269] It can be seen that the terminal device is in the normal state when it starts a round of event-triggered access process based on the Select / Query instruction. After that, the state transition between the trigger state and the normal state of the terminal device is shown in Figure 9.

[0270] Based on the above steps 1-6, two examples are provided, as shown in FIG10 and FIG11 respectively.

[0271] Figure 10 illustrates a conflict-free preemptive access process. In this case, during a round of event-triggered access, Terminal Device 2 meets the triggering conditions of at least one event at a certain point. It then responds with a preemption indication message in the preemption slot of the next Terminal Device reply slot and enters the triggered state. After the base station successfully decodes this message, it issues a preemption reply and initialization command, initiating another round of preemptive access. Terminal Device 2 successfully completes its reply during the preemptive access process and exits this round.

[0272] Figure 11 illustrates a scenario where a conflict in the preemptive access process requires a rollback. Terminal devices 2 and 3 meet the triggering conditions of at least one event at similar times during a round of event-triggered access. Each terminal sends back a preemption indication message in the preemption time slot of the next terminal device reply time slot and enters the triggered state. If the message is not successfully received / decoded by the base station, the base station continues to issue a QueryRep instruction after completing the subsequent normal reply time slot. After receiving the QueryRep instruction, Terminal devices 2 and 3 transition to the normal state and roll back.

[0273] It can be seen from the above examples that in the terminal device access process, the embodiment of the present disclosure takes into account that the terminal device can normally perform its own measurement and / or sensing and / or calculation process through RF and / or other energy supply before its own feedback time slot arrives. Before the terminal device's feedback time slot arrives, it may encounter a situation where an emergency response / attempt priority access is required. Therefore, an event-triggered dynamic priority access method is proposed to improve the flexibility and efficiency of the access process.

[0274] The above describes various methods of the embodiments of the present disclosure. The following further provides apparatuses for implementing the above methods.

[0275] Referring to FIG12 , an embodiment of the present disclosure further provides a terminal device, including:

[0276] The first transceiver module 1201 is configured to receive a first indication message repeatedly sent by a network device, and, if it is determined that preemptive access needs to be initiated through a preemptive time slot, send a first request message within the preemptive time slot, wherein one preemptive time slot is included between two adjacent first indication messages;

[0277] A first receiving module 1202 is configured to receive a first response message sent by the network device, wherein the first response message is used to indicate a first quantity;

[0278] The first access module 1203 is used to determine a second number that is not greater than the first number, and count the first feedback time slots based on the second indication message repeatedly sent by the received network device, and send access information to the network device when the count value of the first feedback time slot reaches the second number; wherein, one first feedback time slot is included between two adjacent second indication messages.

[0279] Optionally, the terminal device further includes:

[0280] A second access module is configured to count a second feedback time slot based on the received first indication message, and send access information to the network device when the count value of the second feedback time slot reaches a third number, wherein one second feedback time slot is included between two adjacent first indication messages.

[0281] Optionally, the terminal device further includes:

[0282] A first determining module, configured to determine whether to start a first type of access process or a second type of access process based on the event information and / or process type information sent by the network device;

[0283] a first generating module, configured to, upon determining that the first type of access process is to be initiated, generate trigger event information according to the event information, and trigger the transceiver module to execute the steps of receiving a first indication message repeatedly sent by a network device, and sending a first request message within the preemption time slot if it is determined that preemptive access needs to be initiated through a preemption time slot;

[0284] Among them, the first type of access process supports terminal devices initiating preemptive access, and the second type of access process does not support terminal devices initiating preemptive access; the event information includes triggering event information of at least one triggering event that triggers preemptive access, and the triggering event information includes triggering conditions; the process type information is used to indicate the start of the first type of access process or the second type of access process.

[0285] Optionally, the trigger condition includes at least one of the following:

[0286] a threshold corresponding to an indicator of a triggering event, and a first logical relationship between the indicator and the threshold;

[0287] The upper and lower limits of the threshold corresponding to the indicator that triggers the event;

[0288] Memory indication information used to indicate a target location in the memory of a terminal device, a codeword used to compare with a target field in the target location, and a second logical relationship between the target field and the codeword.

[0289] Optionally, the first determining module is further configured to determine, based on the event information and / or the process type information, whether to start the first type of access process, including at least one of the following methods:

[0290] Mode 1: The terminal device receives a first configuration message and the start instruction sent by a network device, wherein the first configuration message carries the event information, and the start instruction carries process type information; if the process type information indicates starting the first type of access process, the terminal device determines to start the first type of access process; in the first mode, the triggering event information is generated based on the event information carried in the first configuration message;

[0291] Second mode: The terminal device receives the start instruction sent by the network device, and determines to start the first type of access process when the start instruction carries the event information; in the second mode, the triggering event information is generated according to the event information carried by the start instruction;

[0292] The third method: the terminal device receives the first configuration message and the startup instruction sent by the network device, wherein the first configuration message carries first event information, and the startup instruction carries second event information and / or process type information; when the startup instruction carries the second event information, it is determined to start the first type of access process, and at this time, the triggering event information is generated based on the second event information; when the startup instruction does not carry the second event information but carries the process type information indicating the start of the first type of access process, it is determined to start the first type of access process, and at this time, the triggering event information is generated based on the first event information.

[0293] Optionally, the terminal device further includes:

[0294] The third access module is used to receive the first indication message repeatedly sent by the network device when it is determined to start the second type of access process, count the third feedback time slot according to the received first indication message, and send access information to the network device after the count value of the third feedback time slot reaches a fourth number, where a third feedback time slot is included between two adjacent first indication messages.

[0295] Optionally, the first determining module is further configured to determine, based on the event information and / or the process type information, whether to start the second type of access process, including at least one of the following methods:

[0296] Fourth mode: The terminal device receives the first configuration message and the start instruction sent by the network device, wherein the first configuration message carries the event information, and the start instruction carries the process type information; if the process type information indicates to start the second type of access process, determining to start the second type of access process;

[0297] Fifth mode: The terminal device receives the start instruction sent by the network device, and determines to start the second type of access process when the start instruction does not carry the event information;

[0298] The sixth method: the terminal device receives the first configuration message and the startup instruction sent by the network device, wherein the first configuration message carries event information, and the startup instruction carries event information and / or carries process type information; when the startup instruction does not carry event information and the process type information indicates to start the second type of access process, it is determined to start the second type of access process.

[0299] Optionally, the trigger event information further includes: an event identifier of the trigger event.

[0300] Optionally, the first request message includes at least one of the following information:

[0301] A preset bit sequence used to indicate a first request message;

[0302] An event identifier of a target triggering event, where the target triggering event is all or part of the triggering event that triggers the terminal device to initiate preemptive access.

[0303] Optionally, the first response message includes indication information of the first quantity, or includes indication information of the first quantity and an event identifier of the target triggering event.

[0304] Optionally, the first access module 1203 is further used to determine the first quantity based on the indication information of the first quantity in the first response message; and generate a second quantity that is not greater than the first quantity.

[0305] Optionally, the second access module is further configured to send access information to the network device when the count value of the first feedback timeslot reaches the second number, including:

[0306] Send temporary identity information of the terminal device;

[0307] Upon successfully receiving a confirmation response message sent by the network device carrying the temporary identity information of the terminal device, sending reporting information to the network device;

[0308] The reported information includes at least one of the following: terminal device identity information, event identifier and data of a target triggering event, where the target triggering event is all or part of the triggering event that triggers the terminal device to initiate preemptive access.

[0309] Optionally, the terminal device further includes:

[0310] The return control module is configured to trigger the first transceiver module to execute the step of receiving the first indication message repeatedly sent by the network device, and sending the first request message in the preemption time slot when determining that preemptive access needs to be initiated by preempting the time slot in any of the following situations:

[0311] After sending the first request message, the first response message is not successfully received;

[0312] When the count value of the first feedback time slot reaches the second number, in the process of sending access information to the network device, after sending the temporary identity information of the terminal device, the confirmation response message carrying the temporary identity information of the terminal device sent by the network device is not successfully received, or, after sending the reporting information, the failure indication information carrying the temporary identity information of the terminal device sent by the network device is received.

[0313] Optionally, the trigger event information further includes: failure fallback time slot indication information; and the terminal device further includes:

[0314] A second determining module is configured to determine a fifth number according to the failure fallback time slot indication information;

[0315] The first transceiver module is also used to, when triggered to execute the first indication message repeatedly sent by the receiving network device, and when it is determined that preemptive access needs to be initiated through the preemptive time slot, after sending the first request message within the preemptive time slot, wait for the fifth number of second feedback time slots, and then determine whether access is required through the preemptive time slot.

[0316] Optionally, the terminal device further includes:

[0317] A saving module, configured to save the count value of the second feedback timeslot after receiving the first response message;

[0318] The second access module is further configured to, when the first transceiver module is triggered to execute the first indication message repeatedly sent by the receiving network device, and when it is determined that preemptive access needs to be initiated through the preemptive time slot, continue counting the second feedback time slot according to the saved count value of the second feedback time slot after the step of sending the first request message within the preemptive time slot, and send access information to the network device after the count value of the second feedback time slot reaches the third number.

[0319] The first transceiver module determines that a preemptive access needs to be initiated by seizing a time slot, including at least one of the following:

[0320] When any trigger event meets the trigger condition of the trigger event, it is determined that preemptive access needs to be initiated by preempting the time slot, and the trigger event is used as the target trigger event;

[0321] When at least two triggering events meet their respective triggering conditions, it is determined that preemptive access needs to be initiated by preempting a time slot, and all or part of the at least two triggering events are selected as target triggering events.

[0322] It should be noted that the device in this embodiment is a device corresponding to the method applied to the terminal device side. The implementation methods in the above embodiments are all applicable to the embodiments of this device and can achieve the same technical effects. The above-mentioned device provided in the embodiment of the present disclosure can implement all the method steps implemented in the above-mentioned method embodiment and can achieve the same technical effects. The parts and beneficial effects of this embodiment that are the same as those in the method embodiment will not be described in detail here.

[0323] Referring to FIG13 , an embodiment of the present disclosure further provides a network device, including:

[0324] The first transceiver module 1301 is configured to repeatedly send a first indication message and, in a preemption time slot between two adjacent first indication messages, monitor a first request message sent by a terminal device for requesting preemptive access;

[0325] A first response module 1302 is configured to, upon successfully receiving the first request message within the preemption time slot, stop sending the first indication message, send a first response message, and repeatedly send a second indication message, wherein the first response message is used to indicate the first quantity;

[0326] The first monitoring module 1303 is configured to monitor the access information sent by the terminal device in the first number of first feedback time slots, wherein one first feedback time slot is included between two adjacent second indication messages.

[0327] Optionally, the network device further includes:

[0328] The second monitoring module is used to monitor the access information sent by the terminal device in a second feedback time slot, wherein the second feedback time slot is the remaining part between two adjacent first indication messages except the preemption time slot.

[0329] Optionally, the network device further includes:

[0330] A first starting module, configured to start a first type of access procedure and send event information, wherein the first type of access procedure supports a terminal device to initiate preemptive access, and the event information includes triggering event information of at least one triggering event for triggering preemptive access, and the triggering event information includes a triggering condition;

[0331] The first control module is used to trigger the first transceiver module to execute the steps of repeatedly sending the first indication message after starting the first type of access process, and monitoring the first request message sent by the terminal device in the preemption time slot between two adjacent first indication messages.

[0332] Optionally, the trigger condition includes at least one of the following:

[0333] a threshold corresponding to an indicator of a triggering event, and a first logical relationship between the indicator and the threshold;

[0334] The upper and lower limits of the threshold corresponding to the indicator that triggers the event;

[0335] Memory indication information used to indicate a target location in the memory of a terminal device, a codeword used to compare with a target field in the target location, and a second logical relationship between the target field and the codeword.

[0336] Optionally, the first starting module starts the first type of access process and sends event information, including at least one of the following methods:

[0337] In a first manner, the network device sends a first configuration message and a start instruction for starting an access process, wherein the first configuration message carries the event information, and the start instruction carries process type information for instructing to start the first type of access process;

[0338] Second mode: the network device sends a start instruction for starting the access process, wherein the start instruction carries the event information;

[0339] The third method: the network device sends a first configuration message and a startup instruction for starting the access process, wherein the first configuration message carries first event information, and the startup instruction carries second event information and / or carries process type information for indicating the start of the first type of access process.

[0340] Optionally, the network device further includes:

[0341] The second starting module is used to start the second type of access process, repeatedly send the first indication message, and monitor the access information sent by the terminal device between two adjacent first indication messages, wherein the second type of access process does not support the terminal device to initiate preemptive access.

[0342] Optionally, the second starting module starts the second type of access process in at least one of the following ways:

[0343] Fourth mode: the network device sends a first configuration message and a start instruction for starting the access process, wherein the first configuration message carries the event information, and the start instruction carries process type information for indicating starting the second type of access process;

[0344] Fifth mode: the network device sends a start instruction for starting the access process, wherein the start instruction does not carry the event information;

[0345] The sixth method: the network device sends a first configuration message and a start instruction for starting an access process, wherein the first configuration message carries event information, the start instruction does not carry event information, and carries process type information for indicating the start of the second type of access process.

[0346] Optionally, the trigger event information further includes: an event identifier of the trigger event.

[0347] Optionally, the first request message includes at least one of the following information:

[0348] A preset bit sequence used to indicate a first request message;

[0349] An event identifier of a target triggering event, where the target triggering event is all or part of the triggering event that triggers the terminal device to initiate preemptive access.

[0350] Optionally, the first response message includes indication information of the first quantity, or includes indication information of the first quantity and an event identifier of the target triggering event.

[0351] Optionally, the first monitoring module monitors the access information sent by the terminal device in the first feedback time slot, including at least one of the following:

[0352] When the network device successfully receives the temporary identity information of the terminal device sent by the terminal device, it sends a confirmation response message carrying the temporary identity information of the terminal device and receives the reporting information sent by the terminal device;

[0353] The network device sends a confirmation response message carrying the temporary identity information of the terminal device when successfully receiving the temporary identity information of the terminal device sent by the terminal device, and sends a failure indication message carrying the temporary identity information of the terminal device when unsuccessfully receiving the reporting information sent by the terminal device;

[0354] The network device returns to the network device and repeatedly sends the first indication message after the first number of first feedback time slots have passed, and listens to the first request message for preemptive access sent by the terminal device in the preemption time slot between two adjacent first indication messages;

[0355] The reported information includes at least one of the following: terminal device identity information, event identifier of a target triggering event, and data. The target triggering event is all or part of the triggering event that triggers the terminal device to initiate preemptive access.

[0356] Optionally, the trigger event information also includes: failure fallback time slot indication information; the failure fallback time slot indication information is used for the terminal device to determine a fifth number, and the fifth number is the number of second feedback time slots that the terminal device needs to wait for before determining again whether to initiate preemptive access when the preemptive access fails.

[0357] It should be noted that the device in this embodiment is a device corresponding to the method applied to the network device side. The implementation methods in the above embodiments are all applicable to the embodiments of this device and can achieve the same technical effects. The above-mentioned device provided in the embodiment of the present disclosure can implement all the method steps implemented in the above-mentioned method embodiment and can achieve the same technical effects. The parts and beneficial effects of this embodiment that are the same as those in the method embodiment will not be described in detail here.

[0358] A terminal device according to another embodiment of the present disclosure, as shown in FIG14 , includes a transceiver 1410, a processor 1400, a memory 1420, and a program or instruction stored on the memory 1420 and executable on the processor 1400; when the processor 1400 executes the program or instruction, each process of the method embodiment on the terminal device side described above is implemented, and the same technical effect can be achieved. To avoid repetition, details will not be given here.

[0359] The transceiver 1410 is configured to receive and send data under the control of the processor 1400 .

[0360] In FIG14 , the bus architecture may include any number of interconnected buses and bridges, specifically various circuits of one or more processors represented by processor 1400 and memory represented by memory 1420, linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described herein. The bus interface provides an interface. The transceiver 1410 may be a plurality of components, i.e., a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium. For different user devices, the user interface 1430 may also be an interface capable of externally or internally connecting required devices, and the connected devices include but are not limited to a keypad, a display, a speaker, a microphone, a joystick, and the like.

[0361] The processor 1400 is responsible for managing the bus architecture and general processing, and the memory 1420 can store data used by the processor 1400 when performing operations.

[0362] A network node according to another embodiment of the present disclosure, as shown in FIG15 , includes a transceiver 1510, a processor 1500, a memory 1520, and a program or instruction stored on the memory 1520 and executable on the processor 1500; when the processor 1500 executes the program or instruction, each process of the method embodiment on the network device side described above is implemented, and the same technical effect can be achieved. To avoid repetition, details will not be given here.

[0363] The transceiver 1510 is configured to receive and send data under the control of the processor 1500 .

[0364] In FIG15 , the bus architecture may include any number of interconnected buses and bridges, specifically various circuits of one or more processors represented by processor 1500 and memory represented by memory 1520. The bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described herein. The bus interface provides an interface. The transceiver 1510 may be a plurality of components, i.e., a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium. The processor 1500 is responsible for managing the bus architecture and general processing, and the memory 1520 may store data used by the processor 1500 when performing operations.

[0365] The present disclosure also provides a computer-readable storage medium storing a computer program. When the computer program is executed by a processor, the computer program implements the various processes of the above-mentioned method embodiment and can achieve the same technical effect. To avoid repetition, the details are not described here. The computer-readable storage medium is, for example, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0366] The embodiment of the present disclosure also provides a computer program product, including computer instructions. When the computer instructions are executed by a processor, the various processes of the above-mentioned method embodiment are implemented and the same technical effect can be achieved. To avoid repetition, they are not described here.

[0367] It should be noted that, in this document, the terms "comprises," "includes," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, article, or apparatus comprising a series of elements includes not only those elements but also other elements not explicitly listed, or elements inherent to such process, method, article, or apparatus. In the absence of further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of other identical elements in the process, method, article, or apparatus comprising the element.

[0368] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus the necessary general hardware platform, and of course can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present disclosure, or the part that contributes to the relevant technology, can be embodied in the form of a software product, and the computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), including a number of instructions for enabling a terminal device (which can be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in each embodiment of the present disclosure.

[0369] The embodiments of the present disclosure are described above in conjunction with the accompanying drawings, but the present disclosure is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of the present disclosure, ordinary technicians in this field can also make many forms without departing from the scope of protection of the purpose of the present disclosure and the claims, all of which are protected by the present disclosure.

Claims

1. An access method, applied to a terminal device, comprising: The terminal device receives the first indication message repeatedly sent by the network device, and when determining that preemptive access needs to be initiated through the preemptive time slot, sends a first request message within the preemptive time slot, wherein a preemptive time slot is included between two adjacent first indication messages; The terminal device receives a first response message sent by the network device, wherein the first response message is used to indicate a first quantity; The terminal device determines a second number that is not greater than the first number, and counts the first feedback time slots based on the second indication message repeatedly sent by the received network device, and sends access information to the network device when the count value of the first feedback time slot reaches the second number; wherein, one first feedback time slot is included between two adjacent second indication messages.

2. The method according to claim 1, further comprising: The terminal device counts the second feedback time slot based on the received first indication message, and sends access information to the network device when the count value of the second feedback time slot reaches a third number, wherein a second feedback time slot is included between two adjacent first indication messages.

3. The method according to claim 2, further comprising: The terminal device determines to start the first type of access process or the second type of access process according to the event information and / or process type information sent by the network device; When the terminal device determines to start the first type of access process, it generates trigger event information according to the event information, and enters the step of receiving the first indication message repeatedly sent by the network device, and when it is determined that preemptive access needs to be initiated through the preemptive time slot, sending a first request message within the preemptive time slot; Among them, the first type of access process supports terminal devices initiating preemptive access, and the second type of access process does not support terminal devices initiating preemptive access; the event information includes triggering event information of at least one triggering event that triggers preemptive access, and the triggering event information includes triggering conditions; the process type information is used to indicate the start of the first type of access process or the second type of access process.

4. The method according to claim 3, wherein: The triggering condition includes at least one of the following: a threshold corresponding to an indicator of a triggering event, and a first logical relationship between the indicator and the threshold; The upper and lower limits of the threshold corresponding to the indicator that triggers the event; Memory indication information used to indicate a target location in the memory of a terminal device, a codeword used to compare with a target field in the target location, and a second logical relationship between the target field and the codeword.

5. The method according to claim 3, wherein: Determining, based on the event information and / or the process type information, to initiate the first type of access process includes at least one of the following methods: Mode 1: The terminal device receives a first configuration message and a start instruction sent by a network device, wherein the first configuration message carries the event information, and the start instruction carries process type information; if the process type information indicates starting the first type of access process, the terminal device determines to start the first type of access process; in the first mode, the triggering event information is generated based on the event information carried in the first configuration message; Second mode: The terminal device receives the start instruction sent by the network device, and determines to start the first type of access process when the start instruction carries the event information; in the second mode, the triggering event information is generated according to the event information carried by the start instruction; The third method: the terminal device receives the first configuration message and the startup instruction sent by the network device, wherein the first configuration message carries first event information, and the startup instruction carries second event information and / or process type information; when the startup instruction carries the second event information, it is determined to start the first type of access process, and at this time, the triggering event information is generated based on the second event information; when the startup instruction does not carry the second event information but carries the process type information indicating the start of the first type of access process, it is determined to start the first type of access process, and at this time, the triggering event information is generated based on the first event information.

6. The method according to claim 3, further comprising: When the terminal device determines to start the second type of access process, it receives the first indication message repeatedly sent by the network device, counts the third feedback time slot based on the received first indication message, and sends access information to the network device after the count value of the third feedback time slot reaches a fourth number, and a third feedback time slot is included between two adjacent first indication messages.

7. The method according to claim 6, wherein: Determining, based on the event information and / or the process type information, to initiate the second type of access process includes at least one of the following methods: Fourth mode: The terminal device receives a first configuration message and a start instruction sent by the network device, wherein the first configuration message carries the event information, and the start instruction carries the process type information; if the process type information indicates to start the second type of access process, determining to start the second type of access process; Fifth mode: The terminal device receives the start instruction sent by the network device, and determines to start the second type of access process when the start instruction does not carry the event information; The sixth method: the terminal device receives the first configuration message and the startup instruction sent by the network device, wherein the first configuration message carries event information, and the startup instruction carries event information and / or carries process type information; when the startup instruction does not carry event information and the process type information indicates to start the second type of access process, it is determined to start the second type of access process.

8. The method according to claim 3, wherein: The trigger event information also includes: an event identifier of the trigger event.

9. The method according to claim 8, wherein The first request message includes at least one of the following information: A preset bit sequence used to indicate a first request message; An event identifier of a target triggering event, where the target triggering event is all or part of the triggering event that triggers the terminal device to initiate preemptive access.

10. The method according to claim 9, wherein: The first response message includes the indication information of the first quantity, or includes the indication information of the first quantity and the event identifier of the target triggering event.

11. The method according to claim 10, wherein: The terminal device determines a second number that is not greater than the first number, including: The terminal device determines the first quantity based on the indication information of the first quantity in the first response message; and generates a second quantity that is not greater than the first quantity.

12. The method according to claim 3, wherein: When the count value of the first feedback timeslot reaches the second number, sending access information to the network device includes: Send temporary identity information of the terminal device; Upon successfully receiving a confirmation response message sent by the network device carrying the temporary identity information of the terminal device, sending reporting information to the network device; The reported information includes at least one of the following: terminal device identity information, event identifier and data of a target triggering event, where the target triggering event is all or part of the triggering event that triggers the terminal device to initiate preemptive access.

13. The method according to claim 12, wherein: In any of the following cases, returning to the step of the terminal device receiving the first indication message repeatedly sent by the network device, and sending the first request message in the preemption time slot when determining that preemptive access needs to be initiated by preempting the time slot: After the terminal device sends the first request message, the first response message is not successfully received; When the count value of the first feedback time slot reaches the second number, in the process of sending access information to the network device, the terminal device fails to successfully receive the confirmation response message carrying the temporary identity information of the terminal device sent by the network device after sending the temporary identity information of the terminal device, or receives the failure indication information carrying the temporary identity information of the terminal device sent by the network device after sending the reporting information.

14. The method according to claim 13, wherein The trigger event information further includes: failure fallback time slot indication information; the method further includes: The terminal device determines a fifth number according to the failure fallback time slot indication information; After returning the first indication message repeatedly sent by the network device to the terminal device, and determining that it is necessary to initiate preemptive access through the preemptive time slot, after the step of sending the first request message in the preemptive time slot, the terminal device waits for the fifth number of second feedback time slots, and then determines whether it is necessary to access through the preemptive time slot.

15. The method according to claim 14, further comprising: After receiving the first response message, the terminal device saves the count value of the second feedback timeslot; After the terminal device receives the first indication message repeatedly sent by the network device and, when determining that preemptive access needs to be initiated through the preemptive time slot, sends the first request message within the preemptive time slot, the terminal device continues to count the second feedback time slot based on the saved count value of the second feedback time slot, and sends access information to the network device after the count value of the second feedback time slot reaches the third number.

16. The method according to claim 12, wherein: Determining that a preemptive access is required by preempting a timeslot includes at least one of the following: When any trigger event meets the trigger condition of the trigger event, it is determined that preemptive access needs to be initiated by preempting the time slot, and the trigger event is used as the target trigger event; When at least two triggering events meet their respective triggering conditions, it is determined that preemptive access needs to be initiated by preempting a time slot, and all or part of the at least two triggering events are selected as target triggering events.

17. An access method, applied to a network device, comprising: The network device repeatedly sends the first indication message and, in a preemption time slot between two adjacent first indication messages, listens to a first request message sent by the terminal device for requesting preemptive access; When the network device successfully receives the first request message within the preemption time slot, it stops sending the first indication message, sends a first response message, and repeatedly sends a second indication message, wherein the first response message is used to indicate the first quantity; The network device monitors the access information sent by the terminal device in the first number of first feedback time slots, wherein one first feedback time slot is included between two adjacent second indication messages.

18. The method according to claim 17, further comprising: The network device monitors the access information sent by the terminal device in a second feedback time slot, wherein the second feedback time slot is the remaining part between two adjacent first indication messages except the preemption time slot.

19. The method according to claim 17, further comprising: The network device initiates a first type of access process and sends event information, wherein the first type of access process supports the terminal device to initiate preemptive access, and the event information includes triggering event information of at least one triggering event that triggers preemptive access, and the triggering event information includes a triggering condition; After the network device starts the first type of access process, the network device repeatedly sends a first indication message and monitors a first request message sent by a terminal device in a preemption time slot between two adjacent first indication messages.

20. The method according to claim 19, wherein The triggering condition includes at least one of the following: a threshold corresponding to an indicator of a triggering event, and a first logical relationship between the indicator and the threshold; The upper and lower limits of the threshold corresponding to the indicator that triggers the event; Memory indication information used to indicate a target location in the memory of a terminal device, a codeword used to compare with a target field in the target location, and a second logical relationship between the target field and the codeword.

21. The method according to claim 19, wherein The network device initiates the first access process and sends event information, including at least one of the following methods: In a first manner, the network device sends a first configuration message and a start instruction for starting an access process, wherein the first configuration message carries the event information, and the start instruction carries process type information for instructing to start the first type of access process; Second mode: the network device sends a start instruction for starting the access process, wherein the start instruction carries the event information; The third method: the network device sends a first configuration message and a startup instruction for starting the access process, wherein the first configuration message carries first event information, and the startup instruction carries second event information and / or carries process type information for indicating the start of the first type of access process.

22. The method of claim 19, further comprising: The network device starts a second type of access process, repeatedly sends a first indication message, and monitors access information sent by the terminal device between two adjacent first indication messages, wherein the second type of access process does not support the terminal device initiating preemptive access.

23. The method according to claim 22, wherein The network device initiates the second type of access process, including at least one of the following methods: Fourth mode: the network device sends a first configuration message and a start instruction for starting the access process, wherein the first configuration message carries the event information, and the start instruction carries process type information for indicating starting the second type of access process; Fifth mode: the network device sends a start instruction for starting the access process, wherein the start instruction does not carry the event information; The sixth method: the network device sends a first configuration message and a start instruction for starting an access process, wherein the first configuration message carries event information, the start instruction does not carry event information, and carries process type information for indicating the start of the second type of access process.

24. The method according to claim 19, wherein The trigger event information also includes: an event identifier of the trigger event.

25. The method according to claim 24, wherein The first request message includes at least one of the following information: A preset bit sequence used to indicate a first request message; An event identifier of a target triggering event, where the target triggering event is all or part of the triggering event that triggers the terminal device to initiate preemptive access.

26. The method according to claim 25, wherein The first response message includes the indication information of the first quantity, or includes the indication information of the first quantity and the event identifier of the target triggering event.

27. The method according to claim 17, wherein The network device monitors access information sent by the terminal device in the first feedback time slot, including at least one of the following: When the network device successfully receives the temporary identity information of the terminal device sent by the terminal device, it sends a confirmation response message carrying the temporary identity information of the terminal device and receives the reporting information sent by the terminal device; The network device sends a confirmation response message carrying the temporary identity information of the terminal device when successfully receiving the temporary identity information of the terminal device sent by the terminal device, and sends a failure indication message carrying the temporary identity information of the terminal device when unsuccessfully receiving the reporting information sent by the terminal device; The network device returns to the network device and repeatedly sends the first indication message after the first number of first feedback time slots have passed, and listens to the first request message for preemptive access sent by the terminal device in the preemption time slot between two adjacent first indication messages; The reported information includes at least one of the following: terminal device identity information, event identifier of a target triggering event, and data. The target triggering event is all or part of the triggering event that triggers the terminal device to initiate preemptive access.

28. The method according to claim 19 or 20, wherein The trigger event information also includes: failure fallback time slot indication information; the failure fallback time slot indication information is used for the terminal device to determine the fifth number, and the fifth number is the number of second feedback time slots that the terminal device needs to wait for before determining again whether to initiate preemptive access when the preemptive access fails.

29. A terminal device comprising: A first transceiver module is configured to receive a first indication message repeatedly sent by a network device, and, if it is determined that preemptive access needs to be initiated through a preemptive time slot, send a first request message within the preemptive time slot, wherein one preemptive time slot is included between two adjacent first indication messages; A first receiving module is configured to receive a first response message sent by the network device, wherein the first response message is used to indicate a first quantity; A first access module is configured to determine a second number that is not greater than the first number, count first feedback time slots based on a received second indication message repeatedly sent by the network device, and send access information to the network device when the count value of the first feedback time slot reaches the second number; wherein one first feedback time slot is included between two adjacent second indication messages.

30. A network device comprising: A first transceiver module is configured to repeatedly send a first indication message and, in a preemption time slot between two adjacent first indication messages, monitor a first request message sent by a terminal device for requesting preemptive access; a first response module, configured to, upon successfully receiving the first request message within the preemption time slot, stop sending the first indication message, send a first response message, and repeatedly send a second indication message, wherein the first response message is used to indicate a first quantity; The first monitoring module is used to monitor the access information sent by the terminal device in the first number of first feedback time slots, wherein one first feedback time slot is included between two adjacent second indication messages.

31. A terminal device comprising: A transceiver, a processor, a memory, and a program or instruction stored in the memory and executable on the processor; wherein, when the processor executes the program or instruction, the steps of the method according to any one of claims 1 to 16 are implemented.

32. A network device comprising: A transceiver, a processor, a memory, and a program or instruction stored in the memory and executable on the processor; wherein, when the processor executes the program or instruction, the steps of the method according to any one of claims 17 to 28 are implemented.

33. A computer-readable storage medium having a computer program stored thereon, wherein when the computer program is executed by a processor, the computer program implements the steps of the method according to any one of claims 1 to 16, or implements the steps of the method according to any one of claims 17 to 28.

34. A computer program product comprising computer instructions, wherein when the computer instructions are executed by a processor, the steps of the method according to any one of claims 1 to 16 are implemented, or the steps of the method according to any one of claims 17 to 28 are implemented.

Images