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

Abstract

The present disclosure provides a communication method, a terminal, a network device, a system, and a storage medium. The method comprises: receiving first configuration information sent by a network device, wherein the first configuration information is used for configuring a corresponding data format for a semi-persistent resource, or configuring a corresponding first logical channel for the semi-persistent resource; and on the basis of the first configuration information, sending, on the semi-persistent resource, a first data packet using the data format, and / or receiving a second data packet using the data format. In the present disclosure, a specific data format can be bound to a semi-persistent resource, thereby reducing signaling loss when a terminal sends and receives data by means of the semi-persistent resource, improving data sending and receiving efficiency, improving the spectrum utilization rate, and having high 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 transmission 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 first configuration information sent by a network device; wherein the first configuration information is used to configure a corresponding data format for a semi-persistent resource, or configure a corresponding first logical channel for the semi-persistent resource;

[0007] based on the first configuration information, sending a first data packet using the data format on the semi-persistent resource, 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 first configuration information to a terminal; wherein the first configuration information is used to configure a corresponding data format for a semi-persistent resource, or configure a corresponding first logical channel for the semi-persistent resource;

[0010] based on the first configuration information, receiving a first data packet using the data format on the semi-persistent resource, 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] The transceiver module is configured to receive first configuration information sent by the network device; wherein the first configuration information is used to configure a corresponding data format for a semi-persistent resource, or configure a corresponding first logical channel for the semi-persistent resource;

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

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

[0015] The transceiver module is configured to send first configuration information to a terminal; wherein the first configuration information is used to configure a corresponding data format for a semi-persistent resource, or configure a corresponding first logical channel for the semi-persistent resource;

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

[0017] According to a fifth aspect of an embodiment 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 an embodiment 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 an embodiment of the present disclosure, a communication system is provided, comprising:

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

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

[0026] According to an eighth aspect of an embodiment of the present disclosure, a storage medium is provided, the storage medium stores instructions, when the instructions run on a communication device, the communication device executes the communication method of any one of the first aspect or the second aspect.

[0027] According to a ninth aspect of the embodiments of the present disclosure, a computer program product is provided, including a computer program which, when executed by a processor, is configured 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 the semi-persistent resource based on the first configuration information transmitted by the network device on the semi-persistent resource, and / or receives a second data packet using the data format corresponding to the semi-persistent resource. In the present disclosure, a specific data format can be associated with a semi-persistent resource, thereby reducing signaling loss when the terminal transmits and receives data through the semi-persistent resource, improving data transmission efficiency, improving spectrum utilization, and having high availability.

[0029] It should be understood that the foregoing general description and the following detailed description are only exemplary and explanatory, and are not limiting to the present disclosure. BRIEF DESCRIPTION OF DRAWINGS

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

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

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

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

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

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

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

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

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

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

[0040] FIG. 4B is a second 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 a fourth exemplary schematic diagram of a data format according to an embodiment of the present disclosure.

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

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

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

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

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

[0048] The exemplary embodiments will be described in detail herein with reference to the attached drawings. In the following description, the same numbers refer to the same or similar elements throughout the drawings. The implementations described in the following exemplary embodiments do not represent all implementations consistent with the present disclosure. Instead, they only represent examples of apparatuses and methods consistent with some aspects of the present disclosure as detailed in the appended claims.

[0049] The embodiments of the present disclosure provide a communication method, a terminal, a network device, a system and a storage medium.

[0050] In a first aspect, the embodiments of the present disclosure provide a communication method, which is performed by a terminal, and includes: receiving first configuration information sent by a network device; wherein the first configuration information is used for configuring a corresponding data format for a semi-persistent resource, or configuring a corresponding first logical channel for a semi-persistent resource; and based on the first configuration information, sending a first data packet using the data format on the semi-persistent resource, and / or receiving a second data packet using the data format.

[0051] In the above embodiments, a specific data format can be associated with a semi-persistent resource, thereby reducing signaling loss when the terminal transmits and receives data through the semi-persistent resource, improving data transmission and reception efficiency, improving spectrum usage, and having high availability.

[0052] In some embodiments of the first aspect, when the first configuration information is used to configure a corresponding data format for the semi-persistent resource, the first configuration information comprises at least one of: semi-persistent resource configuration 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.

[0053] In the above embodiments, the first configuration information can comprise but is not limited to at least one of the above, thereby associating the semi-persistent resource with the data format through the first configuration information, achieving simplicity and high availability.

[0054] In some embodiments of the first aspect, 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.

[0055] In the above embodiments, multiple data formats are provided, reducing signaling loss when the terminal transmits and receives data through the semi-persistent resource, and achieving high availability.

[0056] In some embodiments of the first aspect, 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.

[0057] In the above embodiments, the corresponding data format can be determined based on the control signaling indication information, achieving the purpose of associating the semi-persistent resource with the data format, and achieving high availability.

[0058] In some embodiments of the first 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; a radio link control (RLC) entity identifier.

[0059] In the above embodiments, the bearer information can comprise but is not limited to at least one of the above, and the purpose of associating the semi-persistent resource with the bearer is achieved, and the availability is high.

[0060] In some embodiments of the first aspect, in some embodiments, the method further comprises: the first configuration information is used to configure a corresponding first logical channel for the semi-persistent resource, and a data format corresponding to the first logical channel is determined as the data format corresponding to the semi-persistent resource.

[0061] In the above embodiments, the data format corresponding to the semi-persistent resource can be determined based on the data format corresponding to the first logical channel. The signaling resource of the first configuration information is reduced, and the availability is high.

[0062] In some embodiments of the first aspect, in some embodiments, the method further comprises: when the data format is the second format, receiving second configuration information sent by the network device; wherein the second configuration information is used to configure the length of the SDU.

[0063] In the above embodiments, the terminal can determine the length of the SDU based on the second configuration information, which is simple and has high availability.

[0064] In some embodiments of the first aspect, in some embodiments, the method further comprises any one of the following: determining, based on a predefined manner, that the RLC entity type of the bearer corresponding to the data packet of the second format is a first type; determining, based on third configuration information sent by the network device, that the RLC entity type of the bearer corresponding to the data packet of the second format is the first type; wherein the RLC entity of the first type adopts a transparent mode.

[0065] In the above embodiments, the terminal can determine the RLC entity type of the bearer corresponding to the data packet of the second format, which is simple and has high availability.

[0066] In some embodiments of the first aspect, in some embodiments, the sending, based on the first configuration information, of the first data packet using the data format on the semi-persistent resource comprises: when uplink data needs to be sent on the semi-persistent resource, encapsulating an 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.

[0067] In the above embodiment, the terminal can encapsulate the first data packet in the above manner and send the first data packet to the network device, thereby improving data transmission efficiency, improving spectrum utilization, and having high availability.

[0068] In some embodiments of the first aspect, in some embodiments, the receiving, based on the first configuration information, a second data packet using the data format on the semi-persistent resource comprises: receiving downlink data on the semi-persistent resource, and sending the received second data packet to a second bearer after unpacking the second data packet; wherein the second bearer is a bearer corresponding to the data format.

[0069] In the above embodiment, the terminal can encapsulate the first data packet in the above manner and send the first data packet to the network device, thereby improving data transmission efficiency, improving spectrum utilization, and having high availability.

[0070] 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: sending first configuration information to a terminal; wherein the first configuration information is used to configure a corresponding data format for a semi-persistent resource, or configure a corresponding first logical channel for a semi-persistent resource; receiving a first data packet using the data format on the semi-persistent resource based on the first configuration information, and / or sending a second data packet using the data format.

[0071] In some embodiments of the second aspect, when the first configuration information is used to configure a corresponding data format for the semi-persistent resource, the first configuration information comprises at least one of the following: semi-persistent resource configuration 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; data bearer information.

[0072] 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 comprises 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 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); and a fourth format; wherein a PDU of a data packet of the fourth format only comprises one SDU.

[0073] 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.

[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; a radio link control (RLC) entity identifier.

[0075] In some embodiments of the second aspect, in some embodiments, the method further comprises: when the data format is the second format, sending second configuration information to the terminal; wherein the second configuration information is used to configure the length of the SDU.

[0076] In some embodiments of the second aspect, in some embodiments, the method further comprises any one of: determining, based on a predefined manner, that the RLC entity type of the bearer corresponding to the data packet of the second format is a first type; sending third configuration information to the terminal; wherein the third configuration information is used to configure the RLC entity type of the bearer corresponding to the data packet of the second format as the first type; wherein the RLC entity of the first type adopts a transparent mode.

[0077] In some embodiments of the second aspect, in some embodiments, based on the first configuration information, receiving the first data packet using the data format on the semi-persistent resource comprises: when uplink data needs to be received on the semi-persistent 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.

[0078] In some embodiments of the second aspect, in some embodiments, based on the first configuration information, sending the second data packet using the data format on the semi-persistent resource comprises: when downlink data needs to be sent on the semi-persistent 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.

[0079] In a third aspect, the embodiments of the present disclosure provide a terminal, comprising: a transceiver configured to receive first configuration information sent by a network device; wherein the first configuration information is used to configure a corresponding data format for a semi-persistent resource, or configure a corresponding first logical channel for the semi-persistent resource; the transceiver is further configured to send a first data packet using the data format on the semi-persistent resource and / or receive a second data packet using the data format based on the first configuration information.

[0080] In a fourth aspect, the embodiments of the present disclosure provide a network device, comprising: a transceiver configured to send first configuration information to a terminal; wherein the first configuration information is used to configure a corresponding data format for a semi-persistent resource, or configure a corresponding first logical channel for the semi-persistent resource; the transceiver is further configured to receive a first data packet using the data format on the semi-persistent resource and / or send a second data packet using the data format based on the first configuration information.

[0081] 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.

[0082] 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.

[0083] 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; a network device, the second device is configured to implement the communication method of any one of the second aspect.

[0084] 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.

[0085] 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.

[0086] 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.

[0087] 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.

[0088] 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.

[0089] 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, and an embodiment can be combined with the optional implementation manners of other embodiments.

[0090] In the embodiments of the present disclosure, the terms and / or descriptions between 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.

[0091] 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.

[0092] In the embodiments of the present disclosure, unless otherwise specified and logically conflicted, 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.

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

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

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

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

[0097] 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 do they 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,” where 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 their types 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 their contents can be the same or different.

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

[0099] 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.

[0100] 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.

[0101] 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.

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

[0103] 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.

[0104] 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.

[0105] 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.

[0106] 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.

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

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

[0109] 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.

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

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

[0112] 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.

[0113] 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.

[0114] 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.

[0115] 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.

[0116] 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 (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.

[0117] 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).

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

[0119] 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.

[0120] 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:

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

[0122] Media access control unit in MAC subPDU (MAC subPDU including MAC CE): MAC control signaling part;

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

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

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

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

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

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

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

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

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

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

[0133] 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).

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

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

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

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

[0138] Configured Grant Type-1 (CG 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 (that is, the uplink resource is activated immediately after RRC configuration).

[0139] Configured Grant Type-2 (CG Type-2): the RRC message configures the period of uplink resource, and the 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.

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

[0141] 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.

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

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

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

[0145] Unacknowledged Mode (UM): The data transmitted by the RLC layer, and the sender does not need to receive the confirmation information from the receiver.

[0146] Acknowledged Mode (AM): The data transmitted by the RLC layer, and the sender needs to receive the confirmation information from the receiver.

[0147] 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.

[0148] 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.

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

[0150] 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:

[0151] In step S2101, the network device 102 sends first configuration information to the terminal 101.

[0152] In some embodiments, the terminal 101 receives the first configuration information.

[0153] In some embodiments, the first configuration information can be used to configure a corresponding data format for the semi-persistent resource.

[0154] Alternatively, the first configuration information can be used to configure a data format corresponding to the semi-persistent resource.

[0155] Correspondingly, the first configuration information can include, but is not limited to, at least one of the following: semi-persistent resource configuration information; data format configuration information; control signaling indication information; bearer information.

[0156] In one example, the semi-persistent resource configuration can be used to configure a semi-persistent resource, which can include, but is not limited to, at least one of the following: downlink semi-persistent resource configuration; uplink semi-persistent resource configuration.

[0157] Exemplarily, the downlink semi-persistent resource configuration can include, but is not limited to, SPS configuration identification information.

[0158] Exemplarily, the uplink semi-persistent resource configuration can include, but is not limited to, CG configuration identification information.

[0159] In one example, the data format configuration information can be used to configure a data format corresponding to the semi-persistent resource, which can include, but is not limited to, any one of the following: first format; second format; third format; fourth format.

[0160] Exemplarily, the subheader of the subPDU (i.e. MAC subPDU) of the data packet of the first format only includes a first information field, which can be used to indicate whether there are other subPDUs following. That is, the first information field can be E field.

[0161] Wherein, the subPDU of the data packet of the first format does not include L field and LCID field.

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

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

[0164] Exemplarily, the subheader of the subPDU (i.e. MAC subPDU) 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 subPDUs following, i.e. the first information field can be E field. The second information field can be used to indicate the logical channel identification, i.e. the second information field can be LCID field.

[0165] The L field is not included in the sub-PDU of the data packet of the second format.

[0166] The second format can be, for example, as shown in FIG. 4B, 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), in addition to the E field and the LCID field, the R field can also be included.

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

[0168] Exemplarily, the subheader of the sub-PDU (i.e. MAC subPDU) of the data packet of the third format only includes the 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.

[0169] The E field and the LCID field are not included in the sub-PDU of the data packet of the third format.

[0170] The third format can be, for example, as shown in FIG. 4C, 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), in addition to the L field, the R field can also be included.

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

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

[0173] The L field, the E field and the LCID field are not included in the sub-PDU of the data packet of the fourth format.

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

[0175] 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.

[0176] The above is only an exemplary description, and the disclosure does not limit the data format corresponding to the semi-persistent resource.

[0177] 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. whether the control information field is included in the MAC PDU packet and the specific control information field included.

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

[0179] 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.

[0180] When the bit value of the first indication information is a first value, the first indication information can be used to indicate that the L field exists in the subheader, and when the bit value of the first indication information is a second value, the first indication information 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.

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

[0182] For another example, when the bit value of the first indication information is "0", it can be indicated 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.

[0183] 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.

[0184] When the bit value of the second indication information is a first value, the second indication information can be used to indicate that the LCID field exists in the subheader, and when the bit value of the second indication information is a second value, the second indication information 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.

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

[0186] For another example, when the bit value of the second indication information is "0", it can be indicated 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.

[0187] 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 another sub-PDU, i.e., the first information field can be an E field.

[0188] 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 a first value, and the bit value of the third indication information can be used to indicate that the E field does not exist in the subheader when the bit value is a second value. The first value can be 0 or 1, and the second value can be 1 or 0.

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

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

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

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

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

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

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

[0196] The bit value of the third indication information is “0”, the bit value of the second indication information is “0”, and the bit value of the first indication information is “0”, and at this time, the data format can be the fourth format.

[0197] 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.

[0198] Of course, the first configuration information can also include the data format configuration information and the control signaling indication information, and the two can indicate the same data format, or based on the control signaling indication information, a plurality of data formats can be determined, and the data format configuration information can be used to indicate one of the data formats.

[0199] For example, the bit value of the first indication information included in the indication information is "1", and the data format is determined as the third format. In addition, the data format configuration information also indicates the third format.

[0200] For another example, the bit value of the third indication information included in the indication information is "1", and the data format can be the first format or the second format. At this time, the data format configuration information indicates the first format.

[0201] In one example, the bearer information can be used to configure the bearer corresponding to the data packet transmitted on the semi-persistent resource.

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

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

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

[0205] In some embodiments, the first configuration information can also be used to configure a corresponding first logical channel for the semi-persistent resource.

[0206] Alternatively, the first configuration information can be used to configure a first logical channel corresponding to the semi-persistent resource.

[0207] It can be understood that the data format corresponding to each logical channel can be determined by a predefined manner, such as a protocol agreement. At this time, the first configuration information configures the first logical channel corresponding to the semi-persistent resource, thereby implicitly configuring the data format corresponding to the semi-persistent resource.

[0208] In some embodiments, a specific data format can be bound or associated with the semi-persistent resource.

[0209] Exemplarily, the network device 102 provides a semi-persistent resource configuration to support faster data management. In the embodiment of the present disclosure, the network device 102 can bind or associate the provided semi-persistent resource with a specific data format when providing the semi-persistent resource configuration. So that the terminal 101 transmits uplink data using data packets of the data format on the semi-persistent resource, and / or receives downlink data on the semi-persistent resource, and the format of the downlink data packets is the data format bound to the semi-persistent resource, thereby further reducing the loss of control information during data transmission and reception, especially the loss of dynamic control information, improving the efficiency of data transmission and reception while supporting faster data management.

[0210] In step S2102, the terminal 101 determines the data format corresponding to the semi-persistent resource.

[0211] In some embodiments, the first configuration information is used to configure a first logical channel corresponding to the semi-persistent resource. At this time, the terminal can determine the data format corresponding to the semi-persistent resource based on the protocol agreement that the data format corresponding to the first logical channel is determined.

[0212] In some embodiments, step S2102 is an optional execution step. For example, the first configuration information adopts a display indication manner, and provides “data format configuration information” and / or “control signaling indication information”, at this time, step S2102 can not be executed. For another example, the first configuration information adopts an implicit indication manner, that is, the first logical channel corresponding to the semi-persistent resource is provided, at this time, step S2102 can be executed.

[0213] In step S2103, the network device 102 sends second configuration information to the terminal 101.

[0214] In some embodiments, the terminal 101 receives the second configuration information.

[0215] In some embodiments, the second configuration information is used to configure the length of the SDU.

[0216] In some embodiments, when the data format is the second format, the network device 102 sends the second configuration information to the terminal 101.

[0217] When the data format is the second format, only the first information field and the second information field are included in the subheader of the sub-PDU, that is, the L field is not included, so the length of the SDU can be configured by the network device 102 through the second configuration information.

[0218] For example, the network device 102 configures the length of each MAC SDU as N bytes for the second format, N is a positive integer, and it is assumed to be 10 bytes.

[0219] In some embodiments, step S2103 is an optional execution step. For example, the data format is the first format, the second format, or the fourth format, and step S2103 can not be executed.

[0220] Step S2104, the network device 102 determines the RLC entity type of the bearer.

[0221] In some embodiments, the data format is the second format described above, and the network device 102 can determine the RLC entity type of the bearer.

[0222] In some embodiments, the network device 102 can determine the RLC entity type of the bearer based on a predefined manner.

[0223] For example, the network device 102 can determine that the RLC entity type of the bearer corresponding to the data packet in the second format is the first type based on a predefined manner.

[0224] The RLC entity of the first type can adopt a transparent mode, i.e., the RLC entity of the first type is an RLC TM mode.

[0225] In some embodiments, step S2104 is an optional execution step. For example, the network device 102 configures the RLC entity type for the terminal 101, and step S2104 can not be executed.

[0226] Step S2105, the network device 102 sends third configuration information to the terminal 101.

[0227] In some embodiments, the terminal 101 receives the third configuration information.

[0228] In some embodiments, the third configuration information is used to configure the RLC entity type of the bearer corresponding to the data packet in the second format as the first type.

[0229] The RLC entity of the first type can adopt a transparent mode, i.e., the RLC entity of the first type is an RLC TM mode.

[0230] In some embodiments, step S2105 is an optional execution step. For example, the data format is the first format, the second format, or the fourth format, and step S2105 can not be executed. For another example, the data format is the second format, but the network device 102 and the terminal 101 determine the RLC entity type of the bearer corresponding to the data packet in the second format based on a predefined manner, and step S2105 can not be executed.

[0231] Step S2106, the terminal 101 determines the RLC entity type of the bearer.

[0232] In some embodiments, the data format is the second format, and the terminal 101 can determine the RLC entity type of the bearer.

[0233] In some embodiments, the terminal 101 can determine the RLC entity type of the bearer based on a predefined manner.

[0234] For example, the terminal 101 can determine, based on the predefined manner, that the RLC entity type of the bearer corresponding to the data packet in the second format is the first type.

[0235] The RLC entity of the first type can be in a transparent mode, i.e., the RLC entity of the first type is an RLC TM mode.

[0236] In some embodiments, the terminal 101 can determine the RLC entity type of the bearer corresponding to the data packet in the second format based on the third configuration information sent by the network device 102, which can be the first type.

[0237] The RLC entity of the first type can be in a transparent mode, i.e., the RLC entity of the first type is an RLC TM mode.

[0238] In some embodiments, step S2106 is an optional execution step. For example, the data format is the first format, the second format, or the fourth format, and in this case, step S2106 can not be executed.

[0239] In step S2107, the terminal 101 sends the first data packet to the network device 102.

[0240] In some embodiments, the first data packet uses the data format corresponding to the semi-persistent resource.

[0241] In some embodiments, the network device 102 receives the first data packet using the data format.

[0242] In some embodiments, the terminal 101 sends the first data packet in the data format corresponding to the semi-persistent resource to the network device 102 based on the first configuration information.

[0243] In one example, the terminal 101 needs to send uplink data on the semi-persistent resource, can encapsulate 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 then send the first data packet to the network device 102.

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

[0245] 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:

[0246] 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.

[0247] The specified bearer can be a bearer indicated by the bearer information in the first configuration information.

[0248] 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.

[0249] The specified bearer can be a bearer indicated by the bearer information in the first configuration information.

[0250] The specified size can be the length of the SDU configured by the network device 102 through the second configuration information.

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

[0252] 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.

[0253] The specified size can be the length of the SDU configured by the network device 102 through the second configuration information.

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

[0255] 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.

[0256] The specified bearer can be a bearer indicated by the bearer information in the first configuration information.

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

[0258] 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.

[0259] 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.

[0260] The specified bearer can be a bearer indicated by the bearer information in the first configuration information.

[0261] Correspondingly, the network device 102 needs to receive uplink data on the semi-persistent resource, and can send the received first data packet to a first bearer after unpacking, where the first bearer is a bearer corresponding to the data format.

[0262] The first bearer can be at least one of bearers configured by the first configuration information, and details are not described herein.

[0263] In step S2108, the network device 102 sends a second data packet to the terminal 101.

[0264] In some embodiments, the second data packet uses a data format corresponding to the semi-persistent resource.

[0265] In some embodiments, the terminal 101 receives the second data packet using the data format.

[0266] In some embodiments, the network device 102 sends, based on the first configuration information, a second data packet in a data format corresponding to a semi-persistent resource to the terminal 101 on the semi-persistent resource.

[0267] In one example, the network device 102 needs to send downlink data on the semi-persistent resource, and the network device 102 encapsulates an SDU received from a second bearer into a data packet according to the data format to obtain the second data packet, where the second bearer is a bearer corresponding to the data format, and then sends the second data packet to the terminal 101.

[0268] The network device 102 encapsulates the second data packet in a manner similar to that of the terminal 101 encapsulating the first data packet, and details are not described herein.

[0269] Correspondingly, the terminal 101 needs to receive downlink data on the semi-persistent resource, and can send the received second data packet to a second bearer after unpacking, where the second bearer is a bearer corresponding to the data format.

[0270] The second bearer can be at least one of bearers configured by the first configuration information, and details are not described herein.

[0271] The second bearer and the first bearer can be the same or different bearers, and the present disclosure does not limit this.

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

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

[0274] In some embodiments, "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, autonomously implementing, and the like.

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

[0276] The communication method related to the embodiments of the present disclosure can include at least one of steps S2101-S2108. 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, step S2105 can be implemented as an independent embodiment, steps S2105+S2106 can be implemented as an independent embodiment, steps S2104+S2106 can be implemented as an independent embodiment, step S2107 can be implemented as an independent embodiment, step S2108 can be implemented as an independent embodiment, steps S2101-S2108 can be implemented as an independent embodiment, but the present disclosure is not limited thereto.

[0277] In some embodiments, steps S2101-S2108 are optional, and one or more of the steps can be omitted or replaced in different embodiments.

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

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

[0280] In some embodiments, the above step S2101 can be performed alone. For example, when a specific data format(s) is bound or associated with a semi-persistent resource, the network device 102 can provide a semi-persistent resource configuration to the terminal 101, and the semi-persistent resource configuration can include but is not limited to at least one of the following: a configured semi-persistent resource; and indication information, which can be used to indicate the data format when data is transmitted and received using the semi-persistent resource (for example, the indication information can be data format indication information or control signaling indication information). For example, the uplink semi-persistent resource set #1 corresponds to the first format, the uplink semi-persistent resource set #2 corresponds to the second format, and the downlink semi-persistent resource set corresponds to the fourth format. When the terminal transmits uplink data using resources in the uplink semi-persistent resource set #1, the data format can be the first format, when the terminal transmits uplink data using resources in the uplink semi-persistent resource set #2, the data format can be the second format, and when the terminal receives downlink data on resources in the downlink semi-persistent resource set, the data format of the downlink data can be the fourth format. Accordingly, when the semi-persistent resource is not needed for data transmission and reception, steps S2102-S2108 described above can be omitted.

[0281] In the above embodiments, the loss of control information during data transmission and reception is reduced, especially the loss of dynamic control information, and the availability is high.

[0282] 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 method is performed by a terminal 101, and the method comprises the following steps:

[0283] In step S3101, first configuration information is acquired.

[0284] In some embodiments, the first configuration information can be used to configure a corresponding data format for a semi-persistent resource.

[0285] In some embodiments, the terminal 101 can acquire the first configuration information from the network device 102, but is not limited thereto, and can also receive the first configuration information sent by other subjects.

[0286] In some embodiments, the terminal 101 acquires the first configuration information specified by a protocol.

[0287] In some embodiments, the terminal 101 acquires the first configuration information from an upper layer.

[0288] In some embodiments, the terminal 101 processes to obtain the first configuration information.

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

[0290] 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 related to FIG. 2, which will not be repeated here.

[0291] In step S3102, a data format is determined.

[0292] 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 related to FIG. 2, which will not be repeated here.

[0293] In step S3103, second configuration information is acquired.

[0294] In some embodiments, the second configuration information is used to configure the length of an SDU.

[0295] In some embodiments, the terminal 101 can acquire the second configuration information from the network device 102, but is not limited thereto, and can also receive the second configuration information sent by other subjects.

[0296] In some embodiments, the terminal 101 acquires the second configuration information specified by a protocol.

[0297] In some embodiments, the terminal 101 acquires the second configuration information from upper layer(s).

[0298] In some embodiments, the terminal 101 processes to obtain the second configuration information.

[0299] In some embodiments, the step S3103 is omitted, and the terminal 101 autonomously implements the function indicated by the second configuration information, or the terminal 101 acquires the second configuration information based on a predefined rule or protocol agreement, or the above function is default or default.

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

[0301] In step S3104, the third configuration information is acquired.

[0302] In some embodiments, the third configuration information is used to configure the RLC entity type of the bearer corresponding to the data packet of the second format to be the first type.

[0303] In some embodiments, the terminal 101 can acquire the third configuration information from the network device 102, but is not limited thereto, and can also receive the third configuration information sent by other subjects.

[0304] In some embodiments, the terminal 101 acquires the third configuration information specified by a protocol.

[0305] In some embodiments, the terminal 101 acquires the third configuration information from upper layer(s).

[0306] In some embodiments, the terminal 101 processes to obtain the third configuration information.

[0307] In some embodiments, the step S3104 is omitted, and the terminal 101 autonomously implements the function indicated by the third configuration information, or the terminal 101 acquires the third configuration information based on a predefined rule or protocol agreement, or the above function is default or default.

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

[0309] Step S3105: determining the RLC entity type.

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

[0311] Step S3106: sending the first data packet.

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

[0313] In some embodiments, the network device 102 receives the first data packet using the data format.

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

[0315] Step S3107: obtaining the second data packet.

[0316] 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.

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

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

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

[0320] In some embodiments, step S3107 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 predefined rule or protocol agreement, or the above function is default or default.

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

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

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

[0324] In the above embodiments, specific data formats can be associated with semi-persistent resources, thereby reducing signaling loss when the terminal transmits and receives data through semi-persistent resources, improving data transmission and reception efficiency, increasing spectrum utilization, and improving availability.

[0325] Figure 3B is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure. As shown in Figure 3B, the present disclosure relates to a communication method, which is executed by terminal 101, and the method includes:

[0326] Step S3201: Obtain the first configuration information.

[0327] In some embodiments, the first configuration information can be used to configure the corresponding data format for semi-persistent resources.

[0328] In some embodiments, terminal 101 may obtain first configuration information from network device 102, but is not limited thereto, and may also receive first configuration information sent by other entities.

[0329] In some embodiments, terminal 101 obtains first configuration information as defined by the protocol.

[0330] In some embodiments, terminal 101 obtains first configuration information from upper layer(s).

[0331] In some embodiments, the terminal 101 processes the information to obtain the first configuration information.

[0332] In some embodiments, step S3201 is omitted, and the terminal 101 autonomously implements the function indicated by the first configuration information, or the terminal 101 obtains the first configuration information based on predefined rules or protocol agreements, or the above function is a default or default setting.

[0333] In some embodiments, optional implementations of step S3201 can be found in optional implementations of step S2101 in FIG2 and other related parts in the embodiments involved in FIG2, which will not be repeated here.

[0334] In the above embodiments, specific data formats can be associated with semi-persistent resources, thereby reducing signaling loss when the terminal transmits and receives data through semi-persistent resources, improving data transmission and reception efficiency, increasing spectrum utilization, and improving availability.

[0335] 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, wherein the method is performed by the network device 102, and the method comprises the following steps:

[0336] In step S3301, first configuration information is transmitted.

[0337] In some embodiments, the first configuration information can be used to configure a corresponding data format for the semi-persistent resource.

[0338] In some embodiments, the network device 102 transmits the first configuration information to the terminal 101.

[0339] In some embodiments, the terminal 101 acquires the first configuration information.

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

[0341] In step S3302, second configuration information is transmitted.

[0342] In some embodiments, the second configuration information can be used to configure the length of the SDU.

[0343] In some embodiments, the network device 102 transmits the second configuration information to the terminal 101.

[0344] In some embodiments, the terminal 101 acquires the second configuration information.

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

[0346] In step S3303, the type of RLC entity is determined.

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

[0348] In step S3304, third configuration information is transmitted.

[0349] In some embodiments, the third configuration information is used to configure the type of RLC entity of the bearer corresponding to the data packet of the second format as the first type.

[0350] In some embodiments, the network device 102 transmits the third configuration information to the terminal 101.

[0351] In some embodiments, the terminal 101 acquires the third configuration information.

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

[0353] Step S3305: Acquire the first data packet.

[0354] In some embodiments, the network device 102 can acquire 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.

[0355] In some embodiments, the network device 102 acquires the first data packet specified by the protocol.

[0356] In some embodiments, the network device 102 acquires the first data packet from the upper layer(s).

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

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

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

[0360] Step S3306: Send the second data packet.

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

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

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

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

[0365] In some embodiments, the execution sequence of steps S3301 to S3306 is not limited.

[0366] In the above embodiments, the network device can associate a specific data format with the semi-persistent resource through the first configuration information, and can provide related configurations through other configuration information, thereby reducing signaling loss when the terminal transmits and receives data through the semi-persistent resource, improving data transmission efficiency, improving spectrum utilization, and having high availability.

[0367] FIG. 3D is an interaction 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 the following steps:

[0368] In step S3401, the first configuration information is transmitted.

[0369] In some embodiments, the first configuration information can be used to configure a corresponding data format for the semi-persistent resource.

[0370] In some embodiments, the network device 102 transmits the first configuration information to the terminal 101.

[0371] In some embodiments, the terminal 101 acquires the first configuration information.

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

[0373] In the above embodiments, the network device can associate a specific data format with the semi-persistent resource through the first configuration information, thereby reducing signaling loss when the terminal transmits and receives data through the semi-persistent resource, improving data transmission efficiency, improving spectrum utilization, and having high availability.

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

[0375] In the embodiments of the present disclosure, by binding a specific data format type with a downlink or downlink semi-persistent configuration, the terminal can reduce signaling loss when transmitting downlink or uplink data when receiving through the downlink or uplink semi-persistent resource.

[0376] In the embodiments of the present disclosure, the network side (i.e., the network device) provides the terminal side with a "semi-persistent resource corresponding data format type configuration".

[0377] The "semi-persistent resource corresponding data format type configuration" comprises:

[0378] 1, Semi-Persistent Resource Configuration. Wherein the "Semi-Persistent Resource Configuration" includes at least one of the following:

[0379] Downlink Semi-Persistent Resource Configuration;

[0380] Uplink Semi-Persistent Resource Configuration.

[0381] 2, Data Format Type Configuration. Wherein the "Data Format Type Configuration" includes at least one of the following:

[0382] 2-1, Data Format Type Indication Information. Wherein the "Data Format Type Indication Information" includes any one of the following:

[0383] Data Format Type 1: The subheader of the MAC subPDU only includes "Subsequent MAC subPDU Indication Field".

[0384] Data Format Type 2: The subheader of the MAC subPDU only includes "Subsequent MAC subPDU Indication Field" and "Logical Channel Identity Field".

[0385] Data Format Type 3: The subheader of the MAC subPDU only includes "L" field.

[0386] Data Format Type 4: The MAC PDU has only one MAC SDU, for example, using "transparent MAC".

[0387] 2-2, Control Signaling Indication Information. Wherein the "Control Signaling Indication Information" includes at least one of the following:

[0388] Length field indication; logical channel identification indication; subsequent MAC subPDU identification indication.

[0389] 2-3, Data Bearer Information. Wherein the "Data Bearer Information" includes at least one of the following:

[0390] Session Identity (e.g., Session Identity);

[0391] Data Flow Identity (e.g., QoS flow Identity);

[0392] Radio Bearer Identity (e.g., DRB Identity);

[0393] Logical Channel Identity (e.g., LCID Identity);

[0394] RLC Entity Identity (e.g., one of the RLC entities for a split bearer).

[0395] Terminal side: According to the configuration of network side, the terminal transmits the received MAC SDU to the specified data bearer according to the specified data format type after receiving data in the specified semi-persistent resource. According to the configuration of network side, the terminal transmits the received MAC SDU from the specified data bearer according to the specified data format type when transmitting data in the specified semi-persistent resource.

[0396] Network side: Provide the terminal side with the "semi-persistent resource corresponding data format type configuration".

[0397] Embodiment 1:

[0398] For example, as shown in FIG. 4E, the method includes the following steps:

[0399] Step S4501, the network side (i.e. network device) provides the terminal side with the "semi-persistent resource corresponding data format type configuration".

[0400] For example, the network side provides the terminal with SPS-Config, and the MAC subPDU type corresponding to the SPS-Config does not include the indication information of the LCID domain, for example, the LCID identifier corresponding to the SPS-Config, for example, LCID = 1. Then the MAC subPDU of the MAC PDU transmitted through the downlink resource corresponding to the SPS-Config is only used for the logical channel of "LCID = 1", and the MAC subPDU does not include LCID.

[0401] The "semi-persistent resource corresponding data format type configuration" includes:

[0402] 1, semi-persistent resource configuration. The "semi-persistent resource configuration" includes at least one of the following:

[0403] Downlink semi-persistent resource configuration (such as SPS-Config identifier information);

[0404] Uplink semi-persistent resource configuration (such as ConfiguredGrantConfig identifier information).

[0405] 2, data format type configuration. The "data format type configuration" includes at least one of the following:

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

[0407] Data format type 1, for example, as shown in FIG. 4A, the subheader of the MAC subPDU only includes the "subsequent MAC subPDU indication field". For example, the MAC subPDU does not include the "L" field and the "LCID" field, but only includes the "E" field. Among them, the "E" field is used to identify whether there is a MAC subPDU after the MAC subPDU. This type of MAC data packet is suitable for sending MAC SDUs with fixed data length, and the data is derived from the same logical channel MAC SDU.

[0408] Data format type 2, for example, as shown in FIG. 4B, the subheader of the MAC subPDU only includes the "subsequent MAC subPDU indication field" and the "logical channel identification field". For example, the MAC subPDU does not include the "L" field, but only includes the "E" field and the "LCID" field. Among them, the "E" field is used to identify whether there is a MAC subPDU after the MAC subPDU. This type of MAC data packet is suitable for sending MAC SDUs with fixed data length.

[0409] Data format type 3, for example, as shown in FIG. 4B, the subheader of the MAC subPDU only includes the "L" field. For example, the MAC subPDU does not include the "LCID" field. This type of MAC data packet is suitable for sending MAC SDUs derived from the same logical channel.

[0410] Data format type 4, for example, as shown in FIG. 4B, the MAC PDU has only one MAC SDU, for example, using "transparent MAC". This type of MAC data packet is suitable for sending MAC SDUs derived from the same logical channel, and there is only one MAC SDU.

[0411] 2-2, control signaling indication information

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

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

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

[0415] A subsequent MAC subPDU indication (e.g., a value of "1" indicates that a "subsequent MAC subPDU indication" field exists, and a value of "0" indicates that a "subsequent MAC subPDU indication" field does not exist. Crane, the "subsequent MAC subPDU indication" field is used to indicate in the subheader of a MAC subPDU that there are no other MAC subPDUs after this MAC subPDU).

[0416] 2-3, data bearer information. Among them, the "data bearer information" includes at least one of the following:

[0417] Session identifier (e.g., Session identifier);

[0418] Data flow identifier (e.g., QoS flow identifier);

[0419] Radio bearer identifier (e.g., DRB identifier);

[0420] Logical channel identifier (e.g., LCID identifier);

[0421] RLC entity identifier (e.g., one of the RLC entities for a split bearer).

[0422] Among them, the "data format type indication information" can be "explicitly indicated" or "implicitly indicated", for example, in the implicit indication mode, by indicating the logical channel identifier corresponding to the SPS configuration, and the logical channel identifier has its corresponding data format type, the protocol stipulates that the subPDU of the MAC PDU sent by the SPS resource does not include the LCID field.

[0423] Among them, the "control signaling indication information" can be "explicitly indicated" or "implicitly indicated", for example, in the implicit indication mode, by indicating the logical channel identifier corresponding to the SPS configuration, and the logical channel identifier has its corresponding data format type, the protocol stipulates that the subPDU of the MAC PDU sent by the SPS resource does not include the LCID field.

[0424] Among them, for "data format type 2", the network side can configure the data length of the MAC SDU. For example, the network side configures the data length of each MAC SDU of data format type 2 to be 10 bytes.

[0425] In addition, it can be agreed that when the "data format type configuration corresponding to the downlink semi-persistent resource" does not include the MAC SDU length indication field (e.g., L field), the RLC entity type of the corresponding radio bearer is TM mode.

[0426] Step S4502, according to the configuration in step S4501, the terminal can receive the network side sent second data packet of specified format. The terminal receives data in the specified semi-persistent resource, and sends the received MAC SDU to the specified data bearer according to the specified data format type.

[0427] According to the configuration in step S4501, the terminal can send the network side first data packet of specified format. At this time, the terminal sends the MAC SDU received from the specified data bearer according to the specified data format type when sending data in the specified semi-persistent resource.

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

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

[0430] 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 connected with a memory, the memory stores instructions, and the processor calls the instructions stored in the memory to implement any of the above methods or realize the functions of each unit or module of the above apparatus, wherein the processor is, for example, a general processor such as a central processing unit (CPU) or a microprocessor, and the memory is a memory within 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 above units or modules are realized by the design of the logical relationship of the elements in the circuit; for 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 above units or modules. All units or modules of the above apparatus can be implemented in the form of processor calling software, or all units or modules can be implemented in the form of hardware circuit, or part of the units or modules are implemented in the form of processor calling software, and the remaining part is implemented in the form of hardware circuit.

[0431] 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 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.

[0432] 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.

[0433] In some embodiments, the transceiver module 5101 described above is configured to receive first configuration information sent by a network device; wherein the first configuration information is used to configure a corresponding data format for a semi-persistent resource, or configure a corresponding first logical channel for a semi-persistent resource; based on the first configuration information, a first data packet using the data format is transmitted on the semi-persistent resource, and / or a second data packet using the data format is received.

[0434] Optionally, the transceiver module 5101 described above is configured to perform at least one of the communication steps (for example, steps S2101, S2103, S2105, S2107, and S2108, but not limited thereto) of transmitting and / or receiving performed by the terminal 5100 in any of the above methods. Details are not described herein again.

[0435] 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.

[0436] In some embodiments, the transceiver module 5201 described above is configured to send first configuration information to the terminal; wherein the first configuration information is used to configure a corresponding data format for a semi-persistent resource, or configure a corresponding first logical channel for a semi-persistent resource; based on the first configuration information, receive a first data packet using the data format on the semi-persistent resource, and / or send a second data packet using the data format.

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

[0438] 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 replaced by a transceiver.

[0439] FIG. 6A is a structural schematic diagram of a communication device 6100 according to an embodiment 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, or 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.

[0440] 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.

[0441] 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 (e.g., step S2101, step S2103, step S2105, step S2107, step S2108, but not limited to) in the above-described methods, and the processor 6101 performs at least one of the other steps (e.g., step S2102, step S2104, step S2106, but not limited to). 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.

[0442] 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.

[0443] 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 FIG. 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 chip, or chip system or subsystem; (2) a set of one or more ICs, which can optionally also include storage for storing data, programs; (3) an ASIC, such as a modem; (4) a module that can be embedded within other devices; (5) a receiver, terminal device, smart terminal device, cellular phone, wireless device, handset, mobile unit, car-mounted device, network device, cloud device, artificial intelligence device, etc.; (6) other, etc.

[0444] FIG. 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 can be a chip or a chip system, the structural schematic diagram of the chip 6200 shown in FIG. 6B can be referred to, but is not limited thereto.

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

[0446] In some embodiments, the chip 6200 further comprises one or more interface circuits 6202. Optionally, the terms interface circuit, interface, transceiver pin, etc. can be replaced by each other. In some embodiments, the chip 6200 further comprises 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, and 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.

[0447] In some embodiments, the interface circuit 6202 performs at least one of the communication steps (such as step S2101, step S2103, step S2105, step S2107, step S2108, but not limited thereto) of transmitting and / or receiving in the above methods. The interface circuit 6202 performing the communication steps such as transmitting 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 (such as step S2102, step S2104, step S2106, but not limited thereto).

[0448] 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 in cooperation, which is not limited herein.

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

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

[0451] The disclosure also proposes a computer program which, when running on a computer, causes the computer to perform any of the above methods.

[0452] 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. The disclosure is intended to cover any variations, uses or adaptations of the disclosure following, in general, the principles of the disclosure and including such features that are evident to those skilled in the art to which the disclosure pertains. The specification and examples are to be regarded as illustrative only, and the true scope and spirit of the disclosure are indicated by the following claims.

[0453] 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. The disclosure is intended to cover any variations, uses or adaptations of the disclosure following, in general, the principles of the disclosure and including such features that are evident to those skilled in the art to which the disclosure pertains. The specification and examples are to be regarded as illustrative only, and the true scope and spirit of the disclosure are indicated by the following claims.

[0454] It should be understood that the present disclosure is not limited to the precise construction that has been described and shown in the accompanying drawings, and that various modifications and changes can be made by those skilled in the art without departing from the scope of the present disclosure. The scope of the present disclosure is limited only by the claims that follow.

Claims

A communication method characterized by comprising: The method is performed by a terminal, and the method comprises: receiving first configuration information sent by a network device; wherein the first configuration information is used for configuring a corresponding data format for a semi-persistent resource, or configuring a corresponding first logical channel for a semi-persistent resource; based on the first configuration information, sending a first data packet using the data format on the semi-persistent resource, and / or receiving a second data packet using the data format. The method of claim 1, wherein When the first configuration information is used for configuring a corresponding data format for the semi-persistent resource, the first configuration information comprises at least one of the following: semi-persistent resource configuration information; data format configuration information; control signaling indication information; wherein the control signaling indication information is used for indicating the configuration of a control information field in a data packet using the data format; bearer information. The method according to claim 1 or 2, 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 for indicating 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 for indicating whether there are other sub-PDUs, and the second information field is used for indicating 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 for indicating 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. The method according to claim 2, characterized in that The control signaling indication information comprises at least one of the following: first indication information; wherein the first indication information is used for indicating whether there is a third information field in a subheader of a sub-PDU of a data packet, and the third information field is used for indicating the length of an SDU; second indication information; wherein the second indication information is used for indicating whether there is a second information field in a subheader of a sub-PDU of a data packet, and the second information field is used for indicating a logical channel identifier; third indication information; wherein the third indication information is used for indicating whether there is a first information field in a subheader of a sub-PDU of a data packet, and the first information field is used for indicating whether there are other sub-PDUs. The method according to claim 2, characterized in that 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; a radio link control (RLC) entity identifier. The method of claim 1, wherein The method further comprises: when the first configuration information is used for configuring a corresponding first logical channel for the semi-persistent resource, determining the data format corresponding to the first logical channel as the data format corresponding to the semi-persistent resource. The method according to claim 3, characterized in that The method further comprises: when the data format is the second format, receiving second configuration information sent by the network device; wherein the second configuration information is used for configuring the length of an SDU. The method of claim 7, wherein The method further comprises any one of the following: based on a predefined manner, determining that the RLC entity type of a bearer corresponding to a data packet of the second format is a first type; Determine, based on third configuration information sent by the network device, that the RLC entity type of the bearer corresponding to the second format of data packet is a first type; The RLC entity of the first type adopts a transparent mode. The method according to any one of claims 1 to 8, characterized in that The sending, based on the first configuration information, of the first data packet using the data format on the semi-persistent resource includes: If uplink data needs to be sent on the semi-persistent resource, encapsulate a data packet according to the data format to obtain the first data packet from an SDU received from a first bearer; the first bearer is a bearer corresponding to the data format; Send the first data packet to the network device. The method according to any one of claims 1 to 8, characterized in that The receiving, based on the first configuration information, of the second data packet using the data format on the semi-persistent resource includes: If downlink data needs to be received on the semi-persistent resource, send the second data packet received to a second bearer after unpacking the second data packet; the second bearer is a bearer corresponding to the data format. The method is performed by a network device, and the method includes: A communication method characterized by comprising: Send first configuration information to a terminal; the first configuration information is used to configure a corresponding data format for a semi-persistent resource or configure a corresponding first logical channel for a semi-persistent resource; Receive a first data packet using the data format on the semi-persistent resource and / or send a second data packet using the data format based on the first configuration information. When the first configuration information is used to configure a corresponding data format for the semi-persistent resource, the first configuration information includes at least one of the following: The method of claim 11, wherein Semi-persistent resource configuration information; Data format configuration information; Control signaling indication information; the control signaling indication information is used to indicate the configuration of a control information field in a data packet using the data format; Data bearer information. The data format includes any of the following: The method according to claim 11 or 12, characterized in that A first format; a subheader of a sub-protocol data unit (PDU) of a data packet of the first format includes only a first information field; the first information field is used to indicate whether there is a subsequent other sub-PDU; A second format; a subheader of a sub-PDU of a data packet of the second format includes only a first information field and a second information field; the first information field is used to indicate whether there is a subsequent other sub-PDU, and the second information field is used to indicate a logical channel identifier; A third format; a subheader of a sub-PDU of a data packet of the third format includes only a third information field; the third information field is used to indicate the length of a service data unit (SDU); A fourth format; a PDU of a data packet of the fourth format includes only one SDU. The control signaling indication information includes at least one of the following: The method of claim 12, wherein First indication information; the first indication information is used to indicate whether there is a third information field in a subheader of a sub-PDU of a data packet; the third information field is used to indicate the length of an SDU; Second indication information; the second indication information is used to indicate whether there is a second information field in a subheader of a sub-PDU of a data packet; the second information field is used to indicate a logical channel identifier; ​ The third indication information is 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 is used to indicate whether there is another sub-PDU. The method of claim 12, wherein 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; an RLC entity identifier. The method of claim 13, wherein The method further includes: The data format is the second format, and second configuration information is sent to the terminal; wherein the second configuration information is used to configure the length of the SDU. The method of claim 16, wherein The method further includes any of the following: Based on a predefined manner, it is determined that the RLC entity type of the bearer corresponding to the data packet in the second format is the first type; Third configuration information is sent to the terminal; wherein the third configuration information is used to configure the RLC entity type of the bearer corresponding to the data packet in the second format as the first type; The RLC entity of the first type adopts a transparent mode. The method according to any one of claims 11-17, characterized in that The first data packet using the data format is received on the semi-persistent resource based on the first configuration information, including: The received first data packet is unpacked and sent to the first bearer after receiving the uplink data on the semi-persistent resource; wherein the first bearer is the bearer corresponding to the data format. The method according to any one of claims 11-17, characterized in that The second data packet using the data format is sent on the semi-persistent resource based on the first configuration information, including: The SDU received from the second bearer is encapsulated into a data packet according to the data format to obtain the second data packet, and the downlink data is sent on the semi-persistent resource; wherein the second bearer is the bearer corresponding to the data format; The second data packet is sent to the terminal. A terminal, characterized by comprising: It includes: The transceiver module is configured to receive first configuration information sent by the network device; wherein the first configuration information is used to configure a corresponding data format for a semi-persistent resource, or configure a corresponding first logical channel for a semi-persistent resource; The transceiver module is further configured to send a first data packet using the data format on the semi-persistent resource and / or receive a second data packet using the data format based on the first configuration information. A network device, characterized in that It includes: The transceiver module is configured to send first configuration information to the terminal; wherein the first configuration information is used to configure a corresponding data format for a semi-persistent resource, or configure a corresponding first logical channel for a semi-persistent resource; The transceiver module is further configured to receive a first data packet using the data format on the semi-persistent resource and / or send a second data packet using the data format based on the first configuration information. A terminal, characterized by comprising: It includes: One or more processors; The processor is used to execute the communication method in any of claims 1-10. A network device, characterized in that It includes: One or more processors; The processor is used to execute the communication method in any of claims 11-19. A communication system characterized by It includes: The terminal, and the first device is configured to implement the communication method in any of claims 1-10; A network device, the second device being configured to implement the communication method of any of claims 11-19. A storage medium storing instructions, the instructions comprising: The instructions, when run on a communication device, cause the communication device to perform the communication method of any of claims 1-10 or 11-19. A computer program product comprising a computer program, characterized in that The computer program, when executed by a processor, is for implementing the communication method of any of claims 1-10 or 11-19.

Images