WO2012130062A1 - 数据发送方法和装置 - Google Patents
数据发送方法和装置 Download PDFInfo
- Publication number
- WO2012130062A1 WO2012130062A1 PCT/CN2012/072660 CN2012072660W WO2012130062A1 WO 2012130062 A1 WO2012130062 A1 WO 2012130062A1 CN 2012072660 W CN2012072660 W CN 2012072660W WO 2012130062 A1 WO2012130062 A1 WO 2012130062A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- phr
- uplink resource
- bsr
- triggered
- scheduling information
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/02—Traffic management, e.g. flow control or congestion control
- H04W28/0205—Traffic management, e.g. flow control or congestion control at the air interface
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/12—Wireless traffic scheduling
- H04W72/1221—Wireless traffic scheduling based on age of data to be sent
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/20—Control channels or signalling for resource management
- H04W72/21—Control channels or signalling for resource management in the uplink direction of a wireless link, i.e. towards the network
Definitions
- the present invention relates to the field of mobile communications, and in particular, to a data transmission method and apparatus.
- wireless access technologies for wireless cellular mobile networks are constantly evolving.
- the current technology evolution is moving from 3G systems to LTE (Long Term Evolution) systems and further to LTE-Advanced systems.
- the LTE system can allocate time-frequency resources according to the instantaneous needs of the user and the channel state.
- the LTE can divide the frequency domain resources into multiple segments. Therefore, the LTE can schedule resources for multiple user equipments (User Equipments, called UEs) in the same subframe.
- the radio resource used by the UE to send the uplink data to the network depends on the base station, such as the eNodeB allocation.
- the eNodeB notifies the radio resource allocated to the specific UE to the UE by means of signaling, and the UE sends the resource indicated in the signaling. Upstream data.
- the eNodeB Before the eNodeB schedules resources for the UE, the eNodeB needs to determine the size of resources allocated to the specific UE. To minimize unnecessary waste of radio resources, the eNodeB needs to allocate appropriate resources for the UE to fully utilize the radio resources. To achieve this goal, the UE first needs to report the amount of data buffered by the UE to the eNodeB through signaling. The eNodeB comprehensively evaluates the priority and quantity of the cached data, and finally initiates a data scheduling for the user. In the prior art, since the data sent by the user equipment may need to be sent through multiple scheduling, the communication technology may specify that different types of information units, such as MAC CE, are sent.
- TB transport block
- SDU Service Data Unit priority
- data with higher priority is preferentially multiplexed in the transport block (TB) Is transmitted, for information units with lower priority, in the case of limited resources, only after carrying the information unit with higher priority, the multiplexing can be transmitted in the transport block, and in the process of data transmission, Since the transmission of the MAC CE is unnecessary, the data transmission is incomplete, thereby causing unnecessary scheduling signaling, causing delay in data transmission and length of data transmission.
- an embodiment of the present invention provides a data transmission method and apparatus.
- the technical solution is as follows:
- a data transmission method including:
- the determined multiplexed scheduling information and buffer data are multiplexed and transmitted in a transport block.
- a data transmitting apparatus including:
- a multiplexing content determining module configured to determine a trigger state of the scheduling information according to a current triggering state of the scheduling information, an uplink resource required to send the buffered data, and the obtained uplink resource, and determine the multiplexed scheduling information and/or Caching data, where the scheduling information is reference information that the base station schedules resources for the user equipment UE;
- a sending module configured to multiplex the multiplexed scheduling information and the cache data determined by the multiplexed content determining module into a transport block for transmission.
- a user equipment comprising any one of the above data transmitting apparatuses.
- the triggering status of the uplink resource actually obtained by the user equipment and each scheduling information on the user equipment is determined, and the content multiplexed during transmission is determined according to the judgment result, and the transmission is performed, thereby reducing the delay of the data in the sending process. It ensures that the data transmission can be flexibly adjusted according to the specific conditions of the user equipment data when the resources are limited, and the base station and the user equipment are prevented from generating excessive scheduling signaling during the transmission process, and the data transmission is also ensured. Timeliness. DRAWINGS
- FIG. 1 is a flow chart of an embodiment of a data transmitting method provided by the present invention.
- FIG. 2 is a flow chart of an embodiment of a data transmitting method provided by the present invention.
- FIG. 3 is a flow chart of an embodiment of a data transmitting method provided by the present invention.
- FIG. 4 is a flow chart of an embodiment of a data transmitting method provided by the present invention.
- FIG. 5 is a flowchart of an embodiment of a data sending method provided by the present invention.
- FIG. 6 is a flow chart of an embodiment of a data transmitting method provided by the present invention.
- FIG. 7 is a flow chart of an embodiment of a data transmitting method provided by the present invention.
- FIG. 8 is a schematic structural diagram of an embodiment of a data transmitting apparatus provided by the present invention
- FIG. 9 is a schematic structural diagram of an embodiment of a data transmitting apparatus provided by the present invention.
- FIG. 1 is a flowchart of an embodiment of a data sending method according to the present invention.
- an execution entity is a user equipment.
- the embodiment specifically includes:
- the scheduling information is reference information that the base station is scheduling resources for the UE.
- the triggering status of the scheduling information includes triggered and untriggered, and the trigger status of determining the scheduling information is: canceling the trigger status of the triggered scheduling information, or retaining The trigger status of the triggered scheduling information, but delays the transmission of scheduling information.
- the above cached data may be all cached data.
- the current trigger state of the scheduling information in the present disclosure may be the current trigger state of each scheduling information, or the current trigger state of all scheduling information, or the current trigger state of at least two scheduling information.
- the above scheduling information includes a BSR and/or a PHR. In the following examples In the above, only the two examples of BSR and PHR are described.
- the determined multiplexed scheduling information and the buffer data are multiplexed and transmitted in a transport block.
- the triggering status of the uplink resource actually obtained by the user equipment and each scheduling information on the user equipment is determined, and the content multiplexed during transmission is determined according to the judgment result, and the transmission is performed, thereby reducing the delay of the data in the sending process. It ensures that the data transmission can be flexibly adjusted according to the specific conditions of the user equipment data when the resources are limited, and the base station and the user equipment are prevented from generating excessive scheduling signaling during the transmission process, and the data transmission is also ensured. Timeliness.
- FIG. 2 is a flowchart of an embodiment of a data sending method provided by the present invention.
- an execution entity is a user equipment and a base station. Referring to FIG. 2, the embodiment specifically includes:
- Step 203 When it is determined that the triggering status of the BSR and the PHR is triggered, determining whether the uplink resource UL Grant allocated by the current base station to the user equipment can carry all cached data of the user equipment, if yes, executing step 204, if not, executing Step 207;
- the determining whether the uplink resource UL Grant allocated by the current base station to the user equipment can carry all the cached data of the user equipment is determining whether the uplink resource obtained by the current user equipment is greater than the uplink resource required for sending all the cached data.
- UL Grant is the uplink resource obtained by the user equipment.
- All the cached data is buffered by the user equipment.
- the resources are temporarily allocated.
- the base station needs to send the scheduled control signaling before the sending time, so as to allocate resources to the user equipment. If the uplink resource required for the user equipment to send all the buffered data is 100 bytes, the resources given by the base station may be able to carry 100 bytes or may not carry 100 bytes. Therefore, when the resources provided by the base station are obtained, the resources are required. Carrying capacity to judge.
- 204 Determine whether the uplink resource can further carry the PHR, if no, perform step 205; 205: when the uplink resource cannot bear the all cached data and the PHR, the reservation is triggered a triggering state of the BSR, and determining to multiplex the BSR, the PHR, and a portion of the cached data that the remaining resources of the uplink resource can bear;
- step 205 the obtained uplink resource cannot carry all the cached data and the PHR, and then the BSR and the PHR are completely transmitted, and the uplink data remaining on the uplink resources after the BSR and the PHR are carried, and the cached data is All of the cached data, the rest of which can be notified to the base station via the BSR.
- the determined multiplexed scheduling information and the buffer data are multiplexed in a transport block and sent to the base station.
- the trigger state of the triggered BSR is retained, and the BSR is sent and sent to notify the base station how much remaining data is to be sent later, which does not waste data, and also causes the base station to check the status of the user equipment. Have a timely judgment.
- multiplexing i.e., data multiplexing of multiple logical channels
- a video telephony service consists of two logical channels that are combined in the same transport block.
- step 205 if the uplink resource cannot carry the entire cached data and the PHR, and cannot carry all the cached data and the BSR, the trigger state of the triggered BSR is cancelled or the triggered state of the triggered PHR is cancelled.
- the cached data or undoing the triggered state of the triggered PHR and multiplexing the cached data, or retaining the triggered state of the triggered PHR and multiplexing the cached data.
- the BSR or PHR or all cached data is multiplexed in the transport block and sent to the base station according to the original priority.
- FIG. 3 is a flowchart of an embodiment of a data sending method according to the present invention.
- an execution subject is a user equipment and a base station
- FIG. 3 is different from the embodiment shown in FIG. 2 in that FIG. 2
- the determination is to determine whether the uplink resource can further carry the PHR, and the result of the determination is that the uplink resource cannot bear the data to be transmitted and the PHR.
- the determination result is that the uplink resource can carry the data to be sent.
- PHR referring to FIG. 3, the embodiment specifically includes:
- step 303 When it is determined that the triggering status of the BSR and the PHR is triggered, determining whether the uplink resource UL Grant allocated by the current base station to the user equipment can carry all the cached data of the user equipment, and if yes, executing step 304, if no, performing the step 308;
- step 304 Determine whether the uplink resource can further carry the PHR, and if yes, perform step 305; the steps 301-304 are the same as the steps 201-204, and are not further described.
- step 306 Determine whether the uplink resource can carry data to be sent, PHR and BSR, and if not, perform step 306;
- the uplink resource can carry the all cached data and the PHR, but cannot carry the entire cached data, the BSR, and the PHR, determine to multiplex the all cached data and the PHR; further, adjust the multiplexing priority At the same time of the level, or before multiplexing, the trigger state of the triggered BSR can also be spoofed to avoid subsequent reporting of the BSR.
- the BSR or PHR or all cached data is multiplexed in the transport block and sent to the base station according to the original priority.
- FIG. 4 is a flowchart of an embodiment of a data sending method according to the present invention.
- an execution subject is a user equipment and a base station
- FIG. 4 is different from the embodiment shown in FIG. 3 in that FIG. 3
- the method for determining whether the uplink resource can further carry the PHR is determined, and the determination result is that the uplink resource can carry all the cached data and the PHR, and the embodiment of FIG. 4 determines whether the uplink resource can further carry the BSR.
- the result of the determination is that the uplink resource can carry all the cached data and the BSR.
- the embodiment specifically includes:
- 402 Determine a trigger status of the PHR
- 403 When it is determined that the triggering status of the BSR and the PHR is triggered, determining whether the uplink resource UL Grant allocated by the current base station to the user equipment can carry all cached data of the user equipment, if yes, executing step 404, if no, executing Step 408;
- step 404 Determine whether the uplink resource can further carry the BSR, and if yes, perform step 405; the steps 401-404 are the same as the steps 201-204, and are not further described.
- step 406 Determine whether the uplink resource can carry all cached data, PHR and BSR, if not, proceed to step 406;
- the uplink resource can carry the all cached data and the BSR, but cannot carry the entire cached data, the BSR, and the PHR, determine to multiplex the all cached data and the BSR; further, determine the multiplexed content.
- the BSR and all cached data are multiplexed in a transport block and sent to the base station.
- FIG. 5 is a flowchart of an embodiment of a data sending method according to the present invention.
- an execution entity is a user equipment and a base station, and FIG. 5 is different from the embodiment shown in FIG.
- the trigger states of the BSR and the PHR are both triggered, and in the embodiment shown in FIG. 5,
- the triggering state of the BSR is triggered, and the triggering state of the PHR is determined to be untriggered.
- the embodiment specifically includes:
- Step 503 When it is determined that the triggering state of the BSR is triggered, and determining that the triggering state of the PHR is not triggered, determining whether the uplink resource UL Grant allocated by the current base station to the user equipment can carry all cached data of the user equipment, and if yes, Step 504 is performed. If no, step 507 is performed; the steps 501-503 are the same as the steps 201-203, and are not described again.
- 504 trigger status of the triggered BSR
- 505 Determine to reuse the all cached data
- All the buffered data is multiplexed in the transport block and sent to the base station.
- the BSR or PHR or all cached data is multiplexed in the transport block and sent to the base station according to the original priority.
- FIG. 6 a flowchart of an embodiment of a data sending method provided by the present invention
- an execution subject is a user equipment and a base station
- FIG. 6 is different from the embodiment shown in FIG. 2 to FIG.
- the triggering states of the BSR and the PHR are determined.
- the embodiment shown in FIG. 6 only the triggering state of one of the scheduling information is determined.
- the description is made by taking the scheduling information as a BSR as an example. Referring to FIG. 6, the embodiment specifically includes:
- step 602 When it is determined that the triggering state of the BSR is triggered, it is determined whether the uplink resource UL Grant allocated by the current base station to the user equipment can carry all cached data of the user equipment, and if yes, step 603 is performed.
- step 603 Determine whether the uplink resource can further carry the triggered BSR, if no, go to step 604, and if yes, go to step 606;
- All the buffered data is multiplexed in the transport block and sent to the base station.
- step 601 when the determination in step 601 is to determine the trigger state of the PHR and determine that the trigger state of the PHR is triggered, determining that the current uplink allocated by the base station to the user equipment can carry all caches of the user equipment cache. After the data, it is further determined whether the uplink resource can further carry the triggered PHR. If the uplink resource cannot be carried, the trigger state of the triggered PHR can be revoked and the all cached data is multiplexed; or the triggered state of the triggered PHR is revoked. And determining to multiplex all cached data; or retaining the trigger state of the PHR, determining to multiplex the cached data and deferring multiplexing of the PHR.
- the BSR or PHR or all cached data is multiplexed in the transport block and sent to the base station according to the original priority.
- an execution entity is a user equipment and a base station.
- the scheduling information may include PHR or extended PHR, in the embodiment shown in FIG. 7, the scheduling information includes an extended PHR, and the number of bytes of the extended PHR is about twice or more than the PHR, about 4 to 13 bytes, so when When the row resource can carry the entire cache data and the BSR, but cannot carry the entire cache data and the extended PHR, the multiplexing content thereof is different from the embodiment shown in FIGS. 2-6.
- the embodiment specifically includes:
- step 703 When it is determined that the triggering state of the BSR and the extended PHR is triggered, it is determined whether the uplink resource UL Grant allocated by the current base station to the user equipment can carry all cached data of the user equipment, and if yes, step 704 is performed, and if no, Perform step 707;
- step 705 Determine whether the uplink resource can further carry the BSR, and if yes, perform step 705; the steps 701-704 are the same as the steps 201-204, and are not further described.
- step 705 Determine whether the uplink resource can carry data to be sent, extend PHR and BSR, and if not, perform step 706;
- the all buffered data and the BSR are multiplexed in a transport block and sent to the base station.
- the BSR or extended PHR or all cached data is multiplexed in the transport block and sent to the base station according to the original priority.
- all the cached data in the foregoing embodiment shown in FIG. 1 to FIG. 7 includes a C-RNTI (Cell Radio Network Temporary Identifier) and/or a control plane message, for all
- C-RNTI Cell Radio Network Temporary Identifier
- the cached data corresponds to the case in the above embodiment in accordance with the difference in the trigger state of the scheduling information and the like.
- determining that the BSR is triggered or determining that the PHR is triggered determining whether the uplink resource UL Grant allocated by the current base station to the user equipment can carry the C-RNTI and the control plane message (such as: RRC connection reconfiguration complete message), when capable of carrying C -RNTI and control plane messages, but can not carry BSR, C-RNTI and control plane messages or PHR, C-RNTI and control plane messages, can retain or trigger the trigger status of the triggered BSR, can also be sold
- the triggered state of the triggered PHR, or the trigger state of the triggered PHR is retained and the PHR is deferred, and the C-RNTI and control plane messages are multiplexed in the transport block and sent to the base station.
- determining that the BSR is triggered or determining that the PHR is triggered determining whether the uplink resource UL Grant allocated by the current base station to the user equipment can carry the C-RNTI+ control plane message, when The C-RNTI and control plane messages can be carried, but the PHR, BSR, C-RNTI, and control plane messages cannot be carried, but cannot be carried.
- the trigger status of the triggered BSR can be retained or revoked, and the C-RNTL control plane can be carried.
- Message multiplexing is sent to the base station in the transport block;
- determining that the BSR is triggered and the PHR is triggered determining whether the uplink resource UL Grant allocated by the current base station to the user equipment can carry the C-RNTI, the BSR, and the control plane message, and can carry the C-RNTI, the BSR, and the
- the trigger state of the triggered PHR may be retained or revoked, and the C-RNTI, BSR and control plane messages are multiplexed and transmitted in the transport block.
- the PHR is triggered, and the BSR is not triggered. It is determined whether the uplink resource UL Grant allocated by the current base station to the user equipment can carry the C-RNTI and the control plane message, and can carry the C-RNTI and the control plane.
- the trigger state of the trigger of the PHR is reserved, and the PHR is deferred, and the C-RNTI and control plane messages are multiplexed in the transport block and sent to the base station.
- the triggering status of the uplink resource actually obtained by the user equipment and each scheduling information on the user equipment is determined, and the C-RNTI and the control plane message used in the handover are used according to the judgment result.
- the multiplexed content is preferentially multiplexed and transmitted in the transport block, it can ensure that when the message such as the handover completion message is sent during the handover, the segment transmission and the delayed transmission are not caused due to the original priority setting, and the handover is guaranteed.
- the smooth transition in the middle does not cause the communication of the user equipment to be disconnected, which improves the switching efficiency and avoids the delay of the switching time.
- the scheduling information is exemplified by the BSR and the PHR.
- the scheduling information may also have a discontinuous reception indication (for notifying the base station that it is about to enter the discontinuous reception period) and no data transmission indication (
- the priority of the scheduling information is higher than all the cached data, and the uplink resources, the obtained uplink resources, and the scheduling required for sending all the cached data may also be used.
- the judgment of the information determines the content of the reuse.
- the C-RNTI and the control plane message are preferentially multiplexed, and the scheduling information may or may not be included according to the judgment result.
- the obtained uplink resource can carry all cached data, and if yes, whether the obtained uplink resource can further carry scheduling information.
- a schematic structural diagram of an embodiment of a data transmitting apparatus includes: a multiplexing content determining module 801, configured to: according to a current triggering state of scheduling information, an uplink resource required to send buffered data, and an obtained uplink a resource, determining a triggering state of the scheduling information, and determining the multiplexed scheduling information and/or the cached data, where the scheduling information is reference information for the base station to schedule resources for the user equipment UE, and the sending module 802 is configured to: The multiplexed scheduling information and the buffered data multiplex determined by the determining module are transmitted in the transport block.
- the multiplexing content determining module 801 includes: a first multiplexing unit, a second multiplexing unit, a third multiplexing unit, a fourth multiplexing unit, a fifth multiplexing unit, and a sixth multiplexing unit, and At least one of the seventh multiplexing unit: the scheduling information includes a BSR and/or a PHR, and the multiplexing content determining module 801 includes: a scheduling information triggering state determining unit 8011, an uplink resource determining unit 8012, and a first multiplexing unit 8013,
- the scheduling information triggering state determining unit 8011 is configured to determine that the triggering states of the BSR and the PHR are triggered;
- the uplink resource determining unit 8012 is configured to determine that the uplink resource can carry the cached data and cannot carry the cached data and the PHR;
- the first multiplexing unit 8013 is configured to: when the scheduling information triggering state determining unit determines that the triggering state of the BSR and the PHR is triggered, and the uplink resource determining unit determines that the uplink resource can carry the cached data, and the uplink resource cannot bear the cached data. And the PHR, retaining the triggered state of the triggered BSR, and determining to multiplex the BSR, the PHR, and a portion of the cached data that the remaining resources of the uplink resource can bear.
- the scheduling information includes a BSR and/or a PHR
- the multiplexed content determining module 801 includes: a scheduling information triggering state determining unit 8011, an uplink resource determining unit 8012, and a second multiplexing unit 8014, where the scheduling information triggering state determining unit 8011 is used. Determining that the trigger status of the BSR and the PHR is triggered;
- the uplink resource determining unit 8012 is configured to determine that the uplink resource can carry the cached data and cannot carry the cached data and the PHR;
- the second multiplexing unit 8014 is configured to: when the scheduling information triggering state determining unit determines that the triggering state of the BSR and the PHR is triggered, and the uplink resource determining unit determines that the uplink resource can carry the cached data, and the uplink resource cannot bear the cached data.
- the PHR, and the uplink resource cannot bear the cached data and the BSR, cancel the trigger state of the triggered BSR, determine to multiplex the cached data, or revoke the triggered state of the triggered PHR, and determine to multiplex the cached data, Or retain the trigger state of the triggered PHR and determine to reuse the cached data.
- the scheduling information includes a BSR and/or a PHR
- the multiplexed content determining module 801 includes: a scheduling information triggering state determining unit 8011, an uplink resource determining unit 8012, and a third multiplexing unit 8015, and the scheduling information triggering state determining unit 8011, Determining that the trigger status of the BSR and the PHR is triggered;
- the uplink resource determining unit 8012 is configured to determine that the uplink resource can carry the cached data and cannot carry the cached data and the PHR;
- the third multiplexing unit 8015 is configured to: when the scheduling information triggering state determining unit determines that the triggering state of the BSR and the PHR is triggered, and the uplink resource determining unit determines that the uplink resource can carry the cached data and the uplink resource can carry the cache When the data and the BSR are unable to carry the cached data, the BSR, and the PHR, it is determined to multiplex the cached data and the BSR.
- the scheduling information includes a BSR and/or a PHR
- the multiplexed content determining module 801 includes: a scheduling information triggering state determining unit 8011, an uplink resource determining unit 8012, and a fourth multiplexing unit 8016, the scheduling information triggering state determining unit 8011, Determining that the trigger status of the BSR and the PHR is triggered;
- the uplink resource determining unit 8012 is configured to determine that the uplink resource can carry the cached data and cannot carry the cached data and the PHR;
- the fourth multiplexing unit 8016 is configured to: when the scheduling information triggering state determining unit determines that the triggering state of the BSR and the PHR is triggered, and the uplink resource determining unit determines that the uplink resource can carry the buffered data, and the uplink resource can carry the cached data. And the PHR, and when the cached data, the BSR, and the PHR cannot be carried, it is determined to multiplex the cached data and the PHR.
- the scheduling information includes a BSR and/or a PHR
- the multiplexed content determining module 801 includes: a scheduling information triggering state determining unit 8011, an uplink resource determining unit 8012, and a fifth multiplexing unit 8017, and a fifth multiplexing unit 8017, configured to
- the scheduling information triggering state determining unit determines that the triggering state of the BSR is triggered and determines that the triggering state of the PHR is not triggered, and the uplink resource determining unit Determining that the uplink resource can carry the cache data, revoking the triggered state of the triggered BSR, and determining to reuse the cached data.
- the scheduling information includes a BSR and/or a PHR
- the multiplexed content determining module 801 includes: a scheduling information triggering state determining unit 8011, an uplink resource determining unit 8012, and a sixth multiplexing unit 8018, and a sixth multiplexing unit 8018, configured to
- the scheduling information triggering state determining unit determines that the triggering state of the BSR or the PHR is triggered, and the uplink resource determining unit determines that the uplink resource can bear the buffered data, and the uplink resource cannot bear the cached data and the triggered BSR, and the revocation has been performed. Triggering the triggered state of the BSR, determining to reuse the cached data; or,
- the sixth multiplexing unit 8018 is configured to: when the scheduling information triggering state determining unit determines that the triggering state of the BSR or the PHR is triggered, and the uplink resource determining unit determines that the uplink resource cannot bear the cached data and the triggered PHR, Undoing the triggered state of the triggered PHR, determining to reuse the cached data; or,
- the sixth multiplexing unit 8018 is configured to: when the scheduling information triggering state determining unit determines that the triggering state of the BSR or the PHR is triggered, and the uplink resource determining unit determines that the uplink resource cannot bear the cached data and the triggered PHR, The trigger state of the PHR is reserved, it is determined that the cached data is multiplexed and the PHR is deferred.
- the scheduling information includes a BSR and/or a PHR
- the multiplexed content determining module 801 includes: a scheduling information triggering state determining unit 8011, an uplink resource determining unit 8012, and a seventh multiplexing unit 8019, and a seventh multiplexing unit 8019, for
- the scheduling information includes an extended PHR
- the triggering state determining unit determines that the triggering state of the BSR and the PHR is triggered
- the uplink resource determining unit determines that the uplink resource can carry the cached data and the uplink resource can carry the cached data and the
- the PHR is deferred and the buffered data and the BSR are determined to be multiplexed.
- the cached data includes a cell radio network temporary identification and/or control plane message of the user equipment.
- the device provided by this embodiment may be specifically a user equipment.
- the specific implementation process refer to the method embodiment, and details are not described herein again.
- a user equipment comprising any one of the above embodiments.
- the user equipment provided in this embodiment may be a mobile terminal, and may be the same as the method embodiment.
- All or part of the foregoing technical solutions provided by the embodiments of the present invention may be implemented by hardware related to program instructions, and the program may be stored in a readable storage medium, where the storage medium includes:
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Description
数据发送方法和装置 本申请要求于 2011年 3月 31 日提交的, 申请号为 201110081210.4,发明 名称为 "数据发送方法和装置" 的中国申请的优先权, 其全部内容通过引用 结合在本申请中。 技术领域
本发明涉及移动通信领域, 特别涉及一种数据发送方法和装置。
背景技术
为了满足将来用户对更高速率、 更广阔的覆盖和更大的容量的需求, 无 线蜂窝移动网络的无线接入技术正在不断的发展。 目前的技术演进正由 3G 系统向 LTE (Long Term Evolution,长期演进)系统,并进一步向 LTE- Advanced 系统演进。
对于通信系统, 如 LTE系统, 对于上行或下行, 都同时支持快速的调度和 链路适应技术。 因此, LTE系统可以依据用户的瞬时的需求和信道状态, 来进 行时频资源的分配。 在上行调度技术中, 由于 LTE可以将频域资源分割成多个 分段,因此 LTE可以在同一个子帧上,同时为多个用户设备(User Equipment, 筒称 UE )调度资源。 UE发送给网络的上行数据所使用的无线资源, 依赖于基 站,如 eNodeB分配, eNodeB将分配给特定 UE的无线资源采用信令的方式通知 给 UE, UE在信令中所指示的资源上发送上行数据。 在 eNodeB为 UE调度资源 之前, eNodeB需要决定调度给特定 UE的资源的大小, 为了尽量减少不必要的 浪费无线资源, eNodeB需要为 UE分配适当的资源, 以达到充分利用无线资源 的目的。 为了达到该目的, 首先需要 UE将其緩存的数据量, 通过信令的方式 报告给 eNodeB, eNodeB综合评估其緩存数据量的优先级, 数量等因素, 最终 为用户发起一次数据调度。 现有技术中, 由于用户设备所发送的数据可能需要通过多次调度才能完 成发送, 因此, 在通信技术中可以规定发送不同类型信息单元例如 MAC CE
(媒体接入控制层控制单元, Media Access Control Control Element ) 或 SDU ( Service Data Unit, 服务数据单元) 的优先级, 即优先级高的数据优先复用 在传输块(TB, transport block )中而被发送, 对于优先级比较低的信息单元, 在资源受限的情况下, 只有在承载完优先级比较高的信息单元后, 才能复用 在传输块中被发送, 而在数据发送过程中, 由于不必要 MAC CE的发送, 导致 数据发送不完全, 从而引发不必要的调度信令, 使得数据发送中发生时延, 数据传输用时长。
发明内容
为了减少数据传输时延, 节省调度信令, 本发明实施例提供了一种数据 发送方法和装置。 所述技术方案如下:
根据本发明的一方面, 提供一种数据发送方法, 包括:
根据调度信息当前的触发状态、 发送緩存数据所需要上行资源和所获得 的上行资源, 确定所述调度信息的触发状态, 并确定被复用的调度信息和 /或 緩存数据, 所述调度信息为基站为用户设备 UE调度资源的参考信息;
将所述确定的被复用的调度信息和緩存数据复用在传输块中发送。
根据本发明的一方面, 提供一种数据发送装置, 包括:
复用内容确定模块, 用于根据调度信息当前的触发状态、 发送緩存数据 所需要上行资源和所获得的上行资源, 确定所述调度信息的触发状态, 并确 定被复用的调度信息和 /或緩存数据, 所述调度信息为基站为用户设备 UE调 度资源的参考信息;
发送模块, 用于将所述复用内容确定模块确定的被复用的调度信息和緩 存数据复用在传输块中发送。
根据本发明的一方面, 提供一种用户设备, 所述用户设备包括上述任一 项数据发送装置。
本发明实施例提供的技术方案的有益效果是:
通过用户设备实际获得的上行资源和该用户设备上各个调度信息的触发 状态, 进行判断, 根据其判断结果确定传输时复用的内容, 并进行传输, 可 以降低数据在发送过程中的时延, 保证了在资源受限的情况下, 能够根据用 户设备数据的具体情况灵活的调整数据的发送, 避免了基站和用户设备在传 输过程中产生过多的调度信令, 也保证了数据发送中的及时性。
附图说明
为了更清楚地说明本发明实施例或现有技术中的技术方案, 下面将对实 施例或现有技术描述中所需要使用的附图作筒单地介绍, 显而易见地, 下面 描述中的附图仅仅是本发明的一些实施例, 对于本领域普通技术人员来讲, 在不付出创造性劳动性的前提下, 还可以根据这些附图获得其他的附图。
图 1是本发明提供的数据发送方法的一个实施例的流程图;
图 2是本发明提供的数据发送方法的一个实施例的流程图;
图 3是本发明提供的数据发送方法的一个实施例的流程图;
图 4是本发明提供的数据发送方法的一个实施例的流程图;
图 5是本发明提供的数据发送方法的一个实施例的流程图;
图 6是本发明提供的数据发送方法的一个实施例的流程图;
图 7是本发明提供的数据发送方法的一个实施例的流程图;
图 8是本发明提供的数据发送装置的一个实施例的结构示意图; 图 9是本发明提供的数据发送装置的一个实施例的结构示意图。
具体实施方式
为使本发明的目的、 技术方案和优点更加清楚, 下面将结合附图对本发 明实施方式作进一步地详细描述。
图 1 为本发明提供的数据发送方法的一个实施例的流程图, 在该实施例 中, 执行主体为用户设备, 参见图 1 , 该实施例具体包括:
101: 根据调度信息当前的触发状态、 发送緩存数据所需要上行资源和所 获得的上行资源, 确定该调度信息的触发状态, 并确定被复用的调度信息和 / 或緩存数据;
其中,调度信息为基站为 UE调度资源的参考信息;调度信息的触发状态 包括已触发和未被触发, 相应的确定该调度信息的触发状态包括: 撤销已触 发的调度信息的触发状态, 或保留已触发的调度信息的触发状态, 但推迟调 度信息的发送。
上述緩存数据可以是全部緩存数据。
需要说明的是, 本发明中所述的调度信息当前的触发状态可以是指每个 调度信息的当前触发状态, 或全部调度信息的当前触发状态, 或至少 2个调 度信息的当前触发状态。上述调度信息包括 BSR和 /或 PHR。在下述的实施例
中, 仅以 BSR和 PHR这两种为例进行说明。
102: 将所述确定的被复用的调度信息和緩存数据复用在传输块中发送。 通过用户设备实际获得的上行资源和该用户设备上各个调度信息的触发 状态, 进行判断, 根据其判断结果确定传输时复用的内容, 并进行传输, 可 以降低数据在发送过程中的时延, 保证了在资源受限的情况下, 能够根据用 户设备数据的具体情况灵活的调整数据的发送, 避免了基站和用户设备在传 输过程中产生过多的调度信令, 也保证了数据发送中的及时性。
图 为本发明提供的数据发送方法的一个实施例的流程图, 在该实施例 中, 执行主体为用户设备和基站, 参见图 2, 该实施例具体包括:
201: 判断 BSR(Buffer Status Report, 緩存数据量报告)的触发状态; 本领域技术人员可以获知, BSR的触发可以通过周期性 BSR定时器超时 实现。 另外, BSR还可以由其他情况触发, 本实施例不做具体限定。
202: 判断 PHR(Power Headroom Report, 功率余量报告)的触发状态; 本领域技术人员可以获知, PHR的触发可以通过周期性 PHR定时器超时 实现。 另外, PHR还可以由其他情况触发, 本实施例不做具体限定。
203: 当确定 BSR和 PHR的触发状态为被触发, 则判断当前基站分配给 用户设备的上行资源 UL Grant是否能够承载用户设备的全部緩存数据, 如果 是, 则执行步骤 204, 如果否, 则执行步骤 207;
其中, 判断当前基站分配给用户设备的上行资源 UL Grant是否能够承载 用户设备的全部緩存数据即是判断发送当前用户设备得到的上行资源是否大 于发送全部緩存数据所需要上行资源。 UL Grant为用户设备所获得的上行资 源。
其中, 全部緩存数据是用户设备緩存的, 在 LTE里面, 由于资源是临时 分配的, 用户设备在发送数据时, 需要由基站在发送时刻之前发送调度的控 制信令, 以便给用户设备分配资源, 假如用户设备发送全部緩存数据所需要 的上行资源为 100个字节, 基站给的资源可能能够承载 100字节, 也可能不 能承载 100字节, 所以需要在获得基站提供的资源时, 对资源的承载能力进 行判断。
204: 判断该上行资源是否能够进一步承载 PHR, 如果否,执行步骤 205; 205: 当该上行资源不能承载该全部緩存数据和该 PHR时, 保留已触发
的 BSR的触发状态, 并确定复用所述 BSR、 PHR和所述上行资源的剩余资源 能够承载的一部分所述緩存数据;
在步骤 205中, 获得的上行资源不能承载全部緩存数据和该 PHR, 则将 BSR和 PHR完整的发送, 并再承载了 BSR和 PHR以后剩余的上行资源上承 载緩存数据, 此时的緩存数据是全部緩存数据的一部分, 其剩余部分可以通 过 BSR通知基站。
206: 将确定的被复用的调度信息和緩存数据复用在传输块中发送给基 站。
本领域技术人员可以获知, 在现有技术中, 在上行资源能够承载下所需 要发送的全部数据, 但不能承载下 BSR和全部数据, 而且上行资源不能承载 全部緩存数据和 PHR时, 会撤销 BSR的发送, 但由于 PHR被触发, 并且复 用优先级高于所要发送的数据, 因此 PHR在该情况下, 会优先于数据被复用 在传输块中,最终导致用户设备的緩存数据不能被全部发送,而由于此时 BSR 已经被撤销, 会造成基站接收到部分緩存数据时, 由于没有收到 BSR, 无法 预知用户设备的緩存数据量, 基站无法为用户设备的后续调度分配合适的上 行资源,在本实施例中,保留已触发的 BSR的触发状态,并将 BSR—并发送, 以便通知基站后续还有多少剩余数据待发送, 不会造成数据的浪费, 也同时 使得基站对用户设备的状态有及时的判断。
本领域技术人员可以获知, 复用即是多个逻辑信道的数据复用在一个传 输块发送。 例如, 视频电话的业务由两个逻辑信道组成, 综合在同一个传输 块发送。
在步骤 205中, 如果该上行资源既不能承载该全部緩存数据和该 PHR, 也不能承载全部緩存数据和该 BSR, 则撤销已触发的 BSR的触发状态或撤销 已触发的 PHR的触发状态并复用所述緩存数据,或撤销已触发的 PHR的触发 状态并复用所述緩存数据, 或保留已触发的 PHR的触发状态并复用所述緩存 数据。
207: 按照原有优先级, 将 BSR或 PHR或全部緩存数据复用在传输块中 发送给基站。
在现有技术中, 一般来说, BSR、 PHR等调度信息的优先级高于全部緩 存数据的优先级。
图 3 为本发明提供的数据发送方法的一个实施例的流程图, 在该实施例 中, 执行主体为用户设备和基站, 图 3与图 2所示的实施例的不同之处在于, 图 2所示为对上行资源是否能够进一步承载 PHR进行了判断, 其判断结果为 确定上行资源不能承载待发送数据和 PHR, 而图 3的实施例中, 其判断结果 为确定上行资源能够承载待发送数据和 PHR, 参见图 3, 该实施例具体包括:
301: 判断 BSR的触发状态;
302: 判断 PHR的触发状态;
303: 当确定 BSR和 PHR的触发状态为被触发, 则判断当前基站分配给 用户设备的上行资源 UL Grant是否能够承载用户设备的全部緩存数据, 如果 是, 则执行步骤 304, 如果否, 执行步骤 308;
304: 判断该上行资源是否能够进一步承载 PHR, 如果是,执行步骤 305; 该步骤 301-304与步骤 201-204原理相同, 不再赞述。
305: 判断该上行资源是否能够承载待发送数据、 PHR和 BSR, 如果否, 则执行步骤 306;
如果是, 执行步骤 308;
306: 当该上行资源能够承载该全部緩存数据和该 PHR, 但不能承载该全 部緩存数据、 该 BSR和该 PHR时, 确定复用该全部緩存数据和该 PHR; 进一步地, 在调整复用优先级的同时, 或复用之前, 还可以 ·^销已触发 的 BSR的触发状态, 以避免 BSR的后续上报。
307: 将 PHR和全部緩存数据复用在传输块中发送给基站, 结束;
308: 按照原有优先级, 将 BSR或 PHR或全部緩存数据复用在传输块中 发送给基站。
图 4为本发明提供的数据发送方法的一个实施例的流程图, 在该实施例 中, 执行主体为用户设备和基站, 图 4与图 3所示的实施例的不同之处在于, 图 3所示为对上行资源是否能够进一步承载 PHR进行了判断, 其判断结果为 确定上行资源能够承载待全部緩存数据和 PHR, 而图 4的实施例对上行资源 是否能够进一步承载 BSR进行了判断, 其判断结果为确定上行资源能够承载 全部緩存数据和 BSR, 参见图 4, 该实施例具体包括:
401: 判断 BSR的触发状态;
402: 判断 PHR的触发状态;
403: 当确定 BSR和 PHR的触发状态为被触发, 则判断当前基站分配给 用户设备的上行资源 UL Grant是否能够承载用户设备的全部緩存数据, 如果 是, 则执行步骤 404, 如果否, 则执行步骤 408;
404: 判断该上行资源是否能够进一步承载 BSR, 如果是, 执行步骤 405; 该步骤 401-404与步骤 201-204原理相同, 不再赞述。
405:判断该上行资源是否能够承载全部緩存数据、 PHR和 BSR,如果否, 则执行步骤 406;
如果是, 执行步骤 408;
406: 当该上行资源能够承载该全部緩存数据和该 BSR, 但不能承载该全 部緩存数据、 该 BSR和该 PHR时, 确定复用该全部緩存数据和该 BSR; 进一步地, 在确定复用内容的同时, 或在复用之前, 还可以 ·^销已触发 的 PHR的触发状态, 或推迟复用已触发的 PHR, 优先发送緩存数据, 减少数 据时延。
407: 将 BSR和全部緩存数据复用在传输块中发送给基站。
408: 按照原有优先级, 将 BSR或 PHR或全部緩存数据复用在传输块中 发送给基站。 图 5 为本发明提供的数据发送方法的一个实施例的流程图, 在该实施例 中, 执行主体为用户设备和基站, 图 5与图 2~4所示的实施例的不同之处在 于, 图 2~4所示实施例中, BSR和 PHR的触发状态均为被触发, 而图 5所 示实施例中,
BSR的触发状态为被触发, 而确定 PHR的触发状态为未被触发, 参见图 5, 该实施例具体包括:
501: 判断 BSR的触发状态;
502: 判断 PHR的触发状态;
503: 当确定 BSR的触发状态为被触发, 并确定 PHR的触发状态为未被 触发, 则判断当前基站分配给用户设备的上行资源 UL Grant是否能够承载用 户设备的全部緩存数据, 如果是, 则执行步骤 504, 如果否, 则执行步骤 507; 该步骤 501-503与步骤 201-203原理相同, 不再赘述。
504: 已触发的 BSR的触发状态;
505: 确定复用该全部緩存数据;
506: 将全部緩存数据复用在传输块中发送给基站。
507: 按照原有优先级, 将 BSR或 PHR或全部緩存数据复用在传输块中 发送给基站。
参见图 6, 本发明提供的数据发送方法的一个实施例的流程图, 在该实施 例中, 执行主体为用户设备和基站, 图 6与图 2~5所示的实施例的不同之处 在于, 图 2~5所示实施例中, 对 BSR和 PHR的触发状态都进行判断, 而图 6 所示实施例中, 只对其中一种调度信息的触发状态进行判断, 在本实施例中, 仅以该调度信息为 BSR为例进行说明, 参见图 6, 该实施例具体包括:
601: 判断 BSR的触发状态;
602: 当确定 BSR的触发状态为被触发,则判断当前基站分配给用户设备 的上行资源 UL Grant是否能够承载用户设备的全部緩存数据, 如果是, 则执 行步骤 603,
603: 判断该上行资源是否能够进一步承载已触发的该 BSR, 如果否, 执 行步骤 604, 如果是, 执行步骤 606;
604: ·^销已触发的 BSR的触发状态, 并确定复用该全部緩存数据;
605: 将全部緩存数据复用在传输块中发送给基站。
在本实施例中, 当步骤 601中的判断是对 PHR的触发状态进行判断并确 定 PHR的触发状态为被触发时, 在确定当前基站分配给用户设备的上行资能 够承载用户设备緩存的全部緩存数据后, 应进一步判断上行资源是否能够进 一步承载已触发的该 PHR, 如果不能承载, 则可以撤销已触发的 PHR的触发 状态并确定复用该全部緩存数据; 或撤销已触发的 PHR的触发状态, 并确定 复用全部緩存数据; 或保留 PHR的触发状态, 确定复用所述緩存数据并推迟 复用所述 PHR。
606: 按照原有优先级, 将 BSR或 PHR或全部緩存数据复用在传输块中 发送给基站。
参见图 7, 本发明提供的数据发送方法的一个实施例的流程图, 在该实施 例中, 执行主体为用户设备和基站, 在上述图 2~6所示的实施例中, 调度信 息可以包括 PHR或扩展 PHR,在图 7所示实施例中,调度信息包括扩展 PHR, 扩展 PHR的字节数约为 PHR的两倍以上, 大约 4~13个字节, 因此, 当该上
行资源能够承载该全部緩存数据和该 BSR, 但不能承载该全部緩存数据和该 扩展 PHR时, 其复用内容与图 2~6所示的实施例不同。 参见图 7, 该实施例 具体包括:
701: 判断 BSR的触发状态;
702: 判断扩展 PHR的触发状态;
703: 当确定 BSR和扩展 PHR的触发状态为被触发, 则判断当前基站分 配给用户设备的上行资源 UL Grant是否能够承载用户设备的全部緩存数据, 如果是, 则执行步骤 704, 如果否, 则执行步骤 707;
704: 判断该上行资源是否能够进一步承载 BSR, 如果是, 执行步骤 705; 该步骤 701-704与步骤 201-204原理相同, 不再赞述。
705: 判断该上行资源是否能够承载待发送数据、 扩展 PHR和 BSR, 如 果否, 则执行步骤 706;
706: 当该上行资源能够承载该全部緩存数据和该 BSR, 但不能承载该全 部緩存数据和该扩展 PHR时,撤销已触发的 PHR的触发状态,或推迟复用该 扩展 PHR, 并确定复用该全部緩存数据和该 BSR;
707: 将该全部緩存数据和该 BSR复用在传输块中发送给基站。
708: 按照原有优先级, 将 BSR或扩展 PHR或全部緩存数据复用在传输 块中发送给基站。
在基站切换过程中, 上述图 1~图 7中所示的实施例中的全部緩存数据包 括 C-RNTI ( Cell Radio Network Temporary Identifier, 小区无线网络临时标识 ) 和 /或控制面消息,针对该全部緩存数据,根据调度信息的触发状态等的区别, 与上述实施例中的情况——对应。 具体地, 确定 BSR被触发或确定 PHR被 触发; 判断当前基站分配给用户设备的上行资源 UL Grant是否能够承载 C-RNTI和控制面消息(比如: RRC连接重配完成消息), 当能够承载 C-RNTI 和控制面消息,但不能承载 BSR、 C-RNTI和控制面消息或 PHR 、 C-RNTI和 控制面消息时, 可以保留或 ·^销已触发的 BSR的触发状态, 还可以 ·^销已触 发的 PHR的触发状态, 或保留已触发的 PHR的触发状态并推迟复用 PHR, 将 C-RNTI和控制面消息复用在传输块中发送给基站。
在另一实施例中, 确定 BSR被触发或确定 PHR被触发; 判断当前基站 分配给用户设备的上行资源 UL Grant是否能够承载 C-RNTI+控制面消息, 当
能够承载 C-RNTI和控制面消息, 但不能承载 PHR、 BSR、 C-RNTI和控制面 消息时, 但不能承载下, 可以保留或撤销已触发的 BSR 的触发状态, 并将 C-RNTL 控制面消息复用在传输块中发送给基站;
在又一实施例中, 确定 BSR被触发和 PHR被触发; 判断当前基站分配 给用户设备的上行资源 UL Grant是否能够承载 C-RNTI、 BSR和控制面消息, 当能够承载 C-RNTI、 BSR和控制面消息, 但不能承载 PHR、 BSR, C-RNTI 和控制面消息时, 可以保留或撤销已触发的 PHR的触发状态, 并将 C-RNTI、 BSR和控制面消息复用在传输块中发送给基站;
在再一实施例中, 确定 PHR被触发, 而 BSR没有被触发; 判断当前基站 分配给用户设备的上行资源 UL Grant是否能够承载 C-RNTI和控制面消息, 当能够承载 C-RNTI和控制面消息, 但不能承载 PHR 、 C-RNTI 和控制面消 息时, 保留 PHR的触发的触发状态, 并推迟复用 PHR, 并将 C-RNTI和控制 面消息复用在传输块中发送给基站。
在上述图 7 以后的实施例中, 通过用户设备实际获得的上行资源和该用 户设备上各个调度信息的触发状态, 进行判断, 根据其判断结果将切换中用 到的 C-RNTI和控制面消息作为复用内容优先复用在传输块中发送,可以保证 切换过程中在发送切换完成消息等消息时, 不会由于原有优先级的设置造成 分段发送、 延时发送等情况, 保证了切换中的平滑过渡, 不会使用户设备的 通信产生断开的现象, 提高了切换的效率, 避免了切换时间的延时。
在上述实施例中,调度信息以 BSR和 PHR为例,在实际用户设备运行时, 调度信息还可以有非连续接收指示 (用于通知基站其将要进入非连续接收周 期)和无数据传输指示(用于指示终端后续将无数据需要传输), 在现有技术 中, 调度信息的优先级均高于全部緩存数据, 也可以通过对发送全部緩存数 据所需的上行资源、 获得的上行资源以及调度信息的判断, 确定复用内容。 在切换过程中, 优先复用 C-RNTI和控制面消息, 可根据判断结果包括或不 包括调度信息。
需要说明的是, 在上述图 2~图 7所示的实施例中, 是先判断获得的上行 资源是否能够承载全部緩存数据, 如果是, 再判断该获得的上行资源是否能 够进一步承载调度信息, 在另一实施例中, 还可以通过先判断获得的上行资 源是否能够承载调度信息与全部緩存数据, 如果否, 则进一步判断获得的上
行资源是否能够承载全部緩存数据, 再根据判断的结果撤销或保留调度信息 的触发状态, 并确定被复用的调度信息和 /或緩存数据,。
参见图 8,本发明提供的数据发送装置的一个实施例的结构示意图,包括: 复用内容确定模块 801 , 用于根据调度信息当前的触发状态、发送緩存数 据所需要上行资源和所获得的上行资源, 确定该调度信息的触发状态, 并确 定被复用的调度信息和 /或緩存数据, 该调度信息为基站为用户设备 UE调度 资源的参考信息; 发送模块 802,用于将该复用内容确定模块确定的被复用的调度信息和緩 存数据复用在传输块中发送。
其中, 参见图 9, 复用内容确定模块 801包括: 第一复用单元、 第二复用 单元、 第三复用单元、 第四复用单元、 第五复用单元、 第六复用单元以及第 七复用单元中的至少一个: 该调度信息包括 BSR和 /或 PHR,该复用内容确定 模块 801包括: 调度信息触发状态判断单元 8011、 上行资源判断单元 8012以 及第一复用单元 8013,
该调度信息触发状态判断单元 8011 , 用于确定 BSR和 PHR的触发状态 为被触发;
该上行资源判断单元 8012, 用于确定上行资源能够承载緩存数据且不能 承载该緩存数据和该 PHR;
第一复用单元 8013, 用于当该调度信息触发状态判断单元确定 BSR和 PHR的触发状态为被触发, 并该上行资源判断单元确定上行资源能够承载緩 存数据且该上行资源不能承载该緩存数据和该 PHR时,保留已触发的 BSR的 触发状态, 并确定复用该 BSR、 PHR和该上行资源的剩余资源能够承载的一 部分该緩存数据。
该调度信息包括 BSR和 /或 PHR,该复用内容确定模块 801包括: 调度信 息触发状态判断单元 8011、 上行资源判断单元 8012以及第二复用单元 8014, 该调度信息触发状态判断单元 8011 , 用于确定 BSR和 PHR的触发状态 为被触发;
该上行资源判断单元 8012, 用于确定上行资源能够承载緩存数据且不能 承载该緩存数据和该 PHR;
第二复用单元 8014, 用于当该调度信息触发状态判断单元确定 BSR和 PHR的触发状态为被触发, 并该上行资源判断单元确定上行资源能够承载緩 存数据并且该上行资源不能承载该緩存数据和该 PHR并且该上行资源不能承 载该緩存数据和该 BSR时,撤销已触发的 BSR的触发状态并确定复用该緩存 数据, 或撤销已触发的 PHR的触发状态并确定复用该緩存数据, 或保留已触 发的 PHR的触发状态并确定复用该緩存数据。
该调度信息包括 BSR和 /或 PHR,该复用内容确定模块 801包括: 调度信 息触发状态判断单元 8011、 上行资源判断单元 8012以及第三复用单元 8015, 该调度信息触发状态判断单元 8011 , 用于确定 BSR和 PHR的触发状态 为被触发;
该上行资源判断单元 8012, 用于确定上行资源能够承载緩存数据且不能 承载该緩存数据和该 PHR;
该第三复用单元 8015,用于当该调度信息触发状态判断单元确定 BSR和 PHR的触发状态为被触发, 并且该上行资源判断单元确定上行资源能够承载 緩存数据并且该上行资源能够承载该緩存数据和该 BSR并且不能承载该緩存 数据、 该 BSR和该 PHR时, 确定复用该緩存数据和该 BSR。
该调度信息包括 BSR和 /或 PHR,该复用内容确定模块 801包括: 调度信 息触发状态判断单元 8011、 上行资源判断单元 8012以及第四复用单元 8016, 该调度信息触发状态判断单元 8011 , 用于确定 BSR和 PHR的触发状态 为被触发;
该上行资源判断单元 8012, 用于确定上行资源能够承载緩存数据且不能 承载该緩存数据和该 PHR;
第四复用单元 8016, 用于当该调度信息触发状态判断单元确定 BSR和 PHR的触发状态为被触发, 并该上行资源判断单元确定上行资源能够承载緩 存数据并且该上行资源能够承载该緩存数据和该 PHR, 且不能承载该緩存数 据、 该 BSR和该 PHR时, 确定复用该緩存数据和该 PHR 。
该调度信息包括 BSR和 /或 PHR,该复用内容确定模块 801包括: 调度信 息触发状态判断单元 8011、 上行资源判断单元 8012以及第五复用单元 8017, 第五复用单元 8017,用于当该调度信息触发状态判断单元确定 BSR的触 发状态为被触发并确定 PHR的触发状态为未被触发,并该上行资源判断单元
确定该上行资源能够承载緩存数据, 撤销已触发的 BSR的触发状态, 并确定 复用该緩存数据。
该调度信息包括 BSR和 /或 PHR,该复用内容确定模块 801包括: 调度信 息触发状态判断单元 8011、 上行资源判断单元 8012以及第六复用单元 8018, 第六复用单元 8018, 用于当该调度信息触发状态判断单元确定 BSR或 PHR的触发状态为被触发, 并该上行资源判断单元确定上行资源能够承载緩 存数据并且该上行资源不能够承载该緩存数据和已触发的 BSR时, 撤销已触 发的 BSR的触发状态, 确定复用该緩存数据; 或,
第六复用单元 8018, 用于当该调度信息触发状态判断单元确定 BSR或 PHR的触发状态为被触发, 并该上行资源判断单元确定上行资源不能够承载 该緩存数据和已触发的 PHR时,撤销已触发的 PHR的触发状态,确定复用该 緩存数据; 或,
第六复用单元 8018, 用于当该调度信息触发状态判断单元确定 BSR或 PHR的触发状态为被触发, 并该上行资源判断单元确定上行资源不能够承载 该緩存数据和已触发的 PHR时,保留 PHR的触发状态,确定复用该緩存数据 并推迟复用该 PHR。
该调度信息包括 BSR和 /或 PHR,该复用内容确定模块 801包括: 调度信 息触发状态判断单元 8011、 上行资源判断单元 8012以及第七复用单元 8019, 第七复用单元 8019, 用于当调度信息包括扩展 PHR, 当该该调度信息触 发状态判断单元确定 BSR和 PHR的触发状态为被触发,并该上行资源判断单 元确定上行资源能够承载緩存数据并且该上行资源能够承载该緩存数据和该 BSR, 且不能承载该緩存数据和该 PHR时, 推迟复用该 PHR, 并确定复用该 緩存数据和该 BSR。
在基站切换过程中, 所述緩存数据包括用户设备的小区无线网络临时标 识和 /或控制面消息。
本实施例提供的装置, 具体可以是用户设备, 其具体实现过程可以参见 方法实施例, 这里不再赘述。
一种用户设备, 所述用户设备包括上述实施例中任一种数据发送装置。 本实施例提供的用户设备, 具体可以移动终端, 与方法实施例属于同一 构思, 其具体实现过程详见方法实施例, 这里不再赘述。
本发明实施例提供的上述技术方案的全部或部分可以通过程序指令相关 的硬件来完成, 所述程序可以存储在可读取的存储介质中, 该存储介质包括:
ROM, RAM, 磁碟或者光盘等各种可以存储程序代码的介质。
以上所述仅为本发明的较佳实施例, 并不用以限制本发明, 凡在本发明 的精神和原则之内, 所作的任何修改、 等同替换、 改进等, 均应包含在本发 明的保护范围之内。
Claims
1、 一种数据发送方法, 其特征在于, 包括:
根据调度信息当前的触发状态、 发送緩存数据所需要上行资源和所获得的 上行资源, 确定所述调度信息的触发状态, 并确定被复用的调度信息和 /或緩存 数据, 所述调度信息为基站为用户设备 UE调度资源的参考信息;
将所述确定的被复用的调度信息和緩存数据复用在传输块中发送。
2、 根据权利要求 1所述的方法, 其特征在于,
所述调度信息包括緩存数据量报告 BSR和 /或功率余量报告 PHR;
所述根据调度信息当前的触发状态、 发送緩存数据所需要上行资源和所获 得的上行资源, 确定所述调度信息的触发状态, 并确定被复用的调度信息和 /或 緩存数据, 包括:
确定 BSR和 PHR的触发状态为被触发,并确定上行资源能够承载緩存数据, 当所述上行资源不能承载所述緩存数据和所述 PHR时,保留已触发的 BSR的触 发状态, 并确定复用所述 BSR、 PHR和所述上行资源的剩余资源能够^载的一 部分所述緩存数据; 或,
确定 BSR和 PHR的触发状态为被触发,并确定上行资源能够承载緩存数据, 当所述上行资源不能承载所述緩存数据和所述 PHR, 且不能承载所述緩存数据 和所述 BSR时,撤销已触发的 BSR的触发状态并确定复用所述緩存数据, 或撤 销已触发的 PHR 的触发状态并确定复用所述緩存数据, 或保留已触发的 PHR 的触发状态并确定复用所述緩存数据; 或,
确定 BSR和 PHR的触发状态为被触发,并确定上行资源能够承载緩存数据, 当所述上行资源能够承载所述緩存数据和所述 BSR,且不能承载所述緩存数据、 所述 BSR和所述 PHR时, 将确定复用所述緩存数据和所述 BSR; 或,
确定 BSR和 PHR的触发状态为被触发,并确定上行资源能够承载緩存数据, 当所述上行资源能够承载所述緩存数据和所述 PHR,且不能承载所述緩存数据、 所述 BSR和所述 PHR时, 将确定复用所述緩存数据和所述 PHR。
3、 根据权利要求 1所述的方法, 其特征在于, 所述根据调度信息当前的触 发状态、 发送緩存数据所需要上行资源和所获得的上行资源, 确定所述调度信 息的触发状态, 并确定被复用的调度信息和 /或緩存数据, 包括:
确定 BSR的触发状态为被触发, 并确定 PHR的触发状态为未被触发, 并 确定所述上行资源能够承载緩存数据;
撤销已触发的 BSR的触发状态, 并确定复用所述緩存数据。
4、 根据权利要求 1所述的方法, 其特征在于, 所述根据调度信息当前的触 发状态、 发送緩存数据所需要上行资源和所获得的上行资源, 确定所述调度信 息的触发状态, 并确定被复用的调度信息和 /或緩存数据, 包括:
确定 BSR或 PHR的触发状态为被触发,并确定上行资源能够承载緩存数据, 当所述上行资源不能够承载所述緩存数据和已触发的 BSR 时, 撤销已触发的 BSR的触发状态, 确定复用所述緩存数据; 或,
确定 BSR或 PHR的触发状态为被触发,并确定上行资源能够承载緩存数据, 当所述上行资源不能够承载所述緩存数据和已触发的 PHR 时, 撤销已触发的 PHR的触发状态, 确定复用所述緩存数据; 或,
确定 BSR或 PHR的触发状态为被触发,并确定上行资源能够承载緩存数据, 当所述上行资源不能够承载所述緩存数据和已触发的 PHR时,保留 PHR的触发 状态, 确定复用所述緩存数据并推迟复用所述 PHR。
5、 根据权利要求 1 所述的方法, 其特征在于, 当调度信息包括扩展 PHR 时, 根据调度信息当前的触发状态、 发送緩存数据所需要上行资源和所获得的 上行资源, 确定所述调度信息的触发状态, 并确定被复用的调度信息和 /或緩存 数据, 包括:
确定 BSR和 PHR的触发状态为被触发,并确定上行资源能够承载緩存数据; 当所述上行资源能够承载所述緩存数据和所述 BSR, 且不能承载所述緩存 数据和所述 PHR时,推迟复用所述 PHR,并确定复用所述緩存数据和所述 BSR。
6、 根据权利要求 1~5任一项所述的方法, 其特征在于,
所述緩存数据包括用户设备的小区无线网络临时标识和 /或控制面消息。
7、 一种数据发送装置, 其特征在于, 包括: 复用内容确定模块, 用于根据调度信息当前的触发状态、 发送緩存数据所 需要上行资源和所获得的上行资源, 确定所述调度信息的触发状态, 并确定被 复用的调度信息和 /或緩存数据, 所述调度信息为基站为用户设备 UE调度资源 的参考信息;
发送模块, 用于将所述复用内容确定模块确定的被复用的调度信息和緩存 数据复用在传输块中发送。
8、 根据权利要求 7所述的装置, 其特征在于, 所述调度信息包括 BSR和 / 或 PHR, 所述复用内容确定模块包括: 调度信息触发状态判断单元、 上行资源 判断单元以及第一复用单元,
所述调度信息触发状态判断单元,用于确定 BSR和 PHR的触发状态为被触 发;
所述上行资源判断单元, 用于确定上行资源能够承载緩存数据且不能承载 所述緩存数据和所述 PHR;
第一复用单元,用于当所述调度信息触发状态判断单元确定 BSR和 PHR的 触发状态为被触发, 并所述上行资源判断单元确定上行资源能够承载緩存数据 且所述上行资源不能承载所述緩存数据和所述 PHR时,保留已触发的 BSR的触 发状态, 并确定复用所述 BSR、 PHR和所述上行资源的剩余资源能够^载的一 部分所述緩存数据。
9、 根据权利要求 7所述的装置, 其特征在于, 所述调度信息包括 BSR和 / 或 PHR, 所述复用内容确定模块包括: 调度信息触发状态判断单元、 上行资源 判断单元以及第二复用单元,
所述调度信息触发状态判断单元,用于确定 BSR和 PHR的触发状态为被触 发;
所述上行资源判断单元, 用于确定上行资源能够承载緩存数据且不能承载 所述緩存数据和所述 PHR;
第二复用单元,用于当所述调度信息触发状态判断单元确定 BSR和 PHR的 触发状态为被触发, 并所述上行资源判断单元确定上行资源能够承载緩存数据 并且所述上行资源不能承载所述緩存数据和所述 PHR并且所述上行资源不能承 载所述緩存数据和所述 BSR时,撤销已触发的 BSR的触发状态并确定复用所述 緩存数据, 或撤销已触发的 PHR的触发状态并确定复用所述緩存数据, 或保留 已触发的 PHR的触发状态并确定复用所述緩存数据。
10、 根据权利要求 7所述的装置, 其特征在于, 所述调度信息包括 BSR和 / 或 PHR, 所述复用内容确定模块包括: 调度信息触发状态判断单元、 上行资源 判断单元以及第三复用单元,
所述调度信息触发状态判断单元,用于确定 BSR和 PHR的触发状态为被触 发;
所述上行资源判断单元, 用于确定上行资源能够承载緩存数据且不能承载 所述緩存数据和所述 PHR;
第三复用单元,用于当所述调度信息触发状态判断单元确定 BSR和 PHR的 触发状态为被触发, 并且所述上行资源判断单元确定上行资源能够承载緩存数 据并且所述上行资源能够承载所述緩存数据和所述 BSR并且不能承载所述緩存 数据、 所述 BSR和所述 PHR时, 确定复用所述緩存数据和所述 BSR。
11、 根据权利要求 7所述的装置, 其特征在于, 所述调度信息包括 BSR和 / 或 PHR, 所述复用内容确定模块包括: 调度信息触发状态判断单元、 上行资源 判断单元以及第四复用单元,
所述调度信息触发状态判断单元,用于确定 BSR和 PHR的触发状态为被触 发;
所述上行资源判断单元, 用于确定上行资源能够承载緩存数据且不能承载 所述緩存数据和所述 PHR;
第四复用单元,用于当所述调度信息触发状态判断单元确定 BSR和 PHR的 触发状态为被触发, 并所述上行资源判断单元确定上行资源能够承载緩存数据 并且所述上行资源能够承载所述緩存数据和所述 PHR, 且不能承载所述緩存数 据、 所述 BSR和所述 PHR时, 确定复用所述緩存数据和所述 PHR 。
12、 根据权利要求 7所述的装置, 其特征在于, 所述调度信息包括 BSR和 / 或 PHR, 所述复用内容确定模块包括: 调度信息触发状态判断单元、 上行资源 判断单元以及第五复用单元,
第五复用单元, 用于当所述调度信息触发状态判断单元确定 BSR的触发状 态为被触发并确定 PHR的触发状态为未被触发,并所述上行资源判断单元确定 所述上行资源能够承载緩存数据, 撤销已触发的 BSR的触发状态, 并确定复用 所述緩存数据。
13、 根据权利要求 7所述的装置, 其特征在于, 所述调度信息包括 BSR和 / 或 PHR, 所述复用内容确定模块包括: 调度信息触发状态判断单元、 上行资源 判断单元以及第六复用单元,
第六复用单元,用于当所述调度信息触发状态判断单元确定 BSR或 PHR的 触发状态为被触发, 并所述上行资源判断单元确定上行资源能够承载緩存数据 并且所述上行资源不能够承载所述緩存数据和已触发的 BSR时, 撤销已触发的 BSR的触发状态, 确定复用所述緩存数据; 或,
所述第六复用单元, 用于当所述调度信息触发状态判断单元确定 BSR或 PHR 的触发状态为被触发, 并所述上行资源判断单元确定上行资源不能够承载 所述緩存数据和已触发的 PHR时,撤销已触发的 PHR的触发状态,确定复用所 述緩存数据; 或,
所述第六复用单元, 用于当所述调度信息触发状态判断单元确定 BSR或 PHR 的触发状态为被触发, 并所述上行资源判断单元确定上行资源不能够承载 所述緩存数据和已触发的 PHR时,保留 PHR的触发状态,确定复用所述緩存数 据并推迟复用所述 PHR。
14、 根据权利要求 7所述的装置, 其特征在于, 所述调度信息包括 BSR和 / 或 PHR, 所述复用内容确定模块包括: 调度信息触发状态判断单元、 上行资源 判断单元以及第七复用单元,
第七复用单元, 用于当调度信息包括扩展 PHR, 当所述所述调度信息触发 状态判断单元确定 BSR和 PHR的触发状态为被触发,并所述上行资源判断单元 确定上行资源能够承载緩存数据并且所述上行资源能够承载所述緩存数据和所 述 BSR, 且不能承载所述緩存数据和所述 PHR时, 推迟复用所述 PHR, 并确定 复用所述緩存数据和所述 BSR。
15、 根据权利要求 7~14任一项所述的装置, 其特征在于, 所述緩存数据包 括用户设备的小区无线网络临时标识和 /或控制面消息。
16、 一种用户设备, 其特征在于, 所述用户设备包括上述权利要求 7~12所 述的任一项数据发送装置。
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP18151520.6A EP3367724A1 (en) | 2011-03-31 | 2012-03-21 | Method and device for transmitting data |
EP12762792.5A EP2677804B1 (en) | 2011-03-31 | 2012-03-21 | Method and device for transmitting data |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201110081210.4 | 2011-03-31 | ||
CN201110081210.4A CN102740483B (zh) | 2011-03-31 | 2011-03-31 | 数据发送方法和装置 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2012130062A1 true WO2012130062A1 (zh) | 2012-10-04 |
Family
ID=46929435
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2012/072660 WO2012130062A1 (zh) | 2011-03-31 | 2012-03-21 | 数据发送方法和装置 |
Country Status (3)
Country | Link |
---|---|
EP (2) | EP3367724A1 (zh) |
CN (1) | CN102740483B (zh) |
WO (1) | WO2012130062A1 (zh) |
Families Citing this family (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2015035579A1 (zh) * | 2013-09-11 | 2015-03-19 | 华为技术有限公司 | 一种数据传输方法及用户设备 |
US20160014794A1 (en) * | 2014-07-08 | 2016-01-14 | Htc Corporation | Device and Method of Handling Device-to-Device communication |
CN109906646B (zh) * | 2016-11-30 | 2021-02-12 | 华为技术有限公司 | 信息传输方法、基站和终端设备 |
CN108924930B (zh) * | 2017-03-24 | 2024-05-21 | 华为技术有限公司 | 无线连接建立方法及装置 |
EP3689058A4 (en) | 2017-09-28 | 2021-05-05 | Nokia Technologies Oy | METHOD, DEVICE, COMPUTER PROGRAM PRODUCT AND COMPUTER PROGRAM |
CN109587781A (zh) * | 2017-09-29 | 2019-04-05 | 中兴通讯股份有限公司 | 信息上报方法及装置 |
JP7053823B2 (ja) * | 2017-10-30 | 2022-04-12 | ノキア テクノロジーズ オサケユイチア | 方法、装置、コンピュータプログラム製品およびコンピュータプログラム |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101127748A (zh) * | 2006-08-15 | 2008-02-20 | 大唐移动通信设备有限公司 | Ofdm移动通信系统中上行同步命令字的发送方法及装置 |
CN101296480A (zh) * | 2007-04-26 | 2008-10-29 | 中兴通讯股份有限公司 | 增强上行链路调度信息的触发及数据分配方法和装置 |
CN101925128A (zh) * | 2009-06-17 | 2010-12-22 | 大唐移动通信设备有限公司 | 一种上报缓存状态报告的方法及装置 |
Family Cites Families (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP2136586B1 (en) * | 2008-06-18 | 2017-11-08 | LG Electronics Inc. | Method of transmitting power headroom reporting in wireless communication system |
-
2011
- 2011-03-31 CN CN201110081210.4A patent/CN102740483B/zh not_active Expired - Fee Related
-
2012
- 2012-03-21 EP EP18151520.6A patent/EP3367724A1/en not_active Withdrawn
- 2012-03-21 EP EP12762792.5A patent/EP2677804B1/en not_active Not-in-force
- 2012-03-21 WO PCT/CN2012/072660 patent/WO2012130062A1/zh active Application Filing
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101127748A (zh) * | 2006-08-15 | 2008-02-20 | 大唐移动通信设备有限公司 | Ofdm移动通信系统中上行同步命令字的发送方法及装置 |
CN101296480A (zh) * | 2007-04-26 | 2008-10-29 | 中兴通讯股份有限公司 | 增强上行链路调度信息的触发及数据分配方法和装置 |
CN101925128A (zh) * | 2009-06-17 | 2010-12-22 | 大唐移动通信设备有限公司 | 一种上报缓存状态报告的方法及装置 |
Non-Patent Citations (1)
Title |
---|
See also references of EP2677804A4 * |
Also Published As
Publication number | Publication date |
---|---|
EP2677804A1 (en) | 2013-12-25 |
CN102740483A (zh) | 2012-10-17 |
EP3367724A1 (en) | 2018-08-29 |
EP2677804B1 (en) | 2018-05-09 |
EP2677804A4 (en) | 2014-04-02 |
CN102740483B (zh) | 2015-09-23 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11178656B2 (en) | Method and apparatus of operating multiple time alignment timers in mobile communication system supporting carrier aggregation | |
JP6630785B2 (ja) | コンポーネント・キャリアを監視および処理するための方法および装置 | |
TWI422266B (zh) | 無線通訊系統中改善上鏈路傳輸之方法及相關裝置 | |
JP5654068B2 (ja) | 無線通信システムにおける方法及び装置 | |
RU2768363C2 (ru) | Способ передачи данных и устройство | |
KR101768738B1 (ko) | 캐리어 집적을 이용하는 불연속 수신 모드에서의 동작 | |
US9814075B2 (en) | Method and apparatus for transmitting and receiving data using plurality of carriers in mobile communication system | |
CN104737613B (zh) | 在无线通信系统中执行用于调度请求的退避的方法和设备 | |
JP2020511805A (ja) | 切り捨てられたバッファステータスレポーティング | |
WO2012130062A1 (zh) | 数据发送方法和装置 | |
US20220078771A1 (en) | Method and apparatus of operating multiple time alignment timers in mobile communication system supporting carrier aggregation | |
WO2013139302A1 (zh) | 上行功率控制方法、网络节点及系统 | |
WO2012159496A1 (zh) | 一种资源调度指示方法及装置 | |
WO2014134785A1 (zh) | 状态切换的方法、装置和系统 | |
WO2009100668A1 (zh) | 一种触发资源配置的方法、装置及系统 | |
JP6101486B2 (ja) | バッファ状態報告の送信制御方法、ユーザ装置、および無線通信システム | |
WO2019062838A1 (zh) | 数据传输方法及装置 | |
US9107118B2 (en) | Method for signaling a mobile wireless device to switch to a preset carrier in a multi-carrier 4G network | |
WO2013166670A1 (zh) | 上行信道资源配置方法和设备 | |
CN109156020A (zh) | 调度请求触发方法、装置和系统 | |
JP2022529576A (ja) | Sl sr/bsr処理のための方法 | |
WO2010066171A1 (zh) | 调度信息上报方法、装置及系统 | |
WO2012083855A1 (zh) | 一种移动终端和上行增强随机接入信道接入的方法 | |
CN109644475A (zh) | 数据传输方法、装置和系统 | |
CN116114332A (zh) | 用于通信的方法、设备和计算机存储介质 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 12762792 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2012762792 Country of ref document: EP |
|
NENP | Non-entry into the national phase |
Ref country code: DE |