EP3209047B1 - Système de communication et procédé de communication - Google Patents

Système de communication et procédé de communication Download PDF

Info

Publication number
EP3209047B1
EP3209047B1 EP15849906.1A EP15849906A EP3209047B1 EP 3209047 B1 EP3209047 B1 EP 3209047B1 EP 15849906 A EP15849906 A EP 15849906A EP 3209047 B1 EP3209047 B1 EP 3209047B1
Authority
EP
European Patent Office
Prior art keywords
timing
grant
bsr
unit
transmission
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
EP15849906.1A
Other languages
German (de)
English (en)
Other versions
EP3209047A1 (fr
EP3209047A4 (fr
Inventor
Satoshi Tanaka
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
NEC Corp
Original Assignee
NEC Corp
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 NEC Corp filed Critical NEC Corp
Publication of EP3209047A1 publication Critical patent/EP3209047A1/fr
Publication of EP3209047A4 publication Critical patent/EP3209047A4/fr
Application granted granted Critical
Publication of EP3209047B1 publication Critical patent/EP3209047B1/fr
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/14—Relay systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W16/00—Network planning, e.g. coverage or traffic planning tools; Network deployment, e.g. resource partitioning or cells structures
    • H04W16/24—Cell structures
    • H04W16/26—Cell enhancers or enhancement, e.g. for tunnels, building shadow
    • 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/0278—Traffic management, e.g. flow control or congestion control using buffer status reports
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/1263—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/21—Control channels or signalling for resource management in the uplink direction of a wireless link, i.e. towards the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/04—Large scale networks; Deep hierarchical networks
    • H04W84/042—Public Land Mobile systems, e.g. cellular systems
    • H04W84/047—Public Land Mobile systems, e.g. cellular systems using dedicated repeater stations
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/08—Access point devices

Definitions

  • the present invention relates to a radio relay station, a radio base station, a communication system, and a communication method that perform communication.
  • FIG. 21 is a diagram illustrating one form of a common radio communication system provided with a relay apparatus.
  • the radio communication system illustrated in FIG. 21 is composed of DeNBs (Donor evolved Node Bs) 1000-1 and 1000-2 that are radio base stations, an RN (Relay Node) 2000 that is a radio relay station, and UEs (User Equipments) 3000-1 and 3000-2 that are communication terminals.
  • DeNBs Donor evolved Node Bs
  • RN Relay Node
  • UEs User Equipments
  • the RN 2000 relays communication between the DeNB 1000-1 and the UE 3000-1. Furthermore, the RN 2000 relays communication between the DeNB 1000-2 and the UE 3000-2.
  • a technology in which, when, in a radio relay station as described above, a downlink line control signal is sent from a radio base station to the radio relay station at a timing at which the radio relay station is sending a downlink line control signal to a communication terminal, the radio relay station allocates a resource region that can receive the downlink line control signal sent from the radio base station has been considered (refer to, e.g., PTL 1).
  • US 2010/302946 discloses a system and method for relay node flow control and/or congestion control in a wireless communications system.
  • a method for relay operation includes determining a buffer status of a buffer for data to be transmitted on a communications channel allocated from network resources controlled by a communications controller, computing buffer status information based on the buffer status, and transmitting the buffer status information to the communications controller.
  • US 2011/269393 discloses a method and apparatus for "early" triggering of a BSR in a relay node in order to reduce the overall time between a UE's transmission of data to a relay node on an access link and the corresponding transmission of that data from the relay node to a donor base station on a backhaul link.
  • FIG. 22 is a sequence chart for describing an example of uplink data transmission processing in the radio communication system illustrated in FIG. 21 .
  • the UE 3000-1 sends, to the RN 2000, an uplink scheduling request signal (SR_a) for sending uplink data to the DeNB 1000-1. Then, the RN 2000 sends, as a response signal therefor, an uplink scheduling information signal (UL_Grant for SR_a) to the UE 3000-1. Subsequently, the UE 3000-1 sends, to the RN 2000, an uplink buffer status-reporting signal (BSR_a) indicating a storage status of a buffer that temporarily stores uplink data. Then, the RN 2000 sends a response signal (UL_Grant for BSR_a) therefor to the UE 3000-1.
  • SR_a uplink scheduling request signal
  • BSR_a uplink buffer status-reporting signal
  • the UE 3000-1 When receiving the UL_Grant for BSR_a, the UE 3000-1 sends, to the RN 2000, uplink data (UL_Data_a) that are to be sent to the DeNB 1000-1. After receiving the UL_Data_a from the UE 3000-1, the RN 2000 sends an SR_a to the DeNB 1000-1.
  • UL_Data_a uplink data
  • the UE 3000-2 sends, to the RN 2000, an uplink scheduling request signal (SR_b) for sending uplink data to the DeNB 1000-2. Then, the RN 2000 sends, as a response signal therefor, an uplink scheduling information signal (UL_Grant for SR_b) to the UE 3000-2. Subsequently, the UE 3000-2 sends, to the RN 2000, an uplink buffer status-reporting signal (BSR_b) that indicates a storage status of a buffer that temporarily stores uplink data. Then, the RN 2000 sends a response signal (UL_Grant for BSR_b) therefor to the UE 3000-2.
  • SR_b uplink scheduling request signal
  • BSR_b uplink buffer status-reporting signal
  • the UE 3000-2 When receiving the UL_Grant for BSR_b, the UE 3000-2 sends, to the RN 2000, uplink data (UL_Data_b) that are to be sent to the DeNB 1000-2. After receiving the UL_Data_b from the UE 3000-2, the RN 2000 sends an SR_b to the DeNB 1000-2.
  • UL_Data_b uplink data
  • the DeNB 1000-2 sends the UL_Grant for SR_b to the RN 2000
  • the RN 2000 can perform reception processing of only one of the uplink scheduling information signals. Furthermore, even when the RN 2000 attempts to simultaneously perform sending of the BSR_a to the DeNB 1000-1 and sending of the BSR_b to the DeNB 1000-2, the RN 2000 can send the uplink buffer status-reporting signal for only one thereof.
  • the DeNB 1000-2 sends the UL_Grant for BSR_b to the RN 2000 simultaneously with the DeNB 1000-1 sending the UL_Grant for BSR_a to the RN 2000
  • the RN 2000 can only perform reception processing of only one thereof.
  • the RN 2000 can send only the uplink data to one thereof.
  • timings at which signals are sent to or received from a plurality of radio base stations are simultaneous. For example, when transmission/reception of such signals between the RN 2000 and the DeNB 1000-2 cannot be carried out, retransmission processing for these signals is performed with the DeNB 1000-2, resulting in a problem of delayed uplink data transmission.
  • FIG. 23 is a sequence chart for describing another example of the uplink data transmission processing in the radio communication system illustrated in FIG. 21 .
  • a procedure until the RN 2000 attempts to perform simultaneously sending of the UL_Data_a to the DeNB 1000-1 and sending of the UL_Data_b to the DeNB 1000-2 is substantially the same as a procedure in FIG. 22 .
  • FIG. 23 a case where a packet is subsequently discarded will be described.
  • FIG. 23 illustrates a case where, when timings at which signals are sent to or received from a plurality of radio base stations become simultaneous and, therefore, for example, the RN 2000 cannot perform transmission/reception of such signals to/from the DeNB 1000-2, a packet (uplink data) related to delay is discarded.
  • a packet uplink data related to delay
  • the RN 2000 cannot send uplink data to the DeNB 1000-2 and, therefore, an amount of time for which the uplink data are buffered within the RN 2000 runs out, the buffered uplink data are discarded.
  • transmission/reception of the signals are performed between the UE 3000-2 and the RN 2000 again, retransmission processing for these signals is performed between the RN 2000 and the DeNB 1000-2, resulting in a problem of the uplink data transmission being delayed.
  • FIG. 24 is a sequence chart for describing an example of downlink data transmission processing performed by the radio communication system illustrated in FIG. 21 .
  • the RN 2000 can perform reception processing for the downlink data from only one of the DeNB 1000-2 and the DeNB 1000-1. For example, when the RN 2000 has performed only reception processing of the DL_Data_a sent from the DeNB 1000-1, the RN 2000 sends the DL_Data_a to the UE 3000-1. Then, as a response to receiving the downlink data, the UE 3000-1 sends an Ack(HARQ)_a to the RN 2000.
  • the RN 2000 After receiving the Ack(HARQ)_a from the UE 3000-1, the RN 2000 sends the Ack(HARQ)_a to the DeNB 1000-1. On the other hand, since the RN 2000 has not received the downlink data from the DeNB 1000-2, the RN 2000 sends, to the DeNB 1000-2, a Nack(HARQ)_b that is a signal indicating that the RN 2000 has not received the downlink data from the DeNB 1000-2.
  • the DeNB 1000-2 resends, to the RN 2000, the downlink data (DL_Data_b) to be sent to the UE 3000-2.
  • the RN 2000 sends the DL_Data_b to the UE 3000-2.
  • the downlink data transmission has a problem of being delayed by simultaneous transmission, as is the case with the uplink data transmission.
  • the technology described in PTL 1 is merely a technology that carries out allocation of resource regions and, as is the case with the foregoing configuration, has a problem of being incapable of preventing data transmission delay caused by simultaneous sending to or simultaneous reception from a plurality of nodes.
  • the present invention provides a communication system, and a communication method, as set out in the appended claims.
  • a radio relay station that includes a transmission means for notifying a radio base station of a timing at which uplink data sent from a communication terminal are able to be sent to the radio base station and then sending the uplink data to the radio base station.
  • a radio base station that includes a transmission means for notifying a radio relay station that relays communication with a communication terminal of a timing at which downlink data are able to be sent to the radio relay station and then sending the downlink data to the radio relay station.
  • FIG. 1 is a diagram illustrating a first example embodiment of the communication system of the present invention.
  • a communication system in this example embodiment, as illustrated in FIG. 1 includes a DeNB 100, an RN 200, and a UE 300.
  • the DeNB 100 is a radio base station that communicates with the UE 300 via the RN 200.
  • the RN 200 is a radio relay station that relays communication between the DeNB 100 and the UE 300.
  • the UE 300 is a communication terminal that communicates with the DeNB 100 via the RN 200.
  • FIG. 2 is a diagram illustrating an example of an internal structure of the RN 200 illustrated in FIG. 1 .
  • the RN 200 illustrated in FIG. 1 includes a transmission unit 201 as illustrated in FIG. 2 .
  • FIG. 2 illustrates only structural elements concerning this example embodiment, of structural elements that the RN 200 illustrated in FIG. 1 includes.
  • the transmission unit 201 sends to the DeNB 100 uplink data sent from the UE 300. At this time, the transmission unit 201 notifies the DeNB 100 of the timing at which the uplink data sent from the UE 300 can be sent to the DeNB 100 and then sends the uplink data to the DeNB 100. Note that in each block diagram in the present application, an arrow provided for a block indicates only a propagating direction of a signal that corresponds to a description and does not limit the propagating directions of other signals.
  • FIG. 3 is a flowchart for describing an example of the communication method in the communication system illustrated in FIG. 1 .
  • the transmission unit 201 notifies the DeNB 100 of timing at which the transmission unit 201 can send the uplink data (step S2). After that, at that timing, the transmission unit 201 sends the uplink data to the DeNB 100 (step S3).
  • the radio relay station notifies the radio base station of the timing at which the radio relay station can send the uplink data, and then sends the uplink data to the radio base station at the timing. Therefore, the communication system of the first example embodiment can prevent failure in sending the uplink data and therefore can make the data transmission more efficient.
  • FIG. 4 is a diagram illustrating a second example embodiment of the communication system of the present invention.
  • the communication system in this example embodiment includes a DeNB 101, an RN 202, and a UE 300 as illustrated in FIG. 4 .
  • the DeNB 101 is a radio base station that communicates with the UE 300 via the RN 202.
  • the RN 202 is a radio relay station that relays communication between the DeNB 101 and the UE 300.
  • the UE 300 is a communication terminal that communicates with the DeNB 101 via the RN 202.
  • FIG. 5 is a diagram illustrating an example of an internal structure of the DeNB 101 illustrated in FIG. 4 .
  • the DeNB 101 illustrated in FIG. 4 includes a transmission unit 102 as illustrated in FIG. 5 .
  • FIG. 5 illustrates only structural elements concerning this example embodiment, of the structural elements that the DeNB 101 illustrated in FIG. 4 includes.
  • the transmission unit 102 notifies the RN 202 of the timing at which downlink data can be sent to the RN 202 and then sends the downlink data to the RN 202.
  • FIG. 6 is a flowchart for describing an example of the communication method in the communication system illustrated in FIG. 4 .
  • the DeNB 101 receives downlink data sent from a higher-order apparatus (e.g., a SGW (Serving Gateway)) of the DeNB 101 (step S11)
  • the transmission unit 102 notifies the RN 202 of the timing at which downlink data can be sent (step S12).
  • the transmission unit 102 at that timing, sends the downlink data to the RN 202 (step S13).
  • the radio base station notifies the radio relay station of the timing at which the station can send downlink data, and then, at that timing, sends the downlink data to the radio relay station. Therefore, the communication system of the second example embodiment can prevent failure in sending downlink data and therefore can make data transmission more efficient.
  • FIG. 7 is a diagram illustrating a third example embodiment of the communication system of the present invention.
  • the communication system in this example embodiment includes DeNBs 103-1 and 103-2, the RN 203, and UEs 300-1 and 300-2.
  • the DeNB 103-1 is a radio base station that communicates with the UE 300-1 via the RN 203.
  • the DeNB 103-2 is a radio base station that communicates with the UE 300-2 via the RN 203.
  • the RN 203 is a radio relay station that relays communication between the DeNB 103-1 and the UE 300-1 and communication between the DeNB 103-2 and the UE 300-2.
  • the RN 203 sends uplink signals to the DeNBs 103-1 and 103-2 by using a communication method of SC-FDMA or TD-SCDMA.
  • the SC-FDMA is an abbreviation of "Single Carrier-Frequency Division Multiple Access”
  • TD-SCDMA is an abbreviation of "Time Division-Synchronous Code Division Multiple Access”.
  • the UE 300-1 is a communication terminal that communicates with the DeNB 103-1 via the RN 203.
  • the UE 300-2 is a communication terminal that communicates with the DeNB 103-2 via the RN 203.
  • FIG. 8 is a diagram illustrating an example of an internal structure of the RN 203 illustrated in FIG. 7 .
  • the RN 203 illustrated in FIG. 7 includes a transmission unit 204 and a UL Data receiving unit 211, as illustrated in FIG. 8 .
  • the transmission unit 204 includes a UL Grant receiving unit 210, a UL Grant information accumulating unit 212, a UL SR/BSR information accumulating unit 213, a UL transmission establishment timing extracting unit 214, a UL transmission/reception candidate timing extracting unit 215, a UL opposing node determination unit 216, a UL opposing node flag providing unit 217, a UL transmission/reception feasible timing candidate providing unit 218, a UL SR/BSR determination unit 219, a UL BSR generating unit 220, a UL BSR transmission unit 221, a UL SR generating unit 222, a UL SR transmission unit 223, a UL Data transmission feasibility determination unit 224, an SR/BSR retransmission processing unit 225, and a UL Data transmission unit 226.
  • FIG. 8
  • the UL Data receiving unit 211 receives uplink data sent from the UEs 300-1 and 300-2 and outputs the received uplink data to the UL opposing node determination unit 216.
  • the UL Grant receiving unit 210 receives response signals (UL Grant), such as uplink scheduling information, that are sent from the DeNBs 103-1 and 103-2, and outputs the signals to the UL Grant information accumulating unit 212.
  • UL Grant response signals
  • the UL Grant information accumulating unit 212 accumulates the UL Grant that have been output from the UL Grant receiving unit 210.
  • the UL SR/BSR information accumulating unit 213 accumulates reception timing information regarding UL Grant and send timing information regarding an uplink buffer status report (UL Buffer Status Report, referred to hereinafter as UL BSR) signal contained in an uplink scheduling request (UL Scheduling Request, referred to hereinafter as UL SR) signal that has already been sent from the UL SR transmission unit 223. Furthermore, the UL SR/BSR information accumulating unit 213 accumulates the reception timing information regarding UL Grant and the send timing information regarding uplink data (UL Data) contained in the UL BSR that has already been sent from the UL BSR transmission unit 221.
  • UL BSR uplink buffer status report
  • UL Scheduling Request UL Scheduling Request
  • the UL transmission establishment timing extracting unit 214 extracts a send feasible timing candidate for UL BSR that is to be contained in UL SR, based on the UL Grant accumulated in the UL Grant information accumulating unit 212. Furthermore, the UL transmission establishment timing extracting unit 214 extracts a send feasible timing candidate for UL Data that is to be contained in UL BSR, based on the UL Grant accumulated in the UL Grant information accumulating unit 212.
  • the UL transmission/reception candidate timing extracting unit 215 refers to the reception timing for UL Grant and the transmission timing candidate for sending UL BSR contained in the UL SR accumulated in the UL SR/BSR information accumulating unit 213. Furthermore, the UL transmission/reception candidate timing extracting unit 215 refers to the reception timing for the UL Grant and the send timing candidate for sending UL Data contained in the UL BSR accumulated in the UL SR/BSR information accumulating unit 213.
  • the UL transmission/reception candidate timing extracting unit 215 extracts, from these timings referred to, a send timing candidate for next UL BSR/UL Data that can be sent by the UL SR/BSR and a reception timing candidate for receiving a UL Grant for sending the UL BSR/UL Data.
  • the UL opposing node determination unit 216 determines an opposing node. Concretely, the UL opposing node determination unit 216 determines whether the opposing node is the DeNB 103-1 or 103-2 or a higher-order apparatus such as a SGW. In this example embodiment, because the transmission unit 204 is packaged in the RN 203, the UL opposing node determination unit 216 determines that the opposing node is the DeNB 103-1 or 103-2. On the other hand, in the case where the transmission unit 204 is packaged in the DeNB 103-1 or the DeNB 103-2, the UL opposing node determination unit 216 determines that the opposing node is an SGW that is a higher-order apparatus above the DeNBs 103-1 and the DeNB 103-2.
  • the UL opposing node flag providing unit 217 provides a flag according to a result of determination by the UL opposing node determination unit 216.
  • the UL transmission/reception feasible timing candidate providing unit 218, based on information extracted by the UL transmission establishment timing extracting unit 214 and the UL transmission/reception candidate timing extracting unit 215, provides a send feasible timing candidate for a UL BSR contained in the UL SR and a reception feasible timing candidate for the UL Grant. Furthermore, the UL transmission/reception feasible timing candidate providing unit 218, based on information extracted by the UL transmission establishment timing extracting unit 214 and the UL transmission/reception candidate timing extracting unit 215, provides a send feasible timing candidate for UL Data that is to be contained in the UL BSR and a reception feasible timing candidate for the UL Grant.
  • the UL SR/BSR determination unit 219 determines which one of the UL SR and the UL BSR is the signal that is to be sent next.
  • the UL BSR generating unit 220 When the UL SR/BSR determination unit 219 has determined that the signal to be sent next is a UL BSR, the UL BSR generating unit 220 generates a UL BSR in which the timing information is contained.
  • the UL BSR transmission unit 221 is an uplink buffer status-reporting signal transmission unit that sends the UL BSR generated by the UL BSR generating unit 220 to the DeNBs 103-1 and 103-2.
  • the UL BSR transmission unit 221 when sending the UL BSR to the DeNBs 103-1 and 103-2, sends the UL BSR in which information indicating the timing at which a UL Grant for the UL BSR can be received and information indicating a timing at which the UL Data can be sent to the DeNBs 103-1 and 103-2 are contained.
  • the UL SR generating unit 222 generates a UL SR in which the timing information is contained, when the UL SR/BSR determination unit 219 has determined that the signal to be sent next is a UL SR.
  • the UL SR transmission unit 223 is an uplink scheduling request signal transmission unit that sends the UL SR generated by the UL SR generating unit 222 to the DeNBs 103-1 and 103-2.
  • the UL Data transmission feasibility determination unit 224 determines whether the sending of the UL Data is feasible, based on the UL Grant accumulated in the UL Grant information accumulating unit 212. Concretely, the UL Data transmission feasibility determination unit 224 determines whether the sending of the UL Data is feasible, based on the send timing notified by the UL Grant accumulated by the UL Grant information accumulating unit 212.
  • the SR/BSR retransmission processing unit 225 performs retransmission processing for the UL SR and the UL BSR when the UL Data transmission feasibility determination unit 224 has determined that the UL Data cannot be sent.
  • the UL Data transmission unit 226 sends the UL Data to the DeNBs 103-1 and 103-2 when the UL Data transmission feasibility determination unit 224 has determined that the UL Data can be sent.
  • FIG. 9 is a diagram illustrating an example of an internal structure of the DeNB 103-1 illustrated in FIG. 7 .
  • the DeNB 103-1 illustrated in FIG. 7 includes, as illustrated in FIG. 9 , a UL SR/BSR receiving unit 110, a UL SR/BSR information accumulating unit 111, a UL transmission/reception candidate timing extracting unit 112, a UL Grant information accumulating unit 113, a UL transmission/reception establishment timing extracting unit 114, a UL opposing node determination unit 115, a UL Grant establishment timing providing unit 116, a UL Grant generation unit 117, and a UL Grant transmission unit 118.
  • FIG. 9 illustrates only structure elements concerning this example embodiment, of the structure elements that the DeNB 103-1 illustrated in FIG. 7 includes.
  • the DeNB 103-2 illustrated in FIG. 7 also includes the structure elements illustrated in FIG. 9 .
  • the UL SR/BSR receiving unit 110 receives the UL SR and the UL BSR sent from the RN 203 and outputs the UL SR and the UL BSR to the UL opposing node determination unit 115.
  • the UL SR/BSR information accumulating unit 111 accumulates a send feasible timing candidate for the UL BSR and reception feasible timing candidate information regarding the UL Grant that are contained in the UL SR that the UL SR/BSR receiving unit 110 has output. Furthermore, the UL SR/BSR information accumulating unit 111 accumulates a send feasible timing candidate for the UL Data and reception feasible timing candidate information regarding the UL Grant that are contained in the UL BSR that the UL SR/BSR receiving unit 110 has output.
  • the UL transmission/reception candidate timing extracting unit 112 extracts the send feasible timing candidate for the UL BSR and the reception feasible timing candidate information regarding the UL Grant that are accumulated in the UL SR/BSR information accumulating unit 111. Furthermore, the UL transmission/reception candidate timing extracting unit 112 extracts the send feasible timing candidate for the UL Data and the reception feasible timing candidate information regarding the UL Grant that are accumulated in the UL SR/BSR information accumulating unit 111.
  • the UL Grant information accumulating unit 113 accumulates the send timing of the UL BSR/UL Data and the reception timing information regarding the UL Grant that have already been sent from the UL Grant transmission unit 118.
  • the UL transmission/reception establishment timing extracting unit 114 extracts the send timing of the UL BSR/UL Data and the reception timing information regarding the UL Grant that are accumulated in the UL Grant information accumulating unit 113.
  • the UL opposing node determination unit 115 performs determination regarding an opposing node. Concretely, the UL opposing node determination unit 115 determines whether the opposing node connected to a lower order is the UE 300-1, 300-2 or the RN 203. In this example embodiment, because the structure elements illustrated in FIG. 9 are packaged in the DeNB 103-1, the UL opposing node determination unit 115 determines that the opposing node is the RN 203. On the other hand, in the case where the structure elements illustrated in FIG. 9 are packaged in the RN 203, the UL opposing node determination unit 115 determines that the opposing node is the UE 300-1 or 300-2.
  • the UL opposing node determination unit 115 has determined that the opposing node is the UE 300-1 or 300-2.
  • the UL Grant establishment timing providing unit 116 provides timings other than the timings extracted by the UL transmission/reception establishment timing extracting unit 114 as a reception timing of the UL Grant and a send timing of the UL BSR/UL Data.
  • the UL opposing node determination unit 115 has determined that the opposing node is the RN 203.
  • the UL Grant establishment timing providing unit 116 provides the timings extracted by the UL transmission/reception establishment timing extracting unit 114 and the UL transmission/reception candidate timing extracting unit 112 as a reception timing of the UL Grant and a send timing of the UL BSR/UL Data.
  • the UL Grant generation unit 117 based on the information provided by the UL Grant establishment timing providing unit 116, generates a UL Grant and outputs the UL Grant to the UL Grant transmission unit 118.
  • the UL Grant transmission unit 118 sends to the RN 203 the UL Grant that the UL Grant generation unit 117 has output.
  • FIG. 10 is a flowchart for describing an example of the transmission processing of the UL SR/UL BSR in the RN 203 illustrated in FIG. 7 , in the communication method in the communication system illustrated in FIG. 7 .
  • the UL opposing node determination unit 216 determines whether the opposing node is the DeNB 103-1 or a higher-order apparatus, such as SGW (step S22).
  • the UL opposing node flag providing unit 217 provides a DeNB flag (step S23).
  • the UL transmission establishment timing extracting unit 214 determines whether the UL Grant receiving unit 210 has received the UL Grant, that is, whether the UL Grant information accumulating unit 212 has accumulated UL Grant (step S24). When the UL Grant information accumulating unit 212 has accumulated the UL Grant, the UL transmission establishment timing extracting unit 214 removes the send timing of the Uplink that has already been allocated by the accumulated UL Grant (step S25).
  • step S24 when in the step S24, the UL Grant information accumulating unit 212 has not accumulated the UL Grant, the processing in step S25 is not performed.
  • the UL SR/BSR information accumulating unit 213 determines whether the UL SR transmission unit 223 has already sent the UL SR or whether the UL BSR transmission unit 221 has already sent the UL BSR (step S26). This determination utilizes the determination carried out by the UL SR/BSR information accumulating unit 213 as to whether the UL SR/BSR information accumulating unit 213 has accumulated the send timing information on the UL BSR and the reception timing information on the UL Grant, or, the send timing information on the UL Data and the reception timing information on the UL Grant.
  • the UL SR/BSR information accumulating unit 213 determines that the UL SR transmission unit 223 has already sent the UL SR. Furthermore, for example, when the UL SR/BSR information accumulating unit 213 has accumulated the send timing information on the UL Data and the reception timing information on the UL Grant, the UL SR/BSR information accumulating unit 213 determines that the UL BSR transmission unit 221 has already sent the UL BSR.
  • the UL transmission/reception candidate timing extracting unit 215, using the UL SR removes the UL Grant reception feasible timing and the Uplink send feasible timing that have been already notified. Furthermore, when the UL SR/BSR information accumulating unit 213 has determined that the UL BSR transmission unit 221 has already sent the UL BSR, the UL transmission/reception candidate timing extracting unit 215, using the UL BSR, removes the UL Grant reception feasible timing and the Uplink send feasible timing that have been already notified (step S27).
  • step S26 when, in step S26, the UL SR/BSR information accumulating unit 213 has determined that the UL SR transmission unit 223 has not already sent the UL SR or the UL BSR transmission unit 221 has not already sent the UL BSR, the processing in step S27 is not performed.
  • the UL transmission/reception feasible timing candidate providing unit 218 based on a result of the foregoing timing removal, provides a reception feasible timing candidate for the UL Grant and a send feasible timing candidate for the UL BSR that are to be contained in the UL SR.
  • the UL SR in which the provided timing information is contained is generated by the UL SR generating unit 222 and is sent to the DeNB 103-1 by the UL SR transmission unit 223.
  • the UL transmission/reception feasible timing candidate providing unit 218 based on a result of the foregoing timing removal, provides a send feasible timing candidate for the UL Data and a reception feasible timing candidate for the UL Grant. Then, the UL BSR in which the provided timing information is contained is generated by the UL BSR generating unit 220 and sent to the DeNB 103-1 by the UL BSR transmission unit 221 (step S28).
  • the UL opposing node determination unit 216 determines in step S22 that the opposing node is an SGW, so that the UL opposing node flag providing unit 217 provides an SGW flag (step S29). Then, the DeNB 103-1 sends the UL Data to the SGW (step S30).
  • FIG. 11 is a flowchart for describing an example of the transmission processing of the UL Grant in the DeNB 103-1 illustrated in FIG. 7 , in the communication method in the communication system illustrated in FIG. 7 .
  • step S42 it is determined whether the UL Grant transmission unit 118 has sent another UL Grant. For example, it may be determined whether the UL Grant transmission unit 118 has sent another UL Grant, based on whether the UL Grant information accumulating unit 113 has accumulated the reception timing information on the UL Grant already sent from the UL Grant transmission unit 118. Concretely, when the UL Grant information accumulating unit 113 has accumulated the reception timing information on the UL Grant already sent from the UL Grant transmission unit 118, it may be determined that the UL Grant transmission unit 118 has sent another UL Grant.
  • the UL transmission/reception establishment timing extracting unit 114 removes the send timing of the Uplink and the reception timing of the UL Grant already allocated in the UL Grant accumulated in the UL Grant information accumulating unit 113 (step S43).
  • step S42 when, in step S42, the UL Grant information accumulating unit 113 has not accumulated the UL Grant, the processing in step S43 is not performed.
  • the UL SR/BSR information accumulating unit 111 determines whether the UL SR/UL BSR received by the UL SR/BSR receiving unit 110 contains the UL Grant reception feasible timing and the Uplink send feasible timing (step S44).
  • the UL SR/BSR information accumulating unit 111 accumulates these timings.
  • the UL transmission/reception candidate timing extracting unit 112 extracts the UL Grant reception feasible timing and the Uplink send feasible timing accumulated in the UL SR/BSR information accumulating unit 111 (step S45).
  • the UL Grant establishment timing providing unit 116 determines whether the UL Grant can be sent at the timings extracted by the UL transmission/reception establishment timing extracting unit 114 and the UL transmission/reception candidate timing extracting unit 112 (step S46).
  • the UL Grant establishment timing providing unit 116 provides the timings as the reception timing of the UL Grant and the send timing of the UL BSR/UL Data.
  • the UL Grant generation unit 117 generates the UL Grant, based on information provided by the UL Grant establishment timing providing unit 116.
  • the UL Grant transmission unit 118 sends the UL Grant generated by the UL Grant generation unit 117 to the RN 203 (step S47).
  • step S44 when, in step S44, the UL SR/UL BSR received by the UL SR/BSR receiving unit 110 does not contain the UL Grant reception feasible timing and the Uplink send feasible timing, the UL Grant generation unit 117 generates a UL Grant. Subsequently, the UL Grant transmission unit 118 sends the UL Grant generated by the UL Grant generation unit 117 to the RN 203 (step S48).
  • step S46 the UL Grant establishment timing providing unit 116 determines that the UL Grant cannot be sent at the extracted timings.
  • the UL Grant establishment timing providing unit 116 provides timings other than the aforementioned timings as a reception timing of the UL Grant and a send timing of the UL BSR/UL Data.
  • the UL Grant generation unit 117 generates a UL Grant based on information provided by the UL Grant establishment timing providing unit 116.
  • the UL Grant transmission unit 118 sends the UL Grant generated by the UL Grant generation unit 117 to the RN 203 (step S49).
  • FIG. 12 is a flowchart for describing an example of the transmission processing of the UL Data in the RN 203 illustrated in FIG. 7 , in the communication method in the communication system illustrated in FIG. 7 .
  • the UL Grant receiving unit 210 receives a UL Grant sent from the DeNB 103-1 (step S51)
  • the UL Grant information accumulating unit 212 accumulates timing information contained in the received UL Grant.
  • the UL Data transmission feasibility determination unit 224 determines whether the UL Data can be sent, based on the timing information accumulated in the UL Grant information accumulating unit 212 (step S52). For example, the UL Data transmission feasibility determination unit 224 determines that the UL Data cannot be sent, when the timing information accumulated in the UL Grant information accumulating unit 212 is used for sending to another DeNB.
  • the UL Data transmission unit 226 sends the UL Data to the DeNB 103-1 at that timing (step S53).
  • step S52 when, in step S52, the UL Data transmission feasibility determination unit 224 determines that the UL Data cannot be sent at the timing received by the UL Grant receiving unit 210, the SR/BSR retransmission processing unit 225 performs the retransmission processing of the UL SR/BSR (step S54).
  • FIG. 13 is a sequence chart for describing an example of the flow of data in the communication system illustrated in FIG. 7 .
  • the UE 300-1 sends to the RN 203 an uplink scheduling request signal (UL SR_a) for sending to the DeNB 103-1 UL Data that are uplink data (step S61). Then, the RN 203 sends the response signal (UL Grant for SR_a) to the UE 300-1 (step S62). Subsequently, the UE 300-1 sends to the RN 203 an uplink buffer status-reporting signal (UL BSR_a) that indicates the storage status of a buffer that temporarily stores the UL Data (step S63). Then, the RN 203 sends the response signal (UL Grant for BSR_a) to the UE 300-1 (step S64). The UE 300-1, receiving the UL Grant for BSR_a, sends to the RN 203 the uplink data (UL Data_a) that is to be sent to the DeNB 103-1 (step S65).
  • UL SR_a uplink scheduling request signal
  • the RN 203 sends the response signal (UL Grant for SR
  • the RN 203 after receiving the UL Data_a from the UE 300-1, sends the UL SR_a to the DeNB 103-1 (step S66). At this time, the RN 203 sends the UL SR_a in which a timing at which a UL Grant for SR_a that is a response signal to the UL SR_a can be received and a timing at which a UL BSR_a can be sent are contained.
  • the UE 300-2 sends to the RN 203 an uplink scheduling request signal (UL SR_b) for sending to the DeNB 103-2 UL Data that are uplink data (step S67). Then, the RN 203 sends a response signal (UL Grant for SR_b) to the UE 300-2 (step S68). Subsequently, the UE 300-2 sends to the RN 203 an uplink buffer status-reporting signal (UL BSR_b) that indicates the storage status of a buffer that temporarily stores the UL Data (step S69). Then, the RN 203 sends a response signal (UL Grant for BSR_b) to the UE 300-2 (step S70). Receiving the UL Grant for BSR_b, the UE 300-2 sends to the RN 203 uplink data (UL Data_b) that are to be sent to the DeNB 103-2 (step S71).
  • UL SR_b uplink scheduling request signal
  • the RN 203 after receiving the UL Data_b from the UE 300-2, sends the UL SR_b to the DeNB 103-2 (step S72). At this time, the RN 203 sends the UL SR_b in which a timing at which a UL Grant for SR_b that is a response signal to the UL SR_b can be received and a timing at which a UL BSR_b can be sent are contained.
  • timing at which the UL Grant for SR_a can be received and which is sent in step S66 and the timing at which the UL Grant for SR_b can be received and which is sent in step S72 are timings such that the reception processing of one of the signals does not affect the reception processing of the other signal. This is just as stated above.
  • the timing at which the UL BSR_a can be sent and which is contained in the UL SR_a in step S66 and the timing at which the UL BSR_b can be sent and which is contained in the UL SR_b in step S72 are timings such that the transmission processing of one of the two signals does not affect the transmission processing of the other signal. This is also just as stated above.
  • the DeNB 103-1 sends the UL Grant for SR_a to the RN 203, based on the timing at which UL Grant for SR_a can be received and which is contained in the UL SR_a sent from the RN 203 (step S73). Furthermore, the DeNB 103-2 sends the UL Grant for SR_b to the RN 203, based on the timing at which the UL Grant for SR_b can be received and which is contained in the UL SR_b sent from the RN 203 (step S74).
  • the RN 203 sends the UL BSR_a to the DeNB 103-1 at the timing notified to the DeNB 103-1 in step S66 (step S75).
  • the RN 203 sends the UL BSR_a in which a timing at which the UL Grant for BSR_a, which is a response signal to the UL BSR_a, can be received and a timing at which the UL Data_a can be sent are contained.
  • the RN 203 sends the UL BSR_b to the DeNB 103-2 at the timing notified to the DeNB 103-2 in step S72 (step S76).
  • the RN 203 sends the UL BSR_b in which a timing at which the UL Grant for BSR_b, which is a response signal to the UL BSR_b, can be received and a timing at which the UL Data_b can be sent are contained.
  • the timing at which the UL Grant for BSR_a can be received and which is contained in the UL BSR_a in step S75 and the timing at which the UL Grant for BSR_b can be received and which is contained in the UL BSR_b in step S76 are timings such that the reception processing of one of the two signals does not affect the reception processing of the other signal. This is just as stated above. Furthermore, the timing at which the UL Data_a can be sent and which is contained in the UL BSR_a in step S75 and the timing at which the UL Data_b can be sent and which is contained in the UL BSR_b in step S76 are timings such that the transmission processing of one of the two signals does not affect the transmission processing of the other signal. This is also just as stated above.
  • the DeNB 103-1 sends the UL Grant for BSR_a to the RN 203, based on the timing at which the UL Grant for BSR_a can be received and which is contained in the UL BSR_a sent from the RN 203 (step S77). Furthermore, the DeNB 103-2 sends the UL Grant for BSR_b to the RN 203, based on the timing at which the UL Grant for BSR_b can be received and which is contained in the UL BSR_b sent from the RN 203 (step S78).
  • the RN 203 sends the UL Data_a to the DeNB 103-1 at the timing notified to the DeNB 103-1 in step S75 (step S79). Furthermore, the RN 203 sends the UL Data_b to the DeNB 103-2 at the timing notified to the DeNB 103-2 in step S76 (step S80).
  • the RN 203 notifies the DeNBs 103-1 and 103-2 of the timing at which the RN 203 can receive the response signal and the timing at which the RN 203 can send uplink data and then, at these timings, sends the request signal and the uplink data to the DeNBs 103-1 and 103-2. Therefore, the communication system of the third example embodiment can prevent failure in the reception processing of the response signal and failure in the transmission processing of uplink data and therefore can made data transmission more efficient.
  • FIG. 14 is a diagram illustrating a fourth example embodiment of the communication system of the present invention.
  • the communication system in this example embodiment includes DeNBs 104-1 and 104-2, an RN 205, and UEs 300-1 and 300-2 as illustrated in FIG. 14 .
  • the DeNB 104-1 is a radio base station that communicates with the UE 300-1 via the RN 205.
  • the DeNB 104-2 is a radio base station that communicates with the UE 300-2 via the RN 205.
  • the DeNBs 104-1 and 104-2 send downlink signals to the RN 205, using an orthogonal frequency-division multiplexing access method.
  • the RN 205 is a radio relay station that relays communication between the DeNB 104-1 and the UE 300-1 and communication between the DeNB 104-2 and the UE 300-2.
  • the UE 300-1 is a communication terminal that communicates with the DeNB 104-1 via the RN 205.
  • the UE 300-2 is a communication terminal that communicates with the DeNB 104-2 via the RN 205.
  • FIG. 15 is a diagram illustrating an example of an internal structure of the RN 205 illustrated in FIG. 14 .
  • the RN 205 illustrated in FIG. 14 includes, as illustrated in FIG. 15 , a DL SR/BSR receiving unit 231, a DL SR/BSR information accumulating unit 232, a DL transmission/reception candidate timing extracting unit 233, a DL Grant information accumulating unit 234, a DL transmission/reception establishment timing extracting unit 235, a DL Grant establishment timing providing unit 236, a DL Grant generation unit 237, and a DL Grant transmission unit 238.
  • FIG. 15 illustrates only structure elements concerning this example embodiment, of the structure elements that the RN 205 illustrated in FIG. 14 include.
  • the DL SR/BSR receiving unit 231 receives a downlink buffer status report (DL Buffer Status Report, referred to hereinafter as DL BSR) and a downlink scheduling information (DL Scheduling Request, referred to hereinafter as DL SR) sent from the DeNBs 104-1 and 104-2.
  • the DL SR/BSR receiving unit 231 outputs the DL SR and the DL BSR received to the DL SR/BSR information accumulating unit 232.
  • the DL SR/BSR information accumulating unit 232 accumulates a send feasible timing candidate for the DL BSR and reception feasible timing candidate information on a DL Grant that is a response signal to the DL SR which are contained in the DL SR output by the DL SR/BSR receiving unit 231.
  • the DL SR/BSR information accumulating unit 232 accumulates a send feasible timing candidate for downlink data (DL Data) and reception feasible timing candidate information on the DL Grant that is a response signal to the DL BSR which are contained in the DL BSR output by the DL SR/BSR receiving unit 231.
  • the DL transmission/reception candidate timing extracting unit 233 extracts from the DL SR/BSR information accumulating unit 232 the send feasible timing candidate for the DL BSR and the reception feasible timing candidate information for the DL Grant that is a response signal to the DL SR. Furthermore, the DL transmission/reception candidate timing extracting unit 233 extracts from the DL SR/BSR information accumulating unit 232 the send feasible timing candidate for the DL Data and the reception feasible timing candidate information on the DL Grant that is a response signal to the DL BSR.
  • the DL Grant information accumulating unit 234 accumulates the send timing of the DL BSR/DL Data and the reception timing information on the DL Grant that the DL Grant transmission unit 238 sends.
  • the DL transmission/reception establishment timing extracting unit 235 extracts the send timing of the DL SR/BSR and the reception timing information on the DL Grant from the DL Grant information accumulating unit 234.
  • the DL Grant establishment timing providing unit 236 provides the reception timing of the DL Grant and the send timing of the DL BSR/DL Data, based on the timings extracted by the DL transmission/reception establishment timing extracting unit 235 and the DL transmission/reception candidate timing extracting unit 233.
  • the DL Grant generation unit 237 generates the DL Grant based on the timing provided by the DL Grant establishment timing providing unit 236.
  • the DL Grant transmission unit 238 sends the DL Grant generated by the DL Grant generation unit 237 to the DeNBs 104-1 and 104-2.
  • FIG. 16 is a diagram illustrating an example of an internal structure of the DeNB 104-1 illustrated in FIG. 14 .
  • the DeNB 104-1 illustrated in FIG. 14 includes a transmission unit 105 and a DL Data receiving unit 131 as illustrated in FIG. 16 .
  • the transmission unit 105 includes a DL Grant receiving unit 130, a DL Grant information accumulating unit 132, a DL SR/BSR information accumulating unit 133, a DL transmission establishment timing extracting unit 134, a DL transmission/reception candidate timing extracting unit 135, a DL opposing node determination unit 136, a DL opposing node flag providing unit 137, a DL transmission/reception feasible timing candidate providing unit 138, a DL SR/BSR determination unit 139, a DL BSR generating unit 140, a DL BSR transmission unit 141, a DL SR generating unit 142, a DL SR transmission unit 143, a DL Data transmission feasibility determination unit 144, an SR/BSR retransmission processing unit 145, and a DL Data transmission unit 146.
  • the DL Data receiving unit 131 receives downlink data (DL Data) sent from a higher-order apparatus such as an SGW.
  • the DL Data receiving unit 131 outputs the received DL Data to the DL opposing node determination unit 136.
  • the DL Grant receiving unit 130 receives the DL Grant sent from the RN 205.
  • the DL Grant receiving unit 130 outputs the received DL Grant to the DL Grant information accumulating unit 132.
  • the DL Grant information accumulating unit 132 accumulates the DL Grant output by the DL Grant receiving unit 130.
  • the DL SR/BSR information accumulating unit 133 accumulates send timing information on the DL BSR and reception timing information on the DL Grant that are contained in a DL SR already sent by the DL SR transmission unit 143. Furthermore, the DL SR/BSR information accumulating unit 133 accumulates send timing information on the DL Data and reception timing information on the DL Grant that are contained in a DL BSR already sent from the DL BSR transmission unit 141.
  • the DL transmission establishment timing extracting unit 134 extracts a send timing candidate for the DL BSR that is to be contained in the DL SR, by using the DL Grant accumulated in the DL Grant information accumulating unit 132. Furthermore, the DL transmission establishment timing extracting unit 134 extracts a send feasible timing candidate for the DL Data that are to be contained in the DL BSR, by using the DL Grant accumulated in the DL Grant information accumulating unit 132.
  • the DL transmission/reception candidate timing extracting unit 135 refers to the send timing candidate for the DL BSR and the reception timing for the DL Grant that are contained in the DL SR accumulated in the DL SR/BSR information accumulating unit 133. Furthermore, the DL transmission/reception candidate timing extracting unit 135 refers to the send timing candidate for the DL Data and the reception timing of the DL Grant that are contained in the DL BSR accumulated in the DL SR/BSR information accumulating unit 133.
  • the DL transmission/reception candidate timing extracting unit 135 extracts, from these timings referred to, the send timing candidates for the next DL BSR/DL Data that can be sent in the DL SR/BSR and the reception timing candidate for receiving the DL Grant for sending the DL BSR/DL Data.
  • the DL opposing node determination unit 136 determines an opposing node. Concretely, the DL opposing node determination unit 136 determines whether the opposing node is the RN 205 or the UE 300-1 or 300-2. In this example embodiment, because the transmission unit 105 is packaged in the DeNB 104-1, the DL opposing node determination unit 136 determines that the opposing node is the RN 205. On the other hand, in the case where the transmission unit 105 is packaged in the RN 205, the DL opposing node determination unit 136 determines that the opposing node is the UE 300-1 or 300-2.
  • the DL opposing node flag providing unit 137 provides a flag according to a result of the determination performed by the DL opposing node determination unit 136.
  • the DL transmission/reception feasible timing candidate providing unit 138 provides a send feasible timing candidate for the DL BSR and a reception feasible timing candidate for the DL Grant that are to be contained in the DL SR. These are accomplished based on the information extracted by the DL transmission/reception candidate timing extracting unit 135 and the DL transmission establishment timing extracting unit 134.
  • the DL transmission/reception feasible timing candidate providing unit 138 provides a send feasible timing candidate for the DL Data and a reception feasible timing candidate for the DL Grant that are to be contained in the DL BSR. These are accomplished based on the information extracted by the DL transmission/reception candidate timing extracting unit 135 and the DL transmission establishment timing extracting unit 134.
  • the DL SR/BSR determination unit 139 determines which one of the DL SR and the DL BSR is the next signal to be sent based on the DL Grant.
  • the DL BSR generating unit 140 generates the DL BSR in which the foregoing timing information is contained, when the DL SR/BSR determination unit 139 has determined that the next signal to be sent is the DL BSR.
  • the DL BSR transmission unit 141 is a downlink buffer status-reporting signal transmission unit that sends the DL BSR generated by the DL BSR generating unit 140 to the RN 205.
  • the DL BSR transmission unit 141 when sending the DL BSR to the RN 205, sends the DL BSR in which information that indicates a timing at which the DL Grant for the DL BSR can be received and information that indicates a timing at which the DL Data can be sent to the RN 205 are contained.
  • the DL SR generating unit 142 when the DL SR/BSR determination unit 139 has determined that the next signal to be sent is the DL SR, generates the DL SR in which the foregoing timing information is contained.
  • the DL SR transmission unit 143 is a downlink scheduling request signal transmission unit that sends the DL SR generated by the DL SR generating unit 142 to the RN 205.
  • the DL SR transmission unit 143 when sending the DL SR to the RN 205, sends the DL SR in which information that indicates a timing at which the DL Grant for the DL SR can be received and information that indicates a timing at which the DL BSR can be sent to the RN 205 are contained.
  • the DL Data transmission feasibility determination unit 144 determines whether the sending of the DL Data is feasible, based on the DL Grant accumulated in the DL Grant information accumulating unit 132. Concretely, the DL Data transmission feasibility determination unit 144 determines whether the sending of the DL Data is feasible based on the send timing notified in the DL Grant accumulated in the DL Grant information accumulating unit 132.
  • the SR/BSR retransmission processing unit 145 performs the retransmission processing of the DL SR and the DL BSR when the DL Data transmission feasibility determination unit 144 has determined that the DL Data cannot be sent.
  • the DL Data transmission unit 146 sends the DL Data to the RN 205.
  • FIG. 17 is a flowchart for describing an example of the transmission processing of the DL SR/DL BSR in the DeNB 104-1 illustrated in FIG. 14 , in the communication method in the communication system illustrated in FIG. 14 .
  • the DL opposing node determination unit 136 determines which one of the RN 205 and the UE 300-1 is the opposing node (step S92).
  • the DL opposing node flag providing unit 137 provides an RN flag (step S93).
  • step S94 it is determined whether the DL Grant receiving unit 130 has received the DL Grant, that is, whether the DL Grant information accumulating unit 132 has accumulated the DL Grant.
  • the DL transmission establishment timing extracting unit 134 removes the send timing of the Downlink already allocated in the accumulated DL Grant (step S95).
  • step S94 when, in step S94, the DL Grant information accumulating unit 132 has not accumulated the DL Grant, the processing in step S95 is not performed.
  • the DL SR/BSR information accumulating unit 133 determines whether the DL SR transmission unit 143 has already sent the DL SR or whether the DL BSR transmission unit 141 has already sent the DL BSR (step S96). This determination utilizes the determination carried out by the DL SR/BSR information accumulating unit 133 as to whether the DL SR/BSR information accumulating unit 133 has accumulated the send timing information on the DL BSR and the reception timing information on the DL Grant or the send timing information on the DL Data and the reception timing information on the DL Grant.
  • the DL SR/BSR information accumulating unit 133 determines that the DL SR transmission unit 143 has already sent the DL SR.
  • the DL SR/BSR information accumulating unit 133 has accumulated the send timing information on the DL Data and the reception timing information on the DL Grant. In this case, the DL SR/BSR information accumulating unit 133 determines that the DL BSR transmission unit 141 has already sent the DL BSR.
  • the DL transmission/reception candidate timing extracting unit 135 removes the DL Grant reception feasible timing and the Downlink send feasible timing that have been already notified by using the DL SR.
  • the DL transmission/reception candidate timing extracting unit 135 removes the DL Grant reception feasible timing and the Downlink send feasible timing that have been already notified by using the DL BSR (step S97).
  • step S96 when, in step S96, the DL SR/BSR information accumulating unit 133 determines that the DL SR transmission unit 143 has not already sent the DL SR or the DL BSR transmission unit 141 has not already sent the DL BSR, the processing in step S97 is not performed.
  • the DL transmission/reception feasible timing candidate providing unit 138 when the signal to be sent is the DL SR, the DL transmission/reception feasible timing candidate providing unit 138, based on a result of the foregoing timing removal, provides a send feasible timing candidate for the DL BSR and a reception feasible timing candidate for the DL Grant that are to be contained in the DL SR. Then, the DL SR in which the provided timing information is contained is generated by the DL SR generating unit 142 and sent to the RN 205 by the DL SR transmission unit 143.
  • the DL transmission/reception feasible timing candidate providing unit 138 when the signal to be sent is the DL BSR, the DL transmission/reception feasible timing candidate providing unit 138, based on a result of the foregoing timing removal, provides a send feasible timing candidate for the DL Data and a reception feasible timing candidate for the DL Grant. Then, the DL BSR in which the provided timing information is contained is generated by the DL BSR generating unit 140 and sent to the RN 205 by the DL BSR transmission unit 141 (step S98).
  • the DL opposing node determination unit 136 determines in step S92 that the opposing node is the UE 300-1. Therefore, the DL opposing node flag providing unit 137 provides a UE flag (step S99). Then, the RN 205 sends the DL Data to the UE 300-1 (step S100).
  • FIG. 18 is a flowchart for describing an example of the transmission processing of the DL Grant in the RN 205 illustrated in FIG. 14 , in the communication method in the communication system illustrated in FIG. 14 .
  • the DL Grant information accumulating unit 234 may determine whether the DL Grant transmission unit 238 has sent another DL Grant, based on whether the DL Grant information accumulating unit 234 has accumulated the reception timing information on the DL Grant already sent from the DL Grant transmission unit 238.
  • the DL Grant information accumulating unit 234 may determine that the DL Grant transmission unit 238 has sent another DL Grant, when the DL Grant information accumulating unit 234 has accumulated the reception timing information on the DL Grant already sent from the DL Grant transmission unit 238.
  • step S112 it is determined that the DL Grant transmission unit 238 has sent another DL Grant.
  • the DL transmission/reception establishment timing extracting unit 235 removes the reception timing for the DL Grant and the send timing for the Downlink that have been already allocated in the DL Grant accumulated in the DL Grant information accumulating unit 234 (step S113).
  • step S112 when, in step S112, the DL Grant information accumulating unit 234 has not accumulated the DL Grant, the processing in step S113 is not performed.
  • the DL SR/BSR information accumulating unit 232 determines whether the DL SR/DL BSR received by the DL SR/BSR receiving unit 231 contains the DL Grant reception feasible timing and the Downlink send feasible timing (step S114).
  • the DL SR/BSR information accumulating unit 232 accumulates these timings.
  • the DL transmission/reception candidate timing extracting unit 233 extracts the DL Grant reception feasible timing and the Downlink send feasible timing accumulated in the DL SR/BSR information accumulating unit 232 (step S115).
  • the DL Grant establishment timing providing unit 236 determines whether the DL Grant can be sent at the timings extracted by the DL transmission/reception establishment timing extracting unit 235 and the DL transmission/reception candidate timing extracting unit 233 (step S116). When the DL Grant establishment timing providing unit 236 determines that the DL Grant can be sent at the extracted timings, the DL Grant establishment timing providing unit 236 provides these timings as the reception timing for the DL Grant and the send timing for the DL BSR/DL Data. Then, the DL Grant generation unit 237 generates the DL Grant based on the information provided by the DL Grant establishment timing providing unit 236. Subsequently, the DL Grant transmission unit 238 sends the DL Grant generated by the DL Grant generation unit 237 to the DeNB 104-1 (step S117).
  • step S114 the DL SR/DL BSR received by the DL SR/BSR receiving unit 231 does not contain the DL Grant reception feasible timing and the Downlink send feasible timing.
  • the DL Grant generation unit 237 generates a DL Grant.
  • the DL Grant transmission unit 238 sends the DL Grant generated by the DL Grant generation unit 237 to the DeNB 104-1 (step S118).
  • step S116 the DL Grant establishment timing providing unit 236 determines that the DL Grant cannot be sent at the extracted timings.
  • the DL Grant establishment timing providing unit 236 provides timings other than these timings as a reception timing for the DL Grant and a send timing for the DL BSR/DL Data.
  • the DL Grant generation unit 237 generates a DL Grant based on the information provided by the DL Grant establishment timing providing unit 236.
  • the DL Grant transmission unit 238 sends the DL Grant generated by the DL Grant generation unit 237 to the DeNB 104-1 (step S119).
  • FIG. 19 is a flowchart for describing an example of the transmission processing of the DL Data in DeNB 104-1 illustrated in FIG. 14 , in the communication method in the communication system illustrated in FIG. 14 .
  • the DL Grant information accumulating unit 132 accumulates the timing information contained in the received DL Grant. Subsequently, the DL Data transmission feasibility determination unit 144 determines whether the DL Data can be sent, based on the timing information accumulated by the DL Grant information accumulating unit 132 (step S122). For example, the DL Data transmission feasibility determination unit 144 determines that the DL Data cannot be sent, when the timing information accumulated in the DL Grant information accumulating unit 132 is used for sending to another RN. When the DL Data transmission feasibility determination unit 144 determines that the DL Data can be sent at the timing received by the DL Grant receiving unit 130, the DL Data transmission unit 146 sends the DL Data to the RN 205 at that timing (step S123).
  • step S122 when, in step S122, the DL Data transmission feasibility determination unit 144 determines that the DL Data cannot be sent at the timing received by the DL Grant receiving unit 130, the SR/BSR retransmission processing unit 145 performs the retransmission processing of the DL SR/BSR (step S124).
  • FIG. 20 is a sequence chart for describing an example of the flow of data in the communication system illustrated in FIG. 14 .
  • the DeNB 104-1 after receiving downlink data from a higher-order apparatus, such as an SGW, sends a DL SR_a to the RN 205 (step S131). At this time, the DeNB 104-1 sends the DL SR_a in which a timing at which the DL Grant for SR_a that is a response signal to the DL SR_a can be received and a timing at which the DL BSR_a can be sent are contained.
  • the DeNB 104-2 after receiving downlink data from a higher-order apparatus, such as SGW, sends a DL SR_b to the RN 205 (step S132). At this time, the DeNB 104-2 sends the DL SR_b in which a timing at which the DL Grant for SR_b that is a response signal to the DL SR_b can be received and a timing at which the DL BSR_b can be sent are contained.
  • the RN 205 sends the DL Grant for SR_a, which is a response signal to the DL SR_a, to the DeNB 104-1 at the reception feasible timing contained in the DL SR_a sent from the DeNB 104-1 (step S133). Furthermore, the RN 205 sends the DL Grant for SR_b, which is a response signal to the DL SR_b, to the DeNB 104-2 at the reception feasible timing contained in the DL SR_b sent from the DeNB 104-2 (step S134).
  • the RN 205 may change the reception timings for the DL Grant for SR_a and the DL Grant for SR_b to timings other than the timings contained in the DL SR_a and the DL SR_b. In this case, the RN 205 may also change the send timings for the DL BSR_a and the DL BSR_b to different timings.
  • the RN 205 may generate the DL Grant for SR_a and the DL Grant for SR_b and sent them to the DeNB 104-1, based on these changed timings. These operations correspond to the processing in step S119 in FIG. 18 .
  • the DeNB 104-1 sends the DL BSR_a to the RN 205 at the send feasible timing for the DL BSR_a that is contained in the DL SR_a that the DeNB 104-1 has sent (step S135).
  • the DeNB 104-1 sends the DL BSR_a in which a reception feasible timing for a DL Grant for BSR_a that is a response signal to the DL BSR_a and a send feasible timing for the DL Data_a are contained.
  • the DeNB 104-2 sends the DL BSR_b to the RN 205 at the send feasible timing for the DL BSR_b that is contained in the DL SR_b that the DeNB 104-2 has sent (step S136). At this time, the DeNB 104-2 sends the DL BSR_b in which a reception feasible timing for the DL Grant for BSR_b that is a response signal to the DL BSR_b and a send feasible timing for the DL Data_b are contained.
  • the RN 205 sends the DL Grant for BSR_a, which is a response signal to the DL BSR_a, to the DeNB 104-1 at the reception feasible timing contained in the DL BSR_a sent from the DeNB 104-1 (step S137). Furthermore, the RN 205 sends the DL Grant for BSR_b, which is a response signal to the DL BSR_b, to the DeNB 104-2 at the reception feasible timing contained in the DL BSR_b sent from the DeNB 104-2 (step S138).
  • the DeNB 104-1 sends the DL Data_a to the RN 205 at the send feasible timing for the DL Data_a contained in the DL BSR_a that has been sent (step S139).
  • the RN 205 after receiving the DL Data_a sent from the DeNB 104-1, sends the DL Data_a to the UE 300-1 (step S140).
  • the DeNB 104-2 sends the DL Data_b to the RN 205 at the send feasible timing for the DL Data_b contained in the DL BSR_b that has been sent (step S141).
  • the RN 205 after receiving the DL Data_b sent from the DeNB 104-2, sends the DL Data_b to the UE 300-2 (step S142).
  • each of the DeNBs 104-1 and 104-2 notifies the RN 205 of a timing at which the DeNB can receive a response signal and a timing at which the DeNB can send downlink data and then, at these timings, sends the request signal and the downlink data to the RN 205. Therefore, the communication system of the fourth example embodiment can be prevent failure in the reception processing of the response signal and failure in the transmission processing of the downlink data and therefore can make data transmission more efficient.
  • a first advantageous effect is that because of having the functions of sending and receiving the DL SR, the DL BSR, and the DL Grant, the example embodiments can negotiate the timing to send DL Data not only with higher-order radio base station apparatuses but also with lower-order radio relay base station apparatuses. Furthermore, the DL SR and the DL BSR can be provided with a send feasible timing for the next Downlink communication (DL BSR and DL Data) and a reception timing for the DL Grant.
  • a reason for that is that the negotiation for the timing to send DL Data between nodes makes it possible to prevent DL Data from being received at the same timing.
  • a second advantageous effect is that the UL SR and the UL BSR are provided with a send feasible timing for the next Uplink communication (UL BSR and UL Data) and a reception timing for a UL Grant.
  • a reason for that is that the negotiation for the timing to send UL Data between nodes makes it possible to prevent UL Data from being received at the same timing.
  • a third advantageous effect is that, using the DL opposing node determination unit, it can be determined whether to perform a method of sending DL Data as in the related art or the sending of a DL SR or the like, according to an opposing node.
  • a reason for that is that because while a radio relay base station apparatus has a plurality of higher-order radio base station apparatuses, communication with a radio communication terminal involves a DeNB or a higher-order RN that is uniquely determined, an unnecessary radio scheduling function can be excluded.
  • a fourth advantageous effect is that, using the UL opposing node determination unit, it can be determined whether to perform a method of sending UL Data as in the related art or the sending of a UL SR or the like, according to an opposing node.
  • a reason for that is that because while a radio relay base station apparatus has a plurality of higher-order radio base station apparatuses, communication with an SGW or the like involves a high-order node that is uniquely determined, an unnecessary radio scheduling function can be excluded.
  • the case of sharing a radio base station apparatus in an MVNO (Mobile Virtual Network Operator) system or the like among a plurality of operators and performing the RAN (Radio Access Network) sharing including RNs will lead a better radio resource.
  • MVNO Mobile Virtual Network Operator
  • RAN Radio Access Network

Landscapes

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

Claims (6)

  1. Procédé de communication dans un réseau de radiocommunication dans lequel une station de relai radio (203) est prévue entre une pluralité de terminaux de communication (300-1, 300-2) et une pluralité de stations de base radio (103-1, 103-2), et relaie une communication entre un terminal de communication (300-1 ou 300-2) et une station de base radio (103-1 ou 103-2), ledit procédé comprenant :
    lorsqu'une donnée de liaison montante provenant du terminal de communication (300) a été reçue au niveau de la station de relai radio (203), l'envoi d'un signal de demande d'ordonnancement de liaison montante de la station de relai radio (203) à la station de base radio (103) avec des informations de synchronisation, qui indiquent une première synchronisation à laquelle un premier signal d'autorisation, correspondant au signal de demande d'ordonnancement de liaison montante, peut être reçu et une deuxième synchronisation à laquelle un signal de rapport de statut de mémoire tampon de liaison montante peut être envoyé ;
    lorsque le premier signal d'autorisation a été reçu selon la première synchronisation, l'envoi du signal de rapport de statut de mémoire tampon de liaison montante sur la base de la deuxième synchronisation de la station de relai radio (203) à la station de base radio (103) avec des informations de synchronisation, qui indiquent une troisième synchronisation à laquelle un deuxième signal d'autorisation, correspondant au signal de rapport de statut de mémoire tampon de liaison montante, peut être reçu et une quatrième synchronisation à laquelle la donnée de liaison montante peut être envoyée ; et
    lorsque le deuxième signal d'autorisation a été reçu selon la troisième synchronisation, l'envoi de la donnée de liaison montante sur la base de la quatrième synchronisation de la station de relai radio (203) à la station de base radio (103),
    dans lequel la première synchronisation et la troisième synchronisation sont des synchronisations qui n'affectent pas des traitements de réception dans la station de relai radio (203) pour une autre communication réalisée en même temps, et
    dans lequel la deuxième synchronisation et la quatrième synchronisation sont des synchronisations qui n'affectent pas des traitements de transmission dans la station de relai radio (203) pour une autre communication réalisée en même temps.
  2. Procédé de communication selon la revendication 1, comprenant en outre :
    la génération, au niveau de la station de base radio (103), du premier signal d'autorisation avec des informations sur la deuxième synchronisation contenue dans le signal de demande d'ordonnancement de liaison montante reçu depuis la station de relai radio (203) ;
    l'envoi du premier signal d'autorisation généré à la station de relai radio (203) sur la base de la première synchronisation contenue dans le signal de demande d'ordonnancement de liaison montante reçu depuis la station de relai radio (203) ;
    la génération, au niveau de la station de base radio (103), du deuxième signal d'autorisation avec des informations sur la quatrième synchronisation contenue dans le signal de rapport de statut de mémoire tampon de liaison montante reçu depuis la station de relai radio (203) ; et
    l'envoi du deuxième signal d'autorisation généré à la station de relai radio (203) sur la base de la troisième synchronisation contenue dans le signal de rapport de statut de mémoire tampon de liaison montante reçu depuis la station de relai radio (203).
  3. Procédé de communication selon la revendication 2, comprenant en outre :
    le fait de déterminer si la donnée de liaison montante peut être envoyée à la station de base radio (103) sur la base de la quatrième synchronisation contenue dans le deuxième signal d'autorisation reçu ; et
    la détermination que la donnée de liaison montante ne peut pas être envoyée lorsque la quatrième synchronisation est utilisée pour un traitement de transmission dans la station de relai radio (203) pour une autre communication, et la réalisation d'un traitement de retransmission.
  4. Système de communication d'un réseau de radiocommunication dans lequel une station de relai radio (203) est prévue entre une pluralité de terminaux de communication (300-1, 300-2) et une pluralité de stations de base radio (103-1, 103-2), et relaie une communication entre un terminal de communication (300-1 ou 300-2) et une station de base radio (103-1 ou 103-2), ladite station de relai radio (203) comprenant :
    un moyen de transmission de signal de demande d'ordonnancement de liaison montante (218, 219, 222, 223) qui est adapté, lorsqu'une donnée de liaison montante provenant du terminal de communication (300) a été reçue, pour envoyer un signal de demande d'ordonnancement de liaison montante à la station de base radio (103) avec des informations de synchronisation, qui indiquent une première synchronisation à laquelle un premier signal d'autorisation, correspondant au signal de demande d'ordonnancement de liaison montante, peut être reçu et une deuxième synchronisation à laquelle un signal de rapport de statut de mémoire tampon de liaison montante peut être envoyé ;
    un moyen de transmission de signal de rapport de statut de mémoire tampon de liaison montante (218, 219, 220, 221) qui est adapté, lorsque le premier signal d'autorisation a été reçu selon la première synchronisation, pour envoyer le signal de rapport de statut de mémoire tampon de liaison montante sur la base de la deuxième synchronisation à la station de base radio (103) avec des informations de synchronisation, qui indiquent une troisième synchronisation à laquelle un deuxième signal d'autorisation, correspondant au signal de rapport de statut de mémoire tampon de liaison montante, peut être reçu et une quatrième synchronisation à laquelle la donnée de liaison montante peut être envoyée ; et
    un moyen de transmission de donnée de liaison montante (224, 225, 226) qui est adapté, lorsque le deuxième signal d'autorisation a été reçu selon la troisième synchronisation, pour envoyer la donnée de liaison montante sur la base de la quatrième synchronisation à la station de base radio (103),
    dans lequel la première synchronisation et la troisième synchronisation sont des synchronisations qui n'affectent pas des traitements de réception dans la station de relai radio (203) pour une autre communication réalisée en même temps, et
    dans lequel la deuxième synchronisation et la quatrième synchronisation sont des synchronisations qui n'affectent pas des traitements de transmission dans la station de relai radio (203) pour une autre communication réalisée en même temps.
  5. Système de communication selon la revendication 4, dans lequel la station de base radio (103) comprend :
    un moyen de transmission de signal d'autorisation (116, 117, 118) qui est adapté pour générer le premier signal d'autorisation avec des informations sur la deuxième synchronisation contenue dans le signal de demande d'ordonnancement de liaison montante reçu depuis la station de relai radio (203), et pour envoyer le premier signal d'autorisation généré à la station de relai radio (203) sur la base de la première synchronisation contenue dans le signal de demande d'ordonnancement de liaison montante reçu depuis la station de relai radio (203), et
    adapté pour générer le deuxième signal d'autorisation avec des informations sur la quatrième synchronisation contenue dans le signal de rapport de statut de mémoire tampon de liaison montante reçu depuis la station de relai radio (203), et pour envoyer le deuxième signal d'autorisation généré à la station de relai radio (203) sur la base de la troisième synchronisation contenue dans le signal de rapport de statut de mémoire tampon de liaison montante reçu depuis la station de relai radio (203).
  6. Système de communication selon la revendication 5, dans lequel le moyen de transmission de donnée de liaison montante (224, 225, 226) comporte,
    un moyen de détermination qui est adapté pour déterminer si la donnée de liaison montante peut être envoyée à la station de base radio (103) sur la base de la quatrième synchronisation contenue dans le deuxième signal d'autorisation reçu, et adapté pour déterminer que la donnée de liaison montante ne peut pas être envoyée et qu'un traitement de retransmission doit être réalisé lorsque la quatrième synchronisation est utilisée pour un traitement de transmission dans la station de relai radio (203) pour une autre communication.
EP15849906.1A 2014-10-15 2015-10-09 Système de communication et procédé de communication Active EP3209047B1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2014210873 2014-10-15
PCT/JP2015/005127 WO2016059782A1 (fr) 2014-10-15 2015-10-09 Station relais de base, station radio fixe, système de communication et procédé de communication

Publications (3)

Publication Number Publication Date
EP3209047A1 EP3209047A1 (fr) 2017-08-23
EP3209047A4 EP3209047A4 (fr) 2018-06-20
EP3209047B1 true EP3209047B1 (fr) 2020-01-01

Family

ID=55746343

Family Applications (1)

Application Number Title Priority Date Filing Date
EP15849906.1A Active EP3209047B1 (fr) 2014-10-15 2015-10-09 Système de communication et procédé de communication

Country Status (6)

Country Link
US (1) US10278199B2 (fr)
EP (1) EP3209047B1 (fr)
JP (1) JP6399099B2 (fr)
CN (1) CN107113629A (fr)
AU (1) AU2015331962B2 (fr)
WO (1) WO2016059782A1 (fr)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3324679A4 (fr) * 2015-08-12 2018-08-08 Huawei Technologies Co., Ltd. Procédé de transmission de données, équipement d'utilisateur, et station de base
GB2562220A (en) * 2017-05-05 2018-11-14 Tcl Communication Ltd Methods and devices associated with direct communications in a radio access network
JP6977187B2 (ja) * 2019-02-14 2021-12-08 京セラ株式会社 通信制御方法

Family Cites Families (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1804535B1 (fr) * 2004-09-17 2011-11-16 Ntt Docomo, Inc. Station mobile, systeme de communication mobile et procede de communication mobile
EP1852987A4 (fr) 2005-03-18 2012-01-18 Panasonic Corp Appareil de station mobile et procede de communication sans fil
US20080045145A1 (en) * 2006-08-17 2008-02-21 Fujitsu Limited Radio Relay Communication Method, Radio Base Station, and Radio Relay Station in Radio Communication System
JP4907260B2 (ja) * 2006-08-18 2012-03-28 富士通株式会社 無線中継システム、無線中継局装置及び無線通信方法
RU2419981C2 (ru) * 2006-10-25 2011-05-27 Фудзицу Лимитед Базовая радиостанция, ретрансляционная станция, система радиосвязи и способ радиосвязи
KR100964192B1 (ko) 2008-01-15 2010-06-17 한국전자통신연구원 중계국의 전송 타이밍 설정 방법
US8576714B2 (en) * 2009-05-29 2013-11-05 Futurewei Technologies, Inc. System and method for relay node flow control in a wireless communications system
CN101932007B (zh) * 2009-06-22 2014-02-26 中兴通讯股份有限公司 一种实现移动终端业务流传输的方法及无线中继系统
US9655138B2 (en) * 2010-04-01 2017-05-16 Telefonaktiebolaget Lm Ericsson (Publ) System and method for scheduling wireless transmissions
US8543054B2 (en) * 2010-05-03 2013-09-24 Telefonaktiebolaget L M Ericsson (Publ) Method and apparatus for uplink scheduling using relays
JP5454792B2 (ja) * 2010-06-21 2014-03-26 株式会社Ｎｔｔドコモ 無線中継局装置及び無線中継方法
CN102026313B (zh) * 2010-06-21 2012-03-21 华为技术有限公司 切换处理方法和设备
JP5647453B2 (ja) * 2010-07-20 2014-12-24 京セラ株式会社 無線通信システム、無線中継局、無線端末、及び通信制御方法
WO2012093428A1 (fr) * 2011-01-05 2012-07-12 日本電気株式会社 Dispositif de nœud relais, système de communication et procédé de réduction du brouillage utilisé à cet effet
EP2704497B1 (fr) 2011-04-27 2018-12-19 Panasonic Intellectual Property Corporation of America Dispositif d'émission, dispositif de réception, procédé d'émission et procédé de réception
US8576766B2 (en) * 2011-08-29 2013-11-05 Telefonaktiebolaget L M Ericsson (Publ) Dynamic scheduling of in-band relay node resources
US9351160B2 (en) * 2012-05-07 2016-05-24 Telefonaktiebolaget L M Ericsson (Publ) Base station and method in relay node mobility
JP5851025B2 (ja) * 2012-05-14 2016-02-03 株式会社日立製作所 無線基地局、無線通信ネットワークシステム、及び通信制御方法

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
None *

Also Published As

Publication number Publication date
US20170311338A1 (en) 2017-10-26
EP3209047A1 (fr) 2017-08-23
AU2015331962A1 (en) 2017-04-27
WO2016059782A1 (fr) 2016-04-21
AU2015331962B2 (en) 2018-05-10
EP3209047A4 (fr) 2018-06-20
JP6399099B2 (ja) 2018-10-03
US10278199B2 (en) 2019-04-30
JPWO2016059782A1 (ja) 2017-07-27
CN107113629A (zh) 2017-08-29

Similar Documents

Publication Publication Date Title
CN112368988B (zh) 在集成接入及回程系统中进行动态路由选择
CN110636628B (zh) 信息传输方法及装置
EP3089511B1 (fr) Système de communication mobile, station de base, processeur et terminal utilisateur
EP3270622A1 (fr) Équipement utilisateur et dispositif de communication sans fil
TWI426807B (zh) 基地台、中繼台及其後端控制通訊方法
US8792422B2 (en) Transferring method, relay station and base station for uplink feedback information in relay link
JP2022548782A (ja) ハンドオーバに関与するユーザ機器および基地局
US20230171826A1 (en) Feedback and traffic differentiation in sidelink relays
US20120243462A1 (en) Transmission in a communication system using relay nodes
CN109314988B (zh) 上行数据传输方法、装置、设备及系统
EP3656164A1 (fr) Procédé et système de gestion de l'interférence d'ue à ue dans un réseau de télécommunication mobile
US20230171036A1 (en) Feedback and traffic differentiation in sidelink relays
EP3685624B1 (fr) Procédés et dispositifs d'accès au réseau
JP7291763B2 (ja) 通信制御方法
CN107113821B (zh) 上行数据传输的方法和装置
EP3101977A1 (fr) Système de communication mobile et terminal d'utilisateur
EP3209047B1 (fr) Système de communication et procédé de communication
EP3179814A1 (fr) Appareil et procédé d'établissement de liaison de transmission de données et système de communication
EP4055875A1 (fr) Rapport basé sur un seuil à des fins de prise en charge de commande d'admission efficace de réseaux sans fil
US8855640B2 (en) Partitioning resources on a target side of a handover of a user equipment based on data traffic indication
CN108886424B (zh) 数据传输方法、设备及系统
CN115150965A (zh) 数据调度方法、装置及设备
JP2022189090A (ja) 制御装置、基地局、制御方法、及びプログラム
CN115915462A (zh) 信道接入优先级capc的确定方法和网络侧设备
EP4349042A1 (fr) Flux de qualité de service hybride

Legal Events

Date Code Title Description
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE

PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20170515

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME

DAV Request for validation of the european patent (deleted)
DAX Request for extension of the european patent (deleted)
A4 Supplementary search report drawn up and despatched

Effective date: 20180518

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 72/04 20090101AFI20180514BHEP

Ipc: H04W 72/12 20090101ALI20180514BHEP

REG Reference to a national code

Ref country code: DE

Ref legal event code: R079

Ref document number: 602015044892

Country of ref document: DE

Free format text: PREVIOUS MAIN CLASS: H04W0016260000

Ipc: H04W0072040000

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: GRANT OF PATENT IS INTENDED

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 84/04 20090101ALN20190705BHEP

Ipc: H04W 72/04 20090101AFI20190705BHEP

Ipc: H04W 72/12 20090101ALN20190705BHEP

INTG Intention to grant announced

Effective date: 20190724

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE PATENT HAS BEEN GRANTED

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

Ref country code: AT

Ref legal event code: REF

Ref document number: 1221452

Country of ref document: AT

Kind code of ref document: T

Effective date: 20200115

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602015044892

Country of ref document: DE

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20200101

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG4D

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: NL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200101

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200101

Ref country code: NO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200401

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200101

Ref country code: RS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200101

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200101

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200527

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: BG

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200401

Ref country code: LV

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200101

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200501

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200101

Ref country code: HR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200101

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200402

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602015044892

Country of ref document: DE

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200101

Ref country code: SM

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200101

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200101

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200101

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200101

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200101

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 1221452

Country of ref document: AT

Kind code of ref document: T

Effective date: 20200101

26N No opposition filed

Effective date: 20201002

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200101

Ref country code: IT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200101

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200101

Ref country code: PL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200101

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20201009

Ref country code: MC

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200101

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20201031

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: FR

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20201031

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20201031

Ref country code: BE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20201031

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20201031

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20201009

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: TR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200101

Ref country code: MT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200101

Ref country code: CY

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200101

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200101

Ref country code: AL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200101

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: GB

Payment date: 20231020

Year of fee payment: 9

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: DE

Payment date: 20231020

Year of fee payment: 9