Classifications

• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L1/00—Arrangements for detecting or preventing errors in the information received
  • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
  • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
  • H04L1/1607—Details of the supervisory signal
  • H04L1/1664—Details of the supervisory signal the supervisory signal being transmitted together with payload signals; piggybacking
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L1/00—Arrangements for detecting or preventing errors in the information received
  • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
  • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
  • H04L1/1607—Details of the supervisory signal
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L1/00—Arrangements for detecting or preventing errors in the information received
  • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
  • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
  • H04L1/1607—Details of the supervisory signal
  • H04L1/1685—Details of the supervisory signal the supervisory signal being transmitted in response to a specific request, e.g. to a polling signal
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L1/00—Arrangements for detecting or preventing errors in the information received
  • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
  • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
  • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
  • H04L1/1829—Arrangements specially adapted for the receiver end
  • H04L1/1854—Scheduling and prioritising arrangements
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
  • H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
  • H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
  • H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
  • H04L69/324—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the data link layer [OSI layer 2], e.g. HDLC
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W24/00—Supervisory, monitoring or testing arrangements
  • H04W24/08—Testing, supervising or monitoring using real traffic
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W24/00—Supervisory, monitoring or testing arrangements
  • H04W24/10—Scheduling measurement reports ; Arrangements for measurement reports
• • 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/04—Error control
• • 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/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information

Definitions

• the invention discloses a method for use in a cellular access system, in which system there is at least one Radio Base Station, RBS, for the control of the traffic to and from a cell in the system, in which cell there can be a user with a User Equipment, UE.
• RBS Radio Base Station
• improved performance of so called ACK/NACK reports can be obtained.
• the current EDGE standard allows for two different Radio Link Control, RLC, modes of operation: acknowledged and un-acknowledged mode.
• RLC Radio Link Control
• NPM non-persistent RLC operating mode
• This non-persistent mode is similar to the acknowledged mode operation, but with the difference that a timer is suggested for use in order to enforce a maximum allowed time from the reception of an RLC block until it must be delivered to the Logical Link Protocol, LLC, protocol layer above.
• the ACK/NACK information for acknowledged mode is sent in special control blocks, containing a starting sequence number and a bitmap representing radio blocks.
• the reporting strategy e. g. how and when reports are sent etc., is controlled by the network.
• the mobile will send ACK/NACK information as a response to a poll from the base station.
• the poll will include information of when to send the control block, and the content of the report.
• FPB first partial bitmap
• NPB next partial bitmap
• a drawback of the current ACK/NACK reporting protocols is that a full control block is needed every time ACK/NACK information is sent. Therefore the overhead will be large when frequent ACK/NACK information is needed for delay sensitive services.
• PANs piggy-backed ACK/NACK Reports
• BSN Block Sequence Numbers
• BSN Block Sequence Numbers
• bitmaps giving ACK/NACK information of radio blocks after a specified BSN
• size bits or extension bits specifying the size of the ACK/NACK information. This method allows for the sent ACK/NACK information to consist either of one single PAN or be split into several multiple segment PANs.
• the First Partial Bitmap, FPB. and Next Partial Bitmap, NPB, reporting strategies do not guarantee that the BSN number that identifies the RLC block causing the event will be included in the PAN.
• FPB this BSN will not be included in the PAN until it has reached the lower end (lowest BSNs) of the RLC window, thus causing retransmission delays to become significantly larger.
• the method should be aimed at applications in cellular access systems.
• This need is addressed by the present invention in that it provides a method for use in a cellular access system in which system there is at least one Radio Base Station, RBS, which controls the traffic to and from a cell in the system.
• RBS Radio Base Station
• the cell there can be a user with a User Equipment, UE, and the RBS and the UE are able to send and receive data blocks, which may comprise sequence numbers, to and from each other.
• UE User Equipment
• the RBS and the UE also exchange reports comprising information on whether or not data blocks have been received successfully, so that both the UE and the RBS can be either the reporting party or the report receiving party.
• the method of the invention further comprises:
• the reporting party decides the contents of the report using at least one of the following priority rules which have been given an internal priority ranking: • Data blocks which are identified as having a lower delay tolerance than other data blocks are given priority. • Data blocks which have been detected as received in error, and whose status has not been reported since the error was detected are given priority,
• the invention also discloses a transceiver such as a User Equipment or a Radio Base Station for use in a cellular access system which works according to the principles described above.
• Fig 1 shows an example of a system in which the invention may be applied
• Fig 2 shows a flow chart of some steps of the invention
• Fig 3 shows a transceiver of the invention.
• RBS Radio Base Station
• Node B a node known as Node B or sometimes "eNodeB"
• UE User Equipment
• MS Mobile Stations
• a cellular access system 100 is shown in which the invention may be applied.
• the system 100 comprises a Radio Base Station, an RBS 120, which controls the traffic to and from a cell 110 in the system 100.
• UE 130, 140 In the cell 110 there can be a user with a User Equipment.
• UE 130, 140 The RBS 120 and the UE 130, 140, are able to send and receive data in blocks to and from each other.
• the data which is sent between the RBS and the UE may comprise sequence numbers, which aid in identifying the data blocks.
• the invention is primarily intended to provide a new reporting strategy for ACK/NACK reports, which can be used together with "event based" reporting of ACK/NACK, especially if the ACK/NACK reports are "piggy backed" ("PAN") on data sent from the reporting party to the other party, i.e. the "report receiving party", which is the party that sent the data that the report refers to.
• PAN packet backed
• the invention can be applied either to the acknowledged or to the non persistent RLC mode, which have been explained above, and the invention describes which parts of the RLC transmission window that should be covered by the PANs for those modes.
• an ACK/NACK report can be "piggy backed" to a data transmission which is addressed to, or intended for, a party in the system which is not the report receiving party.
• both the RBS 120 and the UE 130, 140 can be either the reporting or the report receiving party.
• the reporting party or the "report receiving party” or words which are essentially synonyms of those words.
• the reporting party sends an ACK/NACK report to the report receiving party, and thus lets the report comprise information on whether or not data blocks which were transmitted by the report receiving party were received successfully. Also, according to this embodiment of the invention, the reporting party sends the ACK/NACK report together with data which it, i.e. the reporting party, needs to transmit to the report receiving party, i.e. the party which transmitted the data that the ACK/NACK-report concerns.
• the reporting party which has thus received data from the report receiving party may decide the contents of the ACK/NACK report using at least one of a number of priority rules which will be described in the following.
• the reporting party or the system needs to make a ranking of the priority rules, i.e. a rule which enables the reporting party to decide which of the rules is the most important if there is a conflict between two or more of the rules explained below.
• This ranking can be done either once and for all, for example when installing or setting up the system, or the ranking can be done adaptively, either at regular intervals in time or each time that a report is to be sent.
• the ACK/NACK reporting can be controlled by the UE as well.
• the idea will in the following be described with reference to a reporting party, since the idea behind the invention can also be used by the RBS when sending ACK/NACK reports to the UE.
• the network If the UE is the reporting party, there is also a possibility for the network to send a poll for a PAN report to the UEs via the RBS.
• priority rules are comprised in the invention:
• the priority rules can also change depending on whether or not there has been a poll, usually from the RBS to the UE. For example, data blocks that belong to a TBF, Temporary Block Flow, that has been polled could be given top priority. Another way of adapting the priorities would be to give data block with lowest BSN from a polled TBF top priority. With that rule, a PAN poll would be similar to a FPB poll, First Partial Bitmap, which gives the base station ACK/NACK information of the beginning of the reception window in the UE.
• the priority rules can also be used to decide the size of the PAN. For example, it could be decided that the PAN should be sufficiently large to cover all data blocks that are covered by one or more of the priority rules of the invention.
• a multi segment PAN with several Starting Sequence Numbers, SSN is needed. If the PAN has its own channel coding in the system, the size of the PAN should be predefined or signalled in the header of the message, so that the size is known before the party which receives the PAN starts to decode it. As an option, a flag (consisting of one or more bits) in the message can be used to signal the presence or absence of a PAN in the transmission or message, and if there is a PAN included in the transmission or message, the receiving party can try to decode the PAN, with attempts being made for a number of different but known alternative PAN sizes.
• SSN Starting Sequence Numbers
• the structure of the PAN i.e. the number of segments and the relative size of the segments, could also be signalled in the message header, as an alternative to which, in order to save space in the header, a specific structure field in the beginning of the PAN could be used.
• This structure field will then comprise information on which of one or more predefined PAN structures that is used. The size and interpretation of the structure field could vary depending on the size of the PAN.
• a decision on whether to let the PAN consist of one or more segments should be made by the party which transmits the PAN.
• a single segment PAN can carry ACK/NACK information for more consecutive BSNs than a two-segment PAN of the same size, but a two-segment PAN can cover a larger range of BSNs.
• the method proposed by the invention is to test both these types of PAN, and to evaluate which type that fulfils the priority rules best and contains the largest amount of erroneous blocks.
• an ACK/NACK reporting scheme could be included using PANs and the reporting strategy shown below.
• the example below will use a UE as the reporting party, but those skilled in the field will realize that the method described below could also be applied to an RBS with the proper modifications.
• a UE 130, 140 will send a PAN if polled for it by the RBS 120, or if it detects an erroneous transmission.
• This PAN has one of two or three predefined sizes, the size being signalled in the header, as described above. If a large PAN size is used, the PAN starts with a structure bit, defining if one or two segments are used.
• TBFs Temporary Block Flows, which have received a forced PAN poll, i.e. a poll where the response to the poll, the ACK/NACK information, is allowed to be piggybacked in a PAN.
• the NPM TBF with the lowest delay tolerance (e.g. lowest setting of NPM transfer time) will be selected first.
• acknowledge mode it should be noted that item 3, acknowledged mode RLC, will make sure to encapsulate the BSN causing the event in the PAN.
• the second segment will continue to be filled with the remaining new unreported errors.
• item 4 will enforce that the second segment covers the beginning of the reception window and effectively work as a First Partial Bitmap, FPB, which can, for example, help to prevent stalling.
• FPB First Partial Bitmap
• BSN_MAP 1011 , which covers BSNs 17-20.
• the reporting strategy of the invention would in this example produce a PAN with the following characteristics:
• the FPB strategy on the other hand, would have produced a PAN with the following characteristics:
• fig 2 shows a brief flow chart 200 with some of the steps of a method of the invention:
• the reporting party sends a transmission comprising a report to the report receiving party, the report comprising information on whether or not data blocks which were transmitted by the report receiving party were received successfully, and the report is sent together with data from the reporting party to the report receiving party, or as mentioned previously, to another party in the cell.
• the reporting party attaches addresses for the recipient of the data blocks and for the report in the transmission.
• step 220 the reporting party decides the contents of the report using at least one of the following priority rules, steps 230-250, which have been given an internal priority ranking:
• Fig 3 shows a rough block diagram of a transceiver 300 of the invention, the transceiver being either a UE or an RBS in the system 100 described above.
• the transceiver 300 comprises means 310, for sending and means 320 for receiving data blocks, which may comprise sequence numbers, to and from a second transceiver in the system, so that the transceiver 300 can be either a reporting or a report receiving party with respect to the second transceiver.
• the transceiver 300 comprises means 330 for sending a report, when the first transceiver is the reporting party, to the report receiving party, the report comprising information on whether or not data blocks which were transmitted by the report receiving party were received successfully, and also comprises means 340 for sending said report together with data to the report receiving party.
• the means 330 and 340 may be one and the same, for example a microprocessor or some other controlling device, as shown in fig 3. which controls and coordinates the transmitter 310 and the receiver 320.
• the transceiver 300 also comprises means 350 for deciding the contents of the report using at least one of the priority rules described above. These means 350 may also be embodied by the processor or controller mentioned previously.
• the reporting party can send the ACK/NACK report together with data to the report receiving party or to another party in the cell.
• an RBS may broadcast a message which comprises data intended for one UE in the cell together with an ACK/NACK report (a " PAN") which is intended for another UE in the cell. Since the message is a "broadcast" message, both of the UEs will receive the message, and since the RBS includes addresses both for the recipient of the data and for the recipient of the ACK/NACK report in the transmission, both of the UEs will extract only that part of the transmission or message which is intended for them.
• a typical message according to the invention will comprise a data part and a "report part", i.e. a PAN part. The message will also include an address for the data, as well as an address for the PAN.
• the address for the PAN may be designed in a number of ways.
• One way is to let a message comprise explicit addresses both for the data and for the PAN, another way is to let the message comprise a flag (one or more bits) which signals the presence or absence of a PAN in the message, and to let the PAN as such comprise the address for which it is intended.
• An alternative way, as described previously in this text is to use a flag to signal the absence or presence of a PAN in the message, and to then let the report receiving party try different PAN sizes.

Landscapes

• Engineering & Computer Science (AREA)
• Computer Networks & Wireless Communication (AREA)
• Signal Processing (AREA)
• Computer Security & Cryptography (AREA)
• Mobile Radio Communication Systems (AREA)
• Detection And Prevention Of Errors In Transmission (AREA)

Priority Applications (9)

Applications Claiming Priority (4)

Related Child Applications (2)

Publications (2)

Family

ID=38609928

Family Applications (1)

Country Status (5)

Cited By (7)

Families Citing this family (9)

Family Cites Families (27)

• 2007
  • 2007-03-27 DK DK07716142.0T patent/DK2008391T3/da active
  • 2007-03-27 WO PCT/SE2007/050186 patent/WO2007120107A2/en not_active Ceased
  • 2007-03-27 JP JP2009506448A patent/JP4927940B2/ja not_active Expired - Fee Related
  • 2007-03-27 EP EP07716142.0A patent/EP2008391B1/en not_active Not-in-force
  • 2007-03-27 US US12/297,808 patent/US8155034B2/en not_active Expired - Fee Related
  • 2007-03-27 EP EP13188011.4A patent/EP2685655B1/en active Active
• 2012
  • 2012-03-05 US US13/411,903 patent/US8630210B2/en active Active
• 2013
  • 2013-11-26 US US14/090,540 patent/US9001706B2/en active Active
• 2015
  • 2015-03-06 US US14/640,983 patent/US20150180614A1/en not_active Abandoned

Non-Patent Citations (1)

Also Published As

Similar Documents

Legal Events