Patent Description:
In a fifth-generation (<NUM>-th Generation, <NUM>) mobile communications technology system or a long term evolution (Long Term Evolution, LTE) system, an air interface capability of a terminal, such as user equipment (User Equipment, UE), is reported through a radio resource control (Radio Resource Control, RRC) layer. In cases in which, for example, a quantity of frequency band combinations increases, capabilities of combined frequency bands vary, or both multiple-input multiple-output (Multiple-Input Multiple-Output, MIMO) and radio frequency (Radio Frequency, RF) capabilities are different, capability reporting for UE may need to occupy very large space. For example, during <NUM> air interface capability reporting for UE, a maximum value of <NUM> bytes (byte) may be reached.

In addition, a new radio (New Radio, NR) system has channel state information-reference signal (Channel State Information-Reference Signal, CSI-RS) related measurement configuration information and random access channel (Random Access Channel, RACH) configuration information. When the CSI-RS uses excessive resources, a corresponding RRC message is also excessively large.

Currently, a processing mechanism for an RRC layer entity is directly sending a generated RRC message to a packet data convergence protocol (Packet Data Convergence Protocol, PDCP) layer entity as an RRC protocol data unit (Protocol Data Unit, PDU), that is, a PDCP service data unit (Service Data Unit, SDU). However, a maximum size of a PDCP SDU is, for example, <NUM> bytes (byte) in a <NUM> (<NUM>-th Generation) system, and <NUM> bytes in a <NUM> system.

In this case, when the RRC message is excessively large, a limit of the PDCP SDU is exceeded, and excessively large burden is imposed on an RRC buffer, affecting smooth proceeding of a corresponding communication procedure.

<NPL>)) relates to segmentation of system information blocks performed by the RRC layer.

<CIT> Al relates to a method and apparatus for redundantly transmitting dual- or multi-connectivity based-data.

Embodiments of this disclosure provide a data transmission method and a communications device, to resolve an existing problem that when an RRC message is excessively large, a limit of a PDCP SDU is exceeded, and excessively large burden is imposed on an RRC buffer.

In the embodiments of this disclosure, the plurality of RRC segments are generated by using the RRC segmentation function, where each of the plurality of RRC segments carries partial data content of the RRC message generated by the sender communications device, and all data content of the RRC message is carried in the plurality of RRC segments; and the plurality of RRC segments are sent to the receiver communications device. In this way, the RRC message can be segmented. Therefore, when the RRC message is excessively large, adaptation to a PDCP SDU can be implemented, to reduce burden on an RRC buffer, and complete transmission of the RRC message, thereby ensuring smooth proceeding of a corresponding communication procedure.

To describe the technical solutions in the embodiments of this disclosure more clearly, the following briefly describes the accompanying drawings required for describing the embodiments of this disclosure. Apparently, the accompanying drawings in the following descriptions show only some embodiments of this disclosure, and a person of ordinary skill in the art may still derive other drawings from these accompanying drawings without creative efforts.

To describe the technical solutions in the embodiments of this disclosure more clearly, the following briefly describes the accompanying drawings required for describing the embodiments of this disclosure. Apparently, the accompanying drawings in the following descriptions show only some embodiments of this disclosure, and a person of ordinary skill in the art may still derive other drawings from these accompanying drawings without creative efforts. The present invention is defined by the attached independent claims. Advantageous embodiments are described in the attached dependent claims. Embodiments and/or examples mentioned in the description that do not fall under the scope of the claims are useful for understanding the present invention.

First, it should be noted that, to resolve a problem in a related technology that when an RRC message is excessively large, a limit of a PDCP SDU is exceeded, and excessively large burden is imposed on an RRC buffer, an RRC segmentation function is introduced in the embodiments of this disclosure. The RRC segmentation function may be implemented by an RRC layer entity, or may be implemented by a new protocol layer entity. In this way, an excessively large RRC message may be segmented by using the introduced RRC segmentation function, to obtain a plurality of RRC segments. The plurality of RRC segments may carry all data content of the corresponding RRC message. Each of the plurality of RRC segments may carry partial data content of the corresponding RRC message, and each RRC segment is transferred to a PDCP layer entity as a PDCP SDU. Therefore, when the RRC message is excessively large, adaptation to a PDCP SDU can be implemented, to reduce burden on an RRC buffer, and complete transmission of the RRC message, thereby ensuring smooth proceeding of a corresponding communication procedure.

During specific implementation, after a sender communications device (which may be referred to as a sender for short) generates an RRC message, a corresponding transmission procedure may be sequentially as follows: from a sender RRC layer entity to a sender PDCP layer entity, then to a sender RLC layer entity, then to a sender MAC layer entity, then to a sender PHY layer entity, then to a receiver (that is, a receiver communications device) PHY layer entity, then to a receiver MAC layer entity, then to a receiver RLC layer entity, then to a receiver PDCP layer entity, and finally to a receiver RRC layer entity. In this way, an RRC segment generated by using the RRC segmentation function may exist in an RRC PDU form for the sender, and may be received by a receiver as a PDCP SDU, that is, the RRC PDU may be equivalent to the PDCP SDU.

In a wireless communications system, a dual connectivity (Dual Connectivity, DC) architecture may be used for a terminal, and correspondingly includes two cell groups: a master cell group (Master Cell Group, MCG) and a secondary cell group (Secondary Cell Group, SCG). The MCG corresponds to a network-side master node (Master Node, MN), and the SCG corresponds to a network-side secondary node (secondary node, SN). The MCG may include a primary cell PCell and a secondary cell SCell, and the SCG may include a primary secondary cell PSCell and a secondary cell SCell. The PCell and the PSCell may also be collectively referred to as an SpCell. Bearer types may include a signaling radio bearer (Signaling Radio Bearer, SRB) and a data radio bearer (Data Radio Bearers, DRB). An MCG SRB (or DRB) transmits or receives data by using only the MCG. An SCG SRB (or DRB) transmits or receives data by using only the SCG. A split SRB (or DRB) transmits or receives data by using both the MCG and the SCG.

When the DC architecture is used, an LTE cell may serve as an MCG cell, and an NR (New RAT, new radio, namely, <NUM>) cell may serve as an SCG cell. In the DC architecture, a core network to which the terminal is connected is an LTE core network, for example, an evolved packet core (Evolved Packet Core, EPC). In the DC architecture, an NR configuration may be used for a PDCP layer entity corresponding to the MCG (that is, the PDCP layer entity is configured to an NR PDCP layer entity), and LTE configurations are still used for other configurations in the MCG, including configurations of the RLC layer entity, the MAC layer entity, and the like.

The following describes a data transmission method of this disclosure with reference to the embodiments and the accompanying drawings.

Referring to <FIG>, an embodiment of this disclosure provides a data transmission method, applied to a sender communications device. The sender communications device may be either a terminal or a network device. The method includes the following steps <NUM> and <NUM>.

Step <NUM>: Generate a plurality of RRC segments by using an RRC segmentation function of an RRC layer entity of the sender communications device or an RRC segmentation function of a new protocol layer entity.

For the sender, the RRC segment may exist in an RRC PDU form. Each of the plurality of RRC segments carries partial data content of an RRC message generated by the sender communications device. All data content of the RRC message may be carried in the plurality of RRC segments. The generating a plurality of RRC segments may be understood as segmenting the generated RRC message by using the RRC segmentation function of the RRC layer entity or the new protocol layer entity of the sender communications device, to obtain the plurality of RRC segments. That is, with the RRC segmentation function, the generated RRC message may be divided into the plurality of RRC messages for transmission.

It can be understood that, during specific implementation, in an uplink data transmission procedure, a sender communications device is a terminal, and a receiver communications device is a network device; and in a downlink data transmission procedure, a sender communications device is a network device, and a receiver communications device is a terminal.

For example, if the sender communications device is UE <NUM>, and an RRC message generated by the UE <NUM> occupies <NUM> bytes (which exceeds a limit of a PDCP SDU), the UE <NUM> may segment the RRC message into an RRC PDU <NUM> (which for example occupies <NUM> bytes) and an RRC PDU <NUM> (which for example occupies <NUM> bytes) by using the RRC segmentation function of the RRC layer entity (or the new protocol layer entity), or segment the RRC message into an RRC PDU <NUM> (which for example occupies <NUM> bytes), an RRC PDU <NUM> (which for example occupies <NUM> bytes), and an RRC PDU <NUM> (which for example occupies <NUM> bytes), to adapt to the PDCP SDU, and complete transmission of the RRC message.

It should be noted that segmenting the message into two segments or three segments is merely used as an example in the foregoing embodiment, and during specific implementation, the message may be alternatively segmented into four segments or the like. This is not limited in this embodiment of this disclosure. For how to segment the RRC message, that is, how to choose bytes occupied by an RRC segment, the sender may make a choice as required, or may make a choice according to a preset rule.

Step <NUM>: Send the plurality of RRC segments to a receiver communications device.

In this way, after receiving the plurality of RRC segments, the receiver communications device may reassemble the plurality of RRC segments, to obtain the complete RRC message.

In the data transmission method in this embodiment of this disclosure, the plurality of RRC segments are generated by using the RRC segmentation function, where each of the plurality of RRC segments carries partial data content of the RRC message generated by the sender communications device; and the plurality of RRC segments are sent to the receiver communications device. In this way, the RRC message can be segmented. Therefore, when the RRC message is excessively large, adaptation to a PDCP SDU can be implemented, to reduce burden on an RRC buffer, and complete transmission of the RRC message, thereby ensuring smooth proceeding of a corresponding communication procedure.

In a specific embodiment of this disclosure, optionally, packet assembly information of the RRC segments may include reassembly indication information, and the reassembly indication information is used for the receiver communications device to reassemble the plurality of received RRC segments, to obtain the complete RRC message. The packet assembly information may be an information element in a packet header form or another form.

Further, the reassembly indication information may include at least one of the following:
segmentation information (segmentation info, SI), a sequence number (sequence number, SN), an segmentation offset (segmentation offset, SO), and priority indication information.

Optionally, the segmentation information may be used to indicate a location of a corresponding RRC segment in an RRC message, that is, a location, in all data content of the RRC message, of partial data content of the RRC message that is carried in the corresponding RRC segment. In this way, the receiver may determine a location of an RRC segment in a corresponding RRC message based on the segmentation information, to complete reassembly of the corresponding RRC message.

For example, during specific implementation, the segmentation information may include X bits, and a typical value of X may be <NUM>. The segmentation information may be used to indicate that the corresponding RRC segment is at the first (first), in the middle (middle), or at the last (last) of the RRC message. A meaning of an X-bit field in another form may be different from this. In addition, when no segmentation is performed, the segmentation information may alternatively indicate that an RRC message corresponding to a related RRC PDU is not segmented.

Optionally, the sequence number may be used to indicate a sequence number of an RRC message corresponding to a related RRC segment. In this way, the receiver may determine, based on the sequence number, RRC segments of a same RRC message, to complete reassembly of the RRC message.

It should be noted that, when an RRC duplication (duplication) function is enabled, the reassembly indication information needs to include the sequence number, so that the receiver identifies RRC segments of a same RRC message. For example, during specific implementation, the sequence number may include Y bits, and a typical value of Y may be <NUM> or <NUM>.

Optionally, the segmentation offset may be used to indicate an offset location of a corresponding RRC segment in an RRC message, that is, an offset location, in all data content of the RRC message, of partial data content of the RRC message that is carried in the corresponding RRC segment. It should be noted that, when PDCPs are transferred out of order, the reassembly indication information needs to include the segmentation offset, to differentiate locations, in an RRC message, of RRC segments at similar locations. For example, during specific implementation, the segmentation offset may include P bits, and a typical value of P may be <NUM> or <NUM>. Alternatively, the segmentation offset may be in a segment number form. A specific form of an offset is not limited in this disclosure. If the segment number form is used, Z bits may be used.

For example, it is assumed that an RRC message generated by UE is segmented into an RRC PDU <NUM>, an RRC PDU <NUM>, an RRC PDU <NUM>, and an RRC PDU <NUM>, and respective SI indicates that the RRC PDU <NUM> is at the first of the RRC message, the RRC PDU <NUM> is in the middle of the RRC message, the RRC PDU <NUM> is in the middle of the RRC message, and the RRC PDU <NUM> is at the last of the RRC message. In this case, after receiving the RRC PDU <NUM> and the RRC PDU <NUM>, the receiver cannot differentiate sequential locations of the RRC PDU <NUM> and the RRC PDU <NUM> (but only knows that the RRC PDU <NUM> and the RRC PDU <NUM> are in the middle of the RRC message). However, the sequential locations of the RRC PDU <NUM> and the RRC PDU <NUM> can be differentiated based on an offset location indicated by an SO, that is, the RRC PDU <NUM> is located before the RRC PDU <NUM>, so as to complete reassembly of the RRC message.

Optionally, the priority indication information may be used to indicate a reassembly priority of an RRC message corresponding to a related RRC segment, to complete reassembly of the RRC message based on the priority. For example, if there are a plurality of RRC messages that need to be reassembled, the plurality of RRC messages may be sequentially reassembled based on priorities according to priority indication information included in RRC segments corresponding to the RRC messages.

In a specific embodiment of this disclosure, the packet assembly information of the RRC segments may further include a reserved bit (R bit). The reserved bit may be used when a new function is subsequently added. To ensure that the packet assembly information occupies an integer quantity of bytes (byte align), a location with less than <NUM> byte may be filled with a reserved bit.

In a specific embodiment of this disclosure, optionally, when the sender communications device is a terminal, the new protocol layer entity may be one of the following cases:
per-SRB (per-SRB), per-DRB (per-DRB), per-terminal (per-UE), and per-cell group (per-cell group).

Alternatively, when the sender communications device is a network device, the new protocol layer entity may be one of the following cases:
per-SRB (per-SRB), per-DRB (per-DRB), and per-cell group (per-cell group).

The per-SRB may be understood as follows: procedures such as establishment and release of the new protocol layer entity are affected by procedures such as establishment and release of a related SRB. For example, when an SRB is released, a corresponding new protocol layer entity also needs to be released, or each SRB corresponds to one new protocol layer entity.

The per-DRB may be understood as follows: procedures such as establishment and release of the new protocol layer entity are affected by procedures such as establishment and release of a related DRB. For example, when a DRB is released, a corresponding new protocol layer entity also needs to be released, or each DRB corresponds to one new protocol layer entity.

The per-UE may be understood as follows: A new protocol layer entity is retained by a terminal itself, and the terminal may have one or more new protocol layer entities that are not affected by procedures such as establishment and release of an SRB (or a DRB), or network-side configurations.

The per-cell group may be understood as follows: A new protocol layer entity is affected by DC configurations of a terminal. For example, an MCG may correspond to a new protocol layer entity, and an SCG may correspond to a new protocol layer entity.

In a specific embodiment of this disclosure, based on the foregoing cases of the new protocol layer entity, the new protocol layer entity may be established, released, reset, and/or the like in different manners. Descriptions are shown below.

Optionally, when the sender communications device is a terminal, and the new protocol layer entity is per-cell group, the method may further include:.

Alternatively, when the sender communications device is a network device, and the new protocol layer entity is per-cell group, the method may further include:.

The resetting the new protocol layer entity may be understood as follows: Reassembly indication information, such as SI, an SN, and/or an SO, corresponding to the new protocol layer entity is reset to zero, or is reset to an initial value.

Optionally, when the sender communications device is a terminal, and the new protocol layer entity is per-SRB, the method may further include:.

Alternatively, when the sender communications device is a network device, and the new protocol layer entity is per-SRB, the method may further include:.

Optionally, when the sender communications device is a terminal, and the new protocol layer entity is per-DRB, the method may further include:.

Alternatively, when the sender communications device is a network device, and the new protocol layer entity is per-DRB, the method may further include:.

It can be understood that a new protocol layer entity of the terminal corresponds to a new protocol layer entity of the network device. For example, if the network device needs to release the new protocol layer entity (a sending entity) of the network device, the network device needs to first send signaling to the terminal to release the new protocol layer entity (a receiving entity) of the terminal, and then release the new protocol layer entity of the network device.

In a specific embodiment of this disclosure, an RRC segmentation function (which may correspond to an RRC layer entity or a new protocol layer entity) of the terminal may be activated by using activation signaling of the network device, or may be deactivated by using deactivation signaling of the network device.

Optionally, when the sender communications device is a terminal, the method may further include:.

Further, the activation signaling may be in at least one of the following forms:
a MAC control element (Control Element, CE), downlink control information (Downlink Control Information, DCI), and an RRC message.

The deactivation signaling may be in at least one of the following forms:
a MAC CE, DCI, and an RRC message.

Further, an activation condition (to be specific, when the condition is met, the network device may send activation signaling to the terminal) for the RRC segmentation function may be at least one of the following:.

Optionally, the capability-related information may include at least one of the following:.

Further, a deactivation condition (to be specific, when the condition is met, the network device may send deactivation signaling to the terminal) for the RRC segmentation function may be at least one of the following:.

It can be understood that duration of the preset time may be an absolute value, or may be indicated by maintaining a timer (timer). A determining condition for the duration or the timer may be one or any combination of the following: An agreement is made in a protocol in advance; the network device (for example, a base station) performs configuration or re-configuration; or the network device (for example, a base station) negotiates with the terminal. The preset time included in the foregoing deactivation condition may be the same or different in different deactivation conditions based on specific cases. This is not limited in this embodiment of this disclosure.

The first preset threshold may be one of the following cases:.

In a specific embodiment of this disclosure, optionally, if the RRC segmentation function is completed by the new protocol layer entity, activating or deactivating the RRC segmentation function by the network device may also be performed by establishing, reconfiguring, or releasing a corresponding protocol layer entity.

Optionally, when the RRC layer entity or the new protocol layer entity that carries the RRC segmentation function is per-SRB (that is, configured in a per-SRB manner), the activation signaling may include activation indication information for a related SRB, and the deactivation signaling may include deactivation indication information for a related SRB; or.

According to the claimed invention, the new protocol layer entity is one of the following cases: per-signaling radio bearer SRB, per-data radio bearer DRB; the RRC layer entity is one of the following cases: per-SRB, per-DRB.

In a specific embodiment of this disclosure, the RRC segmentation function of the RRC layer entity or the new protocol layer entity may take effect only for a preset RRC message (that is, a specific RRC message).

Optionally, when the sender communications device is a terminal, the corresponding RRC segmentation function may be specific to at least one of the following RRC messages:.

The second preset threshold may be one of the following cases:.

Alternatively, when the sender communications device is a network device, the corresponding RRC segmentation function may be specific to at least one of the following RRC messages:.

The third preset threshold may be one of the following cases:.

It can be understood that, during specific implementation, the first preset threshold, the second preset threshold, and the third preset threshold may be the same or different based on specific cases.

Referring to <FIG>, an embodiment of this disclosure provides a data transmission method, applied to a receiver communications device. The receiver communications device may be either a terminal or a network device. The method includes the following steps <NUM> and <NUM>.

Step <NUM>: Receive a plurality of RRC segments from a sender communications device.

For the receiver, the RRC segment may be received as a PDCP SDU. Each of the plurality of RRC segments carries partial data content of an RRC message generated by the sender communications device. All data content of the RRC message may be carried in the plurality of RRC segments.

Step <NUM>: Reassemble the plurality of RRC segments by using an RRC reassembly function of an RRC layer entity of the receiver communications device or an RRC reassembly function of a new protocol layer entity, to obtain the complete RRC message.

In the data transmission method in this embodiment of this disclosure, the RRC message can be segmented. Therefore, when the RRC message is excessively large, adaptation to a PDCP SDU can be implemented, to reduce burden on an RRC buffer, and complete transmission of the RRC message, thereby ensuring smooth proceeding of a corresponding communication procedure.

In a specific embodiment of this disclosure, optionally, when the receiver communications device is a terminal, the new protocol layer entity is one of the following cases:.

Optionally, when the receiver communications device is a terminal, and the new protocol layer entity is per-cell group, the method further includes:.

Alternatively, when the receiver communications device is a network device, and the new protocol layer entity is per-cell group, the method further includes:.

Optionally, when the receiver communications device is a terminal, and the new protocol layer entity is per-SRB or per-DRB, the method further includes:.

Alternatively, when the receiver communications device is a network device, and the new protocol layer entity is per-SRB or per-DRB, the method further includes:.

Optionally, when the receiver communications device is a terminal, the method further includes:.

It can be understood that an RRC segmentation function of a sender corresponds to an RRC reassembly function of a receiver. For example, when activating an RRC segmentation function of the terminal by using activation signaling, the network device may also correspondingly activate an RRC reassembly function of the network device; or when deactivating an RRC segmentation function of the terminal by using deactivation signaling, the network device may also correspondingly deactivate an RRC reassembly function of the network device; or when activating an RRC reassembly function of the terminal by using activation signaling, the network device may also correspondingly activate an RRC segmentation function of the network device; or when deactivating an RRC reassembly function of the terminal by using deactivation signaling, the network device may also correspondingly deactivate an RRC segmentation function of the network device. In addition, during specific implementation, the RRC reassembly function of the terminal may alternatively not need to be activated by the network device, but is implemented by the terminal.

Optionally, when the RRC layer entity or the new protocol layer entity that carries the RRC reassembly function is per-SRB, the activation signaling includes activation indication information for a related SRB, and the deactivation signaling includes deactivation indication information for a related SRB; or.

Optionally, when the receiver communications device is a network device, the method further includes:.

Optionally, an activation condition for the foregoing RRC segmentation function (which may belong to the RRC layer entity, or may belong to the new protocol layer entity) is at least one of the following:.

Optionally, a deactivation condition for the foregoing RRC segmentation function (which may belong to the RRC layer entity, or may belong to the new protocol layer entity) is at least one of the following:.

The foregoing embodiment describes the data transmission method of this disclosure. The following describes a communications device of this disclosure with reference to the embodiments and the accompanying drawings.

Referring to <FIG>, an embodiment of this disclosure further provides a communications device <NUM>. The communications device <NUM> is a sender. The communications device <NUM> may be either a terminal or a network device. The communications device <NUM> may include:.

In this embodiment of this disclosure, the RRC message can be segmented. Therefore, when the RRC message is excessively large, adaptation to a PDCP SDU can be implemented, to reduce burden on an RRC buffer, and complete transmission of the RRC message, thereby ensuring smooth proceeding of a corresponding communication procedure.

In this embodiment of this disclosure, optionally, when the communications device <NUM> is the terminal, the new protocol layer entity is one of the following cases:.

Optionally, when the communications device <NUM> is the terminal, and the new protocol layer entity is per-cell group, the communications device <NUM> further includes:.

Alternatively,
when the communications device <NUM> is the network device, and the new protocol layer entity is per-cell group, the communications device <NUM> further includes:.

Optionally, when the communications device <NUM> is the terminal, and the new protocol layer entity is per-SRB or per-DRB, the communications device <NUM> further includes:.

Alternatively, when the communications device <NUM> is the network device, and the new protocol layer entity is per-SRB or per-DRB, the communications device <NUM> further includes:.

Optionally, when the communications device <NUM> is the terminal, the communications device <NUM> further includes:.

Optionally, an activation condition for the RRC segmentation function is at least one of the following:.

Optionally, a deactivation condition for the RRC segmentation function is at least one of the following:.

Optionally, the activation signaling is in at least one of the following forms:.

Optionally, when the RRC layer entity or the new protocol layer entity that carries the RRC segmentation function is per-SRB, the activation signaling includes activation indication information for a related SRB, and the deactivation signaling includes deactivation indication information for a related SRB; or.

Optionally, when the communications device <NUM> is the terminal, the RRC segmentation function is specific to at least one of the following RRC messages:.

Alternatively, when the communications device <NUM> is the network device, the RRC segmentation function is specific to at least one of the following RRC messages:.

Referring to <FIG>, an embodiment of this disclosure further provides a communications device <NUM>. The communications device <NUM> is a receiver. The communications device <NUM> may be either a terminal or a network device. The communications device <NUM> may include:.

Alternatively,
when the communications device <NUM> is the network device, and the new protocol layer entity is per-SRB the communications device <NUM> further includes:.

Optionally, when the communications device <NUM> is the network device, the communications device <NUM> may further include:.

Further, optionally, an activation condition for the RRC segmentation function is at least one of the following:.

Further, optionally, a deactivation condition for the RRC segmentation function is at least one of the following:.

In addition, an embodiment of this disclosure further provides a communications device, including a processor, a memory, and a program that is stored in the memory and capable of running on the processor. When the program is executed by the processor, the processes in the foregoing embodiments of the data transmission method are implemented, and a same technical effect can be achieved. To avoid repetition, details are not described herein again. Optionally, the communications device may be a sender or a receiver, or may be a terminal or a network device.

Specifically, <FIG> is a schematic diagram of a hardware structure of a terminal for implementing the embodiments of this disclosure. The terminal <NUM> includes but is not limited to components such as a radio frequency unit <NUM>, a network module <NUM>, an audio output unit <NUM>, an input unit <NUM>, a sensor <NUM>, a display unit <NUM>, a user input unit <NUM>, an interface unit <NUM>, a memory <NUM>, a processor <NUM>, and a power supply <NUM>. A person skilled in the art may understand that the terminal structure shown in <FIG> does not constitute a limitation to the terminal. The terminal may include more or fewer components than those shown in the figure, or some components may be combined, or there may be a different component layout. In this embodiment of this disclosure, the terminal includes, but is not limited to, a mobile phone, a tablet computer, a notebook computer, a palmtop computer, an in-vehicle terminal, a wearable device, a pedometer, and the like.

Optionally, when the terminal <NUM> is a sender, the processor <NUM> is configured to generate a plurality of RRC segments by using an RRC segmentation function of an RRC layer entity of the terminal <NUM> or an RRC segmentation function of a new protocol layer entity, where each of the plurality of RRC segments carries partial data content of an RRC message generated by the terminal <NUM>; and
the radio frequency unit <NUM> is configured to send the plurality of RRC segments to a network device.

Optionally, when the terminal <NUM> is a receiver, the radio frequency unit <NUM> is configured to receive a plurality of RRC segments from a network device, where each of the plurality of RRC segments carries partial data content of an RRC message generated by the network device; and reassemble the plurality of RRC segments by using an RRC reassembly function of an RRC layer entity of the terminal <NUM> or an RRC reassembly function of a new protocol layer entity, to obtain the complete RRC message.

It should be understood that, in this embodiment of this disclosure, the radio frequency unit <NUM> may be configured to send or receive a signal in an information sending/receiving or call procedure. Specifically, the radio frequency unit <NUM> receives downlink data from a base station and sends the downlink data to the processor <NUM> for processing; and sends uplink data to the base station. Usually, the radio frequency unit <NUM> includes but is not limited to an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like. In addition, the radio frequency unit <NUM> may further communicate with a network and another device by using a wireless communications system.

The terminal provides a user with wireless broadband Internet access by using the network module <NUM>, for example, helps the user send or receive an email, browse a web page, access streaming media, and the like.

The audio output unit <NUM> may convert audio data into an audio signal, and output the audio signal as sound, where the audio data is received by the radio frequency unit <NUM> or the network module <NUM>, or stored in the memory <NUM>. In addition, the audio output unit <NUM> may further provide audio output (for example, a call signal reception tone or a message reception tone) that is related to a specific function performed by the terminal <NUM>. The audio output unit <NUM> includes a loudspeaker, a buzzer, a phone receiver, and the like.

The input unit <NUM> is configured to receive an audio signal or a video signal. The input unit <NUM> may include a graphics processing unit (Graphics Processing Unit, GPU) <NUM> and a microphone <NUM>. The graphics processing unit <NUM> processes image data of a static picture or a video that is obtained by an image capture apparatus (for example, a camera) in a video capture mode or an image capture mode. A processed image frame may be displayed on the display unit <NUM>. An image frame processed by the graphics processing unit <NUM> may be stored in the memory <NUM> (or another storage medium), or may be sent by the radio frequency unit <NUM> or the network module <NUM>. The microphone <NUM> may receive a sound, and can process the sound into audio data. In a phone call mode, processed audio data may be converted, for output, into a format for transmission by the radio frequency unit <NUM> to a mobile communications base station.

The terminal <NUM> further includes at least one sensor <NUM>, for example, an optical sensor, a motion sensor, and another sensor. Specifically, the optical sensor includes an ambient light sensor and a proximity sensor. The ambient light sensor may adjust brightness of a display panel <NUM> based on intensity of ambient light. When the terminal <NUM> moves near an ear, the proximity sensor may disable the display panel <NUM> and/or backlight. As a motion sensor, an accelerometer sensor may detect for a value of an acceleration in various directions (there are usually three axes), may detect for a value and a direction of gravity when the terminal is still, and may be configured to recognize a posture of the terminal (for example, landscape/portrait mode switching, a related game, or magnetometer posture calibration), provide a function related to vibration recognition (for example, a pedometer or a keystroke), or the like. The sensor <NUM> may further include a fingerprint sensor, a pressure sensor, an iris sensor, a molecular sensor, a gyroscope, a barometer, a hygrometer, a thermometer, or an infrared sensor.

The display unit <NUM> is configured to display information entered by the user or information provided for the user. Optionally, the display panel <NUM> may be configured in a form of a liquid crystal display (Liquid Crystal Display, LCD), an organic light-emitting diode (Organic Light-Emitting Diode, OLED), or the like.

The user input unit <NUM> may be configured to receive entered numerical or character information, and generate key signal input that is related to a user setting and function control of the terminal. Specifically, the user input unit <NUM> includes a touch panel <NUM> and other input devices <NUM>. The touch panel <NUM> is also referred to as a touchscreen, and may collect a touch operation of the user on or near the touch panel (for example, an operation performed on or near the touch panel <NUM> by the user by using any appropriate object or accessory such as a finger or a stylus). The touch panel <NUM> may include two parts: a touch detection apparatus and a touch controller. The touch detection apparatus detects for a touch orientation of the user, detects for a signal brought by the touch operation, and transmits the signal to the touch controller. The touch controller receives touch information from the touch detection apparatus, converts the touch information into contact coordinates, sends the contact coordinates to the processor <NUM>, receives a command sent by the processor <NUM>, and executes the command. In addition, the touch panel <NUM> may be implemented in a plurality of types, for example, a resistive type, a capacitive type, an infrared type, and a surface acoustic wave. In addition to the touch panel <NUM>, the user input unit <NUM> may further include the other input devices <NUM>. Specifically, the other input devices <NUM> may include but are not limited to a physical keyboard, a function key (for example, a volume control key or a power on/off key), a track ball, a mouse, and a joystick.

Further, the touch panel <NUM> may cover the display panel <NUM>. After detecting a touch operation on or near the touch panel <NUM>, the touch panel <NUM> transmits the touch operation to the processor <NUM> to determine a type of a touch event. Then the processor <NUM> provides corresponding visual output on the display panel <NUM> based on the type of the touch event. In <FIG>, the touch panel <NUM> and the display panel <NUM> serve as two independent components to implement input and output functions of the terminal. However, in some embodiments, the touch panel <NUM> and the display panel <NUM> may be integrated to implement the input and output functions of the terminal. This is not specifically limited herein.

The interface unit <NUM> is an interface for connecting an external apparatus to the terminal <NUM>. For example, the external apparatus may include a wired or wireless headphone port, an external power supply (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting an apparatus with an identification module, an audio input/output (I/O) port, a video I/O port, or a headset port. The interface unit <NUM> may be configured to receive input (for example, data information and electric power) from the external apparatus, and transmit the received input to one or more elements in the terminal <NUM>; or may be configured to transmit data between the terminal <NUM> and the external apparatus.

The memory <NUM> may be configured to store software programs and various types of data. The memory <NUM> may mainly include a program storage region and a data storage region. The program storage region may store an operating system, an application program required by at least one function (for example, an audio play function or an image play function), and the like. The data storage region may store data (for example, audio data and a phone book) created based on usage of the mobile phone. In addition, the memory <NUM> may include a high-speed random access memory, or may include a non-volatile memory, for example, at least one magnetic disk storage device or a flash memory device, or another volatile solid-state storage device.

The processor <NUM> is a control center of the terminal, connects various parts of the entire terminal by using various interfaces and lines, and executes various functions and data processing of the terminal by running or executing a software program and/or a module stored in the memory <NUM> and invoking data stored in the memory <NUM>, so as to perform overall monitoring on the terminal. The processor <NUM> may include one or more processing units. Optionally, the processor <NUM> may integrate an application processor and a modem processor. The application processor mainly processes an operating system, a user interface, an application program, and the like. The modem processor mainly processes wireless communication. It can be understood that the modem processor may be alternatively not integrated in the processor <NUM>.

The terminal <NUM> may further include a power supply <NUM> (for example, a battery) that supplies power to each component. Optionally, the power supply <NUM> may be logically connected to the processor <NUM> by using a power management system, so as to implement functions such as charging management, discharging management, and power consumption management by using the power management system.

In addition, the terminal <NUM> may further include some functional modules that are not shown.

Specifically, <FIG> is a schematic diagram of a hardware structure of a network device for implementing the embodiments of this disclosure. The network device <NUM> includes but is not limited to a bus <NUM>, a transceiver <NUM>, an antenna <NUM>, a bus interface <NUM>, a processor <NUM>, and a memory <NUM>.

In this embodiment of this disclosure, the network device <NUM> further includes a program that is stored in the memory <NUM> and capable of running on the processor <NUM>.

Optionally, when the network device <NUM> is a sender, the following steps are implemented when the program is executed by the processor <NUM>:
generating a plurality of RRC segments by using an RRC segmentation function of an RRC layer entity of the network device <NUM> or an RRC segmentation function of a new protocol layer entity, where each of the plurality of RRC segments carries partial data content of an RRC message generated by the network device <NUM>; and sending the plurality of RRC segments to a terminal.

Optionally, when the network device <NUM> is a receiver, the following steps are implemented when the program is executed by the processor <NUM>:
receiving a plurality of RRC segments from a terminal, where each of the plurality of RRC segments carries partial data content of an RRC message generated by the terminal; and reassembling the plurality of RRC segments by using an RRC reassembly function of an RRC layer entity of the network device <NUM> or an RRC reassembly function of a new protocol layer entity, to obtain the complete RRC message.

The transceiver <NUM> is configured to send and receive data under control of the processor <NUM>.

In <FIG>, in a bus architecture (represented by the bus <NUM>), the bus <NUM> may include any quantity of interconnected buses and bridges, and the bus <NUM> connects various circuits that include one or more processors represented by the processor <NUM> and a memory represented by the memory <NUM>. The bus <NUM> may further connect various other circuits, such as a peripheral device, a voltage regulator, and a power management circuit. These are well-known in the art, and therefore are not further described in this specification. The bus interface <NUM> provides an interface between the bus <NUM> and the transceiver <NUM>. The transceiver <NUM> may be one element, or may be a plurality of elements, for example, a plurality of receivers and transmitters, and provides a unit for communicating with various other apparatuses on a transmission medium. Data processed by the processor <NUM> is transmitted on a wireless medium through the antenna <NUM>. Further, the antenna <NUM> receives data and transmits the data to the processor <NUM>.

The processor <NUM> is responsible for managing the bus <NUM> and general processing, and may further provide various functions, including timing, a peripheral interface, voltage regulation, power management, and other control functions. The memory <NUM> may be used to store data that is used by the processor <NUM> when the processor <NUM> performs an operation.

Optionally, the processor <NUM> may be a CPU, an ASIC, an FPGA, or a CPLD.

An embodiment of this disclosure further provides a computer-readable storage medium. The computer-readable storage medium stores a program. When the program is executed by a processor, the processes in the foregoing embodiments of the data transmission method are implemented, and a same technical effect can be achieved. To avoid repetition, details are not described herein again. For example, the computer-readable storage medium is a read-only memory (Read-Only Memory, ROM for short), a random access memory (Random Access Memory, RAM for short), a magnetic disk, or an optical disc.

It should be noted that, in this specification, the terms "include", "comprise", or any of their variants are intended to cover a non-exclusive inclusion, such that a process, a method, an article, or an apparatus that includes a list of elements not only includes those elements but also includes other elements that are not expressly listed, or further includes elements inherent to such process, method, article, or apparatus. In absence of more constraints, an element preceded by "includes a. " does not preclude the existence of other identical elements in the process, method, article, or apparatus that includes the element.

Claim 1:
A data transmission method, applied to a sender communications device (<NUM>), wherein the sender communications device (<NUM>) is a terminal, and the method comprises:
generating (<NUM>) a plurality of radio resource control RRC segments by using an RRC segmentation function of an RRC layer entity of the sender communications device (<NUM>) or an RRC segmentation function of a new protocol layer entity, wherein each of the plurality of RRC segments carries partial data content of an RRC message generated by the sender communications device (<NUM>);
sending (<NUM>) the plurality of RRC segments to a receiver communications device (<NUM>);
receiving activation signaling or deactivation signaling for the RRC segmentation function from a network device; and
activating the RRC segmentation function according to the activation signaling, or deactivating the RRC segmentation function according to the deactivation signaling,
characterised in that
the new protocol layer entity is one of the following cases:
per-signaling radio bearer SRB, per-data radio bearer DRB;
the RRC layer entity is one of the following cases:
per-SRB, per-DRB.