Communication methods, terminals, network devices, systems, and storage media

Abstract

This disclosure provides a communication method, terminal, network device, system, and storage medium. The method includes: receiving downlink control information (DCI) sent by the network device; wherein the DCI is used to configure a corresponding data format for a scheduled first resource; sending a first data packet using the data format on the first resource; and / or receiving a second data packet using the data format. In this disclosure, a specific data format can be associated with dynamically scheduled resources, thereby reducing signaling loss when the terminal transmits and receives data through dynamically scheduled resources, improving data transmission and reception efficiency, increasing spectrum utilization, and enhancing availability.

Description

Communication method, terminal, network device, system and storage medium TECHNICAL FIELD

[0001] The present disclosure relates to the field of communication, and in particular, to a communication method, a terminal, a network device, a system and a storage medium. BACKGROUND

[0002] Currently, a radio bearer (RB) is a general term of different layer protocol entities and configurations allocated by a network device, such as a base station, for a terminal, which can include a data radio bearer (DRB) and a signal radio bearer (SRB), the DRB can transmit user plane information, and the SRB can be used to transmit control plane information.

[0003] SUMMARY

[0004] In order to improve the data transceiving efficiency, the embodiments of the present disclosure provide a communication method, a terminal, a network device, a system and a storage medium.

[0005] According to a first aspect of the embodiments of the present disclosure, a communication method is provided, the method is performed by a terminal, and the method comprises:

[0006] receiving downlink control information (DCI) sent by a network device; wherein the DCI is used to configure a corresponding data format for a scheduled first resource;

[0007] on the first resource, sending a first data packet using the data format, and / or receiving a second data packet using the data format.

[0008] According to a second aspect of the embodiments of the present disclosure, a communication method is provided, the method is performed by a network device, and the method comprises:

[0009] sending downlink control information (DCI) to a terminal; wherein the DCI is used to configure a corresponding data format for a scheduled first resource;

[0010] on the first resource, receiving a first data packet using the data format, and / or sending a second data packet using the data format.

[0011] According to a third aspect of the embodiments of the present disclosure, a terminal is provided, comprising:

[0012] a transceiver module configured to receive downlink control information (DCI) sent by a network device; wherein the DCI is used to configure a corresponding data format for a scheduled first resource;

[0013] The transceiver module is further configured to send, on the first resource, a first data packet using the data format, and / or receive a second data packet using the data format.

[0014] According to a fourth aspect of embodiments of the present disclosure, a network device is provided, comprising:

[0015] a transceiver module configured to send, to a terminal, a downlink control information (DCI); wherein the DCI is used to configure a corresponding data format for a scheduled first resource;

[0016] The transceiver module is further configured to receive, on the first resource, a first data packet using the data format, and / or send a second data packet using the data format.

[0017] According to a fifth aspect of embodiments of the present disclosure, a terminal is provided, comprising:

[0018] one or more processors;

[0019] The processor is configured to perform the communication method of any one of the first aspect.

[0020] According to a sixth aspect of embodiments of the present disclosure, a network device is provided, comprising:

[0021] one or more processors;

[0022] The processor is configured to perform the communication method of any one of the second aspect.

[0023] According to a seventh aspect of embodiments of the present disclosure, a communication system is provided, comprising:

[0024] a terminal, the first device being configured to implement the communication method of any one of the first aspect;

[0025] a network device, the second device being configured to implement the communication method of any one of the second aspect.

[0026] According to an eighth aspect of embodiments of the present disclosure, a storage medium is provided, the storage medium storing instructions, when the instructions are executed on a communication device, causing the communication device to perform the communication method of any one of the first aspect or the second aspect.

[0027] According to a ninth aspect of embodiments of the present disclosure, a computer program product is provided, comprising a computer program, the computer program being executed by a processor to implement the communication method of any one of the first aspect or the second aspect.

[0028] In the embodiments of the present disclosure, the terminal transmits a first data packet using a data format corresponding to a first resource based on a DCI transmitted by the network device, and / or receives a second data packet using the data format corresponding to the first resource on the first resource scheduled by the DCI. In the present disclosure, a specific data format can be associated with a dynamically scheduled resource, thereby reducing signaling loss when the terminal transmits and receives data through the dynamically scheduled resource, improving data transmission efficiency, improving spectrum utilization, and having high availability.

[0029] It should be understood that the above general description and the following detailed description are only exemplary and explanatory, and cannot limit the present disclosure. BRIEF DESCRIPTION OF DRAWINGS

[0030] The accompanying drawings, which are incorporated into and form part of the specification, illustrate embodiments consistent with the present disclosure and, together with the specification, serve to explain the principles of the present disclosure.

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

[0032] FIG. 1B is one exemplary schematic diagram of a data format of DRB data uplink transmission according to an embodiment of the present disclosure.

[0033] FIG. 1C is one exemplary schematic diagram of a data format of DRB data downlink reception according to an embodiment of the present disclosure.

[0034] FIG. 2 is one exemplary interaction schematic diagram of a communication method according to an embodiment of the present disclosure.

[0035] FIG. 3A is one exemplary flow schematic diagram of a communication method according to an embodiment of the present disclosure.

[0036] FIG. 3B is another exemplary flow schematic diagram of a communication method according to an embodiment of the present disclosure.

[0037] FIG. 3C is a third exemplary flow schematic diagram of a communication method according to an embodiment of the present disclosure.

[0038] FIG. 3D is a fourth exemplary flow schematic diagram of a communication method according to an embodiment of the present disclosure.

[0039] FIG. 4A is one exemplary schematic diagram of a data format according to an embodiment of the present disclosure.

[0040] FIG. 4B is another exemplary schematic diagram of a data format according to an embodiment of the present disclosure.

[0041] FIG. 4C is a third exemplary schematic diagram of a data format according to an embodiment of the present disclosure.

[0042] FIG. 4D is an example schematic diagram four of a data format according to an embodiment of the present disclosure.

[0043] FIG. 4E is an example schematic diagram two of a communication method according to an embodiment of the present disclosure.

[0044] FIG. 4F is an example schematic diagram three of a communication method according to an embodiment of the present disclosure.

[0045] FIG. 5A is an example block diagram of a terminal according to an embodiment of the present disclosure.

[0046] FIG. 5B is an example block diagram of a network device according to an embodiment of the present disclosure.

[0047] FIG. 6A is an example schematic diagram of a communication device according to an embodiment of the present disclosure.

[0048] FIG. 6B is an example schematic diagram of a chip according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0049] The example embodiments will be described in detail herein with reference to the accompanying drawings. The following description relates to the accompanying drawings, in which the same numbers represent the same or similar elements throughout the several drawings. The implementations described in the following example embodiments do not represent all implementations consistent with the present disclosure. Instead, they are merely examples of apparatuses and methods consistent with some aspects of the present disclosure as detailed in the appended claims.

[0050] Embodiments of the present disclosure provide a communication method, a terminal, a network device, a system and a storage medium.

[0051] In a first aspect, embodiments of the present disclosure provide a communication method, performed by a terminal, the method comprising: receiving a downlink control information (DCI) sent by a network device; wherein the DCI is used to configure a corresponding data format for a scheduled first resource; and transmitting a first data packet using the data format on the first resource, and / or receiving a second data packet using the data format.

[0052] In the above embodiments, a specific data format can be associated with a dynamically scheduled resource, thereby reducing signaling loss when the terminal transmits and receives data through the dynamically scheduled resource, improving data transmission and reception efficiency, improving spectrum utilization, and having high availability.

[0053] In some embodiments of the first aspect, in some embodiments, the DCI comprises at least one of: first resource indication information; data format configuration information; control signaling indication information, wherein the control signaling indication information is used to indicate the configuration of a control information field in a data packet using the data format; and bearer information.

[0054] In the above embodiments, the DCI can comprise at least one of the above, thereby associating the first dynamically scheduled resource with the data format through the DCI, which is simple and has high availability.

[0055] In some embodiments of the first aspect, in some embodiments, the data format comprises any one of: a first format, wherein a subheader of a sub-protocol data unit (PDU) of a data packet of the first format comprises only a first information field, wherein the first information field is used to indicate whether there are other sub-PDUs; a second format, wherein a subheader of a sub-PDU of a data packet of the second format comprises only a first information field and a second information field, wherein the first information field is used to indicate whether there are other sub-PDUs, and the second information field is used to indicate a logical channel identifier; a third format, wherein a subheader of a sub-PDU of a data packet of the third format comprises only a third information field, wherein the third information field is used to indicate the length of a service data unit (SDU); and a fourth format, wherein a PDU of a data packet of the fourth format comprises only one SDU.

[0056] In the above embodiments, multiple data formats are provided, which reduces the signaling loss when the terminal transmits and receives data through dynamically scheduled resources, and has high availability.

[0057] In some embodiments of the first aspect, in some embodiments, the control signaling indication information comprises at least one of: first indication information, wherein the first indication information is used to indicate whether a third information field exists in a subheader of a sub-PDU of a data packet, and the third information field is used to indicate the length of an SDU; second indication information, wherein the second indication information is used to indicate whether a second information field exists in a subheader of a sub-PDU of a data packet, and the second information field is used to indicate a logical channel identifier; and third indication information, wherein the third indication information is used to indicate whether a first information field exists in a subheader of a sub-PDU of a data packet, and the first information field is used to indicate whether there are other sub-PDUs.

[0058] In the above embodiments, the corresponding data format can be determined based on the control signaling indication information, thereby achieving the purpose of associating the first dynamically scheduled resource with the data format through the DCI, which has high availability.

[0059] In some embodiments of the first aspect, in some embodiments, the method further comprises at least one of the following: the data format does not comprise a third information field, receiving a first radio resource control (RRC) message sent by the network device; wherein the third information field is used to indicate a length of the SDU; wherein the first RRC message is used to configure the length of the SDU; the data format does not comprise a second information field, receiving a second RRC message sent by the network device; wherein the second information field is used to indicate a logical channel identifier; wherein the second RRC message is used to configure a bearer information of the SDU; the data format is a fourth format, receiving a second RRC message sent by the network device; wherein the PDU of the data packet of the fourth format comprises only one SDU; wherein the second RRC message is used to configure the bearer information of the SDU.

[0060] In the above embodiments, the length of the SDU and / or the bearer information of the SDU can be configured through the RRC message, thereby saving the signaling resources of the DCI and improving the availability.

[0061] In some embodiments of the first aspect, in some embodiments, the bearer information comprises at least one of the following: a session identifier; a data flow identifier; a radio bearer identifier; a logical channel identifier; and a radio link control (RLC) entity identifier.

[0062] In the above embodiments, the bearer information can comprise, but is not limited to, at least one of the above, thereby achieving the purpose of associating the first resource of dynamic scheduling with the bearer through the DCI and improving the availability.

[0063] In some embodiments of the first aspect, in some embodiments, the sending, on the first resource, the first data packet using the data format comprises: when uplink data needs to be sent on the first resource, encapsulating the SDU received from a first bearer into a data packet according to the data format to obtain the first data packet; wherein the first bearer is a bearer corresponding to the data format; and sending the first data packet to the network device.

[0064] In the above embodiments, the terminal can encapsulate the first data packet in the above manner and send the first data packet to the network device, thereby improving the data transmission efficiency, improving the spectrum utilization rate, and improving the availability.

[0065] In some embodiments of the first aspect, in some embodiments, the receiving, on the first resource, the second data packet using the data format comprises: when downlink data needs to be received on the first resource, sending the second data packet received to a second bearer after unpacking the second data packet; wherein the second bearer is a bearer corresponding to the data format.

[0066] In the above embodiment, the terminal can unpack the received second data packet in the above manner and deliver it to the corresponding second bearer, thereby improving data transmission efficiency, improving spectrum utilization, and having high availability.

[0067] In some embodiments of the first aspect, the number of data packets of the fourth format transmitted each time is 1.

[0068] In the above embodiment, if only a MAC SDU is included in the MAC PDU packet, the number of data packets during transmission is 1, thereby improving the reliability of data transmission.

[0069] In the second aspect, the embodiments of the present disclosure provide a communication method, the method is performed by a network device, and the method comprises the following steps: sending, to a terminal, downlink control information DCI; wherein the DCI is used to configure a corresponding data format for a scheduled first resource; receiving a first data packet using the data format on the first resource, and / or sending a second data packet using the data format.

[0070] In some embodiments of the second aspect, the DCI comprises at least one of the following: first resource indication information; data format configuration information; control signaling indication information, wherein the control signaling indication information is used to indicate the configuration of a control information field in a data packet using the data format; and bearer information.

[0071] In some embodiments of the second aspect, the data format comprises any one of the following: a first format, wherein a subheader of a sub-protocol data unit PDU of a data packet of the first format only includes a first information field, wherein the first information field is used to indicate whether there are other sub-PDUs; a second format, wherein a subheader of a sub-PDU of a data packet of the second format only includes a first information field and a second information field, wherein the first information field is used to indicate whether there are other sub-PDUs, and the second information field is used to indicate a logical channel identifier; a third format, wherein a subheader of a sub-PDU of a data packet of the third format only includes a third information field, wherein the third information field is used to indicate the length of a service data unit SDU; and a fourth format, wherein a PDU of a data packet of the fourth format only includes one SDU.

[0072] In some embodiments of the second aspect, in some embodiments, the control signaling indication information comprises at least one of: first indication information, wherein the first indication information is used to indicate whether a third information field exists in the subheader of the sub-PDU of the data packet, and the third information field is used to indicate the length of the SDU; second indication information, wherein the second indication information is used to indicate whether a second information field exists in the subheader of the sub-PDU of the data packet, and the second information field is used to indicate the logical channel identifier; third indication information, wherein the third indication information is used to indicate whether a first information field exists in the subheader of the sub-PDU of the data packet, and the first information field is used to indicate whether there is another sub-PDU.

[0073] In some embodiments of the second aspect, in some embodiments, the method further comprises at least one of: the data format does not comprise a third information field, and a first radio resource control (RRC) message is sent to the terminal, wherein the third information field is used to indicate the length of the SDU, and wherein the first RRC message is used to configure the length of the SDU; the data format does not comprise a second information field, and a second RRC message is sent to the terminal, wherein the second information field is used to indicate the logical channel identifier, and wherein the second RRC message is used to configure the bearer information of the SDU; the data format is a fourth format, and a second RRC message is sent to the terminal, wherein the PDU of the data packet of the fourth format only comprises one SDU, and wherein the second RRC message is used to configure the bearer information of the SDU.

[0074] In some embodiments of the second aspect, in some embodiments, the bearer information comprises at least one of: a session identifier; a data flow identifier; a radio bearer identifier; a logical channel identifier; and a radio link control (RLC) entity identifier.

[0075] In some embodiments of the second aspect, in some embodiments, the receiving, on the first resource, the first data packet using the data format comprises: when uplink data needs to be received on the first resource, unpacking the received first data packet and sending it to a first bearer, wherein the first bearer is a bearer corresponding to the data format.

[0076] In some embodiments of the second aspect, in some embodiments, the sending, on the first resource, the second data packet using the data format comprises: when downlink data needs to be sent on the first resource, encapsulating the SDU received from a second bearer into a data packet according to the data format to obtain the second data packet, wherein the second bearer is a bearer corresponding to the data format; and sending the second data packet to the terminal.

[0077] In some embodiments of the second aspect, the number of data packets of the fourth format transmitted each time is 1.

[0078] In a third aspect, the embodiments of the present disclosure provide a terminal, comprising: a transceiver configured to receive a downlink control information (DCI) sent by a network device; wherein the DCI is used to configure a corresponding data format for a scheduled first resource; and the transceiver is further configured to send a first data packet using the data format on the first resource, and / or receive a second data packet using the data format.

[0079] In a fourth aspect, the embodiments of the present disclosure provide a network device, comprising: a transceiver configured to send a downlink control information (DCI) to a terminal; wherein the DCI is used to configure a corresponding data format for a scheduled first resource; and the transceiver is further configured to receive a first data packet using the data format on the first resource, and / or send a second data packet using the data format.

[0080] In a fifth aspect, the embodiments of the present disclosure provide a terminal, comprising: one or more processors; wherein the processor is configured to execute the communication method of any one of the first aspect.

[0081] In a sixth aspect, the embodiments of the present disclosure provide a network device, comprising: one or more processors; wherein the processor is configured to execute the communication method of any one of the second aspect.

[0082] In a seventh aspect, the embodiments of the present disclosure provide a communication system, comprising: a terminal, the first device is configured to implement the communication method of any one of the first aspect; and a network device, the second device is configured to implement the communication method of any one of the second aspect.

[0083] In an eighth aspect, the embodiments of the present disclosure provide a storage medium, the storage medium stores instructions, when the instructions are executed on a communication device, the communication device executes the communication method of any one of the first aspect or the second aspect.

[0084] In a ninth aspect, the embodiments of the present disclosure provide a computer program product, comprising a computer program, the computer program is executed by a processor to implement the communication method of any one of the first aspect or the second aspect.

[0085] In a tenth aspect, the embodiments of the present disclosure provide a chip or chip system. The chip or chip system comprises a processing circuit configured to execute the method described in the optional implementation of the first aspect or the second aspect.

[0086] It can be understood that the terminal, network device, communication system, storage medium, computer program product, chip or chip system described above are used to execute the method proposed in the embodiments of the present disclosure. Therefore, the beneficial effects achieved thereby can refer to the beneficial effects in the corresponding method, which will not be described here again.

[0087] The embodiments of the present disclosure propose an invention name. In some embodiments, the terms of communication method, information transmission method, data transmission method, and the like can be replaced with each other, the terms of communication device, information transmission device, data transmission device, and the like can be replaced with each other, and the terms of communication system, information transmission system, data transmission system, and the like can be replaced with each other.

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

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

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

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

[0092] In the embodiments of the present disclosure, "a plurality of" means two or more.

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

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

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

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

[0097] In some embodiments, "comprising", "including", "to indicate", "carrying", can be interpreted as directly carrying A, or indirectly indicating A.

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

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

[0100] In some embodiments, the device and the like can be interpreted as physical or virtual, and the name is not limited to the name described in the embodiments. The terms "device", "equipment", "device", "circuit", "network element", "node", "function", "unit", "section", "system", "network", "chip", "chip system", "entity", "subject" and the like can be replaced with each other.

[0101] In some embodiments, "network" can be interpreted as a device (for example, access network device, core network device, etc.) contained in the network.

[0102] In some embodiments, the terms “access network device (AN device),” “radio access network device (RAN device),” “base station (BS),” “radio base station,” “fixed station,” “node,” “access point,” “transmission point (TP),” “reception point (RP),” “transmission / reception point (TRP),” “panel,” “antenna panel,” “antenna array,” “cell,” “macro cell,” “small cell,” “femto cell,” “pico cell,” “sector,” “cell group,” “serving cell,” “carrier,” “component carrier,” “bandwidth part (BWP),” and the like can be used interchangeably.

[0103] In some embodiments, the terms "terminal," "terminal device," "user equipment (UE)," "user terminal," "mobile station (MS)," "mobile terminal (MT)," "subscriber station," "mobile unit," "subscriber unit," "wireless unit," "remote unit," "mobile device," "wireless device," "wireless communication device," "remote device," "mobile subscriber station," "access terminal," "mobile terminal," "wireless terminal," "remote terminal," "handset," "user agent," "mobile client," "client," and so on can be replaced with each other.

[0104] In some embodiments, the access network device, the core network device, or the network device can be replaced with a terminal. For example, the embodiments of the present disclosure can also be applied to a structure in which communication between the access network device, the core network device, or the network device and the terminal is replaced with communication between a plurality of terminals (e.g., device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, the terminal can also be configured to have all or part of the functions of the access network device. In addition, the terms "uplink," "downlink," and the like can also be replaced with terms corresponding to the inter-terminal communication (e.g., "side"). For example, the uplink channel, the downlink channel, and the like can be replaced with the side channel, and the uplink, the downlink, and the like can be replaced with the sidelink.

[0105] In some embodiments, the terminal can be replaced with the access network device, the core network device, or the network device. In this case, the access network device, the core network device, or the network device can also be configured to have all or part of the functions of the terminal.

[0106] In some embodiments, obtaining data, information, etc. can comply with laws and regulations of the country where the location is.

[0107] In some embodiments, data, information, etc. can be obtained after obtaining the consent of the user.

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

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

[0110] As shown in FIG. 1A, the communication system 100 includes a terminal 101 and a network device 102.

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

[0112] In some embodiments, the network device 102 includes at least one of an access network device and a core network device, but is not limited thereto.

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

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

[0115] In some embodiments, the access network device can be composed of a central unit (CU) and a distributed unit (DU), wherein the CU can also be referred to as a control unit. The CU-DU structure can split the protocol layers of the access network device, and part of the functions of the protocol layers are controlled by the CU, and the remaining part or all of the functions of the protocol layers are distributed in the DU and controlled by the CU, but the present disclosure is not limited thereto.

[0116] In some embodiments, the core network device can be one device including multiple network elements, etc., or can be multiple devices or device groups, each including all or part of multiple network elements. The network element can be virtual or physical. The core network includes, for example, at least one of an evolved packet core (EPC), a 5G core network (5GCN), and a next generation core (NGC).

[0117] In the embodiments of the present disclosure, several formats of DRB data channel MAC PDU are provided.

[0118] Wherein, the uplink transmission of DRB data can use the data format shown in FIG. 1B, and the downlink reception of DRB data can use the data format shown in FIG. 1C.

[0119] Wherein, one MAC PDU contains multiple media access control sub-protocol data units (Media Access Control sub Protocol Data Unit, MAC subPDU). Each MAC subPDU can contain at least one of the following:

[0120] MAC SDU in MAC subPDU (MAC subPDU including MAC SDU): DRB data part;

[0121] MAC CE in MAC subPDU (MAC subPDU including MAC CE): MAC control signaling part;

[0122] Padding bits in MAC subPDU (MAC subPDU including padding).

[0123] Wherein, each MAC subPDU needs to contain 1 subheader, which can include but is not limited to the following information fields:

[0124] Logical channel identity (Logical Channel Identity) information field (i.e. LCID field): used to indicate the logical channel identity;

[0125] Length information field (i.e. L field): used to indicate the length of the MAC service data unit (Service Data Unit, SDU);

[0126] Subsequent MAC subPDU indication information field (i.e. E field): used to indicate whether there are other MAC subPDUs after this MAC subPDU;

[0127] Reserved information field (i.e. R field).

[0128] In the embodiments of the present disclosure, the dual connectivity (Dual Connectivity, DC) is introduced as follows:

[0129] The terminal can be configured with two cell groups at the same time, that is:

[0130] Master Cell Group (MCG): including at least 1 Primary Cell (PCell). In addition, it can include 1 or more Secondary Cells (SCells).

[0131] Secondary Cell Group (SCG): including at least 1 Primary Secondary Cell (PSCell). In addition, it can include 1 or more SCells.

[0132] Among them, the network node for managing MCG is Master Node (MN), and the network node for managing SCG is Secondary Node (SN). Among them, PCell and PSCell can be collectively referred to as Special Cell (SpCell).

[0133] In the embodiments of the present disclosure, the semi-persistent resource configuration is introduced as follows:

[0134] In order to support faster data management, a semi-persistent resource configuration method is provided for uplink data, including:

[0135] Configured Grant (CG): used for uplink data transmission.

[0136] Among them, CG includes the following types:

[0137] Configured Grant Type-1: the uplink resource configuration provides the period of uplink resource and the specific allocation of uplink time-frequency resource through Radio Resource Control (RRC) message. After the terminal receives the configuration, it directly uses the configured uplink resource to transmit uplink data (i.e. the uplink resource is activated immediately after RRC configuration).

[0138] Configured Grant Type-2: RRC message configures the period of uplink resource, and Physical Downlink Control Channel (PDCCH) control signaling activates and indicates the specific allocation of uplink time-frequency resource. The terminal needs to activate the uplink resource configuration through PDCCH control signaling before it can use the configured uplink resource to transmit uplink data.

[0139] In addition, a semi-persistent resource configuration method is provided for downlink data, including:

[0140] Semi-Persistent Scheduling (SPS): RRC message configures the period of downlink resource, and PDCCH control signaling activates and indicates the specific allocation of downlink time-frequency resource. The terminal needs to use the configured downlink resource to receive downlink data after the PDCCH control signaling activates the downlink resource configuration.

[0141] In the embodiments of the present disclosure, the Radio Link Control (RLC) entity is introduced as follows:

[0142] The RB of the terminal has a corresponding RLC entity for data transmission and reception. The types of RLC entities include the following:

[0143] Transparent Mode (TM): RLC data without packet header, directly transmitted through the RLC layer;

[0144] Unacknowledged Mode (UM): The data transmitted by the RLC layer, the sending end does not need to receive the confirmation information of the receiving end.

[0145] Acknowledged Mode (AM): The data transmitted by the RLC layer, the sending end needs to receive the confirmation information of the receiving end.

[0146] In the embodiments of the present disclosure, one RB can be configured with one or more RLC entities, and when the RB is reconfigured with multiple RLC entities, the RB can be referred to as a split bearer.

[0147] In some embodiments, when the terminal is receiving downlink data or sending uplink data, the packet header (i.e., subheader) in the MAC subPDU contains a large amount of control information field, such as the L field and / or the LCID field, resulting in a lot of signaling loss.

[0148] In order to reduce the signaling loss during data transmission and reception and improve the efficiency of data transmission and reception, the present disclosure provides the following communication method, terminal, network device, system and storage medium.

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

[0150] Step S2101, the network device 102 sends downlink control information (DCI) to the terminal 101.

[0151] In some embodiments, the terminal 101 receives the DCI.

[0152] In some embodiments, the DCI is used for scheduling the first resource.

[0153] In one example, the first resource is an uplink resource, and the DCI format can include but is not limited to any one of the following: DCI format 0_0; DCI format 0_1; DCI format 0_2; DCI format 0_3; and the like.

[0154] In one example, the first resource is a downlink resource, and the DCI format can include but is not limited to any one of the following: DCI format 1_0; DCI format 1_1; DCI format 1_2; DCI format 1_3; and the like.

[0155] The above is only an exemplary description, and the present disclosure does not limit the DCI format.

[0156] In some embodiments, the DCI can be used to configure a corresponding data format for the dynamically scheduled first resource.

[0157] Alternatively, the first configuration information can be used to configure a data format corresponding to the first resource, and the first resource is a dynamically scheduled resource.

[0158] In the embodiments of the present disclosure, the DCI sent by the network device 102 can adopt a specific format of the above-mentioned DCI format 0_x and DCI format 1_x (wherein x is a non-negative integer), specifically, the DCI adopting the specific format can be used to schedule the first resource, and can be used to configure a data format corresponding to the first resource.

[0159] Optionally, the DCI in the specific format includes a reserved bit, and the reserved bit can be used to configure the above-mentioned data format.

[0160] In some embodiments, the DCI can include but is not limited to at least one of the following: first resource indication information; data format configuration information; control signaling indication information; and bearer information.

[0161] In one example, the first resource indication information can be used to configure the dynamically scheduled first resource.

[0162] Exemplarily, the first resource indication information can be used to indicate any of the following: time domain resource position and / or frequency domain resource position of a physical uplink shared channel (PUSCH) indicated by a DCI format 0_x (where x can be 0, 1, 2, or 3, etc.); time domain resource position and / or frequency domain resource position of a physical downlink shared channel (PDSCH) indicated by a DCI format 1_x (where x can be 0, 1, 2, or 3, etc.).

[0163] In one example, the data format configuration information can be used to configure a data format corresponding to the first resource.

[0164] Exemplarily, the data format configured by the data format configuration information can be indicated by a reserved bit in the DCI.

[0165] Exemplarily, the data format configured by the data format configuration information can include, but is not limited to, any of the following: a first format; a second format; a third format; a fourth format.

[0166] Wherein, the subheader of the sub-PDU (i.e. MAC sub-PDU) of the data packet of the first format only includes a first information field, and the first information field can be used to indicate whether there are other sub-PDUs following. That is, the first information field can be an E field.

[0167] Wherein, the sub-PDU of the data packet of the first format does not include an L field and an LCID field.

[0168] Wherein, the first format can be as shown in FIG. 4A, and the MAC subheader only includes an E field. Of course, in order to ensure that the length of the subheader is 1 byte (i.e. 8 bits), an R field is also included in addition to the E field.

[0169] Exemplarily, the data packet of the first format can be used to send MAC SDUs of fixed data length and from the same logical channel.

[0170] Exemplarily, the subheader of the sub-PDU (i.e. MAC sub-PDU) of the data packet of the second format only includes a first information field and a second information field, the first information field can be used to indicate whether there are other sub-PDUs following, i.e. the first information field can be an E field. The second information field can be used to indicate a logical channel identifier, i.e. the second information field can be an LCID field.

[0171] Wherein, the sub-PDU of the data packet of the second format does not include an L field.

[0172] The second format can be, for example, as shown in FIG. 4B, and the MAC subheader only includes the E field and the LCID field. Of course, in order to ensure that the length of the subheader is 1 byte (i.e., 8 bits), the R field can also be included in addition to the E field and the LCID field.

[0173] Exemplarily, the data packet of the second format can be used to send a MAC SDU with a fixed data length.

[0174] Exemplarily, the subheader of the sub-PDU (i.e., MAC subPDU) of the data packet of the third format only includes a third information field, and the third information field can be used to indicate the length of the SDU, i.e., the third information field can be the L field.

[0175] The sub-PDU of the data packet of the third format does not include the E field and the LCID field.

[0176] The third format can be, for example, as shown in FIG. 4C, and the MAC subheader only includes the L field. Of course, in order to ensure that the length of the subheader is 1 byte (i.e., 8 bits), the R field can also be included in addition to the L field.

[0177] Exemplarily, the data packet of the third format can be used to send a MAC SDU from the same logical channel.

[0178] Exemplarily, the PDU of the data packet of the fourth format only includes one SDU.

[0179] The sub-PDU of the data packet of the fourth format does not include the L field, the E field, and the LCID field.

[0180] The fourth format can be, for example, as shown in FIG. 4D, and the MAC PDU only includes the MAC SDU.

[0181] Exemplarily, the data packet of the fourth format can be a transparent MAC PDU packet. The transparent MAC PDU packet only includes the SDU and does not include the MAC header.

[0182] Exemplarily, considering that the data packet quantity is 1, the fourth format can be used only when the data packet quantity is 1, and therefore, in the embodiments of the present disclosure, the quantity of the data packet of the fourth format transmitted each time can be limited to 1, thereby improving the reliability of data transmission.

[0183] The above is only an exemplary description, and the present disclosure does not limit the data format corresponding to the first resource.

[0184] In one example, the control signaling indication information can be used to indicate the configuration of the control information field in the data packet using the data format, i.e., the relevant configuration of the control information field in the MAC PDU packet using the data format corresponding to the first resource, including but not limited to: whether the control information field is included in the MAC PDU packet, and the specific control information field included.

[0185] The control signaling indication information can include but is not limited to at least one of the following: first indication information; second indication information; third indication information.

[0186] For example, the first indication information can be used to indicate whether the third information field exists in the subheader of the sub-PDU of the data packet, and the third information field can be used to indicate the length of the SDU, i.e., the third information field can be an L field.

[0187] When the bit value of the first indication information is a first value, it can be used to indicate that the L field exists in the subheader, and when the bit value is a second value, it can be used to indicate that the L field does not exist in the subheader. The first value can be 0 or 1, and the second value can be 1 or 0.

[0188] For example, when the bit value of the first indication information is "1", it can indicate that the L field exists in the subheader, and at this time the data format can be the third format described above.

[0189] For another example, when the bit value of the first indication information is "0", it can indicate that the L field does not exist in the subheader, and at this time the data format can be the first format, the second format, or the fourth format described above.

[0190] For example, the second indication information can be used to indicate whether the second information field exists in the subheader of the sub-PDU of the data packet, and the second information field can be used to indicate the length of the SDU logical channel identifier, i.e., the second information field can be an LCID field.

[0191] When the bit value of the second indication information is a first value, it can be used to indicate that the LCID field exists in the subheader, and when the bit value is a second value, it can be used to indicate that the LCID field does not exist in the subheader. The first value can be 0 or 1, and the second value can be 1 or 0.

[0192] For example, when the bit value of the second indication information is "1", it can indicate that the LCID field exists in the subheader, and at this time the data format can be the second format described above.

[0193] For another example, when the bit value of the second indication information is "0", it can indicate that the LCID field does not exist in the subheader, and at this time the data format can be the first format, the third format, or the fourth format described above.

[0194] Exemplarily, the third indication information can be used to indicate whether the first information field exists in the subheader of the sub-PDU of the data packet, and the first information field can be used to indicate whether there is still other sub-PDU, i.e., the first information field can be the E field.

[0195] Wherein, the bit value of the third indication information can be used to indicate that the E field exists in the subheader when the bit value is the first value, and can be used to indicate that the E field does not exist in the subheader when the bit value is the second value. Wherein, the first value can be 0 or 1, and the second value can be 1 or 0.

[0196] For example, the bit value of the third indication information can indicate that the E field exists in the subheader when the bit value is "1", and the data format can be the first format or the second format at this time.

[0197] For another example, the bit value of the third indication information can indicate that the E field does not exist in the subheader when the bit value is "0", and the data format can be the third format or the fourth format at this time.

[0198] Wherein, one, two or three of the above three indication information can be used to determine a data format.

[0199] For example, the bit value of the first indication information can indicate that the L field exists in the subheader when the bit value is "1", and the data format can be the third format at this time.

[0200] The bit value of the second indication information can indicate that the LCID field exists in the subheader when the bit value is "1", and the data format can be the second format at this time.

[0201] The bit value of the third indication information can indicate that the E field and the LCID field exist in the subheader when the bit value is "1" and the bit value of the second indication information is "1", and the data format can be the second format at this time.

[0202] The bit value of the third indication information can indicate that only the E field exists in the subheader when the bit value is "1" and the bit value of the second indication information is "0", and the data format can be the first format at this time.

[0203] The bit value of the third indication information can indicate that the E field and the LCID field exist in the subheader when the bit value is "1" and the bit value of the second indication information is "1", and the data format can be the second format at this time.

[0204] It can be understood that, in order to save signaling resources, the data format configuration information and the control signaling indication information can be included in the first configuration information.

[0205] Of course, in the case that the first configuration information includes both the data format configuration information and the control signaling indication information, the data format configuration information can indicate one of the data formats, or the control signaling indication information can determine a plurality of data formats based on the data format configuration information.

[0206] For example, the first indication information included in the control signaling indication information has a bit value of "1", and in this case, the data format can be determined as the third format described above. In addition, the data format configuration information also indicates the third format.

[0207] For another example, the third indication information included in the control signaling indication information has a bit value of "1", and in this case, the data format can be the first format or the second format described above. In this case, the data format configuration information indicates the first format.

[0208] In one example, the bearer information can be used to configure a bearer corresponding to the reception and transmission of the data packet on the first resource.

[0209] The bearer information can include, but is not limited to, at least one of the following: a session identifier; a data flow identifier; a radio bearer identifier; a logical channel identifier; and an RLC entity identifier.

[0210] The data flow can also be referred to as a Quality of Service flow (QoS).

[0211] The radio bearer identifier can include, but is not limited to, a DRB identifier. The RLC entity identifier can be an identifier of an RLC entity in a split bearer.

[0212] For example, the bearer information included in the DCI can directly indicate the identifier of the configured bearer, for example, indicating that the logical channel identifier corresponding to the data format is 6.

[0213] For example, the network device 102 can pre-configure the available bearer information through a Radio Resource Control (RRC) message, for example, configure a bearer list through an RRC message, and the bearer information included in the DCI can indicate the bearer number (or sequence number) in the bearer list.

[0214] For example, the bearer information includes a logical channel identifier, and the network device 102 pre-configures a logical channel list through an RRC message, and the list includes, in ascending order of number, number-1, logical channel-5, number-2, logical channel-3, number-3, logical channel-6, number-4, logical channel-9. If the logical channel identifier in the DCI is 3, the logical channel indicated by the DCI is the logical channel-6 with the number 3.

[0215] The above is only an example, and the disclosure does not limit the indication manner of the information carried in the DCI.

[0216] In some embodiments, a specific data format can be bound or associated with the first dynamically scheduled resource.

[0217] In the embodiments of the disclosure, the network device 102 can bind or associate the specific data format or formats with the scheduled first resource in the scheduling information, such as the DCI, when scheduling the first resource. The terminal 101 transmits uplink data using a data packet in the corresponding data format on the scheduled first resource, and / or receives downlink data on the scheduled first resource, and the format of the downlink data packet is the data format bound to the first resource. The data format can be better bound to the first resource by using the reserved bits in the DCI, without the need to bind it through separate scheduling information or control information, reducing the loss of control information during data transmission and reception, improving the flexibility of data transmission during data transmission and reception using dynamically scheduled resources, and improving the efficiency of data transmission and reception.

[0218] In step S2102, the network device 102 sends an RRC message to the terminal 101.

[0219] In some embodiments, the terminal 101 receives the RRC message.

[0220] In some embodiments, when the data format corresponding to the first resource does not include a third information field (i.e., an L field) used to indicate the length of the SDU, for example, when the data format corresponding to the first resource is the first format or the second format, the network device 102 can send a first RRC message to the terminal 101, and the first RRC message can be used to configure the length of the SDU.

[0221] In one example, the first RRC message can configure the length of the SDU to be N bytes, where N is a positive integer, for example, N is 20.

[0222] In some embodiments, when the data format corresponding to the first resource does not include a second information field (i.e., an LCID field) used to indicate the logical channel identifier, for example, when the data format corresponding to the first resource is the first format or the third format, the network device 102 can send a second RRC message to the terminal 101, and the second RRC message can be used to configure the bearer information of the SDU.

[0223] The content of the bearer information has been described in the foregoing embodiments, and will not be described here.

[0224] In some embodiments, the data format corresponding to the first resource is a fourth format, wherein only one SDU is included in a PDU of a data packet of the fourth format, and the network device 102 can send a second RRC message to the terminal 101, the second RRC message being used for configuring the bearer information of the SDU.

[0225] The content of the bearer information has been described in the foregoing embodiments, and will not be described here again.

[0226] In an example, the first RRC message and the second RRC message can be the same RRC message or different RRC messages, and the disclosure does not limit this.

[0227] In some embodiments, the data format corresponding to the first resource does not include a second information field (i.e., an LCID field) and a third information field (an L field), wherein the second information field is used to indicate a logical channel identifier, and the third information field is used to indicate an SDU length, i.e., the data format corresponding to the first resource is a first format (only including an E field), and at this time, the network device 102 can send the first RRC message and the second RRC message to the terminal 101, wherein the first RRC message can be used for configuring the length of the SDU, and the second RRC message is used for configuring the bearer information of the SDU.

[0228] In an example, the first RRC message and the second RRC message can be the same RRC message or different RRC messages, and the disclosure does not limit this.

[0229] It should be noted that step S2102 is an optional execution step. For example, when the network device 102 directly configures the length of the SDU and / or the growth information of the SDU through the DCI, step S2102 can not be executed. For another example, in order to save the signaling resource of the DCI, when the network device 102 does not configure the length of the SDU and / or the growth information of the SDU in the DCI, step S2102 can be executed.

[0230] In step S2103, the terminal 101 sends a first data packet to the network device 102.

[0231] In some embodiments, the first resource is an uplink resource, and the terminal 101 needs to send uplink data on the first resource, encapsulates the SDU received from the first bearer into a data packet according to the data format to obtain the first data packet, wherein the first bearer is a bearer corresponding to the data format, and further, the terminal 101 sends the first data packet to the network device 102.

[0232] In an example, the terminal 101 can assemble data packets in the following manner for different data formats:

[0233] For the first format, the manner in which the terminal 101 assembles the data packet includes but is not limited to at least one of the following:

[0234] Manner 1-1, the terminal 101 assembles the data from the specified bearer according to the first format shown in FIG. 4A to obtain the first data packet.

[0235] The specified bearer can be a bearer indicated by the bearer information in the DCI.

[0236] Manner 1-2, the terminal 101 assembles the data of a specified length from the specified bearer according to the first format shown in FIG. 4A to obtain the first data packet.

[0237] The specified bearer can be a bearer indicated by the bearer information in the DCI.

[0238] The specified size can be the length of the SDU indicated by the network device 102 through the DCI or the first RRC message.

[0239] For the second format, the manner in which the terminal 101 assembles the data packet includes:

[0240] Manner 2, the terminal 101 assembles the data of a specified size according to the second format shown in FIG. 4B to obtain the first data packet.

[0241] The specified size can be the length of the SDU indicated by the network device 102 through the DCI or the first RRC message.

[0242] For the third format, the manner in which the terminal 101 assembles the data packet includes:

[0243] Manner 3, the terminal 101 assembles the data from the specified bearer according to the third format shown in FIG. 4C to obtain the first data packet.

[0244] The specified bearer can be a bearer indicated by the bearer information in the DCI.

[0245] For the fourth format, the manner in which the terminal 101 assembles the data packet includes:

[0246] Manner 4-1, the terminal 101 assembles the data of a specified length from the specified bearer according to the fourth format shown in FIG. 4D to obtain the first data packet.

[0247] Manner 4-2, when the number of data packets from the specified bearer is 1, the terminal 101 assembles the data according to the fourth format shown in FIG. 4D to obtain the first data packet.

[0248] The specified bearer can be a bearer indicated by the bearer information in the DCI.

[0249] Correspondingly, for the network device 102, which needs to receive uplink data on the first resource, the network device 102 can send the received first data packet to the second bearer after unpacking, wherein the second bearer is a bearer corresponding to the data format (corresponding to the first resource).

[0250] In step S2104, the network device 102 sends the second data packet to the terminal 101.

[0251] In some embodiments, the first resource is a downlink resource, and the network device 102 needs to send downlink data on the first resource. The network device 102 encapsulates the received SDU from the second bearer into a data packet according to the data format to obtain the second data packet, wherein the second bearer is a bearer corresponding to the data format, and further, the network device 102 sends the second data packet to the terminal 101.

[0252] The network device 102 encapsulates the second data packet in a manner similar to that of the terminal 101 encapsulating the first data packet, which will not be described here.

[0253] Correspondingly, for the terminal 101, which needs to receive downlink data on the first resource, the terminal 101 can send the received second data packet to the second bearer after unpacking, wherein the second bearer is a bearer corresponding to the data format (corresponding to the first resource).

[0254] In some embodiments, the names of information and the like are not limited to the names described in the embodiments. The terms such as “information”, “message”, “signal”, “signaling”, “report”, “configuration”, “indication”, “instruction”, “command”, “channel”, “parameter”, “domain”, “field”, “symbol”, “symbol”, “codebook”, “codeword”, “code point”, “bit”, “data”, “program”, “chip”, and the like can be replaced with each other.

[0255] In some embodiments, the terms “downlink control information (DCI),” “downlink (DL) assignment,” “DL DCI,” “uplink (UL) grant,” “UL DCI,” and the like can be replaced with each other.

[0256] In some embodiments, the terms “acquire,” “obtain,” “get,” “receive,” “transmit,” “bidirectional transmission,” “send and / or receive,” and the like can be replaced with each other, which can be interpreted as receiving from other subjects, acquiring from protocols, acquiring from higher layers, obtaining by oneself, implementing autonomously, and the like.

[0257] In some embodiments, the terms “send,” “transmit,” “report,” “issue,” “transmit,” “bidirectional transmission,” “send and / or receive,” and the like can be replaced with each other.

[0258] The communication method related to the embodiments of the present disclosure can include at least one of steps S2101-S2104. For example, step S2101 can be implemented as an independent embodiment, step S2102 can be implemented as an independent embodiment, steps S2101+S2102 can be implemented as an independent embodiment, step S2103 can be implemented as an independent embodiment, step S2104 can be implemented as an independent embodiment, steps S2103+S2104 can be implemented as an independent embodiment, steps S2101-S2104 can be implemented as an independent embodiment, but not limited thereto.

[0259] In some embodiments, steps S2101-S2104 are optional, and one or more of these steps can be omitted or replaced in different embodiments.

[0260] In some embodiments, the execution order of steps S2101-S2104 is not limited.

[0261] In the above embodiments, a specific data format can be associated with dynamic scheduling resources, thereby reducing signaling loss when a terminal transmits and receives data through dynamic scheduling resources, improving data transmission and reception efficiency, improving spectrum usage, and having high availability.

[0262] In some embodiments, the above step S2101 can be performed alone, for example, when a specific data format(s) is bound or associated with the first resource of dynamic scheduling, the network device 102 can schedule the first resource for the terminal 101 through DCI, and the DCI can include but is not limited to at least one of the following: the scheduled first resource; and indication information, which can be used to indicate the data format when data is transmitted or received using the first resource (for example, the indication information can be data format indication information or control signaling indication information). For example, the uplink resource #1 scheduled by the DCI corresponds to the first format. When the terminal transmits uplink data using the uplink resource #1, the data format thereof can be the first format. For another example, the downlink resource #1 scheduled by the DCI corresponds to the second format. When the terminal receives downlink data using the downlink resource #1, it can be determined that the data format thereof is the second format.

[0263] Correspondingly, the above steps S2102 to S2104 can be omitted. For example, the first resource includes a time slot #n, and the current time slot is # (n-4), and the above steps S2102 to S2104 can not be performed.

[0264] In the above embodiments, the loss of control information when data is transmitted or received is reduced, the utilization rate of DCI is improved, and the flexibility of data transmission is improved, and the availability is high.

[0265] FIG. 3A is an interaction diagram of a communication method according to an embodiment of the present disclosure. As shown in FIG. 3A, the embodiment of the present disclosure relates to a communication method, and the above method is performed by the terminal 101, and the method includes:

[0266] Step S3101, obtaining DCI.

[0267] In some embodiments, the DCI can be used to configure the corresponding data format for the scheduled first resource.

[0268] In some embodiments, the terminal 101 can obtain the DCI from the network device 102, but is not limited thereto, and can also receive the DCI sent by other subjects.

[0269] In some embodiments, the terminal 101 obtains the DCI specified by a protocol.

[0270] In some embodiments, the terminal 101 obtains the DCI from the upper layer(s).

[0271] In some embodiments, the terminal 101 processes to obtain the DCI.

[0272] In some embodiments, step S3101 is omitted, and the terminal 101 autonomously implements the function indicated by the DCI, or the terminal 101 acquires the DCI based on a predefined rule or protocol agreement, or the above function is default or default.

[0273] In some embodiments, the optional implementation of step S3101 can refer to the optional implementation of step S2101 in FIG. 2 and other associated parts in the embodiments involved in FIG. 2, which will not be repeated here.

[0274] Step S3102, acquiring an RRC message.

[0275] In some embodiments, the first RRC message can be used to configure the length of the SDU.

[0276] In some embodiments, the second RRC message can be used to configure the bearer information of the SDU.

[0277] In some embodiments, the first RRC message and the second RRC message can be the same RRC message or different RRC messages.

[0278] In some embodiments, the terminal 101 can acquire the above RRC message from the network device 102, but is not limited thereto, and can also receive an RRC message sent by other subjects.

[0279] In some embodiments, the terminal 101 acquires the RRC message specified by the protocol.

[0280] In some embodiments, the terminal 101 acquires the RRC message from the upper layer(s).

[0281] In some embodiments, the terminal 101 processes to obtain the RRC message.

[0282] In some embodiments, step S3101 is omitted, and the terminal 101 autonomously implements the function indicated by the RRC message, or the terminal 101 acquires the RRC message based on a predefined rule or protocol agreement, or the above function is default or default.

[0283] In some embodiments, the optional implementation of step S3102 can refer to the optional implementation of step S2102 in FIG. 2 and other associated parts in the embodiments involved in FIG. 2, which will not be repeated here.

[0284] Step S3103, sending a first data packet.

[0285] In some embodiments, the terminal 101 sends the first data packet to the network device 102.

[0286] In some embodiments, the network device 102 receives the first data packet.

[0287] In some embodiments, optional implementation of step S3103 can refer to optional implementation of step S2103 in FIG. 2 and other associated parts in the embodiments involved in FIG. 2, which will not be repeated here.

[0288] Step S3104: obtaining a second data packet.

[0289] In some embodiments, the terminal 101 can obtain the second data packet from the network device 102, but is not limited thereto, and can also receive the second data packet sent by other subjects.

[0290] In some embodiments, the terminal 101 obtains the second data packet specified by a protocol.

[0291] In some embodiments, the terminal 101 obtains the second data packet from upper layer(s).

[0292] In some embodiments, the terminal 101 processes to obtain the second data packet.

[0293] In some embodiments, step S3104 is omitted, and the terminal 101 autonomously implements the function indicated by the second data packet, or the terminal 101 obtains the second data packet based on a pre-defined rule or protocol agreement, or the above function is default or default.

[0294] In some embodiments, optional implementation of step S3104 can refer to optional implementation of step S2104 in FIG. 2 and other associated parts in the embodiments involved in FIG. 2, which will not be repeated here.

[0295] In some embodiments, steps S3101 to S3104 are optional, and one or more of the steps can be omitted or replaced in different embodiments.

[0296] In some embodiments, the execution order of steps S3101 to S3104 is not limited.

[0297] In the above embodiments, a specific data format can be associated with a dynamic scheduling resource, and information not provided in DCI can be configured through an RRC message to save signaling resources of DCI, reduce signaling loss when the terminal transmits and receives data through the dynamic scheduling resource, improve data transmission efficiency, improve spectrum usage, and have high availability.

[0298] FIG. 3B is an interaction schematic diagram of a communication method according to an embodiment of the present disclosure. As shown in FIG. 3B, the embodiment of the present disclosure relates to a communication method, and the above method is performed by the terminal 101, and the method comprises:

[0299] Step S3201: Obtain the DCI.

[0300] In some embodiments, the DCI can be used to configure the corresponding data format for the scheduled first resource.

[0301] In some embodiments, the terminal 101 can obtain the DCI from the network device 102, but is not limited thereto, and can also receive the DCI sent by other subjects.

[0302] In some embodiments, the terminal 101 obtains the DCI specified by the protocol.

[0303] In some embodiments, the terminal 101 obtains the DCI from the upper layer(s).

[0304] In some embodiments, the terminal 101 processes to obtain the DCI.

[0305] In some embodiments, step S3201 is omitted, and the terminal 101 autonomously implements the function indicated by the DCI, or the terminal 101 obtains the DCI based on a predefined rule or protocol agreement, or the above function is default or default.

[0306] In some embodiments, the optional implementation of step S3201 can refer to the optional implementation of step S2101 in FIG. 2 and other associated parts in the embodiments involved in FIG. 2, which will not be repeated here.

[0307] In the above embodiments, a specific data format can be associated with a dynamically scheduled resource, reducing signaling loss when the terminal transmits and receives data through the dynamically scheduled resource, improving data transmission efficiency, improving spectrum utilization, and having high availability.

[0308] FIG. 3C is an interaction diagram of a communication method according to an embodiment of the present disclosure. As shown in FIG. 3C, the embodiment of the present disclosure relates to a communication method, and the above method is performed by the network device 102, and the method comprises the following steps:

[0309] Step S3301: Send the DCI.

[0310] In some embodiments, the DCI can be used to configure the corresponding data format for the scheduled first resource.

[0311] In some embodiments, the network device 102 sends the DCI to the terminal 101.

[0312] In some embodiments, the terminal 101 obtains the DCI.

[0313] In some embodiments, the optional implementation of step S3301 can refer to the optional implementation of step S2101 in FIG. 2 and other associated parts in the embodiments related to FIG. 2, which will not be repeated here.

[0314] In step S3302, an RRC message is sent.

[0315] In some embodiments, the first RRC message can be used to configure the length of the SDU.

[0316] In some embodiments, the second RRC message can be used to configure the bearer information of the SDU.

[0317] In some embodiments, the first RRC message and the second RRC message can be the same RRC message or different RRC messages.

[0318] In some embodiments, the network device 102 sends the above-mentioned RRC message to the terminal 101.

[0319] In some embodiments, the terminal 101 receives the above-mentioned RRC message.

[0320] In some embodiments, the optional implementation of step S3302 can refer to the optional implementation of step S2102 in FIG. 2 and other associated parts in the embodiments related to FIG. 2, which will not be repeated here.

[0321] In step S3303, a first data packet is obtained.

[0322] In some embodiments, the network device 102 can obtain the first data packet from the terminal 101, but is not limited thereto, and can also receive the first data packet sent by other subjects.

[0323] In some embodiments, the network device 102 obtains the first data packet specified by a protocol.

[0324] In some embodiments, the network device 102 obtains the first data packet from an upper layer.

[0325] In some embodiments, the network device 102 processes to obtain the first data packet.

[0326] In some embodiments, step S3303 is omitted, and the network device 102 autonomously implements the function indicated by the first data packet, or the network device 102 obtains the first data packet based on a predefined rule or protocol agreement, or the above-mentioned function is default or default.

[0327] In some embodiments, the optional implementation of step S3303 can refer to the optional implementation of step S2103 in FIG. 2 and other associated parts in the embodiments related to FIG. 2, which will not be repeated here.

[0328] Step S3304, sending the second data packet.

[0329] In some embodiments, the network device 102 sends the second data packet to the terminal 101.

[0330] In some embodiments, the terminal 101 receives the second data packet.

[0331] In some embodiments, the optional implementation of step S3304 can refer to the optional implementation of step S2104 in FIG. 2 and other associated parts in the embodiments involved in FIG. 2, which will not be repeated here.

[0332] In some embodiments, steps S3301 to S3304 are optional, and one or more of these steps can be omitted or replaced in different embodiments.

[0333] In some embodiments, the execution order of steps S3301 to S3304 is not limited.

[0334] In the above embodiments, the network device can associate a specific data format with the dynamic scheduling resource through the DCI, and can configure the information not provided in the DCI through the RRC message, saving the signaling resource of the DCI, reducing the signaling loss when the terminal transmits and receives data through the dynamic scheduling resource, improving the data transmission efficiency, improving the frequency spectrum utilization rate, and having high availability.

[0335] FIG. 3D is an interaction schematic diagram of a communication method according to an embodiment of the present disclosure. As shown in FIG. 3D, the embodiment of the present disclosure relates to a communication method, and the above method is performed by the network device 102, and the method comprises:

[0336] Step S3401, sending a DCI.

[0337] In some embodiments, the DCI can be used to configure a corresponding data format for the scheduled first resource.

[0338] In some embodiments, the network device 102 sends the DCI to the terminal 101.

[0339] In some embodiments, the terminal 101 receives the DCI.

[0340] In some embodiments, the optional implementation of step S3401 can refer to the optional implementation of step S2101 in FIG. 2 and other associated parts in the embodiments involved in FIG. 2, which will not be repeated here.

[0341] In the above embodiments, the network device can associate a specific data format with a dynamically scheduled resource, thereby reducing signaling loss when the terminal transmits or receives data through the dynamically scheduled resource, improving data transmission efficiency, improving spectrum utilization, and having high availability.

[0342] The above process is further illustrated as follows.

[0343] The network side (i.e., the network device) dynamically indicates the data format information used on the "downlink reception resource" or "uplink transmission resource" in the downlink control signaling, so that the terminal can receive downlink data or transmit uplink data through a specific data format, thereby reducing signaling loss when transmitting or receiving data.

[0344] The network side indicates the data format of the downlink data reception or uplink data transmission to the terminal through the downlink control information.

[0345] The "downlink control information" includes the following information:

[0346] 1, resource indication information.

[0347] 2, data format information. The "data format information" includes at least one of the following:

[0348] 2-1, data format type indication information:

[0349] Data format type 1: The subheader of the MAC subPDU only includes the "subsequent MAC subPDU indication field".

[0350] Data format type 2: The subheader of the MAC subPDU only includes the "subsequent MAC subPDU indication field" and the "logical channel identification field".

[0351] Data format type 3: The subheader of the MAC subPDU only includes the "L" field. (For example, the MAC subPDU does not include the "LCID" field.

[0352] Data format type 4: The MAC PDU has only one MAC SDU (for example, using "transparent MAC").

[0353] 2-2, control signaling indication information, including:

[0354] Length field indication;

[0355] Logical channel identification indication;

[0356] Subsequent MAC subPDU identification indication.

[0357] 2-3, bearer information.

[0358] When the terminal receives the downlink control information (e.g., DCI) indicating the data format (e.g., “Data format type 1”) of the downlink data reception or uplink data transmission to the terminal, the terminal receives the downlink data or transmits the uplink data according to the specified physical resource (e.g., PUSCH) in the downlink control information, and decodes the data or assembles the data packet (e.g., MAC PDU) according to the specified data format.

[0359] Terminal side: When the terminal receives the downlink control information indicating the data format of the downlink data reception or uplink data transmission to the terminal, the terminal receives the downlink data or transmits the uplink data according to the specified physical resource in the downlink control information, and decodes the data or assembles the data packet according to the specified data format.

[0360] Network side: The network side indicates the data format of the downlink data reception or uplink data transmission to the terminal through the downlink control information.

[0361] Embodiment 1, the process of downlink data reception is shown in Figure 4E, including the following steps:

[0362] Step S4501, the network side indicates the data format of the downlink data reception to the terminal through the downlink control information. For example, the format of the MAC data packet of the PDSCH received in the specified downlink resource is indicated through the DCI.

[0363] Wherein, the “downlink control information” includes the following information:

[0364] 1, “downlink resource indication information” (e.g., the time or frequency resource position of the PDSCH indicated by the DCI Format 1_0 / 1_1 / 1_2 / 1_3).

[0365] 2, “data format information of downlink data reception”. Wherein, the “data format information of downlink data reception” (e.g., indicated by the reserved bit of the DCI Format 1_0 / 1_1 / 1_2 / 1_3) includes at least one of the following:

[0366] 2-1, data format type indication information. Wherein, the “data format type indication information” includes any one of the following:

[0367] Data format type 1: The subheader of the MAC subPDU only includes “subsequent MAC subPDU indication field”, for example, as shown in Figure 4A.

[0368] Data format type 2: The subheader of the MAC subPDU only includes the "subsequent MAC subPDU indication field" and the "logical channel identification field", for example, as shown in FIG. 4B.

[0369] Data format type 3: The subheader of the MAC subPDU only includes the "L" field. (For example, the MAC subPDU does not include the "LCID" field, for example, as shown in FIG. 4C.

[0370] Data format type 4: The MAC PDU has only one MAC SDU (for example, using "transparent MAC"), for example, as shown in FIG. 4D.

[0371] 2-2, control signaling indication information (for example, indication information used to indicate whether a certain control signaling field (for example, the L field) in the subheader of the MAC subPDU exists). Wherein the "control signaling indication information" includes at least one of the following:

[0372] Length field indication (for example, a value of "1" indicates that the L field exists, and a value of "0" indicates that the L field does not exist);

[0373] Logical channel identification indication (for example, a value of "1" indicates that the LCID field exists, and a value of "0" indicates that the LCID field does not exist);

[0374] Subsequent MAC subPDU identification indication (for example, a value of "1" indicates that the "subsequent MAC subPDU identification" field exists, and a value of "0" indicates that the "subsequent MAC subPDU identification" field does not exist. Note that the "subsequent MAC subPDU identification" field is used to indicate in the subheader of the MAC subPDU whether there are other MAC subPDUs after this MAC subPDU).

[0375] 2-3, bearer information. Wherein the "bearer information" (for the following identification information, the network side can first configure through the RRC message, and sort the identification in the identification list. When indicated by the DCI, the DCI indicates the sorting number of the identification in the identification list. For example, the network side configures multiple logical channels for the terminal, and the sorting of the multiple logical channels in the RRC message configuration signaling is (LCID=5 / 3 / 6 / 9). When the DCI indicates the sorting number 3 of the logical channel identification, it means that the network side currently uses the logical channel with LCID=6) includes at least one of the following:

[0376] Session identification (for example, Session identification);

[0377] Data flow identification (for example, QoS flow identification);

[0378] a radio bearer identity (e.g. DRB identity);

[0379] a logical channel identity (e.g. LCID identity);

[0380] an RLC entity identity (e.g. one of the RLC entities for a split bearer).

[0381] When the “data format” does not include a “length indication field” (e.g. does not include the “L” field of the subheader of a MAC subPDU, but includes the “LCID” field), the RRC configuration information provided by the network to the terminal includes:

[0382] a data length of the MAC SDU using the “data format” (e.g. 20 bytes).

[0383] When the “data format” does not include a “logical channel identity field” (e.g. does not include the “LCID” field of the subheader of a MAC subPDU, but includes the “L” field), the RRC configuration information provided by the network to the terminal includes:

[0384] corresponding “bearer information” of the MAC SDU using the “data format”. The “bearer information” is the same as above.

[0385] When the “data format” does not include a “length indication field” and a “logical channel identity field” (e.g. does not include the “L” field and the “LCID” field of the subheader of a MAC subPDU), but includes a “subsequent MAC subPDU indication field”, the RRC configuration information provided by the network to the terminal includes at least one of:

[0386] a data length of the MAC SDU using the “data format” (e.g. 20 bytes);

[0387] corresponding “bearer information” of the MAC SDU using the “data format”. The “bearer information” is the same as above.

[0388] When the “data format” includes only one MAC SDU, the RRC configuration information provided by the network to the terminal includes:

[0389] corresponding “bearer information” of the MAC SDU using the “data format”. The “bearer information” is the same as above.

[0390] At step S4502, according to the configuration in step S4501, the network device sends a second data packet to the terminal.

[0391] When the terminal receives the downlink control information (e.g., DCI) indicating the data format (e.g., "Data Format Type 1") of the downlink data reception to the terminal, the terminal receives the downlink data on the specified physical resource (e.g., PDSCH) according to the downlink control information, decodes the data (e.g., decodes the received MAC PDU) according to the specified data format, and delivers the decoded data (e.g., MAC SDU) to the bearer corresponding to the specified data format (e.g., LCID corresponding to the MAC SDU).

[0392] Embodiment 2, the process of uplink data transmission is shown in FIG. 4F, including the following steps:

[0393] Step S4601, the network side indicates the data format of the uplink data transmission to the terminal through the downlink control information. For example, the format of the MAC data packet transmitted on the specified uplink resource (PUSCH) is indicated through the DCI.

[0394] The "downlink control information" includes the following information:

[0395] 1. "Uplink resource indication information" (e.g., the time or frequency resource position of PUSCH indicated by DCI Format 0_0 / 0_1 / 0_2 / 0_3).

[0396] 2. "Data format information of uplink data transmission". The "data format information of uplink data transmission" (e.g., indicated by the reserved bit of DCI Format 0_0 / 0_1 / 0_2 / 0_3) includes at least one of the following:

[0397] 2-1. Data format type indication information. The "data format type indication information" includes any of the following:

[0398] Data format type 1: The subheader of the MAC subPDU only includes the "subsequent MAC subPDU indication field".

[0399] Data format type 2: The subheader of the MAC subPDU only includes the "subsequent MAC subPDU indication field" and the "logical channel identification field".

[0400] Data format type 3: The subheader of the MAC subPDU only includes the "L" field. (e.g., the MAC subPDU does not include the "LCID" field.

[0401] Data format type 4: The MAC PDU has only one MAC SDU (e.g., using "transparent MAC").

[0402] 2-2, Control signaling indication information (e.g., indication information used to indicate whether a certain control signaling field (e.g., L field) in the subheader of the MAC subPDU exists or not). Wherein, the "control signaling indication information" includes at least one of the following:

[0403] Length field indication (e.g., taking the value "1" to indicate that the L field exists, and taking the value "0" to indicate that the L field does not exist);

[0404] Logical channel identification indication (e.g., taking the value "1" to indicate that the LCID field exists, and taking the value "0" to indicate that the LCID field does not exist);

[0405] Subsequent MAC subPDU identification indication (e.g., taking the value "1" to indicate that the "subsequent MAC subPDU identification" field exists, and taking the value "0" to indicate that the "subsequent MAC subPDU identification" field does not exist. Note that the "subsequent MAC subPDU identification" field is used to indicate in the subheader of the MAC subPDU whether there is another MAC subPDU after this MAC subPDU).

[0406] 2-3, Bearer information. Wherein, the "bearer information" (for the following identification information, the network side can first configure through the RRC message, and sort the identification in the identification list. When indicated through the DCI, the DCI indicates the sorting number of the identification in the identification list. For example, the network side configures multiple logical channels for the terminal, and the sorting of the multiple logical channels in the RRC message configuration signaling is (LCID = 5 / 3 / 6 / 9). When the DCI indicates the sorting number 3 of the logical channel identification, it means that the network side currently uses the logical channel with LCID = 6) includes at least one of the following:

[0407] Session identification (e.g., Session identification);

[0408] Data flow identification (e.g., QoS flow identification);

[0409] Radio bearer identification (e.g., DRB identification);

[0410] Logical channel identification (e.g., LCID identification);

[0411] RLC entity identification (e.g., for one of the RLC entities of the split bearer).

[0412] Wherein, when the "data format" does not include the "length indication field" (e.g., does not include the "L" field of the subheader of the MAC subPDU, but includes the "LCID" field.), the RRC configuration information provided by the network side to the terminal includes:

[0413] a data length of the MAC SDU using the "data format" (e.g., 20 bytes).

[0414] When the "data format" does not include the "logical channel identification field" (e.g., does not include the "LCID" field of the subheader of the MAC subPDU, but includes the "L" field), the RRC configuration information provided by the network side to the terminal includes:

[0415] corresponding "bearer information" of the MAC SDU using the "data format". Wherein the "bearer information" is the same as above.

[0416] When the "data format" does not include the "length indication field" and the "logical channel identification field" (e.g., does not include the "L" field and the "LCID" field of the subheader of the MAC subPDU), but includes the "subsequent MAC subPDU indication field", the RRC configuration information provided by the network side to the terminal includes at least one of the following:

[0417] a data length of the MAC SDU using the "data format" (e.g., 20 bytes);

[0418] corresponding "bearer information" of the MAC SDU using the "data format". Wherein the "bearer information" is the same as above.

[0419] When the "data format" includes only one MAC SDU, the RRC configuration information provided by the network side to the terminal includes:

[0420] corresponding "bearer information" of the MAC SDU using the "data format". Wherein the "bearer information" is the same as above. Wherein it can be further agreed that the number of packets corresponding to the "bearer" on the terminal side when the terminal uses the "data format" is 1.

[0421] Step S4602, according to the configuration in step S4601, the terminal sends the first data packet to the network device.

[0422] When the terminal receives the downlink control information (e.g., DCI) indicating the data format (e.g., "data format type 1") of the uplink data transmission to the terminal, the terminal transmits the uplink data according to the specified physical resource (e.g., PUSCH) in the downlink control information, and assembles the data packet (e.g., MAC PDU) according to the specified data format. Wherein the "assembling the data packet according to the specified data format" includes any of the following:

[0423] 1. For "data format type 1", the method of assembling the data packet by the terminal includes any of the following:

[0424] The terminal assembles data from a specified bearer (e.g., LCID = 1) according to "Data Format Type 1";

[0425] The terminal assembles data of a specified size (e.g., MAC SDU length = 20 bytes) from a specified bearer (e.g., LCID = 1) according to "Data Format Type 1".

[0426] 2. For "Data Format Type 2", the method for the terminal to assemble a data packet includes:

[0427] The terminal assembles data of a specified size (e.g., MAC SDU length = 20 bytes) according to "Data Format Type 2".

[0428] 3. For "Data Format Type 3", the method for the terminal to assemble a data packet includes:

[0429] The terminal assembles data from a specified bearer (e.g., LCID = 1) according to "Data Format Type 3".

[0430] 4. For "Data Format Type 4", the method for the terminal to assemble a data packet includes any one of:

[0431] The terminal assembles data from a specified bearer (e.g., LCID = 1) according to "Data Format Type 4";

[0432] When the number of data packets from a specified bearer (e.g., LCID = 1) is 1, the terminal assembles according to "Data Format Type 4".

[0433] In the embodiments of the present disclosure, part or all of the steps, and optional implementation manners thereof, can be combined with part or all of the steps in other embodiments, or can be combined with optional implementation manners of other embodiments.

[0434] The embodiments of the present disclosure also propose an apparatus for implementing any one of the above methods, for example, an apparatus including units or modules for implementing each step performed by the terminal in any one of the above methods. For another example, another apparatus is proposed, including units or modules for implementing each step performed by the network device in any one of the above methods.

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

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

[0437] FIG. 5A is a structural schematic diagram of a terminal according to an embodiment of the present disclosure. As shown in FIG. 5A, the terminal 5100 can include a transceiver module 5101.

[0438] In some embodiments, the transceiver module 5101 is configured to receive a downlink control information (DCI) sent by a network device, wherein the DCI is used to configure a corresponding data format for a scheduled first resource; and transmit a first data packet using the data format on the first resource, and / or receive a second data packet using the data format.

[0439] Optionally, the transceiver module 5101 is configured to perform at least one of the communication steps (for example, steps S2101, S2102, S2103, and S2104, but not limited thereto) of the terminal 5100 in any one of the above methods, and details are not described herein.

[0440] FIG. 5B is a structural schematic diagram of a network device according to an embodiment of the present disclosure. As shown in FIG. 5B, the network device 5200 can include a transceiver module 5201.

[0441] In some embodiments, the transceiver module 5201 is configured to send, to the terminal, a downlink control information (DCI); wherein the DCI is used to configure a corresponding data format for a scheduled first resource; and receive a first data packet using the data format on the first resource, and / or send a second data packet using the data format on the first resource.

[0442] Optionally, the transceiver module 5201 is configured to perform at least one of the communication steps (for example, steps S2101, S2102, S2103, S2104, but not limited thereto) of sending and / or receiving performed by the network device 5200 in any of the above methods, which will not be described here.

[0443] In some embodiments, the sending module and / or the receiving module can be referred to as a transceiver module, and the sending module and the receiving module can be separate or integrated together. Optionally, the transceiver module can be mutually replaced with the transceiver.

[0444] FIG. 6A is a structural schematic diagram of a communication device 6100 according to the embodiments of the present disclosure. The communication device 6100 can be a terminal (for example, a user equipment, a vehicle, an Internet of Things device, etc.) or a network device (for example, an access network device, a core network device, etc.), and can also be a chip, a chip system, or a processor supporting the terminal to implement any of the above methods, and can also be a chip, a chip system, or a processor supporting the network device to implement any of the above methods. The communication device 6100 can be used to implement the methods described in the above method embodiments, and specific implementation can be referred to the descriptions in the above method embodiments.

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

[0446] In some embodiments, the communication device 6100 further includes one or more transceivers 6102. When the communication device 6100 includes one or more transceivers 6102, the transceiver 6102 performs at least one of the communication steps (for example, steps S2101, steps S2102, steps S2103, steps S2104, but not limited to) in the above-described methods, and the processor 6101 performs at least one of the other steps. In alternative embodiments, the transceiver can include a receiver and / or a transmitter, which can be separate or integrated together. Alternatively, the terms transceiver, transceiving unit, transceiver, transceiving circuit, interface circuit, interface, etc. can be replaced with each other, the terms transmitter, transmitting unit, transmitter, transmitting circuit, etc. can be replaced with each other, and the terms receiver, receiving unit, receiver, receiving circuit, etc. can be replaced with each other.

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

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

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

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

[0451] In some embodiments, the chip 6200 further includes one or more interface circuits 6202. Optionally, the terms interface circuit, interface, transceiver pin, etc. can replace each other. In some embodiments, the chip 6200 further includes one or more memories 6203 for storing data. Optionally, all or part of the memory 6203 can be outside the chip 6200. Optionally, the interface circuit 6202 is connected with the memory 6203, the interface circuit 6202 can be configured to receive data from the memory 6203 or other devices, and the interface circuit 6202 can be configured to send data to the memory 6203 or other devices. For example, the interface circuit 6202 can read the data stored in the memory 6203 and send the data to the processor 6201.

[0452] In some embodiments, the interface circuit 6202 performs at least one of the communication steps (for example, step S2101, step S2102, step S2103, step S2104, but not limited to) such as sending and / or receiving in the above methods. The interface circuit 6202 performing the communication steps such as sending and / or receiving in the above methods means that the interface circuit 6202 performs data interaction between the processor 6201, the chip 6200, the memory 6203 or the transceiver device. In some embodiments, the processor 6201 performs at least one of the other steps.

[0453] The modules and / or devices described in each of the embodiments of the virtual device, the physical device, the chip, etc. can be combined or separated as appropriate. Optionally, part or all of the steps can also be performed by multiple modules and / or devices, which are not limited herein.

[0454] The disclosure also proposes a storage medium, and the above storage medium stores instructions, when the instructions run on the communication device 6100, the communication device 6100 performs any of the above methods. Optionally, the above storage medium is an electronic storage medium. Optionally, the above storage medium is a computer readable storage medium, but is not limited to this, it can also be a storage medium readable by other devices. Optionally, the above storage medium can be a non-transitory storage medium, but is not limited to this, it can also be a transitory storage medium.

[0455] The disclosure also proposes a program product, and the above program product is executed by the communication device 6100, so that the communication device 6100 performs any of the above methods. Optionally, the above program product is a computer program product.

[0456] The disclosure also proposes a computer program, when it runs on a computer, it makes the computer perform any of the above methods.

[0457] Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the features disclosed herein. It is intended that the specification and examples be considered as exemplary only, with the true scope and spirit of the disclosure being indicated by the following claims.

[0458] Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the features disclosed herein. It is intended that the specification and examples be considered as exemplary only, with the true scope and spirit of the disclosure being indicated by the following claims.

[0459] It is to be understood that the disclosure is not limited to the precise construction described above and shown in the attached drawings, and that various modifications and changes can be made without departing from the scope thereof. The scope of the disclosure is limited only by the claims that follow.

Claims

1. A communication method characterized by comprising: The method is performed by a terminal, and the method comprises: receiving a downlink control information (DCI) sent by a network device; wherein the DCI is used to configure a corresponding data format for a scheduled first resource; sending a first data packet using the data format on the first resource, and / or receiving a second data packet using the data format.

2. The method of claim 1, wherein, The DCI comprises at least one of: first resource indication information; data format configuration information; control signaling indication information, wherein the control signaling indication information is used to indicate the configuration of a control information field in a data packet of the data format; bearer information.

3. The method according to claim 1 or 2, characterized in that, The data format comprises any one of: a first format, wherein a subheader of a sub-protocol data unit (PDU) of a data packet of the first format only comprises a first information field, wherein the first information field is used to indicate whether there are other sub-PDUs after the first information field; a second format, wherein a subheader of a sub-PDU of a data packet of the second format only comprises a first information field and a second information field, wherein the first information field is used to indicate whether there are other sub-PDUs, and the second information field is used to indicate a logical channel identifier; a third format, wherein a subheader of a sub-PDU of a data packet of the third format only comprises a third information field, wherein the third information field is used to indicate the length of a service data unit (SDU); a fourth format, wherein a PDU of a data packet of the fourth format only comprises one SDU.

4. The method of claim 2, wherein, The control signaling indication information comprises at least one of: first indication information, wherein the first indication information is used to indicate whether a third information field exists in a subheader of a sub-PDU of a data packet, and the third information field is used to indicate the length of an SDU; second indication information, wherein the second indication information is used to indicate whether a second information field exists in a subheader of a sub-PDU of a data packet, and the second information field is used to indicate a logical channel identifier; third indication information, wherein the third indication information is used to indicate whether a first information field exists in a subheader of a sub-PDU of a data packet, and the first information field is used to indicate whether there are other sub-PDUs after the first information field.

5. The method according to claim 3 or 4, characterized in that, The method further comprises at least one of: the data format does not comprise a third information field, and a first radio resource control (RRC) message sent by the network device is received, wherein the third information field is used to indicate the length of an SDU, and wherein the first RRC message is used to configure the length of the SDU; the data format does not comprise a second information field, and a second RRC message sent by the network device is received, wherein the second information field is used to indicate a logical channel identifier, and wherein the second RRC message is used to configure bearer information of the SDU; the data format is a fourth format, and a second RRC message sent by the network device is received, wherein a PDU of a data packet of the fourth format only comprises one SDU, and wherein the second RRC message is used to configure bearer information of the SDU.

6. The method according to claim 2 or 5, characterized in that, The bearer information comprises at least one of: a session identifier; a data flow identifier; a radio bearer identifier; a logical channel identifier; a radio link control (RLC) entity identifier.

7. The method according to any one of claims 1 to 6, characterized in that, The sending, on the first resource, of a first data packet using the data format comprises: When uplink data needs to be sent on the first resource, an SDU received from a first bearer is encapsulated into a data packet according to the data format to obtain the first data packet, wherein the first bearer is a bearer corresponding to the data format; The network device is sent the first data packet.

8. The method according to any one of claims 1 to 6, characterized in that, The receiving, on the first resource, of a second data packet using the data format comprises: When downlink data needs to be received on the first resource, the received second data packet is sent to a second bearer after being unpacked, wherein the second bearer is a bearer corresponding to the data format.

9. The method of claim 3, wherein, The number of data packets of the fourth format transmitted each time is 1.

10. A communication method characterized by comprising: The method is performed by a network device, and the method comprises: A terminal is sent downlink control information DCI, wherein the DCI is used to configure a corresponding data format for a scheduled first resource; On the first resource, a first data packet using the data format is received, and / or a second data packet using the data format is sent.

11. The method of claim 10, wherein, The DCI comprises at least one of the following: First resource indication information; Data format configuration information; Control signaling indication information, wherein the control signaling indication information is used to indicate the configuration of a control information field in a data packet using the data format; Bearer information.

12. The method according to claim 10 or 11, characterized in that, The data format comprises any one of the following: A first format, wherein a subheader of a sub-protocol data unit PDU of a data packet of the first format only comprises a first information field, wherein the first information field is used to indicate whether there are other sub-PDUs after the first information field; A second format, wherein a subheader of a sub-PDU of a data packet of the second format only comprises a first information field and a second information field, wherein the first information field is used to indicate whether there are other sub-PDUs, and the second information field is used to indicate a logical channel identifier; A third format, wherein a subheader of a sub-PDU of a data packet of the third format only comprises a third information field, wherein the third information field is used to indicate the length of a service data unit SDU; A fourth format, wherein a PDU of a data packet of the fourth format only comprises one SDU.

13. The method of claim 11, wherein, The control signaling indication information comprises at least one of the following: First indication information, wherein the first indication information is used to indicate whether a third information field exists in a subheader of a sub-PDU of a data packet, and the third information field is used to indicate the length of an SDU; Second indication information, wherein the second indication information is used to indicate whether a second information field exists in a subheader of a sub-PDU of a data packet, and the second information field is used to indicate a logical channel identifier; Third indication information, wherein the third indication information is used to indicate whether a first information field exists in a subheader of a sub-PDU of a data packet, and the first information field is used to indicate whether there are other sub-PDUs after the first information field.

14. The method according to claim 12 or 13, characterized in that, The method further comprises at least one of the following: The data format does not include a third information field, and a first radio resource control (RRC) message is sent to the terminal; the third information field is used to indicate the length of the SDU; and the first RRC message is used to configure the length of the SDU. The data format does not include a second information field, and a second RRC message is sent to the terminal; the second information field is used to indicate the logical channel identifier; and the second RRC message is used to configure the bearer information of the SDU. The data format is a fourth format, and a second RRC message is sent to the terminal; the PDU of the data packet of the fourth format only includes one SDU; and the second RRC message is used to configure the bearer information of the SDU.

15. The method according to claim 11 or 14, characterized in that, The bearer information includes at least one of the following: a session identifier; a data flow identifier; a radio bearer identifier; a logical channel identifier; a radio link control (RLC) entity identifier.

16. The method according to any one of claims 10-15, characterized in that, The receiving, on the first resource, of the first data packet using the data format includes: When uplink data needs to be received on the first resource, the received first data packet is unpacked and sent to a first bearer; the first bearer is a bearer corresponding to the data format.

17. The method according to any one of claims 10-15, characterized in that, The sending, on the first resource, of the second data packet using the data format includes: When downlink data needs to be sent on the first resource, an SDU received from a second bearer is encapsulated into a data packet according to the data format to obtain the second data packet; the second bearer is a bearer corresponding to the data format; and the second data packet is sent to the terminal. The number of data packets of the fourth format per transmission is 1.

18. The method of claim 12, wherein, The apparatus includes:

19. A terminal, characterized by a transceiver configured to receive downlink control information (DCI) sent by a network device; the DCI is used to configure a corresponding data format for a scheduled first resource; the transceiver is further configured to send, on the first resource, a first data packet using the data format and / or receive a second data packet using the data format. The apparatus includes:

20. A network device, comprising: a transceiver configured to send downlink control information (DCI) to a terminal; the DCI is used to configure a corresponding data format for a scheduled first resource; the transceiver is further configured to receive, on the first resource, a first data packet using the data format and / or send a second data packet using the data format. The apparatus includes:

21. A terminal, characterized by one or more processors; the processor is used to perform the communication method in any one of claims 1-9. The apparatus includes:

22. A network device, comprising: one or more processors; the processor is used to perform the communication method in any one of claims 10-18. The apparatus includes:

23. A communication system, characterized by a terminal, and the first device is configured to implement the communication method in any one of claims 1-9; a network device, and the second device is configured to implement the communication method in any one of claims 10-18. When the instructions run on a communication device, the communication device is caused to perform the communication method in any one of claims 1-9 or 10-18.

24. A storage medium, the storage medium storing instructions, wherein, ​ 25. A computer program product comprising a computer program, characterised in that, The computer program is for implementing the communication method of any one of claims 1-9 or 10-18 when executed by a processor.

Images