Communication method, device and storage medium

Abstract

The present disclosure relates to a communication method, a device and a storage medium. The method comprises: transmitting a first message MSG1 to a node device; and receiving a second message MSG2 transmitted by the node device, wherein the MSG2 is used for processing an uplink transmission collision. In the method of the present disclosure, in an uplink transmission collision scenario, a first ambient Internet-of-Things device can perform a corresponding processing operation on the basis of an MSG2, so as to appropriately handle or resolve a collision.

Description

Communication method, device and storage medium TECHNICAL FIELD

[0001] The present disclosure relates to the technical field of communication, and particularly relates to a communication method, device and storage medium. BACKGROUND

[0002] Ambient Internet of Things (Ambient-IoT or A-IoT) devices or passive devices that support ambient power or energy harvesting from the environment can be powered by collecting radio waves, light, motion, heat or any other suitable power source, and have lower complexity, cost and maintenance cost.

[0003] SUMMARY

[0004] In a concurrent communication process, multiple ambient Internet of Things devices are supported to access a network side, and communication of the multiple ambient Internet of Things devices can conflict.

[0005] Embodiments of the present disclosure provide a communication method, device and storage medium.

[0006] In a first aspect, a communication method is provided by embodiments of the present disclosure, and the method is performed by a first ambient Internet of Things device, and the method comprises the following steps.

[0007] sending a first message MSG1 to a node device;

[0008] receiving a second message MSG2 sent by the node device, wherein the MSG2 is used to handle uplink transmission conflict.

[0009] In a second aspect, a communication method is provided by embodiments of the present disclosure, and the method is performed by a node device, and the method comprises the following steps.

[0010] receiving a first message MSG1 sent by a first ambient Internet of Things device;

[0011] when there is uplink transmission conflict, sending a second message MSG2 to the first ambient Internet of Things device, wherein the MSG2 is used to handle uplink transmission conflict.

[0012] In a third aspect, an ambient Internet of Things device is provided by embodiments of the present disclosure, and the device comprises the following steps.

[0013] a transceiver module, configured to send a first message MSG1 to a node device;

[0014] The transceiver module is further configured to receive a second message MSG2 sent by the node device, wherein the MSG2 is used to handle uplink transmission conflict.

[0015] In a fourth aspect, a node device is provided by embodiments of the present disclosure, and the device comprises the following steps.

[0016] transmitting a first message MSG1 to the first environmental IoT device;

[0017] The transceiver module is further configured to transmit a second message MSG2 to the first environmental IoT device when there is an uplink transmission conflict, where the MSG2 is used to handle the uplink transmission conflict.

[0018] In a fifth aspect, an embodiment of the present disclosure provides a communication device, comprising:

[0019] one or more processors;

[0020] The communication device is configured to implement the method of the first aspect or the second aspect.

[0021] In a sixth aspect, an embodiment of the present disclosure provides a storage medium, which stores instructions, wherein,

[0022] When the instructions run on the communication device, the communication device executes the method of the first aspect or the second aspect.

[0023] In a seventh aspect, an embodiment of the present disclosure provides a program product, wherein,

[0024] When the program product is executed by the communication device, the communication device executes the method of the first aspect or the second aspect.

[0025] In an embodiment of the present disclosure, after the first environmental IoT device transmits MSG1, the first environmental IoT device can obtain information for handling uplink transmission conflict according to MSG2 of the node device, so that in the scenario of uplink transmission conflict, the first environmental IoT device can perform corresponding processing operations based on MSG2 to reasonably cope with or solve the conflict. BRIEF DESCRIPTION OF DRAWINGS

[0026] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure, the following describes the drawings required for the embodiments, and the following drawings are only some embodiments of the present disclosure, and do not specifically limit the protection scope of the present disclosure.

[0027] FIG. 1a is an exemplary schematic diagram of an architecture of a communication system according to an embodiment of the present disclosure;

[0028] FIGS. 1b to 1f are schematic diagrams of topologies of a communication system according to an embodiment of the present disclosure;

[0029] FIG. 1g is a schematic diagram of a scenario of a communication system according to an embodiment of the present disclosure;

[0030] FIGS. 1h to 1i are application schematic diagrams in an RFID scenario;

[0031] FIGS. 2a to 2c are an exemplary interaction diagram of a method according to an embodiment of the present disclosure;

[0032] FIG. 2d is an uplink transmission conflict diagram according to an embodiment of the present disclosure;

[0033] FIGS. 3a to 3c are an exemplary flowchart of a method according to an embodiment of the present disclosure;

[0034] FIGS. 4a to 4d are an exemplary flowchart of a method according to an embodiment of the present disclosure;

[0035] FIG. 5a is a structural diagram of a device according to an embodiment of the present disclosure;

[0036] FIG. 5b is a structural diagram of a node device according to an embodiment of the present disclosure;

[0037] FIG. 6a is a diagram of a communication device according to an embodiment of the present disclosure;

[0038] FIG. 6b is a diagram of a communication device according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0039] The present disclosure provides a communication method, device and storage medium.

[0040] In a first aspect, the present disclosure provides a communication method, performed by a first environmental Internet of Things device, the method comprising:

[0041] sending a first message MSG1 to a node device;

[0042] receiving a second message MSG2 sent by the node device, the MSG2 being used to handle uplink transmission conflict.

[0043] In the above embodiments, after sending the MSG1, the first environmental Internet of Things device can obtain information for handling uplink transmission conflict according to the MSG2 of the node device, so that in the scenario of uplink transmission conflict, the first environmental Internet of Things device can perform corresponding processing operation based on the MSG2 to reasonably cope with or solve the conflict.

[0044] In combination with the embodiments of the first aspect, in some embodiments, the uplink transmission conflict comprises at least one of:

[0045] The first environmental Internet of Things device and the second environmental Internet of Things device send the MSG1 in the same time domain unit, and the MSG1 sent by the first environmental Internet of Things device and the second environmental Internet of Things device has the same or different first random number;

[0046] The first environmental IoT device and the second environmental IoT device send MSG1 in the same frequency domain unit, and the first random numbers in the MSG1 sent by the first environmental IoT device and the second environmental IoT device are the same or different.

[0047] The first environmental IoT device and the second environmental IoT device send MSG1 in different time domain units, and the first random numbers in the MSG1 sent by the first environmental IoT device and the second environmental IoT device are the same.

[0048] The first environmental IoT device and the second environmental IoT device send MSG1 in different frequency domain units, and the first random numbers in the MSG1 sent by the first environmental IoT device and the second environmental IoT device are the same.

[0049] In some embodiments, the MSG2 includes the following in combination with the embodiments of the first aspect:

[0050] A resource index, the resource index being used to indicate a frequency domain access occasion at which the corresponding environmental IoT device sends the MSG1.

[0051] In combination with the embodiments of the first aspect, in some embodiments, the method further includes:

[0052] According to whether the resource index in the MSG2 is the same as the resource index at which the first environmental IoT device sends the MSG1, it is determined whether the MSG2 is the MSG2 corresponding to the first environmental IoT device.

[0053] In combination with the embodiments of the first aspect, in some embodiments, the MSG2 further includes at least one of the following:

[0054] A first random number;

[0055] A second random number allocated for the first environmental IoT device, the second random number being different from the first random number, and the second random number being used for communication with the node device after the MSG2;

[0056] A time-frequency resource used for the first environmental IoT device to send a third message MSG3.

[0057] In combination with the embodiments of the first aspect, in some embodiments, the method further includes:

[0058] Sending the MSG3 on the time-frequency resource used for the first environmental IoT device to send the MSG3, the MSG3 containing a device identifier corresponding to the environmental IoT device and / or the second random number.

[0059] In combination with the embodiments of the first aspect, in some embodiments, the MSG2 includes the following:

[0060] The indication information is used for indicating that there is an uplink sending conflict.

[0061] In some embodiments of the first aspect, the MSG2 further comprises at least one of:

[0062] a first random number;

[0063] a resource index, the resource index being used for indicating a frequency domain access occasion in which the corresponding environmental IoT device sends the MSG1;

[0064] one or more time-frequency resources for sending the MSG3.

[0065] In some embodiments of the first aspect, when the MSG2 comprises the first random number and the indication information, the method further comprises:

[0066] determining, according to the indication information, whether to send a third message MSG3 to the node device.

[0067] In some embodiments of the first aspect, when the MSG2 comprises the resource index and the indication information, the method further comprises:

[0068] determining, according to the indication information, whether to resend the first message MSG1 to the node device.

[0069] In some embodiments of the first aspect, when the MSG2 comprises the plurality of time-frequency resources for sending the MSG3, the method further comprises:

[0070] selecting one time-frequency resource from the plurality of time-frequency resources for sending the MSG3;

[0071] sending the MSG3 to the node device according to the selected time-frequency resource.

[0072] In some embodiments of the first aspect, the method further comprises:

[0073] receiving a fourth message MSG4 sent by the node device, the MSG4 comprising a second random number allocated to the first environmental IoT device, the second random number being used for communication with the node device after the MSG4.

[0074] In some embodiments of the first aspect, the MSG2 comprises:

[0075] a device identifier corresponding to the first environmental IoT device.

[0076] In some embodiments of the first aspect, the MSG2 further comprises at least one of:

[0077] a first random number;

[0078] a second random number allocated for the first environmental IoT device, the second random number being used for a communication with the node device after the MSG2.

[0079] With reference to the embodiments of the first aspect, in some embodiments, the method further includes:

[0080] sending uplink information to the node device according to the second random number, or receiving downlink information sent by the node device.

[0081] According to a second aspect, the present disclosure provides a communication method, performed by a node device, the method comprising:

[0082] receiving a first message MSG1 sent by a first environmental IoT device;

[0083] when there is an uplink sending conflict, sending a second message MSG2 to the first environmental IoT device, the MSG2 being used for handling the uplink sending conflict.

[0084] With reference to the embodiments of the second aspect, in some embodiments, the uplink sending conflict includes at least one of:

[0085] the first environmental IoT device and a second environmental IoT device send the MSG1 in a same time domain unit, the first random number in the MSG1 sent by the first environmental IoT device and the second environmental IoT device being same or different;

[0086] the first environmental IoT device and the second environmental IoT device send the MSG1 in a same frequency domain unit, the first random number in the MSG1 sent by the first environmental IoT device and the second environmental IoT device being same or different;

[0087] the first environmental IoT device and the second environmental IoT device send the MSG1 in different time domain units, the first random number in the MSG1 sent by the first environmental IoT device and the second environmental IoT device being same;

[0088] the first environmental IoT device and the second environmental IoT device send the MSG1 in different frequency domain units, the first random number in the MSG1 sent by the first environmental IoT device and the second environmental IoT device being same.

[0089] With reference to the embodiments of the second aspect, in some embodiments, the MSG2 includes:

[0090] a resource index, the resource index being used for indicating a frequency domain access occasion at which a corresponding environmental IoT device sends the MSG1.

[0091] In some embodiments of the second aspect, the MSG2 further comprises at least one of:

[0092] the first random number;

[0093] a second random number allocated to the first environmental IoT device, the second random number being different from the first random number, the second random number being used for communication with the first environmental IoT device after the MSG2;

[0094] a time-frequency resource for the first environmental IoT device to send the MSG3.

[0095] In some embodiments of the second aspect, the method further comprises:

[0096] receiving the MSG3 sent by the first environmental IoT device, the MSG3 containing at least the device identifier corresponding to the first environmental IoT device and / or the second random number.

[0097] In some embodiments of the second aspect, the MSG2 comprises:

[0098] indication information indicating that there is an uplink sending conflict.

[0099] In some embodiments of the second aspect, the MSG2 further comprises at least one of:

[0100] the first random number;

[0101] a plurality of time-frequency resources for sending the MSG3;

[0102] a resource index, the resource index being used to indicate a frequency domain access occasion in which the corresponding environmental IoT device sends the MSG1.

[0103] In some embodiments of the second aspect, when the MSG2 comprises a plurality of time-frequency resources for sending the MSG3, the method further comprises:

[0104] receiving the MSG3 sent by the first environmental IoT device, the MSG3 being sent based on one of the plurality of time-frequency resources for sending the MSG3.

[0105] In some embodiments of the second aspect, the method further comprises:

[0106] sending the MSG4 to the first environmental IoT device, the MSG4 comprising the device identifier corresponding to the first environmental IoT device and a second random number allocated to the environmental IoT device, the second random number being used for communication with the first environmental IoT device after the MSG4.

[0107] In some embodiments, the MSG2 further comprises at least one of the following in combination with the embodiments of the second aspect:

[0108] a device identifier corresponding to the first environmental IoT device.

[0109] In some embodiments, the MSG2 further comprises at least one of the following in combination with the embodiments of the second aspect:

[0110] the first random number;

[0111] a second random number allocated for the first environmental IoT device, the second random number being used for communication with the first environmental IoT device after the MSG2.

[0112] In some embodiments, the method further comprises the following in combination with the embodiments of the second aspect:

[0113] when there is an uplink transmission conflict, ignoring the received MSG1 corresponding to the environmental IoT device in the uplink transmission conflict, and not sending the MSG2 corresponding to the environmental IoT device in the uplink transmission conflict.

[0114] In a third aspect, the embodiments of the present disclosure provide an environmental IoT device, comprising:

[0115] a transceiver module, configured to send a first message MSG1 to a node device;

[0116] the transceiver module is further configured to receive a second message MSG2 sent by the node device, the MSG2 being used to handle an uplink transmission conflict.

[0117] In a fourth aspect, the embodiments of the present disclosure provide a node device, comprising:

[0118] a transceiver module, configured to receive a first message MSG1 sent by a first environmental IoT device;

[0119] the transceiver module is further configured to, when there is an uplink transmission conflict, send a second message MSG2 to the first environmental IoT device, the MSG2 being used to handle the uplink transmission conflict.

[0120] In a fifth aspect, the embodiments of the present disclosure provide a communication device, comprising:

[0121] one or more processors;

[0122] The communication device is configured to implement the method of the first aspect or the second aspect.

[0123] In a sixth aspect, the embodiments of the present disclosure provide a storage medium, the storage medium storing instructions, wherein:

[0124] The instructions, when executed on the communication device, cause the communication device to perform the method of the first aspect, or the second aspect.

[0125] In a seventh aspect, an embodiment of the present disclosure provides a program product, wherein,

[0126] The program product, when executed by the communication device, causes the communication device to perform the method of the first aspect, or the second aspect.

[0127] In an eighth aspect, an embodiment of the present disclosure provides a computer program, which, when executed on a computer, causes the computer to perform the method described in the first aspect, the second aspect, or the optional implementation of the third aspect.

[0128] In a ninth aspect, an embodiment of the present disclosure provides a chip or chip system. The chip or chip system includes processing circuitry configured to perform the method described in the first aspect, the second aspect, or the optional implementation of the third aspect.

[0129] It can be understood that the terminal, the device, the communication system, the storage medium, the program product, the computer program, the chip or the chip system are all used to perform the method proposed in the embodiments of the present disclosure. Therefore, the beneficial effects that can be achieved are referred to the beneficial effects in the corresponding method, which will not be described here.

[0130] The embodiments of the present disclosure are not exhaustive, but only illustrate some embodiments, and are not specific limitations on the protection scope of the present disclosure. In the case of no contradiction, each step in an embodiment can be implemented as an independent embodiment, and the steps can be combined arbitrarily, for example, the scheme after removing some steps in an embodiment can also be implemented as an independent embodiment, and the order of the steps in an embodiment can be exchanged arbitrarily, in addition, the optional implementation in an embodiment can be combined arbitrarily; in addition, the embodiments can be combined arbitrarily, for example, some or all steps of different embodiments can be combined arbitrarily, an embodiment can be combined with the optional implementation of other embodiments.

[0131] In each embodiment of the present disclosure, if there is no special description and logical conflict, the terms and / or descriptions between the embodiments are consistent and can be referred to each other, and the technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0132] The terms used in the embodiments of the present disclosure are only for the purpose of describing specific embodiments, and not as a limitation on the present disclosure.

[0133] In the embodiments of the present disclosure, an element expressed in singular form, such as "a", "an", "the", "said", "the aforementioned", "the foregoing", "this", and the like, unless otherwise specified, can represent "one and only one", or can represent "one or more", "at least one", and the like. For example, in the case of using an article such as "a", "an", "the" in English, the noun after the article can be understood as a singular expression, or can be understood as a plural expression.

[0134] In the embodiments of the present disclosure, "plurality" refers to two or more.

[0135] In some embodiments, the terms "at least one of", "one or more", "a plurality of", "multiple", and the like can be replaced with each other.

[0136] In some embodiments, the description modes such as "at least one of A, B", "A and / or B", "A in one case and B in another case", "in response to a case A, in response to a case B", and the like can include the following technical solutions according to the case: in some embodiments, A is executed regardless of B; in some embodiments, B is executed regardless of A; in some embodiments, A and B are selectively executed from A and B; in some embodiments, A and B are executed (A and B are both executed). When there are more branches such as A, B, C, and the like, it is similar to the above.

[0137] In some embodiments, the description modes such as "A or B" and the like can include the following technical solutions according to the case: in some embodiments, A is executed regardless of B; in some embodiments, B is executed regardless of A; in some embodiments, A and B are selectively executed from A and B (A and B are selectively executed). When there are more branches such as A, B, C, and the like, it is similar to the above.

[0138] The prefix words of "first", "second" and the like in the embodiments of the present disclosure are merely used to distinguish different description objects, and do not constitute limitation on the position, order, priority, quantity or content of the description objects. The description objects are described in the claims or embodiments, and should not be construed as redundant limitation because of the use of the prefix words. For example, the description object is "field", and the ordinal words before "field" in "first field" and "second field" do not limit the position or order between "fields", and "first" and "second" do not limit whether the "fields" modified thereby are in the same message or not, nor limit the order of "first field" and "second field". For another example, the description object is "level", and the ordinal words before "level" in "first level" and "second level" do not limit the priority between "levels". For another example, the quantity of the description object is not limited by the ordinal words, and can be one or more. For example, "first device", wherein the quantity of "device" can be one or more. In addition, the objects modified by different prefix words can be the same or different, for example, the description object is "device", and "first device" and "second device" can be the same device or different devices, and the types thereof can be the same or different; for another example, the description object is "information", and "first information" and "second information" can be the same information or different information, and the contents thereof can be the same or different.

[0139] In some embodiments, "including A", "containing A", "for indicating A", "carrying A" can be interpreted as directly carrying A, or indirectly indicating A.

[0140] In some embodiments, the terms of "in response to", "in response to determining", "in the case of", "when", "when", "if", "if" and the like can be replaced with each other.

[0141] In some embodiments, the terms of "greater than", "greater than or equal to", "not less than", "more than", "more than or equal to", "not less than", "higher than", "higher than or equal to", "not lower than", "above" and the like can be replaced with each other, and the terms of "less than", "less than or equal to", "not greater than", "less than", "less than or equal to", "not more than", "lower than", "lower than or equal to", "not higher than", "below" and the like can be replaced with each other.

[0142] In some embodiments, the apparatuses and devices can be interpreted as entities, and can also be interpreted as virtual, whose names are not limited to the names described in the embodiments, and in some cases can also be understood as "equipment", "device", "circuit", "network element", "node", "function", "unit", "section", "system", "network", "chip", "chip system", "entity", "subject", etc.

[0143] In some embodiments, "network" can be interpreted as an apparatus contained in the network, such as a network device, an access network device, a core network device, etc.

[0144] In some embodiments, "access network device (AN device)" can also be referred to as "radio access network device (RAN device)", "base station (BS)", "radio base station", "fixed station", and in some embodiments can also be understood as "node", "access point", "transmission point (TP)", "reception point (RP)", "transmission / reception point (TRP)", "panel", "antenna panel", "antenna array", "cell", "macro cell", "small cell", "femto cell", "pico cell", "sector", "cell group", "serving cell", "carrier", "component carrier", "bandwidth part (BWP)", etc.

[0145] In some embodiments, a "terminal" or "terminal device" can be referred to as a "user equipment" (UE), a "user terminal," a "mobile station" (MS), a "mobile terminal" (MT), a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, and / or the like.

[0146] In some embodiments, data, information and / or the like can be obtained in compliance with laws and regulations of a country where the data, information and / or the like is obtained.

[0147] In some embodiments, data, information and / or the like can be obtained after obtaining consent of a user.

[0148] In addition, each element, each row, or each column in the table of the embodiments of the present disclosure can be implemented as an independent embodiment, and any combination of any element, any row, and any column can also be implemented as an independent embodiment.

[0149] FIG. 1a is a schematic diagram of an architecture of a communication system according to an embodiment of the present disclosure, and FIGS. 1b to 1f are schematic diagrams of topologies of the communication system according to an embodiment of the present disclosure.

[0150] As shown in FIG. 1a, the communication system 100 can include a first environment Internet of Things device 101 and a node device 102.

[0151] In some embodiments, the first ambient IoT device 101 can refer to one of a plurality of ambient IoT devices, which can be referred to as a device (Device) for short. Alternatively, the ambient IoT device can be replaced by or referred to as a tag, a terminal, an Ambient-IoT terminal, a passive terminal, a passive node, etc.

[0152] The ambient IoT device can have low memory, low processing power, low power, small data transmission, and mass deployment, etc. It can be maintenance-free and has a long service life, for example, the service life of the ambient IoT device can be more than 10 years. The ambient IoT device supports ambient power, which is powered by energy harvesting, has no battery or limited energy storage capacity (such as using a capacitor). For example, the ambient IoT device needs to collect radio waves transmitted by a network node to obtain energy to drive itself to work. Therefore, before obtaining energy, the ambient IoT device is usually in a "shutdown" state, i.e., an off-network state. Therefore, the communication system 100 needs to support a data communication mode with shorter transmission time, lower memory consumption, and more convenient terminal management to complete the data communication process as soon as possible.

[0153] In some embodiments, the ambient IoT device has different power acquisition and storage capabilities according to different types and working modes of the ambient IoT device.

[0154] For example, the types of ambient IoT devices can include the following:

[0155] Device 1 (Device1) or Device A: no energy storage capability, cannot generate or amplify signals independently, and Device 1 can communicate using backscattering.

[0156] Device 2a (Device2a) or Device B: has energy storage capability, cannot generate signals independently, and Device 2a can communicate using backscattering, and the stored energy can be used for amplification of reflected signals.

[0157] Device 2b (Device2b) or Device C: has energy storage capability and can independently generate signals, such as having an active radio frequency (RF) component for transmission.

[0158] In some embodiments, a harmonized air interface design is intended to minimize the differences of ambient IoT, such as supporting devices that meet the following characteristics or constraints:

[0159] The peak power consumption is about 1 micro-watt (μW), with energy storage function, the initial sampling frequency offset (SFO) is up to 10X ppm, and the device does not support downlink (DL) signal amplification or uplink (UL) signal amplification; the UL signal transmission of the device needs to be backscattered on the externally provided carrier;

[0160] The peak power consumption is less than several hundred μW, with energy storage function, the SFO is up to 10X ppm, and the device has DL signal and / or UL signal amplification function. The UL signal transmission of the device can be generated internally or backscattered on the externally provided carrier. Wherein, X can be determined by the protocol.

[0161] In some embodiments, the node device 102 can include one or more network-side nodes or devices, or nodes or devices that assist in implementing network-side functions. In order to support the data transmission of Ambient-IoT devices, the node device 102 can implement one or more of the following functions:

[0162] Energy source (ES) function: providing energy for Ambient-IoT devices, which can be used for device 2a and device 2b;

[0163] Downlink transmission (DT) function: triggering the uplink transmission of Ambient-IoT devices by sending indication information.

[0164] Continuous wave (CW) excitation function: providing electromagnetic waves required for backscattering for Ambient-IoT devices, which can be used for device 1 and device 2a to realize uplink transmission by backscattering CW. CW is actually also an ES, and Ambient-IoT devices can receive CW and store energy.

[0165] Uplink receiver (UR) function: receiving the uplink information backscattered by Ambient-IoT devices, or receiving the uplink information actively transmitted by Ambient-IoT devices.

[0166] In some embodiments, one node device 102 can simultaneously implement multiple or all of the above functions; or the node device 102 includes multiple network nodes, each of which is used to implement one of the functions. Among them, the network node implementing each function can be a user equipment (UE), a repeater, or a base station, etc. When each network node implements one function, the network can coordinate or control the behavior of different nodes.

[0167] In some embodiments, the node device 102, when being a network device, can include at least one of an access network device and a core network device.

[0168] Optionally, the access network device, for example, is a node or device that accesses a terminal to a wireless network, and the access network device can include at least one of a base station in a 5G communication system, an evolved NodeB (eNB), a next generation eNB (ng-eNB), a next generation NodeB (gNB), a node B (NB), a home node B (HNB), a home evolved node B (HeNB), a wireless backhaul device, a radio network controller (RNC), a base station controller (BSC), a base transceiver station (BTS), a base band unit (BBU), a mobile switching center, a base station in a 6G communication system, an open base station (Open RAN), a cloud base station (Cloud RAN), a base station in other communication systems, an access node in a wireless fidelity (WiFi) system, but is not limited thereto.

[0169] Optionally, the access network device can be composed of a central unit (CU) and a distributed unit (DU), wherein the CU can also be referred to as a control unit, and the CU-DU structure can split the protocol layers of the access network device, and the functions of part of the protocol layers are placed in the CU for centralized control, and the functions of the remaining part or all of the protocol layers are distributed in the DU and controlled by the CU, but is not limited thereto.

[0170] Optionally, the core network device can be one device including one or more network elements, or can be multiple devices or device groups each including all or part of one or more network elements. The network element can be virtual or physical. The core network includes, for example, at least one of an evolved packet core (EPC), a 5G core network (5GCN), and a next generation core (NGC). Alternatively, the core network device refers to a network element with specific functions, such as an access management function (AMF), a service management function (SMF), and the like.

[0171] As shown in topology 1 of FIG. 1b, the first ambient IoT device 101 and the node device 102 can directly communicate, and directly perform DL and UL data reception and transmission. For example, the node device 102 directly interacts with the first ambient IoT device 101 to exchange ambient IoT data or signaling.

[0172] As shown in topology 2 of FIG. 1c, the first ambient IoT device 101 and the node device 102 indirectly perform DL and UL data reception and transmission, and the intermediate node 103 is used for forwarding.

[0173] In some embodiments, the intermediate node 103 can be a relay, a repeater, an integrated access backhaul (IAB), or a user equipment (UE).

[0174] As shown in topology 3 of FIG. 1d and FIG. 1e, the first ambient IoT device 101 and the node device 102 indirectly perform DL and UL data reception and transmission, and then there is an assisting node 104 on the UL or DL, which is responsible for receiving or transmitting UL or receiving DL data.

[0175] In some embodiments, the assisting node 104 can be a relay, a repeater, an IAB, or a UE. The UE can refer to the description of the foregoing embodiments, which will not be described here.

[0176] As shown in Fig. 1f, the topology 4, the first environmental IoT device 101 directly receives and transmits data with the UE 105 in DL and UL; the UE 105 is responsible for collecting data and forwarding the collected data to the network side, such as the node device 102.

[0177] In the above embodiments, the UE includes at least one of a mobile phone, a wearable device, an IoT device, a car with communication function, a smart car, a Pad, a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical surgery, a wireless terminal device in smart grid, a wireless terminal device in transportation safety, a wireless terminal device in smart city, a wireless terminal device in smart home, but is not limited thereto.

[0178] In some embodiments, the communication between the first environmental IoT device 101 and the node device 102, such as the communication based on the topologies 1 and 2, can use spectrum resources in three forms: In-Band, Guard Band and Stand-alone. Among them, In-band uses normal NR communication DL and / or UL spectrum resources, such as the DL / UL communication (Fig. 1b) spectrum resources of the base station and other UEs, or the DL / UL communication (Fig. 1c) spectrum resources between the UE and the base station. Guard-band uses the spectrum resources of the guard band of the normal NR communication DL and / or UL spectrum, and Stand alone uses the spectrum resources unrelated to the NR communication.

[0179] In some embodiments, the number of devices or nodes in Figs. 1a-1f is only illustrative, and in actual applications, the devices or nodes can adopt multiple.

[0180] In some embodiments, the technical solutions of the present disclosure can be applied to the Open RAN architecture, at this time, the interfaces between the access network devices or within the access network devices involved in the embodiments of the present disclosure can become internal interfaces of the Open RAN, and the processes and information interactions between these internal interfaces can be realized through software or programs.

[0181] It can be understood that the communication system described in the embodiments of the present disclosure is for more clearly illustrating the technical solutions of the embodiments of the present disclosure, and does not constitute a limitation on the technical solutions provided by the embodiments of the present disclosure. Those skilled in the art can know that, with the evolution of system architecture and the appearance of new business scenarios, the technical solutions provided by the embodiments of the present disclosure are also applicable to similar technical problems.

[0182] The embodiments of the present disclosure described below can be applied to the communication system 100 shown in FIGS. 1a to 1f or part of the subjects, but are not limited thereto.

[0183] The subjects shown in FIGS. 1a to 1f are examples. The communication system can include all or part of the subjects in FIGS. 1a to 1f, or other subjects other than FIGS. 1a to 1f. The number and form of each subject is arbitrary. The connection relationship between the subjects is exemplary. The subjects can not be connected or can be connected. The connection can be in any manner, can be direct connection or indirect connection, and can be wired connection or wireless connection.

[0184] Embodiments of the present disclosure can be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G new radio (NR), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Future generation radio access (FX), Global System for Mobile communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (Bluetooth (registered trademark)), Public Land Mobile Network (PLMN) network, Device-to-Device (D2D) system, Machine to Machine (M2M) system, Internet of Things (IoT) system, Vehicle-to-Everything (V2X), system using other communication processing methods, next-generation system expanded based thereon, and the like. Further, a plurality of systems can be applied in combination (for example, combination of LTE or LTE-A and 5G, and the like).

[0185] Traditional Internet of Things (IoT) devices are usually powered by a battery with limited life span. With the popularity of IoT networks and the large number of IoT devices, the problems of battery maintenance, battery recycling, and battery replacement of traditional IoT devices are increasingly serious. The batteries that cannot be successfully recycled will also have harmful effects on the ecology and environment. Based on this, environmentally friendly and safe battery-free communication has emerged. Battery-free communication can improve network performance and sustainability, expand application scenarios, and significantly reduce device size and cost.

[0186] In 5G communication technology, existing low-power wide-area (LPWA) technologies such as machine type communication (MTC), narrowband Internet of Things (NB-IoT), reduced capability (RedCap), etc. can meet the growing demand of vertical fields, and can achieve low cost, low power consumption and large-scale connection. However, the following needs cannot be met: first, devices driven by traditional batteries are not suitable, for example, in extreme environmental conditions (such as high pressure, extremely high / low temperature, humid environment); second, maintenance-free devices are needed (for example, traditional batteries do not need to be replaced); finally, ultra-low complexity, very small device size or form factor (such as mm thickness), longer life cycle, etc. are needed. IoT that supports environmental power or environmental energy can meet the above needs.

[0187] Low-power IoT communication chips such as Bluetooth Low Energy (BLE), Long Range Radio (LoRa), or NB-IoT have a transmit-receive power consumption of tens of milliwatts or even hundreds of milliwatts. In combination with the description of the foregoing embodiments, the energy harvested from the environment is only in the order of microwatts. The energy harvested from the environment can drive the perception node such as the environmental IoT device 101 to perform data transmission and wireless communication. Wireless communication technology that can reduce communication energy consumption to tens of microwatts or even below ten microwatts is needed, such as backscatter communication.

[0188] Backscatter communication is a modulation and transmission technology with extremely low power consumption using the principle of radio frequency signal backscattering, and is a means to realize everything intelligent connection. In backscatter communication, since part of the radio frequency signal such as electromagnetic wave is reflected when reaching the surface of an object, a passive node such as an environmental Internet of Things device 101 as a sending node adjusts the matching between the receiving antenna and the impedance according to the information to be sent, enhances the reflection of the incident radio frequency signal, and modulates the sensing data obtained by itself onto the reflected signal to complete the sending of data. Compared with other communication technologies, backscatter communication does not require complex radio frequency structures, reduces the use of power amplifiers, high-precision crystal oscillators, duplexers, high-precision filters and other devices, and does not require complex baseband processing, so it can simplify terminal design and greatly reduce the cost of terminal nodes.

[0189] In a wireless radio frequency identification (RFID) system applying backscatter communication, as shown in FIG. 1g, a receiver sends a radio frequency excitation signal to activate a passive node. The receiver is, for example, an RFID reader (Reader) corresponding to the node device 102, and the passive node is, for example, an RFID electronic tag (tag) corresponding to the first environmental Internet of Things device 101. The electronic tag modulates its own information onto the radio frequency signal using backscatter communication, and the reader receives the reflected signal of the passive electronic tag and demodulates it to achieve information transmission. The RFID communication process has the following disadvantages: the wireless signal will experience double-path fading, the path loss is large, the effective communication distance is short, and therefore the coverage distance is small; single-channel transmission is required; the tag needs to be strictly aligned; there is no power control, etc. It is necessary to integrate 3GPP communication technology to improve the wireless communication performance of the RFID technology in the passive Internet of Things.

[0190] In the RFID communication system, as shown in FIG. 1h, from the perspective of use, it is divided into three types of commands: tag selection (Select), inventory (Inventory) and access (Access). Among them: the selection command includes: Select command and Challenge command. The inventory command includes: Query command, QueryAdjust command, QueryRep command, ACK command and NAK command. The access command includes: Req_RN command, Read command, Write command, Kill command and Lock command; optionally, it can also include: Access command, BlockWrite command and BlockErase command.

[0191] In combination with the inventory and access example shown in FIG. 1i, the command application examples in inventory and access can include:

[0192] (1) After the tag receives a valid Query command, each tag that meets the set criteria generates a random number. Each tag with a random number of zero will produce a response, such as sending back a temporary password RN16, which is a 16-bit random number, and moving to the Reply state; other tags can change some attributes and flags, and exit the group of tags with a random number of zero, which is conducive to reducing repeated identification.

[0193] (2) After the tag receives a valid QueryAdjust command, each tag respectively generates a new random number, and the other behaviors are the same as the Query command.

[0194] (3) After the tag receives a valid QueryRep command, the original random number of each tag in the tag group is reduced by one, and the other behaviors are the same as the Query command.

[0195] (4) Only a single tag can receive a valid ACK command, and after receiving the ACK command, the tag sends back the content in the EPC area according to the Electronic Product Code (EPC) communication protocol. Among them, the ACK command can use the above RN16 or Handle, which is a 16-bit random number temporarily representing the identity of the tag.

[0196] (5) After the tag receives a valid NAK command, the tag in the Ready state and the Killed state remains in the original state, and the tag in other states all moves to the Arbitrate state. Among them, the several states of the tag are shown in FIG. 1h.

[0197] In RFID, after the tag receives the Query command of the interrogator, the Query command carries a Q, and the value of Q is (0..15). The tag will generate a random number in the range of (0...2 Q -1) using a random number generator RNG according to this Q value. Based on RN16, the identification and access operation for a specific tag can be completed, and after obtaining the Electronic Product Code (EPC), the network side identifies a tag. The network side asks the tag for a new random value Handle before starting the access command operation for the tag. Subsequent communication is based on Handle to identify a tag. The network side asks the tag for a new random value, i.e., handle, before starting the access command operation for a specific tag. Subsequent communication is based on handle to identify a tag.

[0198] RFID communication conforms to the half-duplex EPC protocol, which allows one reader to send signals or one tag to send signals in one transmission. The reader and the tag do not send signals at the same time, and different tags work in series. In ambient IOT, concurrent communication needs to be considered, such as the existence of multiple tags and network sides at the same time, and 1-to-1 operations such as access command-like commands, which need to ensure the uniqueness of Handle. In addition, the negotiation process signaling interaction of RN16 in RFID communication is complex and affects communication efficiency.

[0199] In ambient IOT, different ambient IOT devices can access the network side based on competition-based (CB) initial access or random access. In such concurrent communication processes, multiple devices or multiple tags that perform initial access may collide when accessing the network side.

[0200] FIG. 2a is an interaction diagram of a communication method according to an embodiment of the present disclosure. As shown in FIG. 2a, the embodiment of the present disclosure relates to a communication method, and the method comprises:

[0201] In step S2101, the node device 102 sends a trigger instruction to the first ambient IOT device 101.

[0202] In some embodiments, the node device 102 can include one or more of a network device, a base station, an intermediate node, an auxiliary node, or a UE. Alternatively, the node device 102 can be a reader. The node device 102 can be used to implement one or more of the following functions: ES function, DT function, CW excitation function, and UR function.

[0203] For example, when the node device 102 is a base station or a network device, the first ambient IOT device 101 can directly communicate with the node device 102 based on topology 1, such as directly sending MSG1; or communicate with the node device 102 through a UE based on topology 2, such as sending MSG1 to the UE and forwarding relevant information to the node device 102 through the UE.

[0204] In some embodiments, the first ambient IOT device 101 can be a passive node or simply a device, or the first ambient IOT device 101 can be an electronic tag. The first ambient IOT device 101 can refer to one of a plurality of ambient IOT devices, or in other words, any ambient IOT device can perform the method related to the embodiments of the present disclosure according to the description of the first ambient IOT device 101.

[0205] In some embodiments, the trigger instruction can be a R2D (Reader to Device) instruction sent by the reader to the first environmental IoT device 101 for triggering the CB access of the first environmental IoT device 101.

[0206] In some embodiments, in the concurrent communication, the node device 102 can send the trigger instruction to multiple environmental IoT devices, such as sending the trigger instruction to Device1 and Device2 respectively. Among them, the first environmental IoT device 101 can refer to any one of Device1 and Device2.

[0207] In some embodiments, after receiving the trigger instruction, the first environmental IoT device 101 can initiate the access, as described in step S2102.

[0208] In step S2102, the first environmental IoT device 101 sends MSG1 to the node device 102.

[0209] In some embodiments, in the concurrent communication, multiple environmental IoT devices or different environmental IoT devices can send MSG1 to the node device 102 respectively. For example, Device1 and Device2 send MSG1 to the node device 102 respectively.

[0210] In some embodiments, each environmental IoT device such as the first environmental IoT device 101 can include a random number RN16 generated by the environmental IoT device in the MSG1 sent by the environmental IoT device, and the RN16 can be used to identify the environmental IoT device.

[0211] In an example, for each environmental IoT device sending MSG1, in the 2-step CB access, the MSG1 sent by each environmental IoT device includes RN16 and the device ID of the environmental IoT device 101.

[0212] In some embodiments, when multiple environmental IoT devices send MSG1 respectively, uplink transmission conflicts can occur or exist.

[0213] In some embodiments, the uplink transmission conflict includes at least one of the following:

[0214] Multiple environmental IoT devices send MSG1 in the same time domain unit, wherein the MSG1 sent by the multiple environmental IoT devices in the same time domain unit is the same or different; for example, the first environmental IoT device and the second environmental IoT device send MSG1 in the same time domain unit, and the first random number in the MSG1 sent by the first environmental IoT device and the second environmental IoT device is the same or different.

[0215] The plurality of environmental IoT devices transmit MSG1 in the same frequency domain unit, wherein the MSG1 transmitted by the plurality of environmental IoT devices in the same frequency domain unit are the same or different; for example, the first environmental IoT device and the second environmental IoT device transmit MSG1 in the same frequency domain unit, and the first random number in the MSG1 transmitted by the first environmental IoT device and the second environmental IoT device are the same or different.

[0216] The MSG1 transmitted by the plurality of environmental IoT devices in different time domain units are the same; for example, the first environmental IoT device and the second environmental IoT device transmit MSG1 in different time domain units, and the first random number in the MSG1 transmitted by the first environmental IoT device and the second environmental IoT device are the same.

[0217] The MSG1 transmitted by the plurality of environmental IoT devices in different frequency domain units are the same; for example, the first environmental IoT device and the second environmental IoT device transmit MSG1 in different frequency domain units, and the first random number in the MSG1 transmitted by the first environmental IoT device and the second environmental IoT device are the same.

[0218] Optionally, the same time domain unit can be within one time slot, within one access time, or within one access retransmission time. For example, in a scenario where the environmental IoT device supports frequency division multiple access (FDMA), the uplink transmission conflict can be that the plurality of environmental IoT devices transmit MSG1 in the same time domain unit, and the plurality of environmental IoT devices can transmit MSG1 using different frequency domain access occasions within one time slot or one access retransmission time; the MSG1 transmitted by the plurality of environmental IoT devices can contain the same first random number. The first random number can be used to represent the same RN16 in the MSG1 transmitted in the uplink transmission conflict at this time.

[0219] As shown in the example of FIG. 2d, Device1 and Device2 transmit MSG1 in different frequency domain access occasions within one time slot or one access retransmission time, and the RN16 in the MSG1 transmitted by the two devices are the same, both being a, i.e., the first random number is the same. At this time, there is an uplink transmission conflict.

[0220] Optionally, the same frequency domain unit can be within one channel, within one subchannel, within one bandwidth, or within one frequency range, etc. For example, in a scenario where the environmental IoT device supports time division multiplexing (TDM), the uplink transmission conflict can be that multiple environmental IoT devices send MSG1 in the same frequency domain unit, which can be in different time domain occasions in the same frequency domain unit; the MSG1 sent by the multiple environmental IoT devices can contain the same first random number. The first random number can be used to represent the RN16 in the MSG1 sent in the uplink transmission conflict at this time.

[0221] Optionally, the uplink transmission conflict can be that the multiple environmental IoT devices include the same RN16, i.e., the first random number, in each MSG1 sent in different time domain units.

[0222] Optionally, the uplink transmission conflict can be that the multiple environmental IoT devices include the same RN16, i.e., the first random number, in each MSG1 sent in different frequency domain units.

[0223] Step S2103: The node device 102 sends MSG2 to the first environmental IoT device 101.

[0224] In some embodiments, in the scenario of uplink transmission conflict, for example, the node device 102 receives MSG1 sent by multiple environmental IoT devices in the same time domain unit or the same frequency domain unit (the first random number in MSG1 is the same or different), or the node device 102 receives MSG1 containing the same first random number sent by multiple environmental IoT devices in different time domain units or frequency domain units, which is described above in the description of the uplink transmission conflict scenario.

[0225] When there is an uplink conflict, the node device 102 can send MSG2 to multiple environmental IoT devices 101 that have uplink transmission conflicts, for example, MSG2 is sent to Device1 and Device2 respectively.

[0226] In some embodiments, MSG2 can be used to process the uplink transmission conflict, or include information for processing the uplink transmission conflict, so as to improve the probability of successful access of the multiple environmental IoT devices sending MSG1 in conflict.

[0227] In a first possible implementation, MSG2 includes a resource index (resource index or resource ID), which is used to indicate the frequency domain access occasion in which the corresponding environmental IoT device sends MSG1.

[0228] In this embodiment, the uplink transmission conflict can be a scenario where multiple environmental IoT devices send MSG1 in the same time domain unit, such as a time domain conflict, or a conflict where different MSG1 in the same time domain unit contain the same first random number. For different environmental IoT devices, MSG1 can be sent in different frequency domain access occasions in the same time domain unit, and the resource index can be used to indicate the frequency domain access occasion where the environmental IoT device sends MSG1, thereby distinguishing the MSG2 corresponding to different devices.

[0229] In this embodiment, the resource index can also be used as a conflict indication to indicate that the environmental IoT device has an uplink transmission conflict, such as a conflict where the same first random number is generated.

[0230] In this embodiment, if the node device 102 receives multiple MSG1 in different frequency domain access occasions in one time slot or one access retransmission time, and the first random numbers of the multiple MSG1 are the same, i.e., there is an uplink transmission conflict, the node device 102 can carry the conflict resolution information in MSG2.

[0231] In this embodiment, the MSG2 can further include at least one of the following:

[0232] The first random number;

[0233] A second random number allocated to the first environmental IoT device, the second random number being different from the first random number, and the second random number being used for communication with the node device after the MSG2.

[0234] In an example of this embodiment, Device1 and Device2 send MSG1 containing the same first random number in the same time slot, and the node device 102 can send MSG2 for the two devices, and the MSG2 includes the first random number (the same RN16 in MSG1) and the resource index. The multiple environmental IoT devices in conflict, such as Device1 and Device2, can perform the following steps S2103-11 upon receiving the MSG2.

[0235] In step S2103-11, the first environmental IoT device determines whether the MSG2 is the MSG2 corresponding to the first environmental IoT device according to whether the resource index in the MSG2 is the same as the resource index when the first environmental IoT device sends MSG1.

[0236] In this step, the first environmental IoT device can be any one of the multiple environmental IoT devices in conflict, such as Device1 and Device2.

[0237] In this step, each environmental IoT device, such as the first environmental IoT device, can determine whether the received MSG2 is the MSG2 corresponding to the device based on the resource ID in the MSG2. If the first environmental IoT device confirms that the resource ID in the received MSG2 is the same as the resource ID of the MSG1 sent by itself, it can be considered that the conflict resolution is successful.

[0238] In this example, the MSG2 can also include a new random number, i.e., a second random number, allocated by the node device 102 for the device corresponding to the MSG2, such as the first environmental IoT device 101. For example, the node device 102 sends two MSG2s for Device1 and Device2 respectively: one MSG2 includes the first random number, the resource index corresponding to the MSG1 sent by Device1, and the second random number RN16' allocated for Device1, and the other MSG2 includes the first random number, the resource index corresponding to the MSG1 sent by Device2, and the second random number RN16" allocated for Device2, wherein the values of the second random numbers allocated for Device1 and Device2 are different. Thus, the two devices in conflict can communicate based on the newly allocated second random number in the subsequent communication, as described in step S2104.

[0239] In a second possible implementation, the MSG2 includes a device identifier (device id) corresponding to the first environmental IoT device.

[0240] In this implementation, in the 2-step CB access, the node device 102 can learn the device id of each environmental IoT device 101 based on the MSG1 sent by each environmental IoT device 101.

[0241] In this implementation, the MSG2 further includes at least one of the following:

[0242] The first random number;

[0243] The second random number allocated for the first environmental IoT device.

[0244] In an example of the embodiment, in a scenario of uplink transmission conflict, such as node device 102 receiving multiple MSG1s on different frequency domain access occasions in one time slot or one access retransmission time, the first random numbers of the multiple MSG1s being the same, the node device 102 can send MSG2s for solving the conflict to respective environment Internet of Things devices, such as the first environment Internet of Things device 101, corresponding to the multiple MSG1s. Wherein, each environment Internet of Things device, such as the first environment Internet of Things device 101, can determine whether the MSG2 received is the MSG2 corresponding to the device based on the device id in the MSG2.

[0245] In this example, the node device 102 sends MSG2s for different devices respectively, and each MSG2 can include a second random number allocated to the device corresponding to the MSG2, such as one MSG2 including a second random number RN16' allocated to Device 1, and another MSG2 including a second random number RN16" allocated to Device 2, wherein the values of the second random numbers allocated to Device 1 and Device 2 are different. Thus, the two devices in conflict can perform subsequent communication based on the newly allocated second random numbers, such as described in step S2104.

[0246] It is worth noting that in the 2-step CB access of the related Device, MSG2 can not be sent.

[0247] Step S2104: The first environment Internet of Things device 101 communicates with the node device 102 according to the second random number.

[0248] Wherein, in combination with the description of the two embodiments in step S2103, if the node device 102 allocates a new RN16, i.e. a second random number, to the devices in conflict in the MSG2, the environment Internet of Things device 101 in conflict can perform step S2104.

[0249] In some embodiments, after receiving the second random number, the environment Internet of Things device in conflict can keep the second random number and discard the previously randomly generated RN16, i.e. discard the first random number.

[0250] In some embodiments, the first environment Internet of Things device 101 can perform subsequent communication based on the second random number, which can include:

[0251] Sending uplink information to the node device according to the second random number, such as carrying the second random number in the uplink information to identify the corresponding device; or receiving downlink information sent by the node device according to the second random number, such as carrying the second random number in the downlink information to identify the corresponding device.

[0252] The uplink information can be device-to-network side information, i.e., D2R (Device To Reader) information. The downlink information can be R2D information.

[0253] In some embodiments, the names of information and the like are not limited to the names described in the embodiments, and the terms of "signal", "message", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "field", and the like can be replaced with each other.

[0254] In some embodiments, "acquire", "obtain", "get", "receive", "transmit", "bidirectional transmission", "send and / or receive" can be replaced with each other, and can be interpreted as receiving from other subjects, acquiring from a protocol, acquiring from a higher layer, obtaining by self-processing, autonomously implementing, and the like.

[0255] In some embodiments, the terms of "send", "transmit", "report", "issue", "transmit", "bidirectional transmission", "send and / or receive" can be replaced with each other.

[0256] In some embodiments, the terms of "radio", "wireless", "radio access network (RAN)", "access network (AN)", "RAN-based" can be replaced with each other.

[0257] In some embodiments, the terms of "time", "time point", "time", "time position" can be replaced with each other, and the terms of "time length", "time period", "time window", "window", "time" can be replaced with each other.

[0258] In some embodiments, the terms of "certain", "preset", "preset", "set", "indicated", "certain", "arbitrary", "first" can be replaced with each other, and "certain A", "preset A", "preset A", "set A", "indicated A", "certain A", "arbitrary A", "first A" can be interpreted as A specified in advance in a protocol and the like, or can be interpreted as A obtained by setting, configuring, or indicating, or can be interpreted as certain A, certain A, arbitrary A, or first A, but is not limited thereto.

[0259] The method related to the embodiments of the present disclosure can include at least one of steps S2101-S2104.

[0260] In some embodiments, step S2101 can be omitted, and in different embodiments, one or more steps can be replaced.

[0261] In some embodiments, at least one of steps S2103-S2104 can be omitted, and in different embodiments, one or more steps can be replaced. For example, as shown in FIG. 2c, step S2103 can be replaced by step S2303.

[0262] In some embodiments, reference can be made to other optional implementations described before or after the description corresponding to FIG. 2a.

[0263] In the embodiments of the present disclosure, in 2-step CB-based access, when multiple environmental IoT devices exist uplink sending conflicts, the node device 102 can carry information for solving or processing the conflicts through MSG2, thereby solving the conflicts and improving the probability of successful access of the environmental IoT device.

[0264] FIG. 2b is an interaction schematic diagram of a communication method according to an embodiment of the present disclosure. As shown in FIG. 2b, the embodiments of the present disclosure relate to a communication method, and the above method includes:

[0265] Step S2201, the node device 102 sends a trigger instruction to the first environmental IoT device 101.

[0266] In some embodiments, the implementation of step S2201 can refer to the implementation of step S2101 in FIG. 2a, which will not be described here.

[0267] Step S2202, the first environmental IoT device 101 sends MSG1 to the node device 102.

[0268] In some embodiments, in 3-step CB access, RN16 is included in MSG1. In 3-step CB access, no device identifier is included in MSG1, and the description of MSG1 other than this can refer to the description of step S2102 in FIG. 2a.

[0269] For example, Device1 and Device2 that exist uplink sending conflicts respectively send MSG1 to the node device 102, and at least the first random number can be included in the two MSG1s, and no device identifier is included.

[0270] Step S2203, the node device 102 sends MSG2 to the first environmental IoT device 101.

[0271] In some embodiments, the MSG2 sent by the node device 102 can refer to the description of step S2103 in FIG. 2a, for example, can refer to the description in the first possible implementation described above. Or refer to the description of the third possible implementation below.

[0272] In the first possible implementation, the resource index is included in the MSG2, and the resource index is used to indicate the frequency domain access occasion in which the corresponding environmental Internet of Things device sends the MSG1; the MSG2 can further include at least one of the following:

[0273] The first random number;

[0274] The second random number allocated to the environmental Internet of Things device, the second random number being different from the first random number, and the second random number being used for communication with the node device after the MSG2;

[0275] The time-frequency resource used by the first environmental Internet of Things device to send the MSG3.

[0276] In this implementation, the uplink transmission conflict can be the same as the MSG1, i.e., the conflict of the RN16.

[0277] In this implementation, the MSG2 can include a time-frequency resource used by the first environmental Internet of Things device 101 to send the MSG3. For example, there is an uplink transmission conflict between multiple environmental Internet of Things devices, and the node device 102 can send multiple MSG2s corresponding to the multiple environmental Internet of Things devices respectively, and carry information such as the time-frequency resource used by a certain environmental Internet of Things device 101 to send the MSG3 in the MSG2, so that in the subsequent, each device can send the MSG3 on its own corresponding MSG3 time-frequency resource, avoiding the conflict of the MSG3, thereby solving the uplink transmission conflict.

[0278] In the third possible implementation, the MSG2 includes indication information used to indicate that there is an uplink transmission conflict.

[0279] In this implementation, the indication information can be used to indicate that there is a conflict or an uplink transmission conflict, such as indicating to the first environmental Internet of Things device 101 receiving the MSG2 that the MSG1 received by the node device 102 has an uplink transmission conflict. Alternatively, the indication information can indicate other conflict-related information, such as the time domain information or the frequency domain information of the conflicting MSG1.

[0280] In this implementation, the uplink transmission conflict indicated by the indication information can be a conflict caused by the same first random number in different MSG1s, or can be a conflict of different MSG1 time-frequency resources.

[0281] In this implementation, the MSG2 further includes at least one of the following:

[0282] a first random number;

[0283] a resource index, the resource index being used to indicate a frequency domain access occasion in which the corresponding environmental IoT device transmits the MSG1;

[0284] one or more time-frequency resources for transmitting the MSG3.

[0285] In an example of this embodiment, for the uplink transmission collision scenario in which different MSG1s are transmitted in the same time-frequency location, i.e., there is a collision in time domain resources or time-frequency resources, for example, multiple environmental IoT devices transmit different MSG1s in the same time domain unit or in the same time domain unit, the node device 102 can not demodulate the multiple collided MSG1 information, but can determine that a collision occurs, at this time, the indication information and the resource ID can be transmitted through the MSG2, so that the collided environmental IoT devices can retransmit the MSG1. In this example, the first environmental IoT device 101 can further perform step S2204.

[0286] In another example of this embodiment, when the MSG2 includes the first random number and the indication information, it indicates that the uplink transmission collision can be a RN16 collision in the MSG1, i.e., a collision caused by the same first random number, and there is no collision in the time-frequency domain resources. In this example, the first environmental IoT device 101 can further perform step S2205.

[0287] In yet another example of this embodiment, if the MSG2 contains a time-frequency resource for MSG3, for example, the MSG2 sent by the node device 102 to different environmental IoT devices can be the same, such as a MSG2 sent by the node device 102 in reply, which contains a time-frequency resource for MSG3. At this time, the multiple environmental IoT devices whose MSG1s collide will transmit MSG3 on the same time-frequency resource, thus causing the MSG3s transmitted by the multiple environmental IoT devices to also collide, thereby causing the multiple environmental IoT devices to all fail to access. Alternatively, the MSG2 contains a collision indication and a time-frequency resource for MSG3, and the environmental IoT device receiving the MSG2 can learn about the collision and determine whether to perform MSG3 transmission by itself, so as to improve the possibility of solving the collision.

[0288] Step S2204: The first environmental IoT device 101 determines whether to retransmit the MSG1 to the node device 102 according to the indication information.

[0289] In this step, the resource index and the indication information can be contained in the MSG2 received by the first environmental IoT device 101.

[0290] In this step, in the multiple environmental IoT devices that exist time-frequency domain resource conflict in the first sending MSG1, each environmental IoT device such as the first environmental IoT device 101 can resend MSG1 after receiving the above MSG2, or randomly select whether to resend MSG1.

[0291] In step S2205, the first environmental IoT device 101 determines whether to send MSG3.

[0292] In some embodiments, the environmental IoT device 101 can select whether to send MSG3 by itself when receiving MSG2.

[0293] In some embodiments, for the above first implementation, when MSG2 includes a time-frequency resource for the first environmental IoT device 101 to send MSG3, the first environmental IoT device 101 can send MSG3 based on the time-frequency resource for MSG3 of the device. Wherein, the MSG3 can include at least the device identifier of the first environmental IoT device and / or the second random number.

[0294] In this embodiment, different environmental IoT devices can send MSG3, and one environmental IoT device such as the first environmental IoT device 101 can send MSG3 on the time-frequency resource allocated by the node device 102 for MSG3 of the device, to reduce the possibility of conflict in sending MSG3 by different devices. In addition, different environmental IoT devices carry the second random number allocated by the node device 102 for the device and / or the device identifier of the device in the sent MSG3, to further avoid conflict in subsequent communication.

[0295] In some embodiments, for the above third implementation, when MSG2 includes the first random number and the indication information, the step S2205 can include the following step S2205-11:

[0296] In step S2205-11, the first environmental IoT device 101 determines whether to send the third message MSG3 to the node device according to the indication information.

[0297] In this step, each environmental IoT device 101 that exists conflict can randomly select whether to send MSG3, that is, this embodiment is determined by the environmental IoT device 101 whether to send MSG3. For example, for the above Device1 and Device2, Device1 selects to send MSG3 based on its own communication condition or energy; while Device2 selects not to send MSG3 based on its own communication condition or energy, at this time it can be considered that the conflict is solved.

[0298] In some embodiments, for the third implementation described above, if the MSG2 received by the first environmental IoT device 101 includes multiple time-frequency resources for sending MSG3, the step S2205 can include the following steps S2205-21-S2205-22:

[0299] Step S2205-21, the first environmental IoT device 101 selects one time-frequency resource from the multiple time-frequency resources for sending MSG3.

[0300] In this step, the MSG2 sent by the node device 102 to each environmental IoT device can include multiple time-frequency resources for MSG3, and different environmental IoT devices, such as the first environmental IoT device 101, can randomly select one from the multiple time-frequency resources for sending MSG3 after receiving the MSG2. For example, for the Device1 and Device2 described above, Device1 can randomly select one from the multiple time-frequency resources for sending MSG3, and Device2 can randomly select one from the multiple time-frequency resources for sending MSG3, and the time-frequency resources selected by the two devices are different with high probability.

[0301] Step S2205-22, the first environmental IoT device 101 sends MSG3 to the node device 102 according to the selected time-frequency resource.

[0302] In this step, each environmental IoT device 101 can send MSG3 to the node device 102 based on the time-frequency resource selected by itself.

[0303] Wherein, when the time-frequency resources selected by the conflicting environmental IoT devices for sending MSG3 are different, such as the time-frequency resources for sending MSG3 by Device1 and Device2 are different, the two devices are conflict resolved, and the node device 102 can receive MSG3 corresponding to different devices.

[0304] In some embodiments, for the third implementation described above, the MSG3 sent by the first environmental IoT device 101 can include the device identifier and the generated RN16, such as the first random number.

[0305] Step S2206, if MSG3 is received, the node device 102 sends MSG4 to the first environmental IoT device 101.

[0306] In some embodiments, if the node device 102 receives the MSG3 of the first environmental IoT device 101, it can send MSG4 to the first environmental IoT device 101 that sent the MSG3.

[0307] In some embodiments, the MSG4 sent by the node device 102 comprises: the second random number allocated to the first environmental Internet of Things device 101, for example, comprising the device identifier corresponding to the first environmental Internet of Things device 101 and the second random number allocated to the first environmental Internet of Things device 101. In this embodiment, the node device 102 can allocate a new RN16, i.e., a second random number, to the environmental Internet of Things device sending the MSG3, and the second random numbers allocated to different devices are different. The second random number can be associated with the environmental Internet of Things device through the device identifier, so as to avoid conflict in subsequent communication.

[0308] It is worth noting that in the related 3-step CB access of Device, MSG4 can not be sent.

[0309] In step S2207, the first environmental Internet of Things device 101 communicates with the node device 102 according to the second random number.

[0310] In some embodiments, the implementation of step S2207 can refer to the description of step S2104 in FIG. 2a, which will not be repeated here.

[0311] The method related to the embodiments of the present disclosure can include at least one of steps S2201-S2207.

[0312] In some embodiments, step S2201 can be omitted, and in different embodiments, one or more steps can be replaced.

[0313] In some embodiments, at least one of steps S2204 and S2205 can be omitted, or both can be parallel schemes.

[0314] In some embodiments, reference can be made to other optional implementations described before or after the corresponding description of FIG. 2b.

[0315] In the embodiments of the present disclosure, in the 3-step CB-based access, when there is an uplink sending conflict among multiple environmental Internet of Things devices 101, the node device 102 can carry information for solving or processing the conflict through MSG2, and the first environmental Internet of Things device 101 can determine whether to send MSG3 based on the received MSG2, thereby improving the probability of successful access of the environmental Internet of Things device.

[0316] FIG. 2c is an interaction schematic diagram of a communication method according to an embodiment of the present disclosure. As shown in FIG. 2c, the present disclosure relates to a communication method, and the above method comprises:

[0317] In step S2301, the node device 102 sends a trigger instruction to the first environmental Internet of Things device 101.

[0318] In some embodiments, the implementation of step S2301 can refer to the implementation of step S2101 in FIG. 2a, which will not be repeated here.

[0319] In step S2302, the first environmental IoT device 101 sends MSG1 to the node device 102.

[0320] In some embodiments, the implementation of step S2302 can refer to the implementation of step S2102 in FIG. 2a, which will not be repeated here.

[0321] In some embodiments, the implementation of step S2302 can refer to the implementation of step S2202 in FIG. 2b, which will not be repeated here.

[0322] In step S2303, when there is an uplink sending conflict, the node device 102 does not send MSG2 corresponding to the environmental IoT device in the uplink sending conflict.

[0323] In this step, the node device 102 ignores the received MSG1 corresponding to the environmental IoT device in the uplink sending conflict.

[0324] For example, the node device 102 receives MSG1 of Device1 and Device2 in different frequency domain access occasions in one time slot (or in one access retransmission time). The RN16 in the two MSG1s has the same value, i.e., contains the same first random number. At this time, the node device 102 can not reply to the two MSG1s, i.e., does not reply MSG2 for the first random number.

[0325] Optionally, the node device 102 does not reply MSG2, and the related devices such as Device1 and Device2 fail to access.

[0326] In some embodiments, this embodiment can be applied to 2-step or 3-step CB-based access.

[0327] The method related to the embodiments of the present disclosure can include at least one of steps S2301-S2303.

[0328] In some embodiments, step S2101 can be omitted, and in different embodiments, one or more steps can be replaced.

[0329] In some embodiments, step S2302 can be replaced by one or more steps of other embodiments.

[0330] In some embodiments, other optional implementations can be described before or after the corresponding description of FIG. 2c.

[0331] In the 2-step or 3-step CB-based access, when multiple environmental IoT devices exist uplink sending conflicts, the node device 102 can resolve the conflict by not sending the related MSG2, thereby saving the operation of the node device 102.

[0332] FIG. 3a is a flow diagram illustrating a communication method according to an embodiment of the present disclosure. As shown in FIG. 3a, the present embodiment relates to a communication method performed by a first environmental IoT device 101, and the above method comprises:

[0333] In step S3101, a trigger instruction is received.

[0334] In some embodiments, the implementation of step S3101 can refer to the implementation of step S2101 in FIG. 2a, which will not be repeated here.

[0335] In step S3102, MSG1 is sent.

[0336] In some embodiments, the implementation of step S3102 can refer to the implementation of step S2102 in FIG. 2a, which will not be repeated here.

[0337] In some embodiments, the implementation of step S3102 can refer to the implementation of step S2202 in FIG. 2b, which will not be repeated here.

[0338] In step S3103, MSG2 is received.

[0339] In some embodiments, the implementation of step S3103 can refer to the implementation of step S2103 in FIG. 2a, which will not be repeated here.

[0340] In some embodiments, the implementation of step S3103 can refer to the implementation of step S2203 in FIG. 2b, which will not be repeated here.

[0341] In step S3104, it is determined whether to send MSG3.

[0342] In some embodiments, the implementation of step S3104 can refer to the implementation of step S2205 in FIG. 2b, which will not be repeated here.

[0343] In step S3105, MSG4 is received.

[0344] In some embodiments, the implementation of step S3105 can refer to the implementation of step S2206 in FIG. 2b, which will not be repeated here.

[0345] In step S3106, the node device 102 communicates according to the second random number.

[0346] In some embodiments, the implementation of step S3106 can refer to the implementation of step S2104 in FIG. 2a, which will not be repeated here.

[0347] In some embodiments, the implementation of step S3106 can refer to the implementation of step S2207 in FIG. 2b, which will not be repeated here.

[0348] The method related to the embodiments of the present disclosure can include at least one of steps S3101-S3106.

[0349] In some embodiments, the method includes at least one of steps S3101, S3102, S3103, and S3106.

[0350] In some embodiments, other optional implementations can be described before or after the corresponding description of FIG. 3a.

[0351] FIG. 3b is a flow diagram illustrating a communication method according to an embodiment of the present disclosure. As shown in FIG. 3b, the embodiments of the present disclosure relate to a communication method, which is performed by the first environmental Internet of Things device 101, and the above-mentioned method includes:

[0352] Step S3201, sending MSG1.

[0353] In some embodiments, the implementation of step S3201 can refer to the implementation of step S2102 in FIG. 2a, which will not be repeated here.

[0354] In some embodiments, the implementation of step S3201 can refer to the implementation of step S2202 in FIG. 2b, which will not be repeated here.

[0355] Step S3203, receiving MSG2.

[0356] In some embodiments, the implementation of step S3103 can refer to the implementation of step S2103 in FIG. 2a, which will not be repeated here.

[0357] In some embodiments, the implementation of step S3103 can refer to the implementation of step S2203 in FIG. 2b, which will not be repeated here.

[0358] In some embodiments, other optional implementations can be described before or after the corresponding description of FIG. 3b.

[0359] FIG. 3c is a flow diagram illustrating a communication method according to an embodiment of the present disclosure. As shown in FIG. 3c, the embodiments of the present disclosure relate to a communication method, which is performed by the first environmental Internet of Things device 101, and the above-mentioned method includes:

[0360] Step S3301, sending MSG1.

[0361] In some embodiments, the implementation of step S3301 can refer to the implementation of step S2202 in FIG. 2b, which will not be repeated here.

[0362] Step S3302, receiving MSG2.

[0363] In some embodiments, the implementation of step S3302 can refer to the implementation of step S2203 in FIG. 2b, which will not be repeated here.

[0364] Step S3303, determining whether to send MSG3.

[0365] In some embodiments, the implementation of step S3303 can refer to the implementation of step S2205 in FIG. 2b, which will not be repeated here.

[0366] Step S3304, receiving MSG4.

[0367] In some embodiments, the implementation of step S3304 can refer to the implementation of step S2206 in FIG. 2b, which will not be repeated here.

[0368] In some embodiments, other optional implementations can be described before or after the description corresponding to FIG. 3c.

[0369] FIG. 4a is a flow diagram illustrating a communication method according to an embodiment of the present disclosure. As shown in FIG. 4a, the present embodiment relates to a communication method, which is performed by a node device 102, and the above method comprises:

[0370] Step S4101, sending a trigger instruction.

[0371] In some embodiments, the implementation of step S4101 can refer to the implementation of step S2101 in FIG. 2a, which will not be repeated here.

[0372] Step S4102, receiving a plurality of MSG1.

[0373] In some embodiments, the implementation of step S4102 can refer to the implementation of step S2102 in FIG. 2a, which will not be repeated here.

[0374] In some embodiments, the implementation of step S4102 can refer to the implementation of step S2202 in FIG. 2b, which will not be repeated here.

[0375] Step S4103, sending MSG2 in the presence of uplink transmission conflict.

[0376] In some embodiments, the implementation of step S4103 can refer to the implementation of step S2103 in FIG. 2a, which will not be repeated here.

[0377] In some embodiments, the implementation of step S4103 can refer to the implementation of step S2203 in FIG. 2b, which will not be repeated here.

[0378] Step S4104, in the case of receiving MSG 3, sending MSG4.

[0379] In some embodiments, the implementation of step S4104 can refer to the implementation of step S2206 in FIG. 2b, which will not be repeated here.

[0380] Step S4105, communicating with the first environmental Internet of Things device 101 according to the second random number.

[0381] In some embodiments, the implementation of step S4105 can refer to the implementation of step S2104 in FIG. 2a, which will not be repeated here.

[0382] In some embodiments, the implementation of step S4105 can refer to the implementation of step S2206 in FIG. 2b, which will not be repeated here.

[0383] The method related to the embodiments of the present disclosure can include at least one of steps S4101-S4105.

[0384] In some embodiments, other optional implementations can be described before or after the corresponding description of FIG. 4a.

[0385] FIG. 4b is a flow diagram illustrating a communication method according to an embodiment of the present disclosure. As shown in FIG. 4b, the embodiments of the present disclosure relate to a communication method, which is performed by the node device 102, and the above-mentioned method comprises:

[0386] Step S4201, receiving a plurality of MSG1.

[0387] In some embodiments, the implementation of step S4201 can refer to the implementation of step S2102 in FIG. 2a, which will not be repeated here.

[0388] In some embodiments, the implementation of step S4201 can refer to the implementation of step S2202 in FIG. 2b, which will not be repeated here.

[0389] Step S4202, sending MSG2 in the presence of uplink transmission conflict.

[0390] In some embodiments, the implementation of step S4202 can refer to the implementation of step S2103 in FIG. 2a, which will not be repeated here.

[0391] In some embodiments, the implementation of step S4202 can refer to the implementation of step S2203 in FIG. 2b, which will not be repeated here.

[0392] In some embodiments, other optional implementations can be referred to before or after the corresponding description of FIG. 4b.

[0393] FIG. 4c is a flow diagram illustrating a communication method according to an embodiment of the present disclosure. As shown in FIG. 4c, the embodiment of the present disclosure relates to a communication method, which is performed by the node device 102, and the above method comprises:

[0394] Step S4301, receiving multiple MSG1.

[0395] In some embodiments, the implementation of step S4301 can refer to the implementation of step S2202 in FIG. 2b, which will not be repeated here.

[0396] Step S4302, sending MSG2 in the presence of uplink transmission conflict.

[0397] In some embodiments, the implementation of step S4302 can refer to the implementation of step S2203 in FIG. 2b, which will not be repeated here.

[0398] Step S4303, sending MSG4 in the case of receiving MSG 3.

[0399] In some embodiments, the implementation of step S4303 can refer to the implementation of step S2206 in FIG. 2b, which will not be repeated here.

[0400] In some embodiments, other optional implementations can be referred to before or after the corresponding description of FIG. 4c.

[0401] FIG. 4d is a flow diagram illustrating a communication method according to an embodiment of the present disclosure. As shown in FIG. 4d, the embodiment of the present disclosure relates to a communication method, which is performed by the node device 102, and the above method comprises:

[0402] Step S4401, receiving MSG1 sent by multiple environmental Internet of Things devices.

[0403] In some embodiments, the implementation of step S4401 can refer to the implementation of step S2202 in FIG. 2b, which will not be repeated here.

[0404] Step S4402, ignoring the received MSG1 and not sending the corresponding MSG2 in the presence of uplink transmission conflict.

[0405] In some embodiments, reference can be made to the other optional implementations described before or after the description corresponding to Figure 4d.

[0406] In embodiments of the present disclosure, in the process of initial access, multiple tags can be supported to access the network side at the same time in the concurrent communication process scenario, and a conflict resolution method can be provided. The tag corresponds to a device, i.e., the aforementioned Internet of Things device; the reader described below corresponds to the network side, such as the base station in the aforementioned topology 1 (topology 1) or the UE in the topology 2.

[0407] For the convenience of understanding the embodiments of the present disclosure, in combination with Figure 2d, the conflict involved in the embodiments of the present disclosure is, for example, if device1 and device2 use different FDMA-based access occasions in one time slot (or in one access retransmission time), but use the same RN16 to trigger CB access. The embodiments of the present disclosure can handle the conflict of the two devices. Some embodiments are listed as follows:

[0408] Embodiment one:

[0409] Embodiment one can be applied to 2-step or 3-step CB access.

[0410] If the reader receives the same RN16 value of MSG1 in different access occasions in one time slot (or in one access retransmission time), the reader does not reply MSG2 for the RN16.

[0411] Embodiment two:

[0412] Embodiment two can be applied to 2-step or 3-step CB access.

[0413] If the reader receives the same RN16 value of MSG1 in different access occasions in one time slot (or in one access retransmission time), the reader carries the RN16 and the resource index of the access occasion where MSG1 is sent in the reply in MSG2.

[0414] Optionally, a new RN16 is assigned to the device.

[0415] In this embodiment, after receiving the RN16 containing its own, the device further confirms whether it is the resource id of the access occasion when sending MSG1 if it also contains the resource id, if so, it is considered that the conflict resolution is successful, and the new RN16 configured by the network side is saved as the RN16 used in the subsequent communication process, and the RN16 randomly generated by itself before is discarded.

[0416] Embodiment three:

[0417] Embodiment three can be applied to 2-step or 3-step CB access.

[0418] Embodiment 3-1: If the reader receives the same RN16 value of MSG1 on different access occasions in a time slot (or in an access retransmission time), the reader replies a MSG2 containing RN16. In this embodiment, two devices may fail due to MSG3 conflict on the same time-frequency resource (for MSG3).

[0419] Embodiment 3-2: If the reader receives the same RN16 value of MSG1 on different access occasions in a time slot (or in an access retransmission time), the reader replies a MSG2 containing RN16 and a conflict indication. In this embodiment, two devices randomly select whether to send MSG3.

[0420] Embodiment 3-3: If the reader receives the same RN16 value of MSG1 on different access occasions in a time slot (or in an access retransmission time), the reader replies a MSG2 containing RN16 and / or a conflict indication. Wherein, MSG2 further contains multiple resources for MSG3 transmission. Two devices randomly select one of the resources to send MSG3. If the reader receives the MSG3, optionally, the device id and the new RN16 are sent in MSG4.

[0421] Embodiment four:

[0422] Embodiment four can be applied to 2-step CB access.

[0423] If the reader receives the same RN16 value of MSG1 on different access occasions in a time slot (or in an access retransmission time), the reader replies MSG2 containing RN16 and device id for conflict resolution.

[0424] Meanwhile, the MSG2 can further comprise a new RN16 assigned by the reader for identifying the device in the subsequent communication.

[0425] In this embodiment, the device receives the new RN16 and saves it for subsequent communication while discarding the RN16 generated by itself previously.

[0426] The embodiments of the present disclosure further provide a device for implementing any of the above methods. For example, a device is provided, which comprises units or modules for implementing the steps performed by the terminal in any of the above methods. For another example, another device is provided, which comprises units or modules for implementing the steps performed by the equipment (e.g., an access network device, a core network function node, a core network device, etc.) in any of the above methods.

[0427] It should be understood that the division of units or modules in the above device is only a logical function division, and all or part of them can be integrated into one physical entity or physically separated. In addition, the units or modules in the device can be implemented in the form of processor calling software: for example, the device comprises a processor connected with a memory, the memory stores instructions, and the processor calls the instructions stored in the memory to implement any of the above methods or to implement the functions of the units or modules of the device, wherein the processor is a general processor, such as a central processing unit (CPU) or a microprocessor, and the memory is an internal memory or an external memory of the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuit, and the functions of part or all of the units or modules can be implemented by the design of the hardware circuit, which can be understood as one or more processors; for example, in one implementation, the hardware circuit is an application-specific integrated circuit (ASIC), and the functions of part or all of the units or modules are implemented by the design of the logical relationship between the elements in the circuit; for another example, in another implementation, the hardware circuit is a programmable logic device (PLD), and a field programmable gate array (FPGA) is taken as an example, which can include a large number of logic gate circuits, and the connection relationship between the logic gate circuits is configured by a configuration file, so as to implement the functions of part or all of the units or modules. All units or modules of the above device can be implemented in the form of processor calling software, or all units or modules can be implemented in the form of hardware circuit, or part of the units or modules can be implemented in the form of processor calling software, and the remaining part can be implemented in the form of hardware circuit.

[0428] In the embodiments of the present disclosure, the processor is a circuit with signal processing capability. In one implementation, the processor can be a circuit with instruction reading and running capability, such as a central processing unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), a digital signal processor (DSP), or the like. In another implementation, the processor can implement certain functions through a logical relationship of a hardware circuit, and the logical relationship of the hardware circuit is fixed or reconfigurable. For example, the processor is a hardware circuit implemented by an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In the reconfigurable hardware circuit, the processor loads a configuration document to implement the configuration of the hardware circuit. It can be understood that the processor loads instructions to implement the functions of the above part or all units or modules. In addition, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a neural network processing unit (NPU), a tensor processing unit (TPU), a deep learning processing unit (DPU), and the like.

[0429] FIG. 5a is a structural schematic diagram of an environmental IoT device according to an embodiment of the present disclosure. As shown in FIG. 5a, the environmental IoT device 5100 can include at least one of a transceiver module 5101, a processing module 5102, and the like. In some embodiments, the transceiver module 5101 is configured to send a first message MSG1 to a node device; and the transceiver module 5101 is further configured to receive a second message MSG2 sent by the node device, and the MSG2 is used to process uplink sending conflict.

[0430] Optionally, the transceiver module 5101 is configured to perform at least one of the communication steps, such as sending and / or receiving, performed by the environmental IoT device 101 in any of the above methods, which will not be described herein again. Optionally, the processing module 5102 is configured to perform at least one of the other steps performed by the environmental IoT device 101 in any of the above methods, which will not be described herein again.

[0431] FIG. 5b is a structural diagram of a node device according to an embodiment of the present disclosure. As shown in FIG. 5b, the node device 5200 can include at least one of a transceiver module 5201, a processing module 5202, and the like. In some embodiments, the transceiver module 5201 described above is configured to receive the first message MSG1 sent by the environmental IoT device; and the transceiver module 5201 is further configured to send a second message MSG2 to the plurality of environmental IoT devices when there is an uplink sending conflict, where the MSG2 is used to handle the uplink sending conflict.

[0432] Optionally, the transceiver module 5201 described above is configured to perform at least one of the communication steps, such as sending and / or receiving, performed by the node device in any of the methods described above, which will not be repeated here. Optionally, the processing module 5202 described above is configured to perform at least one of the other steps performed by the node device 102 in any of the methods described above, which will not be repeated here.

[0433] In some embodiments, the transceiver module can include a sending module and / or a receiving module, which can be separate or integrated together. Optionally, the transceiver module can be mutually replaced with a transceiver.

[0434] In some embodiments, the processing module can be a module or can include a plurality of sub-modules. Optionally, the plurality of sub-modules perform all or part of the steps required to be performed by the processing module. Optionally, the processing module can be mutually replaced with a processor.

[0435] FIG. 6a is a structural diagram of a communication device 6100 according to an embodiment of the present disclosure. The communication device 6100 can be a network device (such as an access network device, a core network device, and the like), a terminal (such as a user equipment, and the like), a chip, a chip system, or a processor supporting the network device to implement any of the methods described above, or a chip, a chip system, or a processor supporting the terminal to implement any of the methods described above. The communication device 6100 can be used to implement the methods described in the method embodiments described above, and specific implementation can be referred to the descriptions in the method embodiments described above.

[0436] As shown in FIG. 6a, the communication device 6100 includes one or more processors 6101. The processor 6101 can be a general-purpose processor or a special-purpose processor, for example, a baseband processor or a central processing unit. The baseband processor can be configured to process communication protocols and communication data, and the central processing unit can be configured to control the communication device (such as a base station, a baseband chip, a terminal device, a terminal device chip, a DU or a CU, and the like), execute programs, and process data of the programs. Optionally, the communication device 6100 is configured to perform any of the methods described above. Optionally, the one or more processors 6101 are configured to invoke instructions to cause the communication device 6100 to perform any of the methods described above.

[0437] In some embodiments, the communication device 6100 further includes one or more transceivers 6102. When the communication device 6100 includes one or more transceivers 6102, the transceiver 6102 performs at least one of the communication steps of sending and / or receiving in the above-described methods, and the processor 6101 performs at least one of the other steps. In alternative embodiments, the transceiver can include a receiver and / or a transmitter, which can be separate or integrated together. Alternatively, the terms transceiver, transceiving unit, transceiver, transceiving circuit, interface circuit, interface, etc. can be replaced by each other, the terms transmitter, transmitting unit, transmitter, transmitting circuit, etc. can be replaced by each other, and the terms receiver, receiving unit, receiver, receiving circuit, etc. can be replaced by each other.

[0438] In some embodiments, the communication device 6100 further includes one or more memories 6103 for storing data. Alternatively, all or part of the memory 6103 can also be outside the communication device 6100. In alternative embodiments, the communication device 6100 can include one or more interface circuits 6104. Alternatively, the interface circuit 6104 is connected with the memory 6103, and the interface circuit 6104 can be used to receive data from the memory 6103 or other devices, and can be used to send data to the memory 6103 or other devices. For example, the interface circuit 6104 can read the data stored in the memory 6103 and send the data to the processor 6101.

[0439] The communication device 6100 described in the above embodiments can be a network device or a terminal, but the scope of the communication device 6100 described in the present disclosure is not limited thereto, and the structure of the communication device 6100 can not be limited by Figure 6a. The communication device can be a standalone device or can be part of a larger device. For example, the communication device can be: 1) a standalone integrated circuit (IC), or a chip, or a chip system or subsystem; (2) a set of one or more ICs, which can optionally include storage components for storing data, programs; (3) an ASIC, such as a Modem; (4) a module that can be embedded in other devices; (5) a receiver, a terminal device, a smart terminal device, a cellular phone, a wireless device, a handset, a mobile unit, a vehicle-mounted device, a network device, a cloud device, an artificial intelligence device, etc.; (6) others, etc.

[0440] Figure 6b is a structural schematic diagram of a chip 6200 according to an embodiment of the present disclosure. For the case where the communication device 6100 is a chip or a chip system, the structural schematic diagram of the chip 6200 shown in Figure 6b can be referred to, but is not limited thereto.

[0441] The chip 6200 includes one or more processors 6201. The chip 6200 is configured to execute any of the above methods.

[0442] In some embodiments, chip 6200 further includes one or more interface circuits 6202. Optionally, the terms interface circuit, interface, transceiver pin, and the like can be substituted for one another. In some embodiments, chip 6200 further includes one or more memories 6203 for storing data. Optionally, all or part of memory 6203 can be external to chip 6200. Optionally, interface circuit 6202 is connected to memory 6203, and interface circuit 6202 can be used to receive data from memory 6203 or other devices, and interface circuit 6202 can be used to send data to memory 6203 or other devices. For example, interface circuit 6202 can read data stored in memory 6203 and send the data to processor 6201.

[0443] In some embodiments, interface circuit 6202 performs at least one of the communication steps of sending and / or receiving in the above-described methods. The performance of interface circuit 6202 in the communication steps of sending and / or receiving in the above-described methods refers to, for example, the performance of data interaction between processor 6201, chip 6200, memory 6203, or transceiver devices by interface circuit 6202. In some embodiments, processor 6201 performs at least one of the other steps.

[0444] The modules and / or devices described in each of the embodiments of virtual devices, physical devices, chips, and the like can be combined or separated as appropriate. Optionally, part or all of the steps can also be performed by multiple modules and / or devices in cooperation, which is not limited herein.

[0445] The disclosure further proposes a storage medium having instructions stored thereon, which, when executed on communication device 6100, cause communication device 6100 to perform any of the above methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but is not limited to this, and can also be a storage medium readable by other devices. Optionally, the storage medium can be a non-transitory storage medium, but is not limited to this, and can also be a transitory storage medium.

[0446] The disclosure further proposes a program product, which, when executed by communication device 6100, causes communication device 6100 to perform any of the above methods. Optionally, the program product is a computer program product.

[0447] The disclosure further proposes a computer program, which, when executed on a computer, causes the computer to perform any of the above methods. Industrial applicability

[0448] After the first environmental IoT device sends MSG1, the first environmental IoT device can obtain information for processing uplink transmission conflicts according to MSG2 of the node device, so that in the scenario of uplink transmission conflicts, the first environmental IoT device can perform corresponding operations based on MSG2 to reasonably cope with or solve the conflicts.

Claims

1. A communication method, performed by a first environmental IoT device, the method comprising: sending a first message MSG1 to a node device; receiving a second message MSG2 sent by the node device, the MSG2 being used to handle an uplink transmission conflict.

2. The method of claim 1, wherein, The uplink transmission conflict comprises at least one of: The first environmental IoT device and a second environmental IoT device send the MSG1 in a same time domain unit, and the first environmental IoT device and the second environmental IoT device send a same or different first random number in the MSG1. The first environmental IoT device and the second environmental IoT device send the MSG1 in a same frequency domain unit, and the first environmental IoT device and the second environmental IoT device send a same first random number in the MSG1. The first environmental IoT device and the second environmental IoT device send the MSG1 in different time domain units, and the first environmental IoT device and the second environmental IoT device send a same first random number in the MSG1. The first environmental IoT device and the second environmental IoT device send the MSG1 in different frequency domain units, and the first environmental IoT device and the second environmental IoT device send a same first random number in the MSG1.

3. The method of claim 1 or 2, wherein, The MSG2 comprises: a resource index, the resource index being used to indicate a frequency domain access occasion in which a corresponding environmental IoT device sends the MSG1.

4. The method of claim 3, wherein, The method further comprises: determining whether the MSG2 is a MSG2 corresponding to the first environmental IoT device according to whether the resource index in the MSG2 is same as a resource index in which the first environmental IoT device sends the MSG1.

5. The method of claim 3 or 4, wherein, The MSG2 further comprises at least one of: the first random number; a second random number allocated to the first environmental IoT device, the second random number being different from the first random number, and the second random number being used for a communication with the node device after the MSG2; a time-frequency resource used by the first environmental IoT device to send a third message MSG3.

6. The method according to any one of claims 1 to 5, wherein, The method further comprises: sending the MSG3, the MSG3 containing a device identifier corresponding to the first environmental IoT device, and / or the second random number.

7. The method of claim 1 or 2, wherein, The MSG2 comprises: indication information used to indicate that there is an uplink transmission conflict.

8. The method of claim 7, wherein, The MSG2 further comprises at least one of: the first random number; a resource index, the resource index being used to indicate a frequency domain access occasion in which a corresponding environmental IoT device sends the MSG1; a plurality of time-frequency resources used to send the MSG3.

9. The method of claim 8, wherein, When the MSG2 comprises the first random number and the indication information, the method further comprises: determining, according to the indication information, whether to send a third message MSG3 to the node device.

10. The method of claim 8, wherein, When the MSG2 comprises the resource index and the indication information, the method further comprises: determining, according to the indication information, whether to resend a first message MSG1 to the node device.

11. The method of claim 8, wherein, When the MSG2 comprises a plurality of time-frequency resources used to send the MSG3, the method further comprises: selecting one time-frequency resource from the plurality of time-frequency resources for sending MSG3; sending MSG3 to the node device according to the selected time-frequency resource.

12. The method of claim 11, wherein, The method further comprises: receiving a fourth message MSG4 sent by the node device, the MSG4 comprising a second random number allocated to the first environmental IoT device, the second random number being used for communication with the node device after the MSG4.

13. The method of claim 1 or 2, wherein, The MSG2 comprises: a device identifier corresponding to the first environmental IoT device.

14. The method of claim 13, wherein, The MSG2 further comprises at least one of the following: the first random number; a second random number allocated to the first environmental IoT device, the second random number being used for communication with the node device after the MSG2.

15. A communication method performed by a node device, the method comprising: receiving a first message MSG1 sent by a first environmental IoT device; when there is an uplink sending conflict, sending a second message MSG2 to the first environmental IoT device, the MSG2 being used for handling the uplink sending conflict.

16. The method of claim 15, wherein, The uplink sending conflict comprises at least one of the following: the first environmental IoT device and a second environmental IoT device send MSG1 in a same time domain unit, the first random number in the MSG1 sent by the first environmental IoT device and the second environmental IoT device being same or different; the first environmental IoT device and the second environmental IoT device send MSG1 in a same frequency domain unit, the first random number in the MSG1 sent by the first environmental IoT device and the second environmental IoT device being same or different; the first environmental IoT device and the second environmental IoT device send MSG1 in different time domain units, the first random number in the MSG1 sent by the first environmental IoT device and the second environmental IoT device being same; the first environmental IoT device and the second environmental IoT device send MSG1 in different frequency domain units, the first random number in the MSG1 sent by the first environmental IoT device and the second environmental IoT device being same.

17. The method of claim 15 or 16, wherein, The MSG2 comprises: a resource index, the resource index being used for indicating a frequency domain access occasion in which a corresponding environmental IoT device sends MSG1.

18. The method of claim 17, wherein, The MSG2 further comprises at least one of the following: the first random number; a second random number allocated to the first environmental IoT device, the second random number being different from the first random number, the second random number being used for communication with the first environmental IoT device after the MSG2; time-frequency resources for sending MSG3 by the first environmental IoT device. The method further comprises:

19. The method of any one of claims 15 to 18, wherein, receiving MSG3 sent by the first environmental IoT device, the MSG3 comprising a device identifier corresponding to the first environmental IoT device and / or a second random number. The MSG2 comprises:

20. The method of claim 15 or 16, wherein, indication information used for indicating that there is an uplink sending conflict. The MSG2 further comprises at least one of the following:

21. The method of claim 20, wherein, the first random number; a plurality of time-frequency resources for sending MSG3; ​ a resource index, the resource index being used to indicate a frequency domain access occasion in which the corresponding environmental IoT device transmits the MSG1.

22. The method of claim 21, wherein, when the MSG2 includes a plurality of time-frequency resources for transmitting the MSG3, the method further comprises: receiving a MSG3 transmitted by the first environmental IoT device, the MSG3 being transmitted based on one of the plurality of time-frequency resources for transmitting the MSG3.

23. The method of claim 22, wherein, the method further comprises: transmitting a MSG4 to the first environmental IoT device, the MSG4 including a second random number allocated to the first environmental IoT device, the second random number being used for communications with the first environmental IoT device after the MSG4.

24. The method of claim 15 or 16, wherein, the MSG2 includes: a device identity corresponding to the first environmental IoT device.

25. The method of claim 24, wherein, the MSG2 further includes at least one of: the first random number; a second random number allocated to the first environmental IoT device, the second random number being used for communications with the first environmental IoT device after the MSG2.

26. The method of claim 15 or 16, wherein, the method further comprises: when there is an uplink transmission conflict, ignoring a received MSG1 corresponding to an environmental IoT device in the uplink transmission conflict, and not transmitting a MSG2 corresponding to an environmental IoT device in the uplink transmission conflict.

27. An environmental IoT device, comprising: a transceiver module configured to transmit a first message MSG1 to a node device; the transceiver module is further configured to receive a second message MSG2 transmitted by the node device, the MSG2 being used to handle an uplink transmission conflict.

28. A node device, comprising: a transceiver module configured to receive a first message MSG1 transmitted by a first environmental IoT device; the transceiver module is further configured to transmit a second message MSG2 to the first environmental IoT device when there is an uplink transmission conflict, the MSG2 being used to handle the uplink transmission conflict.

29. A communication device, comprising: one or more processors; wherein the communication device is configured to implement the method of any one of claims 1-14, or any one of claims 15-26.

30. A storage medium, the storage medium storing instructions, wherein, when the instructions are run on a communication device, the communication device is caused to perform the method of any one of claims 1-14, or any one of claims 15-26.

31. A program product, wherein, when the program product is executed by a communication device, the communication device is caused to perform the method of any one of claims 1-14, or any one of claims 15-26.

Images