CN102395156A - Data transmission methods and device applied between packet data convergence protocol (PDCP) entity and radio link control (RLC) entity - Google Patents
Data transmission methods and device applied between packet data convergence protocol (PDCP) entity and radio link control (RLC) entity Download PDFInfo
- Publication number
- CN102395156A CN102395156A CN2011102986774A CN201110298677A CN102395156A CN 102395156 A CN102395156 A CN 102395156A CN 2011102986774 A CN2011102986774 A CN 2011102986774A CN 201110298677 A CN201110298677 A CN 201110298677A CN 102395156 A CN102395156 A CN 102395156A
- Authority
- CN
- China
- Prior art keywords
- pdcp
- rlc
- entity
- sdu
- sublayer
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Abstract
The invention discloses data transmission methods and a data transmission device applied between a packet data convergence protocol (PDCP) entity and a radio link control (RLC) entity. In one method, after receiving a PDCP service data unit (SDU) from a high layer, the PDCP entity acquires a PDCP protocol data unit (PDU) which corresponds to the PDCP SDU, and then directly transmits the PDCP PDU to the RLC entity. In another method, a sending buffer area is arranged on a PDCP sub-layer; after receiving the PDCP SDU from the high layer, the PDCP entity stores the PDCP SDU in the sending buffer area of the PDCP sub-layer; and after receiving an RLC SDU request which is sent by the RLC entity, the PDCP entity transmits the PDCP PDU which corresponds to the PDCP SDU in the sending buffer area of the PDCP sub-layer to the RLC entity according to the RLC SDU request. By the invention, data transmission between the PDCP sub-layer and an RLC sub-layer is realized; and by defining the sending buffer area of the PDCP sub-layer, storing the PDCP SDU which is received from the high layer in the sending buffer area of the PDCP sub-layer by using the PDCP entity, and transmitting the PDCP PDU which corresponds to the PDCP SDU in the sending buffer area to the RLC entity, data packet interactive operation between the PDCP sub-layer and the RLC sub-layer is realized.
Description
Technical field
The present invention relates to the communications field, particularly a kind of data transmission method and device that is applied to PDCP entity and RLC inter-entity.
Background technology
At LTE (Long Term Evolution; Long Term Evolution) eat dishes without rice or wine the layer two agreement in; PDCP (Packet Data Convergence Protocol has been described; Packet data convergence protocol) the data-bag interacting operation between sublayer and RLC (Radio Link Control, the Radio Link control) sublayer, and listed transmission buffering area and retransmission buffer that transmitter side exists in the RLC entity block diagram in rlc protocol.
In the agreement TS36.323 of LTE PDCP sublayer, transmission and re-transmission for PDCP PDU have following regulation:
For the PDCP SDU that receives from high level (Service Data Units, service data unit), the PDCP sublayer is at related SN (Sequence Number; Sequence number); Executive Head compression (if disposing) is carried out integrity protection (if disposing) and is encrypted (if disposing), after the update mode variable; The corresponding PDCP PDU (Protocol Data Unit, protocol Data Unit) that generates is submitted to the RLC sublayer.
UE (User Equipment; Subscriber's installation) side is at switching, RRC (Radio Resource Control; Radio Resource control) connection reconstruction, and it is upright to carry out the PDCP reconstruction in the processes such as RRC connection first time reprovision after the RRC connection reconstruction, is rebuilding immediately; Distinguish following three kinds of situation, carry out corresponding operation:
(1) is mapped to the DRB (Data Radio Bearer, Data Radio Bearer) of RLC AM pattern
If disposed the head compression, a compression protocol of the up link that then resets;
Bring into use and rebuild AES and the key that disposes by high level in the upright process;
Begin from first PDCP SDU that does not receive RLC sublayer success acknowledge, by COUNT value ascending order retransmit or transmit all rebuild upright before association the PDCP SDU of PDCP SN.If disposed head compression, then each is waited the PDCP SDU Executive Head compression that retransmits or transmit; Each is waited to retransmit or the PDCP SDU that transmits carries out and encrypts.The corresponding PDCP PDU that processing is obtained is submitted to the RLC sublayer and transmits.
(2) be mapped to the DRB of RLC UM pattern
If disposed the head compression, a compression protocol of the up link that then resets;
Next_PDCP_TX_SN and TX_HFN are set to 0, the COUNT state of value before promptly removing;
Bring into use and rebuild AES and the key that disposes by high level in the upright process;
For each related PDCP SN but go back the PDCP SDU that no delivery attempted is given the transmission of RLC sublayer, carry out the transmission operation by COUNT value ascending order: compress if disposed head, then each PDCP SDU Executive Head is compressed; Each PDCP SDU is carried out encryption; The corresponding PDCP PDU that processing is obtained is submitted to the RLC sublayer and transmits.
(3) SRB (Signaling Radio Bearer, Signaling Radio Bearer)
Next_PDCP_TX_SN and TX_HFN are set to 0, the COUNT state of value before promptly removing;
Abandon that all have PDCP SDU waiting for transmission and PDCP PDU in the buffering area;
Bring into use and rebuild encryption and protection algorithm integrallty and the corresponding key that disposes by high level in the upright process.
In LTE eats dishes without rice or wine total protocol TS36.300, for changeing before the packet, and the PDCP PDU of target eNB transmission, following regulation is arranged:
In handoff procedure, source eNB (evolved Node B, evolved base station) can change the PDCP SDU of down direction before target eNB, the PDCP SDU scope of preceding commentaries on classics and UE side in rebuilding upright process, retransmit or the PDCP SDU scope of transmission consistent; At down direction, the PDCP SDU that has changeed before target eNB has been transmitted earlier transmits the PDCP SDU from Serving GW (gateway) again.
In the agreement TS36.322 of LTE RLC sublayer, the operation for transmitter side PDCP PDU (RLC SDU) has following regulation:
Send the TM entity, send UM entity and AM entity transmitter side existence transmission buffering area, be used to store RLC SDU from the PDCP sublayer; When receiving that the PDCP sublayer abandons the indication of certain RLC SDU, only when this RLC SDU did not also begin to transmit, perhaps send UM RLC entity abandoned this RLC SDU to the transmitter side of AM RLC entity.
This shows; Though stipulated the associative operation of submitting of PDCP PDU between PDCP sublayer and the RLC sublayer (RLC SDU) at present; And confirm that buffering area is sent in existence in the RLC sublayer, but the concrete implementation of the transfer of data between PDCP sublayer and the RLC sublayer is not stipulated.
Summary of the invention
The embodiment of the invention provides the data transmission method and the device of a kind of PDCP of being applied to entity and RLC inter-entity, in order to realize the transfer of data of PDCP sublayer to the RLC sublayer.
The data transmission method that is applied to PDCP entity and RLC inter-entity that the embodiment of the invention provides comprises:
The PDCP entity obtains corresponding PDCP PDU through protocol processes after receiving and coming from high-rise PDCP SDU;
The PDCP entity is transferred to the RLC entity with said PDCP PDU.
The data transmission device that is applied to PDCP entity and RLC inter-entity that the embodiment of the invention provides comprises: PDCP entity and RLC entity;
The PDCP entity, be used to receive come from high-rise PDCP SDU after, obtain corresponding PDCP PDU through protocol processes, and said PDCP PDU be transferred to the RLC entity;
The RLC entity is used to receive the PDCP PDU of PDCP entity transmission, and obtains corresponding RLC PDU through protocol processes.
In the data transmission method that is applied to PDCP entity and RLC inter-entity that another embodiment of the present invention provides, the PDCP sublayer is provided with the transmission buffering area, and this method comprises:
After the PDCP entity receives and comes from high-rise PDCP SDU, leave said PDCP SDU in the PDCP sublayer and send in the buffering area;
Receive the RLC SDU request of RLC entity transmission when said PDCP entity after, according to said RLC SDU request, the pairing PDCP PDU of PDCP SDU that the PDCP sublayer is sent in the buffering area is transferred to the RLC entity.
The data transmission device that is applied to PDCP entity and RLC inter-entity that another embodiment of the present invention provides comprises: buffer location, PDCP entity and RLC entity are sent in the PDCP sublayer, wherein:
Buffer location is sent in the PDCP sublayer, is used to store as yet not the PDCP SDU to the corresponding PDCP PDU of RLC entity transmission;
The PDCP entity, be used to receive come from high-rise PDCP SDU after, leave said PDCP SDU in the PDCP sublayer and send in the buffer location; And after the RLC SDU request that receives the transmission of RLC entity, according to said RLC SDU request, the pairing PDCP PDU of PDCP SDU that the PDCP sublayer is sent in the buffer location is transferred to the RLC entity;
The RLC entity is used for sending RLC SDU request to the PDCP entity; And, the PDCP PDU of reception PDCP entity transmission.
Compared with prior art, the present invention has following useful technique effect:
After receiving higher layer PDCP SDU, the PDCP PDU that this PDCP SDU is corresponding is transferred to the RLC entity through the PDCP entity, thereby has realized that the PDCP sublayer is to the operation of the data packet transmission between the RLC sublayer.
Description of drawings
One of sketch map of transfer of data flow process between PDCP sublayer that Fig. 1 provides for the embodiment of the invention and the RLC sublayer;
The LTE that Fig. 2 provides for embodiment of the invention layer two the transmission buffering area of eating dishes without rice or wine disposed sketch map;
Between PDCP sublayer that Fig. 3 provides for the embodiment of the invention and the RLC sublayer two of the sketch map of transfer of data flow process;
Between PDCP sublayer that Fig. 4 provides for the embodiment of the invention and the RLC sublayer three of the sketch map of transfer of data flow process;
One of structural representation of the data transmission device that is applied to PDCP entity and RLC inter-entity that Fig. 5 provides for the embodiment of the invention;
Two of the structural representation of the data transmission device that is applied to PDCP entity and RLC inter-entity that Fig. 6 provides for the embodiment of the invention.
Embodiment
Prior art has been stipulated the associative operation of submitting of PDCP PDU between PDCP sublayer and the RLC sublayer (RLC SDU); And confirm that buffering area is sent in existence in the RLC sublayer; But do not stipulate what PDCP PDU (RLC SDU) specifically constantly be delivered to the RLC sublayer from the PDCP sublayer at; And how PDCP sublayer and RLC sublayer to plan the transmission buffering area at transmitter side, and promptly whether the PDCP sublayer exists the transmission buffering area, and the data cached scope in PDCP sublayer and RLC sublayer.The embodiment of the invention provides the data transmission mechanism that is applied between PDCP sublayer and RLC sublayer in order to address the above problem.
Be described in detail in the face of the embodiment of the invention down.
In following examples of the present invention, the functional module that will belong to PDCP sublayer and execution PDCP sublayer relevant treatment is called the PDCP entity, and the functional module that will belong to RLC sublayer and execution RLC sublayer relevant treatment is called the RLC entity.
The moment so that PDCP PDU is submitted to the RLC sublayer in the PDCP sublayer is distinguished, and the embodiment of the invention provides following two kinds of implementations:
Scheme (one): the PDCP entity directly carries on an agreement and goes up predetermined process behind the PDCP SDU that receives from high-rise (rrc layer or IP layer), and the corresponding PDCP PDU that obtains is submitted to the RLC sublayer;
Scheme (two): the PDCP entity is behind the PDCP SDU that receives from high-rise (rrc layer or IP layer); Leaving PDCP SDU in its PDCP sublayer of safeguarding sends in the buffering area; After the RLC SDU request of receiving from the RLC sublayer; Again the PDCP SDU in definite scope is carried on an agreement and go up predetermined process, the corresponding PDCP PDU that obtains is submitted to the RLC entity.
When the PDCP entity adopts such scheme () to RLC entity transmission data; The RLC entity is being received (the Media Access Control from MAC; The medium access control) after the transmission opportunity of the sublayer notice; Directly send the RLC SDU assembling RLC PDU in the buffering area, and be handed down to media access control sublayer based on its RLC sublayer of safeguarding.Its complete process flow can be as shown in Figure 1, may further comprise the steps:
Step 101, the PDCP entity receives the PDCP SDU from high-rise (rrc layer or IP layer).
Step 102, PDCP entity obtain corresponding PDCP PDU according to the PDCP SDU that protocol processes receives.
The PDCP PDU that step 103, PDCP entity obtain after with protocol processes is submitted to the RLC entity.
Step 104, the RLC entity is stored in the RLC SDU that receives (being PDCP PDU) in the transmission buffering area of RLC sublayer.
So far, accomplished the process that the PDCP entity is transferred to PDCP PDU RLC sublayer buffering area.When the MAC entity carried out data dispatch (like the MAC entity of eNB side) or carry out priority of logical channels processing (like the MAC entity of UE side), this flow process also can may further comprise the steps:
The notice of transmission opportunity is sent according to scheduling result or result in step 105 ~ 106, MAC entity to the RLC entity.
Step 107 ~ 108, the RLC entity sends the RLC SDU assembling RLC PDU in the buffering area based on the RLC sublayer, and the RLC PDU after will assembling is delivered to the MAC entity.
Further, the transmission buffering area also can have been safeguarded in the PDCP sublayer, when adopting RLC AM pattern, and a transmission buffering area backup of depositing the PDCP sublayer of original PDCP SDU copy that the PDCP entity also will be corresponding with the PDCP PDU that is submitted to the RLC sublayer.The RLC entity also will copy the initial transmission RLC PDU that is submitted to media access control sublayer to the retransmission buffer backup of RLC sublayer; Partly delete when receiving the corresponding RLC PDU or the RLC PDU that back up in retransmission buffer after the data receiver confirms the correct ACK that receives, otherwise be retained in this retransmission buffer.The RLC entity sends confirmation to the PDCP entity after receiving ACK, and PDCP entity deletion PDCP after receiving the affirmation information that the RLC entity sends sends the corresponding PDCP SDU that backs up in the buffering area in the sublayer.
This data passes mode need not consider the SDU to PDCP sublayer request RLC, so handling process is simple when assembling and transmission RLC PDU, processing delay is little.
To the situation that adopts RLC AM pattern in the such scheme (), and to the situation of employing scheme (two), the embodiment of the invention has proposed the eat dishes without rice or wine transmission buffering area deployment scheme of layer two of a kind of LTE, and is as shown in Figure 2.PDCP sublayer and RLC sublayer have been safeguarded the transmission buffering area respectively.The transmission buffering area that safeguard the PDCP sublayer is used to deposit the PDCP SDU that does not submit corresponding PDCP PDU as yet to the RLC sublayer; Under RLC AM pattern; Also can be used for depositing and submit corresponding PDCP PDU to the RLC sublayer, but the RLC sublayer PDCP SDU of its correct transmission unconfirmed also.The transmission buffering area that safeguard the RLC sublayer is used to deposit PDCP PDU (being RLC SDU) or the PDCP PDU fragment of submitting the PDCP sublayer; These RLC SDU or RLC SDU fragment also do not begin to be submitted to media access control sublayer and carry out HARQ (Hybrid Automatic Repeat Request;, mix automatic repeat requests) and transmission.Further, under RLC AM pattern, retransmission buffer has also been safeguarded in the RLC sublayer, is used to deposit sent but confirmed the RLC PDU or the RLC PDU fragment of correct transmission by the opposite end.
Based on above-mentioned transmission buffering area deployment scheme, the PDCP sublayer can realize that UE stresses to set up process, turns over journey before the eNB side data, and submits the process of PDCP PDU to the RLC sublayer as required; The process of RLC PDU can be realized assembling and issuing based on the request of media access control sublayer in the RLC sublayer.
When the PDCP entity adopts such scheme (two) to RLC entity transmission data; The RLC entity is after the transmission opportunity notice of receiving from the MAC entity; When encapsulation RLC PDU,, confirm whether the RLC SDU that sends in the buffering area satisfies the current data volume requirement that issues according to data volume to be issued.If meet the demands, then the RLC entity is directly assembled RLC PDU based on the RLC SDU that sends in the buffering area, and is handed down to the MAC entity.If do not meet the demands, then the RLC entity is to the RLC SDU of the certain data volume of PDCP sublayer request.After receiving the PDCP PDU that the PDCP entity issues (RLC SDU), the RLC entity is put into the transmission buffering area with these RLC SDU, and based on the RLC SDU assembling RLC PDU that sends in the buffering area, is handed down to the MAC entity then.
Wherein, the RLC entity confirms when the RLC SDU data volume that the PDCP entity is asked, dual mode is arranged:
Mode (one): the RLC entity is at every turn to the RLC SDU of PDCP entity requests predetermined amount of data;
Mode (two): the RLC entity is at every turn to the RLC SDU of PDCP entity requests desired data amount.
When employing mode () is confirmed the data volume of RLC SDU; The RLC entity is at every turn to the RLC SDU of PDCP entity requests predetermined amount of data; Its complete process flow is as shown in Figure 3; The PDCP entity leaves PDCP SDU in the transmission buffering area of PDCP sublayer after receiving the PDCP SDU from high-rise (rrc layer or IP layer).When the MAC entity carried out data dispatch (like the MAC entity of eNB side) or carry out priority of logical channels processing (like the MAC entity of UE side), this flow process also can may further comprise the steps:
Step 301 ~ 302, MAC entity are sent the transmission opportunity notice according to scheduling result or result to RLC.
Step 303, RLC entity confirm according to the data volume of sending the corresponding RLC PDU of RLC SDU to be issued in the buffering area whether the RLC SDU that sends buffering area satisfies the current data volume requirement that issues.If satisfy, then the RLC entity is submitted RLC PDU based on the RLC SDU assembling RLC PDU that sends in the buffering area to media access control sublayer, finishes this data transmission and processing flow process then; If do not satisfy, change step 304.
During practical implementation; The RLC entity can be according to the data volume of sending the corresponding RLC PDU of RLC SDU to be issued in the buffering area; And the transmission opportunity notice data volume of being asked, whether judge the former more than or equal to the latter, if; Think that then sending RLC SDU in the buffering area satisfies and currently issue the data volume requirement, otherwise do not meet the demands.
Step 304, the RLC entity is to the RLC SDU of PDCP sublayer request predetermined amount of data.Wherein, the tentation data method for determination of amount has following several kinds:
(1) predetermined amount of data is the buffer size of hardware supports;
(2) predetermined amount of data is the maximum of the media access control sublayer single request data volume of RLC sublayer statistics;
(3) predetermined amount of data is the mean value of the media access control sublayer single request data volume of RLC sublayer statistics;
Step 305 ~ 306, the PDCP entity is determined PDCP PDU data volume that is handed down to the RLC entity and the PDCP PDU that issues this data volume according to the PDCP PDU data volume of PDCP SDU correspondence in the transmission buffering area and the predetermined amount of data that the RLC entity is asked.
During practical implementation, if the data volume of the PDCP PDU of all PDCP SDU correspondences of storing in the transmission buffering area of PDCP sublayer then issues the corresponding PDCP PDU of all PDCP SDU less than this predetermined amount of data; If the data volume of the PDCP PDU that the PDCP SDU that stores in the transmission buffering area of PDCP sublayer is corresponding is not less than this predetermined amount of data; Then the PDCP entity does not exceed under the situation of this predetermined amount of data in the data volume of the PDCP PDU that guarantees to issue, makes the data volume that issues near this predetermined amount of data as far as possible.
Step 307 ~ 309, the RLC entity is put into the transmission buffering area with the PDCP PDU that receives (RLC SDU), and sends the RLC SDU assembling RLC PDU in the buffering area based on the RLC sublayer, and the RLC PDU after the assembling is delivered to the MAC entity.
If the RLC entity finds that after the PDCP PDU that receives (RLC SDU) being put into the transmission buffering area RLC SDU of this transmission buffering area does not still satisfy MAC data quantity transmitted that entity is asked; Then the RLC entity can be once more to the RLC SDU of PDCP entity requests predetermined amount of data; After this handling process can repeat no more at this as stated.
Further, when adopting RLC AM pattern, a transmission buffering area backup of depositing the PDCP sublayer of original PDCP SDU copy that the PDCP entity also will be corresponding with the PDCP PDU that is submitted to the RLC sublayer.The RLC entity also will copy the RLC PDU that is submitted to media access control sublayer to the retransmission buffer backup of RLC sublayer; Partly delete when receiving the corresponding RLC PDU or the RLC PDU that back up in retransmission buffer after the data receiver confirms the correct ACK that receives, otherwise be retained in this retransmission buffer.The RLC entity sends confirmation to the PDCP entity after receiving ACK, and PDCP entity deletion PDCP after receiving the affirmation information that the RLC entity sends sends the corresponding PDCP SDU that backs up in the buffering area in the sublayer.
This data passes mode RLC sublayer possibly remain indivedual RLC SDU or RLC SDU fragment at the RLC SDU that assembles and issue the request of handling basically in the RLC PDU process in sending buffering area, less to the demand of sending buffering area.Generation is rebuild immediately when the PDCP sublayer, and the PDCP SDU that send in the buffering area PDCP sublayer can continue transmission (UE side) or carry out preceding commentaries on classics (eNB side), and the probability of generation data-bag lost is less.
When employing mode (two) is confirmed the data volume of RLC SDU; The RLC entity is at every turn to the RLC SDU of PDCP entity requests desired data amount; Its complete process flow is as shown in Figure 4; The PDCP entity leaves PDCP SDU in the transmission buffering area of PDCP sublayer after receiving the PDCP SDU from high-rise (rrc layer or IP layer).When the MAC entity carried out data dispatch (like the MAC entity of eNB side) or carry out priority of logical channels processing (like the MAC entity of UE side), this flow process also can may further comprise the steps:
Step 401 ~ 402, MAC entity are sent the transmission opportunity notice according to scheduling result or result to RLC.
Step 403, RLC entity confirm according to the data volume of sending the corresponding RLC PDU of RLC SDU to be issued in the buffering area whether the RLC SDU that sends buffering area satisfies the current data volume requirement that issues.If satisfy, then the RLC entity is submitted RLC PDU based on the RLC SDU assembling RLC PDU that sends in the buffering area to media access control sublayer, finishes this data transmission and processing flow process then; If do not satisfy, change step 404.
Step 404, the RLC entity is to the RLC SDU of PDCP entity requests desired data amount.
During practical implementation, the data volume that the RLC entity can be asked the MAC entity with send buffering area in difference between the data volume of the corresponding RLC PDU of current all RLC SDU, as to the RLC of PDCP entity requests SDU data volume.
Step 405 ~ 406, the PDCP entity is determined PDCP PDU data volume that is handed down to the RLC entity and the PDCP PDU that issues this data volume according to the PDCP PDU data volume of PDCP SDU correspondence in the transmission buffering area and the desired data amount that the RLC entity is asked.
During practical implementation, if the data volume of the PDCP PDU of all PDCP SDU correspondences of storing in the transmission buffering area of PDCP sublayer then issues the corresponding PDCP PDU of all PDCP SDU less than this predetermined amount of data; If the data volume of the PDCP PDU that the PDCP SDU that stores in the transmission buffering area of PDCP sublayer is corresponding is not less than this predetermined amount of data; Then the PDCP entity is not less than under the situation of this predetermined amount of data in the data volume of the PDCP PDU that guarantees to issue, makes the data volume that issues near this predetermined amount of data as far as possible.
Step 407 ~ 409, the RLC entity is put into the transmission buffering area with the PDCP PDU that receives (RLC SDU), and sends the RLC SDU assembling RLC PDU in the buffering area based on the RLC sublayer, and the RLC PDU after the assembling is delivered to the MAC entity.
Further, when adopting RLC AM pattern, a transmission buffering area backup of depositing the PDCP sublayer of original PDCP SDU copy that the PDCP entity also will be corresponding with the PDCP PDU that is submitted to the RLC sublayer.The RLC entity also will copy the RLC PDU that is submitted to media access control sublayer to the retransmission buffer backup of RLC sublayer; Partly delete when receiving the corresponding RLC PDU or the RLC PDU that back up in retransmission buffer after the data receiver confirms the correct ACK that receives, otherwise be retained in this retransmission buffer.The RLC entity sends confirmation to the PDCP entity after receiving ACK, and PDCP entity deletion PDCP after receiving the affirmation information that the RLC entity sends sends the corresponding PDCP SDU that backs up in the buffering area in the sublayer.
The advantage of this data passes mode and employing mode () confirm that the data passes mode of data volume of RLC SDU is identical.
Can find out through above flow process; The embodiment of the invention has been filled up the eat dishes without rice or wine blank of the mechanism of transmission data between PDCP sublayer and the RLC sublayer of LTE in the prior art; Guaranteed under the controlled prerequisite of time delay and buffer memory expense, to realize the complete interaction flow between PDCP sublayer and the RLC sublayer.
Based on identical technical conceive, the embodiment of the invention also provides the data transmission device of a kind of PDCP of being applied to entity and RLC inter-entity.
Referring to Fig. 5, be the data transmission device sketch map that is applied to PDCP entity and RLC inter-entity that the embodiment of the invention provides, this device can be applicable to such scheme (); Can be applicable in the network equipment; Also can be applicable in the user side equipment, as shown in the figure, this device can comprise: the PDCP entity (or is claimed the PDCP processing module; As follows) 501, the RLC entity (or claims RLC processing module; As follows) 502, also can comprise the transmission buffer location and the retransmission buffer unit that are positioned at the RLC sublayer, wherein:
When adopting RLC AM pattern, said apparatus also can comprise PDCP sublayer transmission buffer location 503, is positioned at the PDCP sublayer, is used for buffer memory is confirmed correct transmission by the RLC entity PDCP SDU.
Further, RLC entity 502 can send the RLC SDU assembling RLC PDU in the buffer location according to the RLC sublayer after receiving the transmission opportunity notice of MAC entity, and the RLC PDU of assembling is sent to the MAC entity.
Referring to Fig. 6, be the data transmission device sketch map that is applied to PDCP entity and RLC inter-entity that the embodiment of the invention provides, this device can be applicable to such scheme (two); Can be applicable in the network equipment; Also can be applicable in the user side equipment, as shown in the figure, this device can comprise: buffer location 601, PDCP entity 602, RLC entity 603 are sent in the PDCP sublayer; Also can comprise the transmission buffer location and the retransmission buffer unit that are positioned at the RLC sublayer, wherein:
Be used for asking in said RLC SDU request under the situation of RLC SDU of predetermined amount of data; The pairing PDCP PDU of PDCP SDU data volume in the RLC SDU of the predetermined amount of data that PDCP entity 602 can be asked according to said RLC SDU request and the PDCP sublayer transmission buffer location 601; Confirm to be transferred to the PDCP PDU data volume of RLC entity 603, and the PDCP PDU of corresponding data amount is transferred to RLC entity 603.
Particularly, the size of said predetermined amount of data is: the buffer size of hardware supports; Perhaps, the maximum of the MAC entity single request data volume of RLC sublayer statistics; Perhaps, the mean value of the MAC entity single request data volume of RLC sublayer statistics.
Be used for asking in said RLC SDU request under the situation of RLC SDU of current transmission opportunity desired data amount; The PDCP PDU data volume of the PDCP SDU correspondence in the buffer location is sent in the RLC SDU of the current transmission opportunity desired data amount that PDCP entity 602 can be asked according to said RLC SDU request and PDCP sublayer; Confirm to be transferred to the PDCP PDU data volume of RLC entity 603, and the PDCP PDU of corresponding data amount is transferred to RLC entity 603.
Particularly, RLC entity 603 can receive that the MAC entity sends the transmission opportunity notice after, send said RLC SDU request.
The PDCP sublayer is sent buffer location 601 and also can be used for: when adopting RLC AM pattern, buffer memory is not confirmed the PDCP SDU of correct transmission by the RLC entity.
Through the description of above execution mode, those skilled in the art can be well understood to the present invention and can realize by the mode that software adds essential general hardware platform, can certainly pass through hardware, but the former is better execution mode under a lot of situation.Based on such understanding; The part that technical scheme of the present invention contributes to prior art in essence in other words can be come out with the embodied of software product; This computer software product is stored in the storage medium, comprise some instructions with so that a station terminal equipment (can be mobile phone, personal computer; Server, the perhaps network equipment etc.) carry out the described method of each embodiment of the present invention.
The above only is a preferred implementation of the present invention; Should be pointed out that for those skilled in the art, under the prerequisite that does not break away from the principle of the invention; Can also make some improvement and retouching, these improvement and retouching also should be regarded as protection scope of the present invention.
Claims (16)
1. data transmission method that is applied to PDCP entity and RLC inter-entity is characterized in that this method comprises:
Packet data convergence protocol PDCP entity obtains corresponding PDCP protocol Data Unit PDU through protocol processes after receiving and coming from high-rise PDCP service data unit SDU;
The PDCP entity is transferred to Radio Link control RLC entity with said PDCP PDU.
2. the method for claim 1 is characterized in that, the PDCP sublayer is provided with the transmission buffering area;
When adopting RLC to confirm the AM pattern, the PDCP entity will not confirmed that by the RLC entity PDCP SDU of correct transmission is stored in the transmission buffering area of PDCP sublayer.
3. a data transmission device that is applied to PDCP entity and RLC inter-entity is characterized in that, comprising: PDCP entity and RLC entity;
The PDCP entity, be used to receive come from high-rise PDCP SDU after, obtain corresponding PDCP PDU through protocol processes, and said PDCP PDU be transferred to the RLC entity;
The RLC entity is used to receive the PDCP PDU of PDCP entity transmission, and obtains corresponding RLC PDU through protocol processes.
4. device as claimed in claim 3 is characterized in that, also comprises:
Buffer location is sent in the PDCP sublayer, is used for when adopting RLC AM pattern, and buffer memory is not confirmed the PDCP SDU of correct transmission by the RLC entity.
5. a data transmission method that is applied to PDCP entity and RLC inter-entity is characterized in that the PDCP sublayer is provided with the transmission buffering area, and this method comprises:
After the PDCP entity receives and comes from high-rise PDCP SDU, leave said PDCP SDU in the PDCP sublayer and send in the buffering area;
Receive the RLC SDU request of RLC entity transmission when said PDCP entity after, according to said RLC SDU request, the pairing PDCP PDU of PDCP SDU that the PDCP sublayer is sent in the buffering area is transferred to the RLC entity.
6. method as claimed in claim 5 is characterized in that, said RLC SDU request is used for asking the RLC SDU of predetermined amount of data;
Said PDCP entity is asked according to said RLC SDU, and the pairing PDCP PDU of PDCP SDU that the PDCP sublayer is sent in the buffering area is transferred to the RLC entity, is specially:
The PDCP entity sends the pairing PDCP PDU of the PDCP SDU data volume in the buffering area according to the RLC SDU and the PDCP sublayer of the predetermined amount of data that said RLC SDU request is asked; Confirm to be transferred to the PDCP PDU data volume of RLC entity, and the PDCP PDU of corresponding data amount is transferred to the RLC entity.
7. method as claimed in claim 6 is characterized in that, the size of said predetermined amount of data is:
The buffer size of hardware supports; Or
The maximum of the MAC entity single request data volume of RLC sublayer statistics; Or
The mean value of the MAC entity single request data volume of RLC sublayer statistics.
8. method as claimed in claim 5 is characterized in that, said RLC SDU request is used for asking the RLC SDU of current transmission opportunity desired data amount;
The corresponding PDCP PDU of PDCP SDU that said PDCP entity sends the PDCP sublayer in the buffering area is transferred to the RLC entity, is specially:
The PDCP entity sends the corresponding PDCP PDU data volume of PDCP SDU in the buffering area according to the RLC SDU and the PDCP sublayer of the current transmission opportunity desired data amount that said RLC SDU request is asked; Confirm to be transferred to the PDCP PDU data volume of RLC entity, and the PDCP PDU of corresponding data amount is transferred to the RLC entity.
9. like the described method of one of claim 5-8, it is characterized in that, the RLC SDU request that said RLC entity sends is this RLC entity receive that the MAC entity sends transmission opportunity notice back send.
10. method as claimed in claim 5 is characterized in that, when adopting RLC AM pattern, said PDCP sublayer is sent buffering area and also is used for buffer memory is not confirmed correct transmission by the RLC entity PDCP SDU.
11. a data transmission device that is applied to PDCP entity and RLC inter-entity is characterized in that this device comprises: buffer location, PDCP entity and RLC entity are sent in the PDCP sublayer, wherein:
Buffer location is sent in the PDCP sublayer, is used to store as yet not the PDCP SDU to the corresponding PDCP PDU of RLC entity transmission;
The PDCP entity, be used to receive come from high-rise PDCP SDU after, leave said PDCP SDU in the PDCP sublayer and send in the buffer location; And after the RLC SDU request that receives the transmission of RLC entity, according to said RLC SDU request, the pairing PDCP PDU of PDCP SDU that the PDCP sublayer is sent in the buffer location is transferred to the RLC entity;
The RLC entity is used for sending RLC SDU request to the PDCP entity; And, the PDCP PDU of reception PDCP entity transmission.
12. device as claimed in claim 11 is characterized in that, said RLC SDU request is used for asking the RLC SDU of predetermined amount of data;
Said PDCP entity specifically is used for; The pairing PDCP PDU of PDCP SDU data volume in the RLC SDU of the predetermined amount of data that request is asked according to said RLC SDU and the PDCP sublayer transmission buffer location; Confirm to be transferred to the PDCP PDU data volume of RLC entity, and the PDCP PDU of corresponding data amount is transferred to the RLC entity.
13. device as claimed in claim 12 is characterized in that, the size of said predetermined amount of data is:
The buffer size of hardware supports; Or
The maximum of the MAC entity single request data volume of RLC sublayer statistics; Or
The mean value of the MAC entity single request data volume of RLC sublayer statistics.
14. device as claimed in claim 11 is characterized in that, said RLC SDU request is used for asking the RLC SDU of current transmission opportunity desired data amount;
Said PDCP entity specifically is used for; The PDCP PDU data volume of the PDCP SDU correspondence in the buffer location is sent in the RLC SDU of the current transmission opportunity desired data amount that request is asked according to said RLC SDU and PDCP sublayer; Confirm to be transferred to the PDCP PDU data volume of RLC entity, and the PDCP PDU of corresponding data amount is transferred to the RLC entity.
15., it is characterized in that said RLC entity specifically is used for like the described device of one of claim 11-14, receive that the MAC entity sends the transmission opportunity notice after, send said RLC SDU request.
16. device as claimed in claim 11 is characterized in that, said PDCP sublayer is sent buffer location and also is used for, and when adopting RLC AM pattern, buffer memory is not confirmed the PDCP SDU of correct transmission by the RLC entity.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201110298677.4A CN102395156B (en) | 2011-09-28 | 2011-09-28 | Data transmission methods and device applied between packet data convergence protocol (PDCP) entity and radio link control (RLC) entity |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201110298677.4A CN102395156B (en) | 2011-09-28 | 2011-09-28 | Data transmission methods and device applied between packet data convergence protocol (PDCP) entity and radio link control (RLC) entity |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN102395156A true CN102395156A (en) | 2012-03-28 |
| CN102395156B CN102395156B (en) | 2015-05-20 |
Family
ID=45862342
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201110298677.4A Active CN102395156B (en) | 2011-09-28 | 2011-09-28 | Data transmission methods and device applied between packet data convergence protocol (PDCP) entity and radio link control (RLC) entity |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102395156B (en) |
Cited By (22)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106101285A (en) * | 2016-08-22 | 2016-11-09 | 中国移动通信有限公司研究院 | Distributed data transport method and device based on TM rlc protocol, TM RLC entity |
| CN106161676A (en) * | 2015-03-27 | 2016-11-23 | 瑞昱半导体股份有限公司 | The control circuit of wireless user equipment |
| CN106304154A (en) * | 2016-09-30 | 2017-01-04 | 京信通信技术(广州)有限公司 | The data transmission method of a kind of PDCP entity and PDCP entity |
| CN107027136A (en) * | 2016-02-01 | 2017-08-08 | 中兴通讯股份有限公司 | The method and device of data processing |
| CN107241409A (en) * | 2017-06-05 | 2017-10-10 | 武汉虹信通信技术有限责任公司 | For RLC in LTE and the data transmission method of adjacent layer |
| CN107332648A (en) * | 2017-06-23 | 2017-11-07 | 京信通信系统（中国）有限公司 | Data repeating method, device, storage medium and its computer equipment |
| WO2017198236A1 (en) * | 2016-05-18 | 2017-11-23 | 中兴通讯股份有限公司 | Data transmission method, device, and system |
| CN107708153A (en) * | 2017-09-29 | 2018-02-16 | 重庆邮电大学 | A kind of radio modem ascending packet data processing method |
| CN108282248A (en) * | 2017-01-05 | 2018-07-13 | 电信科学技术研究院 | A kind of data transmission method, network side equipment and user equipment |
| WO2018166517A1 (en) * | 2017-03-17 | 2018-09-20 | 华为技术有限公司 | Data transmission method, data transmitting device, and data receiving device |
| WO2019024535A1 (en) * | 2017-07-31 | 2019-02-07 | Oppo广东移动通信有限公司 | Data processing method and product related thereto |
| CN109428684A (en) * | 2017-08-30 | 2019-03-05 | 中国移动通信有限公司研究院 | A kind of data transmission method, RLC entity and PDCP entity |
| CN109788516A (en) * | 2017-11-13 | 2019-05-21 | 普天信息技术有限公司 | The confirmation method and equipment of downlink data in a kind of LTE handoff procedure |
| CN109936858A (en) * | 2019-02-20 | 2019-06-25 | 武汉虹信通信技术有限责任公司 | A kind of radio link control data processing method and system |
| CN110011763A (en) * | 2018-01-05 | 2019-07-12 | 维沃移动通信有限公司 | Parameter setting method and device |
| CN110417531A (en) * | 2013-10-30 | 2019-11-05 | 交互数字专利控股公司 | Wireless transmitter/receiver unit WTRU and the method executed by WTRU |
| CN110612686A (en) * | 2017-06-02 | 2019-12-24 | 摩托罗拉移动有限责任公司 | Determining data available for transmission |
| CN111757548A (en) * | 2019-03-29 | 2020-10-09 | 华为技术有限公司 | Communication method and communication device |
| CN112399471A (en) * | 2020-10-23 | 2021-02-23 | 紫光展锐(重庆)科技有限公司 | Data caching method and related device |
| CN112953849A (en) * | 2019-12-10 | 2021-06-11 | 中国移动通信有限公司研究院 | Data volume processing method, device and medium |
| WO2022227998A1 (en) * | 2021-04-30 | 2022-11-03 | 华为技术有限公司 | Data transmission method and apparatus |
| US11637763B2 (en) | 2013-10-30 | 2023-04-25 | Interdigital Patent Holdings, Inc. | Connectivity robustness in wireless systems |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101600229A (en) * | 2009-07-24 | 2009-12-09 | 中国科学院计算技术研究所 | Air-link resources dispatching method in a kind of wireless communication system |
| US20100135202A1 (en) * | 2007-09-18 | 2010-06-03 | Sung Duck Chun | Method for qos guarantees in a multilayer structure |
| CN101729524A (en) * | 2008-11-03 | 2010-06-09 | 大唐移动通信设备有限公司 | Data processing method, data processing device, RLC entity and PDCP entity |
-
2011
- 2011-09-28 CN CN201110298677.4A patent/CN102395156B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20100135202A1 (en) * | 2007-09-18 | 2010-06-03 | Sung Duck Chun | Method for qos guarantees in a multilayer structure |
| CN101809948A (en) * | 2007-09-18 | 2010-08-18 | Lg电子株式会社 | A method for QoS guarantees in a multilayer structure |
| CN101729524A (en) * | 2008-11-03 | 2010-06-09 | 大唐移动通信设备有限公司 | Data processing method, data processing device, RLC entity and PDCP entity |
| CN101600229A (en) * | 2009-07-24 | 2009-12-09 | 中国科学院计算技术研究所 | Air-link resources dispatching method in a kind of wireless communication system |
Non-Patent Citations (1)
| Title |
|---|
| 3GPP ORG: "PDCP & RLC Behavior at Non-Handover RLC Re-establishment R2-084083", 《3GPP》, 22 August 2008 (2008-08-22) * |
Cited By (41)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US11924075B2 (en) | 2013-10-30 | 2024-03-05 | Interdigital Patent Holdings, Inc. | Connectivity robustness in wireless systems |
| CN110417531A (en) * | 2013-10-30 | 2019-11-05 | 交互数字专利控股公司 | Wireless transmitter/receiver unit WTRU and the method executed by WTRU |
| US11637763B2 (en) | 2013-10-30 | 2023-04-25 | Interdigital Patent Holdings, Inc. | Connectivity robustness in wireless systems |
| CN106161676A (en) * | 2015-03-27 | 2016-11-23 | 瑞昱半导体股份有限公司 | The control circuit of wireless user equipment |
| CN107027136A (en) * | 2016-02-01 | 2017-08-08 | 中兴通讯股份有限公司 | The method and device of data processing |
| WO2017133595A1 (en) * | 2016-02-01 | 2017-08-10 | 中兴通讯股份有限公司 | Data processing method and apparatus |
| CN107027136B (en) * | 2016-02-01 | 2020-11-20 | 中兴通讯股份有限公司 | Data processing method and device |
| WO2017198236A1 (en) * | 2016-05-18 | 2017-11-23 | 中兴通讯股份有限公司 | Data transmission method, device, and system |
| CN107404734A (en) * | 2016-05-18 | 2017-11-28 | 中兴通讯股份有限公司 | Data transmission method for uplink, apparatus and system |
| CN106101285A (en) * | 2016-08-22 | 2016-11-09 | 中国移动通信有限公司研究院 | Distributed data transport method and device based on TM rlc protocol, TM RLC entity |
| CN106101285B (en) * | 2016-08-22 | 2019-08-13 | 中国移动通信有限公司研究院 | Distributed data transport method and device, TM RLC entity based on TM rlc protocol |
| CN106304154B (en) * | 2016-09-30 | 2019-07-26 | 京信通信系统（中国）有限公司 | A kind of data transmission method and PDCP entity of PDCP entity |
| CN106304154A (en) * | 2016-09-30 | 2017-01-04 | 京信通信技术(广州)有限公司 | The data transmission method of a kind of PDCP entity and PDCP entity |
| CN108282248A (en) * | 2017-01-05 | 2018-07-13 | 电信科学技术研究院 | A kind of data transmission method, network side equipment and user equipment |
| WO2018166517A1 (en) * | 2017-03-17 | 2018-09-20 | 华为技术有限公司 | Data transmission method, data transmitting device, and data receiving device |
| CN110612686A (en) * | 2017-06-02 | 2019-12-24 | 摩托罗拉移动有限责任公司 | Determining data available for transmission |
| CN110612686B (en) * | 2017-06-02 | 2022-10-28 | 摩托罗拉移动有限责任公司 | Determining data available for transmission |
| CN107241409A (en) * | 2017-06-05 | 2017-10-10 | 武汉虹信通信技术有限责任公司 | For RLC in LTE and the data transmission method of adjacent layer |
| CN107332648B (en) * | 2017-06-23 | 2021-01-15 | 京信通信系统（中国）有限公司 | Data retransmission method and device, storage medium and computer equipment thereof |
| CN107332648A (en) * | 2017-06-23 | 2017-11-07 | 京信通信系统（中国）有限公司 | Data repeating method, device, storage medium and its computer equipment |
| CN110192403A (en) * | 2017-07-31 | 2019-08-30 | Oppo广东移动通信有限公司 | Data processing method and Related product |
| CN110192403B (en) * | 2017-07-31 | 2024-02-13 | Oppo广东移动通信有限公司 | Data processing method and related product |
| TWI680664B (en) * | 2017-07-31 | 2019-12-21 | 大陸商Ｏｐｐｏ廣東移動通信有限公司 | A method and device for data processing |
| CN111107015B (en) * | 2017-07-31 | 2021-03-05 | Oppo广东移动通信有限公司 | Data processing method and related product |
| CN111107015A (en) * | 2017-07-31 | 2020-05-05 | Oppo广东移动通信有限公司 | Data processing method and related product |
| WO2019024535A1 (en) * | 2017-07-31 | 2019-02-07 | Oppo广东移动通信有限公司 | Data processing method and product related thereto |
| US10944681B2 (en) | 2017-07-31 | 2021-03-09 | Guangdong Oppo Mobile Telecommunications Corp., Ltd. | Methods and devices for data processing |
| CN109428684B (en) * | 2017-08-30 | 2020-11-27 | 中国移动通信有限公司研究院 | Data transmission method, RLC entity and PDCP entity |
| CN109428684A (en) * | 2017-08-30 | 2019-03-05 | 中国移动通信有限公司研究院 | A kind of data transmission method, RLC entity and PDCP entity |
| CN107708153A (en) * | 2017-09-29 | 2018-02-16 | 重庆邮电大学 | A kind of radio modem ascending packet data processing method |
| CN107708153B (en) * | 2017-09-29 | 2019-11-15 | 重庆邮电大学 | A kind of radio modem ascending packet data processing method |
| CN109788516A (en) * | 2017-11-13 | 2019-05-21 | 普天信息技术有限公司 | The confirmation method and equipment of downlink data in a kind of LTE handoff procedure |
| CN109788516B (en) * | 2017-11-13 | 2021-04-16 | 普天信息技术有限公司 | Method and device for confirming downlink data in LTE switching process |
| CN110011763A (en) * | 2018-01-05 | 2019-07-12 | 维沃移动通信有限公司 | Parameter setting method and device |
| CN109936858B (en) * | 2019-02-20 | 2022-03-25 | 武汉虹信科技发展有限责任公司 | Method and system for processing wireless link control data |
| CN109936858A (en) * | 2019-02-20 | 2019-06-25 | 武汉虹信通信技术有限责任公司 | A kind of radio link control data processing method and system |
| CN111757548A (en) * | 2019-03-29 | 2020-10-09 | 华为技术有限公司 | Communication method and communication device |
| CN112953849A (en) * | 2019-12-10 | 2021-06-11 | 中国移动通信有限公司研究院 | Data volume processing method, device and medium |
| CN112953849B (en) * | 2019-12-10 | 2023-05-09 | 中国移动通信有限公司研究院 | Data volume processing method, device and medium |
| CN112399471A (en) * | 2020-10-23 | 2021-02-23 | 紫光展锐(重庆)科技有限公司 | Data caching method and related device |
| WO2022227998A1 (en) * | 2021-04-30 | 2022-11-03 | 华为技术有限公司 | Data transmission method and apparatus |
Also Published As
| Publication number | Publication date |
|---|---|
| CN102395156B (en) | 2015-05-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102395156B (en) | Data transmission methods and device applied between packet data convergence protocol (PDCP) entity and radio link control (RLC) entity | |
| US11057797B2 (en) | Method and device for processing information | |
| RU2461147C2 (en) | Method of processing radio protocol in mobile communication system and mobile communication transmitter | |
| CN102307084B (en) | Methods and apparatuses for improving buffer status triggering mechanism in wireless communictions system | |
| TWI233309B (en) | Inter node B serving HS-DSCH cell change mechanism in high speed wireless communication system | |
| CN101043301B (en) | Data rearrangement and recombination method in wireless communication system and its base station | |
| US8817806B2 (en) | Method and apparatus for flow control between RLC and PDCP in a communication | |
| CN108282248B (en) | Data transmission method, network side equipment and user equipment | |
| CN103782569B (en) | Data processing equipment and method | |
| WO2018006674A1 (en) | Data processing method and apparatus | |
| CN101039170B (en) | Method for supporting packet retransmission division cascade | |
| US20040151154A1 (en) | Data transmission confirmation in a wireless communication system | |
| RU2012151318A (en) | METHOD FOR EASY TRANSFER OF MOBILE COMMUNICATION DEVICE | |
| KR20130100674A (en) | Mobile system and method for controlling packet thereof | |
| WO2017185941A1 (en) | Data transmission method and relevant device | |
| US8837310B2 (en) | Method and system for determining an end time of uplink back propagation | |
| TW201014433A (en) | Method used in evolved mobile telecommunications system, method used in user equipment, evolved mobile telecommunications system, and user equipment | |
| CN109076475B (en) | Method and system for maintaining synchronization in connectionless transmission | |
| CN101442398A (en) | Method for handling radio bearer messages during reset and reestablishment in a wireless system | |
| CN101267440B (en) | No damage relocation method and system | |
| CN103179614B (en) | The method of transmitting pdcp data unit to upper layer | |
| CN101647257A (en) | Retransmission request transmitting method and receiving side device | |
| CN107005560A (en) | A kind of data transmission method for uplink, data receiver method and relevant device | |
| CN104683017A (en) | Satellite mobile communication RLC layer AM mode transmission method | |
| CN104836648A (en) | Method for fast retransmission and feedback of RLC AM mode |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CP01 | Change in the name or title of a patent holder |
Address after: 100191 No. 40, Haidian District, Beijing, Xueyuan Road Patentee after: CHINA ACADEMY OF TELECOMMUNICATIONS TECHNOLOGY Address before: 100191 No. 40, Haidian District, Beijing, Xueyuan Road Patentee before: CHINA ACADEMY OF TELECOMMUNICATIONS TECHNOLOGY |
|
| CP01 | Change in the name or title of a patent holder | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20210531 Address after: 100085 1st floor, building 1, yard 5, Shangdi East Road, Haidian District, Beijing Patentee after: DATANG MOBILE COMMUNICATIONS EQUIPMENT Co.,Ltd. Address before: 100191 No. 40, Haidian District, Beijing, Xueyuan Road Patentee before: CHINA ACADEMY OF TELECOMMUNICATIONS TECHNOLOGY |
|
| TR01 | Transfer of patent right |