WO2014178375A1 - 親局装置、子局装置、光通信システム、制御装置および帯域割当方法 - Google Patents
親局装置、子局装置、光通信システム、制御装置および帯域割当方法 Download PDFInfo
- Publication number
- WO2014178375A1 WO2014178375A1 PCT/JP2014/061876 JP2014061876W WO2014178375A1 WO 2014178375 A1 WO2014178375 A1 WO 2014178375A1 JP 2014061876 W JP2014061876 W JP 2014061876W WO 2014178375 A1 WO2014178375 A1 WO 2014178375A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- bandwidth
- allocation
- station device
- request
- priority
- Prior art date
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0896—Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/44—Star or tree networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/70—Admission control; Resource allocation
- H04L47/80—Actions related to the user profile or the type of traffic
- H04L47/805—QOS or priority aware
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/70—Admission control; Resource allocation
- H04L47/82—Miscellaneous aspects
- H04L47/826—Involving periods of time
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q11/00—Selecting arrangements for multiplex systems
- H04Q11/0001—Selecting arrangements for multiplex systems using optical switching
- H04Q11/0062—Network aspects
- H04Q11/0067—Provisions for optical access or distribution networks, e.g. Gigabit Ethernet Passive Optical Network (GE-PON), ATM-based Passive Optical Network (A-PON), PON-Ring
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q11/00—Selecting arrangements for multiplex systems
- H04Q11/0001—Selecting arrangements for multiplex systems using optical switching
- H04Q11/0062—Network aspects
- H04Q2011/0064—Arbitration, scheduling or medium access control aspects
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q11/00—Selecting arrangements for multiplex systems
- H04Q11/0001—Selecting arrangements for multiplex systems using optical switching
- H04Q11/0062—Network aspects
- H04Q2011/0086—Network resource allocation, dimensioning or optimisation
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y04—INFORMATION OR COMMUNICATION TECHNOLOGIES HAVING AN IMPACT ON OTHER TECHNOLOGY AREAS
- Y04S—SYSTEMS INTEGRATING TECHNOLOGIES RELATED TO POWER NETWORK OPERATION, COMMUNICATION OR INFORMATION TECHNOLOGIES FOR IMPROVING THE ELECTRICAL POWER GENERATION, TRANSMISSION, DISTRIBUTION, MANAGEMENT OR USAGE, i.e. SMART GRIDS
- Y04S40/00—Systems for electrical power generation, transmission, distribution or end-user application management characterised by the use of communication or information technologies, or communication or information technology specific aspects supporting them
Definitions
- the present invention relates to a master station device, a slave station device, an optical communication system, a control device, and a bandwidth allocation method.
- a master station device hereinafter referred to as OLT (Optical Line Terminal)
- ONU Optical Network Unit
- OLT Optical Line Terminal
- ONU Optical Network Unit
- PON Passive Optical Network
- the ONU transmits a bandwidth request signal for requesting bandwidth allocation for upstream data communication to the own device to the OLT.
- the OLT allocates a band (a time period during which transmission is permitted) to each ONU based on the band request signal of each ONU, and transmits a transmission permission signal indicating a transmission start time and a transmission time as a result of the allocation for each ONU. Thereafter, the ONU receives a transmission permission signal addressed to itself from the OLT, and transmits uplink data according to the content of the transmission permission signal.
- the above band allocation process is performed for the uplink data communication.
- DBA dynamic bandwidth allocation
- SR Service Reporting
- the delay time is guaranteed to be the strictest delay time.
- Bandwidth allocation is performed at a predetermined cycle.
- the delay guarantee class is a class indicating the degree of delay time to be guaranteed.
- the guaranteed delay time is determined according to the service to be provided. In the case where delay guarantee classes coexist, if bandwidth allocation is performed in a cycle that matches the strictest delay time, the bandwidth allocation cycle becomes shorter than necessary for data transmission of a delay guarantee class with a loose delay time requirement.
- the optical burst signal transmitted in the PON system is accompanied by overhead corresponding to the time required for turning on / off the optical transceiver, the synchronization time required for frame synchronization, and the like. Therefore, when the number of bursts per unit time is increased, the burst overhead amount is increased in proportion to this, and the throughput of user data is reduced. For this reason, when bandwidth allocation is performed with a bandwidth allocation cycle shorter than necessary, there is a problem in that bandwidth utilization efficiency is reduced and bandwidth shortage occurs, and as a result, delay time cannot be guaranteed.
- bandwidth allocation to the ONU for each bandwidth allocation cycle using a plurality of bandwidth allocation cycles.
- the first ONU with a short guaranteed delay time is allocated with a bandwidth allocation cycle A
- the second ONU with a long guaranteed delay time is allocated with a bandwidth allocation cycle B (A ⁇ B).
- a ⁇ B bandwidth allocation cycle B
- the present invention has been made in view of the above, and in the case where a plurality of delay guarantee classes coexist, a master station apparatus, a slave station apparatus, which can guarantee a delay time and improve bandwidth utilization efficiency, It is an object to obtain an optical communication system, a control device, and a bandwidth allocation method.
- the present invention is an upstream communication band that is connected to one or more slave station devices through an optical communication path and is directed from the slave station device toward itself.
- receives a bandwidth request signal requesting a bandwidth for transmission of uplink data from the slave station device, and from the bandwidth request signal for each logical link An analysis unit that extracts the requested bandwidth, a bandwidth calculation unit that calculates an upstream band for transmission of the uplink data based on the requested bandwidth, and an allowable delay time for uplink communication for each logical link, An allowance time calculation unit for obtaining an allowance time based on the allowable delay time for each logical link and an estimated value of the stay time of the uplink data in the slave station device, and the allowance time for each logical link
- a priority calculation unit for determining a priority of a bandwidth allocation request for transmitting the uplink data requested by the bandwidth request signal, and allocation of an upstream bandwidth for transmitting a bandwidth request signal for each logical link.
- a bandwidth request generation unit that generates a requested bandwidth allocation request and determines a priority of the generated bandwidth allocation request; an allocation order determination unit that determines an allocation order corresponding to the bandwidth allocation request based on the priority;
- a transmission permission generation unit for determining a transmission permission time zone corresponding to the band allocation request based on the allocation order and the uplink band for each band allocation request, and notifying the child station device of the transmission permission time zone; It is characterized by providing.
- the present invention when a plurality of delay guarantee classes coexist, there is an effect that the delay time is guaranteed and the bandwidth utilization efficiency can be improved.
- FIG. 1 is a diagram showing a configuration example of a PON system (optical communication system) according to the present invention.
- FIG. 2 is a diagram illustrating a configuration example of the ONU.
- FIG. 3 is a diagram illustrating an example of a PON system in which LLIDs having different delay guarantee classes are mixed.
- FIG. 4 is a diagram illustrating an example of band allocation operation when a band allocation period is set according to the minimum delay time.
- FIG. 5 is a diagram illustrating an example of a bandwidth allocation result when a bandwidth allocation cycle is set according to the minimum delay time.
- FIG. 6 is a diagram illustrating an example of a band allocation result when a plurality of band allocation periods are used.
- FIG. 7 is a diagram illustrating an example of a bandwidth allocation result according to the embodiment.
- FIG. 8 is a flowchart illustrating an example of a bandwidth allocation processing procedure according to the embodiment.
- FIG. 9 is a diagram illustrating a configuration example of the allocation order table.
- FIG. 10 is a diagram for explaining the elapsed time since the previous report reception.
- FIG. 11 is a diagram for explaining the effect of the embodiment.
- FIG. 1 is a diagram showing a configuration example of a PON system (optical communication system) according to the present invention.
- the PON system according to the present embodiment includes a station-side optical communication device (also referred to as “Optical Line Terminal”, hereinafter referred to as “OLT”) 1 that operates as a master station device, and a slave station device.
- OLT optical Line Terminal
- a plurality of optical communication apparatuses on the user side also referred to as “Optical Network Unit”, hereinafter referred to as “ONU” 2-1 to 2-3.
- the OLT 1 is connected to the ONUs 2-1 to 2-3 via the optical fiber 4 and the coupler 3.
- FIG. 1 shows an example with three ONUs, the number of ONUs is not limited to this.
- the PON system of the present embodiment may be a GE-PON system based on IEEE (The Institute of Electrical and Electronics Engineers) 802.3ah, or an ITU-T (International Telecommunication Union Telecommunication Standardization Sector) G. A 98-3.1 G-PON system may be used.
- the PON system will be described as an example.
- the present invention is not limited to the PON system, and can be applied to any optical communication system in which a master station device allocates a band to a slave station device.
- the present invention can be similarly applied to a communication system other than the optical communication system as long as the master station apparatus allocates a band to the slave station apparatus.
- FIG. 1 also shows a configuration example of the OLT 1 of the present embodiment.
- the OLT 1 includes an optical reception unit 11, a PON control unit (control device) 12, an uplink data transmission unit 13, a downlink data reception unit 14, and an optical transmission unit 15.
- the PON control unit 12 includes an uplink data distribution unit 101, a report frame analysis unit (analysis unit) 102, a margin time calculation unit 103, a priority calculation unit 104, a report request registration unit (bandwidth request generation unit) 105, and an allocation order update unit.
- An uplink band calculation unit (band calculation unit) 111 is provided.
- 1 shows an example in which the uplink data distribution unit 101 and the downlink data multiplexing unit 109 are provided in the PON control unit 12, but one or both of the uplink data distribution unit 101 and the downlink data multiplexing unit 109 are provided. It may be provided outside the PON control unit 12.
- the optical receiving unit 11 receives the optical signals transmitted from the ONUs 2-1 to 2-3 and converts them into electric signals.
- the upstream data sorting unit 101 of the PON control unit 12 converts the upstream data (electrical signals input from the optical receiving unit 11) from each of the ONUs 2-1 to 2-3 into user data (user data frame) and control data (control data).
- the user data (upstream data) is output to the upstream data transmission unit 13, and the Report frame (also referred to as a Report message) among the control data frames is output to the Report frame analysis unit 102.
- the Report frame is a band request frame (band request signal) transmitted from each ONU, and the transmission queue length (request band) of user data in the transmission source ONU is stored in the Report frame.
- FIG. 1 illustrates components that process a frame related to bandwidth allocation as a control data frame. Since there is no limitation on the configuration and operation for processing other control data, illustration of components for processing other control data is omitted, and description of the operation is also omitted.
- the uplink data transmission unit 13 transmits the user data input from the uplink data distribution unit 101 to the upper network.
- the Report frame analysis unit 102 analyzes the Report frame, extracts the transmission queue accumulation amount for each LLID of each ONU, outputs it to the upstream bandwidth calculation unit 111, and notifies the margin time calculation unit 103 of the reception time of the Report frame To do.
- the upstream bandwidth calculation unit 111 calculates the upstream bandwidth (the length of time permitted for transmission) to be assigned to each LLID based on the transmission queue accumulation amount of each LLID and the data rate of upstream communication.
- the margin time calculation unit 103 calculates a margin time that is a remaining time for satisfying a delay time guaranteed based on the reception time of the Report frame for each LLID of each ONU.
- the priority calculation unit 104 calculates the bandwidth allocation priority for the user data of each LLID based on the uplink bandwidth calculated by the uplink bandwidth calculation unit 111 and the margin time calculated by the margin time calculation unit 103.
- the report request registration unit 105 associates information indicating that it is a report request, LLID, a priority determined based on a delay guarantee class predetermined for each LLID, and a report bandwidth, and an allocation order update unit It registers in the allocation order table in 106.
- the data request registration unit 110 registers information indicating that the request is a data request, the LLID, the priority calculated by the priority calculation unit 104, and the uplink bandwidth allocation amount of each LLID in the allocation order table.
- the allocation order update unit 106 holds an allocation order table, updates the priority of each entry (bandwidth allocation request) registered in the allocation order table, and rearranges them in descending order of priority.
- the allocation order reading unit 107 reads the information of entries from the allocation order table in descending order of priority (that is, determines the allocation order of each bandwidth allocation request), and outputs the read information to the Gate frame creation unit 108.
- the allocation order reading unit 107 deletes the read entry from the allocation order table.
- the timing at which the allocation order reading unit 107 performs the reading may be set in any way. For example, when the creation of the Gate frame of the previous entry is completed, the next entry may be read, When the order table is updated, the highest priority entry in the allocation order table may be read out.
- the Gate frame generation unit 108 Based on the information input from the allocation order reading unit 107, the Gate frame generation unit 108 generates a Gate frame for notifying a band allocation result (a time zone in which transmission is permitted) for each LLID, and a downlink data multiplexing unit 109 Output to.
- the Gate frame (or Grant frame) is a transmission permission signal for notifying a time zone in which uplink transmission is permitted, and stores a time zone in which transmission is permitted (for example, transmission start time and transmission time). At this time, the Gate frame may store information indicating whether it is a band allocation result for user data transmission or a band allocation result for the Report frame.
- a Gate frame is used as a transmission permission signal for notifying a band allocation result will be described, but a transmission permission signal of another format such as a Grant frame may be used.
- the downlink data multiplexer 109 multiplexes the Gate frame and the user data received from the downlink data receiver 14 and outputs the multiplexed data to the optical transmitter 15.
- the optical transmission unit 15 converts the signal input from the downlink data multiplexing unit 109 into an optical signal and transmits it to the ONUs 2-1 to 2-3.
- FIG. 2 is a diagram illustrating a configuration example of the ONU 2-1 according to the present embodiment.
- the ONU 2-1 includes an optical reception unit 21, a PON control unit (control device) 22, an optical transmission unit 23, transmission / reception units 24-1 and 24-2, and a transmission buffer 25. 1, 5-2.
- FIG. 2 shows an example in which two terminals are connected, the number of terminals to be connected is not limited to this.
- the ONUs 2-2 and 2-3 have the same configuration as the ONU 2-1.
- the optical receiver 21 converts the optical signal transmitted from the OLT 1 into an electrical signal and passes it to the PON controller 22.
- the PON control unit 22 distributes the electrical signal received from the optical reception unit 21 into control data and user data (downlink data), and outputs the user data to the transmission / reception units 24-1 and 24-2 corresponding to the destination of the user data. .
- the transmission / reception units 24-1 and 24-2 transmit user data to the terminals 5-1 and 5-2.
- the transmission / reception units 24-1 and 24-2 store user data (uplink data) received from the terminals 5-1 and 5-2 in the transmission buffer 25 via the PON control unit 22, respectively.
- a transmission queue is provided for each LLID.
- the PON control unit 22 stores the bandwidth allocation result for the transmission of user data based on the information. Or whether it is the result of bandwidth allocation for the Report frame. If this information is not stored, for example, it is determined whether or not it is a band allocation result for the Report frame based on whether or not the transmission time is a predetermined value or less.
- the PON control unit 22 When the PON control unit 22 notifies bandwidth allocation for user data, the PON control unit 22 performs transmission for each LLID based on the transmission start time and transmission time stored in the Gate frame, which is a type of control data received from the OLT 1.
- the user data is read out from the transmission buffer 25 and output to the optical transmitter 23.
- the PON control unit 22 transmits the Report frame based on the transmission start time and the transmission time stored in the Gate frame when the Gate frame notifies the band allocation to the Report frame. Further, the PON control unit 22 monitors the transmission queue length of the transmission buffer 25 for each LLID, and based on the transmission start time and the transmission time notified by the Gate frame, a Report frame storing the transmission queue length for each LLID. Generate and output to the optical transmitter 23.
- the optical transmission unit 23 converts the data received from the PON control unit 22 into an optical signal and transmits the optical signal to the OLT 1.
- the delay guarantee class is a class determined according to the guaranteed delay time.
- the guaranteed delay time is determined according to the type of service (for example, VoIP (Voice over Internet Protocol), Video, etc.), for example.
- FIG. 3 is a diagram illustrating an example of a PON system in which LLIDs having different delay guarantee classes are mixed.
- FIG. 3 shows an example in which each of the ONUs 2-1 and 2-2 has a plurality of LLIDs and a delay guarantee class is defined for each LLID in the PON system shown in FIGS.
- the ONU 2-1 has LLID # 1 and LLID # 2
- LLID # 1 has a guaranteed delay time of 3 ms
- LLID # 2 has a guaranteed delay time of 1 ms.
- the ONU 2-2 has LLID # 3 and LLID # 4.
- LLID # 3 has a guaranteed delay time of 3 ms
- LLID # 4 has a guaranteed delay time of 1 ms.
- the ONU when user data to be transmitted is generated, the ONU transmits a bandwidth request signal (Report frame) for requesting allocation of the upstream bandwidth to the OLT, and the OLT transmits the bandwidth request signal from the ONU to each ONU. Allocate upstream bandwidth.
- the OLT performs uplink band allocation within the next band allocation period at regular intervals (band allocation period) and notifies the ONU of allocation of the upstream band. For this reason, the delay time of user data transmitted from the ONU depends on the bandwidth allocation period.
- FIG. 4 is a diagram illustrating an example of band allocation operation when a band allocation period is set according to the minimum delay time.
- FIG. 4 shows an example in which only the ONU 2-1 (LLID # 1, LLID # 2) in FIG. 3 is operating to simplify the drawing. This is an example in which the bandwidth allocation period is set to 1 ms in accordance with LLID # 2 with a short delay time guaranteed between LLID # 1 and LLID # 2.
- R indicates a Report frame
- G indicates a Gate frame
- D indicates Data (uplink user data).
- the Report frame is transmitted for each LLID, and the transmission queue length is stored in the Report frame.
- the Report frame is transmitted every band allocation period (here, 1 ms), and the transmission queue length is not 0 for LLID # 1 whose guaranteed delay time is 3 ms. Transmits data at a cycle of 1 ms or less.
- FIG. 5 is a diagram illustrating an example of a bandwidth allocation result when a bandwidth allocation cycle is set according to the minimum delay time.
- FIG. 5 is based on the configuration shown in FIG. Also, in FIG. 5, for the sake of simplicity, LLID # 1 is abbreviated as # 1, LLID # 2 as # 2, LLID # 3 as # 3, and LLID # 4 as # 4.
- FIG. 5 shows an example in which bandwidth allocation is performed for each LLID so that the upstream bandwidth for the Report frame and the upstream bandwidth for Data are continuous, as in FIG. In FIG.
- the allocation result (allocated upstream bandwidth) for each LLID is indicated by a square in which the LLID number (# 1 etc.) is described, and the upstream bandwidth for the Report frame and the upstream bandwidth for Data are combined into one upstream. It is described as a band.
- the Report frame storing the transmission queue length related to the user data of each LLID is transmitted in the nth band allocation period among the three band allocation periods from nth to n + 2 shown in FIG.
- An arrow such as “3 ms (delay time allowed for # 1)” shown in FIG. 5 is almost equal to the transmission time point of the Report frame storing the transmission queue length related to the user data (here, the user data is generated).
- the delay time allowed until the user data is transmitted is shown.
- the time until the ONU receives user data up to the Report frame is added as a delay time, but here, for simplicity of explanation, the user data is received until the Report frame is received. Time etc. are described as almost zero.
- data transmission is performed with a delay time (1 ms) shorter than an allowable delay time (3 ms).
- the optical burst signal transmitted in the PON system is accompanied by overhead corresponding to the time required for turning on / off the optical transceiver and the synchronization time required for frame synchronization. Therefore, when the number of bursts per unit time is increased, the burst overhead amount is increased in proportion to this, and the throughput of user data is reduced. Therefore, as in the example of LLID # 1 and LLID # 3 shown in FIG. 5, if bandwidth allocation is performed with a bandwidth allocation cycle that is shorter than necessary compared to the allowable delay time (3 ms), bandwidth utilization efficiency decreases. To do.
- FIG. 6 is a diagram illustrating an example of a band allocation result when a plurality of band allocation periods are used. 6 assumes the configuration shown in FIG. 3 as in FIG. Also, in FIG. 6, as in FIG. 5, for simplicity, LLID # 1 is abbreviated as # 1, LLID # 2 as # 2, LLID # 3 as # 3, and LLID # 4 as # 4. ing. 6 shows an example in which bandwidth allocation is performed for each LLID so that the uplink bandwidth for the Report frame and the uplink bandwidth for Data are continuous for each LLID as in FIGS.
- the OLT 1 determines a bandwidth allocation period for each delay guarantee class and performs bandwidth allocation for each delay guarantee class. Specifically, in the example of FIG. 6, for LLID # 2 and # 4, an upstream band is allocated in the first band allocation period (1 ms), and for LLID # 1 and # 3, the second band allocation period (3 ms). ), The uplink band is allocated in the first first band allocation period within the period. In this case, for the first first band allocation period of the second band allocation period, the uplink band is allocated to LLID # 1, # 2, # 3, # 4. As shown in the example of FIG.
- FIG. 7 is a diagram illustrating an example of a bandwidth allocation result according to the present embodiment.
- the uppermost part of FIG. 7 shows the allocation result of the scheme (multiple cycle scheme) using a plurality of band allocation cycles shown in FIG.
- the bandwidth allocation process according to the present embodiment as shown in the middle part of FIG. 7, the last upstream bandwidth allocated to LLID # 1 can be allocated ahead of schedule.
- the upstream band upstream band at the right end
- FIG. 8 is a flowchart illustrating an example of a bandwidth allocation processing procedure according to the present embodiment.
- FIG. 9 is a diagram illustrating a configuration example of the allocation order table.
- the OLT 1 of the present embodiment holds an allocation order table as described in the description of FIG.
- the bandwidth allocation cycle is not set, and the uplink transmission order is determined according to the priority determined based on the remaining time (allowance time) until the allowable delay time. For this reason, the uplink bandwidth calculation unit 111 does not determine the order in which the transmission permission is given, and the length of time (or data amount) that permits transmission based on the transmission queue amount and the uplink communication data rate as the upstream bandwidth.
- One line (one entry) in the allocation order table corresponds to one bandwidth allocation request and stores allocation information indicating the content of the bandwidth allocation request.
- the bandwidth allocation request registered in the allocation order table includes a Report request that is a bandwidth allocation request for transmitting a Report frame and a data request that is a bandwidth allocation request for transmitting user data.
- the allocation order table includes a Report request flag indicating whether the request is a Report request (first request) or a data request (second request), an LLID indicating a bandwidth allocation request source, and The bandwidth request amount indicating the amount of bandwidth for which allocation is requested, and the priority. That is, in the example of FIG.
- the report request flag, the bandwidth request amount, and the priority are stored in the allocation order table as allocation information corresponding to each bandwidth allocation request.
- the Report request flag indicates a Report request when the Report request flag is ON (“1”), and indicates a data request when the Report request flag is OFF (“0”).
- FIG. 9 is an example, and the format of the allocation order table, the method for defining the Report request flag, and the like are not limited to the example of FIG.
- the Report request is registered in the allocation order table for the Report request, and the data request registration unit 110 is registered in the allocation order table for the data request.
- the data request is registered for each LLID when an upstream band is assigned to the LLID.
- the data request registration unit 110 registers OFF (“0”) as the data request flag for each LLID when registering the data request, and is assigned to each LLID calculated by the upstream bandwidth calculation unit 11 as a bandwidth request amount. Register the upstream bandwidth (the amount of data permitted to be transmitted or the time length permitted to be transmitted). The data request registration unit 110 registers the priority calculated by the margin time calculation unit 103 and the priority calculation unit 104 by the following method.
- the allowance time calculation unit 103 calculates the allowance time according to the following equation (1).
- Margin time Allowable delay time (Ta)-Elapsed time since receiving the previous Report frame (Te) ... (1)
- the allowable delay time (Ta) is the allowable time for the time (delay time) from when the ONUs 2-1 to 2-3 receive data from the transmission / reception units 24-1 and 24-2 until the OLT 1 receives the data. For example, it is determined based on data calculated by the OLT 1 at the time of link-up.
- the margin time calculation unit 103 holds an allowable delay time (Ta) for each LLID.
- This allowable delay time is determined so as to be within a delay time guaranteed for user data (guaranteed delay time ⁇ allowable delay time). For example, when the guaranteed delay time is Tp, the maximum value of the time required from the upstream user data arrival in the ONUs 2-1 to 2-3 to the transmission of the Report frame related to the user data is obtained in advance.
- the guaranteed delay time depends on the type of service.
- the OLT 1 may obtain the guaranteed delay time for each LLID and obtain the allowable delay time from the guaranteed delay time, but may obtain the allowable delay time directly based on the type of service or the like.
- a plurality of methods for setting the allowable delay time are considered as follows.
- the setting method of the allowable delay time is not limited to the following example.
- An allowable delay time is set for each LLID as a service level parameter from the operator.
- the delay class is set for each LLID by the operator, and the OLT 1 holds the correspondence between the delay class and the allowable delay time, and calculates the allowable delay time according to the delay class.
- the service type (VoIP / video (Video ) And the like are set, the OLT 1 holds the correspondence between the service type and the allowable delay time, and the OLT 1 calculates the allowable delay time based on the service type set for each LLID.
- the OLT 1 transmits Information indicating the type of service stored in the frame (for example, Tos (Type of Service) value, Cos (Class of Service) value, VID (VLAN (Virtual Local Area Network) IDentifier) value, etc.)) and allowable delay Based on information (for example, Tos value, Cos value, VID value, etc.) stored in the upstream transmission frame of each LLID while maintaining the correspondence of time To calculate the allowable delay time for each LLID
- the elapsed time (Te) from the previous report frame reception is the elapsed time from the previous report frame reception of the LLID.
- the margin time calculation unit 103 holds the reception time of the previous Report frame for each LLID.
- Te is set to a predetermined initial value (for example, 0).
- the elapsed time (Te) from the previous Report frame reception is the elapsed time (ONU2-1 to 2-3) after the user data requested to be allocated by the Report frame arrives at the ONUs 2-1 to 2-3. Used as an estimated value of user data), and a value other than the elapsed time since the last report frame reception may be used. For example, a value obtained by subtracting RTT (Round Trip Time) / 2 from the elapsed time from the transmission start time instructed to the LLID may be used as the Te instead of the elapsed time from the previous Report frame reception. As for the RTT, the OLT 1 normally measures the RTT and uses this measured value.
- the priority calculation part 104 calculates
- Priority (a ⁇ allowance time) ⁇ b + Upstream band of the LLID ⁇ c (2)
- a, b, and c are constants determined in advance, and the uplink band of the LLID is the uplink band calculated by the uplink band calculation unit 111. a, b, and c may be changeable.
- the said Formula (2) is an example, and the priority determination method is not limited to the said Formula (2), What is necessary is just the priority determination method that a priority becomes high, so that margin time decreases. .
- the priority may be obtained in advance for each range of the margin time and the upstream band of the LLID, stored as a table, and the priority may be obtained by referring to the table.
- the Report request registration unit 105 registers ON (“1”) as the Report request flag when registering the Report request, and registers the time required for transmitting the Report frame (or the data amount of the Report frame) as the bandwidth request amount. To do.
- Various methods are conceivable as methods for registering Report requests in the allocation order table. Two examples are given below, but other methods may be used.
- Registration method 1 Register a report request periodically.
- a cycle for registering a report request (hereinafter referred to as a report registration cycle)
- a cycle Tr for transmitting a report request determined based on an allowable delay time (a report so that the delay time of user data is within the allowable delay time)
- the cycle is shorter than the transmission interval at which frames are transmitted.
- the period Tr is not longer than the allowable delay time. For example, the maximum value of the time required from the upstream user data arrival in the ONUs 2-1 to 2-3 to the transmission of the Report frame related to the user data is obtained in advance for the period Tr, and the obtained maximum value is subtracted from the allowable delay time. It is conceivable to use different values.
- a sufficiently high priority for example, a value similar to the maximum value of the priority in the data request described later
- the priority of the Report request may be determined according to the type of LLID service. If a bandwidth allocation request with a higher priority than the report request is present in the allocation order table at the time when the report request is registered, the allocation to the report request is postponed. In this way, even if the allocation to the Report request is delayed to some extent from the time of registration due to the priority of other bandwidth allocation requests, the allocation to the Report request is performed between the previous Report frame transmission and the elapse of Tr As described above, the Report registration cycle is set shorter than the cycle Tr. In addition, by setting the Report registration cycle to be shorter than the cycle Tr, as shown in FIG.
- Tr-Tf is obtained using the elapsed time (Tf) from the previous Report frame transmission, and is set as the margin time for the Report request. Then, a calculation formula is set such that the priority increases as the report request margin time decreases, and the priority is obtained by substituting the report request margin time into the calculation formula.
- this calculation formula for example, the following formula (3) may be used.
- Priority (a′ ⁇ allow time for report request) ⁇ b ′ + d (3) Note that a ′, b ′, and d are predetermined constants. a ′, b ′, and d may be changeable.
- Registration method 2 When the Report frame is received, the next Report request of the LLID corresponding to the Report frame is registered.
- the priority is set to a sufficiently high priority when the elapsed time from the reception of the previous Report frame becomes a period Tr for transmitting a Report request determined based on the allowable delay time for each LLID. Determine the priority.
- a value that is not so high as an initial value is set as an initial value at the time of registration, and when the priority of the report request is updated at the update timing of the allocation order table, It is conceivable that the priority is updated so as to increase as the elapsed time from the reception of the (Report frame) approaches Tr.
- the allocation order reading unit 107 reads the information of the entry with the highest priority with reference to the allocation order table and outputs the information to the Gate frame creation unit 108 (step S1).
- the Gate frame creation unit 108 generates a Gate frame based on the input information and transmits it to the ONUs 2-1 to 2-3 via the downlink data multiplexing unit 109 and the optical transmission unit 15 (issues a Gate) (step S2 ).
- the Report frame analysis unit 102 determines whether or not the Report frame has been received (Step S3). When the Report frame is received (Step S3 Yes), the Report frame analysis unit 102 determines that the Report frame has been received. Is transmitted to the upstream bandwidth calculation unit 111, and the upstream bandwidth calculation unit 111 calculates the upstream bandwidth (step S5).
- the margin time calculation unit 103 calculates the margin time based on the equation (1) as described above based on the reception time of the Report frame (step S6).
- the priority calculation unit 104 calculates the priority based on the margin time as described above (step S7).
- the data request registration unit 110 registers the data request in the allocation order table using the priority calculated in step S7 (step S8), and returns to step S1.
- the allocation order update unit 106 recalculates the priority for the already registered entries, and updates the allocation order table with the result of the recalculation.
- the priority is calculated by the margin time calculation unit 103 and the priority calculation unit 104 based on Ta and Te at that time.
- the Report request registration unit 105 recalculates the priority based on the recalculation instruction from the allocation order update unit 106.
- the allocation order update unit 106 calculates the priority by performing the same calculation as the margin time calculation unit 103 and the priority calculation unit 104 or the report request registration unit 105 based on Ta, Te, etc. at that time. Also good.
- Step S4 determines whether it is the registration timing of the Report request (Step S4), and if it is not the registration timing (Step S3). Step S4 No) returns to Step S1.
- the process proceeds to Step S8, and the Report request is registered in the allocation order table.
- the allocation order update unit 106 recalculates the priority for the already registered entries, and updates the allocation order table with the result of the recalculation.
- the priority of entries already registered is updated when each bandwidth allocation request is registered in the allocation order table.
- a margin time Report request in the case of a Report frame
- the update is performed.
- the timing of updating the priority of the registered entry is not limited to the above example, and may be updated at regular intervals, for example, independently of registration in the allocation order table.
- FIG. 10 is a diagram for explaining the elapsed time since the last report reception.
- R indicates a Report frame
- G indicates a Gate frame
- D indicates Data (uplink user data).
- OLT 1 receives the Report frame from LLID # 2, and the allocation order table is updated.
- Te1 since the elapsed time from the time when the previous Report frame of LLID # 1 was received at point A is Te1 shown in FIG. 10, calculation (update of the priority of the data request and Report request of LLID # 1 ), Te1 is used as Te in the above formula (1).
- OLT 1 receives the Report frame from LLID # 1, and the allocation order table is updated.
- priority is determined based on an allowance time until the allowable delay time and the upstream bandwidth, and the Report request is also based on the time until the transmission interval of the Report request based on the allowable delay time. Priority.
- the priority is not limited to this, and the priority may be determined based on the margin time without considering the upstream bandwidth.
- the allocation order table stores a margin time (a report request margin time for a report request) instead of a priority, and the allocation order update unit 106 updates the allocation order table based on the margin time. Priorities may be calculated and the allocation order table may be rearranged in order of priority.
- the maximum value of the transmission time for each LLID that can be allocated is 0xFFFF [tq] (about 1.049 [ms]) according to the Gate frame format standard.
- the uplink bandwidth assigned to each LLID is set to be equal to or less than the maximum value of this transmission time.
- one LLID requests allocation of a large amount of bandwidth at a time, there is a possibility that allocation to other LLIDs may be delayed, so even if an upper limit is set for the upstream bandwidth allocated to one LLID at a time. Good.
- the bandwidth is allocated without providing the bandwidth allocation cycle, but the bandwidth allocation cycle may be provided.
- the allocation priority order may be determined for each band allocation period based on the margin time as described above.
- a fixed allocation period is not provided, and a priority is determined based on a margin time until an allowable delay time and an upstream bandwidth for a data request, and an allowable delay time of a Report frame.
- the priority is determined based on the margin time until the transmission timing of the Report frame determined based on the above, and the order in which the bandwidth is allocated (uplink transmission order) is determined based on the priority. For this reason, the number of bursts per unit time and the allocation period for each LLID can be dynamically changed according to the congestion state of the line, and delay guarantee can be performed while maintaining necessary bandwidth utilization efficiency. If the method of controlling the allocation order with the priority according to the present embodiment is used, the allocation cycle varies depending on the communication state of the band.
- FIG. 11 is a diagram for explaining the effect of the present embodiment.
- the bandwidth usage efficiency 301 indicates the bandwidth usage efficiency when the conventional bandwidth allocation method is used
- the bandwidth usage efficiency 302 indicates the bandwidth usage efficiency when the bandwidth allocation method of the present embodiment is used.
- FIG. 11 in the present embodiment, it is possible to improve the bandwidth utilization efficiency as compared with the conventional bandwidth allocation method. In particular, the greater the number of LLIDs, the more remarkable the improvement in bandwidth utilization efficiency.
- the master station device, the slave station device, the optical communication system, the control device, and the bandwidth allocation method according to the present invention are useful for the PON system, and particularly suitable for the PON system that guarantees the delay time of the uplink communication. ing.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Small-Scale Networks (AREA)
Abstract
Description
図1は、本発明にかかるPONシステム(光通信システム)の構成例を示す図である。以下、本発明にかかる光通信システムについて、PONシステムを例にとり説明する。図1に示すように、本実施の形態のPONシステムは、親局装置として動作する局側光通信装置(“Optical Line Terminal”とも言い、以降「OLT」と称す。)1と、子局装置として動作する複数の利用者側光通信装置(“Optical Network Unit”とも言い、以降「ONU」と称す。)2-1~2-3と、を備える。OLT1は、光ファイバ4およびカプラ3経由でONU2-1~2-3に接続される。図1では、ONUが3台の例を示しているがONUの数はこれに限定されない。本実施の形態のPONシステムは、IEEE(The Institute of Electrical and Electronics Engineers)802.3ahをベースとしたGE-PONシステムでもよいし、ITU-T(International Telecommunication Union Telecommunication Standardization Sector) G.983.1のG-PONシステムなどでもよい。また、以下では、PONシステムを例に説明するが、本発明はPONシステムに限定されず、親局装置が子局装置へ帯域を割当てる光通信システムであればPONシステム以外にも適用できる。さらには、親局装置が子局装置へ帯域を割当てる通信システムであれば光通信システム以外の通信システムであっても同様に本発明を適用できる。
余裕時間
=許容遅延時間(Ta)-前回のReportフレーム受信からの経過時間(Te)
…(1)
(i)オペレータからサービスレベルパラメータとして、LLIDごとに許容遅延時間が設定される。またはオペレータからLLIDごとに遅延クラスが設定され、OLT1が遅延クラスと許容遅延時間の対応を保持し、遅延クラスに応じて許容遅延時間を算出
(ii)オペレータからサービスの種類(VoIP/映像(Video)など)が設定され、OLT1がサービスの種類と許容遅延時間の対応を保持しておき、LLIDごとに設定されたサービスの種類に基づいてOLT1が許容遅延時間を算出
(iii)OLT1が、送信フレーム内に格納されるサービスの種類を示す情報(例えば、Tos(Type of Service)値、Cos(Class of Service)値、VID(VLAN(Virtual Local Area Network) IDentifier)値など)の値と許容遅延時間の対応を保持しておき、各LLIDの上り送信フレーム内に格納された情報(例えば、Tos値、Cos値、VID値など)に基づいてLLIDごとに許容遅延時間を算出
優先度=(a-余裕時間)×b
+当該LLIDの上り帯域×c …(2)
なお、a,b,cはあらかじめ定めた定数とし、当該LLIDの上り帯域は、上り帯域計算部111により計算された上り帯域とする。a,b,cを変更可能としてもよい。また、ここでは、優先度は、数値が大きいほど高優先であるとする。なお、上記式(2)は一例であり、優先度の決定方法は、上記式(2)に限定されず、余裕時間が少なくなるほど優先度が高くなるような優先度の決定方法であればよい。また、余裕時間と当該LLIDの上り帯域のそれぞれの範囲ごとに優先度をあらかじめ求めておき、テーブルとして保持し、テーブルを参照して優先度を求めるようにしてもよい。
優先度=(a´-Report要求の余裕時間)×b´+d …(3)
なお、a´,b´,dはあらかじめ定めた定数とする。a´,b´,dを変更可能としてもよい。
Claims (17)
- 1つ以上の子局装置と光通信路により接続され、前記子局装置から自身へ向かう方向である上り方向の通信の帯域を論理リンク単位で前記子局装置へそれぞれ割当てる親局装置であって、
前記子局装置から上りデータの送信のための帯域を要求する帯域要求信号を受信し、前記帯域要求信号から論理リンクごとの要求帯域を抽出する解析部と、
前記要求帯域に基づいて前記上りデータの送信のための上り帯域を計算する帯域計算部と、
論理リンクごとの上り方向の通信に対する許容遅延時間を保持し、論理リンクごとに前記許容遅延時間と前記上りデータの前記子局装置における滞在時間の推定値とに基づいて余裕時間を求める余裕時間計算部と、
論理リンクごとに前記余裕時間に基づいて前記帯域要求信号により要求された前記上りデータを送信するための帯域割当要求の優先度を求める優先度計算部と、
論理リンクごとに、帯域要求信号を送信するための上り帯域の割当てを要求する帯域割当要求を生成し、生成した帯域割当要求の優先度を決定する帯域要求生成部と、
前記優先度に基づいて前記帯域割当要求に対応する割当順を決定する割当順決定部と、
前記割当順と前記帯域割当要求ごとの前記上り帯域とに基づいて前記帯域割当要求に対応する送信許可時間帯を決定し、前記送信許可時間帯を前記子局装置へ通知する送信許可生成部と、
を備えることを特徴とする親局装置。 - 前記優先度計算部は、前記余裕時間を前記許容遅延時間から前記上りデータの前記子局装置における滞在時間の推定値を減じた値とし、前記余裕時間が少ないほど高優先となるように前記優先度を計算することを特徴とする請求項1に記載の親局装置。
- 前記優先度計算部は、前記上りデータの帯域割当要求の優先度を、さらに前記上り帯域に基づいて求めることを特徴とする請求項1または2に記載の親局装置。
- 前記優先度計算部は、前記上り帯域が少ないほど高優先となるように前記優先度を計算することを特徴とする請求項3に記載の親局装置。
- 前記帯域要求生成部は、前記許容遅延時間に基づいて定められた帯域要求信号の送信に要求される最小送信間隔から前回の帯域要求信号の送信からの経過時間を減じた時間が少ないほど高優先となるように前記優先度を計算することを特徴とする請求項1から4のいずれか1つに記載の親局装置。
- 前記帯域要求ごとの、当該帯域割当要求が帯域要求信号を送信するための帯域割当要求である第1の割当要求と上りデータを送信するための帯域割当要求である第2の割当要求とのうちいずれの帯域割当要求であるかを示すフラグと論理リンクの識別子と前記優先度と前記上り帯域とを割当情報として保持し、前記割当情報内の優先度の値を更新する割当情報更新部と、
前記帯域要求信号を受信した場合に、第2の割当要求であることを示す値を設定した前記フラグと論理リンクの識別子と前記帯域計算部により計算された上り帯域とを前記割当情報として登録するデータ要求生成部と、
をさらに備え、
前記割当順決定部は、前記割当情報を前記優先度の高い順に読み出し、読み出した情報を前記送信許可生成部へ出力することにより前記割当順を決定し、
前記帯域要求生成部は、前記帯域割当要求の生成時に、第1の割当要求であることを示す値を設定した前記フラグと論理リンクの識別子と前記帯域要求信号を送信するための上り帯域とを前記割当情報として登録し、
前記送信許可生成部は、前記割当順決定部から出力された前記割当情報に基づいて前記送信許可時間帯を決定することを特徴とする請求項1から5のいずれか1つに記載の親局装置。 - 前記割当情報更新部は、前記割当情報の登録時に、登録された前記割当情報以外の登録済みの前記割当情報内の優先度の値を更新することを特徴とする請求項6に記載の親局装置。
- 前記割当情報更新部は、所定の周期ごとに前記割当情報内の優先度の値を更新することを特徴とする請求項1から6のいずれか1つに記載の親局装置。
- 前記帯域要求生成部は、論理リンクごとに、前記許容遅延時間より短い一定周期で前記帯域割当要求を生成することを特徴とする請求項1から8のいずれか1つに記載の親局装置。
- 前記帯域要求生成部は、前記帯域要求信号を受信した場合に、受信した前記帯域要求信号に対応する論理リンクの前記帯域割当要求を生成することを特徴とする請求項1から8のいずれか1つに記載の親局装置。
- 前記上りデータの前記子局装置における滞在時間の推定値を前回の帯域要求信号を受信してからの経過時間とすることを特徴とする請求項1から10のいずれか1つに記載の親局装置。
- 前記上りデータの前記子局装置における滞在時間の推定値を前回指示した送信許可時間帯の送信開始時間からの経過時間から往復遅延時間の2分の1を減じた値とすることを特徴とする請求項1から10のいずれか1つに記載の親局装置。
- 親局装置と光通信路により接続され、前記親局装置へ向かう方向である上り方向の通信の帯域を前記親局装置から論理リンク単位で割当てられる子局装置であって、
前記親局装置へ論理リンクごとに、自装置から上りデータを送信するための要求帯域を格納した帯域要求信号を送信し、
前記親局装置において前記帯域要求信号に基づく帯域割当要求と前記帯域要求信号の送信のための帯域割当要求とに対して論理リンクごとの上り方向の通信に対する許容遅延時間に基づいて決定された割当順に従って論理リンクごとに定められた送信許可時間帯を前記親局装置から受信し、前記送信許可時間帯に基づいて前記帯域要求信号および前記上りデータの送信を行うことを特徴とする子局装置。 - 親局装置と光通信路により前記親局装置に接続される1つ以上の子局装置とを備え、前記子局装置が、前記子局装置から前記親局装置へ向かう方向である上り方向の通信の帯域を前記親局装置から割当てられる光通信システムであって、
前記子局装置は、前記親局装置へ論理リンクごとに、自装置から上りデータを送信するための要求帯域を格納した帯域要求信号を送信し、
前記親局装置は、
前記子局装置から前記帯域要求信号を受信し、前記帯域要求信号から論理リンクごとの前記要求帯域を抽出する解析部と、
前記要求帯域に基づいて前記上りデータの送信のための上り帯域を計算する帯域計算部と、
論理リンクごとの上り方向の通信に対する許容遅延時間を保持し、論理リンクごとに前記許容遅延時間と前記上りデータの前記子局装置における滞在時間の推定値とに基づいて余裕時間を求める余裕時間計算部と、
論理リンクごとに前記余裕時間に基づいて前記帯域要求信号により要求された前記上りデータを送信するための帯域割当要求の優先度を求める優先度計算部と、
論理リンクごとに、帯域要求信号を送信するための上り帯域の割当てを要求する帯域割当要求を生成し、生成した帯域割当要求の優先度を決定する帯域要求生成部と、
前記優先度に基づいて前記帯域割当要求に対応する割当順を決定する割当順決定部と、
前記割当順と前記帯域割当要求ごとの前記上り帯域とに基づいて前記帯域割当要求に対応する送信許可時間帯を決定し、前記送信許可時間帯を前記子局装置へ通知する送信許可生成部と、
を備え、
前記子局装置は、前記親局装置から通知された前記送信許可時間帯に基づいて前記帯域要求信号および前記上りデータの送信を行うことを特徴とする光通信システム。 - 1つ以上の子局装置と光通信路により接続され、前記子局装置から自身へ向かう方向である上り方向の通信の帯域を論理リンク単位で前記子局装置へそれぞれ割当てる親局装置における制御装置であって、
前記子局装置から上りデータの送信のための帯域を要求する帯域要求信号を受信し、前記帯域要求信号から論理リンクごとの要求帯域を抽出する解析部と、
前記要求帯域に基づいて前記上りデータの送信のための上り帯域を計算する帯域計算部と、
論理リンクごとの上り方向の通信に対する許容遅延時間を保持し、論理リンクごとに前記許容遅延時間と前記上りデータの前記子局装置における滞在時間の推定値とに基づいて余裕時間を求める余裕時間計算部と、
論理リンクごとに前記余裕時間に基づいて前記帯域要求信号により要求された前記上りデータを送信するための帯域割当要求の優先度を求める優先度計算部と、
論理リンクごとに、帯域要求信号を送信するための上り帯域の割当てを要求する帯域割当要求を生成し、生成した帯域割当要求の優先度を決定する帯域要求生成部と、
前記優先度に基づいて前記帯域割当要求に対応する割当順を決定する割当順決定部と、
前記割当順と前記帯域割当要求ごとの前記上り帯域とに基づいて前記帯域割当要求に対応する送信許可時間帯を決定し、前記送信許可時間帯を前記子局装置へ通知する送信許可生成部と、
を備えることを特徴とする制御装置。 - 親局装置と光通信路により接続され、前記親局装置へ向かう方向である上り方向の通信の帯域を前記親局装置から論理リンク単位で割当てられる子局装置における制御装置であって、
前記親局装置へ論理リンクごとに、自装置から上りデータを送信するための要求帯域を格納した帯域要求信号を送信し、
前記親局装置において前記帯域要求信号に基づく帯域割当要求と前記帯域要求信号の送信のための帯域割当要求とに対して論理リンクごとの上り方向の通信に対する許容遅延時間に基づいて決定された割当順に従って論理リンクごとに定められた送信許可時間帯を前記親局装置から受信し、前記送信許可時間帯に基づいて前記帯域要求信号および前記上りデータの送信を行うことを特徴とする制御装置。 - 親局装置と光通信路により前記親局装置に接続される1つ以上の子局装置とを備え、前記子局装置が、前記子局装置から前記親局装置へ向かう方向である上り方向の通信の帯域を前記親局装置から割当てられる光通信システムにおける帯域割当方法であって、
前記子局装置が、前記親局装置へ論理リンクごとに、自装置から上りデータを送信するための要求帯域を格納した帯域要求信号を送信する要求信号送信ステップと、
前記親局装置が、前記子局装置から前記帯域要求信号を受信し、前記帯域要求信号から論理リンクごとの前記要求帯域を抽出する解析ステップと、
前記親局装置が、前記要求帯域に基づいて前記上りデータの送信のための上り帯域を計算する帯域計算ステップと、
前記親局装置が、論理リンクごとの上り方向の通信に対する許容遅延時間を保持し、論理リンクごとに前記許容遅延時間と前記上りデータの前記子局装置における滞在時間の推定値とに基づいて余裕時間を求める余裕時間計算ステップと、
前記親局装置が、論理リンクごとに前記余裕時間に基づいて前記帯域要求信号により要求された前記上りデータを送信するための帯域割当要求の優先度を求める優先度計算ステップと、
前記親局装置が、論理リンクごとに、帯域要求信号を送信するための上り帯域の割当てを要求する帯域割当要求を生成し、生成した帯域割当要求の優先度を決定する帯域要求生成ステップと、
前記親局装置が、前記優先度に基づいて前記帯域割当要求に対応する割当順を決定する割当順決定ステップと、
前記親局装置が、前記割当順と前記帯域割当要求ごとの前記上り帯域とに基づいて前記帯域割当要求に対応する送信許可時間帯を決定し、前記送信許可時間帯を前記子局装置へ通知する送信許可生成ステップと、
前記子局装置が、前記親局装置から通知された前記送信許可時間帯に基づいて前記帯域要求信号および前記上りデータの送信を行う送信制御ステップと、
を含むことを特徴とする帯域割当方法。
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/888,504 US20160080208A1 (en) | 2013-05-02 | 2014-04-28 | Master station device, slave station device, optical communication system, control device, and bandwidth allocation method |
JP2015514845A JP5908167B2 (ja) | 2013-05-02 | 2014-04-28 | 親局装置、子局装置、光通信システム、制御装置および帯域割当方法 |
CN201480024236.7A CN105164978A (zh) | 2013-05-02 | 2014-04-28 | 主台装置、从台装置、光通信系统、控制装置及带宽分配方法 |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2013-096894 | 2013-05-02 | ||
JP2013096894 | 2013-05-02 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2014178375A1 true WO2014178375A1 (ja) | 2014-11-06 |
Family
ID=51843501
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2014/061876 WO2014178375A1 (ja) | 2013-05-02 | 2014-04-28 | 親局装置、子局装置、光通信システム、制御装置および帯域割当方法 |
Country Status (4)
Country | Link |
---|---|
US (1) | US20160080208A1 (ja) |
JP (1) | JP5908167B2 (ja) |
CN (1) | CN105164978A (ja) |
WO (1) | WO2014178375A1 (ja) |
Cited By (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2017041724A (ja) * | 2015-08-19 | 2017-02-23 | 日本電信電話株式会社 | 端局装置及び帯域割当方法 |
JP2017041700A (ja) * | 2015-08-18 | 2017-02-23 | 日本電信電話株式会社 | 端局装置及び帯域割当方法 |
JP2017046327A (ja) * | 2015-08-28 | 2017-03-02 | 日本電信電話株式会社 | 端局装置、帯域割当方法及びプログラム |
JP2019062315A (ja) * | 2017-09-25 | 2019-04-18 | 沖電気工業株式会社 | 局側装置、光アクセスネットワーク、及び、帯域割当方法 |
WO2020040047A1 (ja) * | 2018-08-22 | 2020-02-27 | 日本電信電話株式会社 | 帯域割当装置、帯域割当方法及び帯域割当プログラム |
WO2022014018A1 (ja) * | 2020-07-16 | 2022-01-20 | 日本電信電話株式会社 | 帯域制御システム、帯域制御方法、帯域制御用プログラム及び局内光終端装置 |
JP7031706B1 (ja) | 2020-08-31 | 2022-03-08 | 沖電気工業株式会社 | 通信ネットワーク及び帯域割当方法 |
Families Citing this family (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP6159265B2 (ja) * | 2014-01-10 | 2017-07-05 | Kddi株式会社 | 帯域割当方法、局側装置及び光通信システム |
CN107534985B (zh) * | 2015-04-21 | 2019-01-25 | 三菱电机株式会社 | 通信装置、通信方法及通信系统 |
JP6581310B2 (ja) * | 2016-07-22 | 2019-09-25 | 日本電信電話株式会社 | リンク制御回路 |
JP6429225B2 (ja) * | 2016-07-25 | 2018-11-28 | 三菱電機株式会社 | 光ネットワークの光端局装置および上りスケジューリング方式 |
KR20180039399A (ko) | 2016-10-10 | 2018-04-18 | 삼성전자주식회사 | 전자 장치 및 그 제어 방법 |
CN108540221B (zh) * | 2017-03-06 | 2022-12-02 | 中兴通讯股份有限公司 | 数据发送方法及装置 |
CN107257310B (zh) * | 2017-07-05 | 2020-04-24 | 北京东土科技股份有限公司 | 基于工业互联网现场层宽带总线架构的实现系统 |
US11114112B2 (en) | 2017-09-07 | 2021-09-07 | Google Llc | Low power, high bandwidth, low latency data bus |
JP7293257B2 (ja) * | 2018-05-31 | 2023-06-19 | グーグル エルエルシー | 低パワー、高帯域幅、低遅延データバス |
CN112087678B (zh) * | 2019-06-14 | 2023-08-18 | 中兴通讯股份有限公司 | 带宽的分配、带宽的检查方法及装置 |
JP6804695B1 (ja) * | 2019-12-23 | 2020-12-23 | 三菱電機株式会社 | 光通信装置およびリソース管理方法 |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2010068067A (ja) * | 2008-09-09 | 2010-03-25 | Oki Electric Ind Co Ltd | 帯域割当方法及び帯域割当装置 |
JP2011135501A (ja) * | 2009-12-25 | 2011-07-07 | Mitsubishi Electric Corp | 通信システム、親局装置および子局装置 |
JP2011254383A (ja) * | 2010-06-03 | 2011-12-15 | Mitsubishi Electric Corp | 通信装置および帯域制御方法 |
Family Cites Families (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7016372B2 (en) * | 2001-02-28 | 2006-03-21 | Telefonaktiebolaget Lm Ericsson (Publ) | Dynamic bandwidth allocation in AD hoc wireless piconets |
CN101087238B (zh) * | 2003-10-21 | 2010-08-04 | 华为技术有限公司 | 无源光网络的动态带宽分配装置及方法 |
CN101783762B (zh) * | 2009-01-16 | 2012-05-23 | 中华电信股份有限公司 | 以太被动式光纤网络的动态频宽指配方法 |
JP4888515B2 (ja) * | 2009-04-16 | 2012-02-29 | 住友電気工業株式会社 | 動的帯域割当装置及び方法とponシステムの局側装置 |
WO2013108578A1 (ja) * | 2012-01-17 | 2013-07-25 | 日本電信電話株式会社 | 波長帯域割当方法 |
-
2014
- 2014-04-28 JP JP2015514845A patent/JP5908167B2/ja active Active
- 2014-04-28 US US14/888,504 patent/US20160080208A1/en not_active Abandoned
- 2014-04-28 WO PCT/JP2014/061876 patent/WO2014178375A1/ja active Application Filing
- 2014-04-28 CN CN201480024236.7A patent/CN105164978A/zh active Pending
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2010068067A (ja) * | 2008-09-09 | 2010-03-25 | Oki Electric Ind Co Ltd | 帯域割当方法及び帯域割当装置 |
JP2011135501A (ja) * | 2009-12-25 | 2011-07-07 | Mitsubishi Electric Corp | 通信システム、親局装置および子局装置 |
JP2011254383A (ja) * | 2010-06-03 | 2011-12-15 | Mitsubishi Electric Corp | 通信装置および帯域制御方法 |
Cited By (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2017041700A (ja) * | 2015-08-18 | 2017-02-23 | 日本電信電話株式会社 | 端局装置及び帯域割当方法 |
JP2017041724A (ja) * | 2015-08-19 | 2017-02-23 | 日本電信電話株式会社 | 端局装置及び帯域割当方法 |
JP2017046327A (ja) * | 2015-08-28 | 2017-03-02 | 日本電信電話株式会社 | 端局装置、帯域割当方法及びプログラム |
JP2019062315A (ja) * | 2017-09-25 | 2019-04-18 | 沖電気工業株式会社 | 局側装置、光アクセスネットワーク、及び、帯域割当方法 |
WO2020040047A1 (ja) * | 2018-08-22 | 2020-02-27 | 日本電信電話株式会社 | 帯域割当装置、帯域割当方法及び帯域割当プログラム |
JP2020031325A (ja) * | 2018-08-22 | 2020-02-27 | 日本電信電話株式会社 | 帯域割当装置、帯域割当方法及び帯域割当プログラム |
CN112534781A (zh) * | 2018-08-22 | 2021-03-19 | 日本电信电话株式会社 | 带宽分配装置、带宽分配方法以及带宽分配程序 |
WO2022014018A1 (ja) * | 2020-07-16 | 2022-01-20 | 日本電信電話株式会社 | 帯域制御システム、帯域制御方法、帯域制御用プログラム及び局内光終端装置 |
JP7347677B2 (ja) | 2020-07-16 | 2023-09-20 | 日本電信電話株式会社 | 帯域制御システム、帯域制御方法、帯域制御用プログラム及び局内光終端装置 |
JP7031706B1 (ja) | 2020-08-31 | 2022-03-08 | 沖電気工業株式会社 | 通信ネットワーク及び帯域割当方法 |
JP2022044063A (ja) * | 2020-08-31 | 2022-03-17 | 沖電気工業株式会社 | 通信ネットワーク及び帯域割当方法 |
Also Published As
Publication number | Publication date |
---|---|
JPWO2014178375A1 (ja) | 2017-02-23 |
CN105164978A (zh) | 2015-12-16 |
JP5908167B2 (ja) | 2016-04-26 |
US20160080208A1 (en) | 2016-03-17 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
JP5908167B2 (ja) | 親局装置、子局装置、光通信システム、制御装置および帯域割当方法 | |
JP5094664B2 (ja) | 受動光網システムおよびその運用方法 | |
KR100547705B1 (ko) | 기가비트 이더넷 수동 광 가입자망의 음성서비스를 위한대역폭 할당방법 | |
CN101841745A (zh) | 光传送路终端装置、无源光网系统以及频带分配方法 | |
CN109479022B (zh) | 光网络的光终端站装置和上行调度方法 | |
WO2010116561A1 (ja) | 受動光網システムおよびその運用方法 | |
US9680575B2 (en) | Relay device, station side device, and communication system and communication method using relay device | |
WO2012070127A1 (ja) | 通信装置 | |
WO2021053759A1 (ja) | ネットワーク制御装置、通信リソース割り当て方法および通信システム | |
WO2012119358A1 (zh) | 无源光网络的动态带宽分配方法及装置 | |
KR100786527B1 (ko) | 수동광분기망에서 맥을 위한 승인 요청 방법 | |
US20110318009A1 (en) | Pon system, optical network unit used therein, and transmission control method therefor | |
Gravalos et al. | A modified max-min fair dynamic bandwidth allocation algorithm for XG-PONs | |
JPWO2010116411A1 (ja) | 局側通信装置、光通信システムおよびリソース割り当て方法 | |
JP4877483B2 (ja) | 送信割当て方法及び装置 | |
JP2011166328A (ja) | 光伝送システム、局側光終端装置及び上り送信制御方法 | |
Lee et al. | A two‐step scheduling algorithm to support dual bandwidth allocation policies in an Ethernet passive optical network | |
JP6792530B2 (ja) | 通信システム及び通信方法 | |
KR100657122B1 (ko) | 이더넷 수동광가입자망의 상향 데이터 전송을 위한 동적대역폭 할당방법 | |
KR100952833B1 (ko) | 이더넷 수동 광 통신망(epon)의 onu에서의 상향전송 대역 할당 방법 | |
JP5487293B2 (ja) | 受動光網システムおよびその運用方法 | |
KR20170046012A (ko) | 이더넷 수동 광 네트워크에서 동기식 동적 대역 할당 장치 및 방법 | |
JP4957758B2 (ja) | Ponシステムとその宅側装置 | |
JP6841745B2 (ja) | 通信装置および通信装置のフレーム送信方法 | |
Helmy et al. | Taking Turns with adaptive cycle time-an upstream media access scheme for extended-reach FTTx |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
WWE | Wipo information: entry into national phase |
Ref document number: 201480024236.7 Country of ref document: CN |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 14792030 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 2015514845 Country of ref document: JP Kind code of ref document: A |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWE | Wipo information: entry into national phase |
Ref document number: 14888504 Country of ref document: US |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 14792030 Country of ref document: EP Kind code of ref document: A1 |