Communication methods and devices, terminal equipment and network equipment

Abstract

This application discloses communication methods and apparatus, terminal equipment, and network equipment, relating to the field of communication technology. To avoid problems such as high block error rate, low resource efficiency, and poor adaptability caused by directly transmitting the first RRC message, this application proposes a method based on payload segmentation and step-by-step transmission and feedback. In this method, the payload of the first RRC message is segmented into a first segment and a second segment, and the first and second segments are transmitted separately, thus dividing the single transmission of the first RRC message into two transmissions. Then, the network first transmits the first message and then provides feedback on the first message through the second message, thereby completing an independent "transmission-feedback" closed loop. Finally, based on the second message, this application provides the network with the latest channel information for deciding the optimal transmission strategy for the second segment, realizing dynamic adjustment of the transmission strategy and improving the reliability, resource efficiency, and link adaptability of the second segment transmission.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of communication, and in particular to a communication method and device, a terminal device and a network device. BACKGROUND

[0002] With the evolution of communication technology, the complexity and flexibility of network configuration are constantly improving. As key control signaling, Radio Resource Control (RRC) messages are responsible for carrying important information such as network resource establishment, modification and release of resources.

[0003] However, since the payload length / size of the RRC message can be large, in scenarios such as Non-Terrestrial Networks (NTN), mobile edge computing or cell edge, where signal coverage is poor, latency is high and channel quality is unstable, direct transmission of the RRC message by the network can cause high block error rate, low resource efficiency and poor adaptation. SUMMARY

[0004] The present application provides a communication method and device, a terminal device and a network device, in order to achieve a method based on payload segmentation and step-by-step transmission and feedback, to improve transmission reliability, resource efficiency and adaptation.

[0005] In a first aspect, the present application provides a communication method, comprising:

[0006] receiving a first message, the first message being an RRC message containing a first segment of a first RRC message;

[0007] sending a second message, the second message being an RRC message for determining successful completion of the first message;

[0008] wherein the payload of the first RRC message is segmented into a first segment and a second segment, the first segment being part of the fields in the payload of the first RRC message, and the second segment being the remaining fields in the payload of the first RRC message other than the first segment.

[0009] It can be seen that, in order to avoid problems such as high block error rate, low resource efficiency and poor adaptation caused by direct transmission of the first RRC message, the present application segments the payload of the first RRC message into a first segment and a second segment, in order to achieve the following purposes:

[0010] Compared with directly transmitting the first RRC message once, since the payload of the first RRC message is split into the first segment and the second segment, the first segment and the second segment can be transmitted in sequence, so as to implement splitting the one-time transmission of the first RRC message into two-time transmissions to improve transmission flexibility. In this way, after the first segment is encapsulated into one RRC message (i.e., the first message), the network can first transmit the first message to implement transmitting part of the fields of the first RRC message first, and then feed back successful completion of the first message through the second message, so as to complete one independent "transmission-feedback" closed loop.

[0011] 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 likely to have an error code than the transmission of the first RRC message, and the transmission resource of the first message is less than the transmission resource of the first RRC message. In this way, the network can first transmit part of the fields of the first RRC message with lower block error rate and transmission resource to ensure the transmission reliability and resource efficiency of this part of fields. Especially in scenarios such as unstable channel quality and resource shortage, part of the information can be successfully configured to the terminal device through the first message to ensure timely development of part of the RRC-related processing.

[0012] Compared with the fact that the network cannot decide the optimal transmission strategy of the first RRC message according to the latest channel information before directly transmitting the first RRC message, since the application needs to feed back the successful completion of the first message through the second message, the application can provide the network with the latest channel information (i.e., the channel information corresponding to the second message) 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 of the second segment based on the latest channel information, implement dynamic adjustment of the transmission strategy, and ensure the transmission reliability, resource efficiency, and link adaptation in subsequent transmission of the second segment.

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

[0014] As can be seen, since the length of the first segment is smaller than the length of the second segment, the transmission reliability and resource efficiency of the second segment can be lower than those of the first segment. In this way, the embodiment can first transmit the first segment with lower block error rate and transmission resource, and then optimize the transmission strategy of the second segment through the feedback of the first segment, so that the transmission success rate of the second segment is improved, thereby improving the transmission reliability and resource efficiency of the second segment.

[0015] In one possible example of the first aspect, the first message includes a first RRC transaction identification field, a first key extension field, and a first non-key extension field;

[0016] The first segment is in the first critical extension field and / or the first non-critical extension field;

[0017] The first RRC transaction identification field is used to identify the RRC transaction of the first message;

[0018] The first critical extension field is used to carry critical configuration information of the first message;

[0019] The first non-critical extension field is used to carry non-critical configuration information of the first message.

[0020] It can be seen that, when parsing the first message, the terminal device can learn the RRC transaction of the first message through the first RRC transaction identification field, and the terminal device must identify the first critical extension field. Meanwhile, when encountering the first non-critical extension field that cannot be identified, it can be safely ignored without causing the first message parsing to fail.

[0021] In this way, if the first segment is in the first critical extension field, all fields in the first segment must be identified; if the first segment is in the first non-critical extension field, all fields in the first segment are optional and can be ignored; if the first segment is in the first critical extension field and the first non-critical extension field, part of the fields in the first segment must be identified, and the remaining fields are optional and can be ignored.

[0022] In one possible example of the first aspect, the first non-critical extension field contains a first segment serial number field and / or a first last segment field;

[0023] The first segment serial number field indicates the serial number of the first segment in the segments obtained by segmenting the payload of the first RRC message;

[0024] The first last segment field indicates that the first segment is not the last segment in the segments obtained by segmenting the payload of the first RRC message.

[0025] It can be seen that, when parsing the first message, the terminal device can learn the serial number of the first segment through the first segment serial number field. Meanwhile, since the first segment serial number field and / or the first last segment field are in the non-critical extension field, if the terminal device cannot identify the first segment serial number field and / or the first last segment field, it can be safely ignored without causing the first message parsing to fail.

[0026] In one possible example of the first aspect, the first RRC message includes an RRC reconfiguration message;

[0027] The first segment includes a radio bearer configuration field in the RRC reconfiguration message;

[0028] The second segment includes a secondary cell group field and a measurement configuration field in the RRC reconfiguration message.

[0029] It can be seen that, since the payload length of the RRC reconfiguration message is large, the payload of the RRC reconfiguration message can be divided into the first segment and the second segment in the embodiment. The first segment includes the radio bearer configuration field, and the second segment includes the secondary cell configuration field and the measurement configuration field.

[0030] In this way, since the network preferentially transmits the first segment to the terminal device, the terminal device can preferentially receive the radio bearer configuration field, so as to preferentially perform the related processing of the radio bearer according to the radio bearer configuration field. Subsequently, after the transmission of the second segment is completed, the related processing of the secondary cell configuration and the measurement configuration is performed.

[0031] 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,

[0032] The first RRC message is an RRC message transmitted by the network after the terminal device successfully enters the RRC connected state; or,

[0033] The first RRC message is an RRC message transmitted by the network after the terminal device performs the random access.

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

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

[0036] It can be seen that, by repeatedly 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.

[0037] In a possible example of the first aspect, K1 is a value specified by a protocol or a default setting; or,

[0038] K1 is a value determined based on the number of repeated transmissions of message 4 in the random access procedure; or,

[0039] K1 is a value determined based on channel information corresponding to message 3 in the random access procedure.

[0040] It can be seen that the network can determine the number of repeated transmissions of the first message as K1 according to the protocol or default settings, or determine the number of repeated transmissions of the first message as K1 based on the number of repeated transmissions of Msg4, or determine the number of repeated transmissions of the first message as K1 based on the channel information corresponding to Msg3, so as to improve the reception success rate of the first message by repeated transmission of the first message.

[0041] In one possible example of the first aspect, the method further includes:

[0042] Sending device capability information, the device capability information indicating that the terminal device supports the payload segmentation processing of the first RRC message.

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

[0044] In one possible example of the first aspect, the method further includes:

[0045] Receiving a third message, the third message being an RRC message containing the second segment;

[0046] Sending a fourth message, the fourth message being an RRC message used to determine that the integration of the first segment and the second segment is successfully completed.

[0047] It can be seen that, in order to avoid the problems of high block error rate, low resource efficiency, and poor flexibility caused by directly transmitting the first RRC message, the payload of the first RRC message is segmented into the first segment and the second segment in the embodiment, so as to achieve the following purposes:

[0048] Compared with directly transmitting the first RRC message once, since the payload of the first RRC message is segmented into the first segment and the second segment, the first segment and the second segment can be transmitted in sequence in the embodiment, so as to improve the transmission flexibility by dividing the transmission of the first RRC message into two transmissions. In this way, the network can first transmit the first segment, and then transmit the second segment through the third message to implement the transmission of the remaining fields of the first RRC message after the transmission and feedback of the first segment are completed, and finally feed back the successful completion of the integration of the first segment and the second segment through the fourth message, so as to complete the closed loop of two independent “transmission-feedback”.

[0049] Compared with that the network cannot decide the optimal transmission strategy of the first RRC message according to the latest channel information before directly transmitting the first RRC message, since the embodiment can provide the network with the latest channel information through the second message, the network can decide the optimal transmission strategy of the third message according to the latest channel information, realize dynamic adjustment of the transmission strategy, and guarantee the transmission reliability, resource efficiency and link adaptation when the second segment is transmitted.

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

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

[0052] The second RRC transaction identification field is used to identify the RRC transaction corresponding to the third message.

[0053] The second key extension field is used to carry the key configuration information of the third message.

[0054] The second non-key extension field is used to carry the non-key configuration information of the third message.

[0055] As can be seen, when the third message is parsed, the terminal device can learn the RRC transaction of the third message through the second RRC transaction identification field, and the terminal device must identify the second key extension field. Meanwhile, when the second non-key extension field cannot be identified, it can be safely ignored, without causing the third message to fail to be parsed.

[0056] In this way, if the second segment is in the second key extension field, all the fields in the second segment must be identified; if the second segment is in the second non-key extension field, all the 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, part of the fields in the second segment must be identified, and the remaining fields are optional and can be ignored.

[0057] In a possible example of the first aspect, the second non-key extension field includes a second segment serial number field and / or a second last segment field.

[0058] The second segment serial number field indicates the serial number of the second segment in the segments segmented from the payload of the first RRC message.

[0059] The second last segment field indicates that the second segment is the last segment in the segments segmented from the payload of the first RRC message.

[0060] It can be seen that, when the third message is parsed, the terminal device can learn the sequence number of the second segment through the second segment sequence number field. Meanwhile, since 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 identify the second segment sequence number field and / or the second last segment field, it can safely ignore them without causing the third message parsing to fail.

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

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

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

[0064] It can be seen that, since the second message can provide the network with the most up-to-date channel information, the network device can determine the optimal transmission strategy of the third message based on the channel information corresponding to the second message, and determine the number of repeated transmissions of the third message as K2, so as to improve the reception success rate of the third message by repeatedly transmitting the third message.

[0065] The second aspect is a communication method of the present application, comprising:

[0066] sending a first message, the first message being an RRC message containing a first segment in a first RRC message;

[0067] receiving a second message, the second message being an RRC message for determining that the first message is successfully completed;

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

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

[0070] In a possible example of the second aspect, the first message comprises a first RRC transaction identification field, a first critical extension field and a first non-critical extension field;

[0071] the first segment is in the first critical extension field and / or the first non-critical extension field;

[0072] the first RRC transaction identification field is used to identify the RRC transaction of the first message;

[0073] The first key extended field is used to carry key configuration information for the first message;

[0074] The first non-critical extended field is used to carry non-critical configuration information for the first message.

[0075] In one possible example of the second aspect, the first non-critical extended field includes a first segment number field and / or a first last segment field;

[0076] The 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;

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

[0078] In one possible example of the second aspect, the first RRC message includes an RRC reconfiguration message;

[0079] The first segment includes the radio bearer configuration field in the RRC reconfiguration message;

[0080] The second segment includes the secondary cell group field and measurement configuration field in the RRC reconfiguration message.

[0081] In one 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,

[0082] The first RRC message is the RRC message transmitted over the network after the terminal device successfully enters the RRC connection state; or,

[0083] The first RRC message is the RRC message transmitted over the network after the terminal device has completed random access.

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

[0085] In one possible example of the second aspect, K1 is a value specified by the protocol or set by default; or,

[0086] K1 is a value determined based on the number of repeated transmissions of message 4 during the random access process; or,

[0087] K1 is a value determined based on the channel information corresponding to message 3 in the random access process.

[0088] In one possible example of the second aspect, the method also includes:

[0089] Receive device capability information, which indicates that the terminal device supports payload segmentation processing of the first RRC message.

[0090] In one possible example of the second aspect, the method also includes:

[0091] Send a third message, which is an RRC message containing the second segment;

[0092] Receive the fourth message, which is an RRC message used to confirm the successful integration of the first and second segments.

[0093] In one possible example of the second aspect, the third message includes a second RRC transaction identifier field, a second critical extension field, and a second non-critical extension field;

[0094] The second segment is in the second key extended field and / or the second non-key extended field;

[0095] The second RRC transaction identifier field is used to identify the RRC transaction corresponding to the third message;

[0096] The second key extended field is used to carry key configuration information for the third message;

[0097] The second non-critical extended field is used to carry non-critical configuration information for the third message.

[0098] In one possible example of the second aspect, the second non-critical extended field includes the second segment number field and / or the second last segment field;

[0099] The second segment sequence number field indicates the sequence number of the second segment in the segment obtained by dividing the payload of the first RRC message;

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

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

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

[0103] Thirdly, a communication device according to this application includes:

[0104] The receiving unit is configured to receive a first message, wherein the first message is an RRC message containing a first segment of the first RRC message;

[0105] The sending unit is used to send a second message, which is an RRC message used to confirm that the first message was successfully completed;

[0106] The payload of the first RRC message is divided into a first segment and a second segment. The first segment consists of a portion of the fields in the payload of the first RRC message, and the second segment consists of the remaining fields in the payload of the first RRC message excluding the first segment.

[0107] In one possible example of the third aspect, the length of the first segment is less than the length of the second segment.

[0108] In one possible example of the third aspect, the first message includes a first RRC transaction identifier field, a first critical extension field, and a first non-critical extension field;

[0109] The first segment is in the first key extended field and / or the first non-key extended field;

[0110] The first RRC transaction identifier field is used to identify the RRC transaction of the first message;

[0111] The first key extended field is used to carry key configuration information for the first message;

[0112] The first non-critical extended field is used to carry non-critical configuration information for the first message.

[0113] In one possible example of the third aspect, the first non-critical extended field includes a first segment number field and / or a first last segment field;

[0114] The 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;

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

[0116] In one possible example of the third aspect, the first RRC message includes an RRC reconfiguration message;

[0117] The first segment includes the radio bearer configuration field in the RRC reconfiguration message;

[0118] The second segment includes the secondary cell group field and measurement configuration field in the RRC reconfiguration message.

[0119] In one 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,

[0120] The first RRC message is the RRC message transmitted over the network after the terminal device successfully enters the RRC connection state; or,

[0121] The first RRC message is the RRC message transmitted over the network after the terminal device has completed random access.

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

[0123] In one possible example of the third aspect, K1 is a value specified by the protocol or set by default; or,

[0124] K1 is a value determined based on the number of repeated transmissions of message 4 during the random access process; or,

[0125] K1 is a value determined based on the channel information corresponding to message 3 in the random access process.

[0126] In one possible example of the third aspect, the sending unit is also used to send device capability information, which indicates that the terminal device supports payload segmentation processing of the first RRC message.

[0127] In one possible example of the third aspect, the receiving unit is also configured to receive a third message, which is an RRC message containing the second segment;

[0128] The sending unit is also used to send a fourth message, which is an RRC message used to confirm the successful integration of the first segment and the second segment.

[0129] In one possible example of the third aspect, the third message includes a second RRC transaction identifier field, a second critical extension field, and a second non-critical extension field;

[0130] The second segment is in the second key extended field and / or the second non-key extended field;

[0131] The second RRC transaction identifier field is used to identify the RRC transaction corresponding to the third message;

[0132] The second key extended field is used to carry key configuration information for the third message;

[0133] The second non-critical extended field is used to carry non-critical configuration information for the third message.

[0134] In one possible example of the third aspect, the second non-critical extended field includes the second segment number field and / or the second last segment field;

[0135] The second segment sequence number field indicates the sequence number of the second segment in the segment obtained by dividing the payload of the first RRC message;

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

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

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

[0139] Fourthly, a communication device according to this application includes:

[0140] The sending unit is used to send a first message, which is an RRC message containing the first segment of the first RRC message;

[0141] The receiving unit is used to receive a second message, which is an RRC message used to confirm that the first message was successfully completed.

[0142] The payload of the first RRC message is divided into a first segment and a second segment. The first segment consists of a portion of the fields in the payload of the first RRC message, and the second segment consists of the remaining fields in the payload of the first RRC message excluding the first segment.

[0143] In one possible example of the fourth aspect, the length of the first segment is less than the length of the second segment.

[0144] In one possible example of the fourth aspect, the first message includes a first RRC transaction identifier field, a first critical extension field, and a first non-critical extension field;

[0145] The first segment is in the first key extended field and / or the first non-key extended field;

[0146] The first RRC transaction identifier field is used to identify the RRC transaction of the first message;

[0147] The first key extended field is used to carry key configuration information for the first message;

[0148] The first non-critical extended field is used to carry non-critical configuration information for the first message.

[0149] In one possible example of the fourth aspect, the first non-critical extended field includes a first segment number field and / or a first last segment field;

[0150] The 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;

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

[0152] In one possible example of the fourth aspect, the first RRC message includes an RRC reconfiguration message;

[0153] The first segment includes the radio bearer configuration field in the RRC reconfiguration message;

[0154] The second segment includes the secondary cell group field and measurement configuration field in the RRC reconfiguration message.

[0155] In one 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,

[0156] The first RRC message is the RRC message transmitted over the network after the terminal device successfully enters the RRC connection state; or,

[0157] The first RRC message is the RRC message transmitted over the network after the terminal device has completed random access.

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

[0159] In one possible example of the fourth aspect, K1 is a value specified by the protocol or set by default; or,

[0160] K1 is a value determined based on the number of repeated transmissions of message 4 during the random access process; or,

[0161] K1 is a value determined based on the channel information corresponding to message 3 in the random access process.

[0162] In one possible example of the fourth aspect, the receiving unit is also configured to receive device capability information, which indicates that the terminal device supports payload segmentation processing of the first RRC message.

[0163] In one possible example of the fourth aspect, the sending unit is also used to send a third message, which is an RRC message containing the second segment;

[0164] The receiving unit is also used to receive a fourth message, which is an RRC message used to confirm that the integration of the first segment and the second segment has been successfully completed.

[0165] In one possible example of the fourth aspect, the third message includes a second RRC transaction identifier field, a second critical extension field, and a second non-critical extension field;

[0166] The second segment is in the second key extended field and / or the second non-key extended field;

[0167] The second RRC transaction identifier field is used to identify the RRC transaction corresponding to the third message;

[0168] The second key extended field is used to carry key configuration information for the third message;

[0169] The second non-critical extended field is used to carry non-critical configuration information for the third message.

[0170] In one possible example of the fourth aspect, the second non-critical extended field includes the second segment number field and / or the second last segment field;

[0171] The second segment sequence number field indicates the sequence number of the second segment in the segment obtained by dividing the payload of the first RRC message;

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

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

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

[0175] Fifthly, the method described in the first aspect above is applied to terminal devices.

[0176] Sixthly, the method described in the second aspect above is applied to network devices.

[0177] A seventh aspect is a terminal device according to this application, 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 method described in the first aspect above.

[0178] Eighthly, a network device according to this application includes 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.

[0179] A ninth aspect is a chip according to this application, comprising a processor, wherein the processor performs the method described in the first or second aspect above. Optionally, the chip further comprises an interface circuit, the processor being connected to the interface circuit, the interface circuit being used for transmitting and receiving information.

[0180] A tenth aspect is a chip module according to this application, including a transceiver component and a chip, wherein the chip includes a processor, the processor performs the method described in the first or second aspect above, and the transceiver component is used to send and receive information.

[0181] Eleventhly, a communication system according to this application includes the terminal equipment described in the seventh aspect and the network equipment described in the eighth aspect.

[0182] The twelfth aspect is a computer-readable storage medium of this application, wherein the computer-readable storage medium stores a computer program or instructions that, when executed, implement the method described in the first or second aspect above.

[0183] The thirteenth aspect is a computer program product of this application, comprising a computer program or instructions, wherein the computer program or instructions, when executed, implement the method described in the first or second aspect above. Exemplarily, the computer program product may be a software installation package.

[0184] It is worth noting that the beneficial effects of the technical solutions in aspects two through thirteen can be found in the technical effects of the technical solution in aspect one above, and will not be repeated here. Attached Figure Description

[0185] Figure 1 This is a schematic diagram of the architecture of a communication system according to an embodiment of this application;

[0186] Figure 2 This is a schematic diagram of the architecture of another communication system according to an embodiment of this application;

[0187] Figure 3 This is a flowchart illustrating a method for transmission and feedback based on load segmentation and step-by-step transmission according to an embodiment of this application.

[0188] Figure 4 This is a flowchart illustrating a communication method according to an embodiment of this application;

[0189] Figure 5 This is a flowchart illustrating a method for transmission and feedback based on payload segmentation and step-by-step transmission following a four-step random access process, according to an embodiment of this application.

[0190] Figure 6 This is a flowchart illustrating another communication method according to an embodiment of this application;

[0191] Figure 7 This is a flowchart illustrating another communication method according to an embodiment of this application;

[0192] Figure 8This is a flowchart illustrating another method for transmission and feedback based on load segmentation and step-by-step transmission according to an embodiment of this application;

[0193] Figure 9 This is a functional unit block diagram of a communication device according to an embodiment of this application;

[0194] Figure 10 This is a functional unit block diagram of another communication device according to an embodiment of this application;

[0195] Figure 11 This is a schematic diagram of the structure of a terminal device according to an embodiment of this application;

[0196] Figure 12 This is a schematic diagram of the structure of a network device according to an embodiment of this application. Detailed Implementation

[0197] It should be understood that the terms "first," "second," etc., used in the embodiments of this application are used to distinguish different objects, rather than to describe a specific order. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, software, product, or device that includes 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.

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

[0199] In the embodiments of this application, "at least one" or "at least one item" refers to one or more, and "multiple" refers to two or more.

[0200] In the embodiments of this application, "and / or" describes the association relationship between related objects, indicating that there can be three relationships. For example, A and / or B can represent the following three situations: A exists alone, A and B exist simultaneously, and B exists alone. Among them, A and B can be singular or plural.

[0201] In the embodiments of this application, "at least one of the following" or similar expressions refer to any combination of these items, including any combination of single or multiple items. For example, at least one of a, b, or c can represent the following seven cases: 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.

[0202] In this application's embodiments, "equal to" can be used with "greater than" and is applicable to technical solutions where the value is greater than, or it can be used with "less than" and is applicable to technical solutions where the value is less than. When "equal to" is used with "greater than," it is not used with "less than"; when "equal to" is used with "less than," it is not used with "greater than."

[0203] 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 expressed are consistent.

[0204] In the embodiments of this application, "network" can be expressed as the same concept as "system," and a communication system is a communication network.

[0205] In this application, the term "instruction" can be used interchangeably with "configuration" or similar terms.

[0206] In this application, "connection" refers to various connection methods, such as direct connection or indirect connection, to achieve communication between devices, and is not specifically limited thereto.

[0207] The communication system of this embodiment will be described below as an example.

[0208] The technical solutions of this application can be applied to various communication systems. For example, long term evolution (LTE) systems, advanced long term evolution (LTE-A) systems, New Radio (NR) systems, evolution systems of NR systems, LTE-based access to unlicensed spectrum (LTE-U) systems, NR-based access to unlicensed spectrum (NR-U) systems, non-terrestrial networks (NTN) systems, universal mobile telecommunication system (UMTS), or future communication systems, etc.

[0209] 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 can 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.

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

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

[0212] Exemplary, an embodiment of the network architecture of a communication system in this application, such as Figure 1 As shown. In Figure 1In this system, the communication system 10 may include a network device 110 and a terminal device 120. The terminal device 120 can communicate with the network device 110 wirelessly.

[0213] certainly, Figure 1 This is merely an example of a network architecture for a communication system and does not constitute a limitation on the network architecture of the communication systems in the embodiments of this application. For example, the communication system 10 may also include servers or other devices, or the communication system 10 may include other network devices besides network device 110, or the communication system 10 may include other terminal devices besides terminal device 120.

[0214] The terminal device of this embodiment will be described below as an example.

[0215] In one possible example, a terminal device is a device with transceiver capabilities, also known as a terminal, user equipment (UE), remote terminal equipment (relay UE), relay equipment (relay UE), access terminal equipment, user unit, user station, mobile station, mobile station, remote station, mobile device, user terminal equipment, smart terminal equipment, wireless communication equipment, user agent, or user apparatus. It should be noted that a relay device is a terminal device capable of providing relay forwarding services to other terminal devices (including remote terminal devices).

[0216] For example, terminal devices include mobile phones, tablets, computers with wireless transceiver capabilities, virtual reality (VR) terminal devices, augmented reality (AR) terminal devices, wireless terminal devices in industrial control, wireless terminal devices in 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, etc.

[0217] For example, terminal devices include cellular phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), handheld devices with wireless communication capabilities, computing devices or other processing devices connected to a wireless modem, in-vehicle devices, wearable devices, terminal devices in future communication systems, or terminal devices in future evolved public land mobile networks (PLMNs).

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

[0219] 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 water (such as on ships); or it can be deployed in the air (such as airplanes, balloons, and satellites).

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

[0221] The network device of this embodiment will be described below as an example.

[0222] In one possible example, a network device is a device with transceiver capabilities that can be used to communicate with terminal devices.

[0223] In one possible example, the network device includes means for providing wireless communication capabilities to the network device, such as a chip system, a chip, or a chip module. The chip system may include a chip or other discrete components.

[0224] In one possible example, a network device provides services to a cell, and terminal devices within that cell can communicate with the network device via transmission resources (such as spectrum resources). This cell can be a macro cell, small cell, metro cell, micro cell, pico cell, or femto cell, etc.

[0225] In one possible example, the network device has mobility characteristics; for example, the network device is a mobile device. Optionally, 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, a high elliptical orbit (HEO) satellite, etc. Optionally, the network device can also be a base station located on land, water, or other similar locations.

[0226] In one possible example, network devices include access network devices and / or core network (CN) devices.

[0227] The following provides an example of access network equipment.

[0228] In one possible example, the access network equipment 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 radio 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, and is used to implement functions such as radio access bearer control. RAN nodes can be any device with wireless transceiver capabilities, including but not limited to 5G node base (gNB), evolved node base (eNB), access point (AP), world interoperability for microwave access base station (WiMAX BS), transmission receiving point (TRP), wireless relay node, wireless backhaul node, master node (MN) in a dual connectivity architecture, and secondary node (SN) in a dual connectivity architecture, etc.

[0229] In one possible example, access network equipment refers to equipment used to communicate with terminal equipment. For example, access network equipment may include base stations (BTS) in Global System for Mobile Communication (GSM) or Code Division Multiple Access (CDMA), base stations (nodeB, NB) in Wideband Code Division Multiple Access (WCDMA), evolved node base stations (eNB) in LTE systems, radio controllers, relay stations, access points, vehicle-mounted equipment, wearable devices in cloud radio access network (CRAN) scenarios, access network equipment in 5G networks, access network equipment in future networks, or access network equipment in future evolved PLMN networks, etc.

[0230] In a possible example, in 5G NR, the functionality of access network equipment is divided into two parts, referred to 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 are physically connected via fiber optic cable, and logically share a specially defined F1 interface for communication between them. Functionally, the CU is primarily responsible for radio resource control and configuration, inter-cell mobility management, and bearer management. The DU is primarily responsible for scheduling, physical signal generation, and transmission.

[0231] In one possible example, access network equipment includes macro base stations, micro base stations, pico base stations, small cells, relay stations, or balloon stations, etc.

[0232] The following provides an example of core network equipment.

[0233] In one possible example, core network equipment includes network elements that provide various functions. Here, "network element" can also be referred to as an entity, device, apparatus, or module, etc., without specific limitation. Furthermore, for ease of understanding and explanation, the description of "network element" is omitted in some descriptions. For example, the network exposure function (NEF) network element is abbreviated as NEF. In this case, "NEF" should be understood as a NEF network element or NEF entity. The following omits explanations of similar or identical cases.

[0234] 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. Among these, the corresponding functional entities in a 5G system include core network control plane (CP) or user plane (UP) network functions, etc. The core network control plane can also be understood as the core network control plane function (CPF) entity.

[0235] In one possible example, the network elements included in the core network equipment 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.

[0236] It should be noted that terminal devices can connect to access network devices wirelessly, and access network devices can connect to core network devices wirelessly or via wired connections. Core network devices can connect to a data network (DN). Access network devices and core network devices can be independent physical devices, or the functions of core network devices and the logical functions of access network devices can be integrated into the same physical device. Alternatively, a single physical device can integrate some of the functions of core network devices and some of the functions of access network devices.

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

[0238] It should be noted that, Figure 2 The names of the network elements included are merely names and do not limit the functionality of the network element itself. In 5G networks and other future networks, the aforementioned network elements may also have other names, and there are no specific restrictions on this. For example, in future communication systems, some or all of the aforementioned network elements may use the terminology from 5G, or they may have other names, etc. This is explained uniformly here and will not be elaborated further below.

[0239] in addition, Figure 2 The various network elements in the network do not necessarily have to exist at the same time; the required network elements can be determined based on the needs. Figure 2 The connection relationships between the various network elements are not uniquely defined and can be adjusted according to requirements. It is understood that the aforementioned network elements or functions can be network components in hardware devices, software functions running on dedicated hardware, or virtualization functions instantiated on a platform (e.g., a cloud platform).

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

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

[0242] In scenarios with poor signal coverage, high latency, and unstable channel quality, such as NTN, mobile edge computing, or cell edge environments, directly transmitting a large RRC message may face the following severe challenges:

[0243] (1) Larger block error rate

[0244] As the payload length of an RRC message increases, the probability of transmission failure in the above scenario increases exponentially. A single RRC message transmission failure will directly lead to the failure of the RRC process, which may cause disconnection and reconnection, seriously affecting user experience and network stability.

[0245] (2) Lower resource efficiency

[0246] The longer the payload length of an RRC message, the more transmission resources it requires. While using a repetition mechanism to transmit RRC messages can improve the success rate, it also incurs significant resource overhead, especially when channel conditions are not consistently poor.

[0247] (3) Poor flexibility and adaptability

[0248] Network devices may not be able to obtain the latest channel information before sending RRC messages, and can only make a rough estimate based on historical channel information. They cannot make optimal decisions for the transmission of RRC messages, thus lacking link adaptation and failing to achieve link adaptation under uncertain channel information.

[0249] 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), etc.

[0250] Furthermore, the repeated transmission of RRC messages mentioned in this embodiment refers to transmitting the same content of the same RRC message multiple times. The purpose is to improve the success rate of RRC message reception through diversity gain or redundant transmission. These multiple transmissions are part of the same transmission process, initiated proactively by the network, and do not require waiting for feedback from the terminal device.

[0251] 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, aiming to solve the above challenges and achieve the following objectives:

[0252] (1) Payload segmentation of RRC messages

[0253] The payload of the original RRC message is divided into multiple segments, and each segment is encapsulated into a new RRC message. The payload length of each new RRC message is smaller than that of the original RRC message.

[0254] (2) Improve transmission reliability and resource efficiency

[0255] Since the payload length of each new RRC message is smaller than that of the original RRC message, the transmission of new RRC messages is less prone to bit errors and requires fewer transmission resources.

[0256] Thus, when using the retransmission mechanism to transmit new RRC messages, the retransmission of new RRC messages has less resource overhead than the retransmission of the original RRC messages.

[0257] (3) Step-by-step transmission and feedback

[0258] The network transmits a new RRC message in stages, and the terminal device needs to provide feedback on the successful completion of each new RRC message to complete an independent "transmission-feedback" loop. Only after completing an independent "transmission-feedback" loop for the previous new RRC message does the transmission of the next new RRC message begin.

[0259] For example, such as Figure 3 As shown, a method for transmission and feedback based on load segmentation and step-by-step processing includes the following steps:

[0260] S310. The network device retransmits the first new RRC message.

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

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

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

[0264] S330. The network device retransmits the second new RRC message.

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

[0266] S340. The terminal device provides feedback on the successful completion of the second new RRC message that was repeatedly transmitted.

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

[0268] (4) Enhance flexibility and adaptability

[0269] Because terminal devices require step-by-step transmission and feedback, the feedback from the previous 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 previous transmission.

[0270] As can be seen, the network can dynamically adjust its transmission strategy for the next transmission based on the latest channel information. This includes adjusting the modulation and coding scheme (MCS), resource scheduling, or the number of repeated transmissions, thereby achieving link adaptation. In this way, link adaptation can maximize resource conservation, improve transmission reliability, and enhance transmission flexibility, solving the problem of link adaptation being impossible under uncertain channel information.

[0271] For example, in the above Figure 3 In this 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 make a decision on the optimal transmission strategy for the transmission of the second new RRC message based on the latest channel information, thereby realizing dynamic adjustment of the transmission strategy and achieving the purpose of link adaptation.

[0272] Based on the above, this embodiment will use the interaction between a network device and a terminal device as an example to illustrate the method of transmission and feedback based on load segmentation and step-by-step processing. The network device in this method can also be a chip, unit, or device, etc., and the terminal device can also be a chip, unit, or device, etc.

[0273] like Figure 4 As shown, Figure 4 This is a flowchart illustrating a communication method according to an embodiment of this application, including the following steps:

[0274] S410. The network device sends a first message, which is an RRC message containing the first segment of the first RRC message.

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

[0276] The payload of the first RRC message is divided into a first segment and a second segment. The first segment consists of a portion of the fields in the payload of the first RRC message, and the second segment consists of the remaining fields in the payload of the first RRC message excluding the first segment.

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

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

[0279] As can be seen, in order to avoid problems such as high 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:

[0280] (1) Compared with directly transmitting the first RRC message 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 in sequence, thereby dividing the transmission of the first RRC message into two transmissions to improve transmission flexibility.

[0281] 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 realize the transmission of some fields of the first RRC message, and then use the second message to provide feedback on the successful completion of the first message, thereby completing an independent "transmission-feedback" closed loop.

[0282] (2) Since the payload length of the first message is less 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 those of the first RRC message.

[0283] In this way, the network can prioritize transmitting a portion of the first RRC message with a lower block error rate and less transmission resources, ensuring the reliability and resource efficiency of this portion of the transmission. 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, enabling timely execution of some RRC-related processing.

[0284] (3) Compared to the network being unable to make a decision on the optimal transmission strategy of the first RRC message based on the latest channel information before the first RRC message is directly transmitted, since this embodiment needs to provide 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.

[0285] In this way, the network can make decisions on the optimal transmission strategy for the second segment based on the latest channel information, realize dynamic adjustment of the transmission strategy, and ensure transmission reliability, resource efficiency and link adaptability in subsequent transmission of the second segment.

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

[0287] In this embodiment, the first RRC message is a network-transmitted RRC message.

[0288] 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 network transmission or any network transmission).

[0289] As can be seen, since the terminal device has successfully accessed the cell, it is in the RRC connected state. Thus, the network device can make corresponding decisions regarding the RRC connection (such as modification, release, maintenance, or restoration) through the first RRC message.

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

[0291] In this way, network devices can make corresponding decision-making processes (such as modification, release, maintenance, or recovery) on the RRC connection through the first RRC message.

[0292] In one possible example, the first RRC message is an RRC message transmitted over the network after the terminal device has completed random access (such as the first network transmission or any network transmission).

[0293] As can be seen, since the terminal device has completed the random access process, it can successfully enter the RRC connection state. Thus, the network device can make corresponding decision-making processes regarding the RRC connection (such as modification, release, maintenance, or restoration) through the first RRC message.

[0294] In one possible example, the first RRC message includes an RRC reconfiguration message. The RRC reconfiguration message is a command used to modify the RRC connection and can carry information such as measurement configuration, mobility control, radio resource configuration (e.g., resource block (RB), MAC master configuration, and physical channel configuration), and access stratum (AS) security configuration.

[0295] In this way, network devices can modify RRC connections via RRC reconfiguration messages or RRC connection reconfiguration messages.

[0296] It is worth noting that the RRC reconfiguration message mentioned in this embodiment can also be an RRC connection reconfiguration message, and there are no specific restrictions on this.

[0297] 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 the protocol data unit (PDU), the maximum length limit of the service data unit (SDU), or the maximum buffer capacity of the RRC message.

[0298] The payload of the first RRC message refers to the effective information actually carried in the first RRC message, excluding the header information of the underlying protocol.

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

[0300] The payload of the first RRC message includes critical extensions fields and / or non-critical extensions fields. The critical extensions fields are used to carry critical configuration information of the first RRC message, while the non-critical extensions fields are used to carry non-critical configuration information of the first RRC message.

[0301] It should be noted that critical and non-critical extended fields are extension mechanisms based on the abstract syntax notation one (ASN.1) syntax definition. These mechanisms are used to support backward compatibility and functional extensibility of RRC messages, ensuring that devices of different versions can correctly interact with RRC messages.

[0302] For example, in Table 1, the key extended fields are used to carry key configuration information. The information they carry 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.

[0303] Non-critical extension fields can be placed at the end of the RRC message to carry optional or ignorable non-critical configuration information. This allows older terminal devices to safely ignore unrecognized non-critical extension fields when parsing RRC messages, preventing parsing failure.

[0304] Non-critical extension fields can be defined as an extensible sequence and flexibly expanded through an "empty sequence" mechanism. When there is no non-critical extension information, the non-critical extension fields exist as an "empty sequence". When new non-critical configuration information needs to be added, the new field can be appended to the non-critical extension fields without modifying the core structure of the RRC message.

[0305] In this way, when older versions of terminal devices cannot recognize a newly added field, they can treat the newly added field as an "extension of an empty sequence" and ignore the newly added field without affecting the parsing of the entire RRC message.

[0306] Table 1

[0307]

[0308] Key extended fields can be a collection of one or more fields, and non-key extended fields can be a collection of one or more fields.

[0309] For example, taking the first RRC message as including an RRC reconfiguration message as an example, the key extended fields of the RRC reconfiguration message include at least one of the following: radiobearerconfig field, secondary cellgroup field, or measurement configuration field.

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

[0311] The secondary cell configuration field can be used to configure relevant information about 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.

[0312] The measurement configuration field can be used to configure measurement information, such as the measurement object, the triggering conditions for the measurement report, and measurement resources.

[0313] The first and second segments will be explained in detail below.

[0314] In this embodiment, the payload length of the first RRC message directly reflects the complexity of the signaling and resource overhead. For example, the longer the payload length of the first RRC message, the more likely it is to have bit errors, and the more transmission resources it requires, thereby reducing transmission reliability and resource efficiency. Based on this, this embodiment segments the payload of the first RRC message to obtain a first segment and a second segment.

[0315] In one possible example, the first segment is used to carry the minimum RRC configuration information, and the second segment is used to carry the remaining RRC configuration information other than the minimum RRC configuration information.

[0316] The minimum RRC configuration information can refer to the most important (most critical or core) and shortest configuration information, so that the terminal device can perform some important RRC-related processing based on the minimum RRC configuration information.

[0317] In this way, since the network device prioritizes transmitting the first segment to the terminal device, the terminal device can receive the minimum RRC configuration information first, so as to carry out some important RRC-related processing in a timely manner based on the minimum RRC configuration information.

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

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

[0320] It is evident that, since the length of the first segment is shorter 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 transmitting the first segment with a lower block error rate and fewer transmission resources. Then, feedback from the first segment can be used to optimize the transmission strategy for the second segment, thereby improving its transmission success rate and ultimately enhancing its transmission reliability and resource efficiency.

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

[0322] As can be seen, 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.

[0323] In this way, since the network device prioritizes transmitting the first segment to the terminal device, the terminal device can preferentially parse the radio bearer configuration field. This allows it to prioritize radio bearer-related processing based on the radio bearer configuration field, such as establishing SRB2 and / or DRS and activating AS security. Subsequent processing, including secondary cell configuration and measurement configuration, is performed after the second segment is transmitted.

[0324] Optionally, the first segment may include other fields besides the radio bearer configuration field (such as the master cell group field), and the second segment may include other fields besides the secondary cell configuration field and the measurement configuration field. There are no specific restrictions on this.

[0325] The first and second messages are illustrated below.

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

[0327] In one possible example, the first message includes a first RRC transaction identifier field, a first critical extension field, and a first non-critical extension field.

[0328] It is understood that the payload of the first message includes the first RRC transaction identifier field, the first critical extension field, and the first non-critical extension field, and the payload length of the first message is less than the payload length of the first RRC message.

[0329] The first RRC transaction identifier field can be used to identify the RRC transaction of the first message. In this way, the terminal device can obtain the RRC transaction of the first message through the first RRC transaction identifier field, so as to correctly parse the first message.

[0330] The first key extended field can be used to carry key configuration information for the first message.

[0331] It is understandable that the first associated extended field is the associated extended field of the first message. The relevant content of the first key extended field can be found in the "Key Extended Fields" in "Table 1" above, and will not be repeated here.

[0332] Thus, when parsing the first message, the terminal device must parse and identify the first key extended field; otherwise, it will refuse to process the entire RRC message and trigger the corresponding error handling process.

[0333] Among them, the first non-critical extended field can be used to carry non-critical configuration information of the first message.

[0334] It is understandable that the first non-related extended field is the non-related extended field of the first message. For relevant information on the first non-critical extended field, please refer to the "Non-critical Extended Fields" in "Table 1" above. It will not be repeated here.

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

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

[0337] Thus, if the first segment is in the first key extension field, then all fields in the first segment must be identified; if the first segment is in the first non-key extension field, then all fields in the first segment are optional and can be ignored; if the first segment is in both the first key extension field and the first non-key extension field, then some fields in the first segment must be identified, and the remaining fields are optional and can be ignored.

[0338] Optionally, the first non-critical extended field may include the first segment number field and / or the first last segment field.

[0339] The first segment sequence number field indicates the sequence number of the first segment within the segments obtained from the payload of the first RRC message. Of course, the sequence number can also be replaced with an index or an ID; the following explanation primarily uses the sequence number as an example.

[0340] This is because, in the first RRC message payload, which is divided into a first segment and a second segment, each segment has its own sequence number. The sequence number of the first segment is less than that of the second segment; for example, the first segment's sequence number is 0 and the second segment's sequence number is 1. This allows network devices to send the segments in ascending order of sequence number, and terminal devices to integrate the received segments in ascending order of sequence number to obtain the entire payload of the first RRC message.

[0341] 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 extended fields, the terminal device can safely ignore it if it cannot recognize the first segment sequence number field, without causing the first message parsing to fail.

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

[0343] This is because, in the first RRC message payload segmented into a first segment and a 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 tell 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.

[0344] In this way, the terminal device can know that the first segment is not the last segment through the first last segment field, so that the terminal device can continue to wait to receive segments until the last segment. At the same time, since the first last segment field is a non-critical extended 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.

[0345] In one possible example, the first message is transmitted K1 times, where K1 is an integer greater than or equal to 1.

[0346] Understandably, the network device transmits the first message K1 times. When K1 equals 1, it is equivalent to transmitting the first message only once.

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

[0348] Optionally, K1 is a value specified by the protocol or set by default. In this way, the network device can determine the number of times the first message is retransmitted as K1 according to the method specified by the protocol or set by default.

[0349] Optionally, K1 is a value determined based on the number of times message 4 is repeatedly transmitted during the random access process.

[0350] This is because the random access procedure is a fundamental and crucial process in communication systems. Through the random access procedure, terminal devices can establish wireless links with network devices or achieve uplink and downlink synchronization, etc. The random access procedure includes a 4-step random access procedure and a 2-step random access procedure.

[0351] In the 4-step random access process, after the network device receives message 3 (Msg3), in order to improve transmission reliability, the network device may need to repeatedly transmit message 4 (Msg4) to the terminal device. Among them, Msg3 can provide the network device with the latest channel information, so that the network device can determine the number of times Msg4 needs to be repeatedly transmitted based on the channel information corresponding to Msg3.

[0352] 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 retransmissions of the first message as K1 based on the number of retransmissions of Msg4. For example, the number of retransmissions of message 4 and the number of retransmissions of the first message are both K1.

[0353] For example, such as Figure 5 As shown, the method for transmission and feedback based on payload partitioning and step-by-step transmission following the four-step random access process includes the following steps:

[0354] S510. The terminal device sends message 1 (message1, Msg1).

[0355] Correspondingly, the network device receives Msg1.

[0356] Msg1 can also be called the physical random access channel preamble (PRACH preamble).

[0357] Msg1 can be used to request access from network devices so that network devices can estimate the transmission delay between themselves and terminal devices based on Msg1 and use this to calibrate uplink timing.

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

[0359] Correspondingly, the terminal device receives Msg2.

[0360] Msg2 can also be called a random access response (RAR).

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

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

[0363] Correspondingly, the network device receives Msg3.

[0364] Msg3 can be an RRC setup request (RRCSetupRequest) message.

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

[0366] Msg3 can provide network devices with the latest channel information (i.e., the channel information corresponding to Msg3). For example, DMRS in Msg3 provides network devices with the latest channel information.

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

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

[0369] Msg4 can be an RRC setup (RRCSetup) message.

[0370] Msg4 can carry a flag to uniquely identify the terminal device to indicate the winning terminal device, while other terminal devices that did not win in the conflict resolution will re-initiate random access.

[0371] The network device can determine the number of repeated transmissions of Msg4 as K1 based on the channel information corresponding to Msg3.

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

[0373] Correspondingly, the network device receives Msg5.

[0374] Msg5 can be an RRC setup complete message (RRCSetupComplete).

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

[0376] Correspondingly, the terminal device receives the first message that is transmitted repeatedly.

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

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

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

[0380] This is because, as can be seen from the above, since the channel information corresponding to Msg3 can determine the number of times Msg4 is retransmitted, and the number of times Msg4 is retransmitted can determine the number of times the first message is retransmitted, the network device can determine the number of times the first message is retransmitted as K1 based on the channel information corresponding to Msg3, thereby improving the success rate of receiving the first message by retransmitting the first message.

[0381] The following example illustrates how a terminal device reports its ability to perform payload segmentation processing that supports the first RRC message to a network device.

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

[0383] Optionally, this embodiment adopts the "terminal device self-reporting" method for reporting, that is, the terminal device self-reports to the network device whether it has the ability to support the payload segmentation processing of the first RRC message.

[0384] Optionally, this embodiment adopts a "query first, then report" approach for reporting. That is, the network device can first query the terminal device to see if it supports the payload segmentation processing of the first RRC message, and then the terminal device reports to the network device.

[0385] For example, such as Figure 6 As shown, Figure 6 This is a flowchart illustrating another communication method according to an embodiment of this application, including the following steps:

[0386] S610. The network device sends a device capability query message, which is used to query whether the terminal device supports the payload segmentation processing of the first RRC message.

[0387] Correspondingly, the terminal device receives device capability query information.

[0388] S620. The terminal device sends device capability information, which indicates that the terminal device supports payload segmentation processing of the first RRC message.

[0389] Correspondingly, network devices receive device capability information.

[0390] S630. The network device sends the first message.

[0391] Correspondingly, the terminal device receives the first message. The details of S630 can be found in the relevant content of S410 above, and will not be repeated here.

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

[0393] Correspondingly, the network device receives the second message. The details of S640 can be found in the relevant content of S420 above, and will not be repeated here.

[0394] It is evident that by using device capability query information and device capability information, the terminal device can report its support for the first RRC message payload segmentation processing in a "query first, then report" manner.

[0395] The following example illustrates the transmission and feedback of the first and second segments.

[0396] In one possible example, such as Figure 7 As shown, Figure 7 This is a flowchart illustrating another communication method according to an embodiment of this application, including the following steps:

[0397] S710. The network device sends the first message.

[0398] Correspondingly, the terminal device receives the first message. The details of S710 can be found in the relevant content of S410 above, and will not be repeated here.

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

[0400] Correspondingly, the network device receives the second message. The details of S720 can be found in the relevant content of S420 above, and will not be repeated here.

[0401] S730. The network device sends a third message, which is an RRC message containing the second segment.

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

[0403] 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 has been successfully completed.

[0404] The terminal device can integrate the first and second segments, and send the fourth message after the integration is successful.

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

[0406] As can be seen, in order to avoid problems such as high 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:

[0407] (1) 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 transmission of the first RRC message into two separate 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, the second segment is transmitted through the third message to realize the transmission of the remaining fields of the first RRC message. Finally, the fourth message provides feedback on the successful integration of the first segment and the second segment, thus completing a closed loop of two independent "transmission-feedback".

[0408] (2) Compared to the network being unable to make a decision on the optimal transmission strategy of the first RRC message based on the latest channel information before the first RRC message is directly transmitted, since this embodiment can provide the network with the latest channel information through the second message, the network can make a decision on the optimal transmission strategy of the third message based on the latest channel information, thereby realizing dynamic adjustment of the transmission strategy and ensuring transmission reliability, resource efficiency and link adaptation when transmitting the second segment.

[0409] The following provides examples of the third and fourth messages.

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

[0411] In one possible example, the third message includes a second RRC transaction identifier field, a second critical extension field, and a second non-critical extension field.

[0412] It is understood that the payload of the third message includes the second RRC transaction identifier field, the second critical extension field, and the second non-critical extension field, and the payload length of the third message is less than the payload length of the first RRC message.

[0413] The second RRC transaction identifier field can be used to identify the RRC transaction of the third message. In this way, the terminal device can determine the RRC transaction of the third message through the second RRC transaction identifier field, thus enabling it to correctly parse the third message.

[0414] The second key extended field can be used to carry key configuration information for the third message.

[0415] It is understandable that the second related extended field is the related extended field of the third message. The relevant content of the second key extended field can be found in the "Key Extended Fields" in "Table 1" above, and will not be repeated here.

[0416] Thus, when parsing the third message, the terminal device must parse and identify the second key extended field; otherwise, it will refuse to process the entire RRC message and trigger the corresponding error handling process.

[0417] The second non-critical extended field can be used to carry non-critical configuration information for the third message.

[0418] It is understandable that the second non-related extended field is the non-related extended field of the third message. For details on the second non-critical extended field, please refer to the "Non-critical Extended Fields" in "Table 1" above.

[0419] In this way, if the terminal device encounters an unrecognized non-critical extended field when parsing a third message, it can safely ignore it without causing the third message parsing to fail.

[0420] The second segment is located in the second key extended field and / or the second non-key extended field.

[0421] Thus, if the second segment is in the second key extension field, then all fields in the second segment must be identified; if the second segment is in the first non-key extension field, then 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, then some fields in the second segment must be identified, and the remaining fields are optional and can be ignored.

[0422] Optionally, the second non-critical extended field may include the second segment number field and / or the second last segment field.

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

[0424] This is because, in the first RRC message payload, which is divided into a first segment and a second segment, each segment has its own sequence number. The sequence number of the first segment is less than that of the second segment; for example, the first segment's sequence number is 0 and the second segment's sequence number is 1. This ensures that network devices can send the segments in ascending order of sequence number, and that terminal devices can integrate the received segments in ascending order of sequence number to obtain the entire payload of the first RRC message.

[0425] In this way, the terminal device can obtain the sequence number of the second segment through the second segment sequence number field. Furthermore, since the second segment sequence number field is a non-critical extended 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 parsing to fail. Only terminal devices that support payload segmentation processing of the first RRC message can recognize the second segment sequence number field.

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

[0427] This is because, in the first RRC message payload segmented into a first segment and a 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 tell 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.

[0428] In this way, the terminal device can determine that the second segment is the last segment through the second last segment field, allowing it to begin integrating the first and second segments after receiving the second field. Furthermore, since the second last segment field is a non-critical extended field, the terminal device can safely ignore it if it encounters an unrecognizable second last segment field when parsing the third message, without causing the third message parsing to fail. Only terminal devices that support payload segmentation processing of the first RRC message can recognize the second last segment field.

[0429] In one possible example, the third message is transmitted K2 times, where K2 is an integer greater than or equal to 1.

[0430] It is understandable that the network device transmits the third message K2 times. When K2 equals 1, it is equivalent to transmitting the third message only once.

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

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

[0433] 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 on 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 as K2, thereby improving the success rate of receiving the third message by repeatedly transmitting the third message.

[0434] Based on the above, the following example illustrates the entire process of the method based on load segmentation and step-by-step transmission and feedback.

[0435] like Figure 8 As shown, Figure 8 This is a flowchart illustrating another method for transmission and feedback based on load segmentation and step-by-step implementation according to an embodiment of this application, including the following steps:

[0436] S810: Reports with the ability to support payload segmentation processing of RRC messages.

[0437] As can be seen from the foregoing, this embodiment can report the terminal device's support for RRC message payload segmentation processing in either the "terminal device self-reporting" method or the "query first and then report" method, which will not be elaborated further.

[0438] S820: Load splitting decision for RRC messages.

[0439] If a terminal device supports payload segmentation processing for RRC messages, then when a network device needs to send a first RRC message to that terminal device, the network device can decide whether to segment the payload of the first RRC message based on factors such as channel information (such as historical channel information or channel information based on Msg3) and / or the payload length of the first RRC message.

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

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

[0442] When it is necessary to segment the payload of the first RRC message, the network device segments the payload of the first RRC message into a first segment and a second segment. The details of the first and second segments are described above and will not be repeated here.

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

[0444] 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 to the non-critical extended fields of the first message to indicate the sequence number of the first segment and / or that the first segment is not the last segment.

[0445] Then, the network device can transmit the first message once or repeat it 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 through a second message. The relevant content of the first and second messages can be found in the foregoing description and will not be repeated here.

[0446] S840: Provides the network with the latest channel information based on the feedback from the first segment.

[0447] After the network device successfully receives the second message, the second message can provide the network device with the latest channel information. For example, based on the DMRS in the second message, it can provide the latest SINR, PHR, or RSRP.

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

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

[0450] For example, if the latest channel information indicates good channel quality, network devices can choose a more aggressive MCS, a smaller number of retransmissions K1, or allocate fewer transmission resources. This allows for the selection of a higher-order modulation scheme and / or a higher coding rate due to a more aggressive MCS, thereby improving transmission reliability. Conversely, fewer retransmissions or less transmission resources reduce resource overhead, thus improving resource efficiency.

[0451] The network device then encapsulates the second segment into a third message and adds a second segment sequence number field and / or a second last segment field to the non-critical extended fields of the third message to indicate the sequence number of the second segment and / or that the second segment is the last segment.

[0452] Finally, the network device can transmit the third message once or repeat it K2 times based on the channel information corresponding to the second message. The content of the third message can be found in the preceding text and will not be repeated here.

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

[0454] After the terminal device successfully receives the third message, it parses the third message to determine that the second segment is the last segment. At this point, the terminal device can integrate the first and second segments in ascending order of their sequence numbers to obtain the entire payload of the first RRC message.

[0455] Finally, the terminal device provides feedback on the successful integration of the first and second segments, thus completing the entire RRC configuration.

[0456] As can be seen, compared with the direct transmission method of the first RRC message, this embodiment adopts a method based on payload 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.

[0457] For example, this embodiment compares the direct transmission method of the first RRC message with the transmission and feedback method based on payload segmentation and step-by-step processing, as shown in Table 2, using different scenarios as examples. In Table 2, the transmission and feedback method based on payload segmentation and step-by-step processing is designated as "Method 1", and the direct transmission method is designated as "Method 2".

[0458] Table 2

[0459]

[0460] The communication device of this embodiment will be described below as an example.

[0461] The above mainly describes the solution of the embodiments of this application from the perspective of the method. The functional units of a communication device according to this embodiment are illustrated below. It is understood that, in order to achieve the above functions, the terminal device or network device includes hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art should readily recognize that, in conjunction with the units and algorithm steps of the various examples described in the embodiments disclosed herein, this embodiment can be implemented in hardware or a combination of hardware and computer software. Whether a certain function is executed in a hardware or computer software-driven hardware manner depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this embodiment.

[0462] This application embodiment can divide terminal devices or network devices into functional units according to the above method examples. For example, each function can be divided into different functional units, or two or more functions can be integrated into one processing unit. The integrated unit can be implemented in hardware or as a software program module. It should be noted that the unit division in this application embodiment is illustrative and only represents a logical functional division, while other division methods may be used in actual implementation.

[0463] When using integrated units, Figure 9 This is a functional unit block diagram of a communication device according to an embodiment of this application. The communication device 900 includes a receiving unit 901 and a transmitting unit 902.

[0464] Optionally, the receiving unit 901 is a module unit for receiving relevant information, and there are no specific limitations on it.

[0465] Optionally, the transmitting unit 902 is a module unit used to transmit relevant information, and there are no specific limitations on it.

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

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

[0468] Optionally, the communication device 900 may also include a processing unit.

[0469] It should be noted that the processing unit can be a processor or controller, such as a baseband processor, baseband chip, central processing unit (CPU), general-purpose processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA), or other programmable logic device, transistor logic device, hardware component, 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 including one or more microprocessor combinations, a combination of a DSP and a microprocessor, etc.

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

[0471] Optionally, the communication device 900 is used to perform any of the steps performed by the terminal device, chip, or chip module as described in the above method embodiments.

[0472] In specific implementation, the receiving unit 901 and the sending unit 902 are used to execute the steps as described in the above method embodiments, and when performing other actions, they may selectively call other units to complete the corresponding operations. A detailed explanation follows.

[0473] The receiving unit 901 is used to receive a first message, wherein the first message is an RRC message containing the first segment of the first RRC message;

[0474] Sending unit 902 is used to send a second message, which is an RRC message used to confirm that the first message was successfully completed;

[0475] The payload of the first RRC message is divided into a first segment and a second segment. The first segment consists of a portion of the fields in the payload of the first RRC message, and the second segment consists of the remaining fields in the payload of the first RRC message excluding the first segment.

[0476] As can be seen, in order to avoid problems such as high block error rate, low resource efficiency, and poor adaptability caused by directly transmitting the first RRC message, this application divides the payload of the first RRC message into a first segment and a second segment to achieve the following objectives:

[0477] Compared to transmitting the first RRC message all at once, this application allows for the sequential transmission of the first RRC message, since its payload is divided into a first segment and a second segment. This divides the transmission of the first RRC message into two separate transmissions, improving transmission flexibility. After encapsulating the first segment into a single RRC message (i.e., the first message), the network can first transmit the first message to transmit a portion of its fields, and then use the second message to provide feedback on the successful completion of the first message, thus completing an independent "transmission-feedback" closed loop.

[0478] Because the payload length of the first message is shorter than that of the first RRC message, the transmission of the first message is less prone to errors, and the transmission resources for the first message are also less than those for the first RRC message. This allows the network to prioritize the transmission of a portion of the first RRC message with a lower block error rate and fewer transmission resources, ensuring the reliability and resource efficiency of this portion of the transmission. 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, enabling timely execution of some RRC-related processing.

[0479] Compared to the situation where the network might not be able to determine the optimal transmission strategy for the first RRC message based on the latest channel information before direct transmission, this application requires feedback on the successful completion of the first message via a second message. Therefore, this application can provide the network with the latest channel information through 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, achieving dynamic adjustment of the transmission strategy and ensuring transmission reliability, resource efficiency, and link adaptability during subsequent transmission of the second segment.

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

[0481] When using integrated units, Figure 10 This is a functional unit block diagram of another communication device according to an embodiment of this application. The communication device 1000 includes a transmitting unit 1001 and a receiving unit 1002.

[0482] Optionally, the transmitting unit 1001 is a module unit used to transmit relevant information, and there are no specific limitations on it. The transmitting unit 1001 can be a communication interface, transceiver, transceiver circuit, etc.

[0483] Optionally, the receiving unit 1002 is a module unit used to receive relevant information, and there are no specific limitations on it. The receiving unit 1002 can be a communication interface, transceiver, transceiver circuit, etc.

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

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

[0486] Optionally, the communication device 1000 may also include a processing unit.

[0487] It should be noted that the processing unit can be a processor or controller, such as a baseband processor, baseband chip, central processing unit (CPU), general-purpose processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA), or other programmable logic device, transistor logic device, hardware component, 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 including one or more microprocessor combinations, a combination of a DSP and a microprocessor, etc.

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

[0489] Optionally, the communication device 1000 is used to perform any of the steps performed by network devices, chips, or chip modules as described in the above method embodiments.

[0490] In specific implementation, the sending unit 1001 and the receiving unit 1002 are used to execute the steps as described in the above method embodiments, and when performing other actions, other units may be selectively invoked to complete the corresponding operations. A detailed description follows.

[0491] The sending unit 1001 is used to send a first message, which is an RRC message containing the first segment of the first RRC message;

[0492] Receiving unit 1002 is used to receive a second message, which is an RRC message used to confirm that the first message was successfully completed;

[0493] The payload of the first RRC message is divided into a first segment and a second segment. The first segment consists of a portion of the fields in the payload of the first RRC message, and the second segment consists of the remaining fields in the payload of the first RRC message excluding the first segment.

[0494] As can be seen, in order to avoid problems such as high block error rate, low resource efficiency, and poor adaptability caused by directly transmitting the first RRC message, this application divides the payload of the first RRC message into a first segment and a second segment to achieve the following objectives:

[0495] Compared to transmitting the first RRC message all at once, this application allows for the sequential transmission of the first RRC message, since its payload is divided into a first segment and a second segment. This divides the transmission of the first RRC message into two separate transmissions, improving transmission flexibility. After encapsulating the first segment into a single RRC message (i.e., the first message), the network can first transmit the first message to transmit a portion of its fields, and then use the second message to provide feedback on the successful completion of the first message, thus completing an independent "transmission-feedback" closed loop.

[0496] Because the payload length of the first message is shorter than that of the first RRC message, the transmission of the first message is less prone to errors, and the transmission resources for the first message are also less than those for the first RRC message. This allows the network to prioritize the transmission of a portion of the first RRC message with a lower block error rate and fewer transmission resources, ensuring the reliability and resource efficiency of this portion of the transmission. 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, enabling timely execution of some RRC-related processing.

[0497] Compared to the situation where the network might not be able to determine the optimal transmission strategy for the first RRC message based on the latest channel information before direct transmission, this application requires feedback on the successful completion of the first message via a second message. Therefore, this application can provide the network with the latest channel information through 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, achieving dynamic adjustment of the transmission strategy and ensuring transmission reliability, resource efficiency, and link adaptability during subsequent transmission of the second segment.

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

[0499] The structure of a terminal device in this embodiment is illustrated below.

[0500] Please see Figure 11 , Figure 11 This is a schematic diagram of the structure of a terminal device according to an embodiment of this application. 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.

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

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

[0503] Optionally, the terminal device 1100 can be one of the terminal devices described above.

[0504] Optionally, the processor 1110 can be one or more CPUs. If the processor 1110 is a CPU, the CPU can be a single-core CPU or a multi-core CPU.

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

[0506] In one possible example, the processor 1110 in terminal device 1100 is used to execute the computer program or instructions 1121 stored in memory 1120 to perform the following operations:

[0507] Receive a first message, which is an RRC message containing the first segment of the first RRC message;

[0508] Send a second message, which is an RRC message used to confirm that the first message was successfully completed;

[0509] The payload of the first RRC message is divided into a first segment and a second segment. The first segment consists of a portion of the fields in the payload of the first RRC message, and the second segment consists of the remaining fields in the payload of the first RRC message excluding the first segment.

[0510] As can be seen, in order to avoid problems such as high block error rate, low resource efficiency, and poor adaptability caused by directly transmitting the first RRC message, this application divides the payload of the first RRC message into a first segment and a second segment to achieve the following objectives:

[0511] Compared to transmitting the first RRC message all at once, this application allows for the sequential transmission of the first RRC message, since its payload is divided into a first segment and a second segment. This divides the transmission of the first RRC message into two separate transmissions, improving transmission flexibility. After encapsulating the first segment into a single RRC message (i.e., the first message), the network can first transmit the first message to transmit a portion of its fields, and then use the second message to provide feedback on the successful completion of the first message, thus completing an independent "transmission-feedback" closed loop.

[0512] Because the payload length of the first message is shorter than that of the first RRC message, the transmission of the first message is less prone to errors, and the transmission resources for the first message are also less than those for the first RRC message. This allows the network to prioritize the transmission of a portion of the first RRC message with a lower block error rate and fewer transmission resources, ensuring the reliability and resource efficiency of this portion of the transmission. 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, enabling timely execution of some RRC-related processing.

[0513] Compared to the situation where the network might not be able to determine the optimal transmission strategy for the first RRC message based on the latest channel information before direct transmission, this application requires feedback on the successful completion of the first message via a second message. Therefore, this application can provide the network with the latest channel information through 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, achieving dynamic adjustment of the transmission strategy and ensuring transmission reliability, resource efficiency, and link adaptability during subsequent transmission of the second segment.

[0514] It should be noted that the specific implementation of each operation can adopt the corresponding description of the method embodiment shown above. The terminal device 1100 can be used to execute the method embodiment described above in this embodiment, and will not be described again.

[0515] The structure of a network device according to this embodiment is illustrated below.

[0516] Please see Figure 12 , Figure 12 This is a schematic diagram of the structure of a network device according to an embodiment of this application. 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.

[0517] Optionally, the memory 1220 may include, but is not limited to, RAM, ROM, EPROM or CD-ROM, and the memory 1220 may be used to store the program code executed by the network device 1200 and the data transmitted.

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

[0519] Optionally, network device 1200 can be the network device described above.

[0520] Optionally, the processor 1210 can be one or more CPUs. If the processor 1210 is a CPU, the CPU can be a single-core CPU or a multi-core CPU.

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

[0522] In one possible example, the processor 1210 in network device 1200 is used to execute a computer program or instruction 1221 stored in memory 1220 to perform the following operations:

[0523] Send the first message, which is an RRC message containing the first segment of the first RRC message;

[0524] Receive a second message, which is an RRC message used to confirm that the first message was successfully completed;

[0525] The payload of the first RRC message is divided into a first segment and a second segment. The first segment consists of a portion of the fields in the payload of the first RRC message, and the second segment consists of the remaining fields in the payload of the first RRC message excluding the first segment.

[0526] As can be seen, in order to avoid problems such as high block error rate, low resource efficiency, and poor adaptability caused by directly transmitting the first RRC message, this application divides the payload of the first RRC message into a first segment and a second segment to achieve the following objectives:

[0527] Compared to transmitting the first RRC message all at once, this application allows for the sequential transmission of the first RRC message, since its payload is divided into a first segment and a second segment. This divides the transmission of the first RRC message into two separate transmissions, improving transmission flexibility. After encapsulating the first segment into a single RRC message (i.e., the first message), the network can first transmit the first message to transmit a portion of its fields, and then use the second message to provide feedback on the successful completion of the first message, thus completing an independent "transmission-feedback" closed loop.

[0528] Because the payload length of the first message is shorter than that of the first RRC message, the transmission of the first message is less prone to errors, and the transmission resources for the first message are also less than those for the first RRC message. This allows the network to prioritize the transmission of a portion of the first RRC message with a lower block error rate and fewer transmission resources, ensuring the reliability and resource efficiency of this portion of the transmission. 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, enabling timely execution of some RRC-related processing.

[0529] Compared to the situation where the network might not be able to determine the optimal transmission strategy for the first RRC message based on the latest channel information before direct transmission, this application requires feedback on the successful completion of the first message via a second message. Therefore, this application can provide the network with the latest channel information through 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, achieving dynamic adjustment of the transmission strategy and ensuring transmission reliability, resource efficiency, and link adaptability during subsequent transmission of the second segment.

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

[0531] The following provides examples illustrating other relevant aspects of this embodiment.

[0532] Optionally, the above method embodiments can be applied to or incorporated into terminal devices. That is, the executing entity of the above method embodiments can be a terminal device, a chip, a chip module, or a module, etc., without specific limitations.

[0533] Optionally, the above method embodiments can be applied to network devices or applied within network devices. That is, the executing entity of the above method embodiments can be a network device, a chip, a chip module, or a module, etc., without specific limitations.

[0534] This application also provides a communication system, including the aforementioned terminal device and network device.

[0535] This 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 embodiments.

[0536] This application also provides a chip module, including a transceiver component and a chip. The chip includes 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 embodiments.

[0537] This application also provides a computer-readable storage medium storing a computer program or instructions that, when executed, implement the steps described in the above method embodiments.

[0538] This application also provides a computer program product, including a computer program or instructions that, when executed, implement the steps described in the above method embodiments.

[0539] It should be noted that, for the sake of simplicity, the above embodiments are all described as a series of actions. Those skilled in the art should understand that this application is not limited to the described order of actions, as some steps in the embodiments of this application can be performed in other orders or simultaneously. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are preferred embodiments, and the actions, steps, modules, or units involved are not necessarily essential to the embodiments of this application.

[0540] In the above embodiments, the descriptions of each embodiment in this application have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions in other embodiments.

[0541] The steps of the methods or algorithms described in the embodiments of this application can be implemented in hardware or by a processor executing software instructions. The software instructions can consist of corresponding software modules, which can be stored in RAM, flash memory, ROM, EPROM, electrically erasable programmable read-only memory (EEPROM), registers, hard disk, portable hard disk, read-only optical disk (CD-ROM), or any other form of storage medium well known in the art. An exemplary storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and storage medium can reside in an ASIC. Furthermore, the ASIC can reside in a terminal device or management device. Alternatively, the processor and storage medium can exist as discrete components in the terminal device or management device.

[0542] Those skilled in the art will recognize that, in one or more of the examples above, the functions described in the embodiments of this application can be implemented, in whole or in part, by software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. This computer program product includes one or more computer instructions. When these computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. 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 via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device such as a server or data center that integrates one or more available media. The available media can be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., digital video discs (DVDs)), or semiconductor media (e.g., solid-state disks (SSDs)).

[0543] The modules or units included in the various devices and products described in the above embodiments can be software modules or units, hardware modules or units, or a combination of both. For example, for devices and products applied to or integrated into a chip, all modules or units can be implemented using hardware methods such as circuits, or at least some modules or units can be implemented using software programs that run on a processor integrated within the chip, while the remaining (if any) modules or units can be implemented using hardware methods such as circuits. For devices and products applied to or integrated into a chip module, all modules or units can be implemented using hardware methods such as circuits. Different modules or units can be located in the same component (e.g., chip, circuit module, etc.) or different components of the chip module, or at least some modules or units can be implemented using hardware methods such as circuits. The implementation is achieved through a software program that runs on a processor integrated within the chip module. The remaining modules or units (if any) can be implemented using hardware methods such as circuits. For various devices or products applied to or integrated into terminal equipment, each of its modules or units can be implemented using hardware methods such as circuits. Different modules or units can be located in the same component (e.g., chip, circuit module, etc.) or different components within the terminal equipment. Alternatively, at least some modules or units can be implemented using a software program that runs on a processor integrated within the terminal equipment. The remaining modules or units (if any) can be implemented using hardware methods such as circuits.

[0544] The specific embodiments described above further illustrate the purpose, technical solution, and beneficial effects of the embodiments of this application. It should be understood that the above descriptions are merely specific embodiments of the embodiments of this application and are not intended to limit the protection scope of the embodiments of this application. Any modifications, equivalent substitutions, improvements, etc., made on the basis of the technical solutions of the embodiments of this application should be included within the protection scope of the embodiments of this application.

Claims

1. A communication method characterized by comprising: Comprising: receiving a first message, the first message being a radio resource control (RRC) message containing a first segment in a first RRC message; sending a second message, the second message being an RRC message for determining successful completion of the first message; wherein a payload of the first RRC message is split into the first segment and a second segment, the first segment being part fields in the payload of the first RRC message, and the second segment being remaining fields in the payload of the first RRC message except the first segment; wherein the first RRC message comprises an RRC reconfiguration message, the first segment comprises a radio bearer configuration field in the RRC reconfiguration message, and the second segment comprises a secondary cell group field and a measurement configuration field in the RRC reconfiguration message.

2. The method of claim 1, wherein, The length of the first segment is less than the length of the second segment.

3. The method of claim 1, wherein, The first message comprises 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 identification field is used to identify an 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-key extension field is used to carry non-key configuration information of the first message.

4. The method of claim 3, wherein, The first non-key extension field contains a first segment serial number field and / or a first last segment field; The first segment serial number field indicates a serial number of the first segment in segments split from the payload of the first RRC message; The first last segment field indicates that the first segment is not the last segment in the segments split from the payload of the first RRC message.

5. The method of claim 1, wherein, The first RRC message is an RRC message transmitted by a network after a terminal device successfully accesses a cell; or The first RRC message is an RRC message transmitted by a network after a terminal device successfully enters an RRC connected state; or The first RRC message is an RRC message transmitted by a network after a terminal device successfully performs random access.

6. The method of claim 1, wherein, The first message is transmitted K1 times, K1 being an integer greater than or equal to 1.

7. The method of claim 6, wherein, K1 is a value specified by a protocol or a default setting; or K1 is a value determined based on a number of repeated transmissions of a message 4 in a random access procedure; or K1 is a value determined based on channel information corresponding to a message 3 in a random access procedure.

8. The method of claim 1, wherein, Further comprising: sending device capability information, the device capability information indicating that a terminal device supports payload split processing of the first RRC message.

9. The method of claim 1, wherein, Further comprising: receiving a third message, the third message being an RRC message containing the second segment; sending a fourth message, the fourth message being an RRC message for determining successful completion of integration of the first segment and the second segment.

10. The method of claim 9, wherein, The third message comprises 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 identification field is used to identify an 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-key extension field is used to carry non-key configuration information of the third message.

11. The method of claim 10, wherein, The second non-key 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 segments obtained by splitting a payload of the first RRC message. The second last segment field indicates that the second segment is the last segment in the segments obtained by splitting the payload of the first RRC message.

12. The method of claim 9, wherein, The third message is repeatedly transmitted K2 times, where K2 is an integer greater than or equal to 1.

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

14. A communication method, comprising: Comprise: sending a first message, the first message being an RRC message containing a first segment in a first radio resource control (RRC) message; receiving a second message, the second message being an RRC message used to determine successful completion of the first message; wherein a payload of the first RRC message is split into the first segment and a second segment, the first segment being a part of fields in the payload of the first RRC message, and the second segment being remaining fields in the payload of the first RRC message except the first segment field; wherein the first RRC message comprises an RRC reconfiguration message, the first segment comprises a radio bearer configuration field in the RRC reconfiguration message, and the second segment comprises a secondary cell group field and a measurement configuration field in the RRC reconfiguration message.

15. The method of claim 14, wherein, The length of the first segment is less than the length of the second segment.

16. The method of claim 14, wherein, 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 identification field is used to identify an 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-key extension field is used to carry non-key configuration information of the first message.

17. The method of claim 16, wherein, The first non-key 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 segments obtained by splitting a payload of the first RRC message. The first last segment field indicates that the first segment is not the last segment in the segments obtained by splitting the payload of the first RRC message.

18. The method of claim 14, wherein, Further comprise: receiving device capability information, the device capability information indicating that a terminal device supports payload splitting processing of the first RRC message.

19. The method of claim 14, wherein, Further comprise: sending a third message, the third message being an RRC message containing the second segment; receiving a fourth message, the fourth message being an RRC message used to determine successful completion of integration of the first segment and the second segment.

20. The method of claim 19, wherein, The third message comprises 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 identification field is used to identify an RRC transaction corresponding to the third message; The second non-key extension field is used to carry non-key configuration information of the third message.

21. The method of claim 20, wherein, The second non-key extension field comprises a second segment serial number field and / or a second last segment field; The second segment serial number field indicates a serial number of the second segment in segments segmented from a payload of the first RRC message; The second last segment field indicates that the second segment is the last segment in the segments segmented from the payload of the first RRC message.

22. A communications device, characterized by Comprise: The receiving unit is configured to receive a first message, the first message being a radio resource control (RRC) message containing a first segment in a first RRC message; The sending unit is configured to send a second message, the second message being an RRC message used to determine that the first message is successfully completed; The payload of the first RRC message is segmented into the first segment and a second segment, the first segment being part of fields in the payload of the first RRC message, and the second segment being remaining fields in the payload of the first RRC message except the first segment; The first RRC message comprises an RRC reconfiguration message, the first segment comprises a radio bearer configuration field in the RRC reconfiguration message, and the second segment comprises a secondary cell group field and a measurement configuration field in the RRC reconfiguration message.

23. A communications device, characterized by Comprise: The sending unit is configured to send a first message, the first message being a radio resource control (RRC) message containing a first segment in a first RRC message; The receiving unit is configured to receive a second message, the second message being an RRC message used to determine that the first message is successfully completed; The payload of the first RRC message is segmented into the first segment and a second segment, the first segment being part of fields in the payload of the first RRC message, and the second segment being remaining fields in the payload of the first RRC message except the first segment; The first RRC message comprises an RRC reconfiguration message, the first segment comprises a radio bearer configuration field in the RRC reconfiguration message, and the second segment comprises a secondary cell group field and a measurement configuration field in the RRC reconfiguration message.

24. A terminal device comprising a processor, a memory, and a computer program or instructions stored on the memory, wherein, The processor executes the computer program or instruction to implement the method in any one of claims 1-13.

25. A network device comprising a processor, a memory, and a computer program or instructions stored on the memory, wherein, The processor executes the computer program or instruction to implement the method in any one of claims 14-21.

26. A chip comprising a processor, wherein: The processor is configured to implement the method in any one of claims 1-13 or 14-21.

27. A computer-readable storage medium, characterized in that, The computer program or instruction stored in the computer readable storage medium is executed to implement the method in any one of claims 1-13 or 14-21.

Images