WO2012072050A1 - 数据传输的方法和装置 - Google Patents

数据传输的方法和装置 Download PDF

Info

Publication number
WO2012072050A1
WO2012072050A1 PCT/CN2011/083466 CN2011083466W WO2012072050A1 WO 2012072050 A1 WO2012072050 A1 WO 2012072050A1 CN 2011083466 W CN2011083466 W CN 2011083466W WO 2012072050 A1 WO2012072050 A1 WO 2012072050A1
Authority
WO
WIPO (PCT)
Prior art keywords
tfi
block
downlink
shared
terminal
Prior art date
Application number
PCT/CN2011/083466
Other languages
English (en)
French (fr)
Inventor
赵旸
房明
Original Assignee
华为技术有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to BR112013013685-5A priority Critical patent/BR112013013685B1/pt
Priority to EP11845612.8A priority patent/EP2648372B1/en
Publication of WO2012072050A1 publication Critical patent/WO2012072050A1/zh

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/40Connection management for selective distribution or broadcast
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W8/00Network data management
    • H04W8/26Network addressing or numbering for mobility support

Definitions

  • TECHNICAL FIELD The present invention relates to the field of mobile communication technologies, and in particular, to a method and apparatus for data transmission in a wireless communication system.
  • a wireless interface uses a combination of TDMA (Time Division Multiple Access) and FDMA (frequency division multiple access).
  • TDMA Time Division Multiple Access
  • FDMA frequency division multiple access
  • the frequency band allocated by the system is divided into at least two frequency points of 200 kHz, and the user communicates at different frequency points, and each frequency point is divided into 8 time slots of about 0.577 milliseconds in time, and the period of each time slot is 8x0.577 « 4.6 milliseconds.
  • a voice TCH Traffic Channel
  • GSM Global System for Mobile Communications
  • the GPRS General Packet Radio Service
  • GSM Global System for Mobile Communications
  • each time slot can carry one PDCH (Packet Data Channel), but unlike TCH, one PDCH can be shared by at least two terminals, and one terminal can also be allocated at least two.
  • PDCH Packet Data Channel
  • GP RS introduces the concept of data blocks. A burst with the same slot number on four consecutive TDM frames is called a data block.
  • the data block is the basic unit of GPRS for data transmission. The division of the data block is as shown in FIG. 1.
  • One PDCH is repeated in time with 52 TDMA frames, and each cycle is called a 52 multiframe, which is divided into 12 data blocks (Block 0 to Block 1 1) are used to transmit data and higher layer signaling.
  • two frames are used to transmit time advance information, and two frames do not transmit information, but are used for terminal neighbor measurement. Wait.
  • TBF Temporal Block Flow
  • TFI Temporal Flow Identity
  • a method for downlink data transmission of a GP RS in the prior art is: the network side terminal sends a packet downlink link data packet assignment message carrying the frequency and slot information of the PDCH and the TFI allocated to the terminal. . After receiving the Packet Downlink Assignment message, the terminal establishes a downlink TBF with the network side.
  • the terminal monitors the downlink PDCH according to the frequency and time slot information of the PDCH carried in the Packet Downlink Assignment message, parses the block header of the data block in the downlink PDCH, and allocates the TFI in the block header of the data block to When the TFI of the terminal is the same, the terminal considers that the data block is sent to itself and will parse the specific content in the data block. Use the TFI allocated to itself in an exclusive way. Each terminal corresponds to one TFL and the TFI resources of the GPRS system are limited.
  • Embodiments of the present invention provide a method and apparatus for data transmission to save TFI resources of a G P RS system.
  • a data transmission method includes: The network side allocates a shared temporary block flow indication TFI to at least two terminals, and sends the shared TFI to the at least two terminals;
  • the network side sends the downlink block to the at least two terminals, where the downlink block header carries the shared TFI, so that the terminal that receives the downlink block parses the content of the downlink block according to the shared TFI.
  • a data transmission device is disposed on the network side, and includes:
  • the temporary block flow indicates a TFI assignment module, configured to allocate a shared TFI to at least two terminals, and send the shared TFI to the at least two terminals;
  • a downlink block transmission module configured to send a downlink block to the at least two terminals, where the downlink block header carries the shared TFI, so that the terminal that receives the downlink block parses the downlink block according to the shared TFI Content.
  • a data processing method including:
  • a terminal comprising:
  • a first receiving module configured to receive a downlink assignment message or a broadcast message sent by the network side, where the downlink assignment message or the broadcast message includes an allocated shared temporary block flow indication TFI;
  • a data processing module configured to receive a downlink block that is sent by the network side and that carries the shared TFI, and parse the content of the downlink block according to the shared TFI.
  • the embodiment of the present invention can save the TFI resources of the wireless communication system by allocating a shared TFI to at least two terminals, thereby saving the downlink channel transmission of the wireless communication system. Resources.
  • FIG. 1 is a schematic diagram showing a manner of dividing a data block in a 52 multiframe of a G PRS system in the prior art
  • FIG. 2 is a process flow diagram of a data transmission method on a network side according to Embodiment 1 of the present invention
  • FIG. 3 is a process flow diagram of a data processing method on a terminal side according to Embodiment 2 of the present invention.
  • FIG. 4 is a flowchart of processing a downlink data transmission method in a wireless communication system according to Embodiment 3 of the present invention.
  • FIG. 5 is a specific structural diagram of a data transmission apparatus on a network side according to an embodiment of the present invention
  • FIG. 6 is a specific structural diagram of a terminal according to an embodiment of the present invention.
  • FIG. 2 The processing flow of a network side data transmission method provided by this embodiment is shown in FIG. 2, and the package The following processing steps are included:
  • Step 21 The network side allocates a shared TFI to at least two terminals, and sends the shared TFI to the at least two terminals.
  • the network side determines, according to at least one of the current downlink resource usage, the user subscription information, and the terminal capability information, whether to allocate a shared TFI to at least two terminals, and when determining that the shared TFI is allocated to at least two terminals, the network side terminal
  • a downlink assignment message or a broadcast message carrying the shared TFI and the frequency information of the downlink channel allocated to the at least two terminals and the slot information, the broadcast message may include a system message.
  • the at least two terminals may be grouped.
  • the network side needs to save the group identifier to which each terminal belongs, and the terminal side needs to save the group identifier to which the terminal belongs.
  • the downlink identifier corresponding to the shared TFI may be further included in the downlink assignment message or the broadcast message; or, the network side specifies a field or a new field in the block header of the downlink block that is sent to the terminal, and carries the shared TFI corresponding Group ID.
  • the network side can also allocate all the downlink blocks in a certain period to each terminal, and the network side needs to save the block number of the downlink block to which each terminal belongs. Then, in the downlink assignment message or the broadcast message, the block number information of the downlink block to which each terminal belongs may be carried, and the block number of the downlink block to which the terminal belongs needs to be saved on the terminal side.
  • the downlink block may be a downlink data block or a control block, and the control block may carry signaling.
  • the terminal monitors the downlink channel according to the frequency information and the time slot information of the downlink channel carried in the downlink assignment message or the broadcast message, and after intercepting and receiving the downlink block that is sent by the network side and carrying the shared TFI, parsing the block header of the downlink block
  • the terminal considers that the data block is sent to itself, and the specific content in the downlink block is parsed.
  • the message may further include a packet identifier corresponding to the shared TFI; or, after the specified field or the newly added field in the block header of the downlink block carries the packet identifier corresponding to the shared TFI. Determining, by the terminal, that the downlink identifier corresponding to the shared TFI is the same as the packet identifier to which the shared TFI belongs, and the TFI carried in the block header of the downlink block is the same as the shared TFI allocated to the terminal, to determine that the downlink block is sent to the user. And parsing the specific content in the downlink block.
  • the terminal When the network side divides all the downlink blocks in a certain period into the respective terminals, and after the downlink assignment message or the broadcast message further includes the block number information of the downlink block to which each terminal belongs, the terminal according to the block number of the downlink block
  • the information is the same as the block number information of the downlink block to which it belongs, and the TFI carried in the block header of the downlink block is the same as the shared TFI allocated to the terminal, to determine that the downlink block is sent to itself, and parses the downlink.
  • the specific content in the block is the same as the block number information of the downlink block to which it belongs.
  • the shared TFI is allocated to the at least two terminals, and the network side can simultaneously send the shared downlink block to the at least two terminals, and the downlink data block or the control block is not required to be repeatedly transmitted for each terminal.
  • Embodiment 2 The processing flow of a data processing method on the terminal side provided by this embodiment is as shown in FIG. 3, and includes the following processing steps:
  • Step 31 The terminal receives a downlink assignment message or a broadcast message sent by the network side, where the downlink assignment message or the broadcast message includes the allocated shared TFI.
  • the above broadcast message may include a system message.
  • the at least two terminals may be grouped, and the terminal identifier to which the terminal belongs needs to be saved on the terminal side. Then, the downlink identifier corresponding to the shared TFI may be carried in the downlink assignment message or the broadcast message; or the designated field or the newly added field in the block header of the downlink block sent by the network side received by the terminal may further carry the identifier
  • the packet identifier corresponding to the shared TFI is described.
  • the network side can also divide all downlink blocks in a certain period into different And the downlink information of the downlink block to which the terminal belongs may be carried in the downlink assignment message or the broadcast message, and the identifier of the downlink block to which the terminal belongs needs to be saved on the terminal side.
  • the identification information of the downlink block may be block number information of the downlink block.
  • Step 32 The terminal receives the downlink block that is sent by the network side and carries the shared TFI, and parses the content of the downlink block according to the shared TFI.
  • the downlink block may be a downlink data block or a control block, and the control block may carry signaling.
  • the terminal monitors the downlink channel according to the frequency information and the time slot information of the downlink channel carried in the downlink assignment message or the broadcast message, and after intercepting and receiving the downlink block that is sent by the network side and carrying the shared TFI, parsing the block header of the downlink block
  • the terminal considers that the data block is sent to itself, and the specific content in the downlink block is parsed.
  • the downlink assignment message or the broadcast message may further include the group identifier corresponding to the shared TFI; or, the designated field or the newly added field in the block header of the downlink block
  • the packet identifier corresponding to the TFI is shared. Determining, by the terminal, that the downlink identifier corresponding to the shared TFI is the same as the packet identifier to which the shared TFI belongs, and the TFI carried in the block header of the downlink block is the same as the shared TFI allocated to the terminal, to determine that the downlink block is sent to the user. And parsing the specific content in the downlink block.
  • the terminal When the network side divides all the downlink blocks in a certain period into the respective terminals, and after the downlink assignment message or the broadcast message further includes the block number information of the downlink block to which each terminal belongs, the terminal according to the block number of the downlink block
  • the information is the same as the block number information of the downlink block to which it belongs, and the TFI carried in the block header of the downlink block is the same as the shared TFI allocated to the terminal, to determine that the downlink block is sent to itself, and parses the downlink.
  • the specific content in the block is the same as the block number information of the downlink block to which it belongs.
  • the network side can allocate all the downlink blocks in a certain period to each terminal, and the terminal receives the uplink assignment message that is sent by the network side and carries the uplink USF (link status flag) allocated to the terminal. Then, the terminal receives the downlink block that is sent by the network side and carries the shared TFI and the USF, and the USF carried in the downlink block is the same as the USF to which it belongs, and the next The shared TFI carried in the row block determines that the downlink block is sent to itself and parses the content of the downlink block.
  • the terminal parses the shared downlink block sent by the network side to the at least two terminals simultaneously according to the shared TFI allocated by the network side, and the network side does not need to repeatedly send the downlink data block or the control block separately for each terminal, thereby The TFI resources of the GPRS system and the transmission resources of the downlink channel can be saved.
  • Embodiment 3
  • the processing flow of the method for downlink data transmission in a wireless communication system provided by this embodiment is as shown in FIG. 4, and includes the following processing steps:
  • Step 41 The network side determines whether to allocate the shared TFI to at least two terminals.
  • the BSS (Base Station Subsystem) on the network side can determine whether to allocate the shared TFI to at least two terminals according to the current downlink resource usage, user subscription information, and terminal capabilities.
  • the BSS determines that the shared TFI needs to be allocated to at least two terminals.
  • the BSS determines that the shared TFI needs to be allocated to at least two terminals.
  • step 42 is performed.
  • Step 42 The network side carries the shared TFI and the corresponding indication information allocated to the at least two terminals in the downlink assignment message sent to the terminal.
  • a new indication information is added to the downlink assignment message sent by the BSS to the terminal, and the new indication information is used to indicate whether to allocate the shared TFI to the terminal.
  • the following describes the embodiment of the present invention by taking the downlink assignment message as a Packet Downlink ASSIGNMENT message as an example. Add a new indication message to the Packet Downlink ASSIGNMENT message.
  • the format of the information element in the Packet Downlink ASSIGNMENT message with the new indication added is as follows:
  • the BSS When the BSS needs to allocate a shared TFI to at least two terminals, it may choose to set the value of the indication of shared TFI field in the Packet Downlink ASSIGNMENT message to 1 and send it to the terminal. Then, the BSS may allocate the same PDCH frequency and time slot information to the at least two terminals by using a message such as a Packet Downlink Assignment message.
  • the TFI carried in the Packet Downlink Assignment message is confirmed as a BSS.
  • Step 43 After the downlink channel assignment is completed, when the BSS needs to send the downlink data block or the control block (the carrying signaling) shared by the at least two terminals, the BSS carries the foregoing in the downlink data block or the block header of the control block.
  • the TFI is shared, and the downlink data block or the control block is sent to the at least two terminals at one time.
  • the terminal determines whether the network is based on the received data block or the TFI carried in the control block.
  • the network side assigns its own TFI, and if so, parses the data block or the specific content in the control block.
  • the format of the block header carrying the data block sharing the TFI is as follows:
  • the CPS BSN2 5 terminal monitors the downlink PDCH according to the frequency and time slot information of the PDCH carried in the Packet Downlink Assignment message, and parses the data block in the downlink PDCH or the block header of the control block, and the TFI carried in the block header of the data block or the control block.
  • the terminal considers that the data block is sent to itself, and will parse the specific content in the data block or control block.
  • At least two terminals sharing the same TFI may be further grouped, and each group of terminals is identified by a Group ID, and the definition of the Group ID may be determined according to terminal capabilities, subscription attributes, and the like.
  • the Group ID can be used to identify the two sets of M2M terminals.
  • the specified group identification information may be carried by a specified field or a new field in an encoding format of the data block.
  • MCS-9 the format of the block header of the data block carrying the Group ID through the RRBP and ES/P fields is as follows: Octet
  • the Group ID is used to indicate which current downlink block or control block is sent to which group.
  • the Group ID can represent up to 8 packets in 3 bits.
  • terminals belonging to at least two groups can share the same TFI, further saving downlink scheduling resources.
  • the GA display group identifier is invalid, the downlink data block or control block that is delivered is shared by all terminals sharing the TFI, otherwise it is shared by the terminals belonging to the group.
  • the above group identifiers have a maximum of 8 groups because of the limitation of 3 bits.
  • the present invention can also extend other fields to expand the range of values of the group identifiers.
  • the above GA information can be indicated by the PR field in the format of the block header of the data block.
  • the value of the PR field is as follows:
  • the PR field Group ID can be extended to represent up to 16 packets with 4 bits.
  • the BSS when the BSS needs to send the downlink data block or the control block shared by the at least two terminals, the BSS carries the shared TFI and the specified Group ID in the downlink data block or the control block, and the downlink data block is used. Or the control block is distributed to the at least two terminals through the downlink PDCH.
  • the terminal monitors the downlink PDCH according to the frequency and time slot information of the PDCH carried in the Packet Downlink Assignment message, and parses the data block of the downlink PDCH or the block header of the control block, and the Group ID carried in the block header of the data block or the control block.
  • the terminal considers that the data block or the control block is sent to itself, and parses the data block or the specific part in the control block.
  • the above method effectively avoids waste of transmission resources caused by multiple transmissions of the same data to different terminals on the network side, but this also limits the terminal from receiving shared data and exclusive data at the same time. Therefore, the network side can further allocate the shared TFI and the exclusive TFI to the terminal at the same time.
  • the format of the information element in the TFI Packet Downlink Assignment message carrying the shared TFI and exclusive TFI allocated to the terminal is as follows:
  • the value of the indication of shared TFI field in the above message is 0, indicating that the ⁇ Global TFI> assigned to the terminal is an exclusive TFI, and the value of the indication of shared TFI field in the message is 1 indicating that the terminal is allocated to the terminal. ? 1> is the shared TFI.
  • the network side can also choose to allocate an exclusive TFI to the terminal by using the non-shared global TFI field.
  • the network side may simultaneously allocate a shared TFI and an exclusive TFI to the terminal in the downlink assignment message. In this way, when the shared information needs to be delivered, the shared TFI identifier is carried in the downlink data block or the control block.
  • the exclusive TFI identifier is carried in the downlink data block or the control block. Since both TFIs are allocated to the terminal, the terminal can determine whether the downlink data block or the control block belongs to itself, regardless of which downlink data block or control block of the TFI is carried, thereby parsing the downlink data block or Control block content.
  • the network side After the shared data is sent by the network side in the above method, the terminal cannot respond. However, for some data/signaling that needs to be answered, the network side still wants the terminal to respond. Therefore, the network side can further allocate a temporary number to the terminal sharing the TFI when performing downlink assignment as follows:
  • the RRBP field specifies the corresponding reserved block for the terminal to reply back.
  • the network side sends the shared information, when the temporary number of the receiving terminal is 1, the reserved block in the RRBP replies back; when the temporary number of the receiving terminal is 2, the last block of the reserved block is specified in the RRBP. Answer on. For example: Two terminals share the downlink TFI, and the network side specifies in the downlink assignment message that the temporary number of one of the terminals is 0001 and the other is 0010.
  • the shared TFI is allocated to at least two terminals, so that the network side can simultaneously schedule at least two terminals to receive the shared downlink data block or the control block, thereby saving the TFI resources of the GPRS system.
  • the network side of the GPRS system can simultaneously transmit the downlink data/control messages shared by the at least two terminals to the at least two terminals by using the downlink data block or the control block that carries the shared TFI, and does not need to repeatedly send the terminal separately for each terminal.
  • the downlink data block or the control block can save the transmission resources of the downlink channel of the GPRS system.
  • Embodiment 4 By grouping at least two terminals, a more flexible way of sharing TFI resources can be achieved. Embodiment 4
  • the BSS on the network side can also reserve a TFI value (such as 31) in advance, which is dedicated to TFI sharing.
  • a TFI value such as 31
  • the above reserved TFI value may be pre-configured or dynamically changed.
  • the reserved TFI value may be sent to the terminal by using a broadcast message, which may be: a system message (such as a SI2quater message), a paging message, and the like.
  • a broadcast message which may be: a system message (such as a SI2quater message), a paging message, and the like.
  • the reserved TFI value is carried in the Rest Octets of the SI2quater message by the newly added indication.
  • GPRS Real Time Difference Description: ⁇ GPRS— Real Time Difference Description struct »
  • GPRS REPORT PRIORITY Description: ⁇ GPRS— REPORT — PRIORITY Description struct » ⁇
  • NC Measurement Parameters ⁇ NC Measurement Parameters struct » ⁇
  • SI2quater Rest Octets >::
  • the BSS performs a normal downlink assignment process, and does not display whether the currently allocated TFI is shared in the Packet Downlink Assignment message, but indicates that the TFI is set to the reserved TFI (that is, the value sent in the broadcast message).
  • TFI is a shared TFI. For example, when the reserved TFI value is 31, the BSS allocates a value of TFI of 31 to the terminal in the downlink assignment message, and the terminal can know that the TFI is a shared TFI.
  • the BSS when the BSS needs to send the downlink data block or the control block shared by the at least two terminals, the BSS carries the reserved TFI in the downlink data block or the block header of the control block, and the downlink data block or the control The block is broadcast to the at least two terminals through the downlink PDCH.
  • the terminal monitors the downlink PDCH according to the frequency and time slot information of the PDCH carried in the Packet Downlink Assignment message, and parses the data block of the downlink PDCH or the block header of the control block, and the TFI carried in the block header of the data block or the control block and the foregoing When the remaining TFI is the same, the terminal considers that the data block or control block is sent to itself, and will parse the specific content in the data block or control block.
  • At least two terminals are allocated to share the reserved TFI, so that the network side can simultaneously schedule at least two terminals to receive the shared downlink information, thereby saving the TFI resources of the GPRS system.
  • the network side of the GPRS system can simultaneously transmit the downlink data/control messages shared by the at least two terminals to the at least two terminals by using the downlink data block or the control block that carries the shared TFI, and does not need to repeatedly send the terminal separately for each terminal.
  • the downlink data block or the control block can save the transmission resources of the downlink channel of the GPRS system.
  • the BSS on the network side needs to send the information of the data block to which the terminal belongs in the BO ⁇ B1 1 data block to each terminal, and the information of the data block to which the above belongs belongs can be expressed in various manners. For example, each of the data blocks in the period of one data frame and each of the at least two terminals are numbered by the same bit, and the data block having the same number is associated with the terminal.
  • the network side specifies the radio block number that the terminal needs to monitor in the downlink assignment message, because a 52 multiframe has 12 blocks, and the bit corresponding to the bit is 1 is the data block to which the terminal belongs.
  • the data block and the terminal can be numbered by 4 bits in the downlink assignment message, and the data block having the same number is associated with the terminal.
  • the data block number is modulo 2, the value 0 is assigned to the terminal 1, and the value 1 is assigned to the terminal 2.
  • the modulus is not limited, it can be 2, 3, 4, etc. At the same time, this method can also be applied to the frame number.
  • the BSS on the network side may directly indicate the validity period of the shared TFI to the terminal in the Packet Downlink Assignment message. For example, adding a starting block number and an ending block number to the message indicates that the TFI is valid for the terminal during this period of time. After the end block number, the shared TFI is invalid for the terminal.
  • the BSS on the network side carries the above information in the downlink assignment message and sends it to the terminal.
  • the BSS when the BSS needs to send the downlink data block or the control block shared by the at least two terminals, the BSS carries the shared TFI in the downlink data block or the block header of the control block, and The downlink data block or control block is broadcast to the at least two terminals through the downlink PDCH.
  • the terminal monitors the downlink PDCH according to the frequency and time slot information of the PDCH carried in the Packet Downlink Assignment message, and parses the data block of the downlink PDCH or the block header of the control block, when the block number of the data block or the control block and the data to which the terminal belongs
  • the terminal considers that the data block or the control block is sent to itself, and the data block or the control block will be parsed. Specific content.
  • the above method does not limit the radio blocks allocated to different terminals to be different. If information shared by two or more terminals needs to be sent, the radio blocks allocated by the network side for these terminals may have overlapping portions, and the shared data/control messages are sent in the overlapping portions, and are sent to the specific portions in the non-overlapping portions. The data/control message of the terminal.
  • the network side can also use the following display method to distinguish between shared and unshared wireless blocks.
  • the embodiment of the present invention only limits the combination of the TFI value and the data block number by taking the period of 52 multiframe as an example. In practical applications, other period values can be completely used.
  • This embodiment realizes that at least two terminals share one or at least two TFIs in a time-sharing manner, thereby saving TFI resources of the GPRS system.
  • the network side of the GPRS system can send the message shared by the at least two terminals and the non-shared information of each terminal by using the downlink data block/control block carrying the shared TFI, and no need to repeatedly send the data block or control separately for each terminal. Block, so that it can be The transmission resource of the downlink channel of the GPRS system.
  • the fifth embodiment is to distinguish the downlink data blocks that are sent to different terminals by using the time-sharing sharing.
  • the USF Uplink State Flag
  • the USF is used to identify different terminals.
  • the USF is used to schedule the identity of the uplink radio block, which is used in the downlink radio block to indicate which terminal the next uplink block is scheduled for.
  • the USF is allocated to the terminal in the uplink assignment message, which has 8 bits and can be used to identify up to 8 terminals.
  • the network side notifies the terminal in the downlink assignment message or the broadcast message, and currently allocates the shared TFI to the terminal.
  • the terminal parses the data block or the control block, and when the USF and the control unit are the same as the USF to which the terminal belongs, and the data block or the control block carries In the above shared TFI, the terminal considers that the data block or the control block is sent to itself, and will parse the specific content in the data block or the control block; otherwise, the terminal does not parse the data block or the control block.
  • the network side can also set the USF to a special value (such as 111) to indicate that the downlink data block or control block is shared by all terminals.
  • a special value such as 111
  • the notification method of the special value is the same as that of the fourth embodiment.
  • the downlink assignment message in the embodiment of the present invention may also be a message that can allocate TFI, such as a reconfiguration message.
  • TFI such as a reconfiguration message.
  • the block header of the above downlink block is an example of MCS-9, and other coding modes may also be similarly falsified.
  • An embodiment of the present invention provides a data transmission apparatus in a wireless communication system, which is disposed on a network side, and has a specific structure as shown in FIG. 5, and includes the following modules:
  • a TFI assignment module 51 configured to allocate a shared temporary block flow indication TFI to at least two terminals, and Transmitting the shared TFI to the at least two terminals;
  • the downlink block transmission module 52 is configured to send, to the at least two terminals, a downlink block that carries the shared TFI, so that the terminal that receives the downlink block parses the content of the downlink block according to the shared TFI.
  • the downlink block may be a downlink data block or a control block, and the control block may carry signaling.
  • the data transmission device may further include:
  • the determining module 53 is configured to determine, according to current downlink resource usage, user subscription information, and/or terminal capability information, whether to allocate a shared TFI to at least two terminals;
  • the TFI assignment module is configured to allocate a shared TFI to at least two terminals when the determining module determines to be yes, and send, to the terminal, the frequency and time slot information of the shared TFI and the downlink channel that are allocated to the at least two terminals.
  • a downlink assignment message or a broadcast message which may include a system message.
  • the at least two terminals may be grouped.
  • the network side needs to save the group identifier to which each terminal belongs, and the terminal side needs to save the group identifier to which the terminal belongs.
  • the downlink identifier corresponding to the shared TFI may be further included in the downlink assignment message or the broadcast message; or, the network side specifies a field or a new field in the block header of the downlink block that is sent to the terminal, and carries the shared TFI corresponding Group ID.
  • the network side can also allocate all the downlink blocks in a certain period to each terminal, and the network side needs to save the block number of the downlink block to which each terminal belongs. Then, in the downlink assignment message or the broadcast message, the block number information of the downlink block to which each terminal belongs may be carried, and the block number of the downlink block to which the terminal belongs needs to be saved on the terminal side.
  • the terminal that receives the downlink block is configured to determine the downlink block according to the block number information of the downlink block and the block number of the downlink block to which the terminal belongs, and the shared TFI is carried in the block header of the downlink block. Is sent to And parsing the content of the downlink block.
  • the embodiment of the present invention provides a terminal, and the specific structure thereof is as shown in FIG. 6, and includes the following modules:
  • the first receiving module 61 is configured to receive a downlink assignment message or a broadcast message sent by the network side, where the downlink assignment message or the broadcast message includes the allocated shared temporary block flow indication TFI.
  • the network side determines whether to allocate the shared TFI to at least two terminals according to the current downlink resource usage and/or the user subscription information and/or the terminal capability information.
  • the terminal receives the network side to send.
  • a downlink assignment message or a broadcast message carrying frequency and slot information of a shared TFI and a downlink channel allocated to at least two terminals, the broadcast message may include a system message.
  • the data processing module 62 is configured to receive a downlink block that is sent by the network side and that carries the shared TFI, and parse the content of the downlink block according to the shared TFI.
  • the data processing module 62 is configured to monitor the downlink channel according to the frequency and time slot information of the downlink channel carried in the downlink assignment message or the broadcast message, and listen to and receive the downlink block that is sent by the network side and that carries the shared TFI. Then, the block header of the downlink block is parsed. When the TFI carried in the block header of the downlink block is the same as the shared TFI allocated to the terminal, the terminal considers that the data block is sent to itself, and the specific content in the downlink block is parsed.
  • the at least two terminals may be grouped, and the terminal identifier to which the terminal belongs needs to be saved on the terminal side. Then, the downlink identifier corresponding to the shared TFI may be carried in the downlink assignment message or the broadcast message; or the designated field or the newly added field in the block header of the downlink block sent by the network side received by the terminal may further carry the identifier
  • the packet identifier corresponding to the shared TFI is described.
  • the data processing module 62 is specifically configured to determine, according to the same, that the packet identifier corresponding to the shared TFI is the same as the group identifier to which the shared TFI belongs, and the TFI carried in the block header of the downlink block is the same as the shared TFI allocated to the terminal.
  • the block is sent to itself and parses the specific content in the downstream block.
  • the network side may also allocate all the downlink blocks in a certain period to each terminal, and then, in the downlink assignment message or the broadcast message, may also carry the block number information of the downlink block to which each terminal belongs, in the terminal. The side needs to save the block number of the downlink block to which the terminal belongs.
  • the data processing module 62 is specifically configured to use the block number information of the downlink block and the block number information of the downlink block to which the downlink block belongs, and the TFI carried in the block header of the downlink block is the same as the shared TFI allocated to the terminal. Determining that the downlink block is sent to itself, and parsing specific content in the downlink block.
  • the network side may allocate all the downlink blocks in a certain period to each terminal, and the terminal receives an uplink assignment message or a broadcast message of the uplink USF (link status flag) to which the bearer belongs, which is sent by the network side.
  • the terminal further includes: a second receiving module 63, configured to receive an uplink assignment message that is sent by the network side and that carries an uplink status flag USF to which the terminal belongs.
  • the data processing module is specifically configured to determine that the downlink block is sent to the terminal according to the USF that is carried in the downlink block and the USF to which it belongs, and the shared TFI carried in the downlink block. And parsing the content of the downlink block.
  • a person skilled in the art can understand that all or part of the process of implementing the above embodiment method can be completed by a computer program to instruct related hardware, and the program can be stored in a computer readable storage medium. In execution, the flow of an embodiment of the methods as described above may be included.
  • the storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM).
  • the embodiment of the present invention increases the number of terminals that can be multiplexed on one downlink packet radio channel by sharing TFI, and saves downlink transmission resources to improve utilization of radio resources.
  • TFI resources of the GPRS system are saved by allocating a shared TFI to at least two terminals.
  • the network side of the GPRS system can send downlink data/control messages shared by at least two terminals through downlink data blocks or control blocks carrying shared TFIs, without The data block is repeatedly transmitted separately for each terminal, thereby saving the transmission resources of the downlink channel of the GP RS system.
  • the shared TFI can be implemented by direct allocation, reservation, or time sharing, and can also be grouped by at least two terminals. Different groups of terminals share the same TFI, which enables more flexible sharing of TFI resources. the way.
  • the message shared by the at least two terminals and the message of the non-shared information of each terminal are transmitted through the downlink data block or the control block carrying the shared TFI, thereby further saving the transmission resource of the downlink channel of the G P RS system.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Description

数据传输的方法和装置 本申请要求于 2010年 12月 03日提交中国专利局、 申请号为 201010579552.4、 发明名称为"数据传输的方法和装置"的中国专利申请的 优先权, 其全部内容通过引用结合在本申请中。
技术领域 本发明涉及移动通信技术领域, 尤其涉及一种无线通信系统中的数据 传输的方法和装置。 背景技术 在 GSM ( Global System for Mobile communications, 全球移动通信 系统) 系统中, 无线接口采用 TDMA ( Time Division Multiple Access, 时 分多址)与 FDMA ( frequency division multiple access, 频分多址)相结 合的方式。 系统所分配的频带被划分为至少两个 200kHz的频点, 用户在不 同频点上通信, 且每一频点在时间上分成 8个长约 0.577毫秒的时隙, 每个 时隙的周期为 8x0.577 « 4.6毫秒。 在 GSM的每个时隙上可以承载一个语音 TCH ( Traffic Channel, 业务信道) , 因此, 一个频点上最多可提供 8路全 速率语音业务。 8个连续的时隙称为一个 TDMA帧, 每个时隙中所传送的信 息称为一个"突发"(burst ) 。
GPRS ( General Packet Radio Service, 通用分组无线业务) 系统是 GSM的演进和延伸, 它采用与 GSM相同的突发结构、 调制方式以及相同的 TDMA帧结构。在 GPRS中,每个时隙上可以承载一个 PDCH ( Packet Data Channel, 数据业务信道) , 但不同于 TCH的是, 一个 PDCH可以由至少两 个终端共享, 而一个终端也可以被分配至少两个 PDCH。 G P RS引入了数据块的概念, 连续 4个 TDM Α帧上时隙号相同的突发称 为一个数据块。数据块是 GPRS进行数据传输的基本单位,数据块的划分方 式如图 1所示, 一个 PDCH在时间上以 52个 TDMA帧为周期重复, 每个周期 称为一个 52复帧, 其内划分出 12个数据块( Block 0到 Block 1 1 )用于发送 数据和高层信令, 此外还有两个帧用于发送时间提前量信息, 两个帧不发 送信息, 而是用于终端邻区测量等。
GPRS中所有的数据传输都是通过建立 TBF ( Temporary Block Flow, 临时块流) 来完成的, TBF由数据块中的 TFI ( Temporary Flow Identity, 临时块流指示)字段进行标识。
现有技术中的一种 G P RS的下行数据传输的方法为:网络侧向终端发送 携带 PDCH所在频点和时隙信息,以及分配给终端的 TFI的 Packet Downlink Assignment下行链路数据块指派)消息。终端接收到上述 Packet Downlink Assignment消息后, 建立和网络侧之间的下行 TBF。
在下行 TBF建立成功后, 终端根据上述 Packet Downlink Assignment 消息中携带的 PDCH所在频点和时隙信息监听下行 PDCH , 解析下行 PDCH 中的数据块的块头, 当数据块的块头中的 TFI与分配给终端的 TFI相同时, 终端认为该数据块是发给自己所用, 将会解析该数据块中的具体内容。 用独占的方式来使用分配给自己的 TFI , 每个终端对应一个 TFL 而 GPRS 系统的 TFI资源是有限的, 当有大量终端接入, 终端的总数大于 GPRS系统 的 TFI资源总数时, 将导致有些终端分配不到 TFI。 发明内容 本发明的实施例提供了一种数据传输的方法和装置,以节约 G P RS系统 的 TFI资源。
一种数据传输方法, 包括: 网络侧给至少两个终端分配共享临时块流指示 TFI, 并将所述共享 TFI 发送给所述至少两个终端;
网络侧向所述至少两个终端发送下行块, 所述下行块块头中携带所述 共享 TFI, 以使接收到所述下行块的终端根据所述共享 TFI解析所述下行块 的内容。
一种数据传输装置, 设置在网络侧, 包括:
临时块流指示 TFI指派模块, 用于给至少两个终端分配共享 TFI, 并将 所述共享 TFI发送给所述至少两个终端;
下行块传输模块, 用于向所述至少两个终端发送下行块, 所述下行块 块头中携带所述共享 TFI, 以使接收到所述下行块的终端根据所述共享 TFI 解析所述下行块的内容。
一种数据处理方法, 包括:
接收网络侧发送下行指派消息或者广播消息, 所述下行指派消息或者 广播消息中包括分配的共享临时块流指示 TFI;
接收网络侧发送的携带所述共享 TFI的下行块, 根据所述共享 TFI解析 所述下行块的内容。
一种终端, 包括:
第一接收模块, 用于接收网络侧发送的下行指派消息或者广播消息, 所述下行指派消息或者广播消息中包括分配的共享临时块流指示 TFI;
数据处理模块, 用于接收网络侧发送的携带所述共享 TFI的下行块, 根 据所述共享 TFI解析所述下行块的内容。
由上述本发明的实施例提供的技术方案可以看出, 本发明实施例通过 给至少两个终端分配一个共享的 TFI , 从而节约无线通信系统的 TFI资源, 可以节约无线通信系统的下行信道的传输资源。 附图说明 为了更清楚地说明本发明实施例的技术方案, 下面将对实施例描述中 所需要使用的附图作筒单地介绍, 显而易见地, 下面描述中的附图仅仅是 本发明的一些实施例, 对于本领域普通技术人员来讲, 在不付出创造性劳 动性的前提下, 还可以根据这些附图获得其他的附图。
图 1为现有技术中的 G PRS系统的一个 52复帧内的数据块的划分方式 示意图;
图 2为本发明实施例一提供的一种网络侧的数据传输方法的处理流程 图;
图 3为本发明实施例二提供的一种终端侧的数据处理方法的处理流程 图;
图 4为本发明实施例三提供的一种无线通信系统中的下行数据传输方 法的处理流程图;
图 5为本发明实施例提供的一种网络侧的数据传输装置的具体结构图; 图 6为本发明实施例提供的一种终端的具体结构图。 具体实施方式 为使本发明实施例的目的、 技术方案和优点更加清楚, 下面将结合本 发明实施例中的附图, 对本发明实施例中的技术方案进行清楚、 完整地描 述, 显然, 所描述的实施例是本发明一部分实施例, 而不是全部的实施例。 基于本发明中的实施例, 本领域普通技术人员在没有作出创造性劳动前提 下所获得的所有其他实施例, 都属于本发明保护的范围。 为便于对本发明实施例的理解, 下面将结合附图以几个具体实施例为 例做进一步的解释说明, 且各个实施例并不构成对本发明实施例的限定。
实施例一
该实施例提供的一种网络侧的数据传输方法的处理流程如图 2所示, 包 括如下的处理步骤:
步骤 21、 网络侧给至少两个终端分配共享 TFI, 并将所述共享 TFI发送 给所述至少两个终端。
网络侧根据当前下行资源使用情况、 用户签约信息、 终端能力信息中 的至少一项, 判断是否给至少两个终端分配共享 TFI, 当判断是给至少两个 终端分配共享 TFI时, 网络侧向终端发送携带分配给至少两个终端的共享 TFI和下行信道所在频点和时隙信息的下行指派消息或者广播消息, 该广播 消息可以包括系统消息。
在实际应用中, 可以对上述至少两个终端进行分组, 在网络侧需要保 存各个终端所属的分组标识, 在终端侧需要保存该终端所属的分组标识。 然后, 在所述下行指派消息或者广播消息中还可以包括所述共享 TFI对应的 分组标识; 或者, 网络侧在向终端发送的下行块的块头中指定字段或者新 增字段携带所述共享 TFI对应的分组标识。
在实际应用中, 网络侧还可以将一定周期内所有下行块分别划分给各 个终端, 在网络侧需要保存各个终端所属的下行块的块号。 然后, 在所述 下行指派消息或者广播消息中还可以携带各个终端所属的下行块的块号信 息, 在终端侧需要保存该终端所属的下行块的块号。 步骤 22、网络侧向所述至少两个终端发送携带所述共享 TFI的下行块, 以使接收到所述下行块的终端根据所述共享 TFI来解析所述下行块的内容。 上述下行块可以为下行的数据块或者控制块, 该控制块可以携带信令。
终端根据上述下行指派消息或者广播消息中携带的下行信道所在频点 和时隙信息监听下行信道, 当监听并接收到上述网络侧发送的携带所述共 享 TFI的下行块后, 解析下行块的块头, 当下行块的块头中携带的 TFI与分 配给终端的上述共享 TFI相同时, 终端认为该数据块是发给自己的, 将会解 析该下行块中的具体内容。
当对上述至少两个终端进行分组, 并且在所述下行指派消息或者广播 消息中还可以包括所述共享 TFI对应的分组标识; 或者, 在上述下行块的块 头中指定字段或者新增字段携带所述共享 TFI对应的分组标识后。 终端根据 所述共享 TFI对应的分组标识和其所属的分组标识相同, 以及所述下行块的 块头中携带的 TFI与分配给终端的上述共享 TFI相同来确定所述下行块是发 送给自己的, 并解析所述下行块中的具体内容。
当网络侧将一定周期内所有下行块分别划分给各个终端, 并且在所述 下行指派消息或者广播消息中还包括各个终端所属的下行块的块号信息 后, 终端根据所述下行块的块号信息和其所属的下行块的块号信息相同, 以及所述下行块的块头中携带的 TFI与分配给终端的上述共享 TFI相同来确 定所述下行块是发送给自己的, 并解析所述下行块中的具体内容。
该实施例实现了给至少两个终端分配共享的 TFI, 可以使网络侧可以同 时向至少两个终端发送共享的下行块, 无需再针对每个终端单独重复发送 下行数据块或者控制块, 从而可以节约 GPRS系统的 TFI资源和下行信道的 传输资源。
实施例二 该实施例提供的一种终端侧的数据处理方法的处理流程如图 3所示, 包 括如下的处理步骤:
步骤 31、 终端接收网络侧发送的下行指派消息或者广播消息, 所述下 行指派消息或者广播消息中包括分配的共享 TFI。 上述广播消息可以包括系 统消息。
在实际应用中, 可以对上述至少两个终端进行分组, 在终端侧需要保 存该终端所属的分组标识。 然后, 在所述下行指派消息或者广播消息中还 可以携带所述共享 TFI对应的分组标识; 或者, 在终端接收到的网络侧发送 的下行块的块头中指定字段或者新增字段还可以携带所述共享 TFI对应的 分组标识。
在实际应用中, 网络侧还可以将一定周期内所有下行块分别划分给各 个终端, 然后, 在所述下行指派消息或者广播消息中还可以携带各个终端 所属的下行块的标识信息, 在终端侧需要保存该终端所属的下行块的标识。 上述下行块的标识信息可以为下行块的块号信息。
步骤 32、 终端接收网络侧发送的携带所述共享 TFI的下行块, 根据所 述共享 TFI解析所述下行块的内容。 上述下行块可以为下行的数据块或者 控制块, 该控制块可以携带信令。
终端根据上述下行指派消息或者广播消息中携带的下行信道所在频点 和时隙信息监听下行信道, 当监听并接收到上述网络侧发送的携带所述共 享 TFI的下行块后, 解析下行块的块头, 当下行块的块头中携带的 TFI与分 配给终端的上述共享 TFI相同时, 终端认为该数据块是发给自己的, 将会解 析该下行块中的具体内容。
当对上述至少两个终端进行分组, 并且在所述下行指派消息或者广播 消息中还可以包括所述共享 TFI对应的分组标识; 或者, 在上述下行块的块 头中指定字段或者新增字段携带所述共享 TFI对应的分组标识后。 终端根据 所述共享 TFI对应的分组标识和其所属的分组标识相同, 以及所述下行块的 块头中携带的 TFI与分配给终端的上述共享 TFI相同来确定所述下行块是发 送给自己的, 并解析所述下行块中的具体内容。
当网络侧将一定周期内所有下行块分别划分给各个终端, 并且在所述 下行指派消息或者广播消息中还包括各个终端所属的下行块的块号信息 后, 终端根据所述下行块的块号信息和其所属的下行块的块号信息相同, 以及所述下行块的块头中携带的 TFI与分配给终端的上述共享 TFI相同来确 定所述下行块是发送给自己的, 并解析所述下行块中的具体内容。
在实际应用中, 网络侧可以将一定周期内所有下行块分别划分给各个 终端, 终端接收网络侧发送的携带分配给终端的上行 USF (链路状态标记) 的上行指派消息。 然后, 终端接收网络侧发送的携带所述共享 TFI和 USF的 下行块, 根据所述下行块中携带的 USF和其所属的 USF相同, 以及所述下 行块中携带的所述共享 TFI来确定所述下行块是发送给自己的, 并解析所述 下行块的内容。
该实施例实现了终端根据网络侧分配的共享的 TFI来解析网络侧同时 向至少两个终端发送的共享的下行块, 网络侧无需再针对每个终端单独重 复发送下行数据块或者控制块, 从而可以节约 GPRS系统的 TFI资源和下行 信道的传输资源。 实施例三
该实施例提供的一种无线通信系统中的下行数据传输的方法的处理流 程如图 4所示, 包括如下的处理步骤:
步骤 41、 网络侧判断是否给至少两个终端分配共享的 TFI。
网络侧的 BSS ( Base Station Subsystem,基站子系统 )可以根据当前下 行资源使用情况、 用户签约信息和终端能力等信息, 判断是否给至少两个 终端分配共享的 TFI。
例如, 当 BSS的下行资源紧张, 接入的终端个数 4艮多时, 则 BSS判断需 要给至少两个终端分配共享 TFI;
当至少两个终端的用户签约信息和 /或终端能力信息具有相同属性时, 比如, 同属于相同抄表业务的 M2M终端, 则 BSS判断需要给至少两个终端 分配共享 TFI。
当 BSS判断需要给至少两个终端分配共享 TFI, 执行步骤 42。
步骤 42、 网络侧在向终端发送的下行指派消息中携带给至少两个终端 分配的共享 TFI和相应的指示信息。
本发明实施例 BSS发送给终端的下行指派消息中添加新的指示信息,通 过该新的指示信息来指明是否给终端分配共享的 TFI。
下面以上述下行指派消息为 Packet Downlink ASSIGNMENT消息为例 来说明本发明实施例。 在 Packet Downlink ASSIGNMENT消息中添加新的指示信息, 添加了新 的指示的 Packet Downlink ASSIGNMENT消息中的信息单元的格式如下:
Packet Downlink ASSIGNMENT information elements
Packet Downlink Assignment message content >:: =
< PAGE— MODE: bit (2) >
{ o 1 1 PERSISTENCE— LEVEL: bit (4) > * 4 }
{ { 0 < Global TFI: < Global TFI IE > >
{null I 0** = <no string>
11
{ indication of shared TFI: bit>} padding bits > } }
-- truncation at end of message allowed, bits Ό' assumed
上述 Packet Downlink ASSIGNMENT消息中的 indication of shared TFI字
当 BSS需要给至少两个终端分配共享 TFI时, 可以选择将上述 Packet Downlink ASSIGNMENT消息中的 indication of shared TFI字段的值置为 1 ,并 发送给终端。 然后, BSS可以通过 Packet Downlink Assignment消息等消息 为上述至少两个终端分配相同的 PDCH所在频点和时隙信息。
上述至少两个终端接收到上述 Packet Downlink Assignment消息后,如 果该消息中携带了上述新的指示信息且 indication of shared TFI字段的值为 1 ,则确认上述 Packet Downlink Assignment消息中携带的 TFI为 BSS给至少 两个终端分配的共享 TFI。
步骤 43、在下行信道指派完成后, 当 BSS需要发送上述至少两个终端共 享的下行的数据块或者控制块(携带信令)时, BSS在该下行的数据块或者 控制块的块头中携带上述共享 TFI, 将该下行的数据块或者控制块一次发送 给上述至少两个终端。
终端根据接收到的数据块或者控制块中携带的上述 TFI判断是否为网 络侧指派给自己的 TFI, 如是则解析该数据块或者控制块中的具体内容。 当采用 MCS-9编码方式时, 上述携带了共享 TFI的数据块的块头的格式 如下:
Bit
8 7 6 5 4 3 2 1 Octet
TFI (共享) RRBP ES/P USF 1
BSN1 PR TFI (共享) 2
BSN1 3
BSN2 BSN 1 4
CPS BSN2 5 终端根据上述 Packet Downlink Assignment消息中携带的 PDCH所在 频点和时隙信息监听下行 PDCH,解析下行 PDCH中的数据块或者控制块的 块头, 当数据块或者控制块的块头中携带的 TFI与分配给终端的上述 TFI相 同时, 终端认为该数据块是发给自己的, 将会解析该数据块或者控制块中 的具体内容。
在实际应用中, 还可以给上述共享同一个 TFI的至少两个终端再进行分 组, 每一组终端用 Group ID来识别, Group ID的定义可以根据终端能力、 签 约属性等来制定。 比如, 有两组 M2M终端, 他们的抄表业务分别用来统计 企业用电和家庭用电, 因此电力公司要求他们上报的数据、 时间各不相同。 但是对于同属企业用电或者家庭用电的终端, 这些要求是相同的, 因此相 应的下行数据或控制消息是共享的,这种情况可以用 Group ID来识别上述两 组 M2M终端。
在对所述至少两个终端进行分组后, 可以通过所述数据块的编码格式 中的指定字段或者新增字段来携带指定的分组标识信息。 当采用 MCS-9编 段来携带。 通过 RRBP和 ES/P字段来携带 Group ID的数据块的块头的格式如 下: Octet
TFI (共享) Group I D GA USF 1
BSN1 PR TFI (共享) 2
BSN1 3
BSN2 BSN1 4
CPS BSN2 5 其中, GA指示组信息是否有效:
bit
0 Group ID is not valid
1 Group ID is valid
而 Group ID用来指示当前的下行数据块或者控制块是发给哪个组的终
通过 RRBP和 ES/P字段 Group ID可以用 3bit表示出最多 8个分组。
这样, 可以使属于至少两个组的终端共享相同的 TFI, 进一步节省下行 调度资源。 当 GA显示组标识无效时, 则下发的下行数据块或者控制块是给 所有共享该 TFI的终端共享, 否则则是属于该组的终端共享。 当然, 上述组 标识因为 3bit的限制, 最多只有 8个组, 本发明也可以扩展其他字段来扩大 组标识的取值范围。
当采用 MCS-9编码方式时, 上述 GA信息可以通过数据块的块头的格式 中的 PR字段来指示。 目前, PR字段的取值如下:
Power Reduction (PR) field
Power Reduction (PR) field
Figure imgf000013_0001
其中的 11字段未使用, 因此可以使用 11字段来表明此时 Group ID有效: Octet
TFI (共享) Group I D USF 1
BSN1 TFI (共享) 2
BSN1 3
BSN2 BSN1 4
CPS BSN2 5
通过 PR字段 Group ID可以扩展到用 4个比特表示出最多 16个分组。
DC
还可以在上述数据块的块头中新增一个字段, 专门用来指示 Group ID 信息, 通过新增的字段来携带 Group ID的数据块的块头的格式如下:
Bit
8 7 6 5 4 3 ί 1 Octet
TFI RRBP ES/P USF 1
BSN1 PR TFI 2
BSN1 3
BSN2 BSN1 4
CPS BSN2 5
Group I D GA 6
然后,当 BSS需要发送上述至少两个终端共享的下行的数据块或者控制 块时, BSS在该下行的数据块或者控制块中携带上述共享的 TFI和指定的 Group ID,将该下行的数据块或者控制块通过下行 PDCH分发给上述至少两 个终端。
终端根据上述 Packet Downlink Assignment消息中携带的 PDCH所在 频点和时隙信息监听下行 PDCH,解析下行 PDCH中的数据块或者控制块的 块头, 当该数据块或者控制块的块头中携带的 Group ID和终端所属的 Group ID相同时, 并且数据块或者控制块中携带上述共享的 TFI , 则终端认为该数 据块或者控制块是发给自己的, 将会解析该数据块或者控制块中的具体内 分配给终端的共享 TFI可以有至少两个。 例如当终端属于至少两个组 时, 就可以为终端分配至少两个共享的 TFI , 携带了给终端分配的至少两个 共享的 TFI Packet Downlink Assignment消息中的信息单元的格式如下:
< Packet Downlink Assignment message content >:: =
{null I 0** = <no string>
11
{ 0 I 1 <shared TFIs <Group TFI struct>:
< spare padding >;
: Group TFI struct >》 :: =
{ 1 < Repeated TFI for groups: Repeated TFI for groups struct:
: Repeated TFI for groups struct>:: =
{ 1 < shared TFI <Global TFI IE> >
{ 1 <Group lD: bit (4) > } **0 } ** 0
上述方法有效避免网络侧多次发送相同的数据给不同终端造成的传输 资源浪费, 但是这种做法也限制了终端不能同时接收共享数据和独占数据。 因此, 网络侧可以进一步为终端同时分配共享 TFI和独占 TFI。 携带了给终 端分配的共享 TFI和独占 TFI的 TFI Packet Downlink Assignment消息中的信 息单元的格式如下:
< Packet Downlink Assignment message content >:: =
< PAGE— MODE: bit (2) >
{ o 1 1 PERSISTENCE— LEVEL: bit (4) > * 4 }
ί ί 0 < Global TFI: < Global TFI IE > >
{null I 0** = <no string>
11
{ indication of shared TFI: bit>}
{ 0
I 1 < non-shared Global TFI: < Global TFI IE > > }
< padding bits > } }// ― truncation at end of message allowed, bits Ό' assumed
其中, 上述消息中的 indication of shared TFI字段的值为 0表示给终端分 配的 <Global TFI>为独占的 TFI,上述消息中的 indication of shared TFI字段的 值为 1表示给终端分配的 <Global丁?1>为共享的 TFI。 当 indication of shared TFI字段为 1时, 网络侧还可以选择用 non-shared global TFI字段再为终端分 配一个独占的 TFI。 当某些业务要求某些下行信息为共享信息某些下行信息 为独占信息时, 网络侧可以在下行指派消息中同时为终端分配共享 TFI和独 占 TFI。 这样, 当有共享信息需要下发时, 则通过在下行数据块或者控制块 中携带共享 TFI标识; 当有独占信息需要下发时, 则通过在下行数据块或者 控制块中携带独占 TFI标识。 由于这两个 TFI都分配给了终端, 因此终端无 论收到携带有哪个 TFI的下行数据块或者控制块, 都能判断出该下行数据块 或者控制块是否属于自己, 从而解析该下行数据块或者控制块内容。
上述方法中网络侧下发共享数据后, 终端无法响应。 然而对于有些需 要应答的数据 /信令, 网络侧还是希望终端能够响应。 因此, 网络侧在进行 下行指派时可以进一步为共享所述 TFI的终端分配一个临时编号如下所示:
< Packet Downlink Assignment message content >:: =
< PAGE— MODE: bit (2) >
{ o 1 1 PERSISTENCE— LEVEL: bit (4) > * 4 }
{ { 0 < Global TFI: < Global TFI IE > >
{null I 0** = <no string>
11
{ indication of shared TFI: bit>
<Temporary MS ID : 4 bits> }
{ 0
I 1 < non-shared Global TFI: < Global TFI IE > > }
< padding bits > } }// - truncation at end of message allowed, bits Ό' assumed 当发送下行信息时, RRBP字段指定了终端回应答的对应预留块。 网络 侧下发共享信息时, 当接收终端的临时编号为 1时, 则在 RRBP指定的预留 块回应答; 当接收终端的临时编号为 2时, 则在 RRBP指定预留块的后一个 块上应答。 例如: 两个终端共享一下下行 TFI, 网络侧在下行指派消息中指 定其中一个终端的临时编号为 0001 , 另一个为 0010。 则当下发的共享下行 块中 RRBP字段有效时, 编号为 0001的终端在对应预留的块上回应答, 编号 为 0002的终端就会在预留的块的后一个块上回应答。 这种应答方式也同样 适用于本发明中的实施例四、 实施例五和实施例六。
该实施例实现了给至少两个终端分配共享的 TFI, 使网络侧可以同时调 度至少两个终端接收共享的下行数据块或者控制块,从而节约 GPRS系统的 TFI资源。 同时, GPRS系统的网络侧还可以将至少两个终端共享的下行数 据 /控制消息,通过携带共享 TFI的下行数据块或者控制块同时发送给至少两 个终端, 无需再针对每个终端单独重复发送下行数据块或者控制块, 从而 可以节约 GPRS系统的下行信道的传输资源。
通过对至少两个终端进行分组, 可以实现更加灵活的 TFI资源的共享方 式。 实施例四
网络侧的 BSS还可以预先预留一个 TFI值(如 31 ) , 专门用于 TFI共享。 上述预留的 TFI值可以是预先配置好的, 也可以是动态改变的。
上述预留的 TFI值可以通过广播消息下发给终端, 该广播消息可以为: 系统消息(如 SI2quater消息)、 paging消息等。 比如, 在 SI2quater消息的 Rest Octets中通过新增加的指示来携带上述预留的 TFI值。
该实施例提供的一种携带了上述预留的 TFI值的 SI2quater消息的格式如 下:
< SI2quater Rest Octets >:: =
< BAJND: bit (1 ) >
< 3G_BA_IND : bit (1 ) >
< MP— CHANGE— MARK: bit (1 ) >
< SI2quater_INDEX: bit (4) >
< SI2quater— COUNT: bit (4) >
Measurement— Parameters Description: < Measurement Parameters Description struct » }
GPRS— Real Time Difference Description: < GPRS— Real Time Difference Description struct »
GPRS)SIC Description: GPRS— BSIC Description struct > }
GPRS— REPORT PRIORITY Description: < GPRS— REPORT— PRIORITY Description struct » }
GPRS— MEASUREMENT— Parameters Description:
< GPRS_MEASUREMENT Parameters Description struct » }
NC Measurement Parameters: < NC Measurement Parameters struct » }
extension length: bit (8) >
< < bit (val(extension length)+1 ) > &
{ < SI2q Extension Information >! { Ignore: bit ** = <no string > } } > }
1
1
1
null I L Receiver compatible with earlier release
I H - Additions in Rel-5:
0 I 1 < 3G Additional Measurement Parameters Description:
< 3G Additional Measurement Parameters Description struct » }
0 I 1 < 3G ADDITIONAL MEASUREMENT Parameters Description 2:
< 3G ADDITIONAL MEASUREMENT Parameters Description 2 struct » }
( null L - Receiver compatible with earlier release
I H -- Additions in Rei-6:
3G—CCN— ACTIVE : bit (1 ) >
null I L -- Receiver compatible with earlier release
I H - Additions in Rel-7:
{ 0 | 1 < 700— REPORTING— OFFSET: bit (3) >
< 700— REPORTING— THRESHOLD: bit (3) > }
{ 0 | 1 < 810_REPORTING_OFFSET: bit (3) >
< 810— REPORTING— THRESHOLD: bit (3) > }
{ null I L -- Receiver compatible with earlier release
I H - Additions in Rel-8
{ 0 I 1 < Priority and E-UTRAN Parameters Description:
< Priority and E-UTRAN Parameters Description struct » }
{ 0 I 1 < 3G CSG Description: < 3G CSG Description struct » }
{ 0 I 1 < E-UTRAN CSG Description: < E-UTRAN CSG Description struct » } { null I L -- Receiver compatible with earlier release
I H - Additions in Rel-9
{ 0 I 1 < Enhanced Cell Reselection Parameters Description:
< Enhanced Cell Reselection Parameters Description struct: { 0 I 1 < CSG Cells Reporting Description:
< CSG Cells Reporting Description struct » }
Null I L
I H
ί 0 I 1 <shared TFI <Global TFI IE> > }
; spare padding:
当然, 如果接入网获知终端的分组信息, 也可以为属于不同组的终端 分配相同的 TFI, 上述 SI2quater消息也可以进一步修改为: < SI2quater Rest Octets >:: =
< BAJND: bit (1 ) >
< 3G_BA_IND : bit (1 ) >
< MP— CHANGE— MARK: bit (1 ) >
< SI2quater_INDEX: bit (4) >
< SI2quater— COUNT: bit (4) >
0 I 1 < Measurement— Parameters Description: < Measurement Parameters Description struct » }
0 I 1 < GPRS— Real Time Difference Description: < GPRS— Real Time Difference Description struct »
0 I 1 < GPRS)SIC Description: GPRS— BSIC Description struct > }
0 I 1 < GPRS— REPORT PRIORITY Description: < GPRS— REPORT— PRIORITY Description struct » }
0 I 1 < GPRS— MEASUREMENT— Parameters Description:
< GPRS_MEASUREMENT Parameters Description struct » }
0 I 1 < NC Measurement Parameters: < NC Measurement Parameters struct » }
0 I 1 < extension length: bit (8) >
< < bit (val(extension length)+1 ) > &
{ < SI2q Extension Information >! { Ignore: bit ** = <no string > } } > }
[ 0 I 1 < 3G Neighbour Cell Description: < 3G Neighbour Cell Description struct » }
[ 0 I 1 < 3G Measurement Parameters Description: < 3G Measurement Parameters Description struct »
[ 0 I 1 < GPRS— 3G— MEASUREMENT Parameters Description:
< GPRS_3G MEASUREMENT Parameters Description struct » }
null I L - Receiver compatible with earlier release
I H - Additions in Rel-5:
{ 0 I 1 < 3G Additional Measurement Parameters Description:
< 3G Additional Measurement Parameters Description struct » }
{ 0 | 1 < 3G ADDITIONAL MEASUREMENT Parameters Description 2:
< 3G ADDITIONAL MEASUREMENT Parameters Description 2 struct »
{ null I L - Receiver compatible with earlier release
I H - Additions in Rei-6:
< 3G—CCN— ACTIVE: bit (1 ) >
{ null I L -- Receiver compatible with earlier release
I H - Additions in Rei-7:
0 I 1 < 700— REPORTING— OFFSET: bit (3) >
< 700— REPORTING— THRESHOLD: bit (3) > }
0 I 1 < 810_REPORTING_OFFSET: bit (3) >
< 810— REPORTING— THRESHOLD: bit (3) > }
null I L -- Receiver compatible with earlier release
I H - Additions in Rei-8
{ 0 I 1 < Priority and E-UTRAN Parameters Description:
< Priority and E-UTRAN Parameters Description struct » }
{ 0 I 1 < 3G CSG Description: < 3G CSG Description struct » }
{ 0 I 1 < E-UTRAN CSG Description: < E-UTRAN CSG Description struct » } { null I L -- Receiver compatible with earlier release
I H - Additions in Rel-9
{ 0 I 1 < Enhanced Cell Reselection Parameters Description:
< Enhanced Cell Reselection Parameters Description struct: { 0 I 1 < CSG Cells Reporting Description:
< CSG Cells Reporting Description struct » }
Null I L
I H
{ 0 I 1 <shared TFIs <Group TFI struct> > }
< spare padding >;
: Group TFI struct >》 :: =
{ 1 < Repeated TFI for groups: Repeated TFI for groups struct:
: Repeated TFI for groups struct>:: =
{ 1 < shared TFI <Global TFI IE> >
{ 1 <Group lD: bit (4) > } **0 } ** 0
BSS进行正常的下行指派流程,在 Packet Downlink Assignment消息中 不显示指示当前分配的 TFI是否为共享, 而是通过将 TFI设置为上述预留的 TFI (即广播消息中下发的值)来表示该 TFI为共享 TFI。 例如, 当上述预留 的 TFI值为 31时, BSS在下行指派消息中将 TFI为 31的值分配给终端, 终端 即可知道该 TFI为共享 TFI。 然后,当 BSS需要发送上述至少两个终端共享的下行的数据块或者控制 块时, BSS在该下行的数据块或者控制块的块头中携带上述预留的 TFI, 将 该下行的数据块或者控制块通过下行 PDCH广播给上述至少两个终端。
终端根据上述 Packet Downlink Assignment消息中携带的 PDCH所在 频点和时隙信息监听下行 PDCH,解析下行 PDCH中的数据块或者控制块的 块头, 当数据块或者控制块的块头中携带的 TFI与上述预留的 TFI相同时, 终端认为该数据块或者控制块是发给自己的, 将会解析该数据块或者控制 块中的具体内容。
该实施例实现了至少两个终端分配共享预留的 TFI, 使网络侧可以同时 调度至少两个终端接收共享的下行信息, 从而节约 GPRS系统的 TFI资源。 同时, GPRS系统的网络侧还可以将至少两个终端共享的下行数据 /控制消 息, 通过携带共享 TFI的下行数据块或者控制块同时发送给至少两个终端, 无需再针对每个终端单独重复发送下行数据块或者控制块, 从而可以节约 GPRS系统的下行信道的传输资源。 实施例五
上述实施例三和四无法解决当大量终端共享同一个 PDCH时,非共享信 息的发送仍然要占用大量 TFI资源的问题。 该实施例提出一种分时共享 TFI 的方法。 即所有终端共享相同的 TFI值, 但该相同的 TFI值的归属在 52复帧 内以数据块为单位进行切分,即某个 TFI值在 52复帧内的 12个数据块中可以 分属于不同的终端, 最多可以有 12个终端。 这样, TFI值和数据块号之间的 组合在一个 52复帧内最多能达到 12x32=384个, 即一个 PDCH上最多能复 用 384个终端。
网络侧的 BSS需要向每个终端发送该终端在 BO ~ B1 1数据块中所属的 数据块的信息, 上述所属的数据块的信息的表达方式可以有多种。 比如, 用相同的比特位来对一个数据帧的周期内的每个数据块和所述 至少两个终端中的每个终端进行编号, 将具有相同编号的数据块和终端进 行对应。
举例说明如下:
1 )用 12bit位图表示:
如下表所示, 网络侧在下行指派消息中指定终端需要监听的无线块号, 因为一个 52复帧有 12个块, bit置为 1所对应的块就是终端归属的数据块。
Figure imgf000021_0001
2 )用块号表示:
可以在下行指派消息中用 4bit来对数据块和终端进行编号,将具有相同 编号的数据块和终端进行对应。
<Assigned Blocks struct>:: =
{ 1 | <Block Nub: bit 4 > } ** 0 又比如, 用设定的数字对一个数据帧的周期内的每个数据块进行取模,
例如, 将数据块号对 2取模, 取值为 0的分配给终端 1 , 取值为 1的分配 给终端 2。 模数不做限制, 可以是 2, 3, 4等等。 同时, 这个方法也能应用 于帧号。
在该实施例和上述实施例三和四中, 网络侧的 BSS还可以在 Packet Downlink Assignment消息中, 直接指示共享的 TFI对终端的有效期。 例如 在消息中增加起始块号和结束块号, 表明该 TFI在这一段时间内对终端有 效, 过了结束块号后, 该共享的 TFI对终端无效。
网络侧的 BSS将上述信息携带在下行指派消息中发送给终端。
然后,当 BSS需要发送上述至少两个终端共享的下行的数据块或者控制 块时, BSS在该下行的数据块或者控制块的块头中携带上述共享的 TFI, 将 该下行的数据块或者控制块通过下行 PDCH广播给上述至少两个终端。 终端根据上述 Packet Downlink Assignment消息中携带的 PDCH所在 频点和时隙信息监听下行 PDCH,解析下行 PDCH中的数据块或者控制块的 块头, 当该数据块或者控制块的块号和终端所属的数据块或者控制块的块 号相同时, 并且数据块或者控制块的块头中携带上述共享的 TFI, 则终端认 为该数据块或者控制块是发给自己的, 将会解析该数据块或者控制块中的 具体内容。
值得指出的是上述方法, 并不限制分配给不同终端的无线块必须各不 相同。 如果有两个及以上终端共享的信息需要发送, 网络侧为这些终端分 配的无线块可以有重叠的部分, 并在这些重叠的部分发送共享的数据 /控制 消息, 在非重叠的部分发送给特定终端的数据 /控制消息。
当然, 网络侧也可以采用如下的显示方法来区分共享和非共享的无线 块,
<Assigned Blocks struct>:: =
{ 0 I 1 < shared blocks struct > }
{ 0 I 1 < non-shared blocks struct > }
< shared blocks struct >: : =
{ 1 I <Block Nub: bit 4 > } ** 0
< non-shared blocks struct >: : =
{ 1 I <Block Nub: bit 4 > } ** 0 在实际应用中, 本发明实施例并不限制某个终端只能分配一个 TFI, 终 端可以分配 384个(TFI值, 数据块号)组合中任意一个或者至少两个, 如 终端 1可以同时分配(TFI=1 , B0 )和(TFI=2, B2 ) 。 另外, 本发明实施 例仅以 52复帧的周期为例限制 TFI值和数据块号的组合方式, 在实际应用 中, 完全可以使用其他的周期值。
该实施例实现了至少两个终端分时共享一个或至少两个 TFI , 从而节约 GPRS系统的 TFI资源。 GPRS系统的网络侧可以将至少两个终端共享的消 息和各个终端的非共享信息的消息,通过携带共享 TFI的下行数据块 /控制块 发送, 无需再针对每个终端单独重复发送数据块或者控制块, 从而可以节 约 GPRS系统的下行信道的传输资源。
实施例六
实施例五是通过分时共享来区分发送给不同终端的下行数据块, 而本 实施例通过 USF ( Uplink State Flag, 上行链路状态标记)来识别不同终端。 USF是用来调度上行无线块的标识,它在下行无线块中用来表示下一个上行 块调度给了哪个终端。 USF在上行指派消息中分配给终端, 共有 8比特, 可 以用来标识最多 8个终端。
8 7 6 5 4 3 2 1 Octet
TFI RRBP ES/P USF 1
BSN1 PR TFI (共享) 2
BSN1 3
BSN2 BSN1 4
CPS BSN2 5
如实施例三或四所述, 网络侧在下行指派消息或广播消息中通知终端, 当前为终端分配了共享的 TFI。 终端收到网络侧发送的数据块或者控制块 后,解析该数据块或者控制块, 当该数据块或者控制块中携带的 USF和终端 所属的 USF相同时, 并且该数据块或者控制块中携带上述共享的 TFI , 则终 端认为该数据块或者控制块是发给自己的, 将会解析该数据块或者控制块 中的具体内容; 否则终端不解析该数据块或者控制块。
当然, 网络侧也可以将 USF设置成一个特殊值(如 111 ) 来表示该下行 数据块或者控制块对所有终端共享。 特殊值的通知方式与实施例四相同。
本发明实施例中的下行指派消息也可以是重配置消息等其他可分配 TFI的消息。 上述下行块的块头是以 MCS-9为例, 其他编码方式也可以 类 似相应爹改。
本发明实施例提供了一种无线通信系统中的数据传输装置, 设置在网 络侧, 其具体结构如图 5所示, 包括如下的模块:
TFI指派模块 51 , 用于给至少两个终端分配共享临时块流指示 TFI, 并 将所述共享 TFI发送给所述至少两个终端;
下行块传输模块 52, 用于向所述至少两个终端发送携带所述共享 TFI 的下行块, 以使接收到所述下行块的终端根据所述共享 TFI来解析所述下行 块的内容。 上述下行块可以为下行的数据块或者控制块, 该控制块可以携带信令。 所述数据传输装置还可以包括:
判断模块 53, 用于根据当前下行资源使用情况、 用户签约信息和 /或终 端能力信息, 判断是否给至少两个终端分配共享 TFI;
所述 TFI指派模块用于当所述判断模块判断为是时, 给至少两个终端分 配共享 TFI, 并向终端发送携带分配给至少两个终端的共享 TFI和下行信道 所在频点和时隙信息的下行指派消息或者广播消息, 该广播消息可以包括 系统消息。
在实际应用中, 可以对上述至少两个终端进行分组, 在网络侧需要保 存各个终端所属的分组标识, 在终端侧需要保存该终端所属的分组标识。 然后, 在所述下行指派消息或者广播消息中还可以包括所述共享 TFI对应的 分组标识; 或者, 网络侧在向终端发送的下行块的块头中指定字段或者新 增字段携带所述共享 TFI对应的分组标识。 以使接收到所述下行块的终端根 据所述下行块中携带的指定的分组标识和其所属的分组标识相同, 以及所 述下行块中携带的所述共享 TFI来确定所述下行块是发送给自己的, 并解析 所述下行块的内容。
在实际应用中, 网络侧还可以将一定周期内所有下行块分别划分给各 个终端, 在网络侧需要保存各个终端所属的下行块的块号。 然后, 在所述 下行指派消息或者广播消息中还可以携带各个终端所属的下行块的块号信 息, 在终端侧需要保存该终端所属的下行块的块号。 以使接收到所述下行 块的终端根据所述下行块的块号信息和终端所属的下行块的块号相同时, 并且下行块的块头中携带了所述共享的 TFI来确定所述下行块是发送给自 己的, 并解析所述下行块的内容。
本发明实施例提供了一种终端, 其具体结构如图 6所示, 包括如下的模 块:
第一接收模块 61 , 用于接收网络侧发送的下行指派消息或者广播消息, 所述下行指派消息或者广播消息中包括分配的共享临时块流指示 TFI。
网络侧根据当前下行资源使用情况和 /或用户签约信息和 /或终端能力 信息, 判断是否给至少两个终端分配共享 TFI, 当判断是给至少两个终端分 配共享 TFI时, 终端接收网络侧发送的携带分配给至少两个终端的共享 TFI 和下行信道所在频点和时隙信息的下行指派消息或者广播消息, 该广播消 息可以包括系统消息。
数据处理模块 62, 用于接收网络侧发送的携带所述共享 TFI的下行块, 根据所述共享 TFI解析所述下行块的内容。
上述数据处理模块 62具体用于根据上述下行指派消息或者广播消息中 携带的下行信道所在频点和时隙信息监听下行信道, 当监听并接收到上述 网络侧发送的携带所述共享 TFI的下行块后, 解析下行块的块头, 当下行块 的块头中携带的 TFI与分配给终端的上述共享 TFI相同时, 终端认为该数据 块是发给自己的, 将会解析该下行块中的具体内容。
在实际应用中, 可以对上述至少两个终端进行分组, 在终端侧需要保 存该终端所属的分组标识。 然后, 在所述下行指派消息或者广播消息中还 可以携带所述共享 TFI对应的分组标识; 或者, 在终端接收到的网络侧发送 的下行块的块头中指定字段或者新增字段还可以携带所述共享 TFI对应的 分组标识。
上述数据处理模块 62具体用于根据所述共享 TFI对应的分组标识和其 所属的分组标识相同, 以及所述下行块的块头中携带的 TFI与分配给终端的 上述共享 TFI相同来确定所述下行块是发送给自己的, 并解析所述下行块中 的具体内容。 在实际应用中, 网络侧还可以将一定周期内所有下行块分别划分给各 个终端, 然后, 在所述下行指派消息或者广播消息中还可以携带各个终端 所属的下行块的块号信息, 在终端侧需要保存该终端所属的下行块的块号。
上述数据处理模块 62具体用于根据所述下行块的块号信息和其所属的 下行块的块号信息相同, 以及所述下行块的块头中携带的 TFI与分配给终端 的上述共享 TFI相同来确定所述下行块是发送给自己的, 并解析所述下行块 中的具体内容。
在实际应用中, 网络侧可以将一定周期内所有下行块分别划分给各个 终端, 终端接收网络侧发送的携带终端所属的上行 USF (链路状态标记)的 上行指派消息或者广播消息。
所述的终端还包括: 第二接收模块 63, 用于接收网络侧发送的携带所 述终端所属的上行链路状态标记 USF的上行指派消息。
所述数据处理模块具体用于根据所述下行块中携带的 USF和其所属的 USF相同, 以及所述下行块中携带的所述共享 TFI来确定所述下行块是发送 给所述终端的, 并解析所述下行块的内容。 本领域普通技术人员可以理解实现上述实施例方法中的全部或部分流 程, 是可以通过计算机程序来指令相关的硬件来完成, 所述的程序可存储 于一计算机可读取存储介质中, 该程序在执行时, 可包括如上述各方法的 实施例的流程。 其中, 所述的存储介质可为磁碟、 光盘、 只读存储记忆体 ( Read-Only Memory , ROM ) 或随机存储记忆体 ( Random Access Memory, RAM )等。 综上所述, 本发明实施例通过共享 TFI, 提高一个下行分组无线信道上 所能够复用的终端数量, 节省下行传输资源提高无线资源的利用率。
本发明实施例通过给至少两个终端分配一个共享的 TFI, 从而节约 GPRS系统的 TFI资源。 GPRS系统的网络侧可以将至少两个终端共享的下 行数据 /控制消息,通过携带共享 TFI的下行数据块或者控制块发送, 无需再 针对每个终端单独重复发送数据块,从而可以节约 G P RS系统的下行信道的 传输资源。
上述共享 TFI可以通过直接分配、 预留的或者分时共享的方式来实现, 并且还可以通过对至少两个终端进行分组, 不同组的终端共享同一个 TFI , 可以实现更加灵活的 TFI资源的共享方式。
本发明实施例还可以实现将至少两个终端共享的消息和各个终端的非 共享信息的消息, 通过携带共享 TFI的下行数据块或者控制块发送, 进一步 节约 G P RS系统的下行信道的传输资源。
以上所述, 仅为本发明较佳的具体实施方式, 但本发明的保护范围并 不局限于此, 任何熟悉本技术领域的技术人员在本发明揭露的技术范围内, 可轻易想到的变化或替换, 都应涵盖在本发明的保护范围之内。 因此, 本 发明的保护范围应该以权利要求的保护范围为准。

Claims

权利要求
1、 一种数据传输方法, 其特征在于, 包括:
网络侧给至少两个终端分配共享临时块流指示 TFI, 并将所述共享 TFI 发送给所述至少两个终端;
网络侧向所述至少两个终端发送下行块, 所述下行块块头中携带所述 共享 TFI, 以使接收到所述下行块的终端根据所述共享 TFI解析所述下行块 的内容。
2、 根据权利要求 1的数据传输方法, 其特征在于, 包括:
所述共享 TFI通过下行指派消息或者广播消息发送。
3、 根据权利要求 1所述的数据传输方法, 其特征在于, 所述的网络侧 给至少两个终端分配共享临时块流指示 TFI, 并将所述共享 TFI发送给所述 至少两个终端包括:
网络侧根据下行资源使用情况、 用户签约信息、 终端能力信息中的至 少一项, 判断是否给至少两个终端分配共享 TFI。
4、 根据权利要求 2所述的数据传输方法, 其特征在于, 所述下行指派 消息或者广播消息还包括所述共享 TFI对应的分组标识, 和 /或, 所述下行块 的块头中指定字段或者新增字段携带所述共享 TFI对应的分组标识; 以使接 收到所述下行块的终端根据所述共享 TFI以及所述共享 TFI对应的分组标识 解析所述下行块的内容。
5、 根据权利要求 2所述的数据传输方法, 其特征在于, 所述方法还包 括:
所述下行指派消息或者广播消息中还包括各个终端所属的下行块的标 识信息,
以使接收到所述下行块的终端根据所述下行块的标识信息、 该终端所 属的下行块的标识信息和所述共享 TFI来解析所述下行块的内容。
6、 一种数据传输装置, 设置在网络侧, 其特征在于, 包括:
临时块流指示 TFI指派模块, 用于给至少两个终端分配共享 TFI, 并将 所述共享 TFI发送给所述至少两个终端;
下行块传输模块, 用于向所述至少两个终端发送下行块, 所述下行块 块头中携带所述共享 TFI, 以使接收到所述下行块的终端根据所述共享 TFI 解析所述下行块的内容。
7、 根据权利要求 6所述的数据传输装置, 其特征在于, 所述数据传输 装置还包括:
判断模块, 用于根据当前下行资源使用情况、 用户签约信息、 终端能 力信息中的至少一项, 判断是否给至少两个终端分配共享 TFI;
所述 TFI指派模块用于当所述判断模块判断为是时, 给至少两个终端分 配共享 TFI, 并向终端发送携带给至少两个终端分配的共享 TFI的下行消息 或者广播消息。
8、 根据权利要求 7所述的数据传输装置, 其特征在于, 所述下行指派 消息或者广播消息还包括所述共享 TFI对应的分组标识, 和 /或, 所述下行块 的块头中指定字段或者新增字段携带所述共享 TFI对应的分组标识; 以使接 收到所述下行块的终端根据所述共享 TFI以及所述共享 TFI对应的分组标识 解析所述下行块的内容。
9、 根据权利要求 7所述的数据传输装置, 其特征在于, 所述下行指派 消息或者广播消息中还包括各个终端所属的下行块的块号信息,
以使接收到所述下行块的终端根据所述下行块的块号信息、 该终端所 属的下行块的块号信息和所述共享 TFI来解析所述下行块的内容。
10、 一种数据处理方法, 其特征在于, 包括:
终端接收网络侧发送下行指派消息或者广播消息, 所述下行指派消息 或者广播消息中包括分配的共享临时块流指示 TFI;
所述终端接收网络侧发送的携带所述共享 TFI的下行块, 根据所述共享 TFI解析所述下行块的内容。
11、 根据权利要求 10所述的数据处理方法, 其特征在于,
所述下行指派消息或者广播消息还包括所述共享 TFI对应的分组标识, 和 /或,所述下行块的块头中指定字段或者新增字段携带所述共享 TFI对应的 分组标识, 根据所述共享 TFI以及所述共享 TFI对应的分组标识解析所述下 行块的内容。
12、 根据权利要求 10所述的数据处理方法, 其特征在于,
所述下行指派消息或者广播消息中还包括各个终端所属的下行块的块 标识信息,
根据所述下行块的块标识信息、 终端所属的下行块的块标识信息和所 述共享 TFI来解析所述下行块的内容。
13、 根据权利要求 10所述的数据处理方法, 其特征在于,
所述终端接收网络侧发送的携带分配给所述终端的上行链路状态标记 USF的上行指派消息;
所述终端根据所述下行块中携带的 USF和所述终端所属的 USF相同,以 及所述下行块中携带的所述共享 TFI来确定所述下行块是发送给所述终端 的, 并解析所述下行块的内容。
14、 一种终端, 其特征在于, 包括:
第一接收模块, 用于接收网络侧发送的下行指派消息或者广播消息, 所述下行指派消息或者广播消息中包括分配的共享临时块流指示 TFI; 数据处理模块, 用于接收网络侧发送的携带所述共享 TFI的下行块, 根 据所述共享 TFI解析所述下行块的内容。
15、 根据权利要求 14所述的终端, 其特征在于, 所述下行指派消息或 者广播消息还包括所述共享 TFI对应的分组标识, 和 /或, 所述下行块的块头 中指定字段或者新增字段携带所述共享 TFI对应的分组标识;
所述数据处理模块具体用于根据所述共享 TFI以及所述共享 TFI对应的 分组标识解析所述下行块的内容。
16、 根据权利要求 14所述的终端, 其特征在于, 所述下行指派消息或 者广播消息中还包括各个终端所属的下行块的块号信息,
所述数据处理模块具体用于根据所述下行块的块号信息、 该终端所属 的下行块的块号信息和所述共享 TFI来解析所述下行块的内容。
17、 根据权利要求 14所述的终端, 其特征在于, 还包括:
第二接收模块, 用于接收网络侧发送的携带分配给所述终端的上行链 路状态标记 USF的上行指派消息;
所述数据处理模块具体用于根据所述下行块中携带的 USF和分配给所 述终端的 USF相同, 以及所述下行块中携带的所述共享 TFI来确定所述下行 块是发送给所述终端的, 并解析所述下行块的内容。
PCT/CN2011/083466 2010-12-03 2011-12-05 数据传输的方法和装置 WO2012072050A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
BR112013013685-5A BR112013013685B1 (pt) 2010-12-03 2011-12-05 Método e aparelho para transmissão de dados, método de processamento de dados e terminal
EP11845612.8A EP2648372B1 (en) 2010-12-03 2011-12-05 Method and apparatus for transmitting data

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN2010105795524A CN102487513A (zh) 2010-12-03 2010-12-03 数据传输的方法和装置
CN201010579552.4 2010-12-03

Publications (1)

Publication Number Publication Date
WO2012072050A1 true WO2012072050A1 (zh) 2012-06-07

Family

ID=46152957

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/083466 WO2012072050A1 (zh) 2010-12-03 2011-12-05 数据传输的方法和装置

Country Status (4)

Country Link
EP (1) EP2648372B1 (zh)
CN (1) CN102487513A (zh)
BR (1) BR112013013685B1 (zh)
WO (1) WO2012072050A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114846774A (zh) * 2019-12-25 2022-08-02 华为技术有限公司 一种通信方法及装置

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102710384A (zh) * 2012-06-13 2012-10-03 华为技术有限公司 一种发送下行数据块的方法及装置
CN103517430B (zh) * 2012-06-29 2016-09-28 华为技术有限公司 数据块的传输方法及装置
WO2015017980A1 (zh) * 2013-08-06 2015-02-12 华为技术有限公司 数据传输方法和装置
CN105532063B (zh) * 2014-08-18 2019-05-28 华为技术有限公司 一种数据传输方法、设备及系统

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6452940B1 (en) * 1999-03-31 2002-09-17 Telefonaktiebolaget L M Ericsson (Publ) Mobile station migration from D-AMPS packet system to edge/GPRS packet system in an integrated wireless network
CN1379600A (zh) * 2001-04-04 2002-11-13 西门子信息通讯网络公司 移动系统中提供多用户共享无线资源的分组服务的方法
CN1939002A (zh) * 2004-04-14 2007-03-28 意大利电信股份公司 用于通过无线通信网络,特别是移动电话网分发多媒体内容的方法和系统
WO2009102109A1 (en) * 2008-02-13 2009-08-20 Lg Electronics Inc. Method of reporting channel quality in egprs system
CN101578784A (zh) * 2007-01-05 2009-11-11 Lg电子株式会社 在egprs系统中报告信道质量的方法

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1745581B1 (en) * 2004-05-10 2008-09-03 Telecom Italia S.p.A. Method and system for efficient distribution of multicast services in a mobile network
US8582429B2 (en) * 2007-03-15 2013-11-12 Interdigital Technology Corporation Resource allocation and signalings for group scheduling in wireless communications
KR20130069883A (ko) * 2007-06-06 2013-06-26 인터디지탈 테크날러지 코포레이션 피기백 전송된 ack/nack 필드가 어드레싱된 임시 블록 흐름(tbf)을 표시하기 위한 방법 및 장치

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6452940B1 (en) * 1999-03-31 2002-09-17 Telefonaktiebolaget L M Ericsson (Publ) Mobile station migration from D-AMPS packet system to edge/GPRS packet system in an integrated wireless network
CN1379600A (zh) * 2001-04-04 2002-11-13 西门子信息通讯网络公司 移动系统中提供多用户共享无线资源的分组服务的方法
CN1939002A (zh) * 2004-04-14 2007-03-28 意大利电信股份公司 用于通过无线通信网络,特别是移动电话网分发多媒体内容的方法和系统
CN101578784A (zh) * 2007-01-05 2009-11-11 Lg电子株式会社 在egprs系统中报告信道质量的方法
WO2009102109A1 (en) * 2008-02-13 2009-08-20 Lg Electronics Inc. Method of reporting channel quality in egprs system

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114846774A (zh) * 2019-12-25 2022-08-02 华为技术有限公司 一种通信方法及装置

Also Published As

Publication number Publication date
CN102487513A (zh) 2012-06-06
BR112013013685A2 (pt) 2016-09-06
BR112013013685B1 (pt) 2022-01-11
EP2648372A1 (en) 2013-10-09
EP2648372B1 (en) 2016-03-09
EP2648372A4 (en) 2014-02-26

Similar Documents

Publication Publication Date Title
US10972877B2 (en) Radio terminal and base station
US10939251B2 (en) User equipment and base station
JP6741969B2 (ja) 移動通信システム
US9860780B2 (en) Communications terminal and method of communicating
EP2850900B1 (en) System and method for allocating periodic resources
JP2018160927A (ja) マシンタイプコミュニケーションのための通信システムおよび通信方法
US10813077B2 (en) Communications device, infrastructure equipment, communication system and methods for group paging and grouping communication devices based on various criteria
KR20080071904A (ko) 시스템 정보의 전송 및 수신 방법
CN111264080A (zh) 在无线通信系统中触发发送载波选择的方法和设备
KR20090028384A (ko) 이동 통신 시스템에서의 데이터 송수신 방법
US20230018928A1 (en) Method and Device for Power-Saving in Wireless Sidelink Communication
WO2011134316A1 (zh) 一种正交频分复用系统的无线资源分配、调度方法和装置
KR20080086399A (ko) 무선 통신 시스템에서의 데이터 전송 방법
EP2625909B1 (en) Communications systems, communications device, infrastructure equipment and method
WO2018084194A1 (ja) 無線端末及び基地局
WO2012072050A1 (zh) 数据传输的方法和装置
CN104469747A (zh) 接收下行数据的方法及终端
CN113498026A (zh) 一种通信方法及相关设备
CN104754754A (zh) 半静态调度下的迟后接入方法
WO2023008481A1 (ja) 通信装置、基地局、及び通信方法
WO2023008483A1 (ja) 通信装置、基地局、及び通信方法
JP7425259B2 (ja) 通信制御方法及び基地局
WO2023153312A1 (ja) 通信装置及び通信方法
WO2023063262A1 (ja) 通信装置、基地局、及び通信方法
JP2023145566A (ja) 通信制御方法、ユーザ装置及びプロセッサ

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: 11845612

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2011845612

Country of ref document: EP

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112013013685

Country of ref document: BR

ENP Entry into the national phase

Ref document number: 112013013685

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20130603