Communication methods, communication device, storage medium and program product

Abstract

Disclosed in the embodiments of the present disclosure are communication methods, a communication device, a storage medium and a program product. A communication method comprises: a first device receiving a first message sent by a second device, the first message being used for determining a first resource; and the first device determining the first resource on the basis of the first message, the first resource being used for sending a first transmission of the first device, wherein the first transmission may be a transmission sent by the first device to the second device, the first device may be an Internet of Things device, and the second device may be a network device or an intermediate node. By implementing the embodiments of the present disclosure, a first resource used for sending a first transmission can be determined by means of a first message sent by a second device, so that the problem of how an Internet of Things (IOT) device determines a start boundary for the first resource in an IOT scenario can be solved, thereby improving the implementation effect of data transmission by IOT devices.

Description

Communication methods, communication equipment, storage media and software products Technical Field

[0001] This disclosure relates to the field of communication technology, and in particular to communication methods, communication devices, storage media, and program products. Background Technology

[0002] Internet of Things (IoT) devices refer to various smart devices connected via the internet. These devices can interact with the external environment by collecting, sending, and receiving data, and are widely used in various fields such as home, industry, and healthcare, driving the intelligent development of society. For example, IoT devices can be applied to automated home scenarios. Summary of the Invention

[0003] This disclosure provides a communication method, communication device, storage medium, and program product that can solve the problem of how IoT devices determine the first resource starting boundary in Internet of Things (IoT) scenarios.

[0004] According to a first aspect of the present disclosure, a communication method is provided, the method being performed by a first device, the method comprising:

[0005] Receive a first message sent by the second device, the first message being used to determine the first resource;

[0006] The first resource is determined based on the first message, and the first resource is used to send a first transmission of the first device; wherein, the first transmission is a transmission sent by the first device to the second device;

[0007] The first device is an Internet of Things (IoT) device, and the second device is a network device or an intermediate node.

[0008] According to a second aspect of the present disclosure, a communication method is provided, the method being performed by a second device, the method comprising:

[0009] A first message is sent to a first device, the first message being used to determine a first resource, the first resource being used to send a first transmission from the first device; wherein, the first transmission is a transmission sent by the first device to a second device;

[0010] The first device is an Internet of Things (IoT) device, and the second device is a network device or an intermediate node.

[0011] According to a third aspect of the present disclosure, a communication device is provided, which is used to perform optional implementations of the first and second aspects described above.

[0012] According to a fourth aspect of the present disclosure, a storage medium is provided that stores instructions which, when executed on a communication device, cause the communication device to perform optional implementations of the first and second aspects described above.

[0013] According to a fifth aspect of the present disclosure, a program product is provided, including at least one of a program and instructions, wherein the program and instructions, when executed by a communication device, implement optional implementations of the first and second aspects described above.

[0014] According to the technical solution disclosed herein, the first resource for sending the first transmission can be determined by the first message sent by the second device. This can solve the problem of how IoT devices determine the starting boundary of the first resource in IoT scenarios, thereby enhancing the data transmission performance of IoT devices. Attached Figure Description

[0015] To more clearly illustrate the technical solutions in the embodiments of this disclosure, the accompanying drawings required for the description of the embodiments are introduced below. The following drawings are only some embodiments of this disclosure and do not impose specific limitations on the protection scope of this disclosure.

[0016] Figure 1 is a schematic diagram of the architecture of a communication system provided in an embodiment of this disclosure;

[0017] Figures 2A-2E are schematic diagrams illustrating the architecture of an A-IoT device communicating with a network device and / or a terminal according to embodiments of the present disclosure.

[0018] Figure 3 is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure;

[0019] Figure 4 is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure;

[0020] Figure 5A is a schematic diagram of the structure of the first device proposed in an embodiment of this disclosure;

[0021] Figure 5B is a schematic diagram of the structure of the second device proposed in an embodiment of this disclosure;

[0022] Figure 6A is a schematic diagram of the structure of the communication device 6100 proposed in an embodiment of this disclosure;

[0023] Figure 6B is a schematic diagram of the structure of the chip 6200 proposed in the embodiment of this disclosure. Detailed Implementation

[0024] This disclosure provides communication methods, communication devices, storage media, and program products.

[0025] In a first aspect, embodiments of this disclosure propose a communication method executed by a first device. The method includes: receiving a first message sent by a second device, the first message being used to determine a first resource; determining the first resource based on the first message, the first resource being used to send a first transmission by the first device; wherein the first transmission is a transmission sent by the first device to the second device; wherein the first device is an Internet of Things (IoT) device, and the second device is a network device or an intermediate node.

[0026] In the above embodiments, the first resource for sending the first transmission can be determined by the first message sent by the second device. This can solve the problem of how IoT devices with lower capabilities can determine the starting boundary of the first resource in IoT scenarios, thereby enhancing the data transmission effect of IoT devices, improving the timeliness of data transmission by IoT devices, and improving communication efficiency.

[0027] In conjunction with some embodiments of the first aspect, in some embodiments, the first transmission includes first data, which is associated with a first service.

[0028] In the above embodiments, the first resource for sending the first transmission can be determined by the first message sent by the second device. The first transmission may include first data, which is associated with a first service. That is, the first data associated with the first service of the first device can be sent to the second device based on the first resource, thereby ensuring that the data associated with the first service of the IoT device is sent to the second device in a timely manner, improving the timeliness of data transmission and thus improving communication efficiency.

[0029] In conjunction with some embodiments of the first aspect, in some embodiments, the first service is a DO-A service initiated by the first device.

[0030] In the above embodiments, the first service can be a DO-A service initiated by the first device. In this way, the first resource for sending the first transmission can be determined by the first message sent by the second device. This makes it easier for the IoT device to send the data associated with the DO-A service initiated by the IoT device through the first resource. This can solve the problem of how the IoT device that initiates the DO-A service determines the first resource in the IoT scenario. It can enhance the implementation effect of IoT devices with lower capabilities actively sending data, improve the timeliness of IoT devices actively sending data, and improve communication efficiency.

[0031] In conjunction with some embodiments of the first aspect, in some embodiments, the first device is an Internet of Things (IoT) device that supports the first service.

[0032] In the above embodiments, only IoT devices that support the first service can determine the first resource based on the first message, which facilitates the use of the first resource to send the data associated with the first service to the second device, further enhancing the effectiveness of the IoT device in actively sending data.

[0033] In conjunction with some embodiments of the first aspect, in some embodiments, the first message includes a first identifier, which is an identifier of a second device. Determining a first resource based on the first message includes: the first identifier included in the first message is the same as the identifier of the second device associated with the first device, and determining the first resource based on the first message.

[0034] In the above embodiments, the system can receive only the first message sent by the pre-configured associated second device, which facilitates the determination of the first resource based on the first message. This can improve security, prevent unauthorized or illegal device access, and reduce the risk of data leakage, tampering, or malicious attacks. It can also reduce unnecessary signal interference and data conflicts, allowing the first device to focus on processing the first message sent by the associated second device, thereby improving the stability and reliability of the system.

[0035] In conjunction with some embodiments of the first aspect, in some embodiments, the first message is a paging message or a newly defined message, wherein the newly defined message is a message from the second device to the first device.

[0036] In the above embodiments, the first message can reuse the paging message, thereby saving signaling overhead. Alternatively, the function of the first message can be implemented by a newly defined message, making it different from the paging message. The message content and format can be defined according to specific needs, accurately implementing specific functions, meeting diverse business needs, realizing remote management and monitoring of devices in IoT scenarios, and enhancing functional customization.

[0037] In conjunction with some embodiments of the first aspect, in some embodiments, the first message includes first indication information, which indicates that the first message is a message sent to a first device that supports the first service.

[0038] In the above embodiments, by setting first indication information in the first message, the first indication information indicates that the first message is sent to a first device supporting the first service. This allows the first device supporting the first service to determine the first resource based on the first message, and then send the data associated with the first service based on the first resource. This solves the problem of how an IoT device that actively initiates the first service determines the resource start boundary in an IoT scenario, thereby enhancing the timeliness of IoT devices actively sending data. Optionally, when the first message is a paging message, i.e., when the paging message is reused, the first indication information can be set in the paging message to indicate that the first message is sent to a first device supporting the first service. This eliminates the need to design a new message and saves the signaling overhead of a new message.

[0039] In conjunction with some embodiments of the first aspect, in some embodiments, when the first message is a newly defined message, the message type of the first message indicates that the first message is a message sent to a first device that supports the first service.

[0040] In the above embodiments, when the first message is a newly defined message, the message type of the message can be used to indicate that the first message is sent to the first device that supports the first service, which can save the signaling overhead of the indication information.

[0041] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes: determining that the first device has a request to send first data, starting to listen for a first message sent by the second device, wherein the first data is associated with a first service; determining that the first data has been sent, and stopping listening for the first message.

[0042] In the above embodiments, when a request to send first data is determined, the system starts listening to the first message sent by the second device. When the first data is determined to be sent, the system stops listening to the first message. This allows the IoT device to wake up and listen to the first message in a timely manner while saving energy. This can further enhance the effect of the IoT device actively sending data, further improve communication efficiency, and effectively manage the energy of the IoT device.

[0043] In conjunction with some embodiments of the first aspect, in some embodiments, the first data is not segmented, and the completion of sending the first data includes: receiving a second message, the second message being a positive acknowledgment message for the first data or the retransmission of the first data; or, if a third message is not received within a first time period, the third message indicates that the first data should be retransmitted.

[0044] In the above embodiments, when the first data does not support segmentation, the first data can be determined to be sent successfully when a positive response message for the first data is received, or when a third message instructing the retransmission of the first data is not received within the first time period. This allows for stopping the monitoring of the first message, thereby ensuring that the first data can be successfully sent to the second device and ensuring data integrity.

[0045] In conjunction with some embodiments of the first aspect, in some embodiments, the first data is segmented into m data segments, and the completion of the first data transmission includes: receiving m fourth messages, the m fourth messages being positive acknowledgment messages corresponding to the m data segments or data segment retransmissions; or, not receiving a fifth message within a first time period, the fifth message indicating that at least some of the m data segments need to be retransmitted.

[0046] In the above embodiments, when the first data supports segmentation, it can be determined that the first data has been sent successfully when a positive response message for all data segments is received, or when a message indicating retransmission of data segments is not received within the first time period. This facilitates stopping the monitoring of the first message, thereby ensuring that the first data can be successfully sent to the second device and ensuring data integrity.

[0047] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes: initiating random access on a first resource, carrying first data or a data segment of the first data in a first transmission, the first data being associated with a first service, and the first transmission being a first message from a first device to a second device initiating random access; or, after the random access process is successful, sending the first data or a data segment of the first data to the second device. Thus, the starting boundary of the resource used to send the first data associated with the first service can be determined, i.e., it can be determined when the first data can be sent, which can enhance the implementation effect of IoT devices actively initiating DO-A services.

[0048] In conjunction with some embodiments of the first aspect, in some embodiments, the first transmission includes second indication information and / or third indication information. The second indication information indicates the reason for initiating random access, and the third indication information indicates the size of the first data or the data segment of the first data. The second indication information is set to a first value, indicating that the first service triggers the random access procedure; or the second indication information is set to a second value, indicating that a non-first service triggers the random access procedure. Alternatively, if the second indication information is not omitted, it indicates that the first service triggers the random access procedure; if the second indication information is omitted, it indicates that a non-first service triggers the random access procedure.

[0049] In the above embodiments, by indicating the reason for the random access (whether it is DO-A, i.e., whether the random access process was triggered by DO-A service) and / or the size of the first data (or the data segment of the first data) in the first transmission initiating random access, the network side can accurately process the data, allocate suitable resources to IoT devices, ensure the continuity of communication, and further improve communication efficiency.

[0050] Secondly, embodiments of this disclosure propose a communication method executed by a second device. The method includes: sending a first message to a first device, the first message being used to determine a first resource, the first resource being used to send a first transmission of the first device; wherein the first transmission is a transmission sent by the first device to the second device; wherein the first device is an Internet of Things (IoT) device, and the second device is a network device or an intermediate node.

[0051] In conjunction with some embodiments of the second aspect, in some embodiments, the first transmission includes first data, which is associated with a first service.

[0052] In conjunction with some embodiments of the second aspect, in some embodiments, the first service is a DO-A service initiated by the first device.

[0053] In conjunction with some embodiments of the second aspect, in some embodiments, the first device is an Internet of Things (IoT) device that supports the first service.

[0054] In conjunction with some embodiments of the second aspect, in some embodiments, sending the first message includes: periodically sending the first message; or sending the first message based on a preset time; or sending the first message when a third message is received from a third device, wherein the third message is used to trigger the second device to send the first message.

[0055] In conjunction with some embodiments of the second aspect, in some embodiments, the first message includes a first identifier, which is an identifier of the second device. The first identifier included in the first message is used by the first device to determine whether to determine the first resource based on the first message.

[0056] In conjunction with some embodiments of the second aspect, in some embodiments, the first message is a paging message or a newly defined message, wherein the newly defined message is a message from the second device to the first device.

[0057] In conjunction with some embodiments of the second aspect, in some embodiments, the first message includes first indication information, which indicates that the first message is a message sent to a first device that supports the first service.

[0058] In conjunction with some embodiments of the second aspect, in some embodiments, when the first message is a newly defined message, the message type of the first message indicates that the first message is a message sent to a first device that supports the first service.

[0059] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes: receiving a first transmission sent by a first device, the first transmission being a first message from the first device to a second device initiating random access, the first transmission carrying first data or a data segment of the first data, the first data being associated with a first service; or, receiving the first data or a data segment of the first data sent by the first device after the random access process is successful.

[0060] In conjunction with some embodiments of the second aspect, in some embodiments, the first transmission includes second indication information and / or third indication information. The second indication information indicates the reason for initiating random access, and the third indication information indicates the size of the first data or the data segment of the first data. The second indication information is set to a first value, indicating that the first service triggers the random access procedure; or the second indication information is set to a second value, indicating that a non-first service triggers the random access procedure. Alternatively, if the second indication information is not omitted, it indicates that the first service triggers the random access procedure; if the second indication information is omitted, it indicates that a non-first service triggers the random access procedure.

[0061] Thirdly, embodiments of this disclosure provide a communication device, including at least one of a transceiver module and a processing module; wherein the first device is used to execute an optional implementation of the first aspect.

[0062] Fourthly, embodiments of this disclosure provide a communication device, including at least one of a transceiver module and a processing module; wherein the second device is used to execute an optional implementation of the second aspect.

[0063] Fifthly, embodiments of this disclosure provide a communication system, including:

[0064] The communication device is configured as an optional implementation of the first aspect mentioned above;

[0065] The communication device is configured to perform an optional implementation of the second aspect described above.

[0066] In a sixth aspect, embodiments of this disclosure provide a communication device, comprising: one or more processors; wherein the processors are configured to invoke instructions to cause the communication device to perform an optional implementation of the first aspect described above.

[0067] In a seventh aspect, embodiments of this disclosure provide a communication device, comprising: one or more processors; wherein the processors are configured to invoke instructions to cause the communication device to perform an optional implementation of the second aspect described above.

[0068] Eighthly, embodiments of this disclosure provide a storage medium storing instructions that, when executed on a communication device, cause the communication device to perform optional implementations of the first and second aspects described above.

[0069] Ninthly, embodiments of this disclosure provide a program product that, when executed by a communication device, causes the communication device to perform the method as described in the optional implementations of the first and second aspects.

[0070] In a tenth aspect, embodiments of this disclosure provide a computer program that, when run on a computer, causes the computer to perform the methods described in alternative implementations of the first and second aspects.

[0071] Eleventhly, embodiments of this disclosure provide a chip or chip system. The chip or chip system includes processing circuitry configured to perform the methods described according to optional implementations of the first and second aspects above.

[0072] It is understood that the aforementioned communication equipment, communication system, storage medium, program product, etc., are all used to execute the methods proposed in the embodiments of this disclosure. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects in the corresponding methods, and will not be repeated here.

[0073] This disclosure provides communication methods, communication devices, storage media, and program products. In some embodiments, terms such as information processing method and communication method may be used interchangeably.

[0074] This disclosure is not exhaustive, but merely illustrative of some embodiments, and is not intended to limit the scope of protection of this disclosure. Unless otherwise specified, each step in a particular embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a particular embodiment can also be implemented as an independent embodiment, and the order of the steps in a particular embodiment can be arbitrarily interchanged. Furthermore, the optional implementation methods in a particular embodiment can be arbitrarily combined; moreover, the embodiments can be arbitrarily combined, for example, some or all steps of different embodiments can be arbitrarily combined, and a particular embodiment can be arbitrarily combined with the optional implementation methods of other embodiments. In all embodiments of this disclosure, unless otherwise specified or logically conflicting, the terminology and / or descriptions between the embodiments are consistent and can be mutually referenced. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.

[0075] The terminology used in the embodiments of this disclosure is for the purpose of describing particular embodiments only and is not intended to limit the scope of this disclosure.

[0076] In this embodiment of the disclosure, unless otherwise stated, elements expressed in the singular form, such as "a," "an," "the," "the," "the," "the," "the," "the," "this," etc., can mean "one and only one," or "one or more," "at least one," etc. For example, when using articles such as "a," "an," "the," etc. in translation, the noun following the article can be understood as either a singular expression or a plural expression.

[0077] In the embodiments disclosed herein, "multiple" refers to two or more.

[0078] In some embodiments, the terms "at least one of A or B, at least one of A and B", "one or more", "a plurality of", "multiple" and the like can be used interchangeably.

[0079] In some embodiments, the notation "at least one of A and B", "A and / or B", "A in one case, B in another", "in response to one case A, in response to another case B", etc., may include the following technical solutions depending on the situation: in some embodiments, A (execute A regardless of whether there is a branch B); in some embodiments, B (execute B regardless of whether there is a branch A); in some embodiments, execution is selected from A and B (A and B are selectively executed); in some embodiments, both A and B are executed. The same applies when there are more branches such as A, B, C, etc.

[0080] In some embodiments, the notation "A or B" may include the following technical solutions, depending on the situation: in some embodiments, A (execute A regardless of whether a branch B exists); in some embodiments, B (execute B regardless of whether a branch A exists); in some embodiments, execution is selected from A and B (A and B are selectively executed). The same applies when there are more branches such as A, B, and C.

[0081] The prefixes "first," "second," etc., used in the embodiments of this disclosure are merely for distinguishing different descriptive objects and do not impose restrictions on the position, order, priority, quantity, or content of the descriptive objects. The description of the descriptive objects is found in the claims or the context of the embodiments, and the use of prefixes should not constitute unnecessary restrictions. For example, if the descriptive object is a "field," the ordinal numbers preceding "field" in "first field" and "second field" do not restrict the position or order of the "fields." "First" and "second" do not restrict whether the "fields" they modify are in the same message, nor do they restrict the order of "first field" and "second field." Similarly, if the descriptive object is a "level," the ordinal numbers preceding "level" in "first level" and "second level" do not restrict the priority between "levels." Furthermore, the number of descriptive objects is not limited by ordinal numbers and can be one or more. For example, in "first device," the number of "devices" can be one or more. Furthermore, the objects modified by different prefixes can be the same or different. For example, if the object being described is "device", then "first device" and "second device" can be the same device or different devices, and their types can be the same or different. Similarly, if the object being described is "information", then "first message" and "second message" can be the same information or different information, and their content can be the same or different.

[0082] In some embodiments, “including A,” “containing A,” “for indicating A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0083] In some embodiments, terms such as "time / frequency" and "time-frequency domain" refer to the time domain and / or frequency domain.

[0084] In some embodiments, terms such as “in response to…”, “in response to determining…”, “in the case of…”, “when…”, “when…”, “if…”, etc. can be used interchangeably. These descriptions all refer to the device making a corresponding action under certain objective circumstances. They do not necessarily limit the time, nor do they require the device to make a judgment action when implementing it, nor do they mean that there must be other limitations.

[0085] In some embodiments, the terms “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,” and “above” can be used interchangeably, as can the terms “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,” and “below”.

[0086] In some embodiments, devices, etc., may be interpreted as physical or virtual, and their names are not limited to those described in the embodiments. Terms such as “device,” “equipment,” “circuit,” “network element,” “network function,” “network device,” “function,” “node,” “unit,” “section,” “system,” “network,” “chip,” “chip system,” “entity,” and “subject” are interchangeable.

[0087] In some embodiments, "network" can be interpreted as devices included in a network (e.g., access network devices, core network devices, etc.).

[0088] In some embodiments, the terms "access network device (AN device)," "radio access network device (RAN device)," "base station (BS)," "radio base station," "fixed station," "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," and "bandwidth part (BWP)" can be used interchangeably.

[0089] In some embodiments, the terms "terminal", "terminal device", "user equipment (UE)", "user terminal", "mobile station (MS)", "mobile terminal (MT)", "subscriber station", "mobile unit", "subscriber unit", "wireless unit", "remote unit", "mobile device", "wireless device", "wireless communication device", "remote device", "mobile subscriber station", "access terminal", "mobile terminal", "wireless terminal", "remote terminal", "handset", "user agent", "mobile client", and "client" can be used interchangeably.

[0090] In some embodiments, access network devices, core network devices, or network devices can be replaced by terminals. For example, embodiments of this disclosure can also be applied to structures where communication between access network devices, core network devices, or network devices and terminals is replaced by communication between multiple terminals (e.g., device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, the structure can also be configured such that the terminal has all or part of the functions of the access network device. Furthermore, terms such as "uplink" and "downlink" can be replaced with terms corresponding to communication between terminals (e.g., "sidelink"). For example, uplink channel, downlink channel, etc., can be replaced with sidelink channel, and uplink link, downlink, etc., can be replaced with sidelink link.

[0091] In some embodiments, the terminal may be replaced by an access network device, a core network device, or a network device. In this case, the access network device, core network device, or network device may also be configured to have all or some of the functions of the terminal.

[0092] In some embodiments, the acquisition of data, information, etc., may comply with the laws and regulations of the country where the location is situated.

[0093] In some embodiments, data, information, etc., may be obtained with the user's consent.

[0094] Furthermore, each element, each row, or each column in the table of this disclosure can be implemented as an independent embodiment, and any combination of any element, any row, or any column can also be implemented as an independent embodiment.

[0095] Figure 1 is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure. This communication system may include, but is not limited to, one first device and one second device. The number and configuration of devices shown in Figure 1 are for illustrative purposes only and do not constitute a limitation on the embodiments of the present disclosure. In practical applications, it may include two or more first devices and two or more second devices. The communication system 100 shown in Figure 1 is exemplified by including one first device 101 and one second device 102.

[0096] In some embodiments, the first device 101 and the second device 102 may both be devices in an Internet of Things (IoT) scenario. In some embodiments, terms such as "Internet of Things (IoT) scenario" and "Ambient Internet of Things (A-IoT) scenario" can be used interchangeably.

[0097] In some embodiments, the first device 101 can be, for example, an Internet of Things (IoT) device, also known as an Ambient Internet of Things (AIoT) or A-IoT device. This IoT device can collect energy without generating its own, such as by collecting energy based on signals emitted by the surrounding environment or nearby devices, and can communicate based on the collected energy. The device may also be battery-free and require no battery replacement. In other words, the environmental IoT device needs to collect energy from radio waves emitted by the surrounding environment or nearby devices to power itself. This environmental IoT device features low memory, low processing power, low power consumption, small data transmission, and mass deployment. Environmental IoT devices are maintenance-free and have a long service life.

[0098] In some embodiments, IoT devices can be categorized into three types: a first type, a second type, and a third type. The first type of IoT device has energy storage but lacks independent signal generation / amplification capabilities. Uplink transmission relies on backscatter transmission. Optionally, the peak power consumption of the first type of IoT device is less than 1 microwatt (µW). The second type of IoT device has energy storage and independent signal amplification capabilities. Uplink transmission is based on internally generated signals. Optionally, the peak power consumption of the second type of IoT device is less than or equal to several hundred µW. The third type of IoT device has energy storage and independent signal amplification capabilities. Uplink transmission relies on backscatter transmission. Optionally, the peak power consumption of the third type of IoT device is less than or equal to several hundred µW. It should be noted that in some embodiments, several hundred µW, such as 100 µW or 200 µW, are examples provided for ease of understanding by those skilled in the art. That is, the peak power consumption is less than or equal to other hundreds-digit µW values, and this disclosure does not impose a specific limitation on this.

[0099] In some embodiments, the second device 102 may be a network device or intermediate node in an IoT scenario. In some embodiments, the second device 102 may perform inventory or paging on the first device 101. In some embodiments, terms such as "inventory," "paging," "statistics," and "counting" may be used interchangeably. In some embodiments, "paging" in this disclosure may refer to finding or inventorying IoT devices in an IoT scenario. "Inventory" in this disclosure may refer to checking the number of existing IoT devices in an IoT scenario using methods such as counting or reconciliation. In some embodiments, terms such as "Internet of Things (IoT) devices" and "Ambient Internet of Things (AIoT) devices" may be used interchangeably.

[0100] In some embodiments, the second device 102 is, for example, a network device in an IoT scenario. In some embodiments, the network device may be an access network device. In some embodiments, the access network device is, for example, a node or device that connects a terminal device to a wireless network. The access network device may include, but is not limited to, at least one of the following in a 5G communication system: evolved Node B (eNB), next-generation eNB (ng-eNB), next-generation Node B (gNB), node B (NB), home node B (HNB), home evolved node B (HeNB), wireless backhaul device, radio network controller (RNC), base station controller (BSC), base transceiver station (BTS), base band unit (BBU), mobile switching center, base station in a 6G communication system, open RAN, cloud RAN, base station in other communication systems, and access node in a Wi-Fi system.

[0101] In some embodiments, the network device may be a core network (CN) device or a server. In some embodiments, the core network device described herein may include, but is not limited to, at least one of the following: AMF (Access and Mobility Management Function); UPF (User Plane Function); SMF (Session Management Function); UDM (Unified Data Management), etc. The AMF can be used to perform registration, connection, reachability, and mobility management. The UPF can be used for packet routing and forwarding, policy enforcement, traffic reporting, and QoS (Quality of Service) processing. The SMF can be used for tunnel maintenance, IP address allocation and management, UP function selection, policy enforcement and QoS control, billing data collection, roaming, etc. The UDM can be used for 3GPP AKA (Authentication and Key Agreement) authentication, user identification, access authorization, registration, mobility, subscription, SMS management, etc.

[0102] In some embodiments, the second device 102 is, for example, an intermediate node in an IoT scenario. In some embodiments, the second device 102 may be a relay, an IAB (Integrated Access and Backhaul), a terminal, or a repeater, etc. In some embodiments, the terminal in this document may be a user-side entity used to receive or transmit signals, such as a mobile phone. It may also be referred to as a terminal, user equipment (UE), mobile station (MS), mobile terminal (MT), etc. The terminal can be at least one of the following: a car with communication capabilities, a smart car, a mobile phone, a wearable device, a tablet computer, a computer with wireless transceiver capabilities, a virtual reality (VR) terminal, an augmented reality (AR) terminal, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical surgery, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, etc. The embodiments of this disclosure do not limit the specific technology or device form used in the terminal.

[0103] In some embodiments, the technical solutions of this disclosure can be applied to the Open RAN architecture. In this case, the interfaces between or within access network devices involved in the embodiments of this disclosure can be transformed into internal interfaces of Open RAN. The processes and information interactions between these internal interfaces can be implemented by software or programs.

[0104] In some embodiments, the access network device may be composed of a central unit (CU) and a distributed unit (DU). The CU may also be called a control unit. The CU-DU structure can separate the protocol layer of the access network device. Some of the protocol layer functions are centrally controlled by the CU, while the remaining part or all of the protocol layer functions are distributed in the DU and centrally controlled by the CU. However, this is not the only possibility.

[0105] It is understood that the communication system described in this disclosure is for the purpose of more clearly illustrating the technical solutions of this disclosure, and does not constitute a limitation on the technical solutions proposed in this disclosure. As those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions proposed in this disclosure are also applicable to similar technical problems.

[0106] The following embodiments of this disclosure can be applied to the communication system 100 shown in FIG1, or to some of the main bodies, but are not limited thereto. The main bodies shown in FIG1 are illustrative. The communication system may include all or some of the main bodies in FIG1, or may include other main bodies outside of FIG1. ​​The number and form of each main body are arbitrary. Each main body may be physical or virtual. The connection relationship between the main bodies is illustrative. The main bodies may not be connected or may be connected. The connection can be in any way, it can be a direct connection or an indirect connection, it can be a wired connection or a wireless connection.

[0107] The embodiments disclosed herein 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), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20, Ultra-Wideband (UWB), Bluetooth (a registered trademark), Public Land Mobile Network (PLMN) networks, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Internet of Things (IoT) systems, Vehicle-to-Everything (V2X) systems, systems utilizing other communication methods, and next-generation systems built upon them, etc. Furthermore, multiple systems can be combined (e.g., a combination of LTE or LTE-A with 5G).

[0108] In communication systems, to save power and reduce device complexity, a new type of Internet of Things (IoT) device has been introduced, such as IoT devices or Ambient Internet of Things (A-IoT) devices. For example, this new type of IoT device needs to collect radio waves emitted by the surrounding environment or nearby devices to obtain energy before it can operate. Therefore, before obtaining energy, this new type of IoT device is usually in a "power-off" state, i.e., offline. For this reason, the communication system needs to support data communication methods with shorter transmission times, lower memory consumption, and more convenient terminal management to complete the data communication process as quickly as possible.

[0109] In some embodiments, this disclosure implements a wireless communication design based on backscattering technology for communication with an ambient energy device (also referred to as an IoT device or an environmental IoT device, i.e., the second device herein). Optionally, the aforementioned IoT device or environmental IoT device (also called an Ambient IoT device, or A-IoT device) can be applied to various different communication architectures in the communication system. Taking an A-IoT device as an example, Figures 2A-2E are schematic diagrams illustrating the architecture of an A-IoT device communicating with a network device and / or a terminal according to embodiments of this disclosure. Optionally, as shown in Figure 2A, the A-IoT device (i.e., the Ambient IoT device in Figure 2A) and the network device (such as a base station (BS)) can directly receive and transmit data or signals.

[0110] Optionally, as shown in Figure 2B, A-IoT devices and network devices (such as base stations (BS)) can indirectly receive and send data or signals through intermediate nodes. These intermediate nodes can be, for example, relays, integrated access backhaul (IAB) devices, terminals, or repeaters.

[0111] Optionally, as shown in Figure 2C, A-IoT devices and network devices (such as base stations (BS)) can directly transmit uplink data, and A-IoT devices and network devices (such as base stations (BS)) can indirectly transmit downlink data through intermediate nodes, such as relays, IAB devices, terminals, and repeaters.

[0112] Optionally, as shown in Figure 2D, downlink data can be transmitted directly between A-IoT devices and network devices (such as base stations (BS)), while uplink data can be transmitted indirectly between A-IoT devices and network devices (such as base stations (BS)) through intermediate nodes.

[0113] Optionally, as shown in Figure 2E, the A-IoT device and the terminal (or user equipment (UE)) can directly receive and send data. The terminal can be responsible for collecting data from the A-IoT device and forwarding the collected data to the network device.

[0114] In some embodiments of a passive IoT system, the data transmission type (also called traffic type) of the IoT device can include, but is not limited to, the following three types: DO-DTT, DT, and DO-A (or DO-DOA). DO-DTT (Device-originated–device-terminated triggered) can be understood as data triggered by a network device or intermediate node (such as a terminal), such as data returned during inventory processing. For example, this returned data can be the identifier of the first device 101, such as an EPC (Electronic Product Code) or a temporary identifier. DT (Device-terminated) can be understood as, for example, an access command. For instance, the first device 101 returns data after executing an access command sent by a network device or intermediate node (such as a terminal). For example, this data can be an ACK (acknowledgment) feedback. DO-A (Device-originated–autonomous) can be understood as data actively sent by the first device 101. For example, this data can be an active reporting triggered by a sensor function.

[0115] In some embodiments, the first message that triggers initial access for an IoT device can be called a paging message or an "initial trigger message". A paging message can page one, a group, or all IoT devices. If a paging message pages one IoT device, it can trigger non-contention-based random access. The paged IoT device responds to the paging message on non-contention-based resources, for example, by sending an ACK message, which may contain the IoT device's identifier, such as an EPC or temporary identifier. If a paging message triggers a group or all IoT devices, it can trigger contention-based random access. The paged group or all IoT devices can generate a random number based on a parameter similar to Q, and then continue to receive query messages (such as query, queryadjust, or queryrepete) until the random number decreases to 0, at which point they initiate random access, for example, by sending the generated random number.

[0116] In some embodiments, an IoT device can proactively initiate a first service, which can be a DO-A service. DO-A service data can be data proactively sent by the IoT device. For example, taking an IoT device as a sensor, the DO-A service data can be data proactively reported by the sensor function. For instance, IoT devices can be applied to autonomous driving scenarios, such as speed detection and vehicle fault detection. An IoT device with multiple integrated sensors mounted on vehicle components can proactively initiate communication when the measured threshold (such as pressure, resistance, temperature, etc.) is exceeded. Alternatively, when the vehicle's speed exceeds a certain threshold, the IoT device can also proactively initiate an alarm, i.e., the IoT device initiates a DO-A service.

[0117] For example, taking the application of IoT devices in autonomous driving scenarios, IoT devices with multiple integrated sensors mounted on vehicle components can initiate communication when the measured threshold (such as pressure, resistance, temperature, etc.) is exceeded. Alternatively, when the vehicle's speed exceeds a certain threshold, the IoT device can also initiate an alarm, i.e., the IoT device initiates a DO-A service.

[0118] However, due to the limited capabilities of IoT devices, how to determine the starting boundaries of resources has become an urgent problem to be solved.

[0119] Based on this, the embodiments of this disclosure provide a communication method, communication device, storage medium, and program product, which can determine the first resource for sending the first transmission through the first message sent by the second device. This can solve the problem of how IoT devices determine the starting boundary of the first resource in the Internet of Things (IoT) scenario, thereby enhancing the data transmission effect of IoT devices.

[0120] Figure 3 is an interactive schematic diagram of the communication method according to an embodiment of the present disclosure. It should be noted that the communication method of this embodiment can be applied to a communication device. In some possible embodiments, the device can be configured in a communication or chip to enable the electronic device or chip to perform communication functions. For example, the electronic device can be a communication device, such as the first or second device in Figure 1. Additionally, in some possible embodiments, the communication device can also be software within an electronic device, such as communication software.

[0121] As shown in Figure 3, the embodiments of this disclosure relate to communication methods, which may include, but are not limited to, the following steps.

[0122] In step S3101, the second device 102 sends a first message. In some embodiments, terms such as "first message," "first signal," "first signaling," and "first information" can be used interchangeably.

[0123] In some embodiments, the first message can be sent by the second device 102. For example, the second device 102 sends the first message to the first device 101, and correspondingly, the first device 101 receives the first message sent by the second device 102. In some embodiments, the first device 101 can be an IoT device, such as an A-IoT device or other IoT devices. In some embodiments, the second device 102 can be a network device or an intermediate node, such as an access network device or a terminal. In some embodiments, the first device 101 can be an IoT device supporting a first service. In some embodiments, the first service can be a DO-A service initiated by the first device 101. For example, the DO-A (Device-originated-autonomous) service can be understood as the first device 101 actively initiating a communication request (or actively initiating an uplink session), rather than being triggered by the network or other devices (such as the second device 102). For example, when the first device 101 is an IoT device that does not support the first service (or the first device 101 is not an IoT device that supports the first service), the first device 101 can ignore the first message.

[0124] In some embodiments, the first message can be used to determine a first resource. In some embodiments, the first resource can be used to send a first transmission from the first device 101, wherein the first transmission can be a transmission from the first device 101 to the second device 102. For example, the second device 102 sends the first message to the first device 101, and the first device 101 receives the first message and can determine the first resource based on the first message. For example, the starting boundary of the first resource can be determined based on the first message. In some embodiments, the first transmission may include first data, which may be associated with the first service mentioned above. For example, the first transmission may include first data associated with a DO-A service initiated by the first device 101 (i.e., service data of a DO-A service initiated by the first device 101). Alternatively, in some embodiments, the first transmission may not carry the first data mentioned above. Optionally, the first data may be sent after the first transmission, that is, the first data is sent after the first transmission is sent on the first resource.

[0125] In some embodiments, the first message can be an R2D message, that is, the first message can refer to a message sent by a network device or intermediate node to an IoT device. In some embodiments, the first message can be sent periodically. For example, the second device 102 sends the first message periodically, wherein the period can be preset, or the period can be indicated by other devices (such as core network devices or servers), or the period can be obtained by the second device 102 based on its implementation.

[0126] In one possible implementation, the third device sends indication information to the second device 102, which may indicate the period for sending the first message. That is, the third device can instruct the second device to send the first message at a period of 600 seconds, meaning the second device can send the first message once every 600 seconds. The third device can be a core network device, but is not limited to this; for example, it could be a server.

[0127] In one possible implementation, the second device 102 can determine the period for sending the first message based on its implementation. For example, the second device 102 can determine the period for sending the first message to be 600 seconds based on the current state or service, meaning that the second device can send the first message once every 600 seconds.

[0128] In some embodiments, the second device 102 may send the first message non-periodically. For example, the second device 102 may send the first message based on a preset time. The preset time may be one or more times; for example, the preset time may be a time period, but is not limited thereto. For instance, the preset time may be associated with the first service, that is, the preset time may be the time when the first service is triggered, i.e., the time when the first service occurs. For example, the first device 101 may be applied to an autonomous driving scenario, and the preset time may be the time when the user uses the autonomous driving scenario. It is understood that the description of the preset time is merely an example given to facilitate understanding by those skilled in the art and should not be construed as a limitation of this disclosure.

[0129] In some embodiments, the second device 102 sends the first message upon receiving a third message from the third device. The third message can be used to trigger the second device 102 to send the first message. That is, the third device can trigger the second device to send the first message. The third device can be a core network device, but is not limited to this; for example, it can be a server.

[0130] In some embodiments, the first message may be a paging message, wherein the paging message may refer to the first message that triggers the first device 101 to perform initial access. In some embodiments, the first message may include first indication information, which may indicate that the first message is sent to the first device 101 that supports the first service. That is, the first message may include first indication information, which may indicate that the first message is for the first device 101, that the first device 101 is a device that supports the first service, and that the first service may be a DO-A service initiated by the first device 101.

[0131] It should be noted that, since this paging message has paging functionality—it can page one, a group, or all IoT devices—if the first message is a paging message and does not carry a device identifier, and is not intended to page all IoT devices that receive the first message, then the first indication information can indicate that the first message is sent to the first device 101 that supports the first service. The number of first devices 101 that support the first service can be one or more. In other words, if the first message is a paging message, and it does not carry a device identifier, and is not intended to page all IoT devices that receive the first message, including the first indication information in the first message indicates that the first message is sent to all first devices 101 that support the first service.

[0132] In some embodiments, the aforementioned first message can be a newly defined message, which can be an R2D message, that is, a message from the second device 102 to the first device 101. In one possible implementation, the first message may include first indication information, which indicates that the first message is sent to the first device 101 that supports the first service. In other words, when the first message is a newly defined message, it may include first indication information, which indicates that the first message is for the first device 101, that the first device 101 is a device that supports the first service, and that the first service may be a DO-A service initiated by the first device 101. In some embodiments, the aforementioned first indication information may be 1-bit indication information, or it may be multi-bit indication information. This disclosure does not limit the specific implementation of the first indication information, nor will it elaborate further.

[0133] In another possible implementation, when the first message is a newly defined message, the message type of the first message can indicate that the first message is sent to the first device 101 that supports the first service. That is, when the first message is a newly defined message, it can be determined by the message type of the first message that the first message is sent to the first device 101, that the first device 101 is a device that supports the first service, and that the first service can be a DO-A service initiated by the first device 101. In this case, the first message may not include the aforementioned first indication information.

[0134] In some embodiments, the first message may include a first identifier, which may be an identifier (reader ID) of the second device 102, enabling the first device receiving the first message to determine whether the second device sending the first message is associated with the first device based on the first identifier contained in the first message. For example, the identifier of the second device 102 may be a device identifier of the second device 102 (a reader device identifier assigned by the core network device or a reader device identifier assigned by a third party, etc.), or it may be a temporary identifier, etc.

[0135] In some embodiments, the first message may further include an identifier of the first device, wherein the identifier of the first device 101 may be, for example, an EPC, an identifier assigned by the core network, or an identifier assigned by a third party. Upon receiving the first message, the first device 101 can identify whether the allocated first resource is intended for the first device 101 to perform the first transmission based on the identifier of the first device carried in the first message, thereby avoiding conflicts with the first resource transmissions of other first devices.

[0136] For example, a first device 101 is associated with a second device A (where the association between the first device 101 and the second device A can mean that there is an association relationship between the first device 101 and the second device A). The second device A and the second device B each send a first message. The first message sent by the second device A contains a first identifier, which is the identifier of the second device A. The first message sent by the second device B contains a first identifier, which is the identifier of the second device B. Since the second device associated with the first device 101 is the second device A, when the first device 101 receives the first message sent by the second device A, it can determine, based on the first identifier contained in the first message, that the second device A that sent the first message is the second device associated with the first device 101, and the first device 101 can determine a first resource based on the first message. If the first device 101 determines, based on the first identifier contained in the first message, that the second device B that sent the first message is not the second device associated with the first device 101, then the first device 101 can ignore the first message, that is, it does not perform the step of "determining the first resource based on the first message".

[0137] In some embodiments, the first identifier may be a server identifier (server ID). This allows the first device receiving the first message to determine, based on the first identifier contained in the first message, whether the server associated with the second device sending the first message is the same server associated with the first device 101.

[0138] For example, first device 101 is associated with second device A, and second device A is associated with server A (i.e., first device 101 is associated with server A). First device 101 is not associated with second device B, and second device B is associated with server B (i.e., first device 101 is not associated with server B). Second device A and second device B respectively send a first message. The first identifier contained in the first message sent by second device A is the identifier of server A, and the first identifier contained in the first message sent by second device B is the identifier of server B. Since the second device associated with first device 101 is second device A, and second device A is associated with server A, when first device 101 receives the first message sent by second device A, it can determine, based on the first identifier contained in the first message, that the server A associated with the second device A that sent the first message is the server associated with first device 101. First device 101 can determine the first resource based on the first message. If the first device 101 determines, based on the first identifier contained in the first message, that the server B associated with the second device B that sent the first message is not a server associated with the first device 101, then the first device 101 can ignore the first message, that is, not perform the step of "determining the first resource based on the first message".

[0139] In step S3102, the first device 101 determines that it has a request to send first data and starts listening for the first message.

[0140] In some embodiments, if the first device 101 determines that it has a request to send first data, then the first device 101 may begin listening for a first message sent by the second device 102. This first data may be associated with a first service; for example, the first data may be the service data of that first service. For instance, if the first service is a DO-A service initiated by the first device 101, the first data may be the service data of that DO-A service. In some embodiments, the terms "listen," "receive," and "monitor" can be used interchangeably.

[0141] For example, if the first message is sent periodically by the second device 102, for instance, if the second device 102 sends the first message every 10 minutes, and assuming that the second device 102 has already sent the first message at 12:10, the second device 102 will send the next first message at 12:20. If the first device 101 has a request to send the first data at 12:15, then the first device 101 can start listening for the first message at this time, and the first device 101 will hear the first message sent by the second device 102 at 12:20.

[0142] For example, if the first message can be sent by the second device based on a preset time, such as 12:00 to 13:00, the second device 102 will send the first message at the preset time. If the first device 101 has a request to send the first data at 12:15, then the first device 101 can start listening to the first message at this time, and the first device 101 can listen to the first message sent by the second device 102 at this time.

[0143] It should be noted that in some embodiments, step S3102 can be performed after step S3101, or in some embodiments, step S3102 can be performed before step S3101, or in some embodiments, step S3102 and step S3101 can be performed simultaneously.

[0144] In step S3103, the first device 101 receives a first message sent by the second device 102 and determines the first resource based on the first message.

[0145] For example, if the first device 101 determines that there is a request to send first data, the first device 101 can start listening for a first message. Upon receiving (or listening to) a first message sent by the second device 102, the first device 101 can determine a first resource based on the first message. In some embodiments, the first resource can be used to send a first transmission by the first device 101; wherein, the first transmission can be a transmission sent by the first device 101 to the second device 102. For the relevant descriptions of "first resource," "first transmission," and "first data," please refer to the description of the example below in step S3101 above, which will not be repeated here.

[0146] It should be noted that in some embodiments, multiple second devices may send the first message. Among these multiple second devices, there may be a second device 102 associated with the first device 101, or there may be no second device 102 associated with the first device 101. The first device 101 may only receive the first message sent by the second device 102 associated with it. For example, the first message may carry the identifier of the second device 102, which allows the first device 101 to determine that the first message was sent by the second device 102. In some embodiments, the first message may include a first identifier, which may be the identifier of the second device 102. In some embodiments, the first identifier included in the first message is the same as the identifier of the second device 102 associated with the first device 101, then the first device 101 can determine the first resource based on the first message.

[0147] For example, a first device 101 is associated with a second device A. Second device A and second device B each send a first message. The first message sent by second device A contains a first identifier, which is the identifier of second device A. The first message sent by second device B contains a first identifier, which is the identifier of second device B. Since the second device associated with first device 101 is second device A, when first device 101 receives the first message sent by second device A, it can determine, based on the first identifier contained in the first message, that the second device A that sent the first message is the second device associated with first device 101. First device 101 can then determine a first resource based on this first message. If first device 101 determines, based on the first identifier contained in the first message, that the second device B that sent the first message is not the second device associated with first device 101, then first device 101 can ignore the first message, i.e., it does not perform the step of "determining the first resource based on the first message".

[0148] It should be noted that in some embodiments, the aforementioned first data or its data segments may be sent to the second device 102 during the random access procedure, or the aforementioned first data or its data segments may be sent to the second device 102 after the random access procedure is successful. Specifically, if the aforementioned first data or its data segments may be sent to the second device 102 during the random access procedure, step S3104 may be executed instead of step S3105; if the aforementioned first data or its data segments may be sent to the second device 102 after the random access procedure is successful, step S3105 may be executed instead of step S3104. That is, steps S3104 and S3105 cannot belong to the same embodiment.

[0149] In step S3104, the first device 101 initiates random access on the first resource, and the first transmission carries the first data or a data segment of the first data.

[0150] In some embodiments, after determining a first resource based on the first message, the first device 101 may initiate random access on the first resource. In some embodiments, the random access may be a 3-step contention-based random access (3-step CBRA), or it may be other types of random access, such as a 2-step contention-based random access (2-step CBRA), but is not limited thereto. In some embodiments, the first transmission is the first message from the first device to the second device initiating random access. For example, if the random access is a 3-step CBRA, the first transmission is message 1 in the 3-step CBRA; or, if the random access is a 2-step CBRA, the first transmission is message 1 in the 2-step CBRA. The first transmission carries the first data or a data segment of the first data.

[0151] For example, when a first device 101 initiates random access on the first resource, it may carry the first data or a data segment of the first data in the first transmission initiating the random access. Correspondingly, a second device 102 may receive the first transmission sent by the first device 101, in which the first transmission carries the first data or a data segment of the first data. That is, the first data or a data segment of the first data may be sent to the second device 102 during the random access initiation process.

[0152] In some embodiments, if the first data is not segmented (e.g., including cases where the first data does not support segmentation, or where the first data supports segmentation but is not segmented), then the first device 101 initiates random access on the first resource and can carry the first data in the first transmission initiating the random access. In some embodiments, if the first data supports segmentation, for example, if the first data is segmented into m data segments, then the first device 101 initiates random access on the first resource and can carry the data segments of the first data in the first transmission initiating the random access. Here, m can be an integer greater than or equal to 2. For a description of the "first data," please refer to the example below in step S3101 above; it will not be repeated here.

[0153] For example, if the random access can be a 3-step CBRA, the first device 101 can carry the first data or a data segment of the first data in message 1 of the 3-step CBRA. As another example, if the random access can be a 2-step CBRA, the first device 101 can carry the first data or a data segment of the first data in message 1 of the 2-step CBRA.

[0154] In some embodiments, the first transmission initiating random access may include second indication information and / or third indication information. For example, the first transmission may include the second indication information; or, the first transmission may include the third indication information; or, the first transmission may include both the second and third indication information. The second indication information may indicate the reason for initiating random access, and the third indication information may indicate the size of the first data or a data segment of the first data. Carrying the third indication information in the first transmission facilitates the network side's understanding of the size of the first data or a data segment of the first data, thereby enabling the allocation of appropriate resources to the first device 101 for transmitting the first data or a data segment of the first data.

[0155] For example, if the first data is not segmented and is carried in the first transmission, the third indication information may not be included in the first transmission.

[0156] For example, when the first data is segmented into m data segments, and the first data carries the data segments of the first data, the first transmission may include third indication information. The third indication information may indicate the size of the next data segment, or the third indication information may indicate whether there is another data segment. For example, the third indication information may be a 1-bit indication information used to indicate whether there is another data segment. For example, if the third indication information is set to a first value, it may indicate that there is another data segment. If the third indication information is set to a second value, it may indicate that there is no next data segment. That is, all data segments of the first data have been sent.

[0157] For example, if the first transmission does not carry the first data or the data segment carrying the first data, that is, the first data is not sent in the first transmission, then the first transmission may include third indication information, which may indicate the size of the first data to be sent.

[0158] In some embodiments, the number of bits occupied by the second indication information can be 1 bit, but is not limited thereto. In some embodiments, if the value of the second indication information is a first value, it can indicate that the first service triggers a random access procedure; if the value of the second indication information is a second value, it can indicate that a non-first service triggers a random access procedure. For example, the aforementioned non-first service triggering a random access procedure can mean that the triggering reason is not the first service. That is, the reason for initiating random access can be indicated by the first value and the second value. For example, if the value of the second indication information is a first value, it can indicate that the first service triggers a random access procedure, that is, the reason for initiating random access is because the first service triggered the random access procedure; if the value of the second indication information is a second value, it can indicate that a non-first service triggers a random access procedure, that is, the reason for initiating random access is because a non-first service triggered the random access procedure, or it can indicate that the reason for initiating random access is not because the first service triggered the random access procedure. For example, the non-first service can mean something other than the first service, such as a second service, like a DO-DTT service or a DT service. For a description of the "first business", please refer to the example below in step S3101 above, which will not be repeated here.

[0159] In some embodiments, if the second indication information is not omitted (i.e., if the second indication information appears), it can indicate that the first service triggers a random access procedure. If the second indication information is omitted, it can indicate that a non-first service triggers a random access procedure. For example, the aforementioned non-first service triggering a random access procedure can mean that the triggering reason is not the first service. For example, the reason for initiating random access can be indicated by whether the second indication information is omitted. For instance, if the first device 101 carries the second indication information in the first transmission initiating random access, it can indicate that the first service triggers a random access procedure, that is, it can indicate that the reason for initiating random access is because the first service triggered the random access procedure. If the first device 101 omits the second indication information in the first transmission initiating random access, it can indicate that a non-first service triggers a random access procedure, that is, it can indicate that the reason for initiating random access is because a non-first service triggered the random access procedure, or it can indicate that the reason for initiating random access is not because the first service triggered the random access procedure. For example, the non-first service can mean something other than the first service, such as a second service, like a DO-DTT service or a DT service. For a description of the "first business", please refer to the example below in step S3101 above, which will not be repeated here.

[0160] It is worth noting that in some embodiments, when the first data or data segments of the first data can be sent to the second device 102 during the random access procedure, step S3104 can be executed instead of step S3105. That is, step S3105 is optional and can be omitted or replaced in different embodiments.

[0161] In step S3105, after the first device 101 successfully completes the random access process, it sends the first data or a data segment of the first data to the second device 102.

[0162] In some embodiments, a first device 101 initiates random access on the first resource. After the random access process is successful, the first device 101 may send the first data or a data segment of the first data to a second device 102. Correspondingly, the second device 102 may receive the first data or the data segment of the first data sent by the first device 101 after the successful random access process. In some embodiments, the size of the first data may be indicated by the first device 101 during the random access process on the first resource. That is, the first device 101 indicates the size of the first data during the random access process on the first resource. For example, the first device 101 may carry third indication information in the message during the random access process on the first resource. Optionally, the third indication information may be carried in message 1 during the random access process. Since the first data or the data segment of the first data is sent after the successful random access process, that is, the first data is not sent during the random access process, the third indication information may be included in message 1. The third indication information may indicate the size of the first data to be sent.

[0163] In some embodiments, if the first data is not segmented (e.g., including cases where the first data does not support segmentation, or where the first data supports segmentation but is not segmented), then the first device 101 can send the first data to the second device 102 after the random access procedure is successful. In some embodiments, if the first data supports segmentation, for example, if the first data is segmented into m data segments, then the first device 101 can send the data segments of the first data to the second device 102 after the random access procedure is successful. Here, m can be an integer greater than or equal to 2. For a description of the "first data," please refer to the example description below in step S3101 above; it will not be repeated here.

[0164] It is worth noting that in some embodiments, if the first data or the data segment of the first data can be sent to the second device 102 after the random access process is successful, step S3105 can be executed instead of step S3104. That is, step S3104 is optional and can be omitted or replaced in different embodiments.

[0165] In step S3106, the first device 101 confirms that the first data transmission is complete and stops listening to the first message.

[0166] In some embodiments, the first device 101 may stop listening to the first message once it determines that the first data has been sent.

[0167] In some embodiments, if the first data is not segmented, the completion of first data transmission may mean that the first data was successfully transmitted, and the first device 101 determining that the first data transmission is complete may mean that the first device 101 determines that the first data was successfully transmitted. In one possible implementation, when the first data is not segmented, the first device 101 can determine that the first data transmission is complete by receiving a second message, which may be a positive acknowledgment (e.g., ACK) message for the first data or a retransmission of the first data. For example, if the first device 101 receives the second message sent by the second device 102 or a third device (e.g., a core network device), and the second message is an ACK message for the first data or a retransmission of the first data, then the first device 101 can determine that the first data transmission is complete. That is, the first device 101 can determine that the first data transmission is complete by the positive acknowledgment of the first data or the first data retransmission by the second device 102 or the third device (e.g., a core network device).

[0168] In another possible implementation, if the first data is not segmented, the first device 101 can determine that the first data transmission is complete by: not receiving a third message within a first time period, the third message indicating that the first data should be retransmitted. For example, if the first device 101 does not receive a third message indicating that the first data should be retransmitted within the first time period, the first device 101 can determine that the first data transmission is complete. The first time period can be predefined; for example, it can be the minimum time interval between a D2R transmission and an associated R2D transmission, or it can be the maximum time interval between a D2R transmission and an associated R2D transmission. The D2R transmission can refer to the transmission from the first device 101 to the second device 102 (i.e., the transmission from the first device 101 to the second device 102), and the R2D transmission can refer to the transmission from the second device 102 to the first device 101 (i.e., the transmission from the second device 102 to the first device 101).

[0169] In some embodiments, if the first data supports segmentation, for example, if the first data is segmented into m data segments, then the completion of the first data transmission may mean that all data segments of the first data have been transmitted successfully. Optionally, the completion of the transmission of all data segments of the first data may mean that all data segments of the first data have been successfully transmitted. In one possible implementation, when the first data is segmented into m data segments, the first device 101 determines that the first data transmission is complete by receiving a positive acknowledgment message corresponding to each data segment or each data segment retransmission. For example, if the first device 101 receives a fourth message sent by the second device 102 or a third device (such as a core network device), and this fourth message can be, for example, an ACK message for a data segment or a data segment retransmission, then the first device 101 can determine that the first data transmission is complete. For example, if the first data is segmented into three data segments, and the first device 101 receives an ACK message from the second device 102 or the third device (such as a core network device) for each data segment or for retransmission of a data segment, then the first device 101 can determine that the first data has been sent.

[0170] In another possible implementation, when the first data is segmented, the first device 101 determines that the first data transmission is complete by: not receiving a fifth message within a first time period, the fifth message indicating that at least some of the m data segments need to be retransmitted. For example, if the first device 101 does not receive a fifth message indicating that at least some of the m data segments need to be retransmitted within the first time period, the first device 101 can determine that the first data transmission is complete. For instance, if the first data is segmented into 3 data segments, and the first device 101 does not receive a fifth message indicating that the data segments need to be retransmitted, then the first device 101 can determine that the first data transmission is complete. The description of "first time period" can be found in the description of the above embodiments, and will not be repeated here.

[0171] In another possible implementation, when the first data is segmented, the first device 101 determines that the first data transmission is complete by not receiving a fifth message within a first time period. This fifth message indicates the retransmission of the last data segment. For example, if the first device 101 does not receive a fifth message indicating the retransmission of the last data segment within the first time period, the first device 101 can determine that the first data transmission is complete. For instance, if the first data is segmented into three data segments, and the first device 101 does not receive a fifth message indicating the retransmission of the last data segment, then the first device 101 can determine that the first data transmission is complete. The description of "first time period" can be found in the description of the above embodiments and will not be repeated here.

[0172] The following section will provide an example of how to send the first data or data segments of the first data, using a specific random access procedure as an example.

[0173] Example 1 uses random access as a 2-step CBRA, with the first data or a data segment of the first data carried in message 1. This process may include, but is not limited to, the following steps 11 and 12:

[0174] Step 11: The first device 101 initiates random access (i.e., 2-step CBRA) on the first resource. The first device 101 sends message 1 to the second device 102. In the 2-step CBRA process, message 1 may include, but is not limited to, at least one of the following: the identifier of the first device 101 (e.g., the identifier assigned by the EPC or core network or the identifier assigned by a third party), the first data or the first data segment, the second identifier (e.g., a 16-bit random number), the second indication information, and the third indication information.

[0175] Step 12: The second device 102 sends a message to the first device 101. This message may include, but is not limited to, at least one of the following: ACK, NACK, or NDI (New Data Indicator) indication, retransmission resource, or new transmission resource. Specifically, ACK may be a positive acknowledgment message for the first data or a data segment of the first data; NACK may be a negative acknowledgment message for the first data or a data segment of the first data. The NDI indication value can be a first value, indicating retransmission, such as retransmitting the first data or a data segment of the first data; or a second value, indicating new transmission. Alternatively, the NDI indication value can be a first value, indicating new transmission, and the NDI indication value can be a second value, indicating retransmission, such as retransmitting the first data or a data segment of the first data. The first value can be 1, and the second value can be 0; or the first value can be 0, and the second value can be 1.

[0176] Example 2 uses a two-step CBRA with random access as an example, where the first data or a data segment of the first data can be sent after the random access process is completed. This process may include, but is not limited to, the following steps 21 and 24:

[0177] Step 21: The first device 101 initiates random access (i.e., 2-step CBRA) on the first resource. The first device 101 sends message 1 to the second device 102. In the 2-step CBRA process, message 1 may include, but is not limited to, at least one of the following: the identifier of the first device 101 (e.g., an identifier assigned by the EPC or core network or an identifier assigned by a third party), a second identifier (e.g., a 16-bit random number), the second indication information, and the third indication information.

[0178] Step 22: The second device 102 sends a message to the first device 101. The message may include, but is not limited to, at least one of the following: the identifier of the first device 101, the second identifier, and a resource that can be used to send the first data or a data segment of the first data.

[0179] Step 23: The first device 101 sends a message on the resource, which may include, but is not limited to, at least one of the following: the identifier of the first device 101, the second identifier, the first data, or a data segment of the first data.

[0180] Step 24: The second device 102 sends a message to the first device 101. This message may include, but is not limited to, at least one of the following: the identifier of the first device 101, the second identifier, an ACK or NACK or NDI indication, a retransmission resource, or a new transmission resource. For the descriptions of "ACK", "NACK", and "NDI indication", please refer to the relevant descriptions below step 12 in Example 1 above, which will not be repeated here.

[0181] Example 2 uses a 3-step CBRA with random access as an example, where the first data or a data segment of the first data can be sent after the random access process is completed. This process may include, but is not limited to, the following steps 31 and 34:

[0182] Step 31: The first device 101 initiates random access (i.e., 3-step CBRA) on the first resource. The first device 101 sends message 1 to the second device 102. In the 3-step CBRA process, message 1 may include, but is not limited to, at least one of the following: a second identifier (such as a 16-bit random number), the second indication information, and the third indication information.

[0183] Step 32: The second device 102 sends a message to the first device 101. This message may include, but is not limited to, at least one of the following: the second identifier, and a resource. The resource can be used to send the identifier of the first device 101 and / or the first data or data segments of the first data. That is, the resource can be used to send the identifier of the first device 101, or the resource can be used to send the first data or data segments of the first data. Alternatively, the resource can be used to send the identifier of the first device 101 and the first data or data segments of the first data. For example, if the first data is not segmented, the resource can be used to send the identifier of the first device 101 and the first data; or, if the first data is segmented into m data segments, the resource can be used to send the identifier of the first device 101 and the data segments of the first data.

[0184] Step 33: The first device 101 sends a message on the resource, which may include, but is not limited to, at least one of the following: the identifier of the first device 101, the first data, or a data segment of the first data.

[0185] Step 34: The second device 102 sends a message to the first device 101. This message may include, but is not limited to, at least one of the following: the identifier of the first device 101, the second identifier, an ACK or NACK or NDI indication, a retransmission resource, or a new transmission resource. For the descriptions of "ACK", "NACK", and "NDI indication", please refer to the relevant descriptions below step 12 in Example 1 above, which will not be repeated here.

[0186] In some embodiments, the names of information, etc., are not limited to the names described in the embodiments. Terms such as "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", "field", "symbol", "symbol", "codebook", "codeword", "codepoint", "bit", "data", "program", and "chip" can be used interchangeably.

[0187] In some embodiments, the terms “radio”, “wireless”, “radio access network (RAN)”, “access network (AN)”, and “RAN-based” can be used interchangeably.

[0188] In some embodiments, "acquire," "get," "obtain," "receive," "transmit," "bidirectional transmission," and "send and / or receive" can be used interchangeably and can be interpreted as receiving from other entities, acquiring from protocols, acquiring from higher layers, obtaining through self-processing, or autonomous implementation. Protocols include, for example, at least one of the 3GPP protocol, Wi-Fi protocol, and audio and / or video protocols.

[0189] In some embodiments, terms such as “send,” “transmit,” “report,” “distribute,” “transfer,” “bidirectional transmission,” “send and / or receive” can be used interchangeably.

[0190] In some embodiments, the determination or judgment can be made by a value represented by 1 bit (0 or 1), or by a true or false value (boolean), or by a comparison of numerical values ​​(e.g., a comparison with a predetermined value), but is not limited thereto.

[0191] The communication method involved in the embodiments of this disclosure may include at least one of steps S3101 to S3106. For example, step S3101 may be implemented as an independent embodiment, step S3102 + step S3103 may be implemented as an independent embodiment, step S3102 + step S3103 + step S3106 may be implemented as an independent embodiment, step S3102 + step S3103 + step S3104 may be implemented as an independent embodiment, step S3102 + step S3103 + step S3105 may be implemented as an independent embodiment, step S3102 + step S3103 + step S3105 + step S3106 may be implemented as an independent embodiment, and step S3102 + step S3106 may be implemented as an independent embodiment, but is not limited thereto.

[0192] In some embodiments, steps S3102, S3103, S3104, S3105, and S3106 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0193] In some embodiments, steps S3101, S3104, S3105, and S3106 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0194] In some embodiments, steps S3101, S3104, and S3105 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0195] In some embodiments, steps S3101, S3105, and S3106 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0196] In some embodiments, steps S3101 and S3105 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0197] In some embodiments, steps S3101, S3104, and S3106 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0198] In some embodiments, steps S3101 and S3104 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0199] In some embodiments, steps S3101, S3103, S3104, and S3105 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0200] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0201] Figure 4 is an interactive schematic diagram of the communication method according to an embodiment of the present disclosure. It should be noted that the communication method of this embodiment can be applied to a communication device. In some possible embodiments, the device can be configured in a communication or chip to enable the electronic device or chip to perform communication functions. For example, the electronic device can be a communication device, such as the first or second device in Figure 1. Additionally, in some possible embodiments, the communication device can also be software within an electronic device, such as communication software.

[0202] As shown in Figure 4, the embodiments of this disclosure relate to communication methods, which may include, but are not limited to, the following steps.

[0203] In step S4101, the second device 102 sends the first message.

[0204] In some embodiments, the first message may be sent by the second device 102. For example, the second device 102 sends the first message to the first device 101, and correspondingly, the first device 101 receives the first message sent by the second device 102.

[0205] In some embodiments, the first message can be sent periodically. In some embodiments, the first message can be sent based on a preset time. In some embodiments, the first message can be sent when a third message is received from a third device, wherein the third message can be used to trigger the second device 102 to send the first message.

[0206] In some embodiments, the first message may be used to determine a first resource, which may be used to send a first transmission from the first device 101; wherein the first transmission may be a transmission from the first device 101 to the second device 102; wherein the first device 101 is an Internet of Things (IoT) device, and the second device 102 is a network device or an intermediate node.

[0207] In some embodiments, the first transmission may include first data associated with a first service. In some embodiments, the first service may be a DO-A service initiated by the first device 101. In some embodiments, the first device 101 may be an IoT device supporting the first service.

[0208] In some embodiments, the first message may be a paging message or a newly defined message, wherein the newly defined message is a message from the second device 102 to the first device 101. For example, the first message may include first indication information, which may indicate that the first message is sent to the first device 101 supporting the first service.

[0209] In some embodiments, when the first message is the newly defined message, the message type of the first message can indicate that the first message is a message sent to the first device 101 that supports the first service.

[0210] In step S4102, the first device 101 determines the first resource based on the first message.

[0211] In some embodiments, the second device 102 sends a first message to the first device 101, and correspondingly, the first device 101 receives the first message sent by the second device 102, and the first device 101 determines the first resource based on the first message.

[0212] In some embodiments, the first message may include a first identifier, which may be an identifier of the second device 102. In some embodiments, if the first identifier included in the first message is the same as the identifier of the second device 102 associated with the first device 101, the first device 101 may determine the first resource based on the first message, wherein the first resource may be used to send a first transmission of the first device 101, wherein the first transmission may be a transmission sent by the first device 101 to the second device 102.

[0213] In some embodiments, if it is determined that the first device 101 has a request to send first data, it may start listening to the first message; if it is determined that the first data has been sent, it may stop listening to the first message.

[0214] In some embodiments, when the first data is not segmented, a possible implementation for determining that the first data has been sent is as follows: upon receiving a second message, the first data is determined to have been sent, wherein the second message can be the first data or a positive response message for the retransmission of the first data.

[0215] In some embodiments, when the first data is not segmented, a possible implementation for determining that the first data has been sent is as follows: if a third message is not received within a first time period, the first data is determined to have been sent, wherein the third message may instruct the first data to be retransmitted.

[0216] In some embodiments, when the first data is segmented into m data segments, the possible implementation of determining that the first data transmission is complete is as follows: upon receiving the m fourth messages, the first data transmission is determined to be complete, wherein the m fourth messages can be the positive acknowledgment messages corresponding to the m data segments or the retransmission of the data segments.

[0217] In some embodiments, when the first data is segmented into m data segments, a possible implementation for determining that the first data transmission is complete is as follows: if a fifth message is not received within a first time period, the first data transmission is determined to be complete, wherein the fifth message may indicate that at least some of the m data segments need to be retransmitted.

[0218] In some embodiments, the first device 101 may initiate random access on the first resource, carrying first data or a data segment of the first data in the first transmission. The first data is associated with a first service, and the first transmission is the first message from the first device to the second device initiating random access. Correspondingly, the second device 102 may receive the first transmission sent by the first device 101, which carries the first data or a data segment of the first data. The first transmission may be the first message from the first device 101 to the second device 102 initiating random access.

[0219] In some embodiments, the first device 101 may initiate random access on the first resource, and after the random access procedure is successful, send the first data or a data segment of the first data to the second device 102. Correspondingly, the second device 102 may receive the first data or a data segment of the first data sent by the first device 101 after the random access procedure is successful.

[0220] In some embodiments, the first transmission includes second indication information and / or third indication information. The second indication information indicates the reason for initiating the random access, and the third indication information indicates the size of the first data or a data segment of the first data. In one possible implementation, the second indication information is set to a first value, which may indicate that the first service triggers the random access procedure. The second indication information is set to a second value, which may indicate that a non-first service triggers the random access procedure. For example, the non-first service triggering the random access procedure may mean that the triggering reason is not the first service. In another possible implementation, the second indication information is not defaulted, which may indicate that the first service triggers the random access procedure. The default second indication information may indicate that a non-first service triggers the random access procedure.

[0221] The communication method involved in the embodiments of this disclosure may include at least one of steps S4101 to S4102. For example, step S4101 may be implemented as a standalone embodiment, step S4102 may be implemented as a standalone embodiment, and step S4101 + step S4102 may be implemented as a standalone embodiment, but is not limited thereto.

[0222] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0223] It is worth noting that the embodiments of this disclosure provide a communication method, specifically a method supporting DO-A data transmission, which can solve the problem of how IoT devices that actively send data in IoT scenarios determine the starting boundary of resources (i.e., the aforementioned first resource). The following will describe this in conjunction with embodiments.

[0224] In some embodiments, the second device periodically sends a first message, through which the first device determines a first resource. This first resource can be used to send a first transmission from the first device to the second device.

[0225] For example, the second device can be a reader, such as a network device (e.g., a BS reader) or an intermediate node. For example, the first device can be an IoT device, such as an A-IoT device or other IoT device; the first device can be an IoT device used for DO-A services. For example, the first message can be an R2D message; for example, the second device can send the first message periodically; for example, the second device can send the first message non-periodically, for example, based on a preset time. For example, a third device (CN) triggers the second device to send the first message; for example, the third device can instruct the second device on the period at which the second device sends the first message. For example, the second device can determine the period for sending the first message based on an implementation. For example, the first message can carry a second device identifier (reader ID) or a server identifier (server ID). For example, the first device can determine the associated second device according to a pre-configuration, and the first device only receives the first message sent by the associated second device.

[0226] For example, the first message can be a paging message or other newly defined R2D message. For example, the first message can include first indication information, which can be used to indicate that the first message is addressed to a first device, and that the first device is used for the DO-A service. For example, the first message can be a paging message, which does not carry a device identifier and is not intended to page all devices that receive the first message; the first indication information indicates that the first message is sent to the first device used for the DO-A service. For example, the first message can be a newly defined R2D message, optionally including first indication information to indicate that the first message is sent to the first device used for the DO-A service. For example, the newly defined R2D message can be identified as an R2D message sent to the first device used for the DO-A service by, for example, the message type; the newly defined R2D message may not contain first indication information. The first indication information can be 1 bit or more bits of indication information, and its specific implementation is not specifically limited.

[0227] For example, IoT devices that do not support DO-A service types can ignore this first message. For example, AIoT devices of version R19 (all types of AIoT devices) ignore this first message.

[0228] In some embodiments, the first device determines that there is a first data transmission request, and the first device listens for R2D transmissions (as described in the first message above). The first device determines that the first data transmission is complete, and the first device stops listening for the R2D transmissions (as described in the first message).

[0229] For example, a first device determines that it has first data to send and begins listening for R2D transmissions. For example, this first data is DO-A data. For example, the first device is a device used for DO-A services. For example, the first data supports segmentation. For example, the first device determining that the first data transmission is complete means that the first device determines that all data segments of the first data have been successfully transmitted. For example, successful transmission is determined by a positive response from a second / third device or other means. For example, the second / third device may send an ACK, or the first device may not receive an instruction to retransmit / retransmit R2D segments within a certain time period, which can be used as a determination of successful transmission. This certain time period can be a defined minimum time interval, such as the minimum time interval between a D2R transmission and an associated R2D transmission; or, the certain time period can be the maximum time interval between a D2R transmission and an associated R2D transmission.

[0230] In some embodiments, the first device indicates in the first D2R message (as described in the first transmission above) that the reason for the random access is DO-A.

[0231] For example, the first device carries second indication information in message 1 during the random access process. This second indication information indicates that the reason for initiating the random access is DO-A. For example, this second indication information can be 1 bit. Setting it to a first value indicates that a DO-A service triggered the random access process; setting it to a second value indicates that a non-DO-A service triggered the random access process. For example, the presence of this second indication information indicates that a DO-A service triggered the random access process; setting it to a default value indicates that a non-DO-A service triggered the random access process.

[0232] For example, the first data or a data segment of the first data can be carried in message 1, and the first data or a data segment of the first data can be sent after the random access procedure is completed. The specific process is as follows:

[0233] CFRA / 2-step CBRA, where the first data or a data segment of the first data is carried in message 1, and the process may include, but is not limited to, the following:

[0234] Step 1: The first device sends at least one of the following to the second device: first device identifier (e.g., EPC); first data or a data segment of the first data; second identifier (16-bit random number); second indication information.

[0235] Step 2: The second device sends at least one of the following to the first device: display ACK or NACK, or NDI indication; retransmit or retransmit resources.

[0236] In CFRA / 2-step CBRA, the first data or a data segment of the first data may be sent after the random access procedure has ended. This procedure may include, but is not limited to, the following:

[0237] Step 1: The first device sends at least one of the following to the second device: first device identifier (e.g., EPC); second identifier (16-bit random number); second indication information.

[0238] Step 2: The second device sends at least one of the following to the first device: a first device identifier (e.g., EPC); a second identifier (16-bit random number); and a resource used to send the first data or a data segment of the first data.

[0239] Step 3: The first device sends at least one of the following to the second device: the first device identifier (e.g., EPC); the second identifier (16-bit random number); the first data or a data segment of the first data.

[0240] Step 4: The second device sends at least one of the following to the first device: the first device identifier (e.g., EPC); the second identifier (16-bit random number); display ACK or NACK, or NDI indication; retransmission or new transmission of resources.

[0241] In a 3-step CBRA, the first data or a segment of the first data may be sent after the random access procedure has ended. This procedure may include, but is not limited to, the following:

[0242] Step 1: The first device sends at least one of the following to the second device: a second identifier (16-bit random number); a second indication message.

[0243] Step 2: The second device sends at least one of the following to the first device: a second identifier (the second identifier in step 1); a resource for sending the first device identifier and / or first data or a data segment of the first data.

[0244] Step 3: The first device sends at least one item to the second device: the first device identifier (e.g., EPC); the first data or a data segment of the first data.

[0245] Step 4: The second device sends at least one of the following to the first device: geothermal identifier (the second identifier in step 1); first device identifier (e.g., EPC); display ACK or NACK, or NDI indication; retransmission or new transmission of resources.

[0246] This disclosure also proposes an apparatus (also referred to as a communication device, etc.) for implementing any of the above methods. For example, an apparatus is proposed that includes units or modules for implementing the steps performed by the first device in any of the above methods. Furthermore, another apparatus is proposed that includes units or modules for implementing the steps performed by the second device (network device or intermediate node) in any of the above methods.

[0247] It should be understood that the division of units or modules in the above device is only a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, the units or modules in the device can be implemented by a processor calling software: for example, the device includes a processor connected to a memory containing instructions. 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 in the above device. The processor can be, for example, a general-purpose processor, such as a Central Processing Unit (CPU) or a microprocessor, and the memory can be internal or external to the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits. The functionality of some or all of the units or modules can be achieved through the design of these hardware circuits, which can be understood as one or more processors. For example, in one implementation, the hardware circuit is an application-specific integrated circuit (ASIC). The functionality of some or all of the units or modules is achieved through the design of the logical relationships between the components within the circuit. In another implementation, the hardware circuit can be implemented using a programmable logic device (PLD). Taking a field-programmable gate array (FPGA) as an example, it can include a large number of logic gates. The connection relationships between the logic gates are configured through configuration files, thereby achieving the functionality of some or all of the units or modules. All units or modules of the above device can be implemented entirely through processor-called software, entirely through hardware circuits, or partially through processor-called software with the remaining parts implemented through hardware circuits.

[0248] In this embodiment, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction read and execute capabilities, such as a Central Processing Unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationships of hardware circuits. The logical relationships of the aforementioned hardware circuits are fixed or reconfigurable. For example, the processor is a hardware circuit implemented using an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and configuring the hardware circuit can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. Furthermore, 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), or a Deep Learning Processing Unit (DPU).

[0249] Figure 5A is a schematic diagram of the structure of the first device proposed in an embodiment of this disclosure. As shown in Figure 5A, the first device 5100 may include at least one of a transceiver module 5101, a processing module 5102, etc. In some embodiments, the transceiver module 5101 is used to receive a first message sent by a second device, the first message being used to determine a first resource; the processing module 5102 is used to determine the first resource based on the first message, the first resource being used to send a first transmission of the first device; wherein, the first transmission is a transmission sent by the first device to the second device; wherein, the first device is an Internet of Things (IoT) device, and the second device is a network device or an intermediate node.

[0250] In some embodiments, the first transmission includes first data, which is associated with a first service. In some embodiments, the first service is a DO-A service initiated by a first device.

[0251] In some embodiments, the first device is an Internet of Things (IoT) device that supports the first service.

[0252] In some embodiments, the first message includes a first identifier, which is an identifier of the second device. The processing module 5102 is configured to: determine a first resource based on the first message if the first identifier included in the first message is the same as the identifier of the second device associated with the first device.

[0253] In some embodiments, the first message is a paging message or a newly defined message, wherein the newly defined message is a message from a second device to a first device. In some embodiments, the first message includes first indication information, which indicates that the first message is a message sent to a first device that supports a first service.

[0254] In some embodiments, when the first message is a newly defined message, the message type of the first message indicates that the first message is a message sent to a first device that supports the first service.

[0255] In some embodiments, the transceiver module 5101 is configured to: start listening for a first message when the first device has a request to send first data, wherein the first data is associated with a first service; and stop listening for the first message when the first data has been sent.

[0256] In some embodiments, the first data is not segmented, and the completion of the first data transmission includes: receiving a second message, the second message being a positive acknowledgment message for the first data or the retransmission of the first data; or, if a third message is not received within a first time period, the third message indicates that the first data should be retransmitted.

[0257] In some embodiments, the first data is segmented into m data segments, and the completion of the first data transmission includes: receiving m fourth messages, which are positive acknowledgment messages corresponding to the m data segments or data segment retransmissions; or, not receiving a fifth message within a first time period, where the fifth message indicates that at least some of the m data segments need to be retransmitted.

[0258] In some embodiments, the transceiver module 5101 is configured to: initiate random access on a first resource, carry first data or a data segment of the first data in a first transmission, the first data being associated with a first service, and the first transmission being a first message from a first device to a second device initiating random access; or, after the random access process is successful, send the first data or a data segment of the first data to the second device.

[0259] In some embodiments, the first transmission includes second indication information and / or third indication information. The second indication information indicates the reason for initiating random access, and the third indication information indicates the size of the first data or the data segment of the first data. The second indication information is set to a first value, indicating that a first service triggers a random access procedure; or the second indication information is set to a second value, indicating that a non-first service triggers a random access procedure. For example, the non-first service triggering a random access procedure could mean that the triggering reason is not the first service. Alternatively, if the second indication information is not defaulted, it indicates that a first service triggers a random access procedure; if the second indication information is defaulted, it indicates that a non-first service triggers a random access procedure. For example, the non-first service triggering a random access procedure could mean that the triggering reason is not the first service.

[0260] Optionally, the transceiver module is used to perform at least one of the communication steps (e.g., steps S3102, S3104, S3105, and S3106) performed by the first device 101 in any of the above methods, which will not be elaborated here. Optionally, the processing module is used to perform at least one of the other steps (e.g., steps S3103 and S4102, but not limited thereto) performed by the first device 101 in any of the above methods, which will not be elaborated here.

[0261] Figure 5B is a schematic diagram of the structure of the second device proposed in an embodiment of this disclosure. As shown in Figure 5B, the second device 5200 may include at least one of a transceiver module 5201, a processing module 5202, etc. In some embodiments, the transceiver module 5201 is used to send a first message to a first device, the first message being used to determine a first resource, the first resource being used to send a first transmission of the first device; wherein, the first transmission is a transmission sent by the first device to the second device; wherein, the first device is an Internet of Things (IoT) device, and the second device is a network device or an intermediate node.

[0262] In some embodiments, the first transmission includes first data, which is associated with a first service. In some embodiments, the first service is a DO-A service initiated by a first device.

[0263] In some embodiments, the first device is an Internet of Things (IoT) device that supports the first service.

[0264] In some embodiments, the transceiver module 5201 is configured to: periodically send a first message; or, send a first message based on a preset time; or, send a first message when a third message is received from a third device, wherein the third message is used to trigger a second device to send the first message.

[0265] In some embodiments, the first message includes a first identifier, which is an identifier of the second device. The first identifier included in the first message is used by the first device to determine whether to determine the first resource based on the first message.

[0266] In some embodiments, the first message is a paging message or a newly defined message, wherein the newly defined message is a message from a second device to a first device. In some embodiments, the first message includes first indication information, which indicates that the first message is a message sent to a first device that supports a first service.

[0267] In some embodiments, when the first message is a newly defined message, the message type of the first message indicates that the first message is a message sent to a first device that supports the first service.

[0268] In some embodiments, the transceiver module 5201 is configured to: receive a first transmission sent by a first device, wherein the first transmission is a first message from the first device to the second device initiating random access, the first transmission carrying first data or a data segment of the first data, and the first data being associated with a first service; or, receive the first data or a data segment of the first data sent by the first device after the random access process is successful.

[0269] In some embodiments, the first transmission includes second indication information and / or third indication information. The second indication information indicates the reason for initiating random access, and the third indication information indicates the size of the first data or the data segment of the first data. The second indication information is set to a first value, indicating that a first service triggers a random access procedure; or the second indication information is set to a second value, indicating that a non-first service triggers a random access procedure. For example, the non-first service triggering a random access procedure could mean that the triggering reason is not the first service. Alternatively, if the second indication information is not defaulted, it indicates that a first service triggers a random access procedure; if the second indication information is defaulted, it indicates that a non-first service triggers a random access procedure. For example, the non-first service triggering a random access procedure could mean that the triggering reason is not the first service.

[0270] Optionally, the transceiver module is used to perform at least one of the communication steps (such as step S3101, step S4101, but not limited thereto) performed by the second device 102 in any of the above methods, which will not be elaborated here. Optionally, the processing module is used to perform at least one of the other steps performed by the second device 102 in any of the above methods, which will not be elaborated here.

[0271] In some embodiments, the transceiver module may include a transmitting module and / or a receiving module, which may be separate or integrated. Optionally, the transceiver module may be interchangeable with a transceiver.

[0272] In some embodiments, the processing module may be a single module or may include multiple sub-modules. Optionally, the multiple sub-modules may each perform all or part of the steps required by the processing module.

[0273] In some embodiments, the processing module can be interchanged with the processor, and the transceiver module can be interchanged with the transceiver.

[0274] Figure 6A is a schematic diagram of the structure of the communication device 6100 proposed in an embodiment of this disclosure. The communication device 6100 can be a first device (such as an IoT device), or a second device, such as a network device (e.g., an access network device, core network device, etc.) or an intermediate node (e.g., a relay, or an IAB, or a terminal, etc.). It can also be a chip, chip system, or processor that supports the first device in implementing any of the above methods, or a chip, chip system, or processor that supports the second device in implementing any of the above methods. The communication device 6100 can be used to implement the methods described in the above method embodiments; for details, please refer to the descriptions in the above method embodiments.

[0275] As shown in Figure 6A, the communication device 6100 is used to execute any of the above methods. In some embodiments, the communication device 6100 includes one or more processors 6101. The processor 6101 may be a general-purpose processor or a special-purpose processor, such as a baseband processor or a central processing unit. The baseband processor may be used to process communication protocols and communication data, and the central processing unit may be used to control communication devices (e.g., base stations, baseband chips, terminal devices, terminal device chips, DUs or CUs, etc.), execute programs, and process program data. Optionally, the communication device 6100 is used to execute any of the above methods. Optionally, one or more processors 6101 are used to invoke instructions to cause the communication device 6100 to execute any of the above methods.

[0276] In some embodiments, the communication device 6100 further includes one or more transceivers 6103. When the communication device 6100 includes one or more transceivers 6103, the transceiver 6103 performs at least one of the communication steps such as sending and / or receiving in the above method (e.g., steps S3101, S4101, S3102, S3104, S3105, S3106, but not limited thereto), and the processor 6101 performs at least one of other steps (e.g., steps S3103, S4102, but not limited thereto). In optional embodiments, the transceiver may include a receiver and / or a transmitter, which may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, interface, etc., can be used interchangeably; the terms transmitter, transmitting unit, transmitter, transmitting circuit, etc., can be used interchangeably; the terms receiver, receiving unit, receiver, receiving circuit, etc., can be used interchangeably.

[0277] In some embodiments, the communication device 6100 further includes one or more memories 6102 for storing data and / or instructions. Optionally, one or more processors 6101 are used to invoke instructions stored in the memory 6102 to cause the communication device 6100 to perform any of the above methods. Optionally, all or part of the memory 6102 may also be located outside the communication device 6100. In an optional embodiment, the communication device 6100 may include one or more interface circuits 6104. Optionally, the interface circuit 6104 is connected to the memory 6102 and can be used to receive data and / or instructions from the memory 6102 or other devices, and can be used to send data and / or instructions to the memory 6102 or other devices. For example, the interface circuit 6104 can read data and / or instructions stored in the memory 6102 and send the data and / or instructions to the processor 6101.

[0278] The communication device 6100 described in the above embodiments may be a first device or a second device, but the scope of the communication device 6100 described in this disclosure is not limited thereto, and the structure of the communication device 6100 may not be limited by FIG. 6A. The communication device may be a standalone device or may be part of a larger device. For example, the communication device may be: (1) a standalone integrated circuit IC, or chip, or chip system or subsystem; (2) a collection of one or more ICs, optionally, the IC collection may also include storage components for storing data, programs and / or instructions; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, terminal device, smart terminal device, cellular phone, wireless device, handheld device, mobile unit, vehicle device, network device, cloud device, artificial intelligence device, etc.; (6) others, etc.

[0279] Figure 6B is a schematic diagram of the structure of chip 6200 according to an embodiment of this disclosure. For cases where the communication device 6100 can be a chip or a chip system, please refer to the schematic diagram of chip 6200 shown in Figure 6B, but it is not limited thereto.

[0280] Chip 6200 includes one or more processors 6201. Chip 6200 is used to perform any of the methods described above.

[0281] In some embodiments, chip 6200 further includes one or more interface circuits 6202. Optionally, terms such as interface circuit, interface, and transceiver pin can be used interchangeably. In some embodiments, chip 6200 further includes one or more memories 6203 for storing data and / or instructions. Optionally, all or part of the memories 6203 may be located outside of chip 6200. Optionally, interface circuit 6202 is connected to memory 6203, and interface circuit 6202 can be used to receive data and / or instructions from memory 6203 or other devices, and interface circuit 6202 can be used to send data and / or instructions to memory 6203 or other devices. For example, interface circuit 6202 can read data and / or instructions stored in memory 6203 and send the data and / or instructions to processor 6201.

[0282] In some embodiments, the interface circuit 6202 performs at least one of the communication steps such as sending and / or receiving in the above-described method (e.g., steps S3101, S4101, S3102, S3104, S3105, and S3106, but not limited thereto). The interface circuit 6202 performing the communication steps such as sending and / or receiving in the above-described method refers, for example, to the interface circuit 6202 performing data and / or instruction interaction between the processor 6201, the chip 6200, the memory 6203, or the transceiver device. In some embodiments, the processor 6201 performs at least one of other steps (e.g., steps S3103 and S4102, but not limited thereto).

[0283] The modules and / or devices described in the various embodiments, such as virtual devices, physical devices, and chips, can be combined or separated arbitrarily as needed. Optionally, some or all steps can also be performed collaboratively by multiple modules and / or devices, which is not limited here.

[0284] This disclosure also proposes a storage mechanism in which instructions are stored on the storage medium, which, when executed on a communication device, cause the communication device 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 not limited thereto; it may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but not limited thereto; it may also be a temporary storage medium.

[0285] This disclosure also proposes a program product, including a program and / or instructions, which, when executed by a communication device, cause the communication device to perform any of the above methods. Optionally, the program product is a computer program product. Optionally, the program product is stored on the storage medium.

[0286] This disclosure also proposes a computer program that, when run on a computer, causes the computer to perform any of the above methods.

[0287] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. The computer program product includes one or more computer programs. When the computer program is loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this disclosure are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer program can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the computer program can be transferred from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device such as a server or data center that integrates one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., high-density digital video discs (DVDs)), or semiconductor media (e.g., solid-state disks (SSDs)).

[0288] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this disclosure.

[0289] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0290] The above description is merely a specific embodiment of this disclosure, but the scope of protection of this disclosure is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this disclosure should be included within the scope of protection of this disclosure. Therefore, the scope of protection of this disclosure should be determined by the scope of the claims.

Claims

1. A communication method, characterized in that, The method is performed by a first device, and the method includes: Receive a first message sent by the second device, the first message being used to determine the first resource; The first resource is determined based on the first message, and the first resource is used to send a first transmission of the first device; wherein, the first transmission is a transmission sent by the first device to the second device; The first device is an Internet of Things (IoT) device, and the second device is a network device or an intermediate node.

2. The method as described in claim 1, characterized in that, The first transmission includes first data, which is associated with a first service.

3. The method as described in claim 2, characterized in that, The first service is a DO-A service initiated by the first device.

4. The method as described in claim 2 or 3, characterized in that, The first device is an IoT device that supports the first service.

5. The method according to any one of claims 1-4, characterized in that, The first message includes a first identifier, which is the identifier of the second device. Determining the first resource based on the first message includes: The first identifier included in the first message is the same as the identifier of the second device associated with the first device, and the first resource is determined based on the first message.

6. The method according to any one of claims 1-5, characterized in that, The first message is a paging message or a newly defined message.

7. The method according to any one of claims 1-6, characterized in that, The first message includes first indication information, which indicates that the first message is sent to a first device that supports the first service.

8. The method as described in claim 6, characterized in that, When the first message is the newly defined message, the message type of the first message indicates that the first message is a message sent to the first device that supports the first service.

9. The method according to any one of claims 1-8, characterized in that, The method further includes: Once it is determined that the first device has a request to send first data, it begins to listen for the first message, and the first data is associated with the first service. Once the first data transmission is complete, stop listening to the first message.

10. The method as described in claim 9, characterized in that, The first data was not segmented, and the completion of the first data transmission includes: A second message is received, wherein the second message is an affirmative acknowledgment message for the first data or a retransmission of the first data; or, If a third message is not received within the first time, the third message indicates that the first data should be retransmitted.

11. The method as described in claim 9, characterized in that, The first data is segmented into m data segments, and the completion of the first data transmission includes: Upon receiving the m fourth messages, wherein the m fourth messages are positive acknowledgment messages corresponding to the m data segments or data segment retransmissions; or, If the fifth message is not received within the first time, the fifth message indicates that at least some of the m data segments need to be retransmitted.

12. The method according to any one of claims 1-11, characterized in that, The method further includes: Initiating random access on the first resource, carrying first data or data segments of the first data in the first transmission, the first data being associated with a first service, and the first transmission being the first message from the first device to the second device for initiating random access; or After the random access procedure is successful, the first data or a data segment of the first data is sent to the second device.

13. The method as described in claim 12, characterized in that, The first transmission includes second indication information and / or third indication information, wherein the second indication information indicates the reason for initiating the random access, and the third indication information indicates the size of the first data or a data segment of the first data; wherein... The second indication information takes a first value, indicating that the first service triggers the random access procedure; or the second indication information takes a second value, indicating that a non-first service triggers the random access procedure; or... If the second indication information is not defaulted, it indicates that the first service triggers the random access procedure; if the second indication information is defaulted, it indicates that a non-first service triggers the random access procedure.

14. A communication method, characterized in that, The method is performed by a second device, and the method includes: A first message is sent to a first device, the first message being used to determine a first resource, the first resource being used to send a first transmission from the first device; wherein, the first transmission is a transmission sent by the first device to the second device; The first device is an Internet of Things (IoT) device, and the second device is a network device or an intermediate node.

15. The method as described in claim 14, characterized in that, The first transmission includes first data, which is associated with a first service.

16. The method as described in claim 15, characterized in that, The first service is a DO-A service initiated by the first device.

17. The method as described in claim 15 or 16, characterized in that, The first device is an IoT device that supports the first service.

18. The method according to any one of claims 14-17, characterized in that, Sending the first message includes: The first message is sent periodically; or, The first message is sent based on a preset time; or... Upon receiving a third message from a third device, the first message is sent, wherein the third message is used to trigger the second device to send the first message.

19. The method according to any one of claims 14-18, characterized in that, The first message includes a first identifier, which is an identifier of the second device. The first identifier included in the first message is used by the first device to determine whether to determine the first resource based on the first message.

20. The method according to any one of claims 14-19, characterized in that, The first message is a paging message or a newly defined message.

21. The method according to any one of claims 14-20, characterized in that, The first message includes first indication information, which indicates that the first message is sent to a first device that supports the first service.

22. The method as described in claim 20, characterized in that, When the first message is the newly defined message, the message type of the first message indicates that the first message is a message sent to the first device that supports the first service.

23. The method according to any one of claims 14-22, characterized in that, The method further includes: The system receives the first transmission sent by the first device, wherein the first transmission is a first message from the first device to the second device initiating random access, and the first transmission carries first data or data segments of the first data, wherein the first data is associated with a first service; or... Receive the first data or a data segment of the first data sent by the first device after the random access procedure is successful.

24. The method as described in claim 23, characterized in that, The first transmission includes second indication information and / or third indication information, wherein the second indication information indicates the reason for initiating the random access, and the third indication information indicates the size of the first data or a data segment of the first data; wherein... The second indication information takes a first value, indicating that the first service triggers the random access procedure; or the second indication information takes a second value, indicating that a non-first service triggers the random access procedure; or... If the second indication information is not defaulted, it indicates that the first service triggers the random access procedure; if the second indication information is defaulted, it indicates that a non-first service triggers the random access procedure.

25. A communication device, characterized in that, The communication device is used to perform the communication method according to any one of claims 1-13 or any one of claims 14-24.

26. A storage medium storing instructions, characterized in that, When the instruction is executed on the communication device, it causes the communication device to perform the communication method as described in any one of claims 1-13 or any one of claims 14-24.

27. A program product comprising at least one of a program and instructions, characterized in that, When at least one of the programs or instructions is executed by the communication device, it implements the steps of any one of claims 1-13 or any one of claims 14-24.

Images