Data transmission method and apparatus

Abstract

A data transmission method and apparatus, applied to the fields of environment Internet of Things, etc. The method comprises: sending a paging message to a terminal device, the paging message being used for paging the terminal device; and sending scheduling information to the terminal device, the scheduling information being used for scheduling a resource for transmitting first data, the resource being determined on the basis of a data size indicated by first information, and the first information coming from a core network device. By means of the above method, a network device can determine the data size of the first data on the basis of the first information, and then schedule the resource on the basis of the data size, without waiting for a buffer status report from the terminal device. The network device can schedule the resource for the terminal device when the terminal device does not send the buffer status report, such that the power consumption of the terminal device can be reduced, the data transmission delay is reduced, and the resource utilization rate is improved. The present application is particularly suitable for scenarios such as environment Internet of Things.

Description

Data transmission method and device

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of the People's Republic of China on September 28, 2023, with application number 202311294495.9 and invention name "A Data Transmission Method and Device"; this application claims priority to the Chinese patent application filed with the State Intellectual Property Office of the People's Republic of China on May 10, 2024, with application number 202410594550.4 and invention name "A Data Transmission Method and Device", all contents of which are incorporated by reference into this application. Technical Field

[0003] The present application relates to the field of communication technology, and in particular to a data transmission method and device. Background Art

[0004] In a wireless communication system, if a terminal device has uplink data to send, the terminal device can first send a buffer status report (BSR) to the base station. The BSR can indicate the size of the buffered data to be sent by the terminal device. The base station can then allocate uplink resources to the terminal device based on the buffered data size indicated by the BSR.

[0005] When IoT technology is introduced into wireless communication systems, the structure of devices such as tags in the IoT is relatively simple. Tags may not be able to report BSRs, or the delay in the tag reporting BSR process is relatively large. At this time, how to allocate resources to devices such as tags when the base station does not receive a BSR is an urgent problem that needs to be solved.

[0006] Summary of the Invention

[0007] The present application provides a data transmission method and apparatus for providing a solution for resource allocation.

[0008] In the first aspect, the present application provides a data transmission method, which is applicable to scenarios such as ambient IoT (AIoT). The execution subject of the method is a network device or a module or chip in the network device, and the method is described here by taking the network device as the execution subject as an example. In the method, a first signaling is sent to a terminal device; the first signaling instructs the terminal device to report first data, and the first signaling is used by the terminal device to determine not to send a buffer status report related to the first data; scheduling information is sent to the terminal device, and the scheduling information is used to schedule resources for transmitting the first data, and the size of the resources is determined according to the preset data size of the first data.

[0009] In the above method, through the first signaling, it can be determined whether the terminal device sends a buffer status report. Therefore, scheduling information can be sent to the terminal device without receiving the buffer status report from the terminal device, thereby proposing a resource scheduling process without buffer status report. Since the terminal device does not need to send a buffer status report, the power consumption of the terminal device can be reduced, the data transmission delay can be reduced, and the resource utilization rate can be improved. It is particularly suitable for scenarios such as the Internet of Things that have high power consumption requirements.

[0010] In a possible implementation manner, the scheduling information is sent without receiving the buffer status report.

[0011] In a possible implementation, the method further includes: receiving the first signaling and first indication information from a core network device, where the first indication information indicates a data size of the first data.

[0012] In this method, since the core network device indicates the data size of the first data through the first indication information, the data size of the first data can be determined when the first signaling is received. Therefore, when scheduling resources, there is no need to wait for the buffer status report of the terminal device, and scheduling information can be sent without receiving the buffer status report of the terminal device.

[0013] In a possible implementation, the first signaling is an inventory signaling, and the first data is service data of an inventory service.

[0014] In a possible implementation, the first signaling is a read signaling, and the first data is data stored in the terminal device.

[0015] In a possible implementation, the first signaling is located in a paging message, a random access response message, or a first message; wherein the first message is a message sent after the random access of the terminal device is completed.

[0016] In a possible implementation manner, the first signaling further includes second indication information, where the second indication information indicates not to send the buffer status report.

[0017] In this method, the second indication information is used to directly instruct the terminal device not to send a buffer status report, thereby reducing the judgment process of whether the terminal device sends a buffer status report, saving power consumption of the terminal device and improving data transmission efficiency.

[0018] In a possible implementation, the terminal device is a tag in an environmental Internet of Things.

[0019] In a possible implementation, the method further includes:

[0020] A second message is received from the terminal device through the resource, wherein the second message includes first data; wherein the data size indicated by the first information is equal to the data size of the first data, or the data size indicated by the first information is equal to the data size of the second message.

[0021] In a possible implementation, the method further includes:

[0022] A second message is received from the terminal device through the resource, wherein the second message includes first data, and the second message also includes at least one of an access layer message header and an access layer signaling; wherein the data size indicated by the first information is equal to the sum of at least one of the data size of the access layer message header and the data size of the access layer signaling and the data size of the first data.

[0023] In a second aspect, the present application provides a data transmission method, which is applicable to scenarios such as the environmental Internet of Things. The execution subject of the method is a terminal device or a module or chip in the terminal device, and the terminal device is used as an example for description. In the method, a first signaling is received from a network device, and the first signaling instructs the terminal device to report first data; based on the first signaling, it is determined not to send a buffer status report related to the first data, and scheduling information is received from the network device, the scheduling information is used to schedule resources, and the resources are used to transmit the first data; the size of the resources is determined according to the preset data size of the first data.

[0024] In a possible implementation, the method further includes: triggering the buffer status report; wherein the logical channel of the buffer status report that is triggered has the lowest priority, or the logical channel of the buffer status report that is triggered is a closed logical channel.

[0025] In a possible implementation, determining not to send a buffer status report related to the first data according to the first signaling includes: a signaling type of the first signaling is a preset type, and determining not to send the buffer status report.

[0026] In one possible implementation, the first signaling also includes second indication information, and the second indication information indicates not to send the buffer status report; the determining not to send the buffer status report related to the first data based on the first signaling includes: determining not to send the buffer status report based on the second indication information.

[0027] In a possible implementation, the first signaling is an inventory signaling, and the first data is service data of an inventory service.

[0028] In a possible implementation, the first signaling is a read signaling, and the first data is data stored in the terminal device.

[0029] In a possible implementation, the first signaling is located in a paging message, a random access response message, or a first message; wherein the first message is a message sent after the random access of the terminal device is completed.

[0030] In a possible implementation, the method is applied to a terminal device, which is a tag in an environmental Internet of Things.

[0031] In a possible implementation, the method further includes:

[0032] A second message is sent to the network device through the resource, where the second message includes first data; wherein the data size indicated by the first information is equal to the data size of the first data, or the data size indicated by the first information is equal to the data size of the second message.

[0033] In a possible implementation, the method further includes:

[0034] A second message is sent to the network device through the resource, wherein the second message includes the first data, and the second message also includes at least one of an access layer message header and an access layer signaling; wherein the data size indicated by the first information is equal to the sum of at least one of the data size of the access layer message header and the data size of the access layer signaling and the data size of the first data.

[0035] In a third aspect, the present application provides a data transmission method applicable to scenarios such as the environmental Internet of Things. The method is performed by a core network device or a module or chip within the core network device. The method is described herein using the core network device as an example. In this method, a first signaling is determined; the first signaling instructs the terminal device to report first data; the first signaling and first indication information are sent to a network device; the first indication information indicates the data size of the first data.

[0036] In a fourth aspect, the present application provides a data transmission method applicable to scenarios such as the environmental Internet of Things. The method is performed by a network device or a module or chip within the network device, and is described herein using the network device as the example execution entity. In this method, a paging message is sent to a terminal device, the paging message being used to page the terminal device; and scheduling information is sent to the terminal device, the scheduling information being used to schedule resources for transmitting first data, the resources being determined based on the data size indicated by first information, the first information being from a core network device.

[0037] Through the above method, the network device can determine the data size of the first data based on the first information, and thus can schedule resources based on the data size without waiting for a buffer status report from the terminal device. If the terminal device does not send a buffer status report, the network device can schedule resources for the terminal device, thereby reducing power consumption of the terminal device, reducing data transmission latency, and improving resource utilization.

[0038] In a possible implementation, the scheduling information is sent without receiving a first buffer status report related to the first data.

[0039] In a possible implementation manner, the first information includes the data size of the first data.

[0040] In a possible implementation, the first information is second data sent to the terminal device, and the second data has a corresponding data size to the first data.

[0041] In a possible implementation, the first information indicates a service corresponding to the first data, and there is a corresponding relationship between the service corresponding to the first data and the data size of the first data.

[0042] In one possible implementation, the method further includes: sending a first signaling to a terminal device; the first signaling instructs the terminal device to report the first data; wherein the first signaling is used to trigger an inventory process, and the first data is business data of an inventory business; or, the first signaling is used to trigger a reading process, and the first data is data stored by the terminal device.

[0043] In a possible implementation manner, the first signaling is located in the paging message, the random access response message, or the first message;

[0044] The first message is a message sent after random access of the terminal device is completed.

[0045] In a possible implementation, the method further includes: sending second information to the terminal device, the second information indicating whether to send or not to send a first buffer status report related to the first data, and the second information is located in the paging message or random access response message.

[0046] In this method, the second information is used to directly indicate not to send a buffer status report, thereby reducing the complexity of the terminal device in determining whether to send a buffer status report, saving power consumption of the terminal device, and being particularly suitable for devices such as tags in the environmental Internet of Things.

[0047] In a possible implementation, the terminal device is a tag in an environmental Internet of Things.

[0048] In a possible implementation, the method further includes: sending third information to the terminal device, wherein the third information instructs the terminal device to report a second buffer status report before data transmission, and the third information is sent after the terminal device completes random access.

[0049] In a fifth aspect, the present application provides a data transmission method applicable to scenarios such as the environmental Internet of Things. The method is performed by a terminal device or a module or chip within the terminal device, and is described herein using the terminal device as the example. In this method, a paging message is received from a network device, the paging message being used to page the terminal device; and scheduling information is received from the network device, the scheduling information being used to schedule resources for transmitting first data, the resources being determined based on the data size indicated by the first information, the first information being from a core network device.

[0050] In a possible implementation manner, the first information includes the data size of the first data.

[0051] In a possible implementation, the first information is second data sent to the terminal device, and the second data has a corresponding data size to the first data.

[0052] In one possible implementation, the method further includes: receiving a first signaling from the network device; the first signaling instructs reporting of the first data; wherein the first signaling is used to trigger an inventory process, and the first data is business data of an inventory business; or, the first signaling is used to trigger a reading process, and the first data is data stored in the terminal device.

[0053] In a possible implementation, the first signaling is located in the paging message or the random access response message or the first message; wherein, the first message is a message sent after the random access of the terminal device is completed.

[0054] In one possible implementation, the method is applied to tags in an environmental Internet of Things.

[0055] In a possible implementation manner, the first data is sent to the network device through the resource.

[0056] In a sixth aspect, the present application provides a data transmission method applicable to scenarios such as the ambient Internet of Things. The method is performed by a core network device or a module or chip within the core network device. The method is described herein using the core network device as an example. In the method, first information is determined, where the first information indicates the size of first data; and the first information is sent to a network device.

[0057] In the seventh aspect, the present application provides a data transmission method, which is applicable to scenarios such as the environmental Internet of Things. The execution subject of the method is a second device or a module or chip in the second device, and the second device is a network device or a reader / writer or a terminal device or a tag and other devices. Here, the second device is used as an example for description. In this method, configuration information is sent to the first device, and the configuration information is used to indicate a first resource or a first transmission block size. The first resource is determined according to the first data size indicated by the first information. The first transmission block size is used to indicate the size of the data sent by the first device, and the first information comes from the core network device.

[0058] In a possible implementation, the method further includes sending a paging message to the first device, where the paging message is used to page the first device.

[0059] In a possible implementation manner, the configuration information is sent without receiving a first buffer status report from the first device.

[0060] In a possible implementation manner, the first information includes the first data size.

[0061] In a possible implementation, the first information is second data sent to the first device, and the second data has a corresponding size to the first data.

[0062] In a possible implementation, the first information indicates a first service, and there is a corresponding relationship between the first service and the first data size.

[0063] In a possible implementation, the method further includes:

[0064] Sending a first signaling to the first device; the first signaling instructs the first device to report first data;

[0065] The first signaling is used to trigger an inventory process, and the first data is service data of an inventory service;

[0066] Alternatively, the first signaling is used to trigger a reading process, and the first data is data stored in the first device.

[0067] In a possible implementation manner, the first signaling is located in a paging message, a random access response message, or a first message;

[0068] The first message is a message sent after random access of the first device is completed.

[0069] In one possible implementation, the method further includes: receiving a second message from the first device through the first resource, the second message including first data; wherein the first data size is equal to the data size of the first data, or the first data size is equal to the data size of the second message.

[0070] In one possible implementation, the method further includes: sending a second message to the second device through the first resource, the second message including first data, the second message also including at least one of an access layer message header, access layer signaling, and padding; the first data size is less than or equal to the sum of at least one of the data size of the access layer message header, the data size of the access layer signaling, the data size of the padding, and the data size of the first data.

[0071] In a possible implementation, the method further includes: sending second information to the first device, where the second information indicates whether to send or not to send the first buffer status report, and the second information is located in the paging message or the random access response message.

[0072] In an eighth aspect, the present application provides a data transmission method, which is applicable to scenarios such as the environmental Internet of Things. The execution subject of the method is a first device or a module or chip in the first device, and the first device is a terminal device or a tag or other device. Here, the first device is used as an example for description. In this method: configuration information is received from the second device, and the configuration information is used to indicate a first resource or a first transmission block size. The first resource is determined according to the first data size indicated by the first information. The first transmission block size is used to indicate the size of the data sent by the first device. The first information comes from the core network device.

[0073] In one possible implementation, a paging message is received from a second device, where the paging message is used to page a first device.

[0074] In a possible implementation manner, the first information includes the first data size.

[0075] In a possible implementation, the first information is second data sent to the first device, and the second data has a corresponding size to the first data.

[0076] In one possible implementation, the method further includes: receiving a first signaling from the second device; the first signaling instructs reporting of first data; wherein the first signaling is used to trigger an inventory process, and the first data is business data of an inventory business; or, the first signaling is used to trigger a reading process, and the first data is data stored by the first device.

[0077] In a possible implementation, the first signaling is located in the paging message or the random access response message or the first message; wherein the first message is a message sent after the random access of the first device is completed.

[0078] In one possible implementation, the method further includes: sending a second message to the second device through the first resource, the second message including first data; wherein the first data size is equal to the data size of the first data, or the first data size is equal to the data size of the second message.

[0079] In one possible implementation, the method further includes: receiving a second message from the first device through the first resource, the second message including first data, the second message also including at least one of an access layer message header, access layer signaling, and padding; the first data size is less than or equal to the sum of at least one of the data size of the access layer message header, the data size of the access layer signaling, the data size of the padding, and the data size of the first data.

[0080] In a ninth aspect, the present application provides a data transmission method applicable to scenarios such as the environmental Internet of Things. The method is performed by a core network device or a module or chip in the core network device. The method is described here using the core network device as an example. The method includes:

[0081] determining first information, the first information indicating a first data size;

[0082] The first information is sent to the second device.

[0083] In a tenth aspect, the present application further provides a communication device capable of implementing any of the methods provided in any of the first to ninth aspects. The communication device can be implemented in hardware or by hardware executing corresponding software implementations. The hardware or software includes one or more units or modules corresponding to the above-mentioned functions.

[0084] In one possible implementation, the communication device includes a processor configured to support the communication device in executing the corresponding functions of the network device, terminal device, or core network device in the above-described method. The communication device may also include a memory, which may be coupled to the processor and stores program instructions and data necessary for the communication device. Optionally, the communication device also includes an interface circuit for supporting communication between the communication device and a device such as a terminal device.

[0085] In one possible implementation, the communication device includes corresponding functional modules for implementing the steps in the above method. The functions can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions.

[0086] In one possible embodiment, the structure of the communication device includes a processing unit and a communication unit, which can perform the corresponding functions in the above method examples. For details, please refer to the description of the method provided in any one of the first to ninth aspects, which will not be repeated here.

[0087] In an eleventh aspect, a communication device is provided, comprising a processor and an interface circuit, the interface circuit being configured to receive signals from a communication device other than the communication device and transmit them to the processor, or to transmit signals from the processor to a communication device other than the communication device, the processor implementing the functional modules of the method in any possible implementation of any of the first to ninth aspects through logic circuitry or by executing a computer program or instruction. Optionally, the communication device further comprises a memory configured to store the computer program or instruction.

[0088] In the twelfth aspect, a computer-readable storage medium is provided, which stores a computer program or instruction. When the computer program or instruction is executed by a processor, the method in any possible implementation of any one of the first to ninth aspects is implemented.

[0089] In the thirteenth aspect, a computer program product storing instructions is provided, which, when read and executed by a computer, implements the method in any possible implementation of any one of the first to ninth aspects.

[0090] In a fourteenth aspect, a circuit is provided for executing the method in any possible implementation of any one of the first to ninth aspects, wherein the circuit may include a chip circuit. Optionally, the circuit may also be coupled to a memory.

[0091] In a fifteenth aspect, a chip is provided, comprising a processor. When the processor executes a computer program or instruction, the processor is configured to implement the method of any possible implementation of any of the first to ninth aspects. Optionally, the chip may further include a memory. The chip may be composed of a single chip or may include a chip and other discrete components.

[0092] In the sixteenth aspect, a communication device is provided, comprising a processor, which implements the method in any possible implementation of any one of the first to ninth aspects through a logic circuit or by executing a computer program or instruction.

[0093] In the seventeenth aspect, a communication device is provided, comprising a unit or module for executing the method in any possible implementation of any one of the first to ninth aspects above.

[0094] In an eighteenth aspect, embodiments of the present application further provide a communication system. The communication system includes: a network device for implementing the method in the aforementioned first aspect and any possible implementation thereof; a terminal device for implementing the method in the aforementioned second aspect and any possible implementation thereof; and a core network device for implementing the method in the aforementioned third aspect.

[0095] In a nineteenth aspect, embodiments of the present application further provide a communication system. The communication system includes: a network device for implementing the method in the fourth aspect and any possible implementation thereof; a terminal device for implementing the method in the fifth aspect and any possible implementation thereof; and a core network device for implementing the method in the sixth aspect.

[0096] In a twentieth aspect, embodiments of the present application further provide a communication system. The communication system includes: a second apparatus for implementing the method in the seventh aspect and any possible implementation thereof; a first apparatus for implementing the method in the eighth aspect and any possible implementation thereof; and a core network device for implementing the method in the ninth aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0097] FIG1 is a schematic diagram of a system architecture provided by an embodiment of the present application;

[0098] FIG2 is a schematic diagram of a system architecture provided in an embodiment of the present application;

[0099] FIG3 is a schematic diagram of a system architecture provided in an embodiment of the present application;

[0100] FIG4 is a schematic diagram of a system architecture provided in an embodiment of the present application;

[0101] FIG5 is a flow chart of a data transmission method provided in an embodiment of the present application;

[0102] FIG6 is a flow chart of a data transmission method provided in an embodiment of the present application;

[0103] FIG7 is a flow chart of a data transmission method provided in an embodiment of the present application;

[0104] FIG8 is a flow chart of a data transmission method provided in an embodiment of the present application;

[0105] FIG9 is a schematic diagram of a data transmission method according to an embodiment of the present application;

[0106] FIG10 is a flow chart of a data transmission method provided in an embodiment of the present application;

[0107] FIG11 is a schematic diagram of the structure of a communication device provided in an embodiment of the present application;

[0108] FIG12 is a schematic diagram of the structure of a communication device provided in an embodiment of the present application;

[0109] FIG13 is a schematic diagram of the structure of a communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0110] The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, not all of the embodiments. The terms "first", "second" and corresponding terminology labels in this application are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the terms used in this way are interchangeable where appropriate, and this is merely a way of distinguishing objects of the same properties when describing the embodiments of the present application. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, so that a process, method, system, product or device that includes a series of units is not necessarily limited to those units, but may include other units that are not clearly listed or inherent to these processes, methods, products or devices.

[0111] The method provided in the embodiment of the present application can be applied to various types of mobile communication systems, for example, the Internet of Things (IoT), narrowband Internet of Things (NB-IoT), the fourth generation (4G) communication system (such as long term evolution (LTE)), the fifth generation (5G) communication system (such as 5G new radio (NR)), the hybrid architecture of LTE and NR, 6G or new communication systems emerging in future communication development, etc. The communication system may also include a machine to machine (M2M) network, a machine type communication (MTC) or other networks. Exemplarily, the method provided in the embodiment of the present application can be applied to a communication system including a tag.

[0112] The methods and devices provided in the embodiments of the present application are based on the same or similar technical concepts. Since the principles of solving problems by the methods and devices are similar, the implementation of the devices and methods can refer to each other, and the repeated parts will not be repeated.

[0113] FIG1 is a schematic diagram of a communication system applicable to an embodiment of the present application. As shown in FIG1 , the communication system includes a network device and a tag. The tag can be a standalone device or integrated with a terminal device, i.e., the tag is part of the terminal device. In this communication system, the network device can function as a reader / writer in a radio frequency identification (RFID) system, i.e., the network device can function as a reader / writer to communicate with the tag.

[0114] FIG2 is a schematic diagram of another communication system applicable to embodiments of the present application. As shown in FIG2 , the communication system includes a terminal device and a tag. The tag can be a standalone device or integrated with the terminal device. In this communication system, the terminal device can function as a reader / writer in an RFID system, i.e., the terminal device can communicate with the tag as a reader / writer, for example, via a sidelink (SL).

[0115] FIG3 shows a schematic diagram of another communication system applicable to an embodiment of the present application. As shown in FIG3 , the communication system includes a network device, an integrated access and backhaul (IAB) node, and a tag. The communication system may also include other devices, such as terminal devices. In this communication system, the network device may have the function of a reader / writer in an RFID system, and the IAB node may serve as a relay node between the network device and the tag. The tag transmits information to the IAB node, and the IAB node forwards the information to the network device via the uu interface.

[0116] In the present application, the communication system including the network device, the terminal device and the tag can also be a system with a separated architecture. In this communication system, as shown in FIG4 , the network device and the terminal device can communicate directly with each other. The network device can also have the function of a reader / writer in an RFID system. There is an uplink connection between the tag and the network device, and a downlink connection between the tag and the terminal device. The terminal device can transmit information to the tag, and the tag then forwards the information to the network device. Alternatively, there is a downlink connection between the tag and the network device, and an uplink connection between the tag and the terminal device. The network device can transmit information to the tag, and the tag then forwards the information to the terminal network device. The energy required for the tag to send information can be provided by an excitation signal, and the excitation signal can come from the network device or the terminal device.

[0117] Below, some terms in the embodiments of the present application are first explained to facilitate understanding by those skilled in the art. These explanations are only examples and do not represent limitations on these terms.

[0118] In this application, transparent transmission refers to the following: a device directly forwards a message after receiving it, without perceiving, processing, interpreting, or parsing the received message. Transparent transmission at the corresponding protocol layer refers to the following: a device directly forwards the content of the protocol layer after receiving a message, without perceiving, processing, interpreting, or parsing the content of the protocol layer that requires transparent transmission.

[0119] In the embodiment of the present application, the network device may be a device in a wireless network, and the network device may also be referred to as a network apparatus. For example, the network device may be a radio access network (RAN) node that connects a terminal device to a wireless network, and may also be referred to as an access network device. The network device includes, but is not limited to, a base station, an evolved NodeB (eNodeB), a transmission reception point (TRP), a next generation NodeB (gNB) in a fifth generation (5G) mobile communication system, an access network device in an open radio access network (O-RAN), a next generation base station in a sixth generation (6G) mobile communication system, a base station in a future mobile communication system, or an access node in a wireless fidelity (WiFi) system; or it may be a module or unit that completes part of the functions of a base station, for example, a centralized unit (CU), a distributed unit (DU), a centralized unit control plane (CU-CP) module, or a centralized unit user plane (CU-UP) module. The access network device may be a macro base station, a micro base station, an indoor station, a relay node, a donor node, etc. The present application does not limit the specific technology and specific device form used by the network device.

[0120] In some deployments, network equipment may include centralized units (CUs) and distributed units (DUs). RAN equipment, including CU and DU nodes, splits the protocol layers of the gNB in ​​the NR system. Some protocol layer functions are centrally controlled by the CU, while some or all of the remaining protocol layer functions are distributed in the DU, which is centrally controlled by the CU. Furthermore, the CU can be divided into a control plane (CU-CP) and a user plane (CU-UP). The CU-CP is responsible for control plane functions, primarily including radio resource control (RRC) and the control plane's corresponding packet data convergence protocol (PDCP) (i.e., PDCP-C). PDCP-C is primarily responsible for encryption, decryption, integrity protection, and data transmission of control plane data. The CU-UP is responsible for user plane functions, primarily including the service data adaptation protocol (SDAP) and the user plane's corresponding PDCP (i.e., PDCP-U). SDAP is primarily responsible for processing core network data and mapping flows to bearers. The PDCP-U is primarily responsible for data plane encryption and decryption, integrity protection, header compression, sequence number maintenance, and data transmission. The CU-CP and CU-UP are connected via the E1 interface. The CU-CP represents the gNB's connection to the core network via the NG interface and to the DU via the F1 control plane (i.e., F1-C). The CU-UP connects to the DU via the F1 user plane (i.e., F1-U). Alternatively, the PDCP-C may also reside in the CU-UP.

[0121] It is understandable that in different systems, CU (including CU-CP or CU-UP) or DU may have different names, but those skilled in the art can understand their meanings. For example, in an open radio access network (O-RAN) system, CU may also be called an open CU (O-CU), DU may also be called O-DU, CU-CP may also be called O-CU-CP, and CU-UP may also be called O-CU-UP. For convenience of description, this application uses CU, CU-CP, CU-UP and DU as examples. The network device may also include an active antenna unit (AAU). The CU implements some functions of the gNB, and the DU implements some functions of the gNB. For example, the CU is responsible for processing non-real-time protocols and services and implementing the functions of the RRC layer. The DU is responsible for processing physical layer protocols and real-time services and implementing the functions of the radio link control (RLC) layer, the media access control (MAC) layer and the physical (PHY) layer. In some deployments, the CU can be further divided into a Centralized Unit Control Plane (CU-CP) node and a Centralized Unit User Plane (CU-UP) node, where the CU-CP is responsible for control plane functions and the CU-UP is responsible for user plane functions.

[0122] Core network equipment: A general term for various functional entities on the network side used to manage users, data transmission, and base station configuration, including Session Management Function (SMF), User Plane Function (UPF), Access and Mobility Management Function (AMF), etc.

[0123] The terminal device involved in the embodiments of the present application may be a wireless terminal device capable of receiving scheduling and instruction information from a network device. The terminal device may be referred to as a terminal device, and may also be referred to as user equipment (UE), mobile station (MS), mobile terminal (MT), etc. The terminal device may be a device that includes wireless communication capabilities (providing voice / data connectivity to the user). For example, a handheld device with wireless connection capabilities, or an in-vehicle device, in-vehicle module, etc. Currently, some examples of terminal devices include: mobile phones, tablet computers, laptop computers, PDAs, mobile internet devices (MIDs), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals in the Internet of Vehicles, wireless terminals in self-driving, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, or wireless terminals in smart homes, device-to-device (D2D) communication terminal devices, vehicle-to-everything (V2X) communication terminal devices, smart vehicles, telematics boxes (T-boxes), machine-to-machine / machine-type communications (M2M / MTC) terminal devices, Internet of Things (IoT) The IoT (Internet of Things) terminal devices, etc. For example, the terminal device can be an onboard device, complete vehicle equipment, an onboard module, a vehicle, an onboard unit (OBU), a roadside unit (RSU), a T-box, a chip, or a system on chip (SOC), etc. The above chip or SOC can be installed in the vehicle, OBU, RSU, or T-box. Wireless terminals in industrial control can be cameras, robots, etc. Wireless terminals in smart homes can be TVs, air conditioners, vacuum cleaners, speakers, set-top boxes, etc.The terminal device can also be a V2X device, such as a smart car (or intelligent car), a digital car, an unmanned car (or driverless car or pilotless car or automobile), a self-driving car or autonomous car, a hybrid electric vehicle (HEV), a pure electric vehicle (pure EV or Battery EV), a range extended electric vehicle (REEV), a plug-in hybrid electric vehicle (plug-in HEV, PHEV), a new energy vehicle (new energy vehicle), and a roadside unit (RSU). The terminal device can also be a device in device-to-device (D2D) communication, such as an electricity meter, a water meter, etc. In addition, in an embodiment of the present application, the terminal device can also be a terminal device in an IoT system. IoT is an important part of the future development of information technology. Its main technical feature is to connect objects to the network through communication technology, thereby realizing an intelligent network of human-machine interconnection and object-to-object interconnection.

[0124] In one example, a terminal device can be called an (Environmental Internet of Things) device (a device can be an example implementation of a terminal device), and a network device or intermediate node can be called a reader. Accordingly, the communication link between the device and the reader can include a device-to-reader (DR or D2R) link and a reader-to-device (RD or R2D) link.

[0125] Optionally, the "uplink" described in the embodiments of the present application can also be understood as "D2R" or "DR", and the "downlink" can also be understood as "R2D" or "RD". Further, the "uplink signaling" can be "D2R signaling" or "DR signaling", and the "downlink signaling" can also be called "R2D signaling" or "RD signaling", but this application does not make specific limitations on this.

[0126] Tags can also be called electronic tags or RFID tags or tag devices. Alternatively, tags can also be called ambient IoT (AIoT) terminals or AIoT devices. In this application, tags can also be regarded as a terminal device. Tags can be divided into passive tags, semi-passive tags and active tags. Among them, passive tags and semi-passive tags can adopt a communication method based on backscatter, and active tags adopt a communication method that actively generates a carrier.

[0127] Another classification method is to divide tags into the following three types of devices:

[0128] Passive terminal, also known as device A: has no energy storage, cannot generate signals independently, and uses backscattering to transmit signals;

[0129] Semi-passive terminal, also known as device B: It has energy storage but cannot generate signals independently. It uses backscattering to transmit signals, and its stored energy can amplify the reflected signal.

[0130] Active terminals, also known as device C, have energy storage, can independently generate signals, and have active RF components for transmission.

[0131] In wireless communication systems, a terminal device must trigger a BSR before sending one. There are many events that trigger a BSR. For example, any of the following events will trigger a BSR:

[0132] A logical channel belonging to a logical channel group has uplink data to be sent in the radio link control (RLC) or packet data convergence protocol (PDCP) entity; or a logical channel with a higher priority than any channel belonging to a logical channel group has data to be sent; or any logical channel belonging to a logical channel group has no data to be sent (that is, a BSR with a send buffer size of 0). The BSRs triggered by these situations are called "regular BSRs".

[0133] The retransmission BSR timer (retxBSR-timer) times out and the terminal device has data available for transmission;

[0134] The periodic BSR-timer times out, triggering a periodic BSR.

[0135] Uplink resources have been allocated, and the number of padding bits is greater than or equal to the BSR control information plus its sub-header. In this case, the triggered BSR is a padding BSR.

[0136] The aforementioned BSR triggering events demonstrate that the BSR triggering and reporting process is overly complex. When IoT technology is introduced into wireless communication systems, the structure of devices such as tags is relatively simple. Tags may not be able to report BSRs, or the reporting process may consume a significant amount of tag resources. Therefore, simplifying the resource allocation process for tags in ambient IoT scenarios is an urgent issue.

[0137] The network architecture and business scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. A person skilled in the art will appreciate that, with the evolution of the network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are equally applicable to similar technical problems.

[0138] When the method provided in the present application is applied to the system in Figures 1 to 4, the method of the terminal device in the embodiment of the present application can be implemented by the label in Figures 1 to 4 or the module or chip in the label, and the method executed by the network device in the embodiment of the present application can be implemented by the network device in Figures 1 to 4 or the module or chip in the network device.

[0139] It can be understood that the present application does not specifically limit the specific structure of the execution subject of the method provided in the embodiment of the present application. The method executed by the terminal device can be applied to the terminal device or a module in the terminal device, and the method executed by the network device can be applied to the network device or a module in the network device, as long as it is possible to communicate according to the method provided in the embodiment of the present application by running a program that records the code of the method provided in the embodiment of the present application.

[0140] In the following process, the interaction between the terminal device and the network device is used as an example for explanation. In another implementation, the method performed by the network device can also be performed by the terminal device, that is, the method provided in this application can also be applied to the interaction between terminal devices.

[0141] FIG5 is a flow chart of a data transmission method according to an embodiment of the present application, wherein the method includes:

[0142] Step 501: The network device sends a first signaling to the terminal device.

[0143] Correspondingly, the terminal device receives the first signaling from the network device.

[0144] In one implementation, the first signaling is located in a paging message or a random access response message or a first message; wherein, the first message is a message after the random access of the terminal device is completed, for example, the first message comes from a second device or a core network device.

[0145] In one implementation, the terminal device may be a tag in the environmental Internet of Things, or a communication device having a tag function in the environmental Internet of Things.

[0146] In the present application, the first signaling instructs the terminal device to report the first data, or the first signaling triggers the terminal device to report the first data. The first signaling may be generated by the network device; or the first signaling may be sent by the core network device to the network device, for example, the core network device may be the AMF. When the network device is replaced with a reader / writer, the first signaling may be sent by the core network device to the network device, which then forwards the first signaling to the reader / writer, which ultimately sends the first signaling to the terminal device. Alternatively, the first signaling is sent by the core network device to the network device, which then transparently transmits the first signaling to the terminal device. If the first signaling originates from the core network device, the core network device may also send first indication information to the network device, where the first indication information indicates the data size of the first data. By indicating the data size in the first indication information, the network device can directly determine the size of the resources used to transmit the first data based on the first indication information, without waiting for the buffer status report of the terminal device. This allows the network device to send scheduling information without receiving the buffer status report from the terminal device, thereby reducing resource scheduling latency.

[0147] In various embodiments of the present application, the buffer status report may also be called a storage area status report, a register status report, a user area status report, etc.; "status report" may be replaced with "data to be transmitted" or "data size / number of bits / number of bytes".

[0148] The buffer status report can indicate the specific data size or the data range, such as indicating that the quantity does not exceed a certain number, which can reduce bit overhead. For example, bit 00 indicates no more than 32 bits, 01 indicates no more than 64 bits, 10 indicates no more than 256 bits, and 11 indicates no more than 512 bits. The specific indicated value is not limited.

[0149] In the present application, the first signaling can also be used by the terminal device to determine whether to send a buffer status report related to the first data, and the buffer status report is used to indicate the data size of the first data. The first data can be understood as the cached data to be sent by the terminal device. For example, in implementation method one, the first signaling includes second indication information, and the second indication information indicates whether to send a buffer status report. If the second indication information indicates not to send a buffer status report, then after receiving the first signaling, the terminal device may not send a buffer status report according to the second indication information; accordingly, the network device may not expect to receive the buffer status report. The second indication information can also be sent independently of the first signaling. For example, the second indication information can be sent after the first signaling.

[0150] In this implementation, the second indication information directly indicates not to send the buffer status report, thereby reducing the complexity of the terminal device in determining whether to send the buffer status report, thereby reducing the power consumption of the terminal device, and is particularly suitable for devices such as tags in the environmental Internet of Things.

[0151] Implementation method 2: When the signaling type of the first signaling is a preset type, the terminal device does not send a buffer status report; when the signaling type of the first signaling is not a preset type, the terminal device sends a buffer status report. In this method, when the signaling type of the first signaling is a preset type, the data size of the first data requested by the first signaling is preset. It can be understood that there is a corresponding relationship between the signaling type of the first signaling and the data size of the first data. When the network device sends the first signaling, it can determine the data size of the first data requested by the first signaling, and then the terminal device may not send a buffer status report. Among them, the core network device can indicate the signaling type of the first signaling to the network device, and the network device thereby determines the data size of the first data requested by the first signaling based on the signaling type of the first signaling.

[0152] For example, if the first signaling is an inventory signaling, the first data triggered by the first signaling to be reported by the terminal device is business data of an inventory service. This business data may be a tag identifier (ID) of the terminal device, and the size of the tag ID is fixed. The inventory signaling may include, but is not limited to, query, query adjustment, and repeated query. For another example, if the first signaling is a read signaling, the first data triggered by the first signaling to be reported by the terminal device is data stored in the terminal device. If the terminal device is a tag, the size range of the data stored in the tag is a preset value.

[0153] Optionally, after receiving the first signaling, the terminal device may also trigger a buffer status report.

[0154] Specifically, the buffer status report may be triggered by the MAC layer of the terminal device.

[0155] In one implementation, if the terminal device determines not to send a buffer status report, then the logical channel (LCH) of the buffer status report triggered by the terminal device has the lowest priority.

[0156] The buffer status report sent by the terminal device is carried by a logical channel, and the terminal device can multiplex the data of multiple logical channels into one medium access control (MAC) protocol data unit (PDU). Since one MAC PDU can multiplex the data of multiple logical channels, the terminal device can assign a priority to each logical channel. The data of the highest priority logical channel is first included in the MAC PDU, followed by the data of the second highest priority logical channel, until the data upper limit of the MAC PDU. The data of the low-priority logical channel may never be sent, so the terminal device sets the logical channel priority of the triggered buffer status report to the lowest priority, so that although the buffer status report is triggered, the buffer status report will not be sent.

[0157] In another implementation, if the terminal device determines not to send a buffer status report, the logical channel for the buffer status report triggered by the terminal device is a closed logical channel.

[0158] Since the data in the closed logical channel will not be multiplexed into the MAC PDU, although the terminal device triggers the buffer status report, the buffer status report will not be sent.

[0159] In this application, there is no limitation on the conditions under which a terminal device triggers a buffer status report. For example, the conditions for triggering a buffer status report may include one or more of the following:

[0160] 1. Data on the terminal device side is created from nothing. Here, data creation means that data on the terminal device side has been created from no data at all.

[0161] 2. New data arrives on the terminal device side (regardless of data priority). New data arrival means that new data arrives on the terminal device side.

[0162] Optionally, after a period of time after triggering the buffer status report, if the terminal device does not receive corresponding scheduling information, a random access process is initiated.

[0163] In the present application, the terminal device may not trigger a buffer status report, or not send a buffer status report, or cancel a triggered buffer status report. For example, the conditions for not triggering a buffer status report, not sending a buffer status report, or canceling a triggered buffer status report may include one or more of the following:

[0164] 1. The terminal device receives uplink scheduling information from the network side, which is used to schedule uplink resources.

[0165] 2. The terminal device receives an instruction from the network side not to report the buffer status report.

[0166] 3. The terminal device receives a first signaling (such as an inventory signaling or a read signaling) from the network side, and determines that it does not need to report a BSR based on the signaling type of the first signaling.

[0167] 4. The logical channel for the terminal device to upload the buffer status report is in the closed state.

[0168] It should be noted that when the terminal device determines not to send a buffer status report, it may not trigger the buffer status report.

[0169] Optionally, if the terminal device sends a buffer status report, the buffer status report indicates the data size of the first data.

[0170] It should be noted that when the terminal device determines not to send the buffer status report related to the first data, it does not send the buffer status report related to the first data.

[0171] In this application, when sending a buffer status report, the sending process of the buffer status report can be optimized to improve the sending efficiency of the buffer status report. Specifically, at least one of the following may exist:

[0172] 1. Only regular buffer status reporting is supported, not periodic buffer status reporting. This can reduce the power consumption of terminal devices and is more suitable for low-power scenarios such as ambient IoT.

[0173] 2. Only one format of BSR is supported, regardless of whether it is a long or short format. For example, existing short format BSRs or new length BSRs can be reused, which can reduce the format selection process of the terminal device and reduce the power consumption of the terminal device.

[0174] 3. The buffer status report belongs to only one logical channel group, or the buffer status report has only one logical channel. In this way, the buffer status report does not need to include a logical channel indication, which reduces resource overhead and improves resource utilization.

[0175] Step 502: The network device sends scheduling information to the terminal device, where the scheduling information is used to schedule resources for transmitting the first data.

[0176] Correspondingly, the terminal device receives the scheduling information.

[0177] In one implementation, if the first signaling is also used by the terminal device to determine not to send a buffer status report related to the first data, then the scheduling information is sent without receiving the buffer status report. In this case, the size of the resources indicated by the scheduling information is determined based on the preset data size of the first data. In this implementation, it can be understood that the network device sends the scheduling information before receiving the buffer status report related to the first data.

[0178] Optionally, in another implementation, if the first signaling is also used by the terminal device to determine whether to send a buffer status report related to the first data, then the scheduling information is sent when the buffer status report is received. In this case, the size of the resources indicated by the scheduling information is determined according to the data size indicated by the buffer status report.

[0179] Optionally, step 503: the terminal device sends the first data through the resources indicated by the scheduling information.

[0180] Correspondingly, the network device receives the first data through the resources indicated by the scheduling information.

[0181] It should be noted that step 503 is an optional step, and whether the terminal device sends the first data is not limited in this application. Optionally, if the network device receives the first data, it can also send the first data to the core network device.

[0182] In one implementation, the terminal device sends a second message to the network device through the resource, and the second message includes first data; wherein the data size indicated by the first indication information is equal to the data size of the first data, or the data size indicated by the first indication information is equal to the data size of the second message. The second message also includes at least one of a non-access layer message, an access layer message header, an access layer signaling, padding, a message prefix, a message suffix, a message preamble, a mid-amble, and a post-amble. The access layer message header, access layer signaling, padding, a message prefix, a message suffix, a message preamble, a mid-amble, and a post-amble can also be understood as air interface data, and the air interface data can be understood as message content that can be known by the network device. The access layer message header may include any access layer message header, such as at least one of an RRC header, a MAC header, an RLC header, and a PDCP header, etc., which is not limited in this application; the access layer signaling may include any access layer signaling, such as at least one of an RRC service data unit (SDU), a MAC control element (CE), and a MAC SDU, etc., which is not limited in this application.

[0183] The data size indicated by the first indication information may be equal to the second data size of the first data; or, the data size indicated by the first indication information may be equal to the data size of the second message, or the data size indicated by the first indication information is less than or equal to the sum of at least one of the data size of the access layer message header, the data size of the access layer signaling, and the data size of the padding and the data size of the first data, in which case the data size indicated by the first indication information is greater than the second data size. For example, the second message includes a non-access layer message (such as a NAS (non access stratum) message or an application layer message), and the second message may also include an access layer message header, such as an access layer message header including a MAC header and / or an RLC header and / or an AIoT access protocol layer header, or the second message includes at least one of an RLC header, a simplified MAC control element (CE), and a MAC header of a logical channel identify (LCID). Exemplarily, the access layer message header can be used to indicate the segmentation information of the message, such as indicating whether the second message is a segmented message, or indicating the message type of the second message.

[0184] The above method provides a process for not reporting a buffer status report. A network device or a terminal device can determine whether a terminal device sends a buffer status report through a first signaling. When a terminal device does not send a buffer status report, power consumption of the terminal device can be reduced, data transmission latency can be reduced, and resource utilization can be improved.

[0185] In combination with the above process, the above process is described below through specific embodiments.

[0186] Example 1:

[0187] In Example 1, the terminal device is used as the label, the network device is gNB, the core network device is AMF, and the first signaling is inventory signaling. Other situations can be deduced by analogy and will not be repeated here.

[0188] FIG6 is a flow chart of a data transmission method provided in an embodiment of the present application, wherein the method includes:

[0189] Step 601: The AMF sends inventory signaling to the gNB.

[0190] The inventory signaling is used to trigger the tag to report the first data, and the first data in this case may be the tag ID of the tag.

[0191] Optionally, the AMF may also send first indication information to the gNB, where the first indication information indicates the data size of the first data.

[0192] The first indication information indicates the data size of the first data. Therefore, when the gNB receives the inventory signaling, it can determine the data size of the first data. Therefore, when scheduling resources, it does not need to wait for the buffer status report of the tag. Therefore, scheduling information can be sent without receiving the buffer status report.

[0193] Step 602: The gNB sends a paging message to the tag.

[0194] The paging message includes inventory signaling, and the paging message is used to page the tag. The inventory signaling is also used by the tag to determine not to send a buffer status report related to the first data.

[0195] The gNB determines the data size of the first data based on the inventory signaling, and may determine that the tag does not need to report a buffer status report. The following implementation methods may be used:

[0196] In one implementation, the inventory signaling further includes second indication information, and the second indication information indicates not to report the buffer status report.

[0197] In another implementation, the paging message further includes second indication information, that is, the second indication information and the inventory signaling are two independent information elements.

[0198] By directly instructing not to send the buffer status report through the second indication information, the complexity of the tag in determining whether to send the buffer status report is reduced, thereby saving power consumption of the tag.

[0199] The gNB may also not carry the second indication information in the paging message, and this application does not limit this.

[0200] Step 603: The tag sends a random access request message to the gNB.

[0201] The random access request message may be a preamble or a 16-bit random number generated for a tag.

[0202] Alternatively, in various embodiments of the present application, the random access request message may also be one or more of the following: a random number or a temporary identifier or a random access identifier (for contention resolution), uplink data, a positioning signal, a reference signal, etc.

[0203] The random access request message can be used to (request / initiate) access / random access, or request / initiate access / random access to an access network device or an intermediate node or a second device or a network, where the intermediate node can be a network device or a terminal device.

[0204] Step 604: The gNB sends a random access response message to the tag.

[0205] If the tag sends a 16-bit random number to initiate random access, the random access response message may include the 16-bit random number.

[0206] Step 605: The tag sends message 3 to the gNB.

[0207] The message 3 is the message 3 in the random access process.

[0208] Step 606: The gNB sends message 4 to the tag.

[0209] This message 4 is the message 4 in the random access process, and may also be called a contention resolution message.

[0210] When the tag determines not to send the buffer status report related to the first data according to the inventory signaling, it no longer sends the buffer status report.

[0211] After the tag is randomly connected to the gNB, the following process is also included.

[0212] Step 607: The gNB sends scheduling information to the tag, which is used to schedule resources.

[0213] The size of the resources scheduled by the scheduling information is determined according to a preset data size of the first data.

[0214] Step 608: The tag sends the first data to the gNB according to the resources scheduled by the scheduling information.

[0215] Step 609: The gNB sends the first data to the AMF.

[0216] In the above process, when scheduling the tag to upload the first data, since the tag does not need to send a buffer status report, the power consumption of the terminal device can be reduced, the data transmission delay can be reduced, and the resource utilization rate can be improved.

[0217] Example 2:

[0218] In Example 2, the terminal device is used as the label, the network device is the gNB, the core network device is the AMF, and the first signaling is the inventory signaling and the reading signaling. Other situations can be deduced by analogy and will not be repeated here.

[0219] FIG7 is a flow chart of a data transmission method provided in an embodiment of the present application, wherein the method includes:

[0220] Step 701: The AMF sends an inventory signaling and a read command to the gNB.

[0221] The inventory signaling is used to trigger the tag to report data 1, where the data 1 may be the tag ID of the tag.

[0222] The read signaling is used to trigger the tag to report data 2, and the data 2 at this time may be the data stored in the tag.

[0223] In one implementation, data 1 includes one or more of the following: device storage area data (such as EPC, tag identification (tag ID), device identification (device ID). Data 2 may include one or more of the following: user data, encrypted data, keys, sensor data, written data, etc.), cached data, feedback (or response) messages for downlink data (or downlink signaling, downlink messages, etc.), data stored in registers or memories, specific sequences (such as positioning sequences, scrambling sequences, etc.), request messages (such as authentication requests, registration requests, authentication requests, etc.), etc.

[0224] Optionally, in one implementation, the AMF may also send first indication information to the gNB, where the first indication information indicates the total data size of data 1 and data 2.

[0225] In another implementation, the AMF may also send information 1 and information 2 to the gNB, where information 1 indicates the data size of data 1 and information 2 indicates the data size of data 2.

[0226] Step 702: The gNB sends a paging message to the tag.

[0227] The paging message includes inventory signaling, and is used to page the tag. The inventory signaling is also used by the tag to determine not to send a buffer status report related to data 1.

[0228] The gNB determines the size of Data 1 based on the inventory signaling and can therefore determine that the tag does not need to report a buffer status report. The following implementations are possible:

[0229] The inventory signaling also includes second indication information, which indicates not to submit a buffer status report. Alternatively, the second indication information and the inventory signaling are two independent information elements, both located in and carried by the paging message.

[0230] The tag receives the inventory signaling in the paging message and may determine not to send a buffer status report related to data 1 according to the second indication information.

[0231] Optionally, the paging message may include a read command.

[0232] Step 703: The tag sends a random access request message to the gNB.

[0233] The random access request message may be a preamble.

[0234] Step 704: The gNB sends a random access response message to the tag.

[0235] If the paging message does not include a read command, the random access response message may include a read command.

[0236] The read command may include the second indication information, or the random access response message may include the second indication information.

[0237] The tag receives the read command and may determine not to send a buffer status report related to data 2 according to the second indication information.

[0238] Step 705: The tag sends message 3 to the gNB.

[0239] Step 706: The gNB sends message 4 to the tag.

[0240] After the tag is randomly connected to the gNB, the following process is also included.

[0241] Step 707: The gNB sends scheduling information to the tag, which is used to schedule resources.

[0242] The size of the resources scheduled by the scheduling information is determined according to the preset data size of data 1 and the preset data size of data 2.

[0243] Step 708: The tag sends data 1 and data 2 to the gNB according to the resources scheduled by the scheduling information.

[0244] The tag can send data 1 and data 2 to the gNB via two messages respectively, or send data 1 and data 2 to the gNB via one message.

[0245] Step 709: gNB sends data 1 and data 2 to AMF.

[0246] The above embodiments are merely examples. There are other implementations of the first signaling, which will not be described one by one here.

[0247] The present application also provides a method by which, when the label does not report the BSR, the network device can determine the data size of the data to be transmitted by the terminal device through the core network device, thereby allocating corresponding resources to the label, which will be described in detail below.

[0248] FIG8 is a flow chart of a data transmission method according to an embodiment of the present application, wherein the method includes:

[0249] Step 801: The network device sends a paging message to the terminal device, where the paging message is used to page the terminal device.

[0250] Correspondingly, the terminal device receives the paging message from the network device.

[0251] In one implementation, after receiving a paging message, the terminal device determines that the paging message is a message for paging itself, and may send a random access request message to the network device, thereby initiating a random access process.

[0252] In this application, a paging message may also be described as an initial trigger message, a trigger message, a downlink trigger message, a paging-like message, a select signaling, or a reader-to-device trigger message. A paging message can be used to instruct a terminal device to access a network, a network device, a terminal device (in the case of a relay node), send data, initiate random access, or wait for an access opportunity.

[0253] In one implementation, the terminal device may be a tag in the environmental Internet of Things, or a communication device having a tag function in the environmental Internet of Things.

[0254] Step 801 is an optional step, and the network device may not send a paging message, which is not limited in this application.

[0255] Step 802: The network device sends scheduling information to the terminal device, where the scheduling information is used to schedule resources for transmitting the first data.

[0256] Correspondingly, the terminal device receives the scheduling information.

[0257] In one implementation, the scheduling information is sent before a first buffer status report related to the first data is received. The first buffer status report related to the first data can be used to indicate the data size of the first data. In this implementation, it can be understood that the network device sends the scheduling information before receiving the first buffer status report related to the first data.

[0258] In one implementation, before a network device sends a paging message to a terminal device, it receives first information from a core network device. The network device determines resources for transmitting the first data based on the data size indicated by the first information. By indicating the data size in the first information, the network device can directly determine the size of the resources for transmitting the first data based on the first information, eliminating the need to wait for a buffer status report from the terminal device. This allows the network device to send scheduling information without receiving a buffer status report from the terminal device, thereby reducing resource scheduling latency.

[0259] Assume that the data size of the first data to be transmitted by the terminal device is the second data size, the data size indicated by the first information is the first data size, and the first data size can be greater than or equal to the second data size. For example, the second message also includes at least one of a non-access layer message, an access layer message header, access layer signaling, padding, a message prefix, a message suffix, a message preamble, a midamble, and a postamble. The access layer message header, access layer signaling, padding, a message prefix, a message suffix, a message preamble, a midamble, and a postamble can also be understood as air interface data, and the air interface data can be understood as the message content known to the network device. The access layer message header can include any access layer message header, such as at least one of an RRC header, a MAC header, an RLC header, and a PDCP header, etc., which is not limited in this application; the access layer signaling can include any access layer signaling, such as at least one of an RRC SDU, a MAC CE, and a MAC SDU, etc., which is not limited in this application.

[0260] The data size indicated by the first information may be equal to the second data size of the first data; or, the data size indicated by the first information may be equal to the data size of the second message, or the data size indicated by the first information is less than or equal to the sum of at least one of the data size of the access layer message header, the data size of the access layer signaling, and the data size of the padding and the data size of the first data, in which case the data size indicated by the first information is greater than the second data size. For example, the second message includes a non-access layer message (such as a NAS (non access stratum) message or an application layer message), and the second message may also include an access layer message header, such as an access layer message header including a MAC header and / or an RLC header and / or an AIoT access protocol layer header, or the second message includes at least one of an RLC header, a simplified MAC control element (CE), and a MAC header of a logical channel identify (LCID). Exemplarily, the access layer message header can be used to indicate message segmentation information, such as indicating whether the second message is a segmented message, or indicating the message type of the second message.

[0261] Optionally, the network device may also indicate whether the first data size refers to the data size of the second message, or refers to the data size of the first data included in the second message.

[0262] If the first data size refers to the data size of the second message, then the data size of the second message is less than or equal to the first data size, and the data size of the first data in the second message is less than the first data size. If the first data size refers to the data size of the first data included in the second message, then the data size of the second message may be greater than the first data size, and the data size of the first data in the second message may be equal to the first data size.

[0263] This application does not limit how the first information indicates the data size of the first data. For example, in implementation mode 1, the first information directly indicates the data size of the first data, for example, the first information includes the data size of the first data.

[0264] In a second implementation, the first information indirectly indicates the size of the first data. For example, the first information is second data sent to a terminal device, and the sizes of the second data and the first data correspond to each other. The network device can determine the size of the first data based on this correspondence. This correspondence can be preset or preconfigured, or determined in other ways, and is not limited by this application.

[0265] Implementation method three, the first information indirectly indicates the data size of the first data, for example, the first information indicates the service corresponding to the first data, and there is a corresponding relationship between the service corresponding to the first data and the data size of the first data. The network device can determine the data size of the first data based on the above-mentioned corresponding relationship. The above-mentioned corresponding relationship can be preset or pre-configured, or determined according to other methods, which is not limited by this application. For example, the first information indicates that the first data corresponds to an inventory service, and the first data is the service data of the inventory service. The service data can be a tag identification (identity, ID) of the terminal device. The size of the tag ID is fixed, so the network device can determine the data size of the first data based on the inventory service.

[0266] In the present application, the network device may also send a first signaling to the terminal device, the first signaling instructing the terminal device to report the first data or the first signaling triggering the terminal device to report the first data. The first signaling may be generated by the network device; or the first signaling may be sent by the core network device to the network device, for example, the core network device may be an AMF. When the network device is replaced with a reader / writer, the first signaling may be sent by the core network device to the network device, and the network device then forwards the first signaling to the reader / writer, and finally the reader / writer sends the first signaling to the terminal device. Alternatively, the first signaling is sent by the core network device to the network device, and the network device transparently transmits the first signaling to the terminal device.

[0267] In this application, the core network equipment may include but is not limited to mobility management network elements, positioning management network elements, tag management network elements and other network elements, without limitation. The mobility management network element may be an access and mobility management function (AMF). The positioning management network element may be a location management function (LMF). The tag management network element may be a tag management function (TMF) or an ambient IoT function (AIoTF) or an ambient IoT management function (AIoTMF).

[0268] In one implementation, the resource may be determined based on the data size indicated by the first information. For example, the size of the resource is determined based on the data size indicated by the first information. For example, the size of the data that can be transmitted in the resource is equal to the data size indicated by the first information. Alternatively, the size of the data that can be transmitted in the resource is greater than the data size indicated by the first information.

[0269] For example, the data size of the first data to be transmitted by the terminal device is the second data size, the first data is carried by the second message, and the second message includes the first data and a message header. If the data size indicated by the first information refers to the data size of the second message, the size of the data that can be transmitted in the resource can be equal to the data size indicated by the first information. If the first data size refers to the data size of the first data included in the second message, the size of the data that can be transmitted in the resource can be greater than the data size indicated by the first information, for example, the size of the data that can be transmitted in the resource is equal to the sum of the second data size and the data size of the message header.

[0270] This application does not limit how the network device sends the first signaling. For example, the first signaling is located in a paging message, a random access response message, or a first message; wherein the first message is a message sent after the terminal device completes random access.

[0271] The first signaling may also have other functions. For example, in one implementation, the first signaling is used to trigger an inventory process, and the first data is business data of the inventory service; in another implementation, the first signaling is used to trigger a read process, and the first data is data stored in the terminal device.

[0272] In the present application, the first signaling may also be used by a terminal device to determine whether to send a buffer status report related to the first data, where the buffer status report is used to indicate the data size of the first data. For example, in implementation method one, the first signaling includes second information, where the second information indicates whether to send a first buffer status report related to the first data. If the second information indicates not to send the first buffer status report related to the first data, then after receiving the first signaling, the terminal device may not send the first buffer status report based on the second information; accordingly, the network device may not expect to receive the first buffer status report.

[0273] The second information may also be sent independently of the first signaling, for example, the second information may be sent after the first signaling, or the second information may be located in a paging message or a random access response message.

[0274] Implementation method 2: When the signaling type of the first signaling is a preset type, the terminal device does not send a first buffer status report related to the first data; when the signaling type of the first signaling is not a preset type, the terminal device sends a first buffer status report. In this method, when the signaling type of the first signaling is a preset type, the data size of the first data requested by the first signaling is preset. It can be understood that there is a corresponding relationship between the signaling type of the first signaling and the data size of the first data. When sending the first signaling, the network device can determine the data size of the first data requested by the first signaling, and the terminal device can then not send the first buffer status report.

[0275] The core network device may indicate the signaling type of the first signaling to the network device, and the network device may determine the data size of the first data requested by the first signaling according to the signaling type of the first signaling.

[0276] Optionally, after receiving the first signaling, the terminal device may further trigger a first buffer status report. The conditions under which the terminal device triggers the first buffer status report and how the first buffer status report is triggered are not limited. For example, reference may be made to the description in step 501, which will not be repeated here. If the terminal device determines not to send the first buffer status report, then although the terminal device triggers the first buffer status report, it does not send the first buffer status report. For details, reference may be made to the description in step 501, which will not be repeated here.

[0277] In one implementation, the scheduling information is sent without receiving the first buffer status report. Alternatively, it can be understood that the network device can send the scheduling information even if the terminal device does not send the first buffer status report related to the first data. In this case, the resources indicated by the scheduling information are determined based on the size of the data indicated by the first information. For example, the size of the resources is determined based on the size of the data indicated by the first information.

[0278] In another implementation, if the terminal device sends a first buffer status report related to the first data, then the size of the resources indicated by the scheduling information is determined according to the size of the data indicated in the first buffer status report.

[0279] Optionally, step 803: the terminal device sends the first data through the resources indicated by the scheduling information.

[0280] Correspondingly, the network device receives the first data through the resources indicated by the scheduling information.

[0281] It should be noted that step 803 is an optional step, and whether the terminal device sends the first data is not limited in this application. Optionally, if the network device receives the first data, it can also send the first data to the core network device.

[0282] In one implementation, the terminal device sends a second message to the network device through the resource, and the second message includes first data; wherein the data size indicated by the first information is equal to the data size of the first data, or the data size indicated by the first information is equal to the data size of the second message, or the data size indicated by the first information is equal to the sum of at least one of the data size of the access layer message header and the data size of the access layer signaling and the data size of the first data.

[0283] In one implementation, the network device may further send third information to the terminal device, instructing the terminal device to submit a second buffer status report before data transmission. The third information is sent after the terminal device completes random access. "Data transmission" here can be understood as the terminal device transmitting other data to the network device after transmitting the first data.

[0284] The third information may be sent together with the first data or separately from the first data, and this application does not limit this. The third information may explicitly instruct the terminal device to submit a second buffer status report before data transmission; the third information may also implicitly instruct the terminal device to submit a second buffer status report before data transmission. For example, the third information may indicate a resource configuration for transmitting the second buffer status report, and the terminal device may submit the second buffer status report based on the resource configuration. The terminal device may submit the second buffer status report only after receiving the third information.

[0285] The above method provides a process for not reporting a buffer status report. The network device can determine the data size of the first data based on the first information, and thus can schedule resources based on the data size without waiting for the buffer status report from the terminal device. In the event that the terminal device does not send a buffer status report, the network device will schedule resources for the terminal device, which can reduce the power consumption of the terminal device, reduce data transmission delay, and improve resource utilization. Furthermore, the network device can also directly indicate not to send a buffer status report through the second information, reducing the complexity of the terminal device in determining whether to send a buffer status report, which can save the power consumption of the terminal device. This is particularly suitable for devices such as tags in the environmental Internet of Things.

[0286] In conjunction with the previous process, the following example describes the process using the terminal device as the tag, the network device as the gNB, and the core network device as the AMF. In this process, the AMF directly indicates to the gNB the data size that the tag needs to report. This allows the gNB to schedule resources for the tag without receiving a buffer status report. This is described in detail below.

[0287] FIG9 is a flow chart of a data transmission method according to an embodiment of the present application, wherein the method includes:

[0288] Step 901: The AMF sends an inventory signaling, a read command, and a first message to the gNB.

[0289] The inventory signaling is used to trigger the tag to report data 1, where the data 1 may be the tag ID of the tag.

[0290] The read signaling is used to trigger the tag to report data 2, and the data 2 at this time may be the data stored in the tag.

[0291] The first information may indicate the total data size of the data 1 and the data 2 , or the first information may indicate the data size of the data 1 and the data size of the data 2 respectively.

[0292] Step 902: The gNB sends a paging message to the tag.

[0293] The paging message includes inventory signaling, and the paging message is used to page the tag.

[0294] The paging message also includes second information, and the second information indicates not to report the buffer status report.

[0295] The tag receives the inventory signaling in the paging message and may determine not to send a buffer status report related to data 1 according to the second information.

[0296] Optionally, the paging message may also include a read command.

[0297] Step 903: The tag sends a random access request message to the gNB.

[0298] The random access request message may be a preamble.

[0299] Step 904: The gNB sends a random access response message to the tag.

[0300] If the paging message does not include a read command, the random access response message may include a read command.

[0301] The random access response message may include the second information.

[0302] The tag receives the read command and may determine not to send a buffer status report related to data 2 according to the second information.

[0303] Step 905: The tag sends message 3 to the gNB.

[0304] Step 906: The gNB sends message 4 to the tag.

[0305] After the tag is randomly connected to the gNB, the following process is also included.

[0306] Step 907: The gNB sends scheduling information to the tag, which is used to schedule resources.

[0307] The size of the resources scheduled by the scheduling information is determined according to the preset data size of data 1 and the preset data size of data 2.

[0308] Step 908: The tag sends data 1 and data 2 to the gNB according to the resources scheduled by the scheduling information.

[0309] The tag can send data 1 and data 2 to the gNB via two messages respectively, or send data 1 and data 2 to the gNB via one message.

[0310] Step 909: gNB sends data 1 and data 2 to AMF.

[0311] In the above process, the gNB can determine the data size of Data 1 and Data 2 based on the first information, and thus schedule resources for Data 1 and Data 2 without waiting for a buffer status report from the tag. If the tag does not send a buffer status report, the gNB can schedule resources for the tag, reducing tag power consumption, data transmission latency, and improving resource utilization.

[0312] The following process uses the interaction between a first device and a second device as an example. The second device may be a terminal device, an access network device, or a network device, or may be a module (such as a chip or modem) within the terminal device, access network device, or network device; the first device may be a tag (such as an AIoT tag) or a terminal device, or may be a module (such as a chip or modem) within a tag or terminal device.

[0313] FIG10 is a flow chart of a data transmission method provided in an embodiment of the present application, wherein the method includes:

[0314] Step 1001: A second device sends a paging message to a first device, where the paging message is used to page the first device.

[0315] Accordingly, the first device receives the paging message from the second device.

[0316] In one implementation, after receiving a paging message, the first device determines that the paging message is a message for paging itself, and may send a random access request message to the second device, thereby initiating a random access process.

[0317] In this application, a paging message may also be described as an initial trigger message, a trigger message, a downlink trigger message, a paging-like message, a select signaling, or a reader-to-device trigger message. A paging message can be used to instruct a terminal device to access a network, a network device, a terminal device (in the case of a relay node), send data, initiate random access, or wait for an access opportunity.

[0318] Step 1001 is an optional step, and the second device may not send a paging message, which is not limited in this application.

[0319] Optionally, the second device may further send a first signaling to the first device. In one implementation, the first signaling is located in a paging message, a random access response message, a contention resolution success message, or a first message, or the first signaling is a paging message, a random access response message, a contention resolution success message, or a first message; wherein the first message is a message received by the first device after accessing the second device, for example, the first message is from the second device or a core network device.

[0320] In one implementation, the first device may be a tag in the environmental Internet of Things, or a communication device having a tag function in the environmental Internet of Things.

[0321] In this embodiment, the first signaling instructs the first device to report the first data, or the first signaling triggers the first device to report the first data. The first data can be understood as buffered data to be sent by the first device, or the first data can be data to be transmitted by the first device, or the first data can be data requested by the second device from the first device.

[0322] The first signaling can be generated by the second device; or the first signaling can be sent by a core network device to the second device. For example, the core network device can be an AMF or AIoTF. If the second device is a reader / writer, the first signaling can be sent by the core network device to a network device, which then forwards the first signaling to the second device, which ultimately sends the first signaling to the first device. Alternatively, the first signaling can be sent by the core network device to the second device, which then transparently transmits the first signaling to the first device.

[0323] In this embodiment, before sending a paging message to the first device, the second device may also receive first information from a core network device, where the first information indicates a first data size. The second device determines resources to be scheduled for the first device based on the first data size indicated by the first information. The first information indicating the first data size allows the second device to directly determine the first resource based on the first data size, eliminating the need to wait for a buffer status report. This allows the second device to schedule resources for the first device, such as sending scheduling information, without receiving a buffer status report from the first device, thereby reducing resource scheduling latency.

[0324] This application does not limit how the first information indicates the first data size. For example, in implementation mode 1, the first information directly indicates the first data size, for example, the first information includes the first data size.

[0325] In a second implementation, the first information indirectly indicates the size of the first data. For example, the first information is second data sent to the first device, and there is a corresponding relationship between the size of the second data and the size of the first data. The second device can determine the size of the first data based on this corresponding relationship. This corresponding relationship can be preset or preconfigured, or determined according to other methods, and this application does not limit it.

[0326] Implementation method three, the first information indirectly indicates the first data size, for example, the first information indicates the first business, and there is a correspondence between the first business and the first data size. The second device can determine the first data size based on the above correspondence. The above correspondence can be preset or preconfigured, or determined according to other methods, which is not limited by this application. For example, the first business indicated by the first information is an inventory business, and the business data of the inventory business can be the tag identification (identity, ID) of the first device. The data size of the tag ID is fixed, so the second device can determine the first data size based on the inventory business.

[0327] Assuming that the data size of the first data to be transmitted by the first device is the second data size, the first data size can be greater than or equal to the second data size. For example, the first data is carried by a second message, the second message includes the first data, and the second message also includes at least one of a non-access layer message, an access layer message header, access layer signaling, padding, a message prefix, a message suffix, a message preamble, a midamble, and a postamble. The access layer message header, access layer signaling, padding, a message prefix, a message suffix, a message preamble, a midamble, and a postamble can also be understood as air interface data, and the air interface data can be understood as message content that can be known by the network device. The access layer message header can include any access layer message header, such as at least one of an RRC header, a MAC header, an RLC header, and a PDCP header, and this application is not limited thereto; the access layer signaling can include any access layer signaling, such as at least one of an RRC SDU, a MAC CE, and a MAC SDU, and this application is not limited thereto.

[0328] The data size indicated by the first information may be equal to the second data size of the first data; or, the data size indicated by the first information may be equal to the data size of the second message, or the data size indicated by the first information may be less than or equal to the sum of at least one of the data size of the access layer message header, the data size of the access layer signaling, and the data size of the padding and the data size of the first data, in which case the data size indicated by the first information is greater than the second data size. For example, the second message includes a non-access layer message (such as a NAS (non access stratum) message or an application layer message), and the second message may also include an access layer message header, such as an access layer message header including a MAC header and / or an RLC header and / or an AIoT access protocol layer header, or the second message includes at least one of an RLC header, a simplified MAC control element (CE), and a MAC header of a logical channel identify (LCID). Optionally, the second message may also include padding. Exemplarily, the access layer message header may be used to indicate message segmentation information, such as indicating whether the second message is a segmented message, or indicating the message type of the second message.

[0329] Optionally, the second device may also indicate whether the first data size refers to the data size of the second message transmitted by the first device or the data size of the first data included in the second message. If the second device does not indicate the above information, it can be agreed that the first data size refers to the data size of the second message transmitted by the first device or the data size of the first data included in the second message.

[0330] If the first data size refers to the data size of the second message transmitted by the first device, then the data size of the second message transmitted by the first device is less than or equal to the first data size, and the data size of the first data in the second message is less than the first data size. If the first data size refers to the data size of the first data included in the second message transmitted by the first device, then the data size of the second message transmitted by the first device may be greater than the first data size, and the data size of the first data in the second message may be equal to the first data size.

[0331] In the present application, the first signaling can also be used by the first device to determine whether to send a first buffer status report. The first device can determine whether to send a first buffer status report based on the first signaling. The first buffer status report is used to indicate a fourth data size. The fourth data size can be the data size of the message or data to be transmitted by the first device.

[0332] For example, in implementation method 1, the first signaling includes second information, where the second information indicates whether to send a first buffer status report. If the second information indicates not to send the first buffer status report, then after receiving the first signaling, the first device may not send the first buffer status report based on the second information; accordingly, the second device may not expect to receive the first buffer status report. The second information may also be sent independently of the first signaling, for example, after the first signaling.

[0333] In this implementation, the second information directly indicates not to send the first buffer status report, thereby reducing the complexity of the first device in determining whether to send the first buffer status report, thereby reducing the power consumption of the first device, and is particularly suitable for devices such as tags in the environmental Internet of Things.

[0334] Implementation method two: when the signaling type of the first signaling is a preset type, or the first signaling is a preset signaling, the first device does not send a first buffer status report; when the signaling type of the first signaling is not a preset type, or the first signaling is not a preset signaling, the first device sends a first buffer status report.

[0335] When the second device is a network device, the core network device can indicate the signaling type of the first signaling to the network device, and the network device determines the data size of the first data requested by the first signaling based on the signaling type of the first signaling.

[0336] In this implementation, the signaling type of the first signaling is a preset type, or when the first signaling is a preset signaling, the third data size of the data requested by the first signaling can be preset. It can be understood that there is a corresponding relationship between the signaling type of the first signaling or the first signaling and the third data size. When the second device sends the first signaling, it can determine that the data size of the data requested by the first signaling is the third data size. If the first device does not send the first buffer status report according to the first signaling, the second device may not expect to receive the first buffer status report accordingly. At this time, the second device can schedule resources for the first device based on the third data size, and can no longer wait for the first buffer status report of the first device, so as to schedule resources for the first device without receiving the first buffer status report of the first device, such as sending scheduling information, which can reduce the delay of resource scheduling.

[0337] For example, if the first signaling is an inventory signaling, the first data triggered by the first signaling to be reported by the first device is business data of an inventory service. This business data may be a tag identifier (ID) of the first device, and the data size of the tag ID is fixed. Inventory signaling may include, but is not limited to, query, query adjustment, and repeated query. For another example, if the first signaling is a read signaling, the first data triggered by the first signaling to be reported by the first device is data stored by the first device. If the first device is a tag, the size range of the data stored in the tag is a preset value.

[0338] Optionally, the third data size may refer to the data size of the second message transmitted by the first device, or may refer to the data size of the first data included in the second message. If the third data size refers to the data size of the second message transmitted by the first device, then the data size of the second message transmitted by the first device is less than or equal to the third data size, and the data size of the first data in the second message is less than the third data size. If the third data size refers to the data size of the first data included in the second message transmitted by the first device, then the data size of the second message transmitted by the first device may be greater than the third data size, and the data size of the first data in the second message may be equal to the third data size.

[0339] The first data size and the third data size may be the same or different. If the first device determines the first data size based on the first indication information and determines the third data size based on the first signaling, then the resources scheduled for the first device may be determined based on the first data size or the third data size. This application does not limit whether resources are scheduled for the first device based on the first data size or the third data size.

[0340] Optionally, after receiving the first signaling, the first device may also trigger a buffer status report.

[0341] Specifically, the buffer status report may be triggered by the MAC layer of the first device.

[0342] In one implementation, if the first device determines not to send the first buffer status report, then the logical channel (LCH) of the first buffer status report triggered by the first device has the lowest priority.

[0343] The first buffer status report sent by the first device is carried by a logical channel, and the first device can multiplex the data of multiple logical channels into one medium access control (MAC) protocol data unit (PDU). Since one MAC PDU can multiplex the data of multiple logical channels, the first device can assign a priority to each logical channel. The data of the highest priority logical channel is first included in the MAC PDU, followed by the data of the second highest priority logical channel, until the data upper limit of the MAC PDU. The data of the low priority logical channel may never be sent, so the first device sets the logical channel priority of the triggered first buffer status report to the lowest priority, so that although the first buffer status report is triggered, the first buffer status report will not be sent.

[0344] In another implementation, if the first device determines not to send the first buffer status report, then the logical channel of the first buffer status report triggered by the first device is a closed logical channel.

[0345] Since the data in the closed logical channel will not be multiplexed into the MAC PDU, although the first device triggers the first buffer status report, the first buffer status report will not be sent.

[0346] In the present application, there is no limitation on the conditions under which the first device triggers the buffer status report. For example, please refer to the description in step 501, which will not be repeated here.

[0347] Optionally, after a period of time after the first trigger buffer status report is issued, if the first device does not receive corresponding scheduling information, a random access process is initiated.

[0348] In the present application, the first device may not trigger the first buffer status report, or not send the first buffer status report, or cancel the triggered first buffer status report. For example, the conditions for not triggering the first buffer status report, not sending the first buffer status report, or canceling the triggered first buffer status report are not limited. For example, refer to the description in step 501, which will not be repeated here.

[0349] It should be noted that when the first device determines not to send the first buffer status report, the first buffer status report may not be triggered.

[0350] Optionally, if the first device sends a first buffer status report, the first buffer status report indicates a fourth data size.

[0351] It should be noted that when the first device determines not to send the buffer status report related to the first data, it does not send the buffer status report related to the first data.

[0352] In the present application, when sending the first buffer status report, the sending process of the first buffer status report can be optimized to improve the sending efficiency of the first buffer status report. Specifically, at least one of the following may exist:

[0353] 1. Only regular buffer status reporting is supported, not periodic buffer status reporting. This can reduce the power consumption of the first device and is more suitable for low-power scenarios such as ambient IoT.

[0354] 2. Only one format of BSR is supported, regardless of whether it is a long or short format. For example, existing short format BSRs or BSRs of a new length can be reused. This can reduce the format selection process of the first device and reduce power consumption of the first device.

[0355] 3. The buffer status report belongs to only one logical channel group, or the buffer status report has only one logical channel. In this way, the buffer status report does not need to include a logical channel indication, which reduces resource overhead and improves resource utilization.

[0356] Step 1002: The second device sends configuration information to the first device, where the configuration information is used to indicate a first resource or a first transmission block size.

[0357] Accordingly, the first device receives the configuration information.

[0358] Configuration information may also be referred to as scheduling information, parameter information, indication information, etc., and this application does not limit the specific name of the configuration information. The configuration information may be carried in at least one of the first signaling, the first message, the random access response message, and the contention resolution success message.

[0359] The configuration information is used to indicate the first resource, and can also be understood as the configuration information being used to schedule, configure, indicate, determine, or associate the first resource. The first transmission block size is used to indicate the size of data sent by the first device. For example, the data size of the second message is determined based on the first transmission block size.

[0360] In one implementation, the first resource may be determined based on the first data size. For example, the size of the first resource is determined based on the first data size. For example, the size of data that can be transmitted in the first resource is equal to the first data size. Alternatively, the size of data that can be transmitted in the first resource is greater than the first data size.

[0361] For example, the data size of first data to be transmitted by a first device is the second data size, the first data is carried by a second message, and the second message includes the first data and a message header. If the first data size refers to the data size of the second message transmitted by the first device, the size of the data that can be transmitted in the first resource can be equal to the first data size. If the first data size refers to the data size of the first data included in the second message transmitted by the first device, the size of the data that can be transmitted in the first resource can be greater than the first data size, for example, the size of the data that can be transmitted in the first resource is equal to the sum of the second data size and the data size of the message header.

[0362] In another implementation, the first resource may be determined based on a third data size corresponding to the signaling type of the first signaling, for example, the size of the first resource is determined based on the third data size. For example, the size of the data that can be transmitted in the first resource is greater than or equal to the third data size.

[0363] For example, if the data size of first data to be transmitted by the first device is the second data size, the first data is carried by a second message, and the second message includes the first data and a message header. If the third data size refers to the data size of the second message, the size of the data that can be transmitted in the first resource can be equal to the third data size. If the third data size refers to the data size of the first data included in the second message, the size of the data that can be transmitted in the first resource can be greater than the third data size. For example, the size of the data that can be transmitted in the first resource is equal to the sum of the second data size and the data size of the message header.

[0364] In one implementation, if the first device determines not to send a buffer status report related to the first data based on the first signaling, the configuration information is sent without receiving the buffer status report. In this case, the size of the first resource indicated by the configuration information is determined based on the size of the first data. In this implementation, it can be understood that the second device sends the configuration information without receiving the buffer status report related to the first data.

[0365] Optionally, in another implementation, the first device determines to send a buffer status report related to the first data based on the first signaling, and the configuration information is sent when the buffer status report is received. In this case, the size of the first resource indicated by the configuration information is determined according to the data size indicated by the buffer status report.

[0366] Optionally, step 1003: the first device sends a second message through the first resource, where the second message includes the first data.

[0367] Correspondingly, the second device receives the second message through the first resource.

[0368] The second message can also be understood as data, signaling, information, etc.

[0369] In the case where the size of the first data to be transmitted by the first device is smaller than the first transmission block size, the second message further includes a padding portion so that the size of the second message can be equal to the first transmission block size. In another implementation, the size of the second message is smaller than or equal to the first transmission block size.

[0370] As previously described, the data size of the first data is the second data size, and the first data size may be greater than or equal to the second data size. For example, the second message includes the first data and a message header, and the first data size may be equal to the second data size of the first data; or, the first data size may be equal to the data size of the second message, that is, the first data size is equal to the sum of the second data size and the data size of the message header, in which case the first data size is greater than the second data size. For example, the second message is a non-access stratum (NAS) message, and the message header of the NAS message includes a MAC header and / or an RLC header, or the message header of the NAS message includes at least one of an RLC header, a simplified MAC control element (CE), and a MAC header following a logical channel identify (LCID).

[0371] In one implementation, the second device may further send third information to the first device, the third information instructing the first device to submit a second buffer status report before data transmission. The third information is sent after the first device completes random access. "Data transmission" here can be understood as the transmission of additional data (e.g., third data or a third message) by the first device to the second device after the first device transmits the second message. The second buffer status report indicates a fifth data size, which is the size of the third data or third message to be transmitted by the first device.

[0372] The third information may be sent together with the first data or separately from the first data, and this application does not limit this. The third information may explicitly instruct the first device to report the second buffer status report before data transmission; the third information may implicitly instruct the first device to report the second buffer status report before data transmission. For example, the third information indicates a resource configuration for transmitting the second buffer status report, and the first device may send the second buffer status report based on the resource configuration. The first device may send the second buffer status report only after receiving the third information.

[0373] It should be noted that step 1003 is an optional step, and whether the first device sends the second message is not limited in this application. Optionally, if the second device receives the second message, it can also forward the second message to the core network device.

[0374] The above method provides a process for not reporting a buffer status report. The second device or the first device can determine whether the first device has sent a buffer status report through the first signaling. When the first device does not send a buffer status report, power consumption of the first device can be reduced, data transmission latency can be reduced, and resource utilization can be improved.

[0375] It is understandable that in order to implement the functions in the above embodiments, the network devices, terminal devices, and core network devices include hardware structures and / or software modules corresponding to the execution of each function. It should be readily apparent to those skilled in the art that, in combination with the units and method steps of each example described in the embodiments disclosed in this application, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in hardware or in a manner driven by computer software depends on the specific application scenario and design constraints of the technical solution.

[0376] The following is a schematic diagram of the structure of possible communication devices provided in the embodiments of the present application. These communication devices can be used to implement the functions of the network device, terminal device, or core network device in the above method embodiments, and thus can also achieve the beneficial effects of the above method embodiments.

[0377] As shown in Figure 11, a communication device 1100 includes a processing unit 1110 and a communication unit 1120. The communication device 1100 is used to implement the functions of the terminal device, network device, or core network device in the above-mentioned various method embodiments.

[0378] When the communication device 1100 is used to implement the functions of the network device in the method embodiment shown in FIG5 :

[0379] a processing unit, configured to send a first signaling to a terminal device through a communication unit; the first signaling instructs the terminal device to report first data, the first signaling being used by the terminal device to determine not to send a buffer status report related to the first data;

[0380] A processing unit is used to send scheduling information to the terminal device through a communication unit, where the scheduling information is used to schedule resources for transmitting the first data, and the size of the resources is determined according to a preset data size of the first data.

[0381] In a possible implementation manner, the scheduling information is sent without receiving the buffer status report.

[0382] In a possible implementation, the communication unit is further used to: receive the first signaling and first indication information from a core network device, where the first indication information indicates a data size of the first data.

[0383] In a possible implementation, the first signaling is an inventory signaling, and the first data is service data of an inventory service.

[0384] In a possible implementation, the first signaling is a read signaling, and the first data is data stored in the terminal device.

[0385] In a possible implementation, the first signaling is located in a paging message, a random access response message, or a first message; wherein the first message is a message sent after the random access of the terminal device is completed.

[0386] In a possible implementation manner, the first signaling further includes second indication information, where the second indication information indicates not to send the buffer status report.

[0387] In a possible implementation, the terminal device is a tag in an environmental Internet of Things.

[0388] When the communication device 1100 is used to implement the functions of the terminal device in the method embodiment shown in FIG5 :

[0389] A communication unit, configured to receive a first signaling from a network device, where the first signaling instructs a terminal device to report first data;

[0390] a processing unit, configured to determine, according to the first signaling, not to send a buffer status report related to the first data;

[0391] The communication unit is used to receive scheduling information from a network device, where the scheduling information is used to schedule resources, and the resources are used to transmit the first data; the size of the resources is determined according to a preset data size of the first data.

[0392] In a possible implementation, the processing unit is further configured to: trigger the buffer status report; wherein the logical channel for triggering the buffer status report has the lowest priority, or the logical channel for triggering the buffer status report is a closed logical channel.

[0393] In a possible implementation manner, the processing unit is configured to: when the signaling type of the first signaling is a preset type, determine not to send a buffer status report.

[0394] In one possible implementation, the first signaling also includes second indication information, and the second indication information indicates not to send the buffer status report; the determining not to send the buffer status report related to the first data based on the first signaling includes: determining not to send the buffer status report based on the second indication information.

[0395] In a possible implementation, the first signaling is an inventory signaling, and the first data is service data of an inventory service.

[0396] In a possible implementation, the first signaling is a read signaling, and the first data is data stored in the terminal device.

[0397] In a possible implementation, the first signaling is located in a paging message, a random access response message, or a first message; wherein the first message is a message sent after the random access of the terminal device is completed.

[0398] When the communication device 1100 is used to implement the functions of the core network device in the above method embodiment:

[0399] a processing unit, configured to determine a first signaling; wherein the first signaling instructs the terminal device to report first data,

[0400] A communication unit is used to send the first signaling and first indication information to a network device, where the first indication information indicates the data size of the first data.

[0401] When the communication device 1100 is used to implement the functions of the network device in the method embodiment shown in FIG8 :

[0402] a processing unit, configured to send a paging message to a terminal device through a communication unit, wherein the paging message is used to page the terminal device;

[0403] The processing unit is used to send scheduling information to the terminal device through the communication unit, where the scheduling information is used to schedule resources for transmitting first data, and the resources are determined based on the data size indicated by the first information, and the first information comes from the core network device.

[0404] When the communication device 1100 is used to implement the functions of the terminal device in the method embodiment shown in FIG8 :

[0405] a processing unit, configured to receive a paging message from a network device through a communication unit, wherein the paging message is used to page the terminal device;

[0406] The processing unit is used to receive scheduling information from the network device through the communication unit, where the scheduling information is used to schedule resources for transmitting first data, and the resources are determined according to the data size indicated by the first information, where the first information comes from the core network device.

[0407] When the communication device 1100 is used to implement the functions of the core network device in the above method embodiment:

[0408] a processing unit, configured to determine first information indicating a data size of first data;

[0409] A communication unit is configured to send the first information to a network device.

[0410] When the communication device 1100 is used to implement the function of the second device in the above method embodiment:

[0411] A processing unit is used to send configuration information to a first device through a communication unit, where the configuration information is used to indicate a first resource or a first transmission block size, the first resource is determined based on a first data size indicated by the first information, the first transmission block size is used to indicate the size of data sent by the first device, and the first information comes from a core network device.

[0412] When the communication device 1100 is used to implement the function of the first device in the above method embodiment:

[0413] A processing unit is used to receive configuration information from a second device through a communication unit, where the configuration information is used to indicate a first resource or a first transmission block size, where the first resource is determined based on a first data size indicated by the first information, where the first transmission block size is used to indicate the size of data sent by the first device, and where the first information comes from a core network device.

[0414] When the communication device 1100 is used to implement the functions of the core network device in the above method embodiment:

[0415] a processing unit, configured to determine first information, wherein the first information indicates a first data size;

[0416] A communication unit is configured to send the first information to a second device.

[0417] A more detailed description of the processing unit 1110 and the communication unit 1120 can be directly obtained by referring to the relevant descriptions in the above-mentioned method embodiments, and will not be repeated here.

[0418] It should be understood that the division of units in the above device is merely a division of logical functions. In actual implementation, they can be fully or partially integrated into one physical entity, or they can be physically separated. Moreover, the units in the device can all be implemented in the form of software calling through processing elements; or they can all be implemented in the form of hardware; or some units can be implemented in the form of software calling through processing elements, and some units can be implemented in the form of hardware. For example, each unit can be a separately established processing element, or it can be integrated into a certain chip of the device. In addition, it can also be stored in the memory in the form of a program, called by a certain processing element of the device and execute the function of the unit. In addition, all or part of these units can be integrated together, or they can be implemented independently. The processing element described here can also be a processor, which can be an integrated circuit with signal processing capabilities. In the implementation process, each operation of the above method or each unit above can be implemented by the integrated logic circuit of the hardware in the processor element or in the form of software calling through the processing element.

[0419] In one example, the unit in any of the above devices may be one or more integrated circuits configured to implement the above method, such as one or more application specific integrated circuits (ASICs), one or more digital singnal processors (DSPs), one or more field programmable gate arrays (FPGAs), or a combination of at least two of these integrated circuit forms. For another example, when the unit in the device can be implemented in the form of a processing element scheduler, the processing element can be a processor, such as a general-purpose central processing unit (CPU), or other processor that can call a program. For another example, these units can be integrated together and implemented in the form of a system-on-a-chip (SOC).

[0420] The above-mentioned receiving unit is an interface circuit of the device, which is used to receive signals from other devices. For example, when the device is implemented as a chip, the receiving unit is the interface circuit of the chip used to receive signals from other chips or devices. The above-mentioned sending unit is an interface circuit of the device, which is used to send signals to other devices. For example, when the device is implemented as a chip, the sending unit is the interface circuit of the chip used to send signals to other chips or devices.

[0421] As another possible product form, the terminal device or network device or core network device described in the embodiment of the present application can be implemented by a general bus architecture. For ease of explanation, refer to Figure 12, which is a structural diagram of a communication device 1200 provided in an embodiment of the present application, and the communication device 1200 includes a processor 1201 and a transceiver 1202. The communication device 1200 can be a terminal device, or a chip or chip system therein; or, the communication device 1200 can be a network device, or a chip or module therein. Figure 12 only shows the main components of the communication device 1200. In addition to the processor 1201 and the transceiver 1202, the communication device 1200 may further include a memory 1203, and an input and output device (not shown in the figure).

[0422] Optionally, the processor 1201 is primarily used to process communication protocols and communication data, as well as control the entire communication device, execute software programs, and process software program data. The memory 1203 is primarily used to store software programs and data. The transceiver 1202 may include a radio frequency circuit and an antenna. The radio frequency circuit is primarily used to convert baseband signals into radio frequency signals and process radio frequency signals. The antenna is primarily used to transmit and receive radio frequency signals in the form of electromagnetic waves. Input and output devices, such as a touch screen, display, and keyboard, are primarily used to receive user input and output data to the user.

[0423] Optionally, the processor 1201 , the transceiver 1202 , and the memory 1203 may be connected via a communication bus.

[0424] When the communication device is powered on, the processor 1201 can read the software program in the memory 1203, interpret and execute the instructions of the software program, and process the data of the software program. When data needs to be sent wirelessly, the processor 1201 performs baseband processing on the data to be transmitted and outputs the baseband signal to the radio frequency circuit. The radio frequency circuit performs radio frequency processing on the baseband signal and then transmits the radio frequency signal to the outside in the form of electromagnetic waves via the antenna. When data is sent to the communication device, the radio frequency circuit receives the radio frequency signal via the antenna, converts the radio frequency signal into a baseband signal, and outputs the baseband signal to the processor 1201. The processor 1201 converts the baseband signal into data and processes the data.

[0425] In another implementation, the RF circuit and antenna may be provided independently of the processor performing baseband processing. For example, in a distributed scenario, the RF circuit and antenna may be remotely arranged independent of the communication device.

[0426] In some embodiments, in terms of hardware implementation, those skilled in the art may conceive that the above-mentioned communication device 1100 may take the form of the communication device 1200 shown in FIG. 12 .

[0427] As an example, the functions / implementation process of the processing unit 1110 in FIG11 may be implemented by the processor 1201 in the communication device 1200 shown in FIG12 calling computer-executable instructions stored in the memory 1203. The functions / implementation process of the communication unit 1120 in FIG11 may be implemented by the transceiver 1202 in the communication device 1200 shown in FIG12.

[0428] As another possible product form, the terminal device, network device, or core network device in this application may adopt the structure shown in Figure 13, or include the components shown in Figure 13. Figure 13 is a schematic diagram of the structure of a communication device 1300 provided in this application.

[0429] As shown in FIG13 , a communication device 1300 includes at least one processor 1301. Optionally, the communication device further includes a communication interface 1302.

[0430] When the program instructions are executed in the at least one processor 1301, the communication device 1300 can implement the method provided in any of the aforementioned embodiments and any possible designs therein. Alternatively, the processor 1301 implements the method provided in any of the aforementioned embodiments and any possible designs therein through logic circuits or by executing code instructions.

[0431] The communication interface 1302 may be used to receive program instructions and transmit them to the processor. Alternatively, the communication interface 1302 may be used for communication between the communication device 1300 and other communication devices, such as exchanging control signaling and / or service data. Exemplarily, the communication interface 1302 may be used to receive signals from devices other than the communication device 1300 and transmit them to the processor 1301, or to send signals from the processor 1301 to other communication devices other than the communication device 1300.

[0432] Optionally, the communication interface 1302 may be a code and / or data read and write interface circuit, or the communication interface 1302 may be a signal transmission interface circuit between a communication processor and a transceiver, or a pin of a chip.

[0433] Optionally, the communication device 1300 may further include at least one memory 1303, which may be used to store required program instructions and / or data. It should be noted that the memory 1303 may exist independently of the processor 1301 or may be integrated with the processor 1301. The memory 1303 may be located within or outside the communication device 1300, without limitation.

[0434] Optionally, the communication device 1300 may further include a power supply circuit 1304, which may be used to supply power to the processor 1301. The power supply circuit 1304 may be located in the same chip as the processor 1301, or in another chip other than the chip where the processor 1301 is located.

[0435] Optionally, the communication device 1300 may further include a bus, and various parts of the communication device 1300 may be interconnected via the bus.

[0436] In some embodiments, in terms of hardware implementation, those skilled in the art may conceive that the communication device 1100 shown in FIG. 11 may take the form of the communication device 1300 shown in FIG. 13 .

[0437] As an example, the functions / implementation processes of the processing unit 1110 in FIG11 may be implemented by the processor 1301 in the communication device 1300 shown in FIG13 calling computer-executable instructions stored in the memory 1303. The functions / implementation processes of the communication unit 1120 in FIG11 may be implemented by the communication interface 1302 in the communication device 1300 shown in FIG13.

[0438] It should be noted that the structure shown in Figure 13 does not constitute a specific limitation on the terminal device, network device, or core network device. For example, in other embodiments of the present application, the terminal device, network device, or core network device may include more or fewer components than shown, or combine or split certain components, or arrange the components differently. The components shown in the figure may be implemented in hardware, software, or a combination of software and hardware.

[0439] The method steps in the embodiments of the present application can be implemented by hardware or by a processor executing software instructions. The software instructions can be composed of corresponding software modules, and the software modules can be stored in a random access memory, a flash memory, a read-only memory, a programmable read-only memory, an erasable programmable read-only memory, an electrically erasable programmable read-only memory, a register, a hard disk, a mobile hard disk, a CD-ROM or any other form of storage medium well known in the art. An exemplary storage medium is coupled to the processor so that the processor can read information from the storage medium and write information to the storage medium. Of course, the storage medium can also be an integral part of the processor. The processor and the storage medium can be located in an ASIC. In addition, the ASIC can be located in a base station or a terminal. Of course, the processor and the storage medium can also exist in a base station or a terminal as discrete components.

[0440] It is understood that the processor in the embodiments of the present application may be a central processing unit (CPU), or may be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. The general-purpose processor may be a microprocessor or any conventional processor.

[0441] The method steps in the embodiments of the present application can be implemented by hardware or by a processor executing software instructions. The software instructions can be composed of corresponding software modules, and the software modules can be stored in a random access memory, a flash memory, a read-only memory, a programmable read-only memory, an erasable programmable read-only memory, an electrically erasable programmable read-only memory, a register, a hard disk, a mobile hard disk, a CD-ROM or any other form of storage medium well known in the art. An exemplary storage medium is coupled to the processor so that the processor can read information from the storage medium and write information to the storage medium. Of course, the storage medium can also be an integral part of the processor. The processor and the storage medium can be located in an ASIC. In addition, the ASIC can be located in a base station or a terminal. Of course, the processor and the storage medium can also exist in a base station or a terminal as discrete components.

[0442] In the above embodiments, all or part of the embodiments may be implemented using software, hardware, firmware, or any combination thereof. When implemented using software, all or part of the embodiments may be implemented in the form of a computer program product. A computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, all or part of the processes or functions of the embodiments of the present application are performed. The computer may be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user device, or other programmable device. The computer program or instructions may be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the computer program or instructions may be transferred from one website, computer, server, or data center to another website, computer, server, or data center via wired or wireless means. The computer-readable storage medium may be any available medium that can be accessed by 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, such as floppy disks, hard disks, or magnetic tapes; optical media, such as digital video disks; or semiconductor media, such as solid-state drives. The computer-readable storage medium may be a volatile or nonvolatile storage medium, or may include both volatile and nonvolatile types of storage media.

[0443] In the various embodiments of the present application, unless otherwise specified or there is a logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships.

[0444] Those skilled in the art will appreciate that the embodiments of the present application can be provided as methods, systems, or computer program products. Therefore, the present application can adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application can adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, optical storage, etc.) that contain computer-usable program code.

[0445] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the present application. It should be understood that each flow and / or box in the flow chart and / or block diagram, as well as the combination of the flow chart and / or box in the flow chart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device produce a device for implementing the functions specified in one or more flow charts and / or one or more boxes in the block diagram.

[0446] These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce a product including an instruction device that implements the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0447] Obviously, those skilled in the art may make various changes and modifications to the present application without departing from the scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include these modifications and variations.

Claims

1. A data transmission method, characterized in that: include: Sending a paging message to a terminal device, wherein the paging message is used to page the terminal device; Send scheduling information to the terminal device, where the scheduling information is used to schedule resources for transmitting first data, and the resources are determined based on the data size indicated by the first information, and the first information comes from a core network device.

2. The method according to claim 1, characterized in that The scheduling information is sent when a first buffer status report related to the first data is not received.

3. The method according to claim 1 or 2, characterized in that: The first information includes a data size of the first data.

4. The method according to claim 1 or 2, characterized in that: The first information is second data sent to the terminal device, and the second data has a corresponding data size with the first data.

5. The method according to claim 1 or 2, characterized in that: The first information indicates a service corresponding to the first data, and there is a corresponding relationship between the service corresponding to the first data and the data size of the first data.

6. The method according to any one of claims 1 to 5, characterized in that: The method further comprises: Sending a first signaling to a terminal device; the first signaling instructs the terminal device to report the first data; Wherein, the first signaling is used to trigger the inventory process, and the first data is the service data of the inventory service; Alternatively, the first signaling is used to trigger a reading process, and the first data is data stored in the terminal device.

7. The method according to claim 6, characterized in that The first signaling is located in the paging message or the random access response message or the first message; The first message is a message sent after random access of the terminal device is completed.

8. The method according to any one of claims 1 to 7, characterized in that: The method further comprises: Sending second information to the terminal device, wherein the second information indicates not to send or to send a first buffer status report related to the first data, and the second information is located in the paging message or the random access response message.

9. The method according to any one of claims 1 to 8, characterized in that: The terminal device is a tag in the environmental Internet of Things.

10. The method according to any one of claims 1 to 9, characterized in that: The method further comprises: Sending third information to the terminal device, wherein the third information instructs the terminal device to report a second buffer status report before data transmission, and the third information is sent after the terminal device completes random access.

11. The method according to any one of claims 6 to 7, characterized in that: The method further comprises: A second message is received from the terminal device through the resource, wherein the second message includes first data; wherein the data size indicated by the first information is equal to the data size of the first data, or the data size indicated by the first information is equal to the data size of the second message.

12. The method according to any one of claims 6 to 7, characterized in that: The method further comprises: A second message is received from the terminal device through the resource, wherein the second message includes first data, and the second message also includes at least one of an access layer message header and an access layer signaling; wherein the data size indicated by the first information is equal to the sum of at least one of the data size of the access layer message header and the data size of the access layer signaling and the data size of the first data.

13. A data transmission method, characterized in that: include: Receiving a paging message from a network device, wherein the paging message is used to page a terminal device; Receive scheduling information from the network device, where the scheduling information is used to schedule resources for transmitting first data, where the resources are determined based on a data size indicated by the first information, and where the first information comes from a core network device.

14. The method according to claim 13, characterized in that The first information includes a data size of the first data.

15. The method according to claim 13, characterized in that The first information is second data sent to the terminal device, and the second data has a corresponding data size with the first data.

16. The method according to any one of claims 13 to 15, characterized in that: The method further comprises: receiving a first signaling from the network device; the first signaling instructs reporting the first data; Wherein, the first signaling is used to trigger the inventory process, and the first data is the service data of the inventory service; Alternatively, the first signaling is used to trigger a reading process, and the first data is data stored in the terminal device.

17. The method according to claim 16, characterized in that The first signaling is located in the paging message or the random access response message or the first message; The first message is a message sent after random access of the terminal device is completed.

18. The method according to any one of claims 13 to 17, characterized in that: The terminal device is a tag in the environmental Internet of Things.

19. The method according to claim 16, characterized in that The method further comprises: A second message is sent to the network device through the resource, wherein the second message includes first data; wherein the data size indicated by the first information is equal to the data size of the first data, or the data size indicated by the first information is equal to the data size of the second message.

20. The method according to claim 16, characterized in that The method further comprises: A second message is sent to the network device through the resource, wherein the second message includes the first data, and the second message also includes at least one of an access layer message header and an access layer signaling; wherein the data size indicated by the first information is equal to the sum of at least one of the data size of the access layer message header and the data size of the access layer signaling and the data size of the first data.

21. A data transmission method, characterized in that: The method is applicable to a core network device, including: determining first information, wherein the first information indicates a data size of the first data; The first information is sent to a network device.

22. A data transmission method, characterized in that: include: Configuration information is sent to a first device, where the configuration information is used to indicate a first resource or a first transmission block size, where the first resource is determined based on a first data size indicated by the first information, where the first transmission block size is used to indicate a size of data sent by the first device, and where the first information comes from a core network device.

23. The method according to claim 22, characterized in that The configuration information is sent without receiving a first buffer status report from the first device.

24. The method according to claim 22 or 23, characterized in that The first information includes the first data size.

25. The method according to claim 22 or 23, characterized in that The first information is second data sent to the first device, and the second data has a corresponding size to the first data.

26. The method according to claim 22 or 23, characterized in that The first information indicates a first service, and there is a corresponding relationship between the first service and the first data size.

27. The method according to any one of claims 22 to 26, characterized in that: The method further comprises: A first signaling is sent to the first device; the first signaling instructs the first device to report first data.

28. The method according to claim 27, characterized in that The first signaling is a paging message, a random access response message, a contention resolution success message, or a first message; The first message is a message sent after random access of the first device is completed.

29. The method according to any one of claims 27 to 28, characterized in that: The method further comprises: A second message is received from the first device through the first resource, wherein the second message includes first data; wherein the size of the first data is equal to the data size of the first data, or the size of the first data is equal to the data size of the second message.

30. The method according to any one of claims 27 to 28, characterized in that: The method further comprises: A second message is received from the first device through the first resource, the second message includes first data, and the second message also includes at least one of an access layer message header, access layer signaling and padding; the first data size is less than or equal to the sum of at least one of the data size of the access layer message header, the data size of the access layer signaling, the data size of the padding and the data size of the first data.

31. The method according to any one of claims 22 to 30, characterized in that: The method further comprises: Second information is sent to the first device, where the second information indicates whether to send or not to send a first buffer status report, and the second information is located in the paging message or the random access response message.

32. A data transmission method, characterized in that: include: Receive configuration information from a second device, the configuration information is used to indicate a first resource or a first transmission block size, the first resource is determined based on a first data size indicated by the first information, the first transmission block size is used to indicate the size of data sent by the first device, and the first information comes from a core network device.

33. The method according to claim 32, characterized in that The first information includes the first data size.

34. The method according to claim 32, characterized in that The first information is second data sent to the first device, and the second data has a corresponding size to the first data.

35. The method according to any one of claims 32 to 34, characterized in that: The method further comprises: A first signaling is received from the second device; the first signaling indicates reporting of first data.

36. The method according to claim 35, characterized in that The first signaling is a paging message, a random access response message, a contention resolution success message, or a first message; The first message is a message sent after random access of the first device is completed.

37. The method according to any one of claims 35 to 36, characterized in that: The method further comprises: A second message is sent to the second device through the first resource, wherein the second message includes first data; wherein the size of the first data is equal to the data size of the first data, or the size of the first data is equal to the data size of the second message.

38. The method according to any one of claims 35 to 36, characterized in that: The method further comprises: A second message is sent to the second device through the first resource, the second message includes first data, and the second message also includes at least one of an access layer message header, access layer signaling and padding; the first data size is less than or equal to the sum of at least one of the data size of the access layer message header, the data size of the access layer signaling, the data size of the padding and the data size of the first data.

39. The method according to any one of claims 37 to 38, characterized in that: The data size of the second message is determined according to the first transmission block size.

40. A data transmission method, characterized in that: The method is applicable to a core network device, including: determining first information, the first information indicating a first data size; The first information is sent to the second device.

41. A communication device, characterized in that: include: A processing unit, configured to send a paging message to a terminal device through a communication unit, wherein the paging message is used to page the terminal device; The processing unit is used to send scheduling information to the terminal device through the communication unit, the scheduling information is used to schedule resources for transmitting first data, the resources are determined according to the data size indicated by the first information, and the first information comes from the core network device.

42. A communication device, characterized in that: include: A processing unit, configured to receive a paging message from a network device through a communication unit, wherein the paging message is used to page the terminal device; The processing unit is used to receive scheduling information from the network device through the communication unit, the scheduling information is used to schedule resources for transmitting first data, the resources are determined according to the data size indicated by the first information, and the first information comes from the core network device.

43. A communication device, characterized in that: include: a processing unit, configured to determine first information indicating a data size of first data; A communication unit is used to send the first information to the network device.

44. A communication device, characterized in that: include: A processing unit is used to send configuration information to a first device through a communication unit, wherein the configuration information is used to indicate a first resource or a first transmission block size, the first resource is determined according to a first data size indicated by the first information, the first transmission block size is used to indicate the size of data sent by the first device, and the first information comes from a core network device.

45. A communication device, characterized in that: include: A processing unit is used to receive configuration information from a second device through a communication unit, wherein the configuration information is used to indicate a first resource or a first transmission block size, the first resource is determined according to a first data size indicated by the first information, the first transmission block size is used to indicate the size of data sent by the first device, and the first information comes from a core network device.

46. ​​A communication device, characterized in that: include: a processing unit, configured to determine first information, wherein the first information indicates a first data size; A communication unit is used to send the first information to the second device.

47. A communication device, characterized in that: The method comprises a unit or a module for executing the method according to any one of claims 1 to 40.

48. A communication device, characterized in that: It comprises a processor, the processor is coupled to a memory, and a computer program is stored in the memory; the processor is used to call the computer program in the memory so that the method according to any one of claims 1 to 40 is executed.

49. A computer-readable storage medium, characterized in that The storage medium stores a computer program or instruction. When the computer program or instruction is executed by a computer, the method according to any one of claims 1 to 40 is executed.

50. A chip, characterized in that: The chip comprises a processor, and when the processor executes a computer program or instruction, the method according to any one of claims 1 to 40 is performed.

51. A computer program product, characterized in that When a computer reads and executes the computer program product, the method according to any one of claims 1 to 40 is performed.

Images