CN103874232B - Semi-static scheduling resources method for releasing and equipment - Google Patents
Semi-static scheduling resources method for releasing and equipment Download PDFInfo
- Publication number
- CN103874232B CN103874232B CN201210552135.XA CN201210552135A CN103874232B CN 103874232 B CN103874232 B CN 103874232B CN 201210552135 A CN201210552135 A CN 201210552135A CN 103874232 B CN103874232 B CN 103874232B
- Authority
- CN
- China
- Prior art keywords
- user terminal
- data unit
- base station
- protocol data
- counter
- 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.)
- Expired - Fee Related
Links
Landscapes
- Mobile Radio Communication Systems (AREA)
Abstract
This application discloses a kind of semi-static scheduling resources method for releasing and equipment.Methods described includes：Receive user terminal and pass through the packet transmitted by Physical Uplink Shared Channel, do not include the quantity of the protocol Data Unit of service data unit in the counters count protocol Data Unit of base station, when the quantity of protocol Data Unit of the counter of base station for not including service data unit in protocol Data Unit reaches threshold value, the scheduling authorization of triggering release user terminal；Methods described also includes：After explicit release order is sent to user terminal, by the counter O reset of the base station synchronous with the holding of the counter of user terminal, explicit to release order for the scheduling authorization for discharging user terminal, the counter of user terminal is used to count the quantity for the protocol Data Unit for not including service data unit in protocol Data Unit by user terminal.The continuous releasing semi-static scheduling resources of user terminal can be prevented or cause PUSCH transmission mistake.
Description
Technical field
The application is related to the communications field, more particularly to semi-static scheduling resources method for releasing and equipment.
Background technology
In communication system, carry out data transmission in order that the user terminal in cell results in running time-frequency resource, just need
It is scheduled.Scheduling point dynamic dispatching and semi-persistent scheduling（Semi-PersistentScheduling, SPS）, wherein, half
In static scheduling, the delivery mode of semi-static scheduling resources has two kinds, implicit release and explicit release.In service ending,
Send and explicitly release order to indicate releasing semi-static scheduling resources from base station to user terminal.When the semi-static tune of user terminal
After degree resource is released successfully, that is, enter the quiet period of communication, quiet period represents that user terminal enters the non-air time.If aobvious
Formula release is unsuccessful, then user terminal may proceed to send protocol Data Unit on authorized running time-frequency resource（Protocol
Data Unit, PDU）In not include service data unit（Service Data Unit, SDU）Packet（I.e.：Sky bag）.
In semi-static scheduling resources scheduling, user terminal and base station are all to count not include the association of service data unit by counter
Discuss data cell.If the statistics for the counter that user terminal passes through itself finds there is multiple in the packet that user terminal is sent
Do not include the protocol Data Unit of service data unit, then can cause the implicit release of user terminal, if base station passes through itself
The statistics of counter find to have in the packet that user terminal is sent and multiple do not include the protocol data list of service data unit
Member, then can cause base station to send display again and release order to user terminal, to ensure that user terminal can successfully discharge money
Source, so as to avoid user terminal from mistakenly occupying semi-static scheduling resources always.Base station is also possible to because other reasonses think user
Terminal sends display and released order.
But, under existing protocol, after explicit release, do not have the counting to the counter and user terminal of base station
The processing method of device.So, under the prior art, usually there is such situation：（1）The counter of base station does not reset and used
The counter O reset of family terminal, the counter of base station is had reached after specific threshold value, and base station sends display release and referred to again
Order, causes semi-static scheduling resources to be continuously released by.（2）The counter O reset of base station and the counter of user terminal is not clear
Zero, it will cause the implicit releasing semi-static scheduling resources of user terminal after the counter of user terminal reaches specific threshold,
If but base station needs to restart scheduling user terminal before this, it is not known that user terminal has released semi-persistent scheduling
Resource, so as to cause Physical Uplink Shared Channel（PUSCH, Physical Uplink Shared Channel）Error of transmission.
The content of the invention
The application is mainly solving the technical problems that offer semi-static scheduling resources method for releasing and equipment, can prevent from using
The continuous releasing semi-static scheduling resources of family terminal and cause PUSCH transmission mistake.
In order to solve the above technical problems, the application first aspect provides a kind of semi-static scheduling resources method for releasing, including
Following steps：User terminal is received by the packet transmitted by Physical Uplink Shared Channel, wherein, the packet includes association
Discuss data cell；Do not include the protocol Data Unit of service data unit in protocol Data Unit described in the counters count of base station
Quantity, the counter of the base station is used to not include the agreement number of the service data unit in the protocol Data Unit
When reaching threshold value according to the quantity of unit, the scheduling authorization of the triggering release user terminal；Methods described also includes：To described
It is after user terminal transmission is explicitly released order, the counter of the base station synchronous with the holding of the counter of user terminal is clear
Zero, described explicitly to release order for the scheduling authorization for discharging the user terminal, the counter of the user terminal is described
User terminal is used to count the quantity for the protocol Data Unit for not including service data unit in the protocol Data Unit.
With reference in a first aspect, in the first possible embodiment of the application first aspect, by the meter with user terminal
Number device is kept after the synchronous counter O reset by base station, in addition to：Uplink semi-persistent is sent to the user terminal
Scheduling authorization order is to activate the user terminal；Receive the user terminal and pass through the number transmitted by Physical Uplink Shared Channel
According to bag, and restart the statistics of the counter of the base station.
In order to solve the above technical problems, the application second aspect also provides a kind of semi-persistent scheduling mandate method for releasing, bag
Include following steps：Packet is sent to base station by Physical Uplink Shared Channel, wherein, the packet includes protocol data list
Member；By not including the protocol Data Unit of service data unit in protocol Data Unit described in the counters count of user terminal
Quantity, the counter of the user terminal is used to not include the association of the service data unit in the protocol Data Unit
When the quantity of view data cell reaches threshold value, the scheduling authorization of the triggering release user terminal；Methods described also includes：Receive
Base station send it is explicit release order, the scheduling authorization of the user terminal is discharged based on explicit release order, and will be with
The counter of base station keeps the counter O reset of the synchronous user terminal, and the counter of the base station is used for by the base station
Count the quantity for the protocol Data Unit for not including service data unit in the protocol Data Unit.
With reference to second aspect, in the first possible embodiment of the application second aspect, the meter by with base station
Number device is kept after the counter O reset of the synchronous user terminal, in addition to：Receive the uplink semi-persistent transmitted by base station
Scheduling authorization order is to activate user terminal；Packet is sent to base station by Physical Uplink Shared Channel, and restarts institute
State the statistics of the counter of user terminal.
With reference to the first possible embodiment of second aspect, second of possible embodiment party of the application second aspect
In formula, the uplink semi-persistent scheduling authorization command transmitted by the reception base station is included with activating user terminal：User terminal enters
Enter quiet period and wait uplink semi-persistent scheduling authorization command transmitted by base station to be received；As up half transmitted by reception base station
After static scheduling authorization command, user terminal is activated.
In order to solve the above technical problems, the application third aspect provides a kind of base station, including：Receiving module, statistical module
And dump block；The receiving module is used to receive the packet transmitted by user terminal, wherein, the packet includes association
Data cell is discussed, the receiving module sends the packet to the statistical module；The statistical module is used to receive described
Packet, counts the quantity for the protocol Data Unit for not including service data unit in the protocol Data Unit, and described
When the quantity for not including the protocol Data Unit of the service data unit in protocol Data Unit reaches threshold value, triggering release institute
State the scheduling authorization of user terminal；The dump block is used for after explicit release order is sent to the user terminal, will be with
The counter of user terminal keeps the counter O reset of the synchronous base station, and explicit release order is used to discharge the use
The scheduling authorization of family terminal, the counter of the user terminal is used to count in the protocol Data Unit by the user terminal
The quantity of the protocol Data Unit of service data unit is not included.
With reference to the third aspect, in the first possible embodiment of the application third aspect, the base station also includes hair
Module is sent, the sending module is used to send uplink semi-persistent scheduling authorization command to activate the user to the user terminal
Terminal；The receiving module is additionally operable to receive the user terminal by the packet transmitted by Physical Uplink Shared Channel, and
Restart the statistics of the counter of the base station.
In order to solve the above technical problems, the application fourth aspect provides a kind of user terminal, including sending module, statistics mould
Block and receiving module；The sending module is used to send packet to base station by Physical Uplink Shared Channel, wherein, it is described
Packet includes protocol Data Unit；The statistical module is used for protocol data list described in the counters count by user terminal
Do not include the quantity of the protocol Data Unit of service data unit in member, and not including the clothes in the protocol Data Unit
When the quantity of the protocol Data Unit for data cell of being engaged in reaches threshold value, the scheduling authorization of the triggering release user terminal；It is described
Receiving module is used to receive explicitly releasing order for base station transmission, based on the explicit release user terminal that releases order
Scheduling authorization, and by the counter O reset of the user terminal synchronous with the holding of the counter of base station, the counting of the base station
Device is used to count the quantity for the protocol Data Unit for not including service data unit in the protocol Data Unit by the base station.
With reference to fourth aspect, in the first possible embodiment of the application fourth aspect, the user terminal is also wrapped
Active module is included, the active module is used to receive the uplink semi-persistent scheduling authorization command transmitted by base station to activate user's end
End；The sending module is additionally operable to send packet to base station by Physical Uplink Shared Channel, and restarts the user
The statistics of the counter of terminal.
With reference to the first possible embodiment of fourth aspect, second of possible embodiment party of the application fourth aspect
In formula, the active module is used to make user terminal enter quiet period and wait uplink semi-persistent scheduling transmitted by base station to be received
Authorization command, after the uplink semi-persistent scheduling authorization command transmitted by base station is received, activates user terminal.
Such scheme is not by the way that after explicit release order is sent to user terminal, unified order statistics includes service data list
The counter of the user terminal of the protocol Data Unit of member or the counter O reset of base station, so as to prevent that base station and/or user are whole
Mistakenly continuously statistics does not include the number of the protocol Data Unit of service data unit at end, user terminal can be prevented continuously to release
Put semi-static scheduling resources or cause PUSCH transmission mistake.
Brief description of the drawings
Fig. 1 is the structural representation that the application semi-static scheduling resources discharge the embodiment of system one；
Fig. 2 is the flow chart of the embodiment of the application semi-static scheduling resources method for releasing one；
Fig. 3 is the flow chart of another embodiment of the application semi-static scheduling resources method for releasing；
Fig. 4 is the flow chart of the application semi-persistent scheduling mandate method for releasing a further embodiment；
Fig. 5 is the flow chart of the another embodiment of the application semi-persistent scheduling mandate method for releasing；
Fig. 6 is the interaction figure of the application semi-persistent scheduling mandate method for releasing base station and user terminal；
Fig. 7 is the structural representation of the embodiment of the application base station one；
Fig. 8 is the structural representation of the embodiment of the application user terminal one；
Fig. 9 is the structural representation of the application base station a further embodiment；
Figure 10 is the structural representation of the application user terminal a further embodiment.
Embodiment
In describing below, in order to illustrate rather than in order to limit, it is proposed that such as particular system structure, interface, technology it
The detail of class, thoroughly to understand the application.However, it will be clear to one skilled in the art that there is no these specific
The application can also be realized in the other embodiment of details.In other situations, omit to well-known device, circuit with
And the detailed description of method, in case unnecessary details hinders the description of the present application.
Refering to Fig. 1, Fig. 1 is the structural representation that the application semi-static scheduling resources discharge the embodiment of system one.This reality
Applying the semi-static scheduling resources release system of mode includes：Base station 110 and user terminal 120.Wherein, base station 110 and user
It can be communicated wirelessly between terminal 120.
Base station 110 covers a range of cell, and the user terminal 120 in cell can be scheduled.Base station 110
When being scheduled, running time-frequency resource is distributed in turn for the user terminal 120 that needs resource to be transmitted in turn.Obtain running time-frequency resource
User terminal 120 i.e. be transmitted using the running time-frequency resource.After the transmission of user terminal 120 data are finished, user is whole
End 120 discharges scheduling authorization, is used so that the running time-frequency resource is released into another user.
Refering to Fig. 2, Fig. 2 is the flow chart of the embodiment of the application semi-static scheduling resources method for releasing one.This embodiment party
The semi-static scheduling resources method for releasing of formula comprises the following steps：
S201：Base station receives user terminal by the packet transmitted by Physical Uplink Shared Channel, wherein, packet bag
Include protocol Data Unit.
Provided according to agreement, be referred to as service data unit into the not processed data of each sublayer, by sub-layer processes
The data for forming specific format afterwards are referred to as protocol Data Unit.So, the protocol Data Unit that this layer is formed is next layer
Service data unit.Such as, in Long Term Evolution（LTE, Long Term Evolution）In agreement, MAC（MediaAccess
Contrl）Sublayer is RLC（Radio Link Contrl）Next layer of sublayer, the service data unit of media access control sublayer is exactly RLC
The protocol Data Unit of sublayer, MAC, which forms the service data unit, becomes the agreement number of this layer after the specific format of this layer
According to unit.Therefore, when no progress data communication, service data unit is not included in protocol Data Unit；Carrying out data
During communication, protocol Data Unit includes service data unit.So, base station receives the packet transmitted by user terminal
In, protocol Data Unit potentially includes service data unit, it is also possible to not including service data unit.Thus, if agreement number
Do not include service data unit according to continuous in unit, then it is considered that without progress data communication.
S202：Do not include the protocol data list of service data unit in protocol Data Unit described in the counters count of base station
The quantity of member.
Inside of base station is provided with the counter with the counter synchronisation of user terminal, is used in the counters count of user terminal
When not including the protocol Data Unit quantity of service data unit in the protocol Data Unit that family terminal is sent, the counting of base station
Do not include the agreement of service data unit in the protocol Data Unit that the user terminal that device synchronization accounting base-station is received is sent
Data cell quantity.If not including the protocol data list of service data unit in the counters count protocol Data Unit of base station
The quantity of member reaches threshold value, the scheduling authorization of the counter triggering release user terminal of base station；If the counters count of base station
The quantity for not including service data unit in protocol Data Unit is not reaching to threshold value, proceeds between base station and user terminal
Normal communication.Wherein, threshold value is that base station is configured according to actual use situation.
S203：Base station, will be synchronous with the holding of the counter of user terminal after explicit release order is sent to user terminal
Base station counter O reset.
Do not include service data list in the protocol Data Unit that the user terminal that service ending or base station are received is sent
When the protocol Data Unit quantity of member reaches threshold value of setting etc., triggering base station sends to user terminal and explicitly released order.
Wherein, explicitly release order for the scheduling authorization for discharging user terminal.Explicitly released order to user terminal transmission base station
Afterwards, the scheduling authorization of user terminal is discharged so that user terminal enters quiet period, will be synchronous with the holding of the counter of user terminal
Base station counter O reset.Because the counter of base station and the counter holding of user terminal are synchronous, so, the counting of base station
After device is reset, the counter of user terminal equally can also be reset, to ensure that the counter of base station and the counter of user terminal are protected
Hold consistent.
Such scheme is not by the way that after explicit release order is sent to user terminal, unified order statistics includes service data list
Member protocol Data Unit base station counter or user terminal counter O reset, so, base station will not mistakenly will clearly
The quantity of the protocol Data Unit not comprising service data unit before zero is added up, and reaches threshold value in accumulative quantity
When, send explicitly release order again, cause continuous releasing semi-static scheduling resources, and, user terminal will not mistakenly by
The quantity of the protocol Data Unit not comprising service data unit before clearing is added up, and reaches threshold value in accumulative quantity
When, implicit releasing semi-static scheduling resources, if but base station need to restart scheduling user terminal before this, it is not known that use
Family terminal has released semi-static scheduling resources, so as to cause PUSCH transmission mistake.
Refering to Fig. 3, Fig. 3 is the flow chart of another embodiment of the application semi-static scheduling resources method for releasing.This implementation
The semi-static scheduling resources method for releasing of mode includes：
S301：Base station receives user terminal by the packet transmitted by Physical Uplink Shared Channel, wherein, packet bag
Include protocol Data Unit.
Provided according to agreement, be referred to as service data unit into the not processed data of each sublayer, by sub-layer processes
The data for forming specific format afterwards are referred to as protocol Data Unit.So, the protocol Data Unit that this layer is formed is next layer
Service data unit.Such as, in Long Term Evolution agreement, media access control sublayer is next layer of rlc sublayer, the service number of media access control sublayer
It is exactly the protocol Data Unit of rlc sublayer according to unit, MAC becomes after the service data unit to be formed to the specific format of this layer
This layer of protocol Data Unit.Therefore, when no progress data communication, service data list is not included in protocol Data Unit
Member；When carrying out data communication, protocol Data Unit includes service data unit.So, base station receives user terminal institute
In the packet of transmission, protocol Data Unit potentially includes service data unit, it is also possible to not including service data unit.Cause
And, do not include service data unit if continuous in protocol Data Unit, it is considered that without progress data communication.
S302：Do not include the protocol data list of service data unit in protocol Data Unit described in the counters count of base station
The quantity of member.
Inside of base station is provided with the counter with the counter synchronisation of user terminal, is used in the counters count of user terminal
When not including the protocol Data Unit quantity of service data unit in the protocol Data Unit that family terminal is sent, the counting of base station
Do not include the agreement of service data unit in the protocol Data Unit that the user terminal that device synchronization accounting base-station is received is sent
Data cell quantity.If not including the protocol data list of service data unit in the counters count protocol Data Unit of base station
The quantity of member reaches threshold value, the scheduling authorization of the counter triggering release user terminal of base station；If the counters count of base station
The quantity for not including service data unit in protocol Data Unit is not reaching to threshold value, proceeds between base station and user terminal
Normal communication.Wherein, threshold value is that base station is configured according to actual use situation.
S303：Base station, will be synchronous with the holding of the counter of user terminal after explicit release order is sent to user terminal
Base station counter O reset.
Do not wrapped in the protocol Data Unit that the user terminal that service ending or base station are received is sent
When the protocol Data Unit quantity for including service data unit reaches threshold value of setting etc., triggering base station is whole to user
End sends and explicitly released order.Wherein, explicitly release order for the scheduling authorization for discharging user terminal.Base station is whole to user
After end transmission is explicitly released order, the scheduling authorization of user terminal is discharged so that user terminal enters quiet period, will be whole with user
The counter at end keeps the counter O reset of synchronous base station.Because the counter of base station and the counter of user terminal keep same
Step, so, after the counter O reset of base station, the counter of user terminal equally can also be reset, with ensure the counter of base station with
The counter of user terminal is consistent.
S304：Base station sends uplink semi-persistent scheduling authorization command to activate user terminal to user terminal.
After user terminal receives explicit release order, user terminal enters quiet period.If base station needs again
Scheduling user terminal, then base station need to user terminal send uplink semi-persistent scheduling authorization command to activate user terminal, lay equal stress on
The statistics of the new counter for starting user terminal.
S305：Base station receives user terminal by the packet transmitted by Physical Uplink Shared Channel, and restarts base
The statistics for the counter stood.
User terminal is received after uplink semi-persistent scheduling authorization command, in dispatching cycle, shared by physical uplink
Channel sends packet to user terminal.Base station receives user terminal and passes through the packet transmitted by Physical Uplink Shared Channel
Afterwards, the statistics of the counter of restarting base station so that the counter of base station and the counter synchronisation of user terminal.
Refering to Fig. 4, Fig. 4 is the flow chart of the application semi-persistent scheduling mandate method for releasing a further embodiment.This implementation
The semi-persistent scheduling mandate method for releasing of mode comprises the following steps：
S401：User terminal sends packet by Physical Uplink Shared Channel to base station.
Provided according to agreement, be referred to as service data unit into the not processed data of each sublayer, by sub-layer processes
The data for forming specific format afterwards are referred to as protocol Data Unit.So, the protocol Data Unit that this layer is formed is next layer
Service data unit.Such as, in Long Term Evolution agreement, media access control sublayer is next layer of rlc sublayer, the service number of media access control sublayer
It is exactly the protocol Data Unit of rlc sublayer according to unit, MAC becomes after the service data unit to be formed to the specific format of this layer
This layer of protocol Data Unit.Therefore, when no progress data communication, service data list is not included in protocol Data Unit
Member；When carrying out data communication, protocol Data Unit includes service data unit.So, user terminal passes through physical uplink
In the packet that shared channel is sent, protocol Data Unit potentially includes service data unit, it is also possible to not including service data
Unit.Thus, do not include service data unit if continuous in protocol Data Unit, it is considered that leading to without data are carried out
News.
S402：Do not include service data unit in the counters count protocol Data Unit that user terminal passes through user terminal
Protocol Data Unit quantity.
User terminal is internally provided with the counter with the counter synchronisation of base station, is used in the counters count of user terminal
When not including the protocol Data Unit quantity of service data unit in the protocol Data Unit that family terminal is sent, the counting of base station
Do not include the agreement of service data unit in the protocol Data Unit that the user terminal that device synchronization accounting base-station is received is sent
Data cell quantity.If not including the agreement number of service data unit in the counters count protocol Data Unit of user terminal
Threshold value is reached according to the quantity of unit, triggering user terminal implicitly discharges scheduling authorization；If the counters count association of user terminal
The quantity for not including service data unit in view data cell is not reaching to threshold value, proceeds just between base station and user terminal
Normal open is interrogated.Wherein, threshold value is that user terminal is configured according to actual use situation.
S403：User terminal receives the explicit of base station transmission and released order, based on the explicit release user terminal that releases order
Scheduling authorization, and by the counter O reset of the user terminal synchronous with the holding of the counter of base station.
Do not include service data list in the protocol Data Unit that the user terminal that service ending or base station are received is sent
When the protocol Data Unit quantity of member reaches threshold value of setting etc., triggering base station sends to user terminal and explicitly released order.
Wherein, explicitly release order for the scheduling authorization for discharging user terminal.User terminal receives the explicit release of base station transmission
After instruction, scheduling authorization is discharged, it is into quiet period, the counter of the user terminal synchronous with the holding of the counter of base station is clear
Zero.Because the counter of user terminal and the counter holding of base station are synchronous, so, after the counter O reset of user terminal, base
The counter stood equally can also be reset, to ensure that the counter of user terminal and the counter of base station are consistent.
Refering to Fig. 5, Fig. 5 is the flow chart of the another embodiment of the application semi-persistent scheduling mandate method for releasing.This implementation
The semi-persistent scheduling mandate method for releasing of mode comprises the following steps：
S501：User terminal sends packet by Physical Uplink Shared Channel to base station.
Provided according to agreement, be referred to as service data unit into the not processed data of each sublayer, by sub-layer processes
The data for forming specific format afterwards are referred to as protocol Data Unit.So, the protocol Data Unit that this layer is formed is next layer
Service data unit.Such as, in Long Term Evolution agreement, media access control sublayer is next layer of rlc sublayer, the service number of media access control sublayer
It is exactly the protocol Data Unit of rlc sublayer according to unit, MAC becomes after the service data unit to be formed to the specific format of this layer
This layer of protocol Data Unit.Therefore, when no progress data communication, service data list is not included in protocol Data Unit
Member；When carrying out data communication, protocol Data Unit includes service data unit.So, user terminal passes through physical uplink
In the packet that shared channel is sent, protocol Data Unit potentially includes service data unit, it is also possible to not including service data
Unit.Thus, do not include service data unit if continuous in protocol Data Unit, it is considered that leading to without data are carried out
News.
S502：Do not include service data unit in the counters count protocol Data Unit that user terminal passes through user terminal
Protocol Data Unit quantity.
User terminal is internally provided with the counter with the counter synchronisation of base station, is used in the counters count of user terminal
When not including the protocol Data Unit quantity of service data unit in the protocol Data Unit that family terminal is sent, the counting of base station
Do not include the agreement of service data unit in the protocol Data Unit that the user terminal that device synchronization accounting base-station is received is sent
Data cell quantity.If not including the agreement number of service data unit in the counters count protocol Data Unit of user terminal
Threshold value is reached according to the quantity of unit, triggering user terminal implicitly discharges scheduling authorization；If the counters count association of user terminal
The quantity for not including service data unit in view data cell is not reaching to threshold value, proceeds just between base station and user terminal
Normal open is interrogated.Wherein, threshold value is that user terminal is configured according to actual use situation.
S503：User terminal receives the explicit of base station transmission and released order, based on the explicit release user terminal that releases order
Scheduling authorization, and by the counter O reset of the user terminal synchronous with the holding of the counter of base station.
Do not include service data list in the protocol Data Unit that the user terminal that service ending or base station are received is sent
When the protocol Data Unit quantity of member reaches threshold value of setting etc., triggering base station sends to user terminal and explicitly released order.
Wherein, explicitly release order for the scheduling authorization for discharging user terminal.User terminal receives the explicit release of base station transmission
After instruction, scheduling authorization is discharged, it is into quiet period, the counter of the user terminal synchronous with the holding of the counter of base station is clear
Zero.Because the counter of user terminal and the counter holding of base station are synchronous, so, after the counter O reset of user terminal, base
The counter stood equally can also be reset, to ensure that the counter of user terminal and the counter of base station are consistent.
S504：User terminal enters quiet period and waits uplink semi-persistent scheduling authorization command transmitted by base station to be received.
User terminal enters after quiet period, the uplink semi-persistent scheduling authorization command transmitted by base station to be received such as always.
S505：After user terminal receives the uplink semi-persistent scheduling authorization command transmitted by base station, user terminal is activated.
If base station needs scheduling user terminal again, base station need to send uplink semi-persistent scheduling mandate to user terminal
Order, after uplink semi-persistent scheduling authorization command is sent, the statistics of the counter of base station restarting base station.User terminal connects
The uplink semi-persistent scheduling authorization command transmitted by base station is received, user terminal is activated.
S506：User terminal sends packet by Physical Uplink Shared Channel to base station, and restarts user terminal
Counter statistics.
User terminal sends packet by Physical Uplink Shared Channel to base station, and restarts the counting of user terminal
The statistics of device, to ensure that the counter of user terminal and the counter of base station are consistent.
Refering to Fig. 6, Fig. 6 is the interaction figure of the application semi-persistent scheduling mandate method for releasing base station and user terminal.Such as Fig. 6
It is shown,
Base station to user terminal send first semi-static scheduling resources authorization command, user terminal receive it is semi-static
After scheduling resource authorization command, data are sent to base station in dispatching cycle.Send packet during, if user terminal to
Base station, which have sent, does not include the packet of service data unit in protocol Data Unit, then the counter of base station and user terminal is each
The quantity of the protocol Data Unit of service data unit is not included from statistics protocol Data Unit.Received in service ending or base station
To the protocol Data Unit that is sent of user terminal in do not include the protocol Data Unit quantity of service data unit and reach and set
During fixed threshold value etc., triggering base station sends to user terminal and explicitly released order, and by the counter O reset of base station.User is whole
Hold receive transmitted by base station it is explicit release order after, into quiet period, and by the counter O reset of user terminal.This
Afterwards, user terminal waits base station to send uplink semi-persistent scheduling authorization command always, to activate user terminal.When base station is to user
Terminal is sent after uplink semi-persistent scheduling authorization command, the statistics of the counter of base station restarting base station.And user terminal exists
Receive after uplink semi-persistent scheduling authorization command, activate user terminal and restart the statistics of the counter of user terminal.
In dispatching cycle, user terminal sends data to base station again.During packet is sent, if user terminal is sent out to base station
Having sent does not include the packet of service data unit in protocol Data Unit, then the counter of base station and user terminal each from
Zero starts not including the quantity of the protocol Data Unit of service data unit in statistics protocol Data Unit again.
Refering to Fig. 7, Fig. 7 is the structural representation of the embodiment of the application base station one.The base station of present embodiment includes：Connect
Receive module 710, statistical module 720, dump block 730 and sending module 740.
Receiving module 710 is used to receive the packet transmitted by user terminal, wherein, packet includes protocol data list
Member.Such as, provided according to agreement, be referred to as service data unit into the not processed data of each sublayer, by sub-layer processes
The data for forming specific format afterwards are referred to as protocol Data Unit.So, the protocol Data Unit that this layer is formed is next layer
Service data unit.Such as, in Long Term Evolution agreement, media access control sublayer is next layer of rlc sublayer, the service number of media access control sublayer
It is exactly the protocol Data Unit of rlc sublayer according to unit, MAC becomes after the service data unit to be formed to the specific format of this layer
This layer of protocol Data Unit.Therefore, when no progress data communication, service data list is not included in protocol Data Unit
Member；When carrying out data communication, protocol Data Unit includes service data unit.So, receiving module 710 receives user
In packet transmitted by terminal, protocol Data Unit potentially includes service data unit, it is also possible to not including service data list
Member.Thus, do not include service data unit if continuous in protocol Data Unit, it is considered that without progress data communication.
Receiving module 710 sends packet to statistical module 720；
Statistical module 720 is used to not include the agreement of service data unit in received data packet, statistics protocol Data Unit
The quantity of data cell, and the quantity of the protocol Data Unit including service data unit does not reach threshold in protocol Data Unit
During value, the scheduling authorization of triggering release user terminal.Such as, inside of base station is provided with the meter with the counter synchronisation of user terminal
Number devices, do not include service data unit in the protocol Data Unit that is sent of counters count user terminal of user terminal
During protocol Data Unit quantity, the protocol data list that the user terminal that the synchronous accounting base-station of statistical module 720 is received is sent
Do not include the protocol Data Unit quantity of service data unit in member.If in the statistics protocol Data Unit of statistical module 720 not
The quantity of protocol Data Unit including service data unit reaches threshold value, the tune of the triggering release user terminal of statistical module 720
Degree is authorized；If the quantity for not including service data unit in the statistics protocol Data Unit of statistical module 720 is not reaching to threshold value,
Proceed normal communication between base station and user terminal.Wherein, threshold value is that base station is configured according to actual use situation
's.
Dump block 730 is used for after explicit release order is sent to user terminal, will be protected with the counter of user terminal
The counter O reset of the synchronous base station is held, is explicitly released order for the scheduling authorization for discharging user terminal, user terminal
Counter be used to count in protocol Data Unit the number for the protocol Data Unit for not including service data unit by user terminal
Amount.Such as, service data list is not included in the protocol Data Unit that the user terminal that service ending or base station are received is sent
When the protocol Data Unit quantity of member reaches threshold value of setting etc., triggering base station sends to user terminal and explicitly released order.
Wherein, explicitly release order for the scheduling authorization for discharging user terminal.Explicitly released order to user terminal transmission base station
Afterwards, the scheduling authorization of user terminal is discharged, dump block 730 causes user terminal to enter quiet period, by the meter with user terminal
Number device keeps the counter O reset of synchronous base station.Because the counter of base station and the counter holding of user terminal are synchronous, institute
So that after the counter O reset of base station, the counter of user terminal equally can also be reset, whole with the counter and user that ensure base station
The counter at end is consistent.
Sending module 740 is used to send uplink semi-persistent scheduling authorization command to activate user terminal to user terminal.Than
Such as, after user terminal receives explicit release order, user terminal enters quiet period.If base station needs to dispatch use again
Family terminal, then sending module 740 send uplink semi-persistent scheduling authorization command to user terminal to activate user terminal, and again
Start the statistics of the counter of user terminal.
Receiving module 710 is additionally operable to receive user terminal by the packet transmitted by Physical Uplink Shared Channel, lays equal stress on
The statistics of the new counter for starting base station.Such as, user terminal is received after uplink semi-persistent scheduling authorization command, in scheduling week
It is interim, packet is sent to user terminal by Physical Uplink Shared Channel.Receiving module 710 receives user terminal and passes through thing
Manage Uplink Shared Channel transmitted by packet after, restart base station counter statistics so that the counter of base station and
The counter synchronisation of user terminal.
Refering to Fig. 8, Fig. 8 is the structural representation of the embodiment of the application user terminal one.The user of present embodiment is whole
End includes：Sending module 810, statistical module 820, receiving module 830 and active module 840.
Sending module 810 is used to send packet to base station by Physical Uplink Shared Channel, wherein, packet includes association
Discuss data cell.Such as, provided according to agreement, be referred to as service data unit into the not processed data of each sublayer, passed through
The data that specific format is formed after sub-layer processes are referred to as protocol Data Unit.So, the protocol Data Unit that this layer is formed is
For next layer of service data unit.Such as, in Long Term Evolution agreement, media access control sublayer is next layer of rlc sublayer, media access control sublayer
Service data unit be exactly rlc sublayer protocol Data Unit, MAC forms the service data unit specific format of this layer
Become the protocol Data Unit of this layer afterwards.Therefore, when no progress data communication, service is not included in protocol Data Unit
Data cell；When carrying out data communication, protocol Data Unit includes service data unit.So, sending module 810 passes through
In the packet that Physical Uplink Shared Channel is sent, protocol Data Unit potentially includes service data unit, it is also possible to do not include
Service data unit.Thus, do not include service data unit if continuous in protocol Data Unit, it is considered that not carrying out
Data communication.
Statistical module 820 is used in the counters count protocol Data Unit by user terminal not include service data list
The quantity of the protocol Data Unit of member, and the not number of the protocol Data Unit including service data unit in protocol Data Unit
When amount reaches threshold value, the scheduling authorization of triggering release user terminal.Such as, in the counters count user terminal institute of user terminal
When not including the protocol Data Unit quantity of service data unit in the protocol Data Unit sent, the counter synchronisation system of base station
Do not include the protocol Data Unit of service data unit in the protocol Data Unit that the user terminal that meter base station is received is sent
Quantity.If not including the agreement number of service data unit in the statistics protocol Data Unit of statistical module 820 of user terminal
Threshold value is reached according to the quantity of unit, triggering user terminal implicitly discharges scheduling authorization；If in the statistical module 820 of user terminal
The quantity for not including service data unit in statistics protocol Data Unit is not reaching to threshold value, continues between base station and user terminal
Carry out normal communication.Wherein, threshold value is that user terminal is configured according to actual use situation.
Receiving module 830 is used to receive explicitly releasing order for base station transmission, whole based on the explicit release user that releases order
The scheduling authorization at end, and by the counter O reset of the user terminal synchronous with the holding of the counter of base station, the counter quilt of base station
Base station is used to count the quantity for the protocol Data Unit for not including service data unit in protocol Data Unit.Such as, in business
Do not include the protocol data list of service data unit in the protocol Data Unit that the user terminal that end or base station are received is sent
When first quantity reaches threshold value of setting etc., triggering base station sends to user terminal and explicitly released order.Wherein, explicit release refers to
Make the scheduling authorization for discharging user terminal.Receiving module 830 receive base station transmission it is explicit release order after, release is adjusted
Degree is authorized, into quiet period, by the counter O reset of the user terminal synchronous with the holding of the counter of base station.Due to user terminal
Counter it is synchronous with the counter holding of base station, so, after the counter O reset of user terminal, the counter of base station is equally
It can reset, to ensure that the counter of user terminal and the counter of base station are consistent.
Active module 840 is used to receive the uplink semi-persistent scheduling authorization command transmitted by base station to activate user terminal.
Such as, make user terminal enter quiet period and wait uplink semi-persistent scheduling authorization command transmitted by base station to be received, receiving
After uplink semi-persistent scheduling authorization command transmitted by base station, user terminal is activated.Specifically, if base station needs to dispatch again
User terminal, then base station need to user terminal send uplink semi-persistent scheduling authorization command, awarded sending uplink semi-persistent scheduling
After power order, the statistics of the counter of base station restarting base station.Active module 840 receives the uplink semi-persistent transmitted by base station
Scheduling authorization order, activates user terminal.
Sending module 810 is additionally operable to send packet to base station by Physical Uplink Shared Channel, and restarts user
The statistics of the counter of terminal.Such as, sending module 810 sends packet by Physical Uplink Shared Channel to base station, lays equal stress on
The statistics of the new counter for starting user terminal, to ensure that the counter of user terminal and the counter of base station are consistent.
Refering to Fig. 9, Fig. 9 is the structural representation of the application base station a further embodiment.The base station of present embodiment includes：
Receiver 910, processor 920 and transmitter 930.Wherein, processor 920 connects with receiver 910 and transmitter 930 respectively
Connect.
Receiver 910 is used to receive the packet transmitted by user terminal, wherein, packet includes protocol Data Unit.
Such as, provided according to agreement, be referred to as service data unit into the not processed data of each sublayer, the shape after sub-layer processes
Data into specific format are referred to as protocol Data Unit.So, the protocol Data Unit that this layer is formed is next layer of clothes
Business data cell.Such as, in Long Term Evolution agreement, media access control sublayer is next layer of rlc sublayer, the service data list of media access control sublayer
Member is exactly the protocol Data Unit of rlc sublayer, and MAC becomes this layer after the service data unit to be formed to the specific format of this layer
Protocol Data Unit.Therefore, when no progress data communication, service data unit is not included in protocol Data Unit；
When carrying out data communication, protocol Data Unit includes service data unit.So, receiver 910 receives user terminal institute
In the packet of transmission, protocol Data Unit potentially includes service data unit, it is also possible to not including service data unit.Cause
And, do not include service data unit if continuous in protocol Data Unit, it is considered that without progress data communication.
Processor 920 is used to not include the agreement number of service data unit in received data packet, statistics protocol Data Unit
According to the quantity of unit, and in protocol Data Unit, the quantity of the protocol Data Unit including service data unit does not reach threshold value
When, the scheduling authorization of triggering release user terminal, after explicit release order is sent to user terminal, by the meter with user terminal
Number device keeps the counter O reset of synchronous base station, explicitly releases order for the scheduling authorization for discharging user terminal, user is whole
The counter at end is not included the protocol Data Unit of service data unit by user terminal for counting in protocol Data Unit
Quantity.Such as, inside of base station is provided with the counter with the counter synchronisation of user terminal, in the counters count of user terminal
When not including the protocol Data Unit quantity of service data unit in the protocol Data Unit that user terminal is sent, processor
Do not include the agreement of service data unit in the protocol Data Unit that the user terminal that 920 synchronous accounting base-stations are received is sent
Data cell quantity.If not including the protocol Data Unit of service data unit in the statistics protocol Data Unit of processor 920
Quantity reach threshold value, the scheduling authorization of the triggering release user terminal of processor 920；If processor 920 counts protocol data
The quantity for not including service data unit in unit is not reaching to threshold value, proceeds positive normal open between base station and user terminal
News.Wherein, threshold value is that base station is configured according to actual use situation.The user terminal received in service ending or base station
The protocol Data Unit quantity for not including service data unit in the protocol Data Unit sent reaches threshold value of setting etc.
When, triggering base station sends to user terminal and explicitly released order.Wherein, explicitly release order for the scheduling for discharging user terminal
Authorize.Base station discharges the scheduling authorization of user terminal after explicit release order is sent to user terminal, and processor 920 causes
User terminal enters quiet period, by the counter O reset of the base station synchronous with the holding of the counter of user terminal.Due to base station
Counter is synchronous with the counter holding of user terminal, so, after the counter O reset of base station, the counter of user terminal is same
Also it can reset, to ensure that the counter of base station and the counter of user terminal are consistent.
Transmitter 930 is used to send uplink semi-persistent scheduling authorization command to activate user terminal to user terminal.Than
Such as, after user terminal receives explicit release order, user terminal enters quiet period.If base station needs to dispatch use again
Family terminal, then transmitter 930 send uplink semi-persistent scheduling authorization command to user terminal to activate user terminal, and again
Start the statistics of the counter of user terminal.
Receiver 910 is additionally operable to receive user terminal by the packet transmitted by Physical Uplink Shared Channel, and again
Start the statistics of the counter of base station.Such as, user terminal is received after uplink semi-persistent scheduling authorization command, in dispatching cycle
In, packet is sent to user terminal by Physical Uplink Shared Channel.Receiver 910 receives user terminal and passed through physically
After packet transmitted by row shared channel, the statistics of the counter of base station is restarted so that the counter of base station and user
The counter synchronisation of terminal.
Refering to Figure 10, Figure 10 is the structural representation of the application user terminal a further embodiment.The use of present embodiment
Family terminal includes：Transmitter 1010, processor 1020 and receiver 1030.Wherein, processor 1020 respectively with transmitter
1010 and receiver 1030 connect.
Transmitter 1010 is used to send packet to base station by Physical Uplink Shared Channel, wherein, packet includes association
Discuss data cell.Such as, provided according to agreement, be referred to as service data unit into the not processed data of each sublayer, passed through
The data that specific format is formed after sub-layer processes are referred to as protocol Data Unit.So, the protocol Data Unit that this layer is formed is
For next layer of service data unit.Such as, in Long Term Evolution agreement, media access control sublayer is next layer of rlc sublayer, media access control sublayer
Service data unit be exactly rlc sublayer protocol Data Unit, MAC forms the service data unit specific format of this layer
Become the protocol Data Unit of this layer afterwards.Therefore, when no progress data communication, service is not included in protocol Data Unit
Data cell；When carrying out data communication, protocol Data Unit includes service data unit.So, transmitter 1010 passes through
In the packet that Physical Uplink Shared Channel is sent, protocol Data Unit potentially includes service data unit, it is also possible to do not include
Service data unit.Thus, do not include service data unit if continuous in protocol Data Unit, it is considered that not carrying out
Data communication.
Processor 1020 is used in the counters count protocol Data Unit by user terminal not include service data list
The quantity of the protocol Data Unit of member, and the not number of the protocol Data Unit including service data unit in protocol Data Unit
When amount reaches threshold value, the scheduling authorization of triggering release user terminal.Such as, in the counters count user terminal institute of user terminal
When not including the protocol Data Unit quantity of service data unit in the protocol Data Unit sent, the counter synchronisation system of base station
Do not include the protocol Data Unit of service data unit in the protocol Data Unit that the user terminal that meter base station is received is sent
Quantity.If not including the protocol data of service data unit in the statistics protocol Data Unit of processor 1020 of user terminal
The quantity of unit reaches threshold value, and triggering user terminal implicitly discharges scheduling authorization；If united in the processor 1020 of user terminal
Meter protocol Data Unit in include service data unit quantity be not reaching to threshold value, continue between base station and user terminal into
Row normal communication.Wherein, threshold value is that user terminal is configured according to actual use situation.
Receiver 1030 is used to receive explicitly releasing order for base station transmission, based on the explicit release user terminal that releases order
Scheduling authorization, and by the counter O reset of the user terminal synchronous with the holding of the counter of base station, the counter of base station is by base
Stand for the quantity for counting the protocol Data Unit for not including service data unit in protocol Data Unit, receive transmitted by base station
Uplink semi-persistent scheduling authorization command to activate user terminal.Such as, the user terminal institute received in service ending or base station
When the protocol Data Unit quantity for not including service data unit in the protocol Data Unit sent reaches threshold value of setting etc.,
Triggering base station sends to user terminal and explicitly released order.Wherein, the scheduling for discharging user terminal of explicitly releasing order is awarded
Power.Receiver 1030 receive base station transmission it is explicit release order after, discharge scheduling authorization, will be with base station into quiet period
Counter keep the counter O reset of synchronous user terminal.Because the counter of user terminal and the counter of base station are kept
It is synchronous, so, after the counter O reset of user terminal, the counter of base station equally can also be reset, in terms of ensuring user terminal
Number device and the counter of base station are consistent.User terminal enters after quiet period, waits up half transmitted by base station to be received quiet
State scheduling authorization order, after the uplink semi-persistent scheduling authorization command transmitted by base station is received, activates user terminal.Specifically
Ground, if base station needs scheduling user terminal again, base station need to send uplink semi-persistent scheduling authorization command to user terminal,
After uplink semi-persistent scheduling authorization command is sent, the statistics of the counter of base station restarting base station.Receiver 1030 is received
Uplink semi-persistent scheduling authorization command transmitted by base station, activates user terminal.
Transmitter 1010 is additionally operable to send packet to base station by Physical Uplink Shared Channel, and it is whole to restart user
The statistics of the counter at end.Such as, transmitter sends packet by Physical Uplink Shared Channel to base station, and restarts use
The statistics of the counter of family terminal, to ensure that the counter of user terminal and the counter of base station are consistent.
Based on above-mentioned base station and user terminal, system is discharged present invention also provides a kind of semi-static scheduling resources, including
Base station and user terminal, wireless connection between the base station and the user terminal.Fig. 1 and associated description specifically are referred to, this
Place does not repeat to repeat.
Such scheme is not by the way that after explicit release order is sent to user terminal, unified order statistics includes service data list
The counter of the user terminal of the protocol Data Unit of member or the counter O reset of base station, so as to prevent that base station and/or user are whole
Mistakenly continuously statistics does not include the number of the protocol Data Unit of service data unit at end, user terminal can be prevented continuously to release
Put semi-static scheduling resources or cause PUSCH transmission mistake.
In several embodiments provided herein, it should be understood that disclosed system, apparatus and method can
To realize by another way.For example, device embodiments described above are only schematical, for example, the mould
The division of block or unit, only a kind of division of logic function can have other dividing mode when actually realizing, such as multiple
Unit or component can combine or be desirably integrated into another system, or some features can be ignored, or not perform.It is another
Point, shown or discussed coupling or direct-coupling or communication connection each other can be by some interfaces, device or
The INDIRECT COUPLING of unit or communication connection, can be electrical, machinery or other forms.
The unit illustrated as separating component can be or may not be it is physically separate, it is aobvious as unit
The part shown can be or may not be physical location, you can with positioned at a place, or can also be distributed to multiple
On NE.Some or all of unit therein can be selected to realize present embodiment scheme according to the actual needs
Purpose.
In addition, each functional unit in the application each embodiment can be integrated in a processing unit, also may be used
To be that unit is individually physically present, can also two or more units it is integrated in a unit.It is above-mentioned integrated
Unit can both be realized in the form of hardware, it would however also be possible to employ the form of SFU software functional unit is realized.
If the integrated unit is realized using in the form of SFU software functional unit and as independent production marketing or used
When, it can be stored in a computer read/write memory medium.Understood based on such, the technical scheme of the application is substantially
The part contributed in other words to prior art or all or part of the technical scheme can be in the form of software products
Embody, the computer software product is stored in a storage medium, including some instructions are to cause a computer
Equipment（Can be personal computer, server, or network equipment etc.）Or processor（processor）Perform the application each
The all or part of step of embodiment methods described.And foregoing storage medium includes：USB flash disk, mobile hard disk, read-only storage
（ROM, Read-Only Memory）, random access memory（RAM, Random Access Memory）, magnetic disc or CD
Etc. it is various can be with the medium of store program codes.
Claims (10)
1. a kind of semi-static scheduling resources method for releasing, comprises the following steps：
User terminal is received by the packet transmitted by Physical Uplink Shared Channel, wherein, the packet includes agreement number
According to unit；
Do not include the quantity of the protocol Data Unit of service data unit in protocol Data Unit described in the counters count of base station,
The counter of the base station is used to not include the protocol Data Unit of the service data unit in the protocol Data Unit
Quantity when reaching threshold value, the scheduling authorization of the triggering release user terminal；
Characterized in that, methods described also includes：
After explicit release order is sent to the user terminal, by the base station synchronous with the holding of the counter of user terminal
Counter O reset, it is described explicitly to release order for the scheduling authorization for discharging the user terminal, the meter of the user terminal
Number device is used to count not include the protocol Data Unit of service data unit in the protocol Data Unit by the user terminal
Quantity.
2. according to the method described in claim 1, it is characterised in that by the general synchronous with the holding of the counter of user terminal
After the counter O reset of base station, in addition to：
Send uplink semi-persistent scheduling authorization command to activate the user terminal to the user terminal；
The user terminal is received by the packet transmitted by Physical Uplink Shared Channel, and restarts the meter of the base station
The statistics of number device.
3. a kind of semi-persistent scheduling mandate method for releasing, comprises the following steps：
Packet is sent to base station by Physical Uplink Shared Channel, wherein, the packet includes protocol Data Unit；
By not including the protocol data list of service data unit in protocol Data Unit described in the counters count of user terminal
The quantity of member, the counter of the user terminal is used in the protocol Data Unit not include the service data unit
When the quantity of protocol Data Unit reaches threshold value, the scheduling authorization of the triggering release user terminal；
Characterized in that, methods described also includes：
Receive that base station sends it is explicit release order, discharge the scheduling of the user terminal based on explicit release order and award
Power, and by the counter O reset of the user terminal synchronous with the holding of the counter of base station, the counter of the base station is by institute
Stating base station is used to count the quantity for the protocol Data Unit for not including service data unit in the protocol Data Unit.
4. method according to claim 3, it is characterised in that described by the use synchronous with the holding of the counter of base station
After the counter O reset of family terminal, in addition to：
The uplink semi-persistent scheduling authorization command transmitted by base station is received to activate user terminal；
Packet is sent to base station by Physical Uplink Shared Channel, and restarts the system of the counter of the user terminal
Meter.
5. method according to claim 4, it is characterised in that the uplink semi-persistent scheduling transmitted by the reception base station is awarded
Power order is included with activating user terminal：
User terminal enters quiet period and waits uplink semi-persistent scheduling authorization command transmitted by base station to be received；
After the uplink semi-persistent scheduling authorization command transmitted by base station is received, user terminal is activated.
6. a kind of base station, it is characterised in that including：Receiving module, statistical module and dump block；
The receiving module is used to receive the packet transmitted by user terminal, wherein, the packet includes protocol data list
Member, the receiving module sends the packet to the statistical module；
The statistical module is used to receive the packet, and counting does not include service data unit in the protocol Data Unit
The quantity of protocol Data Unit, and do not include in the protocol Data Unit protocol Data Unit of the service data unit
Quantity when reaching threshold value, the scheduling authorization of the triggering release user terminal；
The dump block is used for after explicit release order is sent to the user terminal, will be protected with the counter of user terminal
The counter O reset of the synchronous base station is held, it is described explicitly to release order for the scheduling authorization for discharging the user terminal,
The counter of the user terminal is used to count by the user terminal does not include service data list in the protocol Data Unit
The quantity of the protocol Data Unit of member.
7. base station according to claim 6, it is characterised in that the base station also includes sending module,
The sending module is used to send uplink semi-persistent scheduling authorization command to the user terminal to activate user's end
End；
The receiving module is additionally operable to receive the user terminal by the packet transmitted by Physical Uplink Shared Channel, lays equal stress on
Newly start the statistics of the counter of the base station.
8. a kind of user terminal, it is characterised in that including sending module, statistical module and receiving module；
The sending module is used to send packet to base station by Physical Uplink Shared Channel, wherein, the packet includes
Protocol Data Unit；
The statistical module is used in protocol Data Unit described in the counters count by user terminal not include service data
The quantity of the protocol Data Unit of unit, and do not include in the protocol Data Unit agreement number of the service data unit
When reaching threshold value according to the quantity of unit, the scheduling authorization of the triggering release user terminal；
The receiving module is used to receive explicitly releasing order for base station transmission, and described use is discharged based on explicit release order
The scheduling authorization of family terminal, and by the counter O reset of the user terminal synchronous with the holding of the counter of base station, the base
The counter stood is used to count not include the protocol data list of service data unit in the protocol Data Unit by the base station
The quantity of member.
9. user terminal according to claim 8, it is characterised in that the user terminal also includes active module,
The active module is used to receive the uplink semi-persistent scheduling authorization command transmitted by base station to activate user terminal；
The sending module is additionally operable to send packet to base station by Physical Uplink Shared Channel, and restarts the user
The statistics of the counter of terminal.
10. user terminal according to claim 9, it is characterised in that the active module is used to make user terminal enter
Quiet period simultaneously waits uplink semi-persistent scheduling authorization command transmitted by base station to be received, quiet receiving up half transmitted by base station
After state scheduling authorization order, user terminal is activated.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201210552135.XA CN103874232B (en) | 2012-12-18 | 2012-12-18 | Semi-static scheduling resources method for releasing and equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201210552135.XA CN103874232B (en) | 2012-12-18 | 2012-12-18 | Semi-static scheduling resources method for releasing and equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN103874232A CN103874232A (en) | 2014-06-18 |
| CN103874232B true CN103874232B (en) | 2017-08-04 |
Family
ID=50912265
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201210552135.XA Expired - Fee Related CN103874232B (en) | 2012-12-18 | 2012-12-18 | Semi-static scheduling resources method for releasing and equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN103874232B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107211437B (en) * | 2015-02-17 | 2020-06-02 | 维沃移动通信有限公司 | Method for resource release |
| TWI622309B (en) * | 2015-08-06 | 2018-04-21 | 財團法人資訊工業策進會 | Method and apparatus for wireless communications |
| RU2746217C1 (en) | 2018-01-04 | 2021-04-09 | Телефонактиеболагет Лм Эрикссон (Пабл) | Method, network device, and end-point device for semi-permanent scheduling |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101505542A (en) * | 2008-02-04 | 2009-08-12 | 华为技术有限公司 | Method for resource release in communication system and apparatus thereof |
| CN101686556A (en) * | 2008-09-23 | 2010-03-31 | 华为技术有限公司 | Method, device and system of resource release |
| WO2010068770A1 (en) * | 2008-12-12 | 2010-06-17 | Research In Motion Limited | Uplink semi-persistent scheduling explicit release acknowledgement transmission |
| CN101998643A (en) * | 2009-08-26 | 2011-03-30 | 中兴通讯股份有限公司 | System and method of semi-static scheduling uplink activation and reactivation |
| CN102026410A (en) * | 2010-12-21 | 2011-04-20 | 中兴通讯股份有限公司 | Method and system for releasing semi-persistent scheduling (SPS) service resources |
-
2012
- 2012-12-18 CN CN201210552135.XA patent/CN103874232B/en not_active Expired - Fee Related
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101505542A (en) * | 2008-02-04 | 2009-08-12 | 华为技术有限公司 | Method for resource release in communication system and apparatus thereof |
| CN101686556A (en) * | 2008-09-23 | 2010-03-31 | 华为技术有限公司 | Method, device and system of resource release |
| WO2010068770A1 (en) * | 2008-12-12 | 2010-06-17 | Research In Motion Limited | Uplink semi-persistent scheduling explicit release acknowledgement transmission |
| CN101998643A (en) * | 2009-08-26 | 2011-03-30 | 中兴通讯股份有限公司 | System and method of semi-static scheduling uplink activation and reactivation |
| CN102026410A (en) * | 2010-12-21 | 2011-04-20 | 中兴通讯股份有限公司 | Method and system for releasing semi-persistent scheduling (SPS) service resources |
Also Published As
| Publication number | Publication date |
|---|---|
| CN103874232A (en) | 2014-06-18 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105122858B (en) | Handling downlink semi-persistent scheduling retransmissions in a wireless network | |
| CN111034343A (en) | Method and system for handling packet repetition and recovery of RBs in wireless communication system | |
| CN106488576B (en) | Handle the device and method of scheduling request transmission | |
| EP3817419A1 (en) | Method and apparatus for determining user equipment capability based on number of processed channels | |
| CN107113879A (en) | System and method for the discontinuous operation of wireless device | |
| CN104782060B (en) | Reduce method, wireless communications station and the system of starvation of data | |
| CN103874232B (en) | Semi-static scheduling resources method for releasing and equipment | |
| CN106471852A (en) | A kind of data transmission method, apparatus and system | |
| CN107743313B (en) | Method, base station and system for realizing time division duplex configuration of auxiliary cell | |
| CN109246709A (en) | Establish method and the base station of radio bearer | |
| EP3716513B1 (en) | Method for managing timer and transmitting information and terminal device | |
| TW202205904A (en) | User equipment apparatus and base station apparatus | |
| CN107211464A (en) | Perform listem-before-talk（LBT）The system and method for radio protocol | |
| CN109803378A (en) | A kind of resource selection triggering method and user terminal | |
| US20230164764A1 (en) | Method and apparatus for transmitting feedback information, terminal, and network-side device | |
| CN110999498B (en) | Scheduling request procedure with multiple scheduling request configurations | |
| CN107027191B (en) | Handle the device and method of Non-Access Stratum control program | |
| TW201844049A (en) | Device and Method of Handling Scheduling Request for Logical Channel | |
| CN111867063B (en) | Uplink transmission method and communication device | |
| CN113228814B (en) | Communication method and device | |
| US10045370B2 (en) | Device to device communication | |
| CN112970320B (en) | Random access method, base station, terminal and channel structure | |
| EP4369822A1 (en) | Resource configuration method and communication apparatus | |
| EP4307815A1 (en) | Data transmission method and related apparatus | |
| WO2019010746A1 (en) | Resource pool configuration method and apparatus |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20170804 Termination date: 20181218 |