Communication method and device, terminal equipment and network equipment

Abstract

The invention discloses a communication method and device, terminal equipment and network equipment, and relates to the technical field of communication. In order to avoid the problems of high block error rate, low resource efficiency, poor self-adaption and the like caused by direct transmission of a first RRC message, the invention provides a transmission and feedback method based on load segmentation and step-by-step. In the method, a load of a first RRC message is divided into a first segment and a second segment, and the first segment and the second segment are transmitted in batches, so that one-time transmission of the first RRC message is divided into two-time transmission in sequence. And then, the network firstly transmits the first message and then feeds back the first message through the second message, so that an independent'transmission-feedback 'closed loop is completed. Finally, the latest channel information is provided for the network based on the second message so as to be used for deciding the optimal transmission strategy of the second segment, the transmission strategy is dynamically adjusted, and the transmission reliability, the resource efficiency and the link adaptation of the second segment are improved.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a communication method and apparatus, terminal equipment, and network equipment. Background Art

[0002] With the evolution of communication technologies, the complexity and flexibility of network configurations continue to increase. Radio Resource Control (RRC) messages, as key control signaling, are responsible for carrying important information such as the establishment, modification, and release of network resources.

[0003] However, since the payload length / size of RRC messages may be large, in scenarios with poor signal coverage, high latency, and unstable channel quality, such as non-terrestrial networks (NTN), mobile edge computing, or cell edge, direct transmission of RRC messages by the network may lead to problems such as high block error rate, low resource efficiency, and poor adaptability. Summary of the Invention

[0004] The present application provides a communication method and apparatus, a terminal device, and a network device, in the hope of implementing a method of transmission and feedback based on load segmentation and steps, so as to achieve the purpose of improving transmission reliability, resource efficiency, and adaptability.

[0005] In a first aspect, the present application provides a communication method, comprising: receiving a first message, where the first message is an RRC message including a first segment in the first RRC message; Sending a second message, where the second message is an RRC message used to confirm successful completion of the first message; The payload of the first RRC message is divided into a first segment and a second segment. The first segment is part of the fields in the payload of the first RRC message, and the second segment is the remaining fields in the payload of the first RRC message except the first segment.

[0006] It can be seen that in order to avoid problems such as a high block error rate, low resource efficiency, and poor adaptability caused by directly transmitting the first RRC message, the present application divides the payload of the first RRC message into a first segment and a second segment to achieve the following objectives: Compared to directly transmitting the first RRC message all at once, since the payload of the first RRC message is divided into a first segment and a second segment, the present application can transmit the first segment and the second segment sequentially, thereby dividing the transmission of the first RRC message into two transmissions to improve transmission flexibility. In this way, after encapsulating the first segment into an RRC message (i.e., the first message), the network can first transmit the first message to transmit some fields of the first RRC message first, and then provide feedback on the successful completion of the first message through the second message, thereby completing an independent "transmission-feedback" closed loop.

[0007] Because the payload length of the first message is smaller than that of the first RRC message, the transmission of the first message is less prone to bit errors than the transmission of the first RRC message, and the transmission resources of the first message are less than the transmission resources of the first RRC message. In this way, the network can prioritize the transmission of some fields of the first RRC message with a lower block error rate and transmission resources, ensuring the transmission reliability and resource efficiency of these fields. Especially in scenarios such as unstable channel quality and resource constraints, the first message can prioritize the successful configuration of some information to the terminal device so that some RRC-related processing can be carried out in a timely manner.

[0008] Compared to directly transmitting the first RRC message, where the network may not be able to determine the optimal transmission strategy for the first RRC message based on the latest channel information, since the present application requires feedback on the successful completion of the first message via a second message, the present application can provide the network with the latest channel information (i.e., the channel information corresponding to the second message) via the second message. For example, the network can obtain the latest channel information based on the DMRS in the second message. In this way, the network can determine the optimal transmission strategy for the second segment based on the latest channel information, dynamically adjust the transmission strategy, and ensure transmission reliability, resource efficiency, and link adaptability when subsequently transmitting the second segment.

[0009] In a possible example of the first aspect, a length of the first segment is smaller than a length of the second segment.

[0010] As can be seen, because the length of the first segment is smaller than that of the second segment, the transmission reliability and resource efficiency of the second segment may be lower than those of the first segment. Therefore, this embodiment can prioritize the transmission of the first segment with a lower block error rate and transmission resources, and then optimize the transmission strategy for the second segment based on feedback from the first segment, thereby improving the transmission success rate of the second segment and thus the transmission reliability and resource efficiency of the second segment.

[0011] In a possible example of the first aspect, the first message includes a first RRC transaction identifier field, a first key extension field, and a first non-key extension field; The first segment is in the first key extension field and / or the first non-key extension field; The first RRC transaction identifier field is used to identify the RRC transaction of the first message; The first key extension field is used to carry key configuration information of the first message; The first non-critical extension field is used to carry non-critical configuration information of the first message.

[0012] It can be seen that when parsing the first message, the terminal device can obtain the RRC transaction of the first message through the first RRC transaction identification field, and the terminal device must identify the first key extension field. At the same time, when encountering an unrecognizable first non-key extension field, it can be safely ignored without causing the first message parsing to fail.

[0013] In this way, if the first segment is in the first key extension field, all fields in the first segment must be recognized; if the first segment is in the first non-key extension field, all fields in the first segment are optional and can be ignored; if the first segment is in the first key extension field and the first non-key extension field, some fields in the first segment must be recognized, and the remaining fields are optional and can be ignored.

[0014] In a possible example of the first aspect, the first non-critical extension field includes a first segment sequence number field and / or a first last segment field; A first segment sequence number field indicates the sequence number of the first segment in the segments obtained by dividing the payload of the first RRC message; The first last segment field indicates that the first segment is not the last segment among the segments obtained by dividing the payload of the first RRC message.

[0015] As can be seen, when parsing the first message, the terminal device can obtain the sequence number of the first segment through the first segment sequence number field. At the same time, because the first segment sequence number field and / or the first last segment field are in the non-critical extension field, if the terminal device cannot recognize the first segment sequence number field and / or the first last segment field, it can safely ignore them without causing the first message parsing to fail.

[0016] In a possible example of the first aspect, the first RRC message includes an RRC reconfiguration message; The first segment includes the radio bearer configuration field in the RRC reconfiguration message; The second segment includes the secondary cell group field and the measurement configuration field in the RRC reconfiguration message.

[0017] It can be seen that since the payload length of the RRC reconfiguration message is relatively large, this embodiment can divide the payload of the RRC reconfiguration message into a first segment and a second segment, the first segment includes the radio bearer configuration field, and the second segment includes the secondary cell configuration field and the measurement configuration field.

[0018] In this way, because the network prioritizes transmitting the first segment to the terminal device, the terminal device can receive the radio bearer configuration field first, so that it can prioritize radio bearer related processing based on the radio bearer configuration field. After the second segment is transmitted, the secondary cell configuration and measurement configuration related processing will be carried out.

[0019] In a possible example of the first aspect, the first RRC message is an RRC message transmitted by the network after the terminal device successfully accesses the cell; or, The first RRC message is an RRC message transmitted by the network after the terminal device successfully enters the RRC connected state; or, The first RRC message is an RRC message transmitted by the network after the terminal device completes random access.

[0020] It can be seen that since the terminal device successfully accesses the cell, successfully enters the RRC connected state, or completes random access, the terminal device is in the RRC connected state. In this way, the network device can make corresponding decisions (such as modification, release, maintenance, or restoration) on the RRC connection through the first RRC message.

[0021] In a possible example of the first aspect, the first message is repeatedly transmitted K1 times, where the value of K1 is an integer greater than or equal to 1.

[0022] It can be seen that by transmitting the same content of the first message K1 times, diversity gain or redundant transmission is achieved to improve the reception success rate of the first message.

[0023] In a possible example of the first aspect, K1 is a value specified by the protocol or set by default; or, K1 is a value determined based on the number of repeated transmissions of message 4 in the random access process; or, K1 is a value determined based on the channel information corresponding to message 3 in the random access process.

[0024] It can be seen that the network can determine that the number of repeated transmissions of the first message is K1 in accordance with the protocol provisions or default settings; or, the network determines that the number of repeated transmissions of the first message is K1 based on the number of repeated transmissions of Msg4; or, the network determines that the number of repeated transmissions of the first message is K1 based on the channel information corresponding to Msg3, thereby improving the reception success rate of the first message by repeatedly transmitting the first message.

[0025] In a possible example of the first aspect, the method further includes: Send device capability information, where the device capability information indicates that the terminal device supports payload splitting processing of the first RRC message.

[0026] It can be seen that the device capability information is used to report to the network that the terminal device supports the load splitting processing of the first RRC message.

[0027] In a possible example of the first aspect, the method further includes: receiving a third message, where the third message is an RRC message including the second segment; A fourth message is sent, where the fourth message is an RRC message used to confirm that the integration of the first segment and the second segment is successfully completed.

[0028] It can be seen that in order to avoid problems such as a high block error rate, low resource efficiency, and poor flexibility caused by directly transmitting the first RRC message, this embodiment divides the payload of the first RRC message into a first segment and a second segment to achieve the following objectives: Compared to directly transmitting the first RRC message all at once, since the payload of the first RRC message is divided into a first segment and a second segment, this embodiment can transmit the first segment and the second segment sequentially, thereby dividing the single transmission of the first RRC message into two transmissions to improve transmission flexibility. In this way, the network can first transmit the first segment, and after the transmission and feedback of the first segment are completed, transmit the second segment via a third message to transmit the remaining fields of the first RRC message. Finally, feedback is provided via a fourth message to confirm the successful integration of the first segment and the second segment, thereby completing a two-step independent "transmission-feedback" closed loop.

[0029] Compared to the situation where the network may not be able to decide the optimal transmission strategy for the first RRC message based on the latest channel information before directly transmitting the first RRC message, since this embodiment can provide the network with the latest channel information through the second message, the network can decide the optimal transmission strategy for the third message based on the latest channel information, thereby dynamically adjusting the transmission strategy and ensuring transmission reliability, resource efficiency and link adaptability when transmitting the second segment.

[0030] In a possible example of the first aspect, the third message includes a second RRC transaction identifier field, a second key extension field, and a second non-key extension field; The second segment is in the second key extension field and / or the second non-key extension field; The second RRC transaction identifier field is used to identify the RRC transaction corresponding to the third message; The second key extension field is used to carry key configuration information of the third message; The second non-critical extension field is used to carry non-critical configuration information of the third message.

[0031] It can be seen that when parsing the third message, the terminal device can obtain the RRC transaction of the third message through the second RRC transaction identifier field, and the terminal device must identify the second key extension field. At the same time, if the second non-key extension field cannot be identified, it can be safely ignored without causing the parsing of the third message to fail.

[0032] In this way, if the second segment is in the second key extension field, all fields in the second segment must be recognized; if the second segment is in the second non-key extension field, all fields in the second segment are optional and can be ignored; if the second segment is in the second key extension field and the second non-key extension field, some fields in the second segment must be recognized, and the remaining fields are optional and can be ignored.

[0033] In a possible example of the first aspect, the second non-critical extension field includes a second segment sequence number field and / or a second last segment field; A second segment sequence number field indicates the sequence number of the second segment in the segments obtained by dividing the payload of the first RRC message; The second last segment field indicates that the second segment is the last segment among the segments obtained by dividing the payload of the first RRC message.

[0034] As can be seen, when parsing the third message, the terminal device can obtain the sequence number of the second segment through the second segment sequence number field. At the same time, because the second segment sequence number field and / or the second last segment field are in the non-critical extension field, if the terminal device cannot recognize the second segment sequence number field and / or the second last segment field, it can safely ignore them without causing the third message to fail to parse.

[0035] In a possible example of the first aspect, the third message is repeatedly transmitted K2 times, where the value of K2 is an integer greater than or equal to 1.

[0036] It can be seen that by transmitting the same content of the third message K2 times, diversity gain or redundant transmission is achieved to improve the reception success rate of the third message.

[0037] In a possible example of the first aspect, K2 is a value determined based on channel information corresponding to the second message.

[0038] It can be seen that since the second message can provide the network with the latest channel information, the network device can decide the optimal transmission strategy for the third message based on the channel information corresponding to the second message, and determine the number of repeated transmissions of the third message to be K2, thereby repeatedly transmitting the third message to improve the reception success rate of the third message.

[0039] The second aspect is a communication method of the present application, comprising: Sending a first message, where the first message is an RRC message including the first segment in the first RRC message; receiving a second message, where the second message is an RRC message used to confirm successful completion of the first message; The payload of the first RRC message is divided into a first segment and a second segment. The first segment is part of the fields in the payload of the first RRC message, and the second segment is the remaining fields in the payload of the first RRC message except the first segment.

[0040] In a possible example of the second aspect, a length of the first segment is smaller than a length of the second segment.

[0041] In a possible example of the second aspect, the first message includes a first RRC transaction identification field, a first key extension field, and a first non-key extension field; The first segment is in the first key extension field and / or the first non-key extension field; The first RRC transaction identifier field is used to identify the RRC transaction of the first message; The first key extension field is used to carry key configuration information of the first message; The first non-critical extension field is used to carry non-critical configuration information of the first message.

[0042] In a possible example of the second aspect, the first non-critical extension field includes a first segment sequence number field and / or a first last segment field; A first segment sequence number field indicates the sequence number of the first segment in the segments obtained by dividing the payload of the first RRC message; The first last segment field indicates that the first segment is not the last segment among the segments obtained by dividing the payload of the first RRC message.

[0043] In a possible example of the second aspect, the first RRC message includes an RRC reconfiguration message; The first segment includes the radio bearer configuration field in the RRC reconfiguration message; The second segment includes the secondary cell group field and the measurement configuration field in the RRC reconfiguration message.

[0044] In a possible example of the second aspect, the first RRC message is an RRC message transmitted by the network after the terminal device successfully accesses the cell; or, The first RRC message is an RRC message transmitted by the network after the terminal device successfully enters the RRC connected state; or, The first RRC message is an RRC message transmitted by the network after the terminal device completes random access.

[0045] In a possible example of the second aspect, the first message is repeatedly transmitted K1 times, where the value of K1 is an integer greater than or equal to 1.

[0046] In a possible example of the second aspect, K1 is a value specified by the protocol or set by default; or, K1 is a value determined based on the number of repeated transmissions of message 4 in the random access process; or, K1 is a value determined based on the channel information corresponding to message 3 in the random access process.

[0047] In a possible example of the second aspect, the method further includes: Device capability information is received, where the device capability information indicates that the terminal device supports payload splitting processing of the first RRC message.

[0048] In a possible example of the second aspect, the method further includes: Sending a third message, where the third message is an RRC message including the second segment; A fourth message is received, where the fourth message is an RRC message used to confirm that integration of the first segment and the second segment is successfully completed.

[0049] In a possible example of the second aspect, the third message includes a second RRC transaction identification field, a second key extension field, and a second non-key extension field; The second segment is in the second key extension field and / or the second non-key extension field; The second RRC transaction identifier field is used to identify the RRC transaction corresponding to the third message; The second key extension field is used to carry key configuration information of the third message; The second non-critical extension field is used to carry non-critical configuration information of the third message.

[0050] In a possible example of the second aspect, the second non-critical extension field includes a second segment sequence number field and / or a second last segment field; A second segment sequence number field indicates the sequence number of the second segment in the segments obtained by dividing the payload of the first RRC message; The second last segment field indicates that the second segment is the last segment among the segments obtained by dividing the payload of the first RRC message.

[0051] In a possible example of the second aspect, the third message is repeatedly transmitted K2 times, where the value of K2 is an integer greater than or equal to 1.

[0052] In a possible example of the second aspect, K2 is a value determined based on channel information corresponding to the second message.

[0053] A third aspect is a communication device of the present application, comprising: A receiving unit, configured to receive a first message, where the first message is an RRC message including a first segment in a first RRC message; a sending unit, configured to send a second message, where the second message is an RRC message used to confirm that the first message is successfully completed; The payload of the first RRC message is divided into a first segment and a second segment. The first segment is part of the fields in the payload of the first RRC message, and the second segment is the remaining fields in the payload of the first RRC message except the first segment.

[0054] In a possible example of the third aspect, a length of the first segment is smaller than a length of the second segment.

[0055] In a possible example of the third aspect, the first message includes a first RRC transaction identifier field, a first key extension field, and a first non-key extension field; The first segment is in the first key extension field and / or the first non-key extension field; The first RRC transaction identifier field is used to identify the RRC transaction of the first message; The first key extension field is used to carry key configuration information of the first message; The first non-critical extension field is used to carry non-critical configuration information of the first message.

[0056] In a possible example of the third aspect, the first non-critical extension field includes a first segment sequence number field and / or a first last segment field; A first segment sequence number field indicates the sequence number of the first segment in the segments obtained by dividing the payload of the first RRC message; The first last segment field indicates that the first segment is not the last segment among the segments obtained by dividing the payload of the first RRC message.

[0057] In a possible example of the third aspect, the first RRC message includes an RRC reconfiguration message; The first segment includes the radio bearer configuration field in the RRC reconfiguration message; The second segment includes the secondary cell group field and the measurement configuration field in the RRC reconfiguration message.

[0058] In a possible example of the third aspect, the first RRC message is an RRC message transmitted by the network after the terminal device successfully accesses the cell; or, The first RRC message is an RRC message transmitted by the network after the terminal device successfully enters the RRC connected state; or, The first RRC message is an RRC message transmitted by the network after the terminal device completes random access.

[0059] In a possible example of the third aspect, the first message is repeatedly transmitted K1 times, where the value of K1 is an integer greater than or equal to 1.

[0060] In a possible example of the third aspect, K1 is a value specified by the protocol or set by default; or, K1 is a value determined based on the number of repeated transmissions of message 4 in the random access process; or, K1 is a value determined based on the channel information corresponding to message 3 in the random access process.

[0061] In a possible example of the third aspect, the sending unit is further used to send device capability information, where the device capability information indicates that the terminal device supports payload splitting processing of the first RRC message.

[0062] In a possible example of the third aspect, the receiving unit is further configured to receive a third message, where the third message is an RRC message including the second segment; The sending unit is further used to send a fourth message, where the fourth message is an RRC message used to confirm that the integration of the first segment and the second segment is successfully completed.

[0063] In a possible example of the third aspect, the third message includes a second RRC transaction identification field, a second key extension field, and a second non-key extension field; The second segment is in the second key extension field and / or the second non-key extension field; The second RRC transaction identifier field is used to identify the RRC transaction corresponding to the third message; The second key extension field is used to carry key configuration information of the third message; The second non-critical extension field is used to carry non-critical configuration information of the third message.

[0064] In a possible example of the third aspect, the second non-critical extension field includes a second segment sequence number field and / or a second last segment field; A second segment sequence number field indicates the sequence number of the second segment in the segments obtained by dividing the payload of the first RRC message; The second last segment field indicates that the second segment is the last segment among the segments obtained by dividing the payload of the first RRC message.

[0065] In a possible example of the third aspect, the third message is repeatedly transmitted K2 times, where the value of K2 is an integer greater than or equal to 1.

[0066] In a possible example of the third aspect, K2 is a value determined based on channel information corresponding to the second message.

[0067] A fourth aspect is a communication device of the present application, comprising: a sending unit, configured to send a first message, where the first message is an RRC message including a first segment in a first RRC message; a receiving unit, configured to receive a second message, where the second message is an RRC message used to confirm successful completion of the first message; The payload of the first RRC message is divided into a first segment and a second segment. The first segment is part of the fields in the payload of the first RRC message, and the second segment is the remaining fields in the payload of the first RRC message except the first segment.

[0068] In a possible example of the fourth aspect, a length of the first segment is smaller than a length of the second segment.

[0069] In a possible example of the fourth aspect, the first message includes a first RRC transaction identification field, a first key extension field, and a first non-key extension field; The first segment is in the first key extension field and / or the first non-key extension field; The first RRC transaction identifier field is used to identify the RRC transaction of the first message; The first key extension field is used to carry key configuration information of the first message; The first non-critical extension field is used to carry non-critical configuration information of the first message.

[0070] In a possible example of the fourth aspect, the first non-critical extension field includes a first segment sequence number field and / or a first last segment field; A first segment sequence number field indicates the sequence number of the first segment in the segments obtained by dividing the payload of the first RRC message; The first last segment field indicates that the first segment is not the last segment among the segments obtained by dividing the payload of the first RRC message.

[0071] In a possible example of the fourth aspect, the first RRC message includes an RRC reconfiguration message; The first segment includes the radio bearer configuration field in the RRC reconfiguration message; The second segment includes the secondary cell group field and the measurement configuration field in the RRC reconfiguration message.

[0072] In a possible example of the fourth aspect, the first RRC message is an RRC message transmitted by the network after the terminal device successfully accesses the cell; or, The first RRC message is an RRC message transmitted by the network after the terminal device successfully enters the RRC connected state; or, The first RRC message is an RRC message transmitted by the network after the terminal device completes random access.

[0073] In a possible example of the fourth aspect, the first message is repeatedly transmitted K1 times, where the value of K1 is an integer greater than or equal to 1.

[0074] In a possible example of the fourth aspect, K1 is a value specified by the protocol or set by default; or, K1 is a value determined based on the number of repeated transmissions of message 4 in the random access process; or, K1 is a value determined based on the channel information corresponding to message 3 in the random access process.

[0075] In a possible example of the fourth aspect, the receiving unit is further used to receive device capability information, where the device capability information indicates that the terminal device supports payload splitting processing of the first RRC message.

[0076] In a possible example of the fourth aspect, the sending unit is further configured to send a third message, where the third message is an RRC message including the second segment; The receiving unit is further used to receive a fourth message, where the fourth message is an RRC message used to confirm that the integration of the first segment and the second segment is successfully completed.

[0077] In a possible example of the fourth aspect, the third message includes a second RRC transaction identification field, a second key extension field, and a second non-key extension field; The second segment is in the second key extension field and / or the second non-key extension field; The second RRC transaction identifier field is used to identify the RRC transaction corresponding to the third message; The second key extension field is used to carry key configuration information of the third message; The second non-critical extension field is used to carry non-critical configuration information of the third message.

[0078] In a possible example of the fourth aspect, the second non-critical extension field includes a second segment sequence number field and / or a second last segment field; A second segment sequence number field indicates the sequence number of the second segment in the segments obtained by dividing the payload of the first RRC message; The second last segment field indicates that the second segment is the last segment among the segments obtained by dividing the payload of the first RRC message.

[0079] In a possible example of the fourth aspect, the third message is repeatedly transmitted K2 times, where the value of K2 is an integer greater than or equal to 1.

[0080] In a possible example of the fourth aspect, K2 is a value determined based on channel information corresponding to the second message.

[0081] In a fifth aspect, the method described in the first aspect is applied to a terminal device.

[0082] In a sixth aspect, the method described in the second aspect is applied to network equipment.

[0083] The seventh aspect is a terminal device of the present application, comprising a processor, a memory, and a computer program or instructions stored in the memory, wherein the processor executes the computer program or instructions to implement the method described in the first aspect above.

[0084] The eighth aspect is a network device of the present application, comprising a processor, a memory, and a computer program or instructions stored in the memory, wherein the processor executes the computer program or instructions to implement the method described in the second aspect above.

[0085] A ninth aspect is a chip of the present application, comprising a processor, wherein the processor executes the method described in the first or second aspect. Optionally, the chip further comprises an interface circuit, the processor being connected to the interface circuit, and the interface circuit being used to send and receive information.

[0086] The tenth aspect is a chip module of the present application, comprising a transceiver component and a chip, the chip comprising a processor, wherein the processor executes the method described in the first or second aspect above, and the transceiver component is used to send and receive information.

[0087] The eleventh aspect is a communication system of the present application, comprising the terminal device of the seventh aspect and the network device of the eighth aspect.

[0088] The twelfth aspect is a computer-readable storage medium of the present application, wherein the computer-readable storage medium stores a computer program or instructions, and when the computer program or instructions are executed, the method described in the first or second aspect above is implemented.

[0089] A thirteenth aspect is a computer program product of the present application, comprising a computer program or instructions, wherein when the computer program or instructions are executed, the method described in the first or second aspect is implemented. Exemplarily, the computer program product may be a software installation package.

[0090] It is worth noting that the beneficial effects brought about by the technical solutions of the second to thirteenth aspects can be referred to the technical effects brought about by the technical solution of the first aspect mentioned above, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0091] Figure 1 This is a schematic diagram of the architecture of a communication system according to an embodiment of the present application; Figure 2 This is a schematic diagram of the architecture of another communication system according to an embodiment of the present application; Figure 3 1 is a flow chart of a method for load splitting and step-by-step transmission and feedback according to an embodiment of the present application; Figure 4 This is a flow chart of a communication method according to an embodiment of the present application; Figure 5 This is a flow chart of a method for load splitting and step-by-step transmission and feedback after a four-step random access process according to an embodiment of the present application; Figure 6 This is a flow chart of another communication method according to an embodiment of the present application; Figure 7 This is a flow chart of another communication method according to an embodiment of the present application; Figure 8 This is a flow chart of another method for transmission and feedback based on load splitting and step-by-step transmission according to an embodiment of the present application; Figure 9 This is a block diagram of the functional units of a communication device according to an embodiment of the present application; Figure 10 This is a block diagram of the functional units of another communication device according to an embodiment of the present application; Figure 11 This is a schematic diagram of the structure of a terminal device according to an embodiment of the present application; Figure 12 It is a structural diagram of a network device according to an embodiment of the present application. DETAILED DESCRIPTION

[0092] It should be understood that the terms "first," "second," and the like in the embodiments of the present application are used to distinguish between different objects, rather than to describe a specific order. In addition, the terms "including," "having," and any variations thereof, are intended to cover non-exclusive inclusions. For example, a process, method, software, product, or device comprising a series of steps or units is not limited to the listed steps or units, but may also include steps or units not listed, or may also include other steps or units inherent to these processes, methods, products, or devices.

[0093] The term "embodiment" as used in the embodiments of this application means that a particular feature, structure, or characteristic described in conjunction with the embodiment may be included in at least one embodiment of this application. The appearance of this phrase in various locations in the specification does not necessarily refer to the same embodiment, nor does it refer to independent or alternative embodiments that are mutually exclusive with other embodiments. It is understood, both explicitly and implicitly, by those skilled in the art that the embodiments described herein may be combined with other embodiments.

[0094] In the embodiments of the present application, "at least one" or "at least one item" refers to one or more, and "a plurality" refers to two or more.

[0095] In the embodiments of the present application, "and / or" describes the association relationship between associated objects, indicating that three relationships may exist. For example, A and / or B can represent the following three situations: A exists alone, A and B exist at the same time, and B exists alone. A and B can be singular or plural.

[0096] In the embodiments of this application, "at least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, "at least one of a, b, or c" can represent the following seven situations: a; b; c; a and b; a and c; b and c; a, b, and c. Each of a, b, and c can be an element or a set containing one or more elements.

[0097] In the embodiments of this application, "equal to" can be used in conjunction with "greater than" to apply to the technical solution adopted when "greater than" is used, and can also be used in conjunction with "less than" to apply to the technical solution adopted when "less than" is used. When "equal to" is used in conjunction with "greater than", it should not be used in conjunction with "less than"; when "equal to" is used in conjunction with "less than", it should not be used in conjunction with "greater than".

[0098] In the embodiments of this application, the terms "of," "corresponding," "relevant," "corresponding," "associated," "related," and "mapped" may sometimes be used interchangeably. It should be noted that when no distinction is emphasized, the concepts or meanings to be expressed are consistent.

[0099] The “network” in the embodiments of the present application can be expressed as the same concept as the “system”, and the communication system is the communication network.

[0100] The “instruction” in the embodiments of the present application can be expressed as the same concept as “configuration” and the like.

[0101] The "connection" in the embodiments of the present application refers to various connection methods such as direct connection or indirect connection to achieve communication between devices, and is not specifically limited to this.

[0102] The communication system of this embodiment is described below with an example.

[0103] The technical solutions of the embodiments of the present application can be applied to various communication systems. For example, a long term evolution (LTE) system, an advanced long term evolution (LTE-A) system, a new radio (NR) system, an evolution system of the NR system, an LTE-based access to unlicensed spectrum (LTE-U) system on an unlicensed spectrum, an NR-based access to unlicensed spectrum (NR-U) system on an unlicensed spectrum, a non-terrestrial network (NTN) system, a universal mobile telecommunication system (UMTS), or a future communication system.

[0104] It should be noted that some communication systems support a limited number of user connections and are easy to implement. With the development of communication technology, the communication system of this application may also support device-to-device (D2D) communication, machine-to-machine (M2M) communication, machine-type communication (MTC), vehicle-to-vehicle (V2V) communication, vehicle-to-everything (V2X) communication, or narrowband Internet of Things (NB-IoT) communication, etc.

[0105] In a possible example, the communication system of this embodiment may support beamforming, carrier aggregation (CA), dual connectivity (DC) or standalone (SA) deployment scenarios, etc.

[0106] In one possible example, the communication system of this embodiment can support communication scenarios using unlicensed spectrum. In this embodiment of the present application, the unlicensed spectrum can also be considered as shared spectrum. Alternatively, this embodiment of the present application can also be applied to licensed spectrum. Licensed spectrum can also be considered as unshared spectrum.

[0107] For example, a network architecture of a communication system in an embodiment of the present application is as follows: Figure 1 As shown. Figure 1 In the embodiment, the communication system 10 may include a network device 110 and a terminal device 120. The terminal device 120 may communicate with the network device 110 in a wireless manner.

[0108] certainly, Figure 1 This is merely an example of a network architecture for a communication system and does not limit the network architecture of the communication system of the embodiments of the present application. For example, the communication system 10 may further include a server or other devices, or the communication system 10 may include other network devices in addition to the network device 110, or the communication system 10 may include other terminal devices in addition to the terminal device 120.

[0109] The terminal device of this embodiment is described below with an example.

[0110] In one possible example, a terminal device is a device with transceiver functions, also referred to as a terminal, user equipment (UE), remote UE, relay UE, access terminal device, user unit, user station, mobile station, mobile station, remote station, mobile device, user terminal device, intelligent terminal device, wireless communication device, user agent, or user apparatus. It should be noted that a relay device is a terminal device that can provide relay forwarding services for other terminal devices (including remote terminal devices).

[0111] For example, terminal devices include mobile phones, tablet computers, computers with wireless transceiver functions, virtual reality (VR) terminal devices, augmented reality (AR) terminal devices, wireless terminal devices in industrial control, wireless terminal devices in unmanned autonomous driving, wireless terminal devices in remote medical care, wireless terminal devices in smart grids, wireless terminal devices in transportation safety, wireless terminal devices in smart cities, or wireless terminal devices in smart homes.

[0112] For another example, the terminal device includes a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a future communication system, or a terminal device in a future evolved public land mobile network (PLMN), etc.

[0113] In one possible example, a terminal device includes a unit or device that provides wireless communication functionality for the terminal device, such as a chip system, a chip, a chip module, or a radio. The chip system may include a chip or other discrete components; the radio may include a main radio (MR) and / or a low power radio (LR).

[0114] In one possible example, the terminal device is deployed on land, including indoors or outdoors, handheld, wearable, or vehicle-mounted; it can be deployed on the water (such as a ship); or it can be deployed in the air (such as an airplane, balloon, and satellite).

[0115] In one possible example, the terminal device is a chip, a chip module, a device, or a unit, etc., without specific limitation.

[0116] The network device of this embodiment is described below with examples.

[0117] In a possible example, the network device is a device with transceiver functions, which can be used to communicate with a terminal device.

[0118] In one possible example, the network device includes a device that provides wireless communication functionality for the network device, such as a chip system, a chip, or a chip module. The chip system may include a chip or other discrete devices.

[0119] In one possible example, a network device provides services for a cell, and a terminal device in the cell can communicate with the network device using transmission resources (such as spectrum resources). The cell can be a macro cell, a small cell, a metro cell, a micro cell, a pico cell, or a femto cell.

[0120] In one possible example, the network device is mobile, for example, a mobile device. Alternatively, the network device is a satellite or a balloon station. For example, the satellite is a low Earth orbit (LEO) satellite, a medium Earth orbit (MEO) satellite, a geostationary Earth orbit (GEO) satellite, or a high elliptical orbit (HEO) satellite. Alternatively, the network device may be a base station located on land or in water.

[0121] In a possible example, the network device includes an access network device and / or a core network (CN) device.

[0122] The following is an example of access network equipment.

[0123] In one possible example, the access network device is called a radio access network (RAN) node. The RAN is a network composed of multiple RAN nodes (e.g., 5G-RAN nodes) that implements wireless physical layer functions, resource scheduling and radio resource management, radio access control, and mobility management functions. The RAN can connect to the user plane function (UPF) via the user plane interface N3 and can be used to transmit data from terminal devices. The RAN can establish a control plane signaling connection with the access and mobility management function (AMF) via the control plane interface N2 to implement functions such as radio access bearer control. A RAN node can be any device with wireless transceiver functions, including but not limited to a 5G base station (gNB), an evolved base station (eNB), an access point (AP), a world interoperability for microwave access base station (WiMAX BS), a transmission receiving point (TRP), a wireless relay node, a wireless backhaul node, a master node (MN) in a dual-connectivity architecture, a second node or a secondary node (SN) in a dual-connectivity architecture, and the like.

[0124] In one possible example, an access network device refers to a device used to communicate with a terminal device. For example, the access network device may include a base transceiver station (BTS) in a global system of mobile communication (GSM) system or a code division multiple access (CDMA) system, a base station (nodeB, NB) in a wideband code division multiple access (WCDMA) system, an evolutionary node base (eNB) in an LTE system, a wireless controller in a cloud radio access network (CRAN) scenario, a relay station, an access point, a vehicle-mounted device, a wearable device, an access network device in a 5G network, an access network device in a future network, or an access network device in a future evolved PLMN network, etc.

[0125] In one possible example, in 5G NR, the functionality of access network equipment is divided into two parts, known as centralized unit (CU)-distributed unit (DU) separation. From a protocol stack perspective, the CU includes the radio resource control (RRC) layer and packet data convergence protocol (PDCP) layer of the LTE base station, while the DU includes the radio link control (RLC) layer, media access control (MAC) layer, and physical (PHY) layer of the LTE base station. In a typical 5G base station deployment, the CU and DU can be physically connected via optical fiber, and logically there is a specially defined F1 interface for communication between the CU and DU. From a functional perspective, the CU is primarily responsible for radio resource control and configuration, cross-cell mobility management, bearer management, etc. The DU is primarily responsible for scheduling, physical signal generation, and transmission.

[0126] In one possible example, the access network equipment includes a macro base station, a micro base station, a pico base station, a small station, a relay station, or a balloon station, etc.

[0127] The following is an example of core network equipment.

[0128] In one possible example, core network equipment includes network elements that provide various functions. "Network element" may also be referred to as an entity, device, apparatus, or module, without specific limitation. Furthermore, for ease of understanding and explanation, the term "network element" is omitted in some descriptions. For example, a network exposure function (NEF) network element is referred to as NEF. In this case, "NEF" should be understood as either an NEF network element or an NEF entity. The following descriptions of identical or similar situations are omitted.

[0129] For example, core network equipment may include a mobility management entity (MME), a broadcast multicast service center (BMSC), or corresponding functional entities in a 5G system. The corresponding functional entities in a 5G system include core network control plane (CP) or user plan (UP) network functions, and the core network control plane may also be understood as the core network control plane function (CPF) entity.

[0130] In a possible example, the network elements included in the core network device include at least one of the following: session management function (SMF), user plane function (UPF), policy control function (PCF), NEF, authentication server function (AUSF), unified data management (UDM), network slice selection function (NSSF), network repository function (NRF), application function (AF), unified data repository (UDR), network data analytics function (NWDAF), service control point (SCP), network slice admission control function (NSACF), or network slice specific authentication and authorization function (NSSAAF), etc.

[0131] It should be noted that terminal devices can be connected to access network devices wirelessly, and access network devices can be connected to core network devices wirelessly or wired. Core network devices can be connected to the data network (DN). Access network devices and core network devices can be independent and distinct physical devices, or they can integrate the functions of core network devices and the logical functions of access network devices into the same physical device, or they can integrate some core network device functions and some access network device functions into a single physical device.

[0132] For example, Figure 2 This is another schematic diagram of the architecture of a communication system according to an embodiment of the present application. Figure 2In the embodiment, the communication system 20 includes UE, (R)AN, UPF, DN, SMF, SCP, NSACF, AMF, AUSF, NSSAAF, AF, UDM, PCF, NRF, NEF, and NSSF. Among them, the UE is connected to the AMF through the N1 interface, the (R)AN is connected to the UPF through the N2 interface, the UPF is connected through the N6 interface DN, the UPF is connected to other UPFs through the N9 interface, the UPF is connected to the SMF through the N4 interface, the SMF is connected to other network elements through the Nsmf interface, the AMF is connected to other network elements through the Namf interface, the AUSF is connected to other network elements through the Nausf interface, the NSSAAF is connected to other network elements through the Nnssaaf interface, the SCP is connected to other network elements through the Nscp interface, the NSACF is connected to other network elements through the Nnsacf interface, the AF is connected to other network elements through the Naf interface, the UDM is connected to other network elements through the Nudm interface, the PCF is connected to other network elements through the Npcf interface, the NRF is connected to other network elements through the Nnrf interface, the NEF is connected to other network elements through the Nnef interface, and the NSSF is connected to other network elements through the Nnssf interface.

[0133] It should be noted that Figure 2 The names of the network elements included in the above are just names and do not limit the functions of the network elements themselves. In 5G networks and other future networks, the above network elements may also have other names, and this is not specifically limited. For example, in future communication systems, some or all of the above network elements may continue to use 5G terminology, or may have other names, etc., which are uniformly explained here and will not be repeated below.

[0134] in addition, Figure 2 The various network elements in the network do not have to exist at the same time, and the required network elements can be determined based on the needs. Figure 2 The connection relationship between the various network elements in the network is not unique and can be adjusted according to needs. It is understood that the above network elements or functions can be network components in hardware devices, software functions running on dedicated hardware, or virtualized functions instantiated on a platform (e.g., a cloud platform).

[0135] certainly, Figure 2 This is merely an example of a network architecture of a communication system and does not constitute a limitation on the network architecture of the communication system in the embodiments of the present application.

[0136] The communication system of this embodiment has been described above. The technical solution of this embodiment will be described in detail below.

[0137] In scenarios with poor signal coverage, high latency, and unstable channel quality, such as NTN, mobile edge computing, or cell edge, directly transmitting an RRC message with a large payload length / size may face the following severe challenges: (1) Large block error rate As the payload length of the RRC message increases, the probability of transmission failure in the above scenario increases exponentially. A single RRC message transmission failure will directly lead to RRC process failure, which may cause disconnection and reconnection, seriously affecting user experience and network stability.

[0138] (2) Low resource efficiency Because the larger the payload length of an RRC message, the more transmission resources it requires. While using a repetition mechanism to transmit RRC messages can improve transmission success rates, it also incurs significant resource overhead, especially when channel conditions are not consistently poor.

[0139] (3) Poor flexibility and adaptability Before sending an RRC message, the network device may not be able to obtain the latest channel information and can only make a rough estimate based on historical channel information. It is unable to make the optimal decision for the RRC message transmission task, resulting in a lack of link adaptation, which makes it impossible to achieve link adaptation under uncertain channel information.

[0140] It is worth noting that the latest channel information mentioned in this embodiment includes signal-to-interference plus noise ratio (SINR), power headroom report (PHR), or reference signal receiving power (RSRP).

[0141] In addition, the repeated transmission of the RRC message mentioned in this embodiment refers to multiple transmissions of the same content of the same RRC message, the purpose of which is to improve the success rate of RRC message reception through diversity gain or redundant transmission. The multiple transmissions are part of the same transmission process and are initiated by the network without waiting for feedback from the terminal device.

[0142] Based on this, this embodiment considers optimizing the original RRC message transmission process and proposes a method based on payload segmentation and step-by-step transmission and feedback to address the above challenges and achieve the following objectives: (1) Payload segmentation of RRC messages The payload of the original RRC message is divided into multiple segments (segments / parts), and each segment is encapsulated into a new RRC message. The payload length of each new RRC message is smaller than the payload length of the original RRC message.

[0143] (2) Improve transmission reliability and resource efficiency Since the payload length of each new RRC message is smaller than that of the original RRC message, the transmission of the new RRC message is less prone to bit errors than the transmission of the original RRC message, and the new RRC message requires fewer transmission resources.

[0144] In this way, when a repeated transmission mechanism is adopted to transmit a new RRC message, repeated transmission of the new RRC message has smaller resource overhead than repeated transmission of the original RRC message.

[0145] (3) Step-by-step transmission and feedback The network transmits a new RRC message in batches, and the terminal device needs to provide feedback on the successful completion of the new RRC message in batches to complete an independent "transmission-feedback" closed loop. After completing an independent "transmission-feedback" closed loop for the previous new RRC message, the transmission of the next new RRC message begins.

[0146] For example, Figure 3 As shown, a method based on load splitting and step-by-step transmission and feedback includes the following steps: S310. The network device repeatedly transmits the first new RRC message.

[0147] Correspondingly, the terminal device receives the first new RRC message of the repeated transmission.

[0148] S320. The terminal device provides feedback on the successful completion of the first new RRC message of the repeated transmission.

[0149] Correspondingly, the network device receives this feedback, thereby completing the first independent "transmission-feedback" closed loop.

[0150] S330. The network device repeatedly transmits the second new RRC message.

[0151] Correspondingly, the terminal device receives the second new RRC message that is repeatedly transmitted.

[0152] S340. The terminal device provides feedback on the successful completion of the repeated transmission of the second new RRC message.

[0153] Correspondingly, the network device receives this feedback, thereby completing the second independent "transmission-feedback" closed loop.

[0154] (4) Enhanced flexibility and adaptability Because terminal devices need to transmit and provide feedback in stages, the feedback from the last transmission can provide the network with the latest channel information. For example, the network can obtain the latest channel information based on the demodulation reference signal (DMRS) in the feedback signal from the last transmission.

[0155] As can be seen, the network can dynamically adjust the transmission strategy for the next transmission based on the latest channel information, such as adjusting the modulation and coding scheme (MCS), resource scheduling, or the number of repeated transmissions, thereby achieving link adaptation. This maximizes resource conservation, improves transmission reliability, and enhances transmission flexibility, resolving the problem of link adaptation being difficult to implement under uncertain channel information.

[0156] For example, in the above Figure 3 In the process, the feedback of the first new RRC message can provide the network device with the latest channel information so that the network device can decide the optimal transmission strategy for the second new RRC message based on the latest channel information, realize dynamic adjustment of the transmission strategy, and achieve the purpose of link adaptation.

[0157] In conjunction with the above, the following embodiment uses the interaction between a network device and a terminal device as an example to illustrate a method for load splitting and step-by-step transmission and feedback. The network device in this method may also be a chip, unit, or device, and the terminal device may also be a chip, unit, or device.

[0158] like Figure 4 As shown, Figure 4 This is a flow chart of a communication method according to an embodiment of the present application, comprising the following steps: S410. The network device sends a first message, where the first message is an RRC message including the first segment in the first RRC message.

[0159] Correspondingly, the terminal device receives the first message.

[0160] The payload of the first RRC message is divided into a first segment and a second segment. The first segment is part of the fields in the payload of the first RRC message, and the second segment is the remaining fields in the payload of the first RRC message except the first segment.

[0161] S420. The terminal device sends a second message, where the second message is an RRC message used to confirm that the first message is successfully completed.

[0162] Correspondingly, the network device receives the second message.

[0163] It can be seen that in order to avoid problems such as a high block error rate, low resource efficiency, and poor adaptability caused by directly transmitting the first RRC message, this embodiment divides the payload of the first RRC message into a first segment and a second segment to achieve the following objectives: (1) Compared with directly transmitting the first RRC message in one go, since the payload of the first RRC message is divided into the first segment and the second segment, this embodiment can transmit the first segment and the second segment successively, thereby dividing the one-time transmission of the first RRC message into two transmissions successively to improve transmission flexibility.

[0164] In this way, after encapsulating the first segment into an RRC message (i.e., the first message), the network can first transmit the first message to transmit part of the fields of the first RRC message first, and then provide feedback on the successful completion of the first message through the second message, thereby completing an independent "transmission-feedback" closed loop.

[0165] (2) Since the payload length of the first message is smaller than the payload length of the first RRC message, the transmission of the first message is less prone to bit errors than the transmission of the first RRC message, and the transmission resources of the first message are less than the transmission resources of the first RRC message.

[0166] This allows the network to prioritize the transmission of some fields of the first RRC message with a lower block error rate and transmission resources, ensuring the transmission reliability and resource efficiency of these fields. Especially in scenarios with unstable channel quality and limited resources, the first message can prioritize the successful configuration of some information to the terminal device, allowing for timely execution of some RRC-related processing.

[0167] (3) Compared to the case where the network may not be able to decide the optimal transmission strategy for the first RRC message based on the latest channel information before directly transmitting the first RRC message, since this embodiment requires feedback on the successful completion of the first message through the second message, this embodiment can provide the network with the latest channel information (i.e., the channel information corresponding to the second message) based on the second message. For example, the network obtains the latest channel information based on the DMRS in the second message.

[0168] In this way, the network can decide the optimal transmission strategy for the second segment based on the latest channel information, dynamically adjust the transmission strategy, and ensure transmission reliability, resource efficiency, and link adaptability when subsequently transmitting the second segment.

[0169] The following is an example of the first RRC message.

[0170] In this embodiment, the first RRC message is an RRC message transmitted by the network.

[0171] In one possible example, the first RRC message is an RRC message transmitted by the network after the terminal device successfully accesses the cell (such as the first transmission by the network or any transmission by the network).

[0172] It can be seen that since the terminal device successfully accesses the cell, the terminal device is in the RRC connection state. In this way, the network device can make corresponding decision processing (such as modification, release, maintenance or recovery, etc.) on the RRC connection through the first RRC message.

[0173] In one possible example, the first RRC message is an RRC message transmitted by the network (such as the first network transmission or any network transmission) after the terminal device successfully enters the RRC connection state.

[0174] In this way, the network device can perform corresponding decision processing (such as modification, release, maintenance or restoration, etc.) on the RRC connection through the first RRC message.

[0175] In a possible example, the first RRC message is an RRC message transmitted by the network (such as the first network transmission or any network transmission) after the terminal device completes random access.

[0176] It can be seen that since the terminal device completes random access, the terminal device can successfully enter the RRC connection state. In this way, the network device can make corresponding decision processing (such as modification, release, maintenance or recovery, etc.) on the RRC connection through the first RRC message.

[0177] In one possible example, the first RRC message includes an RRC reconfiguration message. The RRC reconfiguration message is a command for modifying an RRC connection and may carry information such as measurement configuration, mobility control, radio resource configuration (such as resource blocks (RBs), MAC main configuration, and physical channel configuration), and access stratum (AS) security configuration.

[0178] In this way, the network device can modify the RRC connection through an RRC reconfiguration message or an RRC connection reconfiguration message.

[0179] It is worth noting that the RRC reconfiguration message mentioned in this embodiment may also be an RRC connection reconfiguration message, and there is no specific limitation on this.

[0180] In one possible example, the payload length of the first RRC message is large, for example, the payload length of the first RRC message exceeds the maximum length limit of a protocol data unit (PDU), the maximum length limit of a service data unit (SDU), or the maximum buffer capacity of an RRC message.

[0181] The payload of the first RRC message refers to the valid information actually carried in the first RRC message except for the header information of the underlying protocol.

[0182] The payload length of the first RRC message refers to the size or length of the valid information actually carried in the first RRC message, in bytes or bits. For example, the payload length of the first RRC message is 5 bytes.

[0183] The payload of the first RRC message includes a critical extension field (criticalExtensions field) and / or a non-critical extension field (nonCriticalExtensions field), the critical extension field is used to carry critical configuration information of the first RRC message, and the non-critical field is used to carry non-critical configuration information of the first RRC message.

[0184] It should be noted that the key extension field and non-key extension field are an extension mechanism based on the abstract syntax notation one (ASN.1) syntax definition, which is used to support the backward compatibility and functional scalability of RRC messages and ensure that RRC messages can be correctly exchanged between devices of different versions.

[0185] For example, in Table 1, the key extension field is used to carry key configuration information, and the information it carries must be parsed and recognized by the terminal device, otherwise the entire RRC message will be rejected and the corresponding error handling process will be triggered.

[0186] The non-critical extension field can be placed at the end of an RRC message to carry optional or ignorable non-critical configuration information. This allows older devices to safely ignore any unrecognized non-critical extension fields when parsing an RRC message, without causing the RRC message to fail.

[0187] The non-critical extension field can be defined as an extensible sequence and flexibly expanded through the "empty sequence" mechanism. When no non-critical extension information is present, the non-critical extension field exists as an empty sequence. To add new non-critical configuration information, additional fields can be appended to the non-critical extension field without modifying the core RRC message structure.

[0188] In this way, when an old version of the terminal device cannot recognize a new field, it can regard the new field as an "extended part of the empty sequence" and ignore the new field without affecting the parsing of the entire RRC message.

[0189] Table 1

[0190] A key extension field can be a collection of one or more fields, and a non-key extension field can be a collection of one or more fields.

[0191] For example, taking the first RRC message including the RRC reconfiguration message as an example, the key extended fields of the RRC reconfiguration message include at least one of the radio bearer configuration field (radioBearerConfig field), the secondary cell configuration field (secondaryCellGroupfield), or the measurement configuration field (measConfig fied).

[0192] The radio bearer configuration field may be used to configure radio bearer related information, such as modifying or releasing the signaling radio bearer 2 (SRB2) and / or data radio bearer (DRB) and activating AS security.

[0193] The secondary cell configuration field may be used to configure the related information of the secondary cell, such as the type of the secondary cell, the resources of the secondary cell, and the establishment, modification or release of the secondary cell.

[0194] The measurement configuration field may be used to configure measurement information, such as measurement objects, triggering conditions for measurement reports, and measurement resources.

[0195] The first segment and the second segment are described in detail below.

[0196] In this embodiment, the payload length of the first RRC message can directly reflect signaling complexity and resource overhead. For example, a larger payload length of the first RRC message increases the likelihood of bit errors in the first RRC message and requires more transmission resources, thereby reducing transmission reliability and resource efficiency. Based on this, this embodiment divides the payload of the first RRC message into a first segment and a second segment.

[0197] In a possible example, the first segment is used to carry minimum RRC configuration information, and the second segment is used to carry remaining RRC configuration information except the minimum RRC configuration information.

[0198] Among them, the minimum RRC configuration information may refer to the most important (most critical or most core) and short configuration information, so that the terminal device can carry out some important RRC-related processing based on the minimum RRC configuration information.

[0199] In this way, since the network device preferentially transmits the first segment to the terminal device, the terminal device can preferentially receive the minimum RRC configuration information, so as to preferentially and promptly carry out some important RRC-related processing according to the minimum RRC configuration information.

[0200] In one possible example, the length of the first segment is smaller than the length of the second segment.

[0201] The length of the first segment refers to the size or length of the information carried by the first segment, in bytes or bits; the length of the second segment refers to the size or length of the information carried by the second segment, in bytes or bits.

[0202] As can be seen, because the length of the first segment is smaller than that of the second segment, the transmission reliability and resource efficiency of the second segment may be lower than those of the first segment. Therefore, the network can prioritize the transmission of the first segment with a lower block error rate and transmission resources, and then optimize the transmission strategy for the second segment based on feedback from the first segment, thereby improving the transmission success rate of the second segment and thus the transmission reliability and resource efficiency of the second segment.

[0203] In one possible example, the first RRC message includes an RRC reconfiguration message, the first segment includes a radio bearer configuration field in the RRC reconfiguration message, and the second segment includes a secondary cell configuration field and a measurement configuration field in the RRC reconfiguration message.

[0204] It can be seen that since the payload length of the RRC reconfiguration message is relatively large, this embodiment can divide the payload of the RRC reconfiguration message into a first segment and a second segment, the first segment includes the radio bearer configuration field, and the second segment includes the secondary cell configuration field and the measurement configuration field.

[0205] In this way, because the network device preferentially transmits the first segment to the terminal device, the terminal device can preferentially parse the radio bearer configuration field, so that it can preferentially perform radio bearer-related processing based on the radio bearer configuration field, such as establishing SRB2 and / or DRS and activating AS security. Subsequently, after completing the transmission of the second segment, the terminal device can perform secondary cell configuration and measurement configuration related processing.

[0206] Optionally, the first segment may include other fields (such as the master cell group (masterCellGroup) field, etc.) in addition to the radio bearer configuration field, and the second segment may include other fields in addition to the secondary cell configuration field and the measurement configuration field. There is no specific restriction on this.

[0207] The first message and the second message are described below with examples.

[0208] In this embodiment, the network device may encapsulate the first segment into an RRC message (i.e., a first message) and transmit the first message. After the terminal device successfully receives the first message, the terminal device may send an RRC message (i.e., a second message) to provide feedback on the successful completion of the first message.

[0209] In a possible example, the first message includes a first RRC transaction identifier (RRC transaction identifier) ​​field, a first key extension field, and a first non-key extension field.

[0210] It can be understood that the payload of the first message includes the first RRC transaction identifier field, the first key extension field and the first non-key extension field, and the payload length of the first message is smaller than the payload length of the first RRC message.

[0211] The first RRC transaction identification field may be used to identify the RRC transaction of the first message. In this way, the terminal device may learn about the RRC transaction of the first message through the first RRC transaction identification field, so as to correctly parse the first message.

[0212] Among them, the first key extension field can be used to carry key configuration information of the first message.

[0213] It can be understood that the first associated extension field is the associated extension field of the first message. The relevant content of the first key extension field can be found in the "key extension field" in the above "Table 1", which will not be repeated here.

[0214] In this way, the terminal device must parse and identify the first key extension field when parsing the first message, otherwise it will refuse to process the entire RRC message and trigger the corresponding error handling process.

[0215] The first non-critical extension field may be used to carry non-critical configuration information of the first message.

[0216] It can be understood that the first non-associated extension field is a non-associated extension field of the first message. The relevant content of the first non-critical extension field can be found in the "non-critical extension field" in the above "Table 1", which will not be repeated here.

[0217] In this way, if the terminal device encounters an unrecognizable non-critical extension field when parsing the first message, it can safely ignore it without causing the parsing of the first message to fail.

[0218] The first segment is in the first key extension field and / or the first non-key extension field.

[0219] In this way, if the first segment is in the first key extension field, all fields in the first segment must be recognized; if the first segment is in the first non-key extension field, all fields in the first segment are optional and can be ignored; if the first segment is in the first key extension field and the first non-key extension field, some fields in the first segment must be recognized, and the remaining fields are optional and can be ignored.

[0220] Optionally, the first non-critical extension field includes a first segment sequence number field and / or a first last segment field.

[0221] The first segment sequence number field may indicate the sequence number of the first segment in the segments obtained by segmenting the payload of the first RRC message. Of course, the sequence number may also be replaced by an index or an ID. The following mainly uses the sequence number as an example for explanation.

[0222] This is because, in the first RRC message payload being divided into a first segment and a second segment, the first segment and the second segment each have their own sequence number. The sequence number of the first segment is smaller than the sequence number of the second segment, for example, the sequence number of the first segment is 0 and the sequence number of the second segment is 1, so that the network device can send the segments in ascending order of sequence numbers, and the terminal device can integrate the received segments in ascending order of sequence numbers to obtain the entire payload of the first RRC message.

[0223] In this way, the terminal device can obtain the sequence number of the first segment through the first segment sequence number field. At the same time, since the first segment sequence number field is in the non-critical extension field, if the terminal device cannot recognize the first segment sequence number field, it can be safely ignored without causing the first message parsing failure.

[0224] The first last segment field may indicate that the first segment is not the last segment among the segments obtained by dividing the payload of the first RRC message.

[0225] This is because, in the first RRC message payload segmented into the first segment and the second segment, the first segment is the first segment and the second segment is the last segment. The purpose of indicating whether a segment is the last segment is to inform the terminal device whether the transmission of all segments has been completed, so that the terminal device can integrate all segments to obtain the entire payload of the first RRC message after successfully receiving the last segment.

[0226] In this way, the terminal device can use the First Last Segment field to know that the first segment is not the last segment, so that the terminal device can continue to wait for receiving segments until the last segment. At the same time, because the First Last Segment field is a non-critical extension field, if the terminal device encounters an unrecognizable First Last Segment field when parsing the first message, it can safely ignore it without causing the parsing of the first message to fail.

[0227] In a possible example, the first message is repeatedly transmitted K1 times, where the value of K1 is an integer greater than or equal to 1.

[0228] It is understandable that the network device repeatedly transmits the first message K1 times, wherein when the value of K1 is equal to 1, it is equivalent to transmitting the first message only once.

[0229] In this way, by transmitting the same content of the first message K1 times, diversity gain or redundant transmission is achieved to improve the reception success rate of the first message.

[0230] Optionally, K1 is a value specified by the protocol or set by default. In this way, the network device can determine the number of repeated transmissions of the first message as K1 in a manner specified by the protocol or set by default.

[0231] Optionally, K1 is a value determined based on the number of repeated transmissions of message 4 during the random access process.

[0232] This is because the random access process is a fundamental and important process in communication systems. Through the random access process, terminal devices can establish a wireless link with network equipment or achieve uplink and downlink synchronization. The random access process includes a four-step random access process and a two-step random access process.

[0233] During the 4-step random access process, after the network device receives Message 3 (Msg3), it may need to repeatedly transmit Message 4 (Msg4) to the terminal device to improve transmission reliability. Msg3 provides the network device with the latest channel information, allowing the network device to determine the number of retransmissions of Msg4 based on the channel information corresponding to Msg3.

[0234] When the first RRC message is the first RRC message transmitted by the network after the terminal device completes random access, the network device can determine the number of repeated transmissions of the first message as K1 based on the number of repeated transmissions of Msg4. For example, the number of repeated transmissions of Message 4 and the number of repeated transmissions of the first message are both K1.

[0235] For example, Figure 5As shown, the method based on load segmentation and step-by-step transmission and feedback after the four-step random access process includes the following steps: S510. The terminal device sends message 1 (message1, Msg1).

[0236] Correspondingly, the network device receives Msg1.

[0237] Msg1 may also be called a physical random access channel preamble (PRACH preamble).

[0238] Msg1 can be used to request access from the network device so that the network device can estimate the transmission delay between the network device and the terminal device based on Msg1 and calibrate the uplink timing accordingly.

[0239] S520. The network device sends message 2 (Msg2).

[0240] Correspondingly, the terminal device receives Msg2.

[0241] Msg2 may also be called a random access response (RAR).

[0242] Msg2 may include a time adjustment amount required for specifying uplink synchronization, uplink resources scheduled by Msg2, a temporary cell-radio network temporary identifier (TC-RNTI), and the like.

[0243] S530. The terminal device sends message 3 (Msg3).

[0244] Correspondingly, the network device receives Msg3.

[0245] Msg3 may be an RRC setup request (RRCSetupRequest) message.

[0246] Msg3 may contain a common control channel (CCCH) service data unit (SDU) or a cell-radio network temporary identifier (C-RNTI) for conflict resolution.

[0247] Msg3 may provide the network device with the latest current channel information (ie, the channel information corresponding to Msg3). For example, the DMRS in Msg3 may provide the network device with the latest current channel information.

[0248] S540. The network device repeatedly transmits message 4 (Msg4) K1 times.

[0249] Correspondingly, the terminal device receives the repeatedly transmitted Msg4.

[0250] Msg4 may be an RRC setup (RRCSetup) message.

[0251] Msg4 may carry a flag for uniquely identifying a terminal device to indicate a winning terminal device, and other terminal devices that have not won in the conflict resolution will re-initiate random access.

[0252] The network device may determine that the number of repeated transmissions of Msg4 is K1 based on the channel information corresponding to Msg3.

[0253] S550. The terminal device sends message 5 (Msg5).

[0254] Correspondingly, the network device receives Msg5.

[0255] Msg5 may be an RRC Setup Complete (RRCSetupComplete) message.

[0256] S560. The network device repeatedly transmits the first message K1 times.

[0257] Correspondingly, the terminal device receives the repeatedly transmitted first message.

[0258] S570. The terminal device sends a second message.

[0259] Correspondingly, the network device receives the second message.

[0260] Optionally, K1 is a value determined based on channel information corresponding to Msg3 in the random access process.

[0261] This is because, combined with the above content, since the channel information corresponding to Msg3 can determine the number of repeated transmissions of Msg4, and the number of repeated transmissions of Msg4 can determine the number of repeated transmissions of the first message, the network device can determine the number of repeated transmissions of the first message as K1 based on the channel information corresponding to Msg3, thereby improving the reception success rate of the first message by repeatedly transmitting the first message.

[0262] The following is an example of a terminal device reporting to a network device that it has the capability to support the payload splitting processing of the first RRC message.

[0263] In one possible example, since different terminal devices may have different device capabilities, such as some terminal devices may have the ability to support payload splitting processing of the first RRC message, while some terminal devices may not have the ability to support payload splitting processing of the first RRC message, the terminal device can report to the network device whether it has the ability to support payload splitting processing of the first RRC message, so that the network device can know and cache the different device capabilities of these terminal devices.

[0264] Optionally, this embodiment adopts the "terminal device autonomous reporting" method for reporting, that is, the terminal device autonomously reports to the network device whether it has the ability to support the load splitting processing of the first RRC message.

[0265] Optionally, this embodiment adopts the "query first and then report" method for reporting, that is, the network device can first ask the terminal device whether it supports the load splitting processing of the first RRC message, and then the terminal device reports to the network device.

[0266] For example, Figure 6 As shown, Figure 6 This is a flow chart of another communication method according to an embodiment of the present application, comprising the following steps: S610. The network device sends a device capability query message, which is used to inquire whether the terminal device supports the payload splitting processing of the first RRC message.

[0267] Correspondingly, the terminal device receives device capability inquiry information.

[0268] S620. The terminal device sends device capability information, where the device capability information indicates that the terminal device supports payload splitting processing of the first RRC message.

[0269] Correspondingly, the network device receives device capability information.

[0270] S630. The network device sends a first message.

[0271] Correspondingly, the terminal device receives the first message. The content of S630 can be found in the relevant content of S410 above, which will not be described in detail.

[0272] S640. The terminal device sends a second message.

[0273] Correspondingly, the network device receives the second message. The content of S640 can be found in the relevant content of S420 above, which will not be described in detail.

[0274] It can be seen that the device capability query information and the device capability information are used to implement the "query first and then report" method to report that the terminal device supports the payload splitting processing of the first RRC message.

[0275] The following is an example of the transmission and feedback of the first segment and the second segment.

[0276] In one possible example, Figure 7 As shown, Figure 7 This is a flow chart of another communication method according to an embodiment of the present application, comprising the following steps: S710. The network device sends a first message.

[0277] Correspondingly, the terminal device receives the first message. The content in S710 can be found in the relevant content in S410 above, which will not be described in detail.

[0278] S720. The terminal device sends a second message.

[0279] Correspondingly, the network device receives the second message. The content in S720 can be found in the relevant content in S420 above, which will not be described in detail.

[0280] S730. The network device sends a third message, where the third message is an RRC message including the second segment.

[0281] Correspondingly, the terminal device receives the third message.

[0282] S740. The terminal device sends a fourth message, which is an RRC message used to confirm that the integration of the first segment and the second segment is successfully completed.

[0283] The terminal device may integrate the first segment and the second segment, and send a fourth message after the integration is successfully completed.

[0284] Correspondingly, the network device receives the fourth message.

[0285] It can be seen that in order to avoid problems such as a high block error rate, low resource efficiency, and poor flexibility caused by directly transmitting the first RRC message, this embodiment divides the payload of the first RRC message into a first segment and a second segment to achieve the following objectives: (1) Compared to directly transmitting the first RRC message in one go, since the payload of the first RRC message is divided into the first segment and the second segment, this embodiment can transmit the first segment and the second segment successively, thereby dividing the one-time transmission of the first RRC message into two transmissions successively to improve transmission flexibility. In this way, the network can first transmit the first segment, and after the transmission and feedback of the first segment are completed, transmit the second segment through the third message to transmit the remaining fields of the first RRC message, and finally feedback the successful completion of the integration of the first segment and the second segment through the fourth message, thereby completing the two independent "transmission-feedback" closed loop.

[0286] (2) Compared with the case where the network may not be able to decide the optimal transmission strategy for the first RRC message based on the latest channel information before directly transmitting the first RRC message, since the present embodiment can provide the network with the latest channel information through the second message, the network can decide the optimal transmission strategy for the third message based on the latest channel information, thereby dynamically adjusting the transmission strategy and ensuring transmission reliability, resource efficiency, and link adaptability when transmitting the second segment.

[0287] The third message and the fourth message are described below with examples.

[0288] In this embodiment, the network device may encapsulate the second segment into an RRC message (i.e., a third message) and transmit the third message. After the terminal device successfully receives the third message, the terminal device may send an RRC message (i.e., a fourth message) to provide feedback on the successful completion of the third message.

[0289] In a possible example, the third message includes a second RRC transaction identification field, a second key extension field, and a second non-key extension field.

[0290] It can be understood that the payload of the third message includes the second RRC transaction identifier field, the second key extension field and the second non-key extension field, and the payload length of the third message is smaller than the payload length of the first RRC message.

[0291] The second RRC transaction identification field can be used to identify the RRC transaction of the third message. In this way, the terminal device can learn the RRC transaction of the third message through the second RRC transaction identification field, so as to correctly parse the third message.

[0292] Among them, the second key extension field can be used to carry key configuration information of the third message.

[0293] It can be understood that the second associated extension field is the associated extension field of the third message. The relevant content of the second key extension field can be found in the "key extension field" in the above "Table 1", which will not be repeated here.

[0294] In this way, the terminal device must parse and identify the second key extension field when parsing the third message, otherwise it will refuse to process the entire RRC message and trigger the corresponding error handling process.

[0295] The second non-critical extension field may be used to carry non-critical configuration information of the third message.

[0296] It can be understood that the second non-associated extension field is a non-associated extension field of the third message. For relevant content of the second non-critical extension field, please refer to the “non-critical extension field” in the above “Table 1”.

[0297] In this way, if the terminal device encounters an unrecognizable non-critical extension field when parsing the third message, it can safely ignore it without causing the parsing of the third message to fail.

[0298] The second segment is in the second key extension field and / or the second non-key extension field.

[0299] In this way, if the second segment is in the second key extension field, all fields in the second segment must be recognized; if the second segment is in the first non-key extension field, all fields in the second segment are optional and can be ignored; if the second segment is in the second key extension field and the second non-key extension field, some fields in the second segment must be recognized, and the remaining fields are optional and can be ignored.

[0300] Optionally, the second non-critical extension field includes a second segment sequence number field and / or a second last segment field.

[0301] The second segment sequence number field may indicate the sequence number of the second segment in the segments obtained by dividing the payload of the first RRC message.

[0302] This is because, in the first RRC message payload being divided into a first segment and a second segment, the first segment and the second segment each have their own sequence number. The sequence number of the first segment is smaller than the sequence number of the second segment, for example, the sequence number of the first segment is 0 and the sequence number of the second segment is 1. This ensures that the network device can send the segments in ascending order of sequence numbers, and that the terminal device can integrate the received segments in ascending order of sequence numbers to obtain the entire payload of the first RRC message.

[0303] In this way, the terminal device can obtain the sequence number of the second segment through the second segment sequence number field. At the same time, because the second segment sequence number field is a non-critical extension field, if the terminal device encounters an unrecognizable second segment sequence number field when parsing the third message, it can safely ignore it without causing the third message to fail to parse. Among them, only terminal devices that support payload splitting processing of the first RRC message can recognize the second segment sequence number field.

[0304] The second last segment field may indicate that the second segment is the last segment among the segments obtained by dividing the payload of the first RRC message.

[0305] This is because, in the first RRC message payload segmented into the first segment and the second segment, the first segment is the first segment and the second segment is the last segment. The purpose of indicating whether a segment is the last segment is to inform the terminal device whether the transmission of all segments has been completed, so that the terminal device can integrate all segments to obtain the entire payload of the first RRC message after successfully receiving the last segment.

[0306] In this way, the terminal device can use the Second Last Segment field to know that the second segment is the last segment, so that the terminal device can begin to integrate the first segment and the second segment after receiving the second field. At the same time, because the Second Last Segment field is a non-critical extension field, if the terminal device encounters an unrecognizable Second Last Segment field when parsing the third message, it can safely ignore it without causing the parsing of the third message to fail. Among them, only terminal devices that support payload splitting processing of the first RRC message can recognize the Second Last Segment field.

[0307] In a possible example, the third message is repeatedly transmitted K2 times, where the value of K2 is an integer greater than or equal to 1.

[0308] It is understandable that the network device repeatedly transmits the third message K2 times, wherein when the value of K2 is equal to 1, it is equivalent to transmitting the third message only once.

[0309] In this way, by transmitting the same content of the third message K2 times, diversity gain or redundant transmission is achieved to improve the reception success rate of the third message.

[0310] Optionally, K2 is a value determined based on channel information corresponding to the second message.

[0311] This is because, since the second message can provide the network with the latest channel information (i.e., the channel information corresponding to the second message), the network device can decide the optimal transmission strategy for the third message based on the channel information corresponding to the second message, adjust the number of repeated transmissions, and determine the number of repeated transmissions of the third message to be K2, thereby improving the reception success rate of the third message by repeatedly transmitting the third message.

[0312] In combination with the above content, the entire process of the method based on load segmentation and step-by-step transmission and feedback is illustrated below.

[0313] like Figure 8 As shown, Figure 8FIG. 1 is a flow chart of another method based on load splitting and step-by-step transmission and feedback according to an embodiment of the present application, comprising the following steps: S810: Reporting the capability of supporting payload splitting processing of RRC messages.

[0314] In combination with the above content, it can be seen that this embodiment can report that the terminal device supports the load splitting processing of the RRC message in the "terminal device autonomous reporting" method or the "query first and then report" method, which will not be repeated here.

[0315] S820: Payload splitting decision for RRC message.

[0316] If a terminal device supports payload splitting of RRC messages, when the network device needs to send a first RRC message to the terminal device, the network device can decide whether to split the payload of the first RRC message based on factors such as channel information (such as historical channel information or channel information corresponding to Msg3) and / or the payload length of the first RRC message.

[0317] For example, if the channel information reflects that the current channel quality is poor, in order to avoid problems such as high block error rate, low resource efficiency and poor adaptability caused by transmitting the first RRC message, the network device can split the payload of the first RRC message.

[0318] For another example, if the payload length of the first RRC message is long, in order to avoid problems such as a high block error rate, low resource efficiency, and poor adaptability caused by transmitting the first RRC message, the network device can split the payload of the first RRC message.

[0319] When the payload of the first RRC message needs to be segmented, the network device segments the payload of the first RRC message into a first segment and a second segment.

[0320] S830: Transmission and feedback of the first segment.

[0321] The network device encapsulates the first segment into a first message and adds a first segment sequence number field and / or a first last segment field in the non-critical extension field of the first message to indicate the sequence number of the first segment and / or that the first segment is not the last segment.

[0322] The network device can then transmit the first message once or repeatedly transmit K1 times based on channel information (such as historical channel information or channel information corresponding to Msg3). After successfully receiving the first message, the terminal device provides feedback on the successful completion of the first message via a second message. The relevant content of the first and second messages can be found in the aforementioned content and will not be further described.

[0323] S840: Provide the network with the latest channel information based on the feedback of the first segment.

[0324] After the network device successfully receives the second message, the second message may provide the network device with the latest channel information, for example, the latest SINR, PHR or RSRP, etc., based on the DMRS in the second message.

[0325] S850: Adaptively adjust the transmission strategy of the second segment based on the channel corresponding to the feedback.

[0326] After the network device successfully receives the second message, since the second message can provide the network device with the latest channel information, the network device can adaptively adjust the transmission strategy of the second segment based on the latest channel information.

[0327] For example, if the latest channel information indicates good channel quality, the network device can select a more aggressive MCS, a smaller number of repetitions K1, or schedule fewer transmission resources. This more aggressive MCS allows for the selection of a higher-order modulation scheme and / or a higher coding rate, improving transmission reliability. The smaller number of repetitions or the scheduling of fewer transmission resources reduces resource overhead, improving resource efficiency.

[0328] Then, the network device encapsulates the second segment into a third message and adds a second segment sequence number field and / or a second last segment field in the non-critical extension field of the third message to indicate the sequence number of the second segment and / or that the second segment is the last segment.

[0329] Finally, the network device may transmit the third message once or K2 times repeatedly according to the channel information corresponding to the second message.

[0330] S860: Integration of the first and second segments and final feedback.

[0331] After the terminal device successfully receives the third message, the terminal device parses the third message to find that the second segment is the last segment. At this time, the terminal device can integrate the first segment and the second segment in ascending order of sequence number to obtain the entire payload of the first RRC message.

[0332] Finally, the terminal device provides feedback on the successful completion of the integration of the first segment and the second segment, thereby completing the entire RRC configuration.

[0333] It can be seen that compared with the direct transmission method of the first RRC message, this embodiment adopts a method based on load segmentation and step-by-step transmission and feedback for the first RRC message, which can achieve the purpose of improving transmission reliability, resource efficiency and adaptability.

[0334] For example, this embodiment takes different scenarios as examples to compare the direct transmission method of the first RRC message with the transmission and feedback method based on payload splitting and step-by-step, as shown in Table 2. In Table 2, the transmission and feedback method based on payload splitting and step-by-step is "Method 1", and the direct transmission method is "Method 2".

[0335] Table 2

[0336] The communication device of this embodiment is described below with an example.

[0337] The above mainly introduces the solution of the embodiment of the present application from the perspective of the method side. The following is an example of the functional unit of a communication device of this embodiment. It can be understood that in order to realize the above functions, the terminal device or network device includes a hardware structure and / or software module corresponding to the execution of each function. It should be easily appreciated by those skilled in the art that, in combination with the units and algorithm steps of each example described in the embodiment disclosed herein, this embodiment can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this embodiment.

[0338] The embodiments of the present application can divide the terminal device or network device into functional units according to the above method examples. For example, each functional unit can be divided according to each function, or two or more functions can be integrated into one processing unit. The above integrated unit can be implemented in the form of hardware or in the form of a software program module. It should be noted that the division of units in the embodiments of the present application is schematic and is only a logical functional division, and other division methods can be used in actual implementation.

[0339] In the case of an integrated unit, Figure 9 9 is a block diagram of the functional units of a communication device according to an embodiment of the present application, wherein the communication device 900 includes a receiving unit 901 and a sending unit 902 .

[0340] Optionally, the receiving unit 901 is a module unit for receiving relevant information, and there is no specific limitation on this.

[0341] Optionally, the sending unit 902 is a module unit for sending relevant information, and there is no specific limitation on this.

[0342] Optionally, the communication device 900 further includes a storage unit for storing computer program codes or instructions executed by the communication device 900. The storage unit may be a memory.

[0343] Optionally, the communication device 900 is a chip or a chip module.

[0344] Optionally, the communication device 900 further includes a processing unit.

[0345] It should be noted that the processing unit can be a processor or controller, for example, a baseband processor, a baseband chip, a central processing unit (CPU), a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It can implement or execute the various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of this embodiment. The processing unit can also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, etc.

[0346] Optionally, the receiving unit 901 and the sending unit 902 are integrated into a communication unit. For example, the communication unit can be an interface circuit, a communication interface, a transceiver, or a transceiver circuit.

[0347] Optionally, the communication device 900 is used to execute any step performed by a terminal device, a chip, or a chip module in the above method embodiment.

[0348] In specific implementation, the receiving unit 901 and the sending unit 902 are used to execute the steps in the above method embodiment, and when executing other actions, other units can be selectively called to complete the corresponding operations.

[0349] The receiving unit 901 is configured to receive a first message, where the first message is an RRC message including a first segment in a first RRC message; A sending unit 902 is configured to send a second message, where the second message is an RRC message used to confirm that the first message is successfully completed; The payload of the first RRC message is divided into a first segment and a second segment. The first segment is part of the fields in the payload of the first RRC message, and the second segment is the remaining fields in the payload of the first RRC message except the first segment.

[0350] It can be seen that in order to avoid problems such as a high block error rate, low resource efficiency, and poor adaptability caused by directly transmitting the first RRC message, the present application divides the payload of the first RRC message into a first segment and a second segment to achieve the following objectives: Compared to directly transmitting the first RRC message all at once, since the payload of the first RRC message is divided into a first segment and a second segment, the present application can transmit the first segment and the second segment sequentially, thereby dividing the transmission of the first RRC message into two transmissions to improve transmission flexibility. In this way, after encapsulating the first segment into an RRC message (i.e., the first message), the network can first transmit the first message to transmit some fields of the first RRC message first, and then provide feedback on the successful completion of the first message through the second message, thereby completing an independent "transmission-feedback" closed loop.

[0351] Because the payload length of the first message is smaller than that of the first RRC message, the transmission of the first message is less prone to bit errors than the transmission of the first RRC message, and the transmission resources of the first message are less than the transmission resources of the first RRC message. In this way, the network can prioritize the transmission of some fields of the first RRC message with a lower block error rate and transmission resources, ensuring the transmission reliability and resource efficiency of these fields. Especially in scenarios such as unstable channel quality and resource constraints, the first message can prioritize the successful configuration of some information to the terminal device so that some RRC-related processing can be carried out in a timely manner.

[0352] Compared to the situation where the network may not be able to decide the optimal transmission strategy for the first RRC message based on the latest channel information before directly transmitting the first RRC message, since the present application requires feedback on the successful completion of the first message through the second message, the present application can provide the network with the latest channel information through the second message. For example, the network obtains the latest channel information based on the DMRS in the second message. In this way, the network can decide the optimal transmission strategy for the second segment based on the latest channel information, dynamically adjust the transmission strategy, and ensure transmission reliability, resource efficiency, and link adaptability when subsequently transmitting the second segment.

[0353] It should be noted that the specific implementation of each operation can adopt the corresponding description of the method embodiment shown above, and the communication device 900 can be used to execute the above method embodiment of this embodiment, which will not be described in detail.

[0354] In the case of an integrated unit, Figure 10 FIG. 1 is a block diagram of functional units of another communication device according to an embodiment of the present application, wherein the communication device 1000 includes a sending unit 1001 and a receiving unit 1002 .

[0355] Optionally, the sending unit 1001 is a module unit for sending relevant information, which is not specifically limited. The sending unit 1001 can be a communication interface, a transceiver, a transceiver circuit, etc.

[0356] Optionally, the receiving unit 1002 is a module unit for receiving relevant information, which is not specifically limited. The receiving unit 1002 can be a communication interface, a transceiver, a transceiver circuit, etc.

[0357] Optionally, the communication device 1000 further includes a storage unit for storing computer program codes or instructions executed by the communication device 1000. The storage unit may be a memory.

[0358] Optionally, the communication device 1000 is a chip or a chip module.

[0359] Optionally, the communication device 1000 further includes a processing unit.

[0360] It should be noted that the processing unit can be a processor or controller, for example, a baseband processor, a baseband chip, a central processing unit (CPU), a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It can implement or execute the various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of this embodiment. The processing unit can also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, etc.

[0361] Optionally, the sending unit 1001 and the receiving unit 1002 are integrated into a communication unit. For example, the communication unit can be an interface circuit, a communication interface, a transceiver, or a transceiver circuit.

[0362] Optionally, the communication device 1000 is used to execute any step executed by a network device, a chip, or a chip module in the above method embodiment.

[0363] In specific implementation, the sending unit 1001 and the receiving unit 1002 are used to execute the steps in the above method embodiment, and when executing other actions, other units can be selectively called to complete the corresponding operations.

[0364] The sending unit 1001 is configured to send a first message, where the first message is an RRC message including a first segment in a first RRC message; The receiving unit 1002 is configured to receive a second message, where the second message is an RRC message used to confirm successful completion of the first message; The payload of the first RRC message is divided into a first segment and a second segment. The first segment is part of the fields in the payload of the first RRC message, and the second segment is the remaining fields in the payload of the first RRC message except the first segment.

[0365] It can be seen that in order to avoid problems such as a high block error rate, low resource efficiency, and poor adaptability caused by directly transmitting the first RRC message, the present application divides the payload of the first RRC message into a first segment and a second segment to achieve the following objectives: Compared to directly transmitting the first RRC message all at once, since the payload of the first RRC message is divided into a first segment and a second segment, the present application can transmit the first segment and the second segment sequentially, thereby dividing the transmission of the first RRC message into two transmissions to improve transmission flexibility. In this way, after encapsulating the first segment into an RRC message (i.e., the first message), the network can first transmit the first message to transmit some fields of the first RRC message first, and then provide feedback on the successful completion of the first message through the second message, thereby completing an independent "transmission-feedback" closed loop.

[0366] Because the payload length of the first message is smaller than that of the first RRC message, the transmission of the first message is less prone to bit errors than the transmission of the first RRC message, and the transmission resources of the first message are less than the transmission resources of the first RRC message. In this way, the network can prioritize the transmission of some fields of the first RRC message with a lower block error rate and transmission resources, ensuring the transmission reliability and resource efficiency of these fields. Especially in scenarios such as unstable channel quality and resource constraints, the first message can prioritize the successful configuration of some information to the terminal device so that some RRC-related processing can be carried out in a timely manner.

[0367] Compared to the situation where the network may not be able to decide the optimal transmission strategy for the first RRC message based on the latest channel information before directly transmitting the first RRC message, since the present application requires feedback on the successful completion of the first message through the second message, the present application can provide the network with the latest channel information through the second message. For example, the network obtains the latest channel information based on the DMRS in the second message. In this way, the network can decide the optimal transmission strategy for the second segment based on the latest channel information, dynamically adjust the transmission strategy, and ensure transmission reliability, resource efficiency, and link adaptability when subsequently transmitting the second segment.

[0368] It should be noted that the specific implementation of each operation can adopt the corresponding description of the method embodiment shown above, and the communication device 1000 can be used to execute the above method embodiment of this embodiment, which will not be described in detail.

[0369] The following is an example of the structure of a terminal device in this embodiment.

[0370] See also Figure 11 , Figure 11 FIG1 is a schematic diagram of the structure of a terminal device according to an embodiment of the present application, wherein the terminal device 1100 may include a processor 1110 , a memory 1120 , and a communication bus for connecting the processor 1110 and the memory 1120 .

[0371] Optionally, the memory 1120 includes but is not limited to random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM) or portable read-only memory (CD-ROM), and the memory 1120 is used to store the program code executed by the terminal device 1100 and the transmitted data.

[0372] Optionally, the terminal device 1100 further includes a communication interface for receiving and sending data.

[0373] Optionally, the terminal device 1100 may be the terminal device mentioned above.

[0374] Optionally, the processor 1110 may be one or more CPUs. When the processor 1110 is a CPU, the CPU may be a single-core CPU or a multi-core CPU.

[0375] Optionally, the processor 1110 may be a baseband chip, a chip, a CPU, a general-purpose processor, a DSP, an ASIC, an FPGA or other programmable logic device, a transistor logic device, a hardware component or any combination thereof.

[0376] In one possible example, the processor 1110 in the terminal device 1100 is configured to execute a computer program or instruction 1121 stored in the memory 1120 to perform the following operations: receiving a first message, where the first message is an RRC message including a first segment in the first RRC message; Sending a second message, where the second message is an RRC message used to confirm successful completion of the first message; The payload of the first RRC message is divided into a first segment and a second segment. The first segment is part of the fields in the payload of the first RRC message, and the second segment is the remaining fields in the payload of the first RRC message except the first segment.

[0377] It can be seen that in order to avoid problems such as a high block error rate, low resource efficiency, and poor adaptability caused by directly transmitting the first RRC message, the present application divides the payload of the first RRC message into a first segment and a second segment to achieve the following objectives: Compared to directly transmitting the first RRC message all at once, since the payload of the first RRC message is divided into a first segment and a second segment, the present application can transmit the first segment and the second segment sequentially, thereby dividing the transmission of the first RRC message into two transmissions to improve transmission flexibility. In this way, after encapsulating the first segment into an RRC message (i.e., the first message), the network can first transmit the first message to transmit some fields of the first RRC message first, and then provide feedback on the successful completion of the first message through the second message, thereby completing an independent "transmission-feedback" closed loop.

[0378] Because the payload length of the first message is smaller than that of the first RRC message, the transmission of the first message is less prone to bit errors than the transmission of the first RRC message, and the transmission resources of the first message are less than the transmission resources of the first RRC message. In this way, the network can prioritize the transmission of some fields of the first RRC message with a lower block error rate and transmission resources, ensuring the transmission reliability and resource efficiency of these fields. Especially in scenarios such as unstable channel quality and resource constraints, the first message can prioritize the successful configuration of some information to the terminal device so that some RRC-related processing can be carried out in a timely manner.

[0379] Compared to the situation where the network may not be able to decide the optimal transmission strategy for the first RRC message based on the latest channel information before directly transmitting the first RRC message, since the present application requires feedback on the successful completion of the first message through the second message, the present application can provide the network with the latest channel information through the second message. For example, the network obtains the latest channel information based on the DMRS in the second message. In this way, the network can decide the optimal transmission strategy for the second segment based on the latest channel information, dynamically adjust the transmission strategy, and ensure transmission reliability, resource efficiency, and link adaptability when subsequently transmitting the second segment.

[0380] It should be noted that the specific implementation of each operation can adopt the corresponding description of the method embodiment shown above, and the terminal device 1100 can be used to execute the above method embodiment of this embodiment, which will not be repeated here.

[0381] The following is an example of the structure of a network device in this embodiment.

[0382] See also Figure 12 , Figure 12 12 is a schematic diagram of the structure of a network device according to an embodiment of the present application, wherein the network device 1200 may include a processor 1210 , a memory 1220 , and a communication bus for connecting the processor 1210 and the memory 1220 .

[0383] Optionally, the memory 1220 includes but is not limited to RAM, ROM, EPROM or CD-ROM, and the memory 1220 is used to store program codes executed by the network device 1200 and the transmitted data.

[0384] Optionally, the network device 1200 further includes a communication interface for receiving and sending data.

[0385] Optionally, the network device 1200 may be the aforementioned network device.

[0386] Optionally, the processor 1210 may be one or more CPUs. When the processor 1210 is a CPU, the CPU may be a single-core CPU or a multi-core CPU.

[0387] Optionally, the processor 1210 may be a baseband chip, a chip, a CPU, a general-purpose processor, a DSP, an ASIC, an FPGA or other programmable logic device, a transistor logic device, a hardware component or any combination thereof.

[0388] In one possible example, the processor 1210 in the network device 1200 is configured to execute a computer program or instruction 1221 stored in the memory 1220 to perform the following operations: Sending a first message, where the first message is an RRC message including the first segment in the first RRC message; receiving a second message, where the second message is an RRC message used to confirm successful completion of the first message; The payload of the first RRC message is divided into a first segment and a second segment. The first segment is part of the fields in the payload of the first RRC message, and the second segment is the remaining fields in the payload of the first RRC message except the first segment.

[0389] It can be seen that in order to avoid problems such as a high block error rate, low resource efficiency, and poor adaptability caused by directly transmitting the first RRC message, the present application divides the payload of the first RRC message into a first segment and a second segment to achieve the following objectives: Compared to directly transmitting the first RRC message all at once, since the payload of the first RRC message is divided into a first segment and a second segment, the present application can transmit the first segment and the second segment sequentially, thereby dividing the transmission of the first RRC message into two transmissions to improve transmission flexibility. In this way, after encapsulating the first segment into an RRC message (i.e., the first message), the network can first transmit the first message to transmit some fields of the first RRC message first, and then provide feedback on the successful completion of the first message through the second message, thereby completing an independent "transmission-feedback" closed loop.

[0390] Because the payload length of the first message is smaller than that of the first RRC message, the transmission of the first message is less prone to bit errors than the transmission of the first RRC message, and the transmission resources of the first message are less than the transmission resources of the first RRC message. In this way, the network can prioritize the transmission of some fields of the first RRC message with a lower block error rate and transmission resources, ensuring the transmission reliability and resource efficiency of these fields. Especially in scenarios such as unstable channel quality and resource constraints, the first message can prioritize the successful configuration of some information to the terminal device so that some RRC-related processing can be carried out in a timely manner.

[0391] Compared to the situation where the network may not be able to decide the optimal transmission strategy for the first RRC message based on the latest channel information before directly transmitting the first RRC message, since the present application requires feedback on the successful completion of the first message through the second message, the present application can provide the network with the latest channel information through the second message. For example, the network obtains the latest channel information based on the DMRS in the second message. In this way, the network can decide the optimal transmission strategy for the second segment based on the latest channel information, dynamically adjust the transmission strategy, and ensure transmission reliability, resource efficiency, and link adaptability when subsequently transmitting the second segment.

[0392] It should be noted that the specific implementation of each operation can adopt the corresponding description of the method embodiment shown above, and the network device 1200 can be used to execute the above method embodiment of this embodiment, which will not be described in detail.

[0393] Other relevant contents of this embodiment are described below with examples.

[0394] Optionally, the above method embodiments may be applied to or within a terminal device. In other words, the execution subject of the above method embodiments may be a terminal device, a chip, a chip module, or a module, etc., without any specific limitation.

[0395] Optionally, the above method embodiments may be applied to or within a network device. In other words, the execution subject of the above method embodiments may be a network device, a chip, a chip module, or a module, etc., without any specific limitation.

[0396] An embodiment of the present application also provides a communication system, including the above-mentioned terminal device and the above-mentioned network device.

[0397] An embodiment of the present application also provides a chip, including a processor, a memory, and a computer program or instructions stored in the memory, wherein the processor executes the computer program or instructions to implement the steps described in the above method embodiment.

[0398] An embodiment of the present application also provides a chip module, including a transceiver component and a chip, wherein the chip includes a processor, a memory, and a computer program or instructions stored on the memory, wherein the processor executes the computer program or instructions to implement the steps described in the above method embodiment.

[0399] An embodiment of the present application further provides a computer-readable storage medium storing a computer program or instructions, which implements the steps described in the above method embodiment when executed.

[0400] An embodiment of the present application further provides a computer program product, including a computer program or instructions, which implement the steps described in the above method embodiment when executed.

[0401] It should be noted that, for the above-mentioned various embodiments, for the sake of simplicity of description, they are all expressed as a series of action combinations. Those skilled in the art should know that this application is not limited by the order of the actions described, because some steps in the embodiments of the present application can be performed in other orders or simultaneously. In addition, those skilled in the art should also know that the embodiments described in the specification are all preferred embodiments, and the actions, steps, modules or units involved are not necessarily required by the embodiments of the present application.

[0402] In the above embodiments, the embodiments of the present application have different focuses on the description of each embodiment. For parts that are not described in detail in a certain embodiment, please refer to the relevant description of other embodiments.

[0403] The steps of the method or algorithm described in the embodiments of the present application can be implemented in hardware or by a processor executing software instructions. The software instructions can be composed of corresponding software modules, which can be stored in RAM, flash memory, ROM, EPROM, electrically erasable programmable read-only memory (EEPROM), registers, hard disk, removable hard disk, CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor so that the processor can read information from the storage medium and write information to the storage medium. Of course, the storage medium can also be an integral part of the processor. The processor and storage medium can be located in an ASIC. In addition, the ASIC can be located in a terminal device or a management device. Of course, the processor and storage medium can also exist as discrete components in the terminal device or the management device.

[0404] Those skilled in the art will appreciate that in one or more of the above examples, the functions described in the embodiments of the present application can be implemented in whole or in part via software, hardware, firmware, or any combination thereof. When implemented using software, they can be implemented in whole or in part in the form of a computer program product. This computer program product comprises one or more computer instructions. When these computer program instructions are loaded and executed on a computer, they fully or partially produce the processes or functions described in the embodiments of the present application. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible by a computer or a data storage device such as a server or data center that integrates one or more available media. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a digital video disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).

[0405] The modules or units included in the various devices and products described in the above embodiments may be software modules or units, hardware modules or units, or may be partially software modules or units and partially hardware modules or units. For example, for various devices and products applied to or integrated into a chip, the modules or units included therein may all be implemented in the form of hardware such as circuits, or at least some of the modules or units may be implemented in the form of software programs, which run on a processor integrated inside the chip, and the remaining (if any) modules or units may be implemented in the form of hardware such as circuits; for various devices and products applied to or integrated into a chip module, the modules or units included therein may all be implemented in the form of hardware such as circuits, and different modules or units may be located in the same component (such as a chip, circuit module, etc.) or different components of the chip module, or at least some of the modules or units may be It is implemented in the form of a software program, which runs on the processor integrated inside the chip module, and the remaining (if any) modules or units can be implemented in the form of hardware such as circuits; for various devices and products applied to or integrated in the terminal equipment, the various modules or units contained therein can be implemented in the form of hardware such as circuits, and different modules or units can be located in the same component (for example, chip, circuit module, etc.) or different components in the terminal equipment, or at least some modules or units can be implemented in the form of a software program, which runs on the processor integrated inside the terminal equipment, and the remaining (if any) modules or units can be implemented in the form of hardware such as circuits.

[0406] The specific implementation methods described above further illustrate the purpose, technical solutions and beneficial effects of the embodiments of the present application. It should be understood that the above description is only a specific implementation method of the embodiments of the present application and is not intended to limit the scope of protection of the embodiments of the present application. Any modifications, equivalent replacements, improvements, etc. made on the basis of the technical solutions of the embodiments of the present application should be included in the scope of protection of the embodiments of the present application.

Claims

1. A communication method, characterized in that: include: Receiving a first message, where the first message is an RRC message including a first segment in a first radio resource control (RRC) message; Sending a second message, where the second message is an RRC message used to confirm successful completion of the first message; The payload of the first RRC message is divided into the first segment and the second segment, the first segment is part of the fields in the payload of the first RRC message, and the second segment is the remaining fields in the payload of the first RRC message except the first segment.

2. The method according to claim 1, characterized in that The length of the first segment is smaller than the length of the second segment.

3. The method according to claim 1, characterized in that The first message includes a first RRC transaction identifier field, a first key extension field, and a first non-key extension field; The first segment is in the first key extension field and / or the first non-key extension field; The first RRC transaction identifier field is used to identify the RRC transaction of the first message; The first key extension field is used to carry key configuration information of the first message; The first non-critical extension field is used to carry non-critical configuration information of the first message.

4. The method according to claim 3, characterized in that The first non-critical extension field includes a first segment sequence number field and / or a first last segment field; The first segment sequence number field indicates a sequence number of the first segment in the segments obtained by dividing the payload of the first RRC message; The first last segment field indicates that the first segment is not the last segment among the segments obtained by dividing the payload of the first RRC message.

5. The method according to claim 1, wherein The first RRC message includes an RRC reconfiguration message; The first segment includes a radio bearer configuration field in the RRC reconfiguration message; The second segment includes a secondary cell group field and a measurement configuration field in the RRC reconfiguration message.

6. The method according to claim 1, wherein The first RRC message is an RRC message transmitted by the network after the terminal device successfully accesses the cell; or, The first RRC message is an RRC message transmitted by the network after the terminal device successfully enters the RRC connected state; or, The first RRC message is an RRC message transmitted by the network after the terminal device completes random access.

7. The method according to claim 1, characterized in that The first message is repeatedly transmitted K1 times, where the value of K1 is an integer greater than or equal to 1.

8. The method according to claim 7, characterized in that K1 is the value specified in the protocol or set by default; or K1 is a value determined based on the number of repeated transmissions of message 4 in the random access process; or, K1 is a value determined based on the channel information corresponding to message 3 in the random access process.

9. The method according to claim 1, characterized in that Also includes: Send device capability information, where the device capability information indicates that the terminal device supports payload splitting processing of the first RRC message.

10. The method according to claim 1, characterized in that Also includes: receiving a third message, where the third message is an RRC message including the second segment; A fourth message is sent, where the fourth message is an RRC message used to confirm that the integration of the first segment and the second segment is successfully completed.

11. The method according to claim 10, characterized in that The third message includes a second RRC transaction identifier field, a second key extension field and a second non-key extension field; The second segment is in the second critical extension field and / or the second non-critical extension field; The second RRC transaction identifier field is used to identify the RRC transaction corresponding to the third message; The second key extension field is used to carry key configuration information of the third message; The second non-critical extension field is used to carry non-critical configuration information of the third message.

12. The method according to claim 11, characterized in that The second non-critical extension field includes a second segment sequence number field and / or a second last segment field; The second segment sequence number field indicates a sequence number of the second segment in the segments obtained by dividing the payload of the first RRC message; The second last segment field indicates that the second segment is the last segment among the segments obtained by dividing the payload of the first RRC message.

13. The method according to claim 10, characterized in that The third message is repeatedly transmitted K2 times, where the value of K2 is an integer greater than or equal to 1.

14. The method according to claim 13, wherein: K2 is a value determined based on the channel information corresponding to the second message.

15. A communication method, characterized in that: include: Sending a first message, where the first message is an RRC message including a first segment in a first radio resource control RRC message; receiving a second message, where the second message is an RRC message used to determine successful completion of the first message; The payload of the first RRC message is divided into the first segment and the second segment, the first segment is a part of the fields in the payload of the first RRC message, and the second segment is the remaining fields in the payload of the first RRC message except the first segment fields.

16. The method according to claim 15, characterized in that The length of the first segment is smaller than the length of the second segment.

17. The method according to claim 15, characterized in that The first message includes a first RRC transaction identifier field, a first key extension field, and a first non-key extension field; The first segment is in the first key extension field and / or the first non-key extension field; The first RRC transaction identifier field is used to identify the RRC transaction of the first message; The first key extension field is used to carry key configuration information of the first message; The first non-critical extension field is used to carry non-critical configuration information of the first message.

18. The method according to claim 17, characterized in that The first non-critical extension field includes a first segment sequence number field and / or a first last segment field; The first segment sequence number field indicates a sequence number of the first segment in the segments obtained by dividing the payload of the first RRC message; The first last segment field indicates that the first segment is not the last segment among the segments obtained by dividing the payload of the first RRC message.

19. The method according to claim 15, characterized in that The first RRC message includes an RRC reconfiguration message; The first segment includes a radio bearer configuration field in the RRC reconfiguration message; The second segment includes a secondary cell group field and a measurement configuration field in the RRC reconfiguration message.

20. The method according to claim 15, wherein Also includes: Receive device capability information, where the device capability information indicates that the terminal device supports payload splitting processing of the first RRC message.

21. The method according to claim 15, characterized in that Also includes: Sending a third message, where the third message is an RRC message including the second segment; A fourth message is received, where the fourth message is an RRC message used to determine that integration of the first segment and the second segment is successfully completed.

22. The method according to claim 21, characterized in that The third message includes a second RRC transaction identifier field, a second key extension field and a second non-key extension field; The second segment is in the second critical extension field and / or the second non-critical extension field; The second RRC transaction identifier field is used to identify the RRC transaction corresponding to the third message; The second non-critical extension field is used to carry non-critical configuration information of the third message.

23. The method according to claim 22, characterized in that The second non-critical extension field includes a second segment sequence number field and / or a second last segment field; The second segment sequence number field indicates a sequence number of the second segment in the segments obtained by dividing the payload of the first RRC message; The second last segment field indicates that the second segment is the last segment among the segments obtained by dividing the payload of the first RRC message.

24. A communication device, characterized in that: include: A receiving unit, configured to receive a first message, where the first message is an RRC message including a first segment in a first radio resource control RRC message; a sending unit, configured to send a second message, where the second message is an RRC message used to determine that the first message is successfully completed; The payload of the first RRC message is divided into the first segment and the second segment, the first segment is part of the fields in the payload of the first RRC message, and the second segment is the remaining fields in the payload of the first RRC message except the first segment.

25. A communication device, characterized in that: include: A sending unit, configured to send a first message, where the first message is an RRC message including a first segment in a first radio resource control RRC message; a receiving unit, configured to receive a second message, where the second message is an RRC message used to determine that the first message is successfully completed; The payload of the first RRC message is divided into the first segment and the second segment, the first segment is part of the fields in the payload of the first RRC message, and the second segment is the remaining fields in the payload of the first RRC message except the first segment.

26. A terminal device comprising a processor, a memory, and a computer program or instruction stored in the memory, characterized in that: The processor executes the computer program or instructions to implement the method according to any one of claims 1 to 14.

27. A network device comprising a processor, a memory, and a computer program or instruction stored in the memory, wherein: The processor executes the computer program or instructions to implement the method of any one of claims 15-23.

28. A chip comprising a processor, characterized in that: The processor is configured to implement the method according to any one of claims 1 to 14 or 15 to 23.

29. A computer-readable storage medium, characterized in that The device stores a computer program or instruction, which implements the method according to any one of claims 1 to 14 or 15 to 23 when executed.

Images