Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
In MTC communication, terminals may be divided into machine terminals (i.e., MTC devices) and terminals used by general users (for convenience of description, terminals used by general users are hereinafter referred to as general terminals). The machine terminals can be specifically vending machines, meter reading equipment and other equipment, and with the wide deployment of M2M application, the number of machine terminals also increases gradually, and the communication of a large number of machine terminals will affect the communication of the mobile phone terminal, for example, because the machine communication occupies more wireless resources, the service initiation success rate and the call quality of the mobile phone are reduced, and the like, so that the machine communication should be prevented from occupying too many wireless resources as much as possible to ensure the normal communication quality of a common terminal.
The embodiment of the invention provides a data processing method, a device and a system. The following are detailed below.
The first embodiment,
The present embodiment will be described from the perspective of the transmitting end, i.e., the machine terminal.
A method of data processing, comprising: the method comprises the steps of obtaining grouping information, generating MAC PDU and RLC PDU when the fact that the network needs to be accessed is determined, determining a public radio bearer corresponding to a group to which a machine terminal belongs according to the grouping information, and transmitting the MAC PDU and the RLC PDU to a public user plane entity through the determined public radio bearer. The grouping information comprises information such as a group identifier, a serial number of the machine terminal in the group, and a position of a public radio bearer configuration parameter corresponding to the group in the broadcast message; the common user plane entity is a common user plane entity established by the network side equipment for a group of machine terminals transmitting through the common radio bearer.
Referring to fig. 1, the specific process is as follows:
101. acquiring grouping information, wherein the grouping information comprises a group identification (ID, IDentity), a serial number of a machine terminal in a group, a position of a public radio bearer configuration parameter corresponding to the group in a broadcast message, and information such as starting time of initiating access by the group;
for example, the machine terminal may obtain the grouping information from the network side, that is, the network side groups the machine terminals according to a preset policy to obtain the grouping information, and then the network side issues the grouping information to each machine terminal and other related devices through dedicated connection or paging.
For another example, the network side may group the machine terminals according to a preset policy to obtain group information, and then directly configure the group information on the machine terminals.
102. Determining a public radio bearer corresponding to a group to which the machine terminal belongs according to the grouping information;
in the embodiment of the present invention, all the machine terminals in a group share a radio bearer, and for convenience of description, the shared radio bearer is referred to as a common radio bearer, the common radio bearer may be a static radio bearer broadcast by a broadcast message, and all the machine terminals in a group may read the relevant configuration belonging to the common radio bearer from the broadcast message according to the "location of the corresponding common radio bearer configuration parameter of the group in the broadcast message" in the grouping information, and initiate access at a specified time point.
103. Generating MAC PDU and RLC PDU; the MAC PDU and the RLC PDU are suitable for application of the Internet of things; for example, any of the following methods may be specifically employed:
(1) neither the MAC layer nor the RLC layer has a segmentation function, as follows:
only one MAC PDU and one RLC PDU are generated in one Transmission, that is, one Transmission is a complete Internet Protocol (IP) packet, so the packet header of the MAC PDU may only include the length indication of the Service Data Unit (SDU) of the MAC, but the information such as the Transmission Sequence Number (TSN), the fragmentation indication (SS), and the LCH-ID in the prior art may be omitted, and the RLC PDU may adopt a Transparent Mode (TM) structure, and therefore, RLC retransmission is not required, and the packet header is not required.
(2) The MAC layer has no segmentation function, while the RLC layer has segmentation function, as follows:
generating one MAC PDU and at least one RLC PDU by one-Time Transmission, namely fixing the length of the RLC PDUs, but not limiting the number of the RLC PDUs, and then connecting all the RLC PDUs in series at an MAC layer to transmit in a Transmission Time Interval (TTI); since only one MAC PDU is generated in one transmission, the header of the MAC PDU may omit information such as TSN, split indication, LCH-ID and the like in the prior art, similarly to (1), except that the header of the MAC PDU at this time includes the number of MAC SDUs, instead of the length indication of the MAC SDUs; at this time, the RLC pdu may adopt a structure of an Unacknowledged Mode (UM), and RLC retransmission is not required; wherein the header of the RLC PDU includes a Sequence Number (SN) for ordering and a length of data other than the padding bits.
(3) The MAC layer has a segmentation function, while the RLC layer does not have a segmentation function, as follows:
one RLC PDU and at least one MAC PDU are generated by one transmission, that is, the RLC PDU may not need to be sequenced, and the MAC PDU needs to be sequenced, so the packet header of the MAC PDU only includes TSN, split indication and length indication of the MAC SDU for sequencing, and the RLC PDU may adopt a transparent mode structure, and RLC retransmission is not needed, and the packet header is not needed.
(4) The MAC layer and the RLC layer each have a segmentation function as follows:
generating at least one MAC PDU and at least one RLC PDU through one-time transmission, namely the RLC PDU and the MAC PDU need to be sequenced, so that the packet header of the MAC PDU only comprises a TSN (transport stream network), a splitting instruction and a length instruction of the MAC SDU, and the RLC PDU adopts a structure of an unacknowledged mode and does not need RLC retransmission; wherein the header of the RLC PDU includes only SN for ordering and the length of data other than the padding bits.
In addition, the header of the MAC PDU may further include a machine terminal identifier (device ID), for example, if the MAC layer needs to perform some machine terminal-specific control, such as Time Advance (TA) maintenance, in the above 4 methods, the header of the MAC PDU may further include the machine terminal identifier. But if the MAC layer does not maintain TA, the machine terminal identification is not needed; alternatively, if the physical resource allocation manner enables the common user plane entity to determine which machine terminal the MAC PDU belongs to through information such as radio bearer, code track, time, etc., for example, by broadcasting the time for transmitting uplink data configured for each machine terminal according to the machine terminal identifier, so that the machine terminals do not overlap each other when transmitting uplink data, the network may infer which machine terminal transmits data according to the data arrival time. Machine terminal identification may not be required. Besides the method for determining whether the fixed machine terminal identifier exists, an indication for indicating whether the machine terminal identifier exists may be carried in a packet header of the MAC PDU.
It should be noted that if there are at least two logical channels, the header of the MAC PDU may further include an LCH-ID indicating the logical channel used, but the number of bits (bits) of the LCH-ID may be reduced correspondingly compared to the prior art.
104. And transmitting the MAC PDU and the RLC PDU to a common user plane entity through the determined common radio bearer, wherein the user plane entity includes a MAC layer (i.e., a MAC entity) and an RLC layer (i.e., an RLC entity).
Optionally, if data needs to be encrypted, the header of the PDU may also carry a random number COUNT for decryption, for example, the method may further include the following steps:
encrypting the generated MAC PDU at an MAC layer, wherein the packet header of the MAC PDU also comprises a random number COUNT for decryption; or,
and encrypting the generated RLC PDU in the RLC layer, wherein the header of the RLC PDU also comprises a random number COUNT and/or a machine terminal identification for decryption.
As can be seen from the above, the embodiments of the present invention adopt grouping the machine terminals according to the preset policy, and make the machine terminals in the group share one radio bearer, so that the machine terminals in the group can only correspond to one common RLC entity, and do not need to establish a corresponding PLC entity for each machine terminal, thereby saving network resources, and simultaneously omitting some header information of the MAC PDU and the RLC PDU, for example, omitting information such as LCH-ID or reducing the number of bits (bit) of the information, so as to save the header overhead, thereby reducing the processing complexity and improving the transmission efficiency.
In addition, because the wireless resources occupied by the machine terminal communication are reduced, the influence of the machine terminal communication on the common terminal can be reduced, and the communication quality of the common terminal can be ensured.
Example II,
This embodiment will be described from the perspective of a receiving end, that is, a network side device, where the network side device includes at least a common user plane entity and may further include a control plane entity. The common user plane entity is a common user plane entity established by the network side equipment for a group of machine terminals transmitted through the common radio bearer; and a common radio bearer refers to one radio bearer that is common to all terminals within each group.
A method of data processing, comprising: and the receiving machine terminal processes the MAC PDU and the RLC PDU according to the MAC PDU and the RLC PDU which are sent by the grouping information through the public radio bearer. The grouping information may include information such as a group identifier, a sequence number of the machine terminal in the group, and a location of a common radio bearer configuration parameter corresponding to the group in the broadcast message.
Referring to fig. 2, the specific process may be as follows:
201. obtaining grouping information of the machine terminals according to a preset strategy, namely grouping the machine terminals according to the preset strategy so as to obtain the grouping information;
the preset policy may be set according to the requirements of the actual application, for example, the preset policy may be divided according to the location of each machine terminal and/or the attributes of the server, and the like.
The grouping information comprises a group identifier, a serial number of the machine terminal in the group, the position of a public radio bearer configuration parameter corresponding to the group in the broadcast message, and information such as starting time of initiating access by the group;
202. notifying the machine terminal of the grouping information;
for example, the packet information may be delivered to each machine terminal and other devices associated therewith via a dedicated connection or page.
203. Receiving MAC PDU and RLC PDU sent by the machine terminal through the public radio bearer according to the grouping information;
it should be noted that, in the embodiment of the present invention, all the machine terminals in a group share one radio bearer, which is referred to as a common radio bearer, the common radio bearer may be a static radio bearer broadcasted by a broadcast message, and all the machine terminals in a group may read, according to a "location of a corresponding common radio bearer configuration parameter of the group in the broadcast message" in the grouping information, a relevant configuration belonging to the common radio bearer from the broadcast message, and initiate access at a specified time point.
Because the machine terminals in the group all share one radio bearer, the machine terminals in the group can only correspond to one common RLC entity without establishing a corresponding PLC entity for each machine terminal, thereby saving network resources and simultaneously omitting some header information of MAC PDU and RLC PDU. Further, the data processing method may further include step 204;
204. and processing the received MAC PDU and the RLC PDU. For example, the following may be specifically mentioned:
(1) if the machine terminal only generates one MAC PDU and one RLC PDU at a time, wherein a packet header of the MAC PDU only includes a length indication of the MAC SDU, and the RLC PDU adopts a transparent mode structure, the specific processing of the MAC PDU and the RLC PDU is as follows:
analyzing the MAC PDU according to the length of the MAC SDU and submitting the MAC PDU to an upper layer; the RLC PDU is parsed and directly submitted to an upper layer.
(2) If the machine terminal generates one MAC PDU and at least one RLC PDU at a time, wherein the header of the MAC PDU only includes the number of MAC SDUs, and the RLC PDU adopts an unacknowledged mode structure, and the header of the RLC PDU only includes SN for sequencing and the length of data other than padding bits, then the processing of the MAC PDU and the RLC PDU is specifically:
analyzing the MAC PDU according to the number of the MAC SDUs and submitting the MAC PDU to an upper layer; and the RLC PDU is analyzed, sequenced, concatenated and recombined according to the SN and the length of data except the padding bits, and submitted to an upper layer.
(3) If the machine terminal generates one RLC PDU and at least one MAC PDU at a time, where a packet header of the MAC PDU only includes a TSN for sorting, a splitting indication, and a length indication of a MAC SDU, and the RLC PDU adopts a structure in a transparent mode, the processing of the MAC PDU and the RLC PDU specifically includes:
analyzing, sequencing, concatenating and recombining the MAC PDU according to the transmission sequence number TSN, the splitting indication and the length indication of the MAC SDU, and submitting the MAC PDU to an upper layer; the RLC PDU is parsed and submitted to an upper layer.
(4) If the machine terminal generates at least one RLC PDU and at least one MAC PDU in one transmission, where a header of the MAC PDU only includes a TSN for sequencing, a split indication, and a length indication of a MAC SDU, and the RLC PDU adopts an unacknowledged mode structure, and the header of the RLC PDU only includes SN for sequencing and a length of data other than padding bits, the processing of the MAC PDU and the RLC PDU is specifically:
analyzing, sequencing, concatenating and recombining the MAC PDU according to the TSN, the splitting indication and the length indication of the MAC SDU, and submitting to an upper layer; the RLCPDU is analyzed, sequenced, concatenated and recombined according to the sequence number SN and the length of data except the filling bits, and is submitted to an upper layer.
In addition, if the data is encrypted, the common user plane entity needs to decrypt the PDU, for example, if the machine terminal encrypts the data at the MAC layer, the header of the MAC PDU may further include a random number COUNT for decryption, and then, processing the MAC PDU and the RLC PDU (i.e. step 204) may further include: and decrypting the MAC PDU according to the random number COUNT at the MAC. Or,
if the machine terminal encrypts data in the RLC layer, the header of the RLC PDU may further include a random number COUNT for decryption and/or a machine terminal identification, and then processing the MAC PDU and the RLC PDU (i.e. step 204) further includes: and deciphering the RLC PDU according to the random number COUNT at the RLC.
In addition, the packet header of the MAC PDU may further include a machine terminal identifier, and then, the MAC layer of the network side device may further perform some operations, such as timing advance maintenance, etc., according to the machine terminal identifier, and optionally, the packet header of the MAC PDU may also be used to indicate an indication whether the machine terminal identifier exists, and then the network side device further needs to determine the indication, that is, step 204 may further include:
and reading the machine terminal identifier in the MAC PDU header when the existence of the machine terminal identifier is determined according to the indication for indicating whether the machine terminal identifier exists.
Otherwise, if it is determined that the machine terminal identifier does not exist, it indicates that the machine terminal identifier does not exist in the MAC PDU header, so that subsequent header information, such as the TSN, the split indication, or the length indication of the MAC sdu, may be directly read.
Wherein, the sending of the packets and the packet information (i.e. steps 201 and 202) may be specifically performed by a control plane entity in the network side device, and the receiving and processing of the PDUs (i.e. steps 203 and 204) may be specifically performed by a common user plane entity in the network side device.
As can be seen from the above, the embodiments of the present invention group the machine terminals according to the preset policy, and enable the machine terminals in the group to share one radio bearer, so that the machine terminals in the group can only correspond to one common RLC entity, and do not need to establish a corresponding PLC entity for each machine terminal, thereby saving network resources, and simultaneously omitting some header information of the MAC PDU and the RLC PDU, for example, omitting information such as LCH-ID or reducing the number of bits of the information.
In addition, because the wireless resources occupied by the machine terminal communication are reduced, the influence of the machine terminal communication on the common terminal can be reduced, and the communication quality of the common terminal can be ensured.
Example III,
The method described according to the implementation of the first and second embodiments will now be described in detail by way of example.
Firstly, the network side groups the machine terminals according to a preset policy, and the preset policy may be set according to the requirements of the actual application, for example, the preset policy may be divided according to the location of each machine terminal and/or the attributes of the server, and the like. After grouping, the grouping information is sent to each machine terminal through dedicated connection or paging, and the sent content may include information such as a group identifier, a serial number of the device in the group, and a position of a public radio bearer configuration parameter corresponding to the group in a broadcast message, and may also include a start time of initiating access by the group, and the like.
The machine terminals in all the groups read the radio bearer configuration parameters belonging to the group from the broadcast message by the pre-obtained information and initiate access at the specified time point. The control plane common radio bearer establishment procedure can be referred to in the prior art, and is not described herein again.
In order to save processing resources of an access network and fully utilize the service characteristics of single MTC service, small data volume and certain allowable failure rate, all machine terminals in each group can be corresponding to a common RLC entity and a MAC entity. For convenience of description, in the embodiment of the present invention, the common RLC entity and the MAC entity are collectively referred to as a common user plane entity.
No matter the in-group equipment adopts an access mode based on competition or non-competition, data among different machine terminals does not need to keep a certain sequence in L2, the data among the machine terminals can be sent to a core network out of order, and the mapping relation between the data and the machine terminals is ensured by an application layer.
Referring to fig. 3, it can be seen from fig. 3 that for a common user plane entity (i.e., common RAN), if the application layer data of one machine terminal is not segmented by the MAC layer and/or the RLC layer, there is no need to order the application layer data to be directly submitted to the upper layer. If the layers are partitioned, the layers that are partitioned are sorted accordingly before being submitted. Two PDUs of the machine terminal 6 as in the MAC layer of the figure: PDU1 of machine terminal 6 and PDU2 of machine terminal 6, and two PDUs of machine terminal 2 of RLC layer: PDU1 for machine terminal 2 and PDU2 for machine terminal 2; while other PDUs, such as the PDUs of machine terminal 1, machine terminal 3, machine terminal 4, machine terminal 7, machine terminal n, etc., do not need to be sorted, but are submitted directly.
In most application scenarios, because the data volume of each machine terminal is the same and fixed, a completely transparent mode can be adopted when the data volume is very small, i.e. the PDU is not segmented in the MAC layer and the RLC layer, which can greatly improve the efficiency. Of course, segmentation may be performed in the RLC layer and/or the MAC layer, and although such a gain is not high in the fully transparent mode, the number of bits of the header information may be much smaller than that in the prior art. For these several application scenarios, the following detailed descriptions will be provided in this embodiment (i.e., embodiment three), and in embodiments four, five, and six, respectively.
In this embodiment, both the MAC layer and the RLC layer on the machine terminal side have no segmentation function, that is, each machine terminal can only generate one MAC PDU and one RLC PDU at a time of transmission, and a complete IP packet is transmitted at a time, so that the machine terminals can be distinguished by the application layer without ensuring sequential delivery between the machine terminals. That is, after the machine terminal determines the common radio bearer to which the machine terminal belongs according to the grouping information (i.e., the machine terminal), and transmits the MAC PDU and the RLC PDU to the common user plane entity according to the common radio bearer, the common user plane entity may submit the received MAC PDU and RLC PDU directly without sorting the received MAC PDU and RLC PDU.
In order to meet the reporting requirements of different application scenarios, the size of the RLC PDU is not fixed at the machine terminal, but a flexible (flexible) manner is adopted, and in addition, the Transport Format Combination (TFC) selection function of the MAC also needs to be changed to some extent, so that the maximum available power of the MAC is not considered, but the selection of the Transport block length exceeding the power limit is supported. Although having some impact on performance, many operations, such as ordering, etc., may be omitted, so overall performance is improved over the prior art. The specific treatment may be as follows:
(1) MAC layer on machine terminal side
Because the MTC service has uniqueness, only one logical channel may be used at the data transmission stage of the sender, and thus, the packet header of the MAC PDU generated by the machine terminal may not carry LCH-ID, and in addition, because the MAC layer does not divide data, the packet header of the MAC PDU may not carry TSN and splitting indication in the existing system, but only needs to include an L field for indicating the size of the MAC SDU, where the number of bits in the L field may be correspondingly reduced according to a specific application.
Of course, if at least two logical channels are set, the LCH-ID needs to be added to the header of the MAC PDU, but the number of bits of the LCH-ID can be reduced accordingly.
In addition, if the MAC layer of the Long Term Evolution (LTE) system needs to perform some control differentiated according to the machine terminal, such as TA maintenance, etc., the MAC layer may also carry the machine terminal identifier in the header of the MAC PDU. But if the MAC layer does not maintain TA, the machine terminal identification is not needed; alternatively, if the physical resource allocation manner enables the common user plane entity to determine which machine terminal the MAC PDU belongs to through information such as radio bearer, code track, time, etc., for example, by broadcasting the time for transmitting uplink data configured for each machine terminal according to the machine terminal identifier, so that the machine terminals do not overlap each other when transmitting uplink data, the network may infer which machine terminal transmits data according to the data arrival time. Machine terminal identification may not be required.
Besides the method of whether the fixed machine terminal identifier exists, an indication for indicating whether the machine terminal identifier exists, such as an indication bit I, may be carried in the packet header of the MAC PDU.
(2) MAC layer for common user plane entities
If the header of the received MAC PDU does not contain the LCH-ID, i.e. the machine terminal side adopts the LCH-ID-free mode, the MAC layer of the common user plane entity does not need the logical channel mapping in the existing system, and if the header of the received MAC PDU contains the LCH-ID, the common user plane entity needs to add the logical channel mapping function.
Because the MAC layer at the machine terminal side does not divide data, after receiving the MAC PDU, the common user plane entity does not need to recombine (reordering) and demultiplex the MAC PDU, does not need to concatenate and merge the MAC PDU, and directly submits the MAC PDU to the upper layer after analysis.
In addition, if the MAC layer of the LTE system needs to perform some control distinguished by the machine terminal, such as TA maintenance, the MAC layer also needs to acquire the machine terminal identifier at this time, and then performs processing such as control or TA maintenance according to the machine terminal identifier, which is described in detail in the prior art and is not described herein again. For example, if the packet header of the MAC PDU does not carry the machine terminal identifier, which machine terminal the MAC PDU belongs to may be determined through information such as radio bearer, code channel, and time.
If the header of the MAC PDU also carries an indication bit I, the common user plane entity also needs to interpret the indication bit I in the MAC layer and determine whether the machine terminal exists.
(3) RLC layer at machine terminal side:
the structure of RLC PDU generated by machine terminal side can adopt transparent mode structure, and retransmission can be handed to application layer and HARQ, so that it also has no need of retransmission in MAC layer, i.e. RLC PDU has no need of packet header, and can be directly passed through to RLC layer of common user plane entity.
Of course, since data is not segmented in the RLC layer, the size of the RLC PDU is not fixed, but is flexible such that the transparent mode structure supports different RLC PDU sizes.
(4) RLC layer of common user plane entity:
because the RLC layer at the machine terminal side does not segment data, after receiving the RLC PDUs, the common user plane entity does not need to sequence the RLC PDUs, does not need to concatenate and merge the MAC PDUs, and directly submits the RLC PDUs to an upper layer.
(5) Encryption
In the LTE system, if ciphering is required and a ciphering algorithm is placed in the PDCP layer, a header of an RLC PDU generated by a machine terminal needs to carry a machine terminal identifier at this time, so that a public user plane entity can acquire decryption (Key) information from a higher layer according to the machine terminal identifier, and then decrypt the received RLC PDU according to the decryption information; of course, if the common user plane entity can determine which machine terminal the RLC PDU belongs to through information such as radio bearer, code channel, time, etc., it may not be necessary to carry the machine terminal identifier.
And if the encryption is placed on the MAC layer, after the machine terminal generates the MAC PDU, the packet header of the MAC PDU also needs to carry the machine terminal identification and the random number COUNT for decryption. If the encryption is placed in the RLC layer, after the machine terminal generates the RLC PDU, the header of the RLC PDU also needs to carry the machine terminal identifier and the random number COUNT for decryption. Wherein, the random number COUNT is randomly generated by the machine terminal. Similarly, if the common user plane entity can determine which machine terminal the RLC PDU belongs to through information such as radio bearer, code track, time, etc., the MAC PDU or the header of the RLC PDU may not need to carry the machine terminal identifier.
For better understanding of the above description, fig. 4 shows a schematic structure diagram of a MAC PDU and an RLC PDU, and it should be noted that fig. 4 illustrates an example in which ciphering is not required and only one logical channel exists. The dotted line indicates that the information may be omitted.
As can be seen from the above, the embodiments of the present invention adopt grouping the machine terminals according to the preset policy, and make the machine terminals in the group share one radio bearer, so that the machine terminals in the group can only correspond to one common RLC entity, and do not need to establish a corresponding PLC entity for each machine terminal, thereby saving network resources.
In addition, because the wireless resources occupied by the machine terminal communication are reduced, the influence of the machine terminal communication on the common terminal can be reduced, and the communication quality of the common terminal can be ensured.
Example four,
Different from the third embodiment, in the present embodiment, the MAC layer at the machine terminal side does not have a segmentation function, and the RLC layer has a segmentation function, that is, only one MAC PDU can be generated per transmission of the machine terminal, but the number of RLC PDUs is not limited. At this time, the RLC length can be fixed, and the MAC layer needs to concatenate all generated RLC PDUs and transmit them in one TTI. The RLC PDUs of the RLC layer need to be ordered, and the MAC PDUs of the MAC layer do not need to be ordered. The specific treatment is as follows:
(1) MAC layer on machine terminal side
The MAC layer specific processing of the machine terminal is similar to that of the third embodiment, except that: since the rlc pdu length is fixed, the number N of MAC SDUs may be used instead of the L field, and the rest can be referred to in embodiment three, which is not described herein again.
(2) MAC layer for common user plane entities
The MAC layer specific processing of the common user plane entity is similar to the third embodiment, except that: the number of MAC SDUs N needs to be used to identify how many fixed length MAC SDUs are contained within the MAC PDU. For other descriptions, refer to the third embodiment, which is not described herein.
(3) RLC layer at machine terminal side
The RLC PDU structure of the machine terminal can adopt a PDU structure of an unacknowledged mode, and RLC retransmission is not needed. The header of the generated RLC PDU may include a sequence number SN used for sorting and a length of data other than padding bits, and may further include a machine terminal identifier, where the machine terminal identifier may specifically be a number allocated to the machine terminal by the system according to the size of the group without using Radio Network Temporary Identifier (RNTI) or the like used in the prior art, and the number of bits of the sequence number SN may also be correspondingly reduced to save the header overhead.
If the common user plane entity can determine which machine terminal the MAC PDU belongs to through information such as radio bearer, code track, time, etc., for example, by broadcasting, each machine terminal is configured with time for transmitting uplink data according to the machine terminal identifier, so that the machine terminals do not overlap with each other when transmitting uplink data, the network can deduce which machine terminal transmits data according to the data arrival time, and then. The machine terminal identification may not be needed, but the MAC layer informs the RLC layer of the machine terminal attribution condition of each RLC PDU.
(4) RLC layer of common user plane entity
The RLC layer of the common user plane entity analyzes, sequences, concatenates and recombines the RLC PDUs according to the sequence number SN and the length of data except the filling bits, and submits the RLC PDUs to an upper layer.
It should be noted that, since all RLC PDUs transmitted at one time are encapsulated in one MAC PDU, if the RLC PDUs can be decapsulated according to the sequence in the MAC PDU at present, sequential reassembly can be guaranteed, and the sequence number SN may not be needed at this time. However, if the group members are too large, the ordering queue maintained by the RLC entity is too large, and the processing power requirement of the RLC entity is increased.
(5) Encryption:
in the LTE system, if encryption is needed and an encryption algorithm is placed on a PDCP layer, a header of an RLC PDU generated by a machine terminal needs to carry a machine terminal identifier at the moment so that a public user plane entity can acquire decryption information from a high layer according to the machine terminal identifier and then decrypt the received RLC PDU according to the decryption information; of course, if the common user plane entity can determine which machine terminal the RLC PDU belongs to through information such as radio bearer, code channel, time, etc., it may not be necessary to carry the machine terminal identifier.
The W system ciphering can be placed in the RLC layer, and since the header of the RLC PDU in this embodiment needs to include SN, the method of calculating COUNT using SN and Hyper Frame Number (HFN) in the prior art can be used, so that the RLC PDU may not need to carry COUNT, but only needs to carry the machine terminal identifier. Similarly, if the common user plane entity can determine which machine terminal the RLC PDU belongs to through information such as radio bearer, code track, time, etc., the header of the RLC PDU may not need to carry the machine terminal identifier.
For the encryption of the W system, the encryption may also be placed in the MAC layer, which may specifically refer to embodiment three, and is not described herein again.
For better understanding of the above description, fig. 5 shows a schematic structure diagram of MAC PDU and RLC PDU, and it should be noted that fig. 5 illustrates an example in which ciphering is not required and only one logical channel exists. The dotted line indicates that the information may be omitted.
As can be seen from the above, the embodiments of the present invention adopt grouping the machine terminals according to the preset policy, and make the machine terminals in the group share one radio bearer, so that the machine terminals in the group can only correspond to one common RLC entity, and do not need to establish a corresponding PLC entity for each machine terminal, thereby saving network resources.
In addition, because the wireless resources occupied by the machine terminal communication are reduced, the influence of the machine terminal communication on the common terminal can be reduced, and the communication quality of the common terminal can be ensured.
Example V,
Unlike the previous embodiments, in this embodiment, the RLC layer of the machine terminal has no segmentation function, and the MAC layer has segmentation function, that is, only one RLC PDU can be generated per transmission of the machine terminal, and the number of MAC PDUs is not limited. At this time, since the RLC packet may be very large, the size of the RLC PDU size may not be fixed, but a flexible manner (i.e. flexible PDU size) may be adopted to adapt to different reporting requirements. The RLC PDUs of the RLC layer do not need to be ordered, while the MAC PDUs of the MAC layer need to be ordered. The specific treatment may be as follows:
(1) MAC layer on machine terminal side:
because the MTC service has uniqueness, only one logical channel can be used at the data transmission stage of the sending end, and in this way, the packet header of the MAC PDU generated by the machine terminal does not carry the LCH-ID; in addition, since the MAC layer needs to segment data, the header of the MAC PDU needs to carry the TSN, the split indication, and an L field for indicating the size of the MAC SDU, wherein the bit number of the L field can be correspondingly reduced according to a specific application.
The header of the MAC PDU may also include a machine terminal identifier, which is also needed if the MAC layer of the LTE system needs some control differentiated by machine terminals, such as TA maintenance. However, if the physical resource allocation manner enables the common user plane entity to determine which machine terminal the MAC PDU belongs to through information such as radio bearer, code channel, time, etc., for example, by broadcasting the time for transmitting uplink data configured for each machine terminal according to the machine terminal identifier, so that the machine terminals do not overlap each other when transmitting uplink data, the network can deduce which machine terminal transmits data according to the data arrival time, and then. Machine terminal identification may not be required.
Of course, if at least two logical channels are set, the LCH-ID needs to be added to the header of the MAC PDU, but the number of bits of the LCH-ID can be reduced accordingly.
Besides the method of whether the fixed machine terminal identifier exists, an indication for indicating whether the machine terminal identifier exists, such as an indication bit I, may be carried in the packet header of the MAC PDU.
(2) MAC layer of common user plane entity:
if the header of the received MAC PDU does not contain the LCH-ID, i.e. the machine terminal side adopts the LCH-ID-free mode, the MAC layer of the common user plane entity does not need the logical channel mapping in the existing system, and if the header of the received MAC PDU contains the LCH-ID, the common user plane entity needs to add the logical channel mapping function.
Because the MAC layer at the machine terminal side divides data, after the MAC PDU is received by the common user plane entity, the MAC layer of the common user plane entity needs to set a sorting queue for each machine terminal, and send the received MAC PDU to the corresponding sorting queue for sorting according to the machine terminal identifier or according to the correspondence between the physical resource and the device, and after the MAC PDU is concatenated and recombined, the MAC PDU is submitted to the upper layer.
If the header of the MAC PDU also carries an indication bit I, the common user plane entity also needs to interpret the indication bit I in the MAC layer and determine whether the machine terminal exists.
In addition, if the MAC layer of the LTE system needs to perform some control differentiated according to the machine terminal, such as TA maintenance, then the MAC layer also needs to perform processing such as control or TA maintenance, which is described in detail in the prior art and is not described herein again.
(3) RLC layer at machine terminal side:
the RLC PDU structure generated at the machine terminal side may adopt a transparent mode structure, which may specifically refer to embodiment three, and is not described herein again.
(4) RLC layer of common user plane entity:
because the RLC layer at the machine terminal side does not segment data, after receiving the RLC PDUs, the common user plane entity does not need to sequence the RLC PDUs, does not need to concatenate and merge the MAC PDUs, and directly submits the RLC PDUs to an upper layer.
(5) Encryption:
the encryption process is the same as the third embodiment, and details are not described herein.
The following diagram shows a structure diagram of the MAC layer (assuming that the MAC layer needs to distinguish the PDU sequencing queue affiliation by device ID), and the structure diagram is not repeated since the RLC layer is completely transparent.
For better understanding of the above description, fig. 6 shows a schematic structure diagram of MAC PDU and RLC PDU, and it should be noted that fig. 6 is described by taking an example in which ciphering is not required and only one logical channel exists. The dotted line indicates that the information may be omitted.
As can be seen from the above, the embodiments of the present invention group the machine terminals according to the preset policy, and make the machine terminals in the group share one radio bearer, so that the machine terminals in the group can only correspond to one common RLC entity, and do not need to establish a corresponding PLC entity for each machine terminal, thereby saving network resources.
In addition, because the wireless resources occupied by the machine terminal communication are reduced, the influence of the machine terminal communication on the common terminal can be reduced, and the communication quality of the common terminal can be ensured.
Example six,
In this embodiment, both the MAC layer and the RLC layer support a segmentation function, that is, each machine terminal can generate at least two RLC PDUs and MAC PDUs by one transmission, i.e., there is no limitation on the number of RLC PDUs and MAC PDUs. At this time, the RLC layer may adopt a fixed RLC PDU size, and the MAC layer concatenates or segments the RLC PDUs according to channel conditions. The specific treatment may be as follows:
(1) MAC layer on machine terminal side
The method can be realized in two ways, as follows:
the first mode is as follows: the header of the MAC PDU needs to carry the TSN, the split indication, the L field for indicating the size of the MAC sdu, and the machine terminal identifier, where the bit number of the L field may be correspondingly reduced according to a specific application.
The second mode is as follows: the header of the MAC PDU may not carry the TSN, the split indication, and the L field for indicating the size of the MAC SDU, but carries the number N of MAC SDUs and the machine terminal identifier, but it is mandatory that the RLC PDU cannot be split.
The second method can save more overhead of packet header than the first method, and the ordering is not needed in the MAC layer, but performed in the RLC layer.
Because the MTC service has uniqueness, only one logical channel can be used at the data transmission stage of the sending end, and in this way, the packet header of the MAC PDU generated by the machine terminal does not carry the LCH-ID; of course, if at least two logical channels are set, the LCH-ID needs to be added to the header of the MAC PDU, but the number of bits of the LCH-ID can be reduced accordingly.
It should be noted that, if the physical resource allocation manner enables the common user plane entity to determine which machine terminal the MAC PDU belongs to through information such as radio bearer, code channel, time, etc., for example, by broadcasting the time for transmitting uplink data configured for each machine terminal according to the machine terminal identifier, so that the machine terminals do not overlap each other when transmitting uplink data, the network may infer which machine terminal transmits data according to the data arrival time. The MAC PDU may not need to carry the machine terminal identity.
Besides the method of whether the fixed machine terminal identifier exists, an indication for indicating whether the machine terminal identifier exists, such as an indication bit I, may be carried in the packet header of the MAC PDU.
(2) MAC layer of common user plane entity:
after the MAC layer of the common user plane entity receives the MAC PDU, the MAC PDU sent by the machine terminal needs to be sequenced, concatenated and recombined according to the TSN, the split indication, the L domain and the machine terminal identifier, and then submitted to the upper layer. If only one logical channel exists at the data transmission stage of the sending end, the logical channel mapping in the prior art is not needed at this time.
(3) RLC layer at machine terminal side:
the specific processing manner is the same as that in the fourth embodiment, and reference may be made to the fourth embodiment for details, which are not described herein again.
(4) RLC layer of common user plane entity:
the specific processing manner is the same as that in the fourth embodiment, and reference may be made to the fourth embodiment for details, which are not described herein again.
(5) Encryption:
the specific processing manner is the same as that in the fourth embodiment, and reference may be made to the fourth embodiment for details, which are not described herein again.
For better understanding of the above description, fig. 7a and 7b show the structure schematic diagrams of the MAC PDU and the RLC PDU of the present embodiment, and it should be noted that fig. 7a and 7b both illustrate the case where encryption is not required and only one logical channel exists. The dotted line indicates that the information may be omitted. In fig. 7a, the MAC PDU structure corresponds to the first processing manner, and is similar to that in fig. 6, except that an L field is assigned to each MAC SDU concatenated in one MAC PDU. While the MAC PDU structure in fig. 7b corresponds to the second process, the MAC PDU structure is the same as in fig. 5, and the RLC PDUs in fig. 7a and 7b are the same as in fig. 5.
As can be seen from the above, in the embodiments of the present invention, machine terminals are grouped according to a preset policy, and the machine terminals in a group share one radio bearer, so that the machine terminals in the group can only correspond to one common RLC entity, and do not need to establish a corresponding PLC entity for each machine terminal, thereby saving network resources.
In addition, because the wireless resources occupied by the machine terminal communication are reduced, the influence of the machine terminal communication on the common terminal can be reduced, and the communication quality of the common terminal can be ensured.
Example seven,
In order to better implement the above method, an embodiment of the present invention further provides a machine terminal, referring to fig. 8a, the machine terminal includes an obtaining unit 701, a generating unit 702, a determining unit 703 and a sending unit 704;
an obtaining unit 701, configured to obtain grouping information, where the grouping information includes a group identifier, a serial number of a machine terminal in a group, and a position of a public radio bearer configuration parameter corresponding to the group in a broadcast message; the information of the starting time of the group for initiating access and the like can be further included;
for example, the network side may group the machine terminals according to a preset policy to obtain group information, and then the network side issues the group information to the obtaining unit 701 of each machine terminal and other related devices through dedicated connection or paging.
For another example, the network side may group the machine terminals according to a preset policy to obtain group information, and then directly configure the group information on the machine terminals.
A determining unit 702, configured to determine, according to the grouping information acquired by the acquiring unit 701, a common radio bearer corresponding to a group to which the machine terminal belongs;
in the embodiment of the present invention, all the machine terminals in a group share a radio bearer, and for convenience of description, the shared radio bearer is referred to as a common radio bearer, the common radio bearer may be a static radio bearer broadcast by a broadcast message, and all the machine terminals in a group may read the relevant configuration belonging to the common radio bearer from the broadcast message according to the "location of the corresponding common radio bearer configuration parameter of the group in the broadcast message" in the grouping information, and initiate access at a specified time point.
A generating unit 703, configured to generate a MAC PDU and an RLC PDU; the MAC PDU and the RLC PDU are suitable for application of the Internet of things;
a sending unit 704, configured to transmit the MAC PDU and the RLC PDU generated by the generating unit 703 to a common user plane entity through the common radio bearer determined by the determining unit 703, where the common user plane entity is a common user plane entity established by the network side device for a group of machine terminals transmitting through the common radio bearer.
The generating unit 703 is specifically a first generating module, or a second generating module, or a third generating module, or a fourth generating module;
the first generation module is used for generating one MAC PDU and one RLC PDU in one transmission mode when the MAC layer and the RLC layer on the terminal side of the machine are not provided with segmentation functions, wherein the packet header of the MAC PDU only comprises the length indication of the MAC SDU, and the RLC PDU adopts a transparent mode structure; that is, the information such as TSN, split indication, LCH-ID, etc. in the header of the mac PDU in the prior art can be omitted, and the RLC PDU does not need the header and RLC retransmission, as in the previous embodiment.
A second generating module, configured to generate one MAC PDU and at least one RLC PDU in one transmission when the segmentation function is set in the RLC layer and the MAC layer on the machine terminal side does not set the segmentation function, where a packet header of the MAC PDU only includes the number of MAC SDUs, the RLC PDU adopts an unacknowledged mode structure, and the packet header of the RLC PDU only includes a sequence number SN for sorting and a length of data other than padding bits; that is, the information such as TSN, split indication, and LCH-ID in the MAC PDU header in the prior art can be omitted, and RLC PDU also does not need RLC retransmission, and the number of bits of the length of data other than the sequence number SN and the padding bits carried in the RLC PDU header can be reduced appropriately, as shown in the foregoing embodiment.
A third generating module, configured to set a segmentation function in an MAC layer at a machine terminal side, and generate one RLC PDU and at least one MAC PDU by one transmission when the segmentation function is not set in the RLC layer, where a packet header of the MAC PDU only includes a transmission sequence number TSN used for sorting, a split indication, and a length indication of a MAC SDU, and the RLC PDU adopts a structure in a transparent mode; that is, the information such as LCH-ID in the header of the MAC PDU in the prior art can be omitted, and the RLC PDU does not need the header and RLC retransmission, as in the previous embodiment.
And the fourth generation module is used for generating at least one MAC PDU and at least one RLC PDU in one transmission mode when the MAC layer and the RLC layer on the machine terminal side are both provided with segmentation functions, wherein the packet header of the MAC PDU only comprises a transmission sequence number TSN for sequencing, a splitting instruction and a length instruction of the MAC SDU, the RLC PDU adopts a structure of an unacknowledged mode, and the packet header of the RLC PDU only comprises a sequence number SN for sequencing and the length of data except for padding bits. That is, information such as LCH-ID in the header of the MAC PDU in the prior art can be omitted, and RLC PDU also does not need RLC retransmission, and the number of bits of the length of data other than the sequence number SN and the padding bits carried in the header of the RLC PDU can be reduced appropriately, as shown in the foregoing embodiment.
As shown in fig. 8b, the machine terminal may further include a first encryption unit 705;
a first encrypting unit 705, configured to encrypt the generated MAC PDU at a MAC layer;
the packet header of the MAC PDU generated by the generation unit 703 also includes a random number COUNT for decryption.
Alternatively, as shown in fig. 8c, the machine terminal may also include a second encryption unit 706;
a second ciphering unit 706 for ciphering the generated RLC PDU in the RLC layer;
the header of the RLC PDU generated by the generation unit 703 further includes a random number COUNT and/or a machine terminal identification for decryption.
In addition, the header of the MAC PDU generated by the generating unit 703 may further include a machine terminal identifier, for example, if the MAC layer needs to perform some machine terminal-specific control, such as TA maintenance, the header of the MAC PDU may further include the machine terminal identifier. But if the MAC layer does not maintain TA, the machine terminal identification is not needed; or, if the physical resource allocation manner enables the common user plane entity to determine which machine terminal the MAC PDU belongs to through information such as radio bearer, code channel, time, etc., for example, by broadcasting the time for transmitting uplink data configured for each machine terminal according to the machine terminal identifier, so that the machine terminals do not overlap each other when transmitting uplink data, the network side device may infer which machine terminal transmits data according to the data arrival time. Machine terminal identification may not be required. Besides the method for determining whether the fixed machine terminal identifier exists, an indication for indicating whether the machine terminal identifier exists may be carried in a packet header of the MAC PDU.
It should be noted that, if there are at least two logical channels, the header of the mac pdu generated by the generating unit 703 may further include an LCH-ID indicating the logical channel used, but the number of bits of the LCH-ID may be correspondingly reduced compared to the prior art, so even then, the header overhead may be reduced compared to the prior art.
The specific implementation of each unit can be referred to the previous embodiment, and is not described herein again.
As can be seen from the above, the embodiments of the present invention adopt grouping the machine terminals according to the preset policy, and make the machine terminals in the group share one radio bearer, so that the machine terminals in the group can only correspond to one common RLC entity, and do not need to establish a corresponding PLC entity for each machine terminal, so that after the acquiring unit 701 of the machine terminal acquires the grouping information, most of the information or bit numbers in the prior art, such as omitting information such as LCH-ID or reducing the bit (bit) number of the information, can be omitted from the packet headers of the MAC PDU and the RLC PDU generated by the generating unit 703, and therefore, compared with the prior art, network resources can be saved, and meanwhile, the packet header overhead can be saved, thereby reducing the processing complexity and improving the transmission efficiency.
In addition, because the wireless resources occupied by the machine terminal communication are reduced, the influence of the machine terminal communication on the common terminal can be reduced, and the communication quality of the common terminal can be ensured.
Example eight,
Correspondingly, an embodiment of the present invention further provides a network side device, as shown in fig. 9a, the network side device includes a grouping unit 801, a notification unit 802, and a receiving unit 803;
a grouping unit 801, configured to obtain grouping information of the machine terminal according to a preset policy, where the grouping information includes a group identifier, a serial number of the machine terminal in the group, and a position of a public radio bearer configuration parameter corresponding to the group in the broadcast message; the information of the starting time of the group for initiating access and the like can be further included;
the preset policy may be set according to the requirements of the actual application, for example, the preset policy may be divided according to the location of each machine terminal and/or the attributes of the server, and the like.
A notifying unit 802 configured to notify the machine terminal of the grouping information obtained by the grouping unit 801;
for example, the notification unit 802 may send the packet information to each machine terminal and other related devices through a dedicated connection or paging.
A receiving unit 803, configured to receive a MAC PDU and an RLC PDU sent by the machine terminal through a common radio bearer according to the grouping information;
it should be noted that, in the embodiment of the present invention, all the machine terminals in a group share one radio bearer, which is referred to as a common radio bearer, the common radio bearer may be a static radio bearer broadcasted by a broadcast message, and all the machine terminals in a group may read, according to a "location of a corresponding common radio bearer configuration parameter of the group in the broadcast message" in the grouping information, a relevant configuration belonging to the common radio bearer from the broadcast message, and initiate access at a specified time point.
Referring to fig. 9f, the network side device may further include a processing unit 804;
a processing unit 804, configured to process the MAC PDU and the RLC PDU received by the receiving unit 803.
If the MAC layer and the RLC layer at the machine terminal side do not set the segmentation function, the machine terminal only generates one MAC PDU and one RLC PDU at a time, wherein a packet header of the MAC PDU includes a length indication of the MAC sdu, and the RLC PDU adopts a transparent structure, that is, information such as the TSN, the splitting indication, and the LCH-ID in the packet header of the MAC PDU in the prior art can be omitted, and the RLC PDU does not need a packet header and does not need RLC retransmission, as in the previous embodiment; the processing unit 804 may specifically include a first MAC processing subunit a8041 and a first RLC processing subunit a8042, see fig. 9 b;
a first MAC processing subunit a8041, configured to parse, according to the length of the MAC SDU, the MAC PDU received by the receiving unit 803 and submit the MAC PDU to an upper layer;
the first RLC processing subunit a8042 is configured to directly submit the RLC PDU received by the receiving unit 803 to an upper layer.
If the MAC layer at the machine terminal side does not set the segmentation function, and the RLC layer sets the segmentation function, the machine terminal transmits and generates one MAC PDU and at least one RLC PDU at a time, wherein a packet header of the MAC PDU includes the number of MAC SDUs, and the RLC PDU adopts a structure of an unacknowledged mode, and the packet header of the RLC PDU includes a sequence number SN for sorting and a length of data other than padding bits, that is, information such as TSN, splitting indication, and LCH-ID in the packet header of the MAC PDU in the prior art can be omitted, and the RLC PDU also does not need RLC retransmission, and bits of the sequence number SN carried by the packet header of the RLC PDU and the length of data other than the padding bits can be appropriately reduced, as shown in the foregoing embodiment; at this time, the processing unit 804 may specifically include a second MAC processing subunit B8041 and a second RLC processing subunit B8042, see fig. 9 c;
a second MAC processing subunit B8041, configured to parse, according to the number of MAC SDUs, the MAC PDU received by the receiving unit 803 and submit the MAC PDU to an upper layer;
and the second RLC processing subunit B8042 is configured to parse, sort, concatenate, and reassemble the RLC PDUs received by the receiving unit 803 according to the sequence number SN and the length of the data other than the padding bits, and submit the RLC PDUs to an upper layer.
The MAC layer at the machine terminal side sets a segmentation function, the RLC layer does not set the segmentation function, the machine terminal transmits and generates one RLC PDU and at least one MAC PDU at a time, wherein the packet header of the MAC PDU comprises a transmission sequence number TSN for sequencing, a splitting instruction and a length instruction of the MAC SDU, and the RLC PDU adopts a structure of a transparent mode, namely information such as LCH-ID in the packet header of the MAC PDU in the prior art can be omitted, and the RLC PDU does not need the packet header and does not need RLC retransmission, which refers to the previous embodiment; at this time, the processing unit 804 may specifically include a third MAC processing subunit C8041 and a third RLC processing subunit C8042, see fig. 9 d;
a third MAC processing subunit C8041, configured to perform parsing, sorting, concatenation and reassembly on the MAC PDU received by the receiving unit 803 according to the transmission sequence number TSN, the split indication, and the length indication of the MAC sdu, and submit the MAC PDU to an upper layer;
a third RLC processing subunit C8042, configured to submit the RLC PDU received by the receiving unit 803 to an upper layer.
The MAC layer and the RLC layer at the machine terminal side both set a segmentation function, and the machine terminal transmits and generates at least one RLC PDU and at least one MAC PDU at a time, wherein a packet header of the MAC PDU includes a transmission sequence number TSN, a split indication, and a length indication of the MAC SDU for sorting, and the RLC PDU adopts a structure of an unacknowledged mode, and the packet header of the RLC PDU includes a sequence number SN for sorting and a length of data other than padding bits, that is, information such as LCH-ID in the packet header of the MAC PDU in the prior art can be omitted, and the RLC PDU does not need RLC retransmission as well, and bits of the sequence number SN carried by the packet header of the RLC PDU and the length of the data other than the padding bits can be appropriately reduced, see the foregoing embodiment; at this time, the processing unit 804 may specifically include a fourth MAC processing subunit D8041 and a fourth RLC processing subunit D8042, see fig. 9 e;
a fourth MAC processing subunit D8041, configured to perform parsing, sorting, concatenation and reassembly on the MAC PDU received by the receiving unit 803 according to the transmission sequence number TSN, the split indication, and the length indication of the MAC sdu, and submit the MAC PDU to an upper layer;
the fourth RLC processing subunit D8042 is configured to parse, sort, concatenate, and reassemble the RLC PDUs received by the receiving unit 803 according to the sequence number SN and the length of the data other than the padding bits, and submit the RLC PDUs to an upper layer.
Optionally, if the machine terminal encrypts the RLC PDU or the MAC PDU, the packet header of the RLC PDU or the MAC PDU may further include a random number COUNT for decryption and/or a machine terminal identifier, at this time, the network side device may further include a decryption unit 805, see fig. 9 f;
a deciphering unit 805, configured to decipher the MAC PDU or the RLC PDU according to the random number COUNT and/or the machine terminal identifier.
In addition, the header of the MAC PDU may further include a machine terminal identifier, as shown in the foregoing embodiment, at this time:
the processing unit 804 is further configured to perform some operations, such as timing advance maintenance, of control distinguished by machine terminals according to the machine terminal identifiers.
Optionally, the header of the MAC PDU may also be used to indicate whether the machine terminal identifier exists, in the previous embodiment, at this time:
the processing unit 804 is further configured to read the machine terminal identifier in the MAC PDU header when determining that the machine terminal identifier exists according to the indication indicating whether the machine terminal identifier exists. Otherwise, if it is determined that the machine terminal identifier does not exist, it indicates that the machine terminal identifier does not exist in the MAC PDU header, so that subsequent header information, such as the TSN, the split indication, or the length indication of the MAC SDU, etc., can be directly read.
The specific implementation of each unit can be referred to the previous embodiment, and is not described herein again.
In a specific implementation, the entities of the network side device at least include a common user plane entity, and may further include a control plane entity, for example, the grouping unit 801 and the notification unit may be implemented by the control plane entity, and the receiving unit 803 and the processing unit 804 may be implemented by the common user plane entity, and so on.
As can be seen from the above, the grouping unit 801 of the network side device in the embodiment of the present invention may group the machine terminals according to the preset policy, and make the machine terminals in the group share one radio bearer, so that the machine terminals in the group may only correspond to one common RLC entity, and do not need to establish a corresponding PLC entity for each machine terminal, so that while saving network resources, some header information of the MAC PDU and the RLC PDU may also be omitted, for example, information such as LCH-ID and the like is omitted or the number of bits (bit) of the information is reduced, and therefore, compared with the prior art, the overhead header may be saved, thereby reducing processing complexity and improving transmission efficiency.
In addition, because the wireless resources occupied by the machine terminal communication are reduced, the influence of the machine terminal communication on the common terminal can be reduced, and the communication quality of the common terminal can be ensured.
Examples nine,
Accordingly, an embodiment of the present invention further provides a communication system, where the communication system includes any one of the machine terminals and the network side device provided in the embodiment of the present invention, which may be specifically referred to in the foregoing embodiment and is not described herein again.
In summary, the network side device in the communication system provided in the embodiment of the present invention may group the machine terminals according to the preset policy, and make the machine terminals in the group share one radio bearer, so that the machine terminals in the group may only correspond to one common RLC entity, and do not need to establish a corresponding PLC entity for each machine terminal, thereby saving network resources, and simultaneously omitting some header information of the MAC PDU and the RLC PDU, for example, omitting information such as LCH-ID or reducing the number of bits (bit) of the information, so as to save the header overhead, thereby reducing the processing complexity and improving the transmission efficiency.
In addition, because the wireless resources occupied by the machine terminal communication are reduced, the influence of the machine terminal communication on the common terminal can be reduced, and the communication quality of the common terminal can be ensured.
Those skilled in the art will appreciate that all or part of the steps in the methods of the above embodiments may be implemented by associated hardware instructed by a program, which may be stored in a computer-readable storage medium, and the storage medium may include: read Only Memory (ROM), Random Access Memory (RAM), magnetic or optical disks, and the like.
The data processing method, apparatus and system provided by the embodiment of the present invention are described in detail above, and a specific example is applied in the description to explain the principle and the implementation of the present invention, and the description of the above embodiment is only used to help understanding the method and the core idea of the present invention; meanwhile, for a person skilled in the art, according to the idea of the present invention, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present invention.