WO2007007426A1 - 同期配信方法 - Google Patents
同期配信方法 Download PDFInfo
- Publication number
- WO2007007426A1 WO2007007426A1 PCT/JP2005/023288 JP2005023288W WO2007007426A1 WO 2007007426 A1 WO2007007426 A1 WO 2007007426A1 JP 2005023288 W JP2005023288 W JP 2005023288W WO 2007007426 A1 WO2007007426 A1 WO 2007007426A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- data
- cycle
- transmitted
- packet
- aggregation device
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
- H04L12/16—Arrangements for providing special services to substations
- H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
- H04L12/1881—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast with schedule organisation, e.g. priority, sequence management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
- H04L12/16—Arrangements for providing special services to substations
- H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
- H04L12/189—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast in combination with wireless systems
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W56/00—Synchronisation arrangements
- H04W56/001—Synchronization between nodes
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W92/00—Interfaces specially adapted for wireless communication networks
- H04W92/04—Interfaces between hierarchically different network devices
- H04W92/12—Interfaces between hierarchically different network devices between access points and access point controllers
Definitions
- the present invention relates to a synchronous distribution method, and in particular, in a wireless communication system including a plurality of base stations and an aggregation device that aggregates the plurality of base stations, the aggregation device includes a plurality of base stations. It is related to the synchronous distribution method that transmits distribution data to each wireless terminal in synchronization with the same time information.
- 3GPP2 3rd Generation Partnership Project 2
- 3rd Generation Partnership Project 2 an international standardization organization, the cdma2000 lx method, which is a mobile communication method capable of voice communication and data communication, and the frequency by specializing in data communication only.
- the cdma2000 lxEV—DO (lx Evolution-Data Only) method which is a mobile radio communication method with improved usage efficiency, is being standardized.
- the cdma2000 lx method and lxEV-DO communication method are used to implement unicast communication that communicates with one-to-one terminals in a mobile network, but realization of multicast communication that performs one-to-many communication has been studied. Yes.
- the broadcast channel power called “broadcast channel” as a data transmission channel in the wireless interface is 3GPP2 standard for ma2000 lx.
- a service standardized at 0 and using broadcast channels is called BCMCS (Broadcast Multicast Service).
- the channel for unicast which has been used for communication between base stations and mobile stations, has the feature that data transmitted from a base station can be received by only a single mobile station.
- a broadcast channel standardized for multicast communication support has the characteristic that all mobile devices capable of receiving radio waves can receive data transmitted from base stations.
- the power is controlled optimally between the mobile station to be communicated with the base station, application of the modulation method, and handoff when approaching another base station.
- soft combine radio waves transmitted from the base station existing between the coverage area of one base station and the coverage area of another base station interfere with each other, and the reception environment is bad! It is known as a technology for improving the reception environment for communications using broadcast channels in the area.
- multiple base stations transmit the same data at the same time using the same radio parameters, so that the receiver of the mobile station receives the radio waves coming from each base station, By combining, the radio waves from other base stations that have been the source of interference are changed to gain, and the reception environment is improved.
- the downlink radio interface is composed of a set of time slots of 1.67 ms seconds, but it is transmitted in units of 1.67 ms time slots. Data must be transmitted in synchronization with the same time information without shifting between base stations. If the mobile device has a function to absorb the timing error between base stations and the arrival time difference due to propagation delay, soft combining is possible even if there is a transmission timing error between base stations. Even in this case, it is necessary to synchronize data transmission so that a certain amount of timing error does not occur between base stations. As a technique for guaranteeing the timing synchronized with the same time information, an unapplied A3 interface disclosed in 3GPP2 standard A.
- Non-patent Document 2 SO 015—C vl. 0 (Non-patent Document 2) is applied.
- a car system is disclosed.
- This anchor method is a technology that realizes a technology equivalent to soft combine called soft handoff in cdma2000 lx radio.
- one base station becomes an anchor base station that aggregates multiple base stations.
- This anchor base station performs transmission control by managing transmission timings of all base stations.
- an anchor base station transmits data by specifying a transmission time in units of 20 ms frames, which is the minimum unit of radio transmission timing. Therefore, it means that the anchor base station that serves as an aggregation device that aggregates base stations must manage detailed radio interface information for calculating radio transmission timing.
- Non-Patent Document 2 3GPP2 Standard A. S0015-C vl. 0
- the present invention enables synchronization distribution even in the absence of radio-specific information in an aggregation device that aggregates base stations, and when synchronization is lost by transmitting a cycle number and a transmission byte position within the cycle as synchronization information.
- the purpose is to enable resynchronization even when a packet loss occurs during transmission.
- an aggregator when an anchor base station is not installed as an apparatus for aggregating base stations, an aggregator is installed at a higher level, and data is transmitted when data is transmitted from the aggregator to each base station.
- timing information By adding timing information to the communication data, it becomes possible to synchronize the timing between base stations necessary to realize soft combine.
- the timing information to be included in the transmission data includes the sequence number calculated based on the time managed by the aggregation device without using the radio specific parameter, and each base station receiving it includes the sequence number.
- the sequence number defines a fixed transmission cycle, and transmits a cycle number indicating what cycle the data should be transmitted and what number of bytes within that cycle. By configuring the sequence number power indicating this, resynchronization is possible even if synchronization is lost once or data destined for a certain base station from the aggregation device is lost during transmission.
- the present invention can enable base station synchronization without making the aggregation device aware of the absolute transmission time.
- a wireless communication system including a plurality of base stations and an aggregation device that aggregates the plurality of base stations
- the aggregation device distributes to each wireless terminal via the plurality of base stations in synchronization with the same time information.
- Each of the plurality of base stations has a cycle number corresponding to a transmission time when transmitting the distribution data by dividing it into a fixed cycle, the number of transmission bytes that can be transmitted in one cycle, and a predetermined cycle number assigned to the transmission packet.
- a path establishment request including the transmission start time of the aggregation device corresponding to the key information for synchronous delivery to the aggregation device,
- the aggregation device When the aggregation device receives the path establishment request, the aggregation device sends a path establishment response including a cycle number used for data distribution and a time corresponding to the start time of the cycle of the cycle number to the plurality of base stations. Respectively, and establishes a node for transmitting data from the aggregation device to each base station,
- the aggregation device gives each packet that distributes distribution data the cycle number that is a basis for calculating time information to be wirelessly transmitted and a sequence number that indicates a transmission position within the cycle indicated by the cycle number.
- Each of the plurality of base stations calculates time information to be wirelessly transmitted to the wireless terminal based on the period number and sequence number assigned to the received packet, and synchronizes with the calculated same time information.
- the synchronous delivery method is provided.
- an aggregation device that aggregates base stations can perform synchronous distribution without radio-specific information, and by transmitting a cycle number and a transmission byte position within the cycle as synchronization information, Resynchronization is possible even if the packet is lost or a packet loss occurs during transmission.
- FIG. 1A 1XEV—A configuration diagram showing a flow of processing for performing synchronized delivery between base stations on a DO network.
- FIG. 1B is a schematic diagram of packet synchronization in the configuration of FIG. 1A.
- FIG. 2 is a configuration diagram showing hardware of a BSN (BCMCS Serving Node) 104.
- BSN BCMCS Serving Node
- FIG. 3 is a configuration diagram showing hardware of AN (Access Network) 102 and AN103.
- FIG. 5 An explanatory diagram showing how to calculate the number of bytes that can be transmitted in one cycle that AN notifies BSN.
- FIG. 6 is a diagram showing a packet configuration to be transmitted from BSN to AN.
- FIG. 7 is a diagram showing an example of using each field when the cycle number 612 and the sequence number 614 in the cycle shown in FIG. 6 are used.
- BSN104 sends the packet received from Content Server 105 and sends AN102, AN1
- FIG. 9 Flowchart showing the method for determining the cycle number and sequence number in BSN104
- FIG. 10 is a diagram showing a transmission time determination method in AN.
- FIG. 11 A diagram showing time synchronization! /, Na! /, In some cases!
- FIG. 13 is an explanatory diagram of the number of bytes that can be transmitted.
- FIG. 15 is a diagram of an example (1) of assigning a cycle number and a sequence number within a cycle.
- FIG. 16 Diagram of example (2) of assigning cycle numbers and sequence numbers within cycles.
- FIG. 1A is a configuration diagram showing a flow of processing for performing synchronized delivery between base stations on the lxEV-DO network.
- the content server 105 is a server for distributing BCMCS data, and manages distribution data and distribution schedules.
- the content server 105 transmits the BCMCS data to the BSN (BCMCS Serving Node) 104 that is the aggregation device.
- the BSN 104 copies the data received from the content server 105 to an AN (Acces s Network) 102 and AN 103 and transmits the data.
- the BSN 104 adds time information including, for example, a transmission cycle number and an in-cycle sequence number to the transmission packet and transmits it.
- AN102 and AN103 When AN102 and AN103 receive data to which time information is added, AN102 and AN103 calculate the time to transmit data wirelessly from the time information, and transmit the data wirelessly at that time.
- ATI 01 which is a group of multiple mobile stations, receives data transmitted at the same time from AN102 and AN103 at the same time, and synthesizes the signals so that when data is transmitted from one AN It is possible to perform reception with better reception quality.
- AN102 and AN103 need to synchronize time to transmit data at the same time, and in the lxEV-DO system, by synchronizing with the time information received by GPS (Global Positioning System) 106, Synchronize time between AN102 and AN103 Is possible.
- GPS Global Positioning System
- BSN104 uses NTP (Network Time Protocol) etc. from time server 107 that synchronizes with the time information from GPS 106. It is possible to synchronize the time by receiving the distribution.
- NTP Network Time Protocol
- the present invention is applicable both when the time synchronization between AN and BSN is performed and when the time synchronization is not performed.
- FIG. 1 it is described that there are two ANs, but the present invention can be applied to the case where there are more than two ANs.
- a network to which two ANs are applied is shown as an application example.
- Figure 1B shows an overview of packet synchronization.
- the packet 108 is transmitted from the content server 105 to the BSN 104, and the BSN 104 receives it as the bucket 109.
- the BSN 104 transmits the received packet 109 to the AN 102 and AN 103 as the packet 110 and the packet 111, respectively.
- These packets 110 and 111 include, for example, cycle number information as time information, and it is assumed here that cycle number 0 is set. Therefore, AN102 and AN103 hold the packet until the transmission timing of the packet with the cycle number 0, and at the transmission timing, transmission is performed at the same timing as shown in the packet 112 and the packet 113.
- FIG. 2 shows the hardware of a BSN (BCMCS Serving Node) 104.
- the BSN 104 includes a network IZF 201 for communicating with other devices such as AN and content server.
- Data distributed from the content server 105 is written to the memory 203 via the network IZF 201 and the communication bus 206.
- the written received data information is read by the CPU 202, and a sequence number generated based on the time information provided by the clock 204 is added to the data and packetized.
- the packet Is transmitted to AN again via communication bus 206 and network IZF 201.
- time information managed by clock 204 is synchronized with time information that can be acquired from GPS receiver 205 or received from time server 107 according to a preset setting. Receive time information.
- FIG. 3 shows the hardware of AN (Access Network) 102 and AN103.
- AN has network I / F 301 to communicate with BSN.
- the data received by the BSN 104 is written into the memory 303 via the network IZF 301 and the communication bus 306.
- the written received data information is read by the CPU 302, and the time to transmit on the radio is determined from the time information provided by the clock 304 and the time information attached to the received data.
- the data is transmitted to the modulation / demodulation circuit 307 via the communication bus 306, and is wirelessly transmitted by the modulation / demodulation circuit 307. Therefore, the data is modulated, converted into an analog signal by the RF circuit 308, and wirelessly transmitted. Is sent.
- the GPS receiver 305 is implemented for the purpose of receiving time information distributed from the GPS 106 and providing time information to the clock 304. 2. Synchronous delivery procedure
- Figure 4 is a sequence diagram showing the procedure (first AN connection) up to soft-conne. This figure shows the flow from when AN102 establishes a path to BSN104 and distributes data. This procedure shows the procedure for AN102 to connect to BSN104 when there is no AN to connect to BSN104.
- the OMC 113 issues a path establishment request instruction to the AN 102 (401).
- This path establishment request instruction includes, for example, the wireless data rate, the RS code type, the number of used slots, and the like.
- the AN 102 transmits a path establishment request to the BSN 104 (402).
- This path establishment request includes the number of transmission bytes that can be transmitted at a fixed period (5.12 seconds in the figure as an example), the BSN time corresponding to period number 0, and the GRE (General Routing Encapsulation) for data transmission. Key information is sent together.
- the number of transmitted bytes that can be transmitted at a fixed period is the number of bytes derived from the radio interface specification, and is a value specific to the radio system. Therefore, it can be derived only by devices such as AN that hold radio-specific information. I can not do such a thing.
- transmission rate of 614.4 kbps, TotalBurstLength of 192 slot is used for 1 interlace (192 slots), and RS code is (12, 4, 16) Is applied, 192 MAC packets that can transmit 1000 bits of data can transmit 192 of which 1Z4 is used as the NOR bit for RS code. Therefore, 1.
- one interlace refers to one of the total radio transmission times divided into four, and refers to the total radio transmission time in four interlaces. TotalBurstLength indicates the length of the BCMCS transmission setting cycle in one interlace unit. When set to 192 slots, the total wireless transmission time is 4 times 768 slots, that is, 1.28 seconds.
- FIG. 13 shows an explanatory diagram of the number of bytes that can be transmitted. This figure shows that TotalBurst Length is 192 slots, RS code (12, 4, 16), no framing header, and one interlaced (192 slots) BCMCS data transmission 5. Bytes that can be transmitted per 12 seconds It is a list of numbers.
- the BSN time corresponding to the cycle number 0 is information used when the BSN 104 transmits data to the AN 102 and determines the cycle number assigned to the transmission packet and the sequence number within the cycle. The use of this information will be described separately.
- the GRE key is set in the key field of the GRE header attached to the transmission packet when data is transmitted from BSN104 to AN102.
- AN 102 can distinguish the data flowing through each path when multiple paths are established between BSN 104 and AN 102.
- the GRE header part will be described later.
- the BSN 104 Upon receiving the path establishment request 402, the BSN 104 performs a path establishment process and transmits a path establishment response 403 to the AN 102 (403).
- This path establishment response 403 includes a cycle number used at the time of data distribution and a corresponding time at the beginning of the cycle. At this point, the establishment of a path for transmitting data from BSN 104 to AN 102 is completed, and data can be transmitted.
- the BSN 104 transmits a data distribution request by a signal such as IGMP Join to instruct the content server 106 to transmit data (404).
- the content server 105 receives the data distribution request 405 and starts distributing data (405).
- the distribution data transmitted from the content server 105 is received by the BSN 104, and the distribution number is transmitted to the AN 102 by assigning a period number and a sequence number within the period, which are the basis for calculating the time to transmit wirelessly (406).
- AN102 calculates the wireless transmission time (time information) for the received distribution data based on the cycle number assigned to the received packet and the sequence number within the cycle, and when the calculated time is reached ( Data is transmitted (in synchronization with time information) (407). All ANs synchronize with the GPS 106, and the period number received from the BSN104 and the sequence number power within the period are the same algorithm, and each AN synchronizes to the same GPS time. Therefore, the wireless transmission time can be synchronized (matched) with the same time information.
- Fig. 12 is a sequence diagram showing the procedure up to soft-conne-in (second and subsequent AN connections). This figure shows the flow from when AN 102 is already connected to BSN 104 until another AN 103 establishes a path to BSN 104 and performs data distribution. Since AN102 has already established a path, the distribution data transmitted from the content server 105 has been transmitted to AT101 via BSN104 and AN102 (1201).
- the OMC 113 transmits a path establishment request instruction to request the AN 103 to establish a path (1202).
- the AN 103 transmits a path establishment request to the BSN 104 (1203).
- This nos establishment request is sent together with the number of notes that can be sent at a fixed period (5.12 seconds as an example in the figure), the BSN time corresponding to period number 0, and the GRE key information for data transmission.
- This path establishment response 1204 includes a cycle number used for data distribution and the corresponding time at the beginning of the cycle.
- the cycle number transmitted here the cycle number n assigned to the distribution data being transmitted to AN102 in step 1201 and the BSN corresponding time corresponding to the time point of the cycle number n are used.
- BSN104 has already received distribution data from Contentsano for AN102 (1205).
- the BSN 104 determines the cycle number to be used and the sequence number in the cycle based on the cycle number n and BS N time transmitted in the path establishment response 1204, assigns them to the data transmission packet, and transmits them to the AN 102 and AN 103 ( 1206).
- AN102 and AN103 calculate the wireless transmission time for the received distribution data based on the period number and the sequence number in the period assigned to the received packet, and when the calculated time is reached, Transmission is performed (1207).
- AN102 and AN103 are synchronized by GP S106, and the algorithm for calculating the wireless transmission time from the period number received from BSN104 and the sequence number in the period is the same, and AN102 and AN103 are the same GPS time. Since synchronization is performed, wireless transmission times can be matched.
- FIG. 8 is a time chart from when the BSN 104 transmits a packet received from the content server 105 to when the AN 102 and AN 103 transmit the packet to the radio.
- the AN102 and AN103 outputs are also delivered to the AT101 from the synchronization number 0 and the sequence number 0.
- a 100-byte packet 801 transmitted from the content server 105 is received as a packet 802 by the BSN 104, and the bucket ⁇ 803 and the bucket 804 set to the cycle number (P) 0 and sequence number (S) 0 are respectively set.
- the BSN 104 receives the packet 805 having a length of 50 bytes transmitted from the content server 105 (packet 806), the BSN 104 compares it with the number of Noits that can be transmitted in one cycle received in steps 402 and 1203, and the cycle number (P) To decide.
- packet 807 and knotette 808 set to cycle number (P) 0 and sequence number (S) 100 are set to AN102, Send to AN103.
- the BSN104 received it as a packet 810, and the BSN104 exceeded the number of notes that could be sent in one cycle by sending packets 802 and 806.
- the packet 811 and the packet 812 set to the next cycle number (P) 1 and the reset sequence number (S) 0 are transmitted to AN102 and AN103, respectively.
- AN102 stores packet 803 and packet 807 in a buffer for cycle number 0, and packet 811 stores it in a buffer for cycle number 1.
- AN103 stores packet 804 and packet 808 in the buffer for cycle number 0, and packet 812 stores it in the buffer for cycle number 1.
- AN102 and AN103 will have the same buffer contents.
- AN102 and AN103 determine the transmission time to based on the transmission time corresponding to cycle number 0 received in advance in steps 403, 1204, etc., and start wireless data transmission from the buffer for cycle number 0 . Therefore, since packet 813 transmitted from AN102 and packet 814 transmitted from AN103 transmit the same data from the same time, AT101 receives packet 813 and packet 814 transmitted from AN102 and AN103 at the same time. Therefore, soft combine becomes possible. Similarly, AN102 and AN103 transmit packet 815 and packet 816 that transmit the same data at the same time, and both the transmission buffers with cycle number 0 of AN102 and AN103 are empty, and transmission during the period with cycle number 0 is not performed. finish.
- AN102 and AN103 transmit packets 817 and knotts 818 from the buffer power for cycle number 1, respectively.
- FIG. 5 is an explanatory diagram showing a method of calculating the number of Neuts that can be transmitted in one cycle that AN notifies BSN.
- delivery method specified in 3GPP2 standard C.
- S0054-0 vl. 1 transmission in units of ECB (Error Control Block) 501 is specified.
- ECB Error Control Block
- the ECB 501 is composed of a plurality of 1000-bit packets, and includes a data part 502 and a parity part 503.
- the data part is a part in which data received from the BSN 104 is stored, and the NOT part 503 stores an error correction code for correcting a packet error generated in the process of transmitting the data wirelessly.
- ECB501 has a horizontal width of 1000 bits, but it consists of multiple 1000-bit packets. Is possible.
- the first 1000 bits of ECB501 are a block header 504 that represents the first byte of ECB501, a Security Layer Packet 505 for transferring encryption information, a framing header 506 that indicates the start of the data part, and a net data that stores net data. Including part 507.
- the framing header 506 is optional, and it is not necessary to include it when HDLC like framing according to RFC 1662 is performed in BSN, but it is necessary when HDL C like framing is not performed.
- the 1000-bit length of the other data portion 502 includes a framing header 508 and a net data portion 509.
- the number of bytes that can be transmitted in one cycle is calculated by calculating how many bytes the net data part included in the ECB is included in one cycle.
- the ECB force included in one cycle 3 ⁇ 4CB51 0, ECB511, ..., ECB512 is shown, and the total of the net data part indicated by the hatched part included in each ECB is obtained.
- the number of bytes that can be transmitted in one cycle can be obtained.
- Figure 6 shows the packet structure transmitted from BSN to AN.
- Data transmitted from BSN is encapsulated by GRE (General Routing Encapsulation) as defined in RFC2784 and RFC2890!
- GRE General Routing Encapsulation
- a packet transmitted from the BSN to the AN includes an IP header portion 601, a GRE header portion 602, and a data portion 603, and details of the GRE header portion 602 are shown in the lower part of the figure.
- the checksum field is included in the GRE header.
- C bit 604 indicates power
- R bit 605 is a reserved field
- K field 606 indicates whether the key field is included in the GRE header
- GRE There is an S field 607 and a reserved field 608 indicating whether or not to include a sequence number in the header.
- the C bit 604 is set to 0 because the checksum field is not used, the reserved bit 605 is set to 0, the key field is used, the K bit 606 is set to 1, and the sequence number is set to S.
- the continuation of the reserved field 608 and the GRE version fee There are 609 powers. Reserved fields 608 are all set to 0, and GRE version 609 is also set to 0.
- the third and fourth octets include a protocol type field 610 indicating the protocol of the packet included in the data portion 603 of the packet, and set to 8881H indicating the Unstructured Byte Stream.
- the 8th octet contains a key field 611 indicating the GRE key.
- This key field 611 is set to a value specified by a path establishment request (401 or 1203) transmitted from the AN. Power used as GRE sequence number from 9th octet to 12th octet In this embodiment, this sequence number field is divided into two fields of period number 612 and sequence number 613 in the period.
- the cycle number 612 is a number that is incremented by one every time the transmission cycle changes. Sequence number 613 in the cycle indicates how many bytes of data in the cycle indicated by cycle number 612 is the first byte included in data portion 603 of the GRE packet.
- FIG. 7 is a diagram showing a usage example of each field when the cycle number 612 and the sequence number 613 in the cycle shown in FIG. 6 are used.
- the cycle number is set to 0 and the sequence number is set to 0. Since the next packet 702 is transmitted within the same period as the packet 701, the period number is set to the same 0. The sequence number is set to 150 because the first byte of the data part of packet 702 is the 151st byte in the cycle.
- the next packet 703 is similarly set to synchronization number 0 and sequence number 200. Since the next packet 704 is a packet transmitted within the next period, the period number is set to 1. In the subsequent packets 705 and 706, the cycle number and sequence number are set according to the same rule.
- the T (terminate) flag indicating whether or not it is the last packet in the cycle has a GRE header part May be provided.
- the transmission source sets whether or not it is the last packet in the cycle by using the ⁇ flag, and the transmission destination detects the T flag, so that the radio resources reserved for BCMCS within the cycle can be cast. It can be used for other purposes such as data transmission, and has the effect of increasing frequency utilization efficiency.
- FIG. 14 is a diagram showing an example of using the cycle number and sequence number. This figure shows an example when a packet transmitted from the BSN104 power spans a cycle. In this example, the number of bytes that can be transmitted in one cycle is 400 bytes.
- the cycle number is set to 0 and the sequence number is set to 0. Since the next packet 1402 is transmitted within the same cycle as the packet 1401, the cycle number is set to the same 0. The sequence number is set to 150 because the first byte of the data portion of the packet 1402 is the 151st byte in the cycle.
- next packet 1403 Since the next packet 1403 is 300 bytes long, it exceeds the number of notes that can be transmitted in one cycle, but BSN104 has a cycle number of 0 and a sequence number of 200. Transmission processing is performed as data belonging to number 0, and the remaining 100 bytes of data are transmitted as data belonging to cycle number 1.
- the BSN104 transmits the next packet 1404, it is determined that 100 bytes of data belonging to the cycle number 1 have already been transmitted when the previous packet 1403 is transmitted, and the cycle number 1, the sequence number 100. Send as. In the same manner as above, packets 1405 and 1406 and data are transmitted.
- the power of BSN104 which shows how to transmit packets that span the cycle as they are, fragmentation of the payload after performing HDLC like framing or dividing the payload using IP fragmentation, etc. By performing processing, data can be transmitted within the cycle.
- FIG. 9 is a flowchart showing the method for determining the cycle number and sequence number in BSN104.
- the cycle number P during transmission is 0, and transmission is in progress.
- the sequence number S is 0, and the amount of data that can be transmitted in one cycle is d (901).
- the time t managed by the BSN 104 is compared with the wireless transmission time derived from the cycle number and the sequence number. For example, compare the time t with the time corresponding to cycle number 0 and the time obtained by multiplying one cycle time by the cycle number P plus the margin ⁇ that takes into account transmission delay and time lag. By this comparison calculation, it is possible to confirm whether the time t of the BSN 104 is earlier than the radio transmission time from which the cycle number and sequence number power are also derived.
- the BSN 104 can use an appropriate value for performing the software combine as the cycle number and sequence number without performing the buffering process.
- FIG. 15 is a diagram of an example (1) of assigning a cycle number and a sequence number within a cycle. This figure shows an example of updating the cycle number according to the BSN time corresponding to the cycle number.
- AN102 transmits 400 bytes as the number of bytes that can be transmitted in 12 seconds and 7: 59: 50.000 as the BSN time corresponding to cycle number 0 (1501).
- AN102 calculates backward from the time of wireless transmission and must start transmission with BSN104. The time that is not available is calculated as this BSN time and transmitted to BSN104.
- the data belonging to cycle number 0 from AN 102 is started wireless transmission at 8:00: 00.000.
- transmission delay from BSN104 to AN102 processing delay in each device, Assuming that the buffering time is 10 seconds, 7: 59: 50.000 minus 10 seconds is selected as the BSN time corresponding to cycle number 0.
- the BSN 104 uses the BSN time received from the AN 102 and transmits a path establishment response signal including the BSN time 7: 59: 50.000 corresponding to the cycle number 0 and the cycle number 0 to the AN 102 (1502).
- FIG. 16 is a diagram of an example (2) of assigning a cycle number and a sequence number within a cycle. This figure shows an example of updating the cycle number due to exceeding the number of bytes that can be transmitted in one cycle.
- AN102 transmits 400 bytes as the number of bytes that can be transmitted in 12 seconds and 7: 59: 50.000 as the BSN time corresponding to cycle number 0 (1601).
- the BSN 104 uses the BSN time received from the AN 102 to transmit a path establishment response signal including the BSN time 7: 59: 50.000 corresponding to the cycle number 0 and the cycle number 0 to the AN 102 (1 602).
- FIG. 10 is a diagram showing a transmission time determination method in AN. This figure shows the procedure from when AN receives a packet in which a cycle number and a sequence number within a cycle are set up to transmit the packet over the air.
- the wireless packet transmission processing is started.
- This transmission time is the time instructed from the BSN 104 in the procedure 403 and the procedure 1204, and a common time is shared by all ANs.
- the AN extracts the packet from the cycle 0 buffer 1005 and configures the ECB 1008.
- the configuration of ECB1008 is completed, the first packet is modulated in order and transmitted wirelessly (bucket 1009, packet 1010).
- the same packet is transmitted at the same timing for all ANs. Thereafter, similarly, when the transmission time corresponding to the cycle 1 buffer is reached, the packet is transmitted from the cycle 1 buffer 1 006.
- FIG. 11 is a diagram showing a case where BSN and AN are not synchronized in time. This figure shows that when BSN and AN are not available, such as GPS 106 and time server 107 etc. The procedure of the synchronous distribution method between base stations in the case of performing time synchronization will be described.
- the path establishment request (1101) and path establishment response (1102) are transmitted! Need to be established.
- the BSN 104 transmits a data distribution request to the content server 105 (1103).
- the content server starts transmission of distribution data and transmits distribution data to the BSN 104 (1104). This distribution data will continue to be buffered in the BSN 104.
- the AN 102 transmits a data transmission request including the sequence number and the requested data amount to the BSN 104 (1105).
- the data with the specified sequence number is sent to the AN 102.
- the data amount to be transmitted is transmitted so as not to exceed the requested data amount specified in step 1005 (1106).
- the sequence number power When the AN 102 receives the distribution data, the sequence number power also calculates the transmission time, and transmits the distribution data at the calculated transmission time (1107). These procedures are repeated in a similar manner (1108, 1109, 1110, 1111).
- the sequence number and data amount used by AN102 that knows the transmission timing in this way and instructing BSN104, synchronous distribution of data is possible even if BSN104 and AN102 are not synchronized in time. Become.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
- Time-Division Multiplex Systems (AREA)
Abstract
Description
Claims
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP05816569.7A EP1903690A4 (en) | 2005-07-08 | 2005-12-19 | SYNCHRON ABLIEFERVERFAHREN |
US11/994,916 US8228892B2 (en) | 2005-07-08 | 2005-12-19 | Synchronous delivery method |
CN200580051019.8A CN101223712B (zh) | 2005-07-08 | 2005-12-19 | 同步分发方法 |
US13/555,222 US8855146B2 (en) | 2005-07-08 | 2012-07-23 | Synchronous delivery method |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2005200337A JP4705814B2 (ja) | 2005-07-08 | 2005-07-08 | 同期配信方法 |
JP2005-200337 | 2005-07-08 |
Related Child Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/994,916 A-371-Of-International US8228892B2 (en) | 2005-07-08 | 2005-12-19 | Synchronous delivery method |
US13/555,222 Continuation US8855146B2 (en) | 2005-07-08 | 2012-07-23 | Synchronous delivery method |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2007007426A1 true WO2007007426A1 (ja) | 2007-01-18 |
Family
ID=37636832
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2005/023288 WO2007007426A1 (ja) | 2005-07-08 | 2005-12-19 | 同期配信方法 |
Country Status (5)
Country | Link |
---|---|
US (2) | US8228892B2 (ja) |
EP (1) | EP1903690A4 (ja) |
JP (1) | JP4705814B2 (ja) |
CN (2) | CN101223712B (ja) |
WO (1) | WO2007007426A1 (ja) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20100110958A1 (en) * | 2006-11-01 | 2010-05-06 | Racz Andras | Method for content synchronization when broadcasting data in a wireless network |
Families Citing this family (25)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP4783179B2 (ja) * | 2006-03-07 | 2011-09-28 | 株式会社日立製作所 | エリア管理システム |
US20080025241A1 (en) * | 2006-07-28 | 2008-01-31 | Naga Bhushan | Method and apparatus for broadcast multicast service in an ultra mobile broadband network |
US8014331B2 (en) * | 2006-07-28 | 2011-09-06 | Qualcomm Incorporated | Method and apparatus for using a MAC protocol for broadcast |
JP4866761B2 (ja) * | 2007-03-07 | 2012-02-01 | 株式会社エヌ・ティ・ティ・ドコモ | 移動通信システム、ユーザ共通データ伝送装置及び無線基地局 |
US7903540B2 (en) | 2007-08-02 | 2011-03-08 | Alvarion Ltd. | Method and device for synchronization in wireless networks |
JP5156959B2 (ja) * | 2008-01-18 | 2013-03-06 | ソフトバンクモバイル株式会社 | 通信制御システム、通信制御方法、およびプログラム |
JP5173541B2 (ja) * | 2008-04-04 | 2013-04-03 | ソフトバンクテレコム株式会社 | コンテンツデータ送信システム |
JP5150830B2 (ja) * | 2008-08-29 | 2013-02-27 | 株式会社Otsl | 通信システム及び通信方法 |
US9596634B2 (en) * | 2008-12-19 | 2017-03-14 | Telefonaktiebolaget Lm Ericsson (Publ) | Assist reordering of downlink data at serving GW relocation |
JP5351790B2 (ja) * | 2010-01-29 | 2013-11-27 | ソフトバンクモバイル株式会社 | 通信システム及び通信制御方法 |
GB201007191D0 (en) * | 2010-04-29 | 2010-06-09 | British Broadcasting Corp | Content provision system |
US8873760B2 (en) * | 2010-12-21 | 2014-10-28 | Motorola Mobility Llc | Service key delivery system |
JP5635928B2 (ja) * | 2011-03-22 | 2014-12-03 | 株式会社日立製作所 | ネットワークシステム、及び通信装置 |
EP2723115A4 (en) * | 2011-06-17 | 2015-07-01 | Fujitsu Ltd | COMMUNICATION SYSTEM, DATA TRANSFER DEVICE, BASE STATION, MOBILE DEVICE AND COMMUNICATION PROCESS |
US9241632B2 (en) * | 2011-07-20 | 2016-01-26 | Biosense Webster (Israel) Ltd. | Synchronization of wireless catheters |
JP5817664B2 (ja) * | 2012-03-19 | 2015-11-18 | カシオ計算機株式会社 | 撮像装置、撮像方法及びプログラム |
JP6516402B2 (ja) * | 2013-10-31 | 2019-05-22 | 株式会社Nttドコモ | ユーザ装置、及びレイヤ2状態制御方法 |
CN105471825B (zh) * | 2014-09-03 | 2019-08-23 | 南京中兴软件有限责任公司 | 丢失数据报文的识别方法及装置 |
KR102460350B1 (ko) * | 2015-11-06 | 2022-10-28 | 삼성전자주식회사 | 통신 시스템에서 데이터 송수신 방법 및 장치 |
KR102386305B1 (ko) * | 2017-07-25 | 2022-04-14 | 삼성전자주식회사 | 무선 네트워크 시스템에서 트래픽을 처리하는 방법 및 장치 |
JP6882684B2 (ja) * | 2017-09-04 | 2021-06-02 | 富士通株式会社 | 通信装置、通信システム、通信制御方法、及び通信制御プログラム |
US10728912B2 (en) * | 2017-09-15 | 2020-07-28 | Qualcomm Incorporated | System and method of modes for data transmission |
CN110518964B (zh) * | 2019-09-06 | 2021-06-08 | 中国电子科技集团公司第五十四研究所 | 一种基于光载无线网络的卫星地面站高精度时间同步方法 |
CN117751556A (zh) * | 2021-06-22 | 2024-03-22 | 三菱电机株式会社 | 通信监视系统、基站、历史管理服务器以及通信监视方法 |
CN117295148B (zh) * | 2023-11-22 | 2024-02-23 | 泉州艾奇科技有限公司 | 一种时间同步方法、中控主机及无线设备 |
Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH10136424A (ja) * | 1996-10-25 | 1998-05-22 | Mitsubishi Electric Corp | 移動体通信システム |
EP1372350A1 (en) | 2002-06-14 | 2003-12-17 | Samsung Electronics Co., Ltd. | Soft handover of a common channel in an asynchronous CDMA mobile communication system providing MBMS services |
US20040008646A1 (en) | 2002-04-27 | 2004-01-15 | Samsung Electronics Co., Ltd. | Soft handover method for multimedia broadcast/multicast service in a CDMA mobile communication system |
US20050094618A1 (en) | 2003-11-05 | 2005-05-05 | Erik Colban | Method of synchronizing broadcast streams in multiple soft handoff sectors |
US20050128996A1 (en) * | 2003-11-07 | 2005-06-16 | Akihiko Yoshida | Radio communication apparatus |
EP1549088A2 (en) | 2003-12-26 | 2005-06-29 | NTT DoCoMo, Inc. | Downlink control channel common to a plurality of cells |
Family Cites Families (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP3513465B2 (ja) * | 2000-02-22 | 2004-03-31 | シャープ株式会社 | 無線通信送信機及び無線通信受信機 |
KR101015768B1 (ko) * | 2003-09-13 | 2011-02-22 | 삼성전자주식회사 | 이동통신 시스템에서 방송 컨텐츠 프레임의 동기화 방법 |
JP4687061B2 (ja) * | 2003-11-07 | 2011-05-25 | 株式会社日立製作所 | 無線通信装置及び無線通信システム |
-
2005
- 2005-07-08 JP JP2005200337A patent/JP4705814B2/ja not_active Expired - Fee Related
- 2005-12-19 CN CN200580051019.8A patent/CN101223712B/zh not_active Expired - Fee Related
- 2005-12-19 EP EP05816569.7A patent/EP1903690A4/en not_active Withdrawn
- 2005-12-19 CN CN201210020859.XA patent/CN102572712B/zh not_active Expired - Fee Related
- 2005-12-19 WO PCT/JP2005/023288 patent/WO2007007426A1/ja active Application Filing
- 2005-12-19 US US11/994,916 patent/US8228892B2/en not_active Expired - Fee Related
-
2012
- 2012-07-23 US US13/555,222 patent/US8855146B2/en not_active Expired - Fee Related
Patent Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH10136424A (ja) * | 1996-10-25 | 1998-05-22 | Mitsubishi Electric Corp | 移動体通信システム |
US20040008646A1 (en) | 2002-04-27 | 2004-01-15 | Samsung Electronics Co., Ltd. | Soft handover method for multimedia broadcast/multicast service in a CDMA mobile communication system |
EP1372350A1 (en) | 2002-06-14 | 2003-12-17 | Samsung Electronics Co., Ltd. | Soft handover of a common channel in an asynchronous CDMA mobile communication system providing MBMS services |
US20050094618A1 (en) | 2003-11-05 | 2005-05-05 | Erik Colban | Method of synchronizing broadcast streams in multiple soft handoff sectors |
US20050128996A1 (en) * | 2003-11-07 | 2005-06-16 | Akihiko Yoshida | Radio communication apparatus |
EP1549088A2 (en) | 2003-12-26 | 2005-06-29 | NTT DoCoMo, Inc. | Downlink control channel common to a plurality of cells |
Non-Patent Citations (2)
Title |
---|
"Interoperability Specification (IOS)for cdma2000 Access Network Interfaces - Part5 (A3 and A7 Interfaces) (3G-I0S v5.0)", 3GPP A. S0015-C VERSION 1.0, February 2005 (2005-02-01), pages 1 - 32, XP002996586 * |
See also references of EP1903690A4 * |
Cited By (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20100110958A1 (en) * | 2006-11-01 | 2010-05-06 | Racz Andras | Method for content synchronization when broadcasting data in a wireless network |
US8873447B2 (en) * | 2006-11-01 | 2014-10-28 | Telefonaktiebolaget L M Ericsson (Publ) | Method for content synchronization when broadcasting data in a wireless network |
US9686057B2 (en) | 2006-11-01 | 2017-06-20 | Telefonaktiebolaget Lm Ericsson (Publ) | Method for content synchronization when broadcasting data in a wireless network |
US10582475B2 (en) | 2006-11-01 | 2020-03-03 | Telefonaktiebolaget Lm Ericsson (Publ) | Method for content synchronization when broadcasting data in a wireless network |
US11006388B2 (en) | 2006-11-01 | 2021-05-11 | Telefonaktiebolaget Lm Ericsson (Publ) | Method for content synchronization when broadcasting data in a wireless network |
Also Published As
Publication number | Publication date |
---|---|
CN101223712A (zh) | 2008-07-16 |
JP4705814B2 (ja) | 2011-06-22 |
JP2007019960A (ja) | 2007-01-25 |
CN101223712B (zh) | 2012-04-04 |
US20090296631A1 (en) | 2009-12-03 |
US8855146B2 (en) | 2014-10-07 |
EP1903690A4 (en) | 2013-07-24 |
EP1903690A1 (en) | 2008-03-26 |
CN102572712A (zh) | 2012-07-11 |
US20120287841A1 (en) | 2012-11-15 |
CN102572712B (zh) | 2014-12-31 |
US8228892B2 (en) | 2012-07-24 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
JP4705814B2 (ja) | 同期配信方法 | |
US11006388B2 (en) | Method for content synchronization when broadcasting data in a wireless network | |
US8005085B2 (en) | Method for distribution of data packets in a single frequency mobile communication network, an access network node, a base station and a single frequency mobile communication network therefor | |
JP3676977B2 (ja) | Gprsにおけるデータ送信方法 | |
JP5225457B2 (ja) | 1つのゲートウェイと複数の基地局との間の同期を行うための方法、並びに対応するゲートウェイおよび基地局 | |
WO2004105418A1 (ja) | 無線ネットワークシステムにおけるノード間同期方法、無線コントロールサーバおよび無線ベアラサーバ | |
US20110199973A1 (en) | Method, device, and system for configuring multicast broadcast single frequency network resources | |
WO2008113265A2 (fr) | Procédé, dispositif et station de base pour générer une unité de données de protocole | |
WO2011038668A1 (zh) | 处理子帧的方法和设备 | |
KR20080018055A (ko) | 패킷 데이터 송수신 방법 및 장치 | |
JP5107415B2 (ja) | 同期配信方法 | |
JP4942834B2 (ja) | 同期配信方法 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
REEP | Request for entry into the european phase |
Ref document number: 2005816569 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2005816569 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 200580051019.8 Country of ref document: CN |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWW | Wipo information: withdrawn in national office |
Ref document number: DE |
|
WWP | Wipo information: published in national office |
Ref document number: 2005816569 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 11994916 Country of ref document: US |